| Summary: | Plasma Live - MCC fails to launch from Welcome screen or panel | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Len Lawrence <tarazed25> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | isobuild, kde, mageia, mageiatools, marja11 |
| Version: | Cauldron | Keywords: | 6sta2 |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | Journal file from Plasma Live session fail to launch mcc | ||
|
Description
Len Lawrence
2017-01-22 13:03:17 CET
Tested on a 64bit EFI machine with 32GB RAM and there is no sign of this bug. (In reply to Len Lawrence from comment #0) > Description of problem: > After a successful Live boot from a USB device the desktop works but MCC > cannot be launched from the Welcome screen nor from the panel but can be > invoked under su from konsole. In MCC there is no admin password request > (perhaps because there is no password) and panel invocation fails silently. > Please attach journal.txt that is the result of running, as root: journalctl -ab > journal.txt from right after you reproduce this issue CC:
sysadmin-bugs =>
kde, mageiatools, marja11 I opened up the laptop and resumed a suspended Live session and copied the journal file as requested after verifying that the problem still existed. See attachment. The gui attempts to establish itself; an empty frame flashes up for a split second, in both cases - panel and welcome screen. One other thing to note is that there was a flashing icon on the panel saying that disk space was low. After a reboot this morning the problem had gone away; mcc launched normally and the low disk space warning had vanished. Created attachment 8892 [details]
Journal file from Plasma Live session fail to launch mcc
Even if Plasma5 is greedy, 4GB RAM for Live mode should be enough, I think. I don't see something specific when you try to start MCC at the end of the log, but there are 143 Plasma5 related errors before that: [marja@localhost ~]$ zcat Downloads/20160journal.txt.gz | grep -i error | grep -v pulse | wc -l 143 [marja@localhost ~]$ I've seen such error before in logs of bug reports that were recently assigned to KDE team, but can't tell whether one or more of those bug reports should be closed as duplicate of another one, nor whether e.g. the first error in your log triggers the following errors, or whether the errors in your log are about several issues Keywords:
(none) =>
6sta2 (In reply to Marja van Waes from comment #5) > Even if Plasma5 is greedy, 4GB RAM for Live mode should be enough, I think. > Otoh, if baloo is running and indexing your mounted 2TB drive with a million files ;-) @ isobuilders Baloo won't run in Live mode, will it? CC:
(none) =>
isobuild @ marja I ran it up again and still no trouble with mcc. journalctl records 18 errors this time. $ cat journal.txt | grep -i baloo Jan 23 14:07:38 localhost kdeinit5[14820]: kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/baloosearchmodule.so" Nothing containing "baloo" registered with ps aux. Len, please don't put [6sta2] in the summary field, which we want as clean as possible. Using the 6sta2 keyword is enough. Summary:
[6sta2] Plasma Live - MCC fails to launch from Welcome screen or panel =>
Plasma Live - MCC fails to launch from Welcome screen or panel Apologies. is it still valid with sta2 isos ? CC:
(none) =>
mageia Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Resolution:
(none) =>
OLD |