Cosmic Desktop crash when left unattended : error 101 #1012
Comments
|
Looks like the log doesn't include any error messages cosmic-comp produced before crashing. |
|
There is Nothing kept in the logs, In fact the last boot I have in the Log in from September 17. Right now this is the only thing I have, wich is still an issu I guess. |
Ok I have some news; |
LinuxBoy-96
changed the title
|
I can confirm this behaviour. It's been happening as long as I've used Cosmic (since just prior to the first alpha cut).
When you return, wake everything up you be returned to an empty session, every single time. It's so bad that I want to turn off the Power savings options, which currently are:
|
Look like we have a reliable way to recreate this bug. |
LinuxBoy-96
changed the title
|
This was one NixOS users solution:
I'm a NixOS user so I'll give this a run. It may also give a clue as to where the underlying problem is for other users. |
At this point, I did they really don't care about this issue.... |
Yes, we do. It's an alpha DE that is currently in heavy development by a small team. We appreciate your patience. |
|
I'd like to just remind you @LinuxBoy-96 that this is still an alpha release. I use it, expecting to find bugs and when I do, to report them - just as you have done. I've added my comments here as additional support for the Cosmic team to leverage when they get to it. I do not believe that they will release Cosmic without patching these crashes (it's currently only alpha-3). |
Also if you are on the alpha-3 release, please try to confirm this using the latest nightly builds, which depends on the distro you are running on. |
|
I too have been having the issue. In alpha 1 and 2 this would occur if I turned off my monitor. There was no screen saver at the time so I needed to power off my monitor. With alpha 3 you introduced the screen savor. Now whenever the screen savor comes on (monitor goes to sleep), about 95% of the time Cosmic session crashes and session starts fresh. Hopefully this will help. cosmic-comp panics calling unwrap(). If you need more info let me know. Dec 03 12:32:47 The-Reach cosmic-comp[44551]: thread 'main' panicked at 'called |
|
I am experiencing the same issue on my system. I am running Python code for machine learning projects that can take hours or even days to complete. My system is kept fairly minimalistic, with only a few additional Python libraries installed. When running Python scripts in JupyterLab, I encounter an issue where, after approximately 12 hours, my desktop goes blank and all (Python) processes are either killed or restarted. Both the "Automatic suspend" and "Turn off the screen" settings are set to "Never." To help diagnose the problem, here are the syslogs from the crash: |
|
Same issue here. Relevant panic: I'm assuming the code to restore previous session isn't complete? |
Correct. A new session starts clean. Nothing running. Is it possible this issue is due to the fact I am using GDM instead of Cosmic-Greeter? |
I'm using cosmic-greeter so that's definitely not the problem here. From cursory and noobish glance at the function ( (I swear I have no idea what I'm doing; I'm raw at Rust.) |
|
So, I do not experiance this bug in this form anymore. Maybe somebody else does? |
|
Great! We can reopen if the bug returns. |
I would suggest to turn some attention to #1377 , as this is probably a new manifestation of that same bug that happen in the same circurmstances. |
|
Thanks for the suggestion. It is on the radar. |
|
Still not working for me unfortunately :( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Lately, I had to left my PC with Pop!_OS w/ Cosmic Alpha unattended for like 10h.
I turn off the monitor and leave.
When I come back I get a message like this
It does that every time
The text was updated successfully, but these errors were encountered: