http://bugzilla.opensuse.org/show_bug.cgi?id=965653 http://bugzilla.opensuse.org/show_bug.cgi?id=965653#c1 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #1 from Wolfgang Bauer --- That kactivitymanagerd crash is likely unrelated and can be ignored. It's a bug in Qt5 and has been workarounded in later versions of kactivities5, but shouldn't cause real problems. The sddm-greeter segfault looks more serious, but would also not cause the desktop session going unresonsive. Maybe it's even just caused by you killing the X session. More likely IMHO is a graphics driver problem, or something taxed the CPU and/or caused heavy file io or swapping. Might have been baloo, the file indexer, disabling Desktop search should circumvent the problem then. Or it might also have been some other random application going crazy and slowing down your system. As I understand it, the actual problem is "fixed" now, right? If not, a look at "top" when it happens might provide a clue... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=965653 http://bugzilla.opensuse.org/show_bug.cgi?id=965653#c3 --- Comment #3 from andreas bittner --- Well the whole desktop was rather semi-reactive and I first wanted to sudo zypper ref in a simple kterm, nothing else was running on the default kde desktop. the command wouldnt execute or print its lines that it was fetching stuff from the servers so I got impatient and try to cancel it, not much was happening and suddenly I couldnt even move around a window or make it react. there wasnt cpu load according to w which eventually executed, and there wasnt any disk activity ongoing. So then I decided to kill the desktop, as I have reported about those other bugs where the xserver and related stuff was hanging because of dbus and related stuff, but that bug causes huge cpu load on xorg process. but this incident is different. I have no more information on this. Later from alt+f1 i restarted the display-manager.service and things became normal again after that. I dont know what processes or parts have been waiting or hanging or why, but something was wrong. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=965653 http://bugzilla.opensuse.org/show_bug.cgi?id=965653#c5 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |maintenance@opensuse.org Resolution|WORKSFORME |--- Flags| |needinfo?(maintenance@opens | |use.org) --- Comment #5 from Wolfgang Bauer --- On further thought, if the maintenance team agrees, we probably should add the KDE workaround for the kactivitymanagerd crash to the running update. You are not the first one to "complain" about that message in the logs (although it shouldn't cause any real problems)... (unfortunately I committed an update for another crash yesterday just hours before you reported this, otherwise I would just have added it right away). But again, this crash is very likely not the reason for your issue. @Maintenance Team: What do you think? Shall I submit a followup update? This is the upstream commit: https://quickgit.kde.org/?p=kactivities.git&a=commit&h=0f44684fb43563565d9926d444a642ca1a5d52ca -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=965653 http://bugzilla.opensuse.org/show_bug.cgi?id=965653#c7 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS --- Comment #7 from Wolfgang Bauer --- Ok, I backported the upstream commit to our Leap package and submitted it: https://build.opensuse.org/request/show/358533 This should fix the (harmless) kactivitymanagerd crash on logout, which is mentioned in the title of this bug report. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=965653 http://bugzilla.opensuse.org/show_bug.cgi?id=965653#c10 --- Comment #10 from andreas bittner --- is this supposed to be fixed already? i just looked at my dmesg and it prints [339876.511255] kactivitymanage[1916]: segfault at 7f20c80e9d10 ip 00007f20c810069a sp 00007fff57a246c8 error 4 in libQt5Sql.so.5.5.1[7f20c80eb000+3f000] [Mar30 18:07] kactivitymanage[1916]: segfault at 7f20c80e9d10 ip 00007f20c810069a sp 00007fff57a246c8 error 4 in libQt5Sql.so.5.5.1[7f20c80eb000+3f000] all updates applied at the moment. which kactivitymanagerd /usr/bin/kactivitymanagerd linux:#~ rpm -qf /usr/bin/kactivitymanagerd kactivities5-5.19.0-11.2.x86_64 Linux linux 4.1.15-8-default #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab) x86_64 x86_64 x86_64 GNU/Linux # zypper ref Repository 'openSUSE-Leap-42.1-Oss' is up to date. Repository 'openSUSE-Leap-42.1-Update' is up to date. All repositories have been refreshed. linux:~ # zypper lu Loading repository data... Reading installed packages... No updates found. linux:~ # date Wed Mar 30 18:10:30 CEST 2016 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=965653 http://bugzilla.opensuse.org/show_bug.cgi?id=965653#c12 --- Comment #12 from Wolfgang Bauer --- (In reply to andreas bittner from comment #10)

is this supposed to be fixed already?

i just looked at my dmesg and it prints

[339876.511255] kactivitymanage[1916]: segfault at 7f20c80e9d10 ip 00007f20c810069a sp 00007fff57a246c8 error 4 in libQt5Sql.so.5.5.1[7f20c80eb000+3f000]

Well, the patch for the upstream bug report has been added to our 5.16.0 packages, and it is included upstream in 5.18.0 and higher. So yes, it is supposed to be fixed. Either the fix is not working, it broke again in 5.19.0, or this is a new/different crash. But again, this is harmless. Feel free to add a comment to the upstream bug report, although it is still open and confirmed though. https://bugs.kde.org/show_bug.cgi?id=348194 -- You are receiving this mail because: You are on the CC list for the bug.