New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pantheon session crash after lock or suspend with multi-monitors #60082
Comments
Steps 3-5 look exactly how a crash in a session would look like, also assuming you're using the default gtk LightDM greeter. But these logs look like X died took everything with it. |
correct
i try to get one
|
I tried to enable core dumps, but the documentation is not clear how to do. #60088 I don't get coredumps after applying the changes and rebooting. But when locked, the system don't reacts on keaboard input, mouse or touchpad interaction. Only clicking the power button let the device shut down. Suspending still let the session crash. But no core dump. |
Have you tried switching to a tty with the shortcut? Also, when having issues with locking and suspending, it could be two independent issues so I'd need to know
|
Edit: saw the video, (felt the frustration 😄) and going with debugging locking specifically where That's a multi-monitor setup if I'm not mistaken? |
yes. it's a thinkpad on a docking station with 2 external displays. this strange thinkpad has also a dedicated radeon GPU, but it has worse performance than the integrated intel gpu when open source drivers are used, so it's ok it is not used. but that might also cause trouble...
that works. then i can also go back and login again, to a new session.
shortcut or menu in upper right
menu
only way is to go to a tty and back to tty 7, then you can login
when hit ENTER, the login screen appears. again login 3 times to new session. moving and clicking mouse does nothing |
✨ I can reproduce steps 3-5 with a multi-monitor setup. I tested that with a laptop with |
I have a |
I can confirm that unlock and resume works without external displays. When trying to unlock, the display still remains dark. I have to go to a tty and back to tty 7, multiple times. Same when bootet without external displays. Now i saw the "This session is locked" when i go back to tty 7, some seconds later i get the login screen. |
That sounds exactly like the-cavalry/light-locker#138 Edit: sounds like light-locker can't switch back to the greeter properly |
in gnome on NixOS 18.09 i had no issues with locking (with GDM! with lightdm locking probably still don't work). but with Xfce earlier, that's why i switched to gnome... #38493 (Xfce uses xflock4)
yes, except
i got the login screen in about 2 seconds |
I can now say that there are no core dumps. Did you have some success with debugging? Can i help in some way? |
I'm looking for time to debug, as it's going to be interesting and involved. And you're and have been very helpful btw |
Next step is to get a backtrace with gdb of the |
I tried Obtaining a stack and JS trace using GDB for an already running gnome-shell
but i only got:
(I locked the screen, tried to unlock but screen was dark no matter what i did. after hitting the power button the system shut down) |
Starting GNOME Shell under gdb
@worldofpeace This output is probably not helpful :/ |
This happens also when switching users. |
This is still reproducible.
Locked at Oct 22 16:50, trying to unlock some seconds after, then session crash, then login sucessfully. See syslog.txt |
I'm using my Thinkpad X230 with 1 external display connected via VGA right now and don't have this problem. So the cause might be the other hardware (it has hybrid graphics) or 2 displays (using docking station.) I will try to test with a desktop computer and more than 1 display. |
I tried this out with #73906, and I can't reproduce this issue anymore. But switchboard-plug-display needs to be updated for latest mutter. |
Great. I'm currently in homeoffice and don't have a docking station or multiple monitors here, so i will not be able to test it for some time... But i put it on the list of tasks to do at the office. |
Thanks. It will be merged to nixos-unstable once staging-next gets merged #83618. |
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them. Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel. |
I don't see this anymore. Closing |
Issue description
I have this problem on a Lenovo Thinkpad L470, but not on a Thinkpad X230 or custom gaming PC.
I had issues with X11 sessions before on this device, see #44344.
See the log full of errors: https://gist.github.com/davidak/d2de7f9ef515755db76f3b61b102b664
And video: https://peertube.social/videos/watch/2c9d8be7-3adb-48ae-a874-799fd9804dd2
cc @worldofpeace
Steps to reproduce
Technical details
"x86_64-linux"
Linux 4.19.36, NixOS, 19.03.172312.330b9fac600 (Koi)
yes
yes
nix-env (Nix) 2.2.2
"nixos-19.03.172312.330b9fac600, nixos-hardware, nixos-unstable-19.09pre176329.d2602779281"
/nix/var/nix/profiles/per-user/root/channels/nixos
The text was updated successfully, but these errors were encountered: