| Summary: | Klipper crashes when restarting plasmashell | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-knotifications | Reporter: | Elias Probst <mail> |
| Component: | general | Assignee: | Martin Klapetek <mklapetek> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | kdelibs-bugs, mgraesslin |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Elias Probst
2014-05-24 15:10:25 UTC
This happens when plasma is quitting or starting new? And what does systemctl --user restart do exactly? I don't have a systemd to reproduce Ok, some more details: It happens when plasmashell is quitting and seems only to happen, when the shutdown was initiated via 'systemctl' which should actually just send a SIGTERM (the same as using 'killall plasmashell' which somehow doesn't seem to trigger the crash). Using kquitapp5 doesn't seem to trigger the crash. Klipper only crashes when it was running before plasmashell was started. Starting plasmashell first, then klipper, then terminating plasmashell doesn't seem to crash klipper. So here are some more details on how to reproduce this crash: 1. Ensure plasmashell isn't running 2. Ensure klipper isn't running 3. Start klipper 4. Start plasmashell (wait until it has fully initialized, it mostly doesn't happen when terminating plasmashell immediately but only after ~15 secs or more) 5. Stop plasmashell → klipper crashes I'm still trying to find out how to reproduce this crash when sending a plain SIGTERM via 'killall plasmashell'. Will provide an update once I have more on this. Oh, and probably relevant: - the plasmashell.service doesn't have any specific 'kill' options set (see: http://www.freedesktop.org/software/systemd/man/systemd.kill.html) - the plasmashell.service is available here: https://github.com/eliasp/plasma-workspace-units/blob/master/systemd/user/plasmashell.service Thanks for the update. I still cannot reproduce here. Which distro is that btw? Running on Gentoo. All KF5/Plasma components from the 'kde' overlay: http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=summary Qt 5.3.0 from the 'qt' overlay: http://git.overlays.gentoo.org/gitweb/?p=proj/qt.git;a=summary The plasma workspace is not started via 'startkde', but using my own systemd user-session units which are the first stepping stones towards getting proper systemd support into KF5/Plasma: https://github.com/eliasp/plasma-workspace-units/ (still needs a lot of polish + work) Are there any other applications which could behave similar to klipper here, so I could test them to see if I can reproduce this crash with any other KF5 application? > Are there any other applications which could behave similar to klipper here,
> so I could test them to see if I can reproduce this crash with any other
> KF5 application?
anyone using a status notifier and being ported to frameworks. I think that are
not so many (kwalletmanager?), but there is a test application in
frameworks/knotifications/tests.
I can't reproduce this anymore since Klipper provides now a native SNI applet. Closing this bug therefore. It might have also been related to bug#339763 (Missing signal handling in QCoreApplication). I believe it might be #339707 rather. I plan to investigate that one today. |