Description of problem:
After updating a 64-bit Mageia-5 installation with Cauldron (to the point where Urpmi reports "Packages are up to date"):
(1) 'Plasma' is not offered at Login
(2) After Logging in with KDE, the screen goes blank and stays blank,
EXCEPT for a confirmation that Yakuake (from a user startup config) has been started - and can be used from PF12.
Version-Release number of selected component (if applicable):
Cauldron as of 9/9/2015.
Steps to Reproduce:
1. Install 64-bit KDE Mageia-5 on netbook (Samsung NC110).
2. urpmi -auto-update --auto (checked first with "--test" option) until reports "Packages are up to date" (in this case 9/9/2015)
3. Reboot and note that:
(a) At login, 'KDE' is offered; no sign of 'Plasma'
(b) After KDE login, screen goes blank, except for a report that 'Yakuake has been started' (and is usable!)
Steps to Reproduce:
Created attachment 7001 [details]
(MB) Log of cauldron update 9/9/15 "Packages are up to date"
Log of update showing 'Packages are up to date".
N.B. One difference between the updates on netbook and on PC is:
On netbook, booting shows "Starting version 225", whereas
on PC. booting shows "Starting version 224".
rpm -qa | grep plasma
rpm -qa | grep plasma
I'm wondering if something in the netbook's spec is failing the criteria for offering Plasma5.
(E.g. screen resolution of 1024x600, which I saw somewhere prevents Windows 10 running.)
There has been no problem installing/running Mageia-5 and earlier, although I've never been able to get the video output onto an external monitor.
After this afternoon's Cauldron update including plasma-workspace and a reboot, I now - for the 1st time - see 'Plasma' offered as DM on login screen rather than KDE!
Sadly, Login once again gave a blank screen (apart from a hollow 'X' mouse pointer and a report that 'Yakuake has been started').
> screen resolution of 1024x600
In today's Cauldron update (including new kernel) I saw that a 'default screen resolution of 1024x768' had been set.
Still wondering what is preventing a successful Plasma5 login.
(Get just blank screen, apart from "Yakuake started" report.)
(In reply to Maurice Batey from comment #6)
> > screen resolution of 1024x600
> In today's Cauldron update (including new kernel) I saw that a 'default
> screen resolution of 1024x768' had been set.
That's an expected behaviour due to bug 763.
> That's an expected behaviour due to bug 763.
Which says "...leave this bug for mga6 and list ALL the DMs and DE's (possibly in different BZs and have them blocking this one... in order to get it fixed for real."
Is that what's failing the Plasma5 login here, though?
(In reply to Maurice Batey from comment #8)
> > That's an expected behaviour due to bug 763.
> Which says "...leave this bug for mga6 and list ALL the DMs and DE's
> (possibly in different BZs and have them blocking this one... in order to
> get it fixed for real."
> Is that what's failing the Plasma5 login here, though?
No I don't think it's related to your issue at all. Bug 763 is just about the default background symlink pointed to an image of the wrong resolution, in the worst case if it affected Plasma you would have a badly scaled background. And the bug itself is worked around via a script at boot, so it shouldn't be an issue. I was just pointed you to the bug report FYI, but that was to indicate that it's a false alert probably non relevant for your issue.
> ... for the 1st time - see 'Plasma' offered as DM on login screen
But - after 11 days of clean Cauldron updates - the plasma login still ends up with a blank screen instead of the kaleidoscope - though Yakuake is usable.
By removing Yakuake (thanks to a hint from Claire), I can now achieve a successful Plasma5 login on the netbook.
Will raise bug report if necessary.
Question is, why does Yakuake freeze the Plasma login on the netbook when it doesn't on the PC?
N.B. The Yakuake problem is now in:
Broadcom WiFi working fine on netbook, though cannot see 'network status' icon (presumably because of missing systray).
Issue was fixed as of comment 5, the rest is about different issues (some fixed, some current, but they don't belong in this bug report).