Comment 54 for bug 2034619
Revision history for this message
| Julian Andres Klode (juliank) wrote Re: gnome-shell gets SIGKILL'd when lock screen in Wayland | #54 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Updates on my end:
Interestingly, I also got my session killed yesterday with an external screen attached, just not one it had seen before. But I was there over the weekend only, so can't continue testing there.
I also created a new user and that shows the same issues, so this is not a user configuration issue, but either system state or a general bug in the code.
As I've said before, I've done plenty of log reading and nothing is in there, just broken pipes and then the message that gnome-shell got killed. Nothing is visible when you bpf trace signals to gnome-shell PID either. I still need to use trace-cmd to ftrace the exit point of gnome-shell to see the path leading to that.
The only reasoning I can see from not getting results from both killsnoop implementations is that the kernel is killing the process itself. But reverting from 6.5 to 6.3 kernel also did not improve things.