Am Dienstag, 26. Juli 2016, 09:02:03 schrieb Bruno Friedmann:
So, can you please try to rename ~/.config/ksmserverrc and enable session management?
here's the file attached below
Ok, so the automatically started applications are: program1=kwin_x11 program2=/ioda/home/bruno/.dropbox-dist/dropbox-lnx.x86_64-6.4.14/dropbox program3=pulseaudio program4=/usr/bin/konsole program5=/usr/bin/korgac program6=/usr/bin/kwalletmanager program7=/usr/bin/dolphin As the crash apparently doesn't appear when you disable session management, I strongly suspect one of those is crashing on login. Do those applications get started fine, i.e. are all of them running after login? If one is not, it's likely the culprit. One thing I find a bit strange here is that pulseaudio is in the list. There should be no need to start it via session management, and the restartCommand is empty anyway (that *may* even be what causes the crash I suppose...). Try to add "pulseaudio" to the list of excluded applications in "Configure Desktop"->"Startup & Shutdown"->Session Management, maybe it helps. (or, if you prefer, you can also try to disable pulseaudio completely in YaST) If not, to verify that the crash is indeed caused by the ksmserverrc content, try to remove/rename the file after you logout, before you login, and check whether the crash is gone or still there.
If you run "coredumpctl", it may show you the crash at logout too. It's stored. The crash dump you posted is definitely a crash when kactivitiymanagerd quits.
That's the part where we «disagree» :-) the timestamps of the crash are really when I login (autologin to be more precise)
You mean the kactivitymanagerd crash? But it is crashing on exit, have a look at the backtrace, the crash happens when the database is closed. Maybe it doesn't quit immediately on logout, but only later after a while... In any case, that crash with that backtrace you posted is a known problem (in Qt5), so no need to report it. A workaround has been added to kactivitymanagerd a while ago, but it turned out to not work (and has been removed again since).
Now I've deeply inspected when I start and shutdown the computer and kdeinit5 crash appear in fact on shutdown.
If things are crashing, it may be worth to report them upstream, though you already did, didn't you? (I haven't really compared the backtraces right now) But at least you should mention that the crashes occur in fact on shutdown.
No I've not yet report it upstream, because I would like to make a as precise as possible report, against the right component.
You did mention a bug report you filed months ago in your opening mail. And I noticed that you filed a second one too, about a kdeinit crash. This last crash shows exactly the same symptom, namely "Cannot open display". Considering this, I don't really think that this one happens on logout/shutdown, I have to say. I don't think anything would launch kdeinit after the display is closed on shutdown. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org