Running multiple xorg tear (:0 and :1), both running plasmashell. :0 keeps on running stably :1 crashes either the whole session or just the plasmashell within 24h The difference between the two sessions is that :0 is the one which is most used and is in focus while :1 crashes. Graphics driver: nVidia 370.28 kde-plasma/plasma-workspace-5.7.4:5::gentoo USE="calendar geolocation handbook qalculate" Reproducible: Always Steps to Reproduce: 1. Setup desktop manager to start up two or more tears, say :0 and :1 2. Login with user A or B in :0 3. Login with the other user on :1 4. switch between users with ctrl-alt f7/f8 5. switch to user on :0 and leave the machine running over night 6. switch to user on :1 in the morning Actual Results: either session or plasmashell has crashed Expected Results: The session should be in the same state as it was when you switched to :0 Only plasma widget is the desktop files. Do not find any information in ~/.xsession-error that seems to be related to plasmashell, no core file.
If there's a crash it would help if we can see a backtrace. Please reopen with one, thanks.
Someone linked me to the G+ post, so I got a bit more info. When you say the "session has crashed" what does that mean? Can you still run krunner with alt+space? We don't do core files generally in KDE code, as we have our own debug hander, drkonqui, normally this prompts you with a backtrace and you should have a big dialog saying about this. (unless explicitly disabled, in which case, don't) The other option is to manually launch plasmashell from a konsole From konsole kquitapp5 plasmashell gdb plasmashell then when you come back and it's crashed type: - "thread apply all bt" and copy and paste the pages of data. I'll also try the multiple sessions thing tonight, and see.
With "session has crashed" I mean I'm back at the desktop manager and required to login again. When only plasmashell has crashed, I can still use yakuake and from there restart plasmashell, which usually will last a shorter time than the previous plasmashell and may lead to that the whole session dies (back out at the desktop manager) in the end. When the plasmashell has crashed, I do have the bug reporter started, and it just says there ain't enough information when I select to send in the report (so really not sure if it does send or not). I do always klick in the option that I know what I was doing, but I never get an option to fill in what I was doing (which should be idling). I can't start a plasmashell session and run it in the environment I use, I know it does crash there too.
Created attachment 101215 [details] The output generated while running plasma in gdb
Created attachment 101216 [details] The result of "thread apply all bt"
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!