-
Notifications
You must be signed in to change notification settings - Fork 86
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
Something went wrong with the screensaver #392
Comments
This happens to me. Never heppened before I've updated to Mint 20.2. |
Hi, can you try uploading it here? https://filebin.net/ and share the download link. The pastebin you shared was for a 'cinnamon' crash, not 'cinnamon-screensaver', by the way. Thanks - I know this is tedious. Github does allow .tar.gz files, but it has a 25mb size limit, unfortunately. |
Forgive me for being thick. I don't understand how to only show the cinnamon-screensaver crashes. Are you saying that after one of the screen saver-related crashes, I should see a specific crash report for cinnamon-screensaver in the list? if that's the case, I don't show that ever. If that's not the case how would I pinpoint those events? Here's what I see: |
I'm also experiencing this issue after upgrading from 20.1 to 20.2. Been using mint for 7 years and this is the first time I'm having this issue. |
this error occured on my machine 4 times since Friday (20. August). I have installed all updates that there available (Mint 20.2). [edit] |
I've come to a bit of a realization - the screensaver here is having issues because cinnamon is crashing. I'm going to fix this and get an update out asap, and try to work out the cinnamon issue (which I think we're already tracking). Thank you for your patience here. |
restarts.zip |
I am now going back to my script. Once again screensaver encountered a problem likely due to their memory-limit restart. Once again had to use Ctrl-Alt-F2 to login and issue "cinnamon-unlock-desktop" so that cinnamon would restart when switched back to GUI. I have attached this morning's logs, which are similar to yesterday morning. |
Hi - I've got a fix for this committed, I was just trying to get a release out. If you're willing to test it, you can either:
or
Note: This should fix the screensaver becoming unresponsive/breaking. But, it won't fix cinnamon crashing, if that was the underlying trigger for this. |
Thank you for your timely response. I might give this a try later, but at present I have fallen back to an alternative to the memory-limit feature which I believe the cause of this problem that does not appear to result in an improper cinnamon restart. As I noted in my posts above, I believe the source of the problem is the cinnamon memory-limit causes an improper restart when the screensaver is active. I believe the logs I have posted here indicate this and there is no crash of cinnamon, simply a failure to restart until the "cinnamon-unlock-desktop" command is issued from a terminal session. I have also posted about this in issue #10287 for cinnamon. I include there a copy of the script I am using for restart which does not have this problem. It uses xdotool to activate the hot-key to request a cinnamon restart and appears to work fine. |
I have just encountered something that might increase the probability that I will install your screensaver fix. As your memory-limit function was logging its actions in ~/.cinnamon/restarts.log I decided to edit my alternative script to log its actions as well. This lead to a surprise, this morning. I had expected to see a logged restart overnight, instead I found: Mon 30 Aug 2021 12:48:09 AM EDT restarting cinnamon. Checking in ~/.xsession-errors I found: Cjs-Message: 06:26:31.180: JS LOG: About to start Cinnamon So while my alternative attempted to restart cinnamon while the screen-saver was active, it appears that it was only completely effective after the screeen-saver was deactivated. I have added an additional diagnostic to my alternative script to include the return code from the call to xdotool that is simulating the restart cinnamon hot key signal to your cinnamon-killer process thinking it might shed some light on what is going on. This might yield some further insight into the issue. So my alternative script seems to be only partially success in restarting cinnamon while the screen-saver is active, but it appears to release some portion of the cinnamon memory or there would be many more entries in the restarts.log file. It does avoid the error that is the subject of this issue, but that was not its complete purpose. Your thoughts on this are welcome. |
Your ctrl-alt-escape is being captured (deliberately) by the screensaver itself, which would be why restarts aren't happening until you unlock. I can't explain why you're not getting a restart attempt every SLEEP_TIME seconds. Perhaps some garbage collection is occurring in cinnamon, bringing you below the threshold? Maybe you could have your script print the memory used every timeout, regardless of whether it wants to restart or not. There's a simple way to do a single test:
You'll see that after those 5 seconds, the screensaver unlock dialog appears (this is the xdotool being captured). Once you unlock the screen, sometime within your SLEEP_TIME you'll get the restart. I added that I may have brought this up in the past, but I wrote an applet quite a while ago to help monitor memory use: https://github.com/mtwebster/Cinnamonitor - it's invaluable ( at least to me) when working on these types of issues. Using the same leakMemory command, I can confirm that the restarts are successful using the patched cinnamon-screensaver. |
Aha! I had not thought about the screen-saver itself getting in the way of the hot key. That certainly explains the delayed restart and might imply that I might see the same problem with the unpatched screen-saver that the memory-limit feature does. Given this I will give your patched screen-saver a try with the memory-limit feature, although at present I can only get the memory-limit appropriate for my system via dconf-editor as the current GUI lower limit it to high for me. If the cinnamon-dbus-command leakMemory 2048 is safe under any circumstances I would consider adding it to my script immediately before the xdotool call, but if it could be problematic unless the screen-saver is active I would need to condition it upon testing for screen-saver activity. In either of these cases I suspect that without the patched screen-saver I would see the same problem as the memory-limit feature, which would render it less useful than the built-in feature. Any schedule for when the fixed version will hit the repository? I might check out your cinnamon memory tool, as perhaps if I knew which applets were leaking I could point it out to support in hopes of it being addressed in later versions. |
Yes you can run cinnamon-dbus-command any time (it will run any dbus command that cinnamon supports, including restarting it - just run it without any arguments to see the commands) |
As expected with the patched stage.py installed the screen-saver did not crash when cinnamon restarted. But this was unexpected: 2021.08.31 00:49:07 - Usage: 320 MB - Limit: 320 MB - Freq: 20 sec Makes me wonder if the screen-saver is a source of the memory leakage I am seeing that causes me to need a restart. |
Weird I'll test it out on my end later |
A troubling datum.I tried the patched stage.py file. After a while, I got one of the screensaver hangs; but this time running If the screensaver bug is not a high-priority one, might I suggest that it becomes so? |
I had deactivated the screensaver, but had left the energy-saving-options alone. See the atached file for the Coredump. The notebook where this happens was installed with Mint 20 Cinnamon an then updated to 20.1 and then 20.2. On an other notebook has the "Somthing went wrong..."-Scenario only happend once. This was installed along time ago with Mint Cinnamon 19.1 and has been updated with every version up to 20.2. On a PC this error has never happened. He was installed a long time ago with Mint Cinnamon 18.1 and has been updated with every version up to 20.2. |
This severe problem persists. Also, and as I noted above, the proposed workaround worsens things on my system. I know bugs can be hard to fix and resources are limited but it does feel as though we really should not have to put up with this. EDIT: by 'the workaround' I mean the patched file. The switching tty and issuing |
Having upgraded to a new kernel (a 5.11 one), this time I found that . . the screensaver would not even allow me to put the caret in the password box. The state of the screensaver is deplorable. |
Just had the same issue for the 2nd time in a few days |
I am experiencing the same thing. After power management turns off my monitors, I have the message telling me to switch to TTY1 and type
Edit: Full system specs at https://termbin.com/pmsi - also, this was a clean install of 20.2 - not an upgrade. There's a lot - like a LOT - of
As of the writing of this post, I've disabled the power management so the monitors won't turn off, and I'll see what (if any) difference that makes, and report back accordingly. |
I can now confirm that as long as Power Management doesn't turn off the monitor, the screensaver doesn't crash.
I'm still seeing errors relating to |
One of my Mint PCs is affected by this bug. On that system, I encounter the bug (or rather that of #263) whether or not power management is set to turn off the monitor. |
I am having this issue as well. Oddly enough, this only happens once I suspend the desktop and leave it like that for a few minutes. If I suspend, and resume like a minute after, the screensaver works fine. Another weird thing is that I have no crash report of this... Someone mentioned that this may be due to Cinnamon crashing. Maybe this is connected to the increased frequency of Cinnamon dropping into "Fallback Mode"? I don't recall this issue being as common in 20.1. |
Also happens to me on occasion since updating from 20.1 to 20.2. It's started happening more frequently in the last week or two. It went from happening about 2-3 times a week to happening almost daily. It's not happening every time my computer suspends or screensaver turns on, but it's frequent enough to be an annoyance. |
Since disabling power-saving while the screen saver is active, preventing
Cinnamon from turning off the monitors, I haven't had the issue.
…------------------------------------------------------------
"Yo, yo. I'm real happy for ya, and I'm glad you can read, but first, I
wanna say that Seann has the best email signatures of all time. OF ALL
TIME!"
-- Kanye West, 2009 Email Signature Awards
------------------------------------------------------------
On Wed., Dec. 8, 2021, 15:21 mfreeman72, ***@***.***> wrote:
Also happens to me on occasion since updating from 20.1 to 20.2. It's
started happening more frequently in the last week or two. It went from
happening about 2-3 times a week to happening almost daily. It's not
happening every time my computer suspends or screensaver turns on, but it's
frequent enough to be an annoyance.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#392 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZA7TWN4ADF4I5L2BTLF63UP645TANCNFSM5BMVSD6A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I disabled "power saving" (I think - I can't find that exact wording in any of the settings), and the problem went away for a bit, but has come back. I'm getting this problem almost daily. |
The same problem, it happens after suspend boot or hibernation. I have a feeling this begun after upgrading kernel from 5.4 to 5.10 Mint 20.2 Linux 5.10.0-1052-oem #54-Ubuntu SMP Tue Nov 23 09:06:13 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux System reports are empty, but here is what I'm getting in syslog.
|
Same problem, syslog:
i'm not able to suspend my computer at all |
TL;DR: Long story: I'm using Mint for years now and I'm experiencing this kind of problem since 20.2 at least, I also fully agree to "392781" - same here:: Sometimes, after wake up, the keyboard is completely dead, not even CTRL-ALT-F1 works, So reading the comment from "Boored-Dude" got my attention: Is there anything I can do to help solving this? |
this error had not occoured a long time for me.
` |
This has happened twice to me when I suspended the system and left it for an hour or two. First time, the laptop was running out of battery, but second time, it was charging. Both times I woke it up and it crashed a second later. |
I have experienced the "Something Went Wong with the screensaver" issue twice now since a FRESH-from-the-ground-up install of Mint 20.2. BOTH times it has occurred AFTER an overnight SUSPEND of the system. (Never went into any "screen-saver" mode).... both times just was using the computer, got tired - bedtime - selected SUSPEND, and get the error upon waking the computer after overnight. Checked the " crash report " as mentioned above, and find NO CRASH REPORT. Very similar to what " 392781 " says above. Here is my system info, in case of need: May 31, 2022 - Happened again today - put computer in SUSPEND for just seconds, and up came the Something Went Wong. - No Crash Report available still |
There seems to have been an uptick in occurances. It's happening daily now, sometimes multiple times per day, on my laptop. I sure hope this gets fixed for Mint 21. It's an incredibly irritating and annoying problem. |
It can seem that the best way to get the devs' attention is to post the problem on the beta bug tracker, when that tracker becomes available. |
I am currently dealing with #417 which seems similar to this. |
I haven't seen this problem since upgrading to Linux Mint 21! This makes me a happy boy! :) |
I had the same issue as the OP with the exact same error screen, right after upgrading to Mint 21 last night. I was using Mint 20.2 before, never had that issue. I will update if it happens again. Below is system info:
Current screen saver and power settings are |
Es la primera vez que me sucede que aparece al volver a iniciar la PC luego de quedó en modo suspensión, aparece leyenda "Algo salio mal con el salvantallas". Me dice que para ir a la consola utilice "Control-Alt-F1" pero no pasa nada, probé con otras combinaicones de "Ctrl-Alt.." pero no logro salir de ahi ¿Alguna sugerencia? Mucha gracias |
I've had a similar issue where I can realiably make cinnamon freeze if the screen is locked and the monitors turn off. This happens bothj when powersaving turns the monitors off and when I just turn them off on their power buttons. If the screen is locked, the system freezes. Mouse cursor moves around but nothin else works. Swithing to tty and using the cinnamon-unlock-desktop command clears it up. This seems to only happen when one of my monitors is in portrait mode. If both are in landscape and therefore have identical resolution, the bug goes away. I'm running this on a Ryzen 7 with Radeon graphics. |
Please have a look here: #416 (comment) Thanks |
This is happening to me a lot. Every time cinnamon crashes, or brave or firefox dumps core, or my system just outright freezes up I can go into journalctl and scroll back to a point just moments before and there it is: WARNING: t+46.38729s: Detected that screensaver has left the bus (removed possibly unrelated info from this spot in an edit) I just killed a mint installation that was having tones of crashes after messages about the screensaver leaving the buse but I kept the logs. I could not even log in for more that 2 min before the screensaver would leave the bus and it would crash. Is there any headway with this? |
I have fixed this issue and all my other problems with Linux crashing. It was directly related to the performance levels of my NVIDA GPU. Once I set PowerMizer to Prefer Maximum Performance everything stabilised and I have been running without issue. See full explanation in page 3 of MY POST on Linux Mint Forum. |
I have mint 21.2 installed on more than one machine with different hardware. On two of them I saw the cinnamon ScreenSaver crashing. I simply opend d-feed and then (Session Bus) clicking on org.cinnamon.ScreenSaver. syslog: |
I am experiencing this issue and cannot find a solution. |
Issue
Return to machine after overnight (no powersave suspend) and machine displays the "Something went wrong with the screensaver" message. This started happening after the 20.2 upgrade.
Steps to reproduce
Allow screensaver control overnight. No user input or activity.
Expected behaviour
Lock screen should appear
Other information
The text was updated successfully, but these errors were encountered: