DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think it's been around 3 weeks now since I could use KDE (now known as sddm??). I am now reduced to using Gnome Flashback Metacity which is very very spartan (no pampering at all) but at least works. I get as far as the sddm login page which looks like this: (see below)
I then selected "Plasma" from the pull-down menu on the left and the loading bar came up and gradually moved to the right till it completed its journey. At that point KDE/SDDM crashed and a crash-report window opened inviting me to send the report to the KDE site. I tried that but then the KDE crash report crashed opening another crash report window and so on...
After a couple of days things improved. KDE/SDDM no longer crashes, rather it FREEZES. I get a black (not blank, black) screen with a pointer which I can move with my mouse but nothing else. At that point all I can do is Ctl-Alt-F1 to a tty and reboot.
I'm running version 5.3.2-3 of kde-window-manager but I don't fancy going back to 4.11.13-2. I'd rather wait out the storm where I am now.
FWIW, here is some (possibly relevant) output from dmesg:
Code:
[ 41.520979] NET: Registered protocol family 17
[ 43.797117] systemd-logind[2591]: New seat seat0.
[ 43.869588] systemd-logind[2591]: Watching system buttons on /dev/input/event5 (Power Button)
[ 43.869700] systemd-logind[2591]: Watching system buttons on /dev/input/event4 (Power Button)
[ 43.876427] systemd-logind[2591]: Failed to start user service: Unknown unit: user@129.service
[ 43.881753] systemd-logind[2591]: New session 1 of user sddm.
[ 70.999217] systemd-logind[2591]: Failed to start user service: Unknown unit: user@1000.service
[ 71.003897] systemd-logind[2591]: New session 2 of user jdkaye.
[27764.129444] Chrome_ChildThr[3974]: segfault at 0 ip 000000000040c578 sp 00007fb115dfe440 error 6 in plugin-container[400000+68000]
[31657.944489] Chrome_ChildThr[7232]: segfault at 0 ip 000000000040c5d8 sp 00007fb53e4fe440 error 6 in plugin-container[400000+68000]
[36465.115367] Chrome_ChildThr[8696]: segfault at 0 ip 000000000040c5d8 sp 00007fe978ffe440 error 6 in plugin-container[400000+68000]
[40282.717625] Chrome_ChildThr[9596]: segfault at 0 ip 000000000040c5d8 sp 00007f3c3d1fe440 error 6 in plugin-container[400000+68000]
[85752.346094] traps: Web Content[10200] general protection ip:7f9a2f457ac4 sp:7fff897848b0 error:0 in libxul.so[7f9a2e07e000+3c0b000]
[127073.556607] Chrome_ChildThr[32094]: segfault at 0 ip 000000000040c578 sp 00007f92d6a4f440 error 6 in plugin-container[400000+68000]
And here is a crash report I managed to salvage when KDE was crashing rather than freezing:
Code:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9afde8d940 (LWP 3467))]
Thread 4 (Thread 0x7f9ae32ac700 (LWP 3516)):
#0 0x00007f9af8a8a53d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f9af562aebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f9af562afcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f9af934e35c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00007f9af92f2b62 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007f9af91008b4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007f9afb982f05 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7 0x00007f9af910587e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007f9af80830a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#9 0x00007f9af8a9307d in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 3 (Thread 0x7f9ad9e9e700 (LWP 3517)):
#0 0x00007f9af808708f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
#1 0x00007f9ae103ef3b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2 0x00007f9ae103e5b7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3 0x00007f9af80830a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#4 0x00007f9af8a9307d in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 2 (Thread 0x7f9ad81f2700 (LWP 3518)):
#0 0x00007f9af8a8a53d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f9af562aebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f9af562afcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f9af934e35c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00007f9af92f2b62 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007f9af91008b4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007f9afb982f05 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7 0x00007f9af910587e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007f9af80830a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#9 0x00007f9af8a9307d in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 1 (Thread 0x7f9afde8d940 (LWP 3467)):
[KCrash Handler]
#6 0x00007f9af89e2107 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#7 0x00007f9af89e34e8 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#8 0x00007f9af90f2baf in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x000000000045e866 in ShellManager::updateShell() ()
#10 0x000000000045f3c7 in ShellManager::loadHandlers() ()
#11 0x00007f9af9326e8a in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f9af9df3adc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f9af9df8fb0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f9af92f53ab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f9af92f741b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f9af934df33 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f9af562ac3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f9af562af20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f9af562afcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f9af934e347 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f9af92f2b62 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f9af92fa7ac in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x0000000000430a43 in main ()
I don't use Stretch but Sid, but FWIW, KDE has been completely broken during the last two weeks on my system. When I try to open a window, it's borderless and I get a dialog box prompting me to choose between kwin_x11 and metacity, but no matter which one I choose, it doesn't work I get the dialog box again. I think it's related to this bug.
In the meantime I'm using OpenSuse and booting Debian from time to time to see if the new upgrades fix KDE. BTW, when I attempt to dist-upgrade, apt-get wants to remove about 180 packages, so I just do a regular upgrade.
Thanks Odiseo77. I read through that bug reference you posted and found the solution. It involved upgrading one package to Sid and keeping another package at Stretch. It involved using the 5.3.2-4 version of breeze but keeping other packages at their Stretch version. I can't say I'm in love with all the changes but I guess this is typical when a DE changes suddenly and radically. Anyway KDE is usable again.
Cheers,
jdk
Just in case, if there's anyone who doesn't want to install the sid version of breeze, you can also simply install openbox, then remove kwin-x11 and go into systemsettings and set openbox as the KDE window manager. At that point you can reinstall kwin-x11 for when everything is fixed, as the openbox window manager works fine as an alternative to kwin.
Good suggestion, Timothy. After one day of Plasma5 Gnome Flashback Metacity is starting to look more appealing. I rate functionality over eye-candy and Plasma is looking a bit too sweet and functioning a bit too sour for my taste.
jdk
Good suggestion, Timothy. After one day of Plasma5 Gnome Flashback Metacity is starting to look more appealing. I rate functionality over eye-candy and Plasma is looking a bit too sweet and functioning a bit too sour for my taste.
jdk
It does have issues. Supposedly 5.4 will fix a LOT of issues, and add some of the MULTITUDES of missing features back. Not sure when 5.4 will be out, however. In the meantime, I've switched to LXQT on one of my machines, and considering going to trinity desktop on another. I will keep KDE on one of my machines just to track if they do improve any, but given it's been over a year since 5 was released, and it's still basically unusable, I don't have a great deal of confidence.
Last edited by Timothy Miller; 08-22-2015 at 03:33 PM.
Thanks Odiseo77. I read through that bug reference you posted and found the solution. It involved upgrading one package to Sid and keeping another package at Stretch. It involved using the 5.3.2-4 version of breeze but keeping other packages at their Stretch version. I can't say I'm in love with all the changes but I guess this is typical when a DE changes suddenly and radically. Anyway KDE is usable again.
Cheers,
jdk
Didn't know the latest version of Breeze fixed the problem (must have missed that part of the bug report). Installed it and got my desktop working again. Thanks for letting me know!
However, the new windows borders are an abomination (a light blue bar at the top more than one centimeter width) and I can't change them because Systemsettings won't open. I guess I'll keep using OpenSuse in the meantime and use Debian again when KDE is fixed.
Didn't know the latest version of Breeze fixed the problem (must have missed that part of the bug report). Installed it and got my desktop working again. Thanks for letting me know!
However, the new windows borders are an abomination (a light blue bar at the top more than one centimeter width) and I can't change them because Systemsettings won't open. I guess I'll keep using OpenSuse in the meantime and use Debian again when KDE is fixed.
Cheers!
Your most welcome. This is why I am a devoted LQ member. Timothy (see above) has given us reason to hope there will be at least some improvement in the (near?) future. Didn't Gnome also do something equally silly a while ago? I remember feeling very smug about being a KDE user back then. I have learned my lesson!
jdk
Yes, the Gnome3/Gnome Shell release. Was essentially unusable for the first few versions. Fedora users were hating life for quite some time because of the issues. They have sorted it out, and while I still think Gnome Shell is ugly, it does work now, although in terms of users, Gnome hasn't yet recovered from that debacle of releasing such a badly designed version, as Mate/Cinnamon/XFCE poached a TON of users. And who knows if they ever WILL recover, of course. I dare say they'll do the same with KDE with v5, although possibly add LXQT since most people who run KDE run it because they prefer QT to GTK, so LXQT to my knowledge the only other full desktop that uses QT beyond KDE.
I most definitely am exceedingly unimpressed with KDE5 in the few months I've been tracking it.
Kde5 not up to much at the moment, too much incompatibility and too many of my favourite apps either not working properly or simply missing. Gone back to stable for a bit while it's sorted out, hope that's not too long.
FYI, plasma 5.4 released today. So those tracking SID should have it fairly shortly available. Those sticking with testing might be a bit until they see it however.
I'm also interested in Plasma 5.4 but I will wait when it hits Stretch. For now KDE 4.14.2 serves me well. I have experience with Plasma 5 on Kubuntu (5.1) and Arch (5.2) a while ago but believe me it was a nightmare! They said that under QT5 KDE will be faster...really? It was laggy as hell. I though they learned they lesson with KDE 4 but...still not.
Did the my morning update as usual. Sure enough, a number of new plasma kde5 packages were included in the "safe" upgrade. Result? KDE now unusable. I reboot and when the login screen appears, I try to login to Plasma as usual. The horizontal narrow, blue progress bar moves along nicely from left to right until it completes its journey. Result: the system freezes at that point. I can ctl-alt-F1 to a tty and have a look at dmesg.
There are a series of error messages (in red) of the form:
Code:
systemd - logind[2588] Failed to start user service: Unknown unit: user@129.service
There were similar entries for "user jdkaye" and "user root" (user@1000.service and user@0.service ).
Soooooo, back to Gnome Flashback Metacity. At least that still works.
Double aaaaarrrrghhhh!
jdk
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
AARRRGGGHHH!!! KDE died again
