Created attachment 7352 [details] .xsession-errors All of Plasma5 is black, except for the cursor and the MageiaWelcome screen, and, a little later, a HPlip pop-up that I always get. XFCE has no such problems My xorg.conf worked well for Plasma5 until the recent updates, but I'm not 100% it is the default configuration or whether I changed anything in the "Device" part to get Plasma5 to work before: Section "Device" Identifier "device1" VendorName "Intel Corporation" BoardName "Intel 810 and later" Driver "intel" Option "DPMS" Option "AccelMethod" "uxa" EndSection attaching .xsession-errors The used laptop is this one: https://wiki.mageia.org/en/User:Marja/QA/Hardware#Lenovo_ThinkPad_SL510
yet one dup of https://bugs.mageia.org/show_bug.cgi?id=17371? (symptoms seem to be same as in https://bugs.mageia.org/show_bug.cgi?id=17450)
CC: (none) => qiilaq69
Indeed. Feel free to mark those as duplicates directly Marek :) *** This bug has been marked as a duplicate of bug 17371 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
(In reply to Marek Laane from comment #1) > yet one dup of https://bugs.mageia.org/show_bug.cgi?id=17371? > (symptoms seem to be same as in > https://bugs.mageia.org/show_bug.cgi?id=17450) The symptoms may be the same, when those bugs were filed my plasma5 still worked fine, so this cannot be a duplicate of either one. My problem dates from after the Plasma5 and KDE applications updates that neoclust started on January 13. I installed all those updates this morning.
Status: RESOLVED => REOPENEDResolution: DUPLICATE => (none)
Indeed, checking the date of the initial post should have let me seen that it might be related to something else. Just to rule this out, what do you get for: rpm -qa | grep database-plugin ?
(In reply to Rémi Verschelde from comment #4) > Indeed, checking the date of the initial post should have let me seen that > it might be related to something else. > > Just to rule this out, what do you get for: > rpm -qa | grep database-plugin > ? I can't boot into the cauldron partition at all atm, not even in RL3 or with an older kernel, there's an avalanche of repeated ata errors that's too fast to read.... it'll be hard to get information for a bug report :-( However, from another partition I can mount the cauldron partitions. grepping the update log from this morning, I see that lib64qt5-database-plugin-mysql-5.6.0-0.beta.7.mga6.x86_64.rpm and lib64qt5-database-plugin-sqlite-5.6.0-0.beta.7.mga6.x86_64.rpm were installed and the matching old versions removed: installing .... lib64qt5-database-plugin-sqlite-5.6.0-0.beta.7.mga6.x86_64.rpm .... 202/387: lib64qt5-database-plugin-sqlite removing package qtbase5-database-plugin-sqlite-5.5.1-1.mga6.x86_64 5/8: removing qtbase5-database-plugin-sqlite-5.5.1-1.mga6.x86_64 .... installing .... lib64qt5-database-plugin-mysql-5.6.0-0.beta.7.mga6.x86_64.rpm .... 385/387: lib64qt5-database-plugin-mysql removing package qtbase5-database-plugin-mysql-5.5.1-1.mga6.x86_64 72/73: removing qtbase5-database-plugin-mysql-5.5.1-1.mga6.x86_64
Summary: Unusable black Plasma5 screen after the recent Plasma5 and KDE Application updates => Unusable black Plasma-5.5.3 screen after the recent Plasma5 and KDE Application updatesSource RPM: (none) => plasma-workspace-5.5.3-1.mga6
CC: qiilaq69 => (none)
Thanks, based on your update log it seems we can confirm that bug 17371 was fixed; but since you still can't boot, there is likely something else that goes wrong. I wouldn't expect the fix for bug 17371 to be the cause of your issue, but that's still something to keep in mind while debugging further.
(In reply to Rémi Verschelde from comment #6) > Thanks, based on your update log it seems we can confirm that bug 17371 was > fixed; but since you still can't boot, there is likely something else that > goes wrong. > > I wouldn't expect the fix for bug 17371 to be the cause of your issue, but > that's still something to keep in mind while debugging further. i don't think not being able to boot into cauldron at all now is related to my black plasma. however, i do admit that i tried to start plasma immediately after the updates, without rebooting first
The HPLIP popup error is https://bugs.mageia.org/show_bug.cgi?id=16946
CC: (none) => ftg
Sorry :-[ I just wanted to run "journalctl --directory /CauldronRoot/var/log/journal/", because of that weird ata errors avalanche. But, even if /CauldronRoot/var/ exists: there is nothing in it. It seems very likely some files on the root partition affecting Plasma got corrupted, too. closing as INVALID
Status: REOPENED => RESOLVEDResolution: (none) => INVALID