-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Strange OS freeze #6351
Comments
What time did you return to the system and find it frozen? Are any of those log entries likely to be relevant? |
I return at about 21:45. Here is additional chunk of log from other file:
And it appears that this is the last records and no logs after 21:47:28 till the new boot. When I returned it shown Wayfire desktop, I'm not sure for 100% but probably I leave it in virtual terminal mode, because I surprised that it shows desktop. But the system was completely unresponsive, mouse didn't worked, keyboard didn't worked. I tried to ssh login to check the logs, but it appears that it don't listen even for ssh connections. I don't remember such freeze for a long time, so I suspect it may be related to virtual terminal, gpm and clipboard with different keyboard shortcuts, like Alt+W, Ctrl+C/Ctrl+V, Cttrl+B and [, Ctrl+B and ], and other, which I played before that issue. |
Could this be related to #6349? You say "I don't remember such freeze for a long time", maybe the virtual terminal is just a coincidence and it's in reality the latest kernel update. |
Describe the bug
I switched to the virtual terminal with Alt+Ctrl+F1 and played with text selection using the mouse and different combinations for copy/paste (I have installed gpm and clipman). Then I left it for 5-10 minutes, and when I came back, the system had frozen. It did not respond to keyboard input or SSH connections.
When it happened, there was a Firefox process running on Wayfire with 3 tabs open.
Steps to reproduce the behaviour
I don't have steps for guaranteed reproduce of the issue.
Device (s)
Raspberry Pi 4 Mod. B
System
Logs
Additional context
No response
The text was updated successfully, but these errors were encountered: