search

linuxmint / cinnamon-screensaver

The Cinnamon screen locker and screensaver program
GNU General Public License v2.0
151 stars 86 forks source link

Something went wrong with the screensaver #392

Open kendoori opened 3 years ago

kendoori commented 3 years ago 
 * Cinnamon-Screensaver version (cinnamon-screensaver --version): cinnamon-screensaver 5.0.6
 * Distribution - (Mint 17.2, Arch, Fedora 25, etc...) Linux Mint 20.2
 * Graphics hardware *and* driver used: Intel Corporation UHD Graphics 620
 * 32 or 64 bit: 64-bit

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.

PXL_20210802_123858264

Steps to reproduce Allow screensaver control overnight. No user input or activity.

Expected behaviour Lock screen should appear

Other information ksnip_20210802-084925

csandrade87 commented 3 years ago

This happens to me. If I try to unlock my machine after some time this screen shows up.

Never heppened before I've updated to Mint 20.2.

mtwebster commented 3 years ago

Does this happen always or occasionally? Is the monitor 'sleeping' when you come back to unlock it (screen completely blank) or is it already displaying that message?

Please run mintreport ("System Reports" in the menu) and click on the 'Crash reports' tab. image If there are any entries for cinnamon-screensaver please select them (it may take a few moments for the view to update) and then click the 'Local files' button and attach the 'crash.tar.gz' file to a response here (you can simply drag the file into the typing box on github).

If there is more than one instance of cinnamon-screensaver in the crash list please attach that file from each of them.

Thanks

kendoori commented 3 years ago

What happens to me is that I leave the machine idle overnight and this happens during that time. I don't suspend. when I come back, there is the "something went wrong" message active on the screen.

Github is not allowing me to attach the crash report Selection_223

Even if I recompress with .zip as suffix it doesn't work.

Here is the pastebin:

https://termbin.com/xi9z

mtwebster commented 3 years ago

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.

kendoori commented 3 years ago

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:

System Reports_001

MarkusAJacobsen commented 3 years ago

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. It usually happens when I boot the pc after having it in hibernate, no matter the timeframe. I've also experienced it on reboot

Boored-Dude commented 3 years ago

this error occured on my machine 4 times since Friday (20. August). I have installed all updates that there available (Mint 20.2). On another machine (all available updates installed) it occured once yesterday. It never happened on ever machine before. Steps to reproduce: do nothing till the screensaver turns on and wait until the screen goes black (Standby). crash.tar.gz inxi.tar.gz Stack Tracking on Pastebin

[edit] in the journal was this message spammed: Aug 22 11:18:56 Mintyi5 org.cinnamon.ScreenSaver[3235]: couldn't grab keyboard after unlooking the cinnamon-session (cinnamon-unlook-desktop) and returning to cinnamon it informed me that cinnamon was in "fallback-mode" und asked if i like to restart cinnamon, wich i did

mtwebster commented 3 years ago

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.

dhdurgee commented 3 years ago

restarts.zip I just encountered this for the first time last evening. I had just enabled the cinnamon memory-limit feature and based on the logs it appears that it attempted a restart overnight that was not completed until after I addressed this issue. I am attaching what I believe are the relative logs. If you need more information please let me know. There was no crash report as cinnamon did not crash, it apparently was improperly restarted.

dhdurgee commented 3 years ago

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.

restarts.zip

mtwebster commented 3 years ago

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.

dhdurgee commented 3 years ago

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.

dhdurgee commented 3 years ago

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. Mon 30 Aug 2021 03:06:17 AM EDT restarting cinnamon. Mon 30 Aug 2021 03:40:19 AM EDT restarting cinnamon. Mon 30 Aug 2021 04:03:01 AM EDT restarting cinnamon. Mon 30 Aug 2021 04:36:02 AM EDT restarting cinnamon. Mon 30 Aug 2021 04:39:03 AM EDT restarting cinnamon. Mon 30 Aug 2021 05:10:05 AM EDT restarting cinnamon. Mon 30 Aug 2021 05:41:27 AM EDT restarting cinnamon. Mon 30 Aug 2021 05:44:47 AM EDT restarting cinnamon. Mon 30 Aug 2021 05:56:48 AM EDT restarting cinnamon. Mon 30 Aug 2021 06:04:28 AM EDT restarting cinnamon. Mon 30 Aug 2021 06:26:30 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.

mtwebster commented 3 years ago

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 leakMemory command specifically for testing the restart mechanism out.

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.

dhdurgee commented 3 years ago

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.

mtwebster commented 3 years ago

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)

dhdurgee commented 3 years ago

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 2021.08.31 04:03:41 - Usage: 320 MB - Limit: 320 MB - Freq: 20 sec 2021.08.31 07:17:53 - 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.

mtwebster commented 3 years ago

Weird I'll test it out on my end later

LinuxOnTheDesktop commented 3 years ago

A troubling datum.I tried the patched stage.py file. After a while, I got one of the screensaver hangs; but this time running cinnamon-unlock-desktop from a tty no longer unlocked the screensaver. I had to do sudo reboot.

If the screensaver bug is not a high-priority one, might I suggest that it becomes so?

Boored-Dude commented 2 years ago

I had deactivated the screensaver, but had left the energy-saving-options alone. After some time the screen was turned off by the energy-saving. And i come back to my notebook to see that cinnamon had crashed and was in fallback-mode.

See the atached file for the Coredump. CoreCump-Cinnamon-crash-afer-powersaving.txt

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.

LinuxOnTheDesktop commented 2 years ago

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 cinnamon-unlock-desktop does work, but it is a pain.

LinuxOnTheDesktop commented 2 years ago

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.

bernardlmolgithub commented 2 years ago

Just had the same issue for the 2nd time in a few days This is just responding to the request to file a report... Greetings

EvilSupahFly commented 2 years ago

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 cinnamon-unlock-desktop to get back to my desktop just like OP shows in the photo above.

 * Distribution - Linux Mint 20.2 Cinnamon on kernel 5.11.0-37-generic
 * Graphics hardware *and* driver used - NVIDIA Corporation TU116 [GeForce GTX 1660], nvidia-graphics-drivers-470 (470.63.01-0ubuntu0.20.04.2) focal - dual monitor setup
 * 32 or 64 bit - (64bit)
 * System: Intel© Core™ i7-3770 CPU @ 3.40GHz × 4 (8 cores found), 32 GB RAM, Disks: 19,577 GB total

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 org.cinnamon.ScreenSaver spam in my syslog as well. I locked my system before going to work on October 12th, and didn't unlock it again until the morning of October 13th, but this screensaver spam appears every three to five minutes throughout the entire time the system is locked. For the sake of brevity, I've cut out the bulk of it because it's all the same thing:

Oct 12 14:59:12 black-beast dbus-daemon[1320]: [session uid=1000 pid=1320] Activating service name='org.cinnamon.ScreenSaver' requested by ':1.248' (uid=1000 pid=15657 comm="/usr/bin/python3 /usr/bin/cinnamon-screensaver-com" label="unconfined")
Oct 12 14:59:12 black-beast dbus-daemon[1320]: [session uid=1000 pid=1320] Successfully activated service 'org.cinnamon.ScreenSaver'
Oct 12 14:59:12 black-beast cinnamon-session[1318]: WARNING: t+23896.09429s: Detected that screensaver has appeared on the bus
[ ... ]
Oct 12 17:14:20 black-beast org.cinnamon.ScreenSaver[15663]: Trying to connect to logind...
Oct 12 17:14:20 black-beast org.cinnamon.ScreenSaver[15663]: Starting screensaver...
Oct 12 17:14:20 black-beast org.cinnamon.ScreenSaver[15663]: Cinnamon Screensaver support not found in current theme - adding some...
Oct 12 17:14:20 black-beast org.cinnamon.ScreenSaver[15663]: Successfully using logind
Oct 12 17:14:20 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 12 17:14:20 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 348 times: [ couldn't grab keyboard]
Oct 12 17:17:27 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 12 17:17:27 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 12 17:20:26 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 12 17:20:26 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 12 17:26:23 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 12 17:26:23 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 12 17:29:21 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 12 17:29:21 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 12 17:35:18 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 12 17:35:18 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 12 17:38:16 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 12 17:38:16 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 12 17:41:14 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 12 17:41:15 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
[ ... ]
Oct 13 07:38:04 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 13 07:38:04 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 13 07:41:03 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 13 07:41:03 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 13 07:44:01 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 13 07:44:01 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 13 07:47:00 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 13 07:47:00 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 13 07:49:58 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 13 07:49:58 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 13 07:52:57 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 13 07:52:57 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 13 07:55:55 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 13 07:55:55 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 13 07:58:54 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 13 07:58:54 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 13 08:01:52 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 13 08:01:52 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 13 08:04:51 black-beast org.cinnamon.ScreenSaver[15663]: couldn't grab keyboard
Oct 13 08:04:51 black-beast org.cinnamon.ScreenSaver[15663]: message repeated 355 times: [ couldn't grab keyboard]
Oct 13 08:06:07 black-beast cinnamon-session[1318]: WARNING: t+85510.84228s: Detected that screensaver has left the bus
Oct 13 08:06:07 black-beast dbus-daemon[1320]: [session uid=1000 pid=1320] Activating service name='org.cinnamon.ScreenSaver' requested by ':1.303' (uid=1000 pid=33642 comm="/usr/bin/python3 /usr/bin/cinnamon-screensaver-com" label="unconfined")
Oct 13 08:06:07 black-beast dbus-daemon[1320]: [session uid=1000 pid=1320] Successfully activated service 'org.cinnamon.ScreenSaver'
Oct 13 08:06:07 black-beast cinnamon-session[1318]: WARNING: t+85511.29287s: Detected that screensaver has appeared on the bus
Oct 13 08:06:40 black-beast cinnamon-screensaver-pam-helper: pam_ecryptfs: seteuid error
Oct 13 08:06:50 black-beast org.cinnamon.ScreenSaver[33648]: Trying to connect to logind...
Oct 13 08:06:50 black-beast org.cinnamon.ScreenSaver[33648]: Starting screensaver...
Oct 13 08:06:50 black-beast org.cinnamon.ScreenSaver[33648]: Cinnamon Screensaver support not found in current theme - adding some...
Oct 13 08:06:50 black-beast org.cinnamon.ScreenSaver[33648]: Successfully using logind
Oct 13 08:06:50 black-beast org.cinnamon.ScreenSaver[33648]: Error writing to child - Error writing to file descriptor: Broken pipe
Oct 13 08:06:50 black-beast cinnamon-session[1318]: WARNING: t+85553.87615s: Detected that screensaver has left the bus

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.

EvilSupahFly commented 2 years ago

I can now confirm that as long as Power Management doesn't turn off the monitor, the screensaver doesn't crash.

Oct 13 09:32:22 black-beast dbus-daemon[1320]: [session uid=1000 pid=1320] Activating service name='org.cinnamon.ScreenSaver' requested by ':1.361' (uid=1000 pid=71058 comm="/usr/bin/python3 /usr/bin/cinnamon-screensaver-com" label="unconfined")
Oct 13 09:32:22 black-beast dbus-daemon[1320]: [session uid=1000 pid=1320] Successfully activated service 'org.cinnamon.ScreenSaver'
Oct 13 09:32:22 black-beast cinnamon-session[1318]: WARNING: t+90686.23862s: Detected that screensaver has appeared on the bus
Oct 13 12:10:38 black-beast cinnamon-screensaver-pam-helper: pam_ecryptfs: seteuid error
Oct 13 12:10:48 black-beast org.cinnamon.ScreenSaver[71064]: Trying to connect to logind...
Oct 13 12:10:48 black-beast org.cinnamon.ScreenSaver[71064]: Starting screensaver...
Oct 13 12:10:48 black-beast org.cinnamon.ScreenSaver[71064]: Cinnamon Screensaver support not found in current theme - adding some...
Oct 13 12:10:48 black-beast org.cinnamon.ScreenSaver[71064]: Successfully using logind
Oct 13 12:10:48 black-beast cinnamon-session[1318]: WARNING: t+100191.62789s: Detected that screensaver has left the bus
Oct 13 12:10:48 black-beast org.cinnamon.ScreenSaver[71064]: Error in sys.excepthook:
Oct 13 12:10:48 black-beast org.cinnamon.ScreenSaver[71064]: Original exception was:
Oct 13 12:14:19 black-beast dbus-daemon[1320]: [session uid=1000 pid=1320] Activating service name='org.cinnamon.ScreenSaver' requested by ':1.378' (uid=1000 pid=75309 comm="/usr/bin/python3 /usr/bin/cinnamon-screensaver-com" label="unconfined")
Oct 13 12:14:19 black-beast dbus-daemon[1320]: [session uid=1000 pid=1320] Successfully activated service 'org.cinnamon.ScreenSaver'
Oct 13 12:14:19 black-beast cinnamon-session[1318]: WARNING: t+100403.37529s: Detected that screensaver has appeared on the bus
Oct 13 12:15:06 black-beast cinnamon-screensaver-pam-helper: pam_ecryptfs: seteuid error
Oct 13 12:15:16 black-beast org.cinnamon.ScreenSaver[75315]: Trying to connect to logind...
Oct 13 12:15:16 black-beast org.cinnamon.ScreenSaver[75315]: Starting screensaver...
Oct 13 12:15:16 black-beast org.cinnamon.ScreenSaver[75315]: Cinnamon Screensaver support not found in current theme - adding some...
Oct 13 12:15:16 black-beast org.cinnamon.ScreenSaver[75315]: Successfully using logind
Oct 13 12:15:16 black-beast cinnamon-session[1318]: WARNING: t+100459.53716s: Detected that screensaver has left the bus
Oct 13 12:15:16 black-beast org.cinnamon.ScreenSaver[75315]: Error in sys.excepthook:
Oct 13 12:15:16 black-beast org.cinnamon.ScreenSaver[75315]: Original exception was:
Oct 13 12:16:33 systemd: Started VTE child process 76140 launched by gnome-terminal-server process 1952.

I'm still seeing errors relating to org.cinnamon.screensaver in syslog, however. Note that syslog also doesn't give any further detail on the exception noted in those last few lines.

LinuxOnTheDesktop commented 2 years ago

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.

392781 commented 2 years ago

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.

mfreeman72 commented 2 years ago

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.

EvilSupahFly commented 2 years ago

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 https://github.com/linuxmint/cinnamon-screensaver/issues/392#issuecomment-989166196, 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.

mfreeman72 commented 2 years ago

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.

alexveden commented 2 years ago

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.

ек 20 22:13:18 ubernote kernel: cinnamon-screen[202925]: segfault at 6174617a ip 00007f355ffed160 sp 00007ffd3644fb38 error 4 in libgobject-2.0.so.0.6400.6[7f355ffbf000+36000]
дек 20 22:13:18 ubernote kernel: Code: fc 03 00 00 77 3c 48 c1 e8 02 48 8d 15 b9 31 02 00 48 8b 04 c2 48 81 fe fc 03 00 00 76 31 48 83 e6 fc 45 31 c0 48 85 c0 74 0e <f6> 40 16 04 74 05 48 8>
дек 20 22:13:18 ubernote systemd[1]: Started Process Core Dump (PID 203241/UID 0).
дек 20 22:13:19 ubernote cinnamon-session[1236]: WARNING: t+144986,57250s: Detected that screensaver has left the bus
дек 20 22:13:19 ubernote systemd-coredump[203242]: Process 202925 (cinnamon-screen) of user 1000 dumped core.

                                                      Stack trace of thread 202925:
                                                      #0  0x00007f355ffed160 g_type_check_instance_is_a (libgobject-2.0.so.0 + 0x3c160)
                                                      #1  0x00007f355ee2a2fa gdk_device_get_source (libgdk-3.so.0 + 0x342fa)
                                                      #2  0x00007f355ee48bec n/a (libgdk-3.so.0 + 0x52bec)
                                                      #3  0x00007f355ee4914e n/a (libgdk-3.so.0 + 0x5314e)
                                                      #4  0x00007f355ee2dd49 n/a (libgdk-3.so.0 + 0x37d49)
                                                      #5  0x00007f355ee2e983 n/a (libgdk-3.so.0 + 0x38983)
                                                      #6  0x00007f355ee2ee24 n/a (libgdk-3.so.0 + 0x38e24)
                                                      #7  0x00007f355ee53fd7 n/a (libgdk-3.so.0 + 0x5dfd7)
                                                      #8  0x00007f355ee26f4d n/a (libgdk-3.so.0 + 0x30f4d)
                                                      #9  0x00007f356006304e g_main_context_dispatch (libglib-2.0.so.0 + 0x5204e)
                                                      #10 0x00007f3560063400 n/a (libglib-2.0.so.0 + 0x52400)
                                                      #11 0x00007f35600634a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3)
                                                      #12 0x00007f355fe07fe5 g_application_run (libgio-2.0.so.0 + 0xe2fe5)
                                                      #13 0x00007f3560d4eff5 n/a (libffi.so.7 + 0x6ff5)
                                                      #14 0x00007f3560d4e40a n/a (libffi.so.7 + 0x640a)
                                                      #15 0x00007f356017e0a5 n/a (_gi.cpython-38-x86_64-linux-gnu.so + 0x290a5)
                                                      #16 0x00007f356017525c n/a (_gi.cpython-38-x86_64-linux-gnu.so + 0x2025c)
                                                      #17 0x00000000005f57ee PyObject_Call (python3.8 + 0x1f57ee)
                                                      #18 0x000000000056cbfb _PyEval_EvalFrameDefault (python3.8 + 0x16cbfb)
                                                      #19 0x00000000005696da _PyEval_EvalCodeWithName (python3.8 + 0x1696da)
                                                      #20 0x00000000005f6403 _PyFunction_Vectorcall (python3.8 + 0x1f6403)
                                                      #21 0x000000000056b5e0 _PyEval_EvalFrameDefault (python3.8 + 0x16b5e0)
                                                      #22 0x00000000005696da _PyEval_EvalCodeWithName (python3.8 + 0x1696da)
                                                      #23 0x000000000068db17 PyEval_EvalCode (python3.8 + 0x28db17)
                                                      #24 0x000000000067eeb1 n/a (python3.8 + 0x27eeb1)
                                                      #25 0x000000000067ef2f n/a (python3.8 + 0x27ef2f)
                                                      #26 0x000000000067efd1 n/a (python3.8 + 0x27efd1)
                                                      #27 0x000000000067f377 PyRun_SimpleFileExFlags (python3.8 + 0x27f377)
                                                      #28 0x00000000006b7902 Py_RunMain (python3.8 + 0x2b7902)
                                                      #29 0x00000000006b7c8d Py_BytesMain (python3.8 + 0x2b7c8d)
                                                      #30 0x00007f3560b730b3 __libc_start_main (libc.so.6 + 0x270b3)
                                                      #31 0x00000000005fb12e _start (python3.8 + 0x1fb12e)

                                                      Stack trace of thread 202928:
                                                      #0  0x00007f3560c61aff __GI___poll (libc.so.6 + 0x115aff)
                                                      #1  0x00007f356006336e n/a (libglib-2.0.so.0 + 0x5236e)
                                                      #2  0x00007f35600634a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3)
                                                      #3  0x00007f355ad1a99d n/a (libdconfsettings.so + 0xa99d)
                                                      #4  0x00007f356008cad1 n/a (libglib-2.0.so.0 + 0x7bad1)
                                                      #5  0x00007f3560b32609 start_thread (libpthread.so.0 + 0x9609)
                                                      #6  0x00007f3560c6e293 __clone (libc.so.6 + 0x122293)

                                                      Stack trace of thread 202927:
                                                      #0  0x00007f3560c61aff __GI___poll (libc.so.6 + 0x115aff)
                                                      #1  0x00007f356006336e n/a (libglib-2.0.so.0 + 0x5236e)
                                                      #2  0x00007f35600636f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3)
                                                      #3  0x00007f355fe43f8a n/a (libgio-2.0.so.0 + 0x11ef8a)
                                                      #4  0x00007f356008cad1 n/a (libglib-2.0.so.0 + 0x7bad1)
                                                      #5  0x00007f3560b32609 start_thread (libpthread.so.0 + 0x9609)
                                                      #6  0x00007f3560c6e293 __clone (libc.so.6 + 0x122293)

                                                      Stack trace of thread 202926:
                                                      #0  0x00007f3560c61aff __GI___poll (libc.so.6 + 0x115aff)
                                                      #1  0x00007f356006336e n/a (libglib-2.0.so.0 + 0x5236e)
                                                      #2  0x00007f35600634a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3)
                                                      #3  0x00007f35600634f1 n/a (libglib-2.0.so.0 + 0x524f1)
                                                      #4  0x00007f356008cad1 n/a (libglib-2.0.so.0 + 0x7bad1)
                                                      #5  0x00007f3560b32609 start_thread (libpthread.so.0 + 0x9609)
                                                      #6  0x00007f3560c6e293 __clone (libc.so.6 + 0x122293)
дек 20 22:13:19 ubernote systemd[1]: systemd-coredump@5-203241-0.service: Succeeded.
okkindel commented 2 years ago

Same problem, syslog:

Jan  3 09:10:05 k171195 cinnamon-screensaver-pam-helper: pam_ecryptfs: seteuid error
Jan  3 09:10:07 k171195 systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan  3 09:10:15 k171195 org.cinnamon.ScreenSaver[15951]: Trying to connect to logind...
Jan  3 09:10:15 k171195 org.cinnamon.ScreenSaver[15951]: Starting screensaver...
Jan  3 09:10:15 k171195 org.cinnamon.ScreenSaver[15951]: Successfully using logind
Jan  3 09:10:15 k171195 cinnamon-session[6296]: WARNING: t+197,44883s: Detected that screensaver has left the bus
Jan  3 09:10:15 k171195 org.cinnamon.ScreenSaver[15951]: Error in sys.excepthook:
Jan  3 09:10:15 k171195 org.cinnamon.ScreenSaver[15951]: Original exception was:
Jan  3 09:10:15 k171195 org.cinnamon.ScreenSaver[15951]: Error in sys.excepthook:
Jan  3 09:10:15 k171195 org.cinnamon.ScreenSaver[15951]: Original exception was:
Jan  3 09:10:15 k171195 org.cinnamon.ScreenSaver[15951]: Error in sys.excepthook:
Jan  3 09:10:15 k171195 org.cinnamon.ScreenSaver[15951]: Original exception was:

i'm not able to suspend my computer at all

kafido commented 2 years ago

TL;DR: "couldn't grab keyboard" might be the issue ...

Long story: Same problem here, getting a screensaver segfault, pretty much the same as "alexveden" posted. screensaver-segfault.txt

I'm using Mint for years now and I'm experiencing this kind of problem since 20.2 at least, if not 20.1 or even 20, on three completely different Laptops! Now I'm running 20.3 - I was hoping this could have been solved in the meantime - but it still exists.

I also fully agree to "392781" - same here:: "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."

Sometimes, after wake up, the keyboard is completely dead, not even CTRL-ALT-F1 works, however, mouse does work and ssh-ing in from another machine through network works also ...

So reading the comment from "Boored-Dude" got my attention:
"Aug 22 11:18:56 Mintyi5 org.cinnamon.ScreenSaver[3235]: couldn't grab keyboard" However, I haven't had this line in my syslog so far.

Is there anything I can do to help solving this? Any additional debug log I can turn on?

Boored-Dude commented 2 years ago

this error had not occoured a long time for me. But today, after waking up my Notebook from Standby, it showed its ugly face... These are the journal-entrys: `Jan 14 17:45:40 mint-a6 kernel: cinnamon-screen[63199]: segfault at 76677276 ip 00007fbf0b960160 sp 00007ffcd92e5818 error 4 in libgobject-2.0.so.0.6400.6[7fbf0b932000+36000] Jan 14 17:45:40 mint-a6 kernel: Code: fc 03 00 00 77 3c 48 c1 e8 02 48 8d 15 b9 31 02 00 48 8b 04 c2 48 81 fe fc 03 00 00 76 31 48 83 e6 fc 45 31 c0 48 85 c0 74 0e 40 16 04 74 05 48 85 f6 75 35 45 31 c0 44 89 c0 c3 66 0f 1f 44 Jan 14 17:45:40 mint-a6 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Jan 14 17:45:40 mint-a6 systemd[1]: Started Process Core Dump (PID 64103/UID 0). Jan 14 17:45:43 mint-a6 cinnamon-session[1423]: WARNING: t+19242,31368s: Detected that screensaver has left the bus Jan 14 17:45:45 mint-a6 systemd-coredump[64105]: Process 63199 (cinnamon-screen) of user 1001 dumped core.

                                             Stack trace of thread 63199:
                                             #0  0x00007fbf0b960160 g_type_check_instance_is_a (libgobject-2.0.so.0 + 0x3c160)
                                             #1  0x00007fbf0a7b82fa gdk_device_get_source (libgdk-3.so.0 + 0x342fa)
                                             #2  0x00007fbf0a7bcab8 n/a (libgdk-3.so.0 + 0x38ab8)
                                             #3  0x00007fbf0a7bcd17 n/a (libgdk-3.so.0 + 0x38d17)
                                             #4  0x00007fbf0a7e1fd7 n/a (libgdk-3.so.0 + 0x5dfd7)
                                             #5  0x00007fbf0a7b4f4d n/a (libgdk-3.so.0 + 0x30f4d)
                                             #6  0x00007fbf0b9d604e g_main_context_dispatch (libglib-2.0.so.0 + 0x5204e)
                                             #7  0x00007fbf0b9d6400 n/a (libglib-2.0.so.0 + 0x52400)
                                             #8  0x00007fbf0b9d64a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3)
                                             #9  0x00007fbf0b77afe5 g_application_run (libgio-2.0.so.0 + 0xe2fe5)
                                             #10 0x00007fbf0c726ff5 n/a (libffi.so.7 + 0x6ff5)
                                             #11 0x00007fbf0c72640a n/a (libffi.so.7 + 0x640a)
                                             #12 0x00007fbf0baf70a5 n/a (_gi.cpython-38-x86_64-linux-gnu.so + 0x290a5)
                                             #13 0x00007fbf0baee25c n/a (_gi.cpython-38-x86_64-linux-gnu.so + 0x2025c)
                                             #14 0x00000000005f57ee PyObject_Call (python3.8 + 0x1f57ee)
                                             #15 0x000000000056cbfb _PyEval_EvalFrameDefault (python3.8 + 0x16cbfb)
                                             #16 0x00000000005696da _PyEval_EvalCodeWithName (python3.8 + 0x1696da)
                                             #17 0x00000000005f6403 _PyFunction_Vectorcall (python3.8 + 0x1f6403)
                                             #18 0x000000000056b5e0 _PyEval_EvalFrameDefault (python3.8 + 0x16b5e0)
                                             #19 0x00000000005696da _PyEval_EvalCodeWithName (python3.8 + 0x1696da)
                                             #20 0x000000000068db17 PyEval_EvalCode (python3.8 + 0x28db17)
                                             #21 0x000000000067eeb1 n/a (python3.8 + 0x27eeb1)
                                             #22 0x000000000067ef2f n/a (python3.8 + 0x27ef2f)
                                             #23 0x000000000067efd1 n/a (python3.8 + 0x27efd1)
                                             #24 0x000000000067f377 PyRun_SimpleFileExFlags (python3.8 + 0x27f377)
                                             #25 0x00000000006b7902 Py_RunMain (python3.8 + 0x2b7902)
                                             #26 0x00000000006b7c8d Py_BytesMain (python3.8 + 0x2b7c8d)
                                             #27 0x00007fbf0c5450b3 __libc_start_main (libc.so.6 + 0x270b3)
                                             #28 0x00000000005fb12e _start (python3.8 + 0x1fb12e)

                                             Stack trace of thread 63200:
                                             #0  0x00007fbf0c633aff __GI___poll (libc.so.6 + 0x115aff)
                                             #1  0x00007fbf0b9d636e n/a (libglib-2.0.so.0 + 0x5236e)
                                             #2  0x00007fbf0b9d64a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3)
                                             #3  0x00007fbf0b9d64f1 n/a (libglib-2.0.so.0 + 0x524f1)
                                             #4  0x00007fbf0b9ffad1 n/a (libglib-2.0.so.0 + 0x7bad1)
                                             #5  0x00007fbf0c504609 start_thread (libpthread.so.0 + 0x9609)
                                             #6  0x00007fbf0c640293 __clone (libc.so.6 + 0x122293)

                                             Stack trace of thread 63202:
                                             #0  0x00007fbf0c633aff __GI___poll (libc.so.6 + 0x115aff)
                                             #1  0x00007fbf0b9d636e n/a (libglib-2.0.so.0 + 0x5236e)
                                             #2  0x00007fbf0b9d64a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3)
                                             #3  0x00007fbf0660199d n/a (libdconfsettings.so + 0xa99d)
                                             #4  0x00007fbf0b9ffad1 n/a (libglib-2.0.so.0 + 0x7bad1)
                                             #5  0x00007fbf0c504609 start_thread (libpthread.so.0 + 0x9609)
                                             #6  0x00007fbf0c640293 __clone (libc.so.6 + 0x122293)

                                             Stack trace of thread 63201:
                                             #0  0x00007fbf0c633aff __GI___poll (libc.so.6 + 0x115aff)
                                             #1  0x00007fbf0b9d636e n/a (libglib-2.0.so.0 + 0x5236e)
                                             #2  0x00007fbf0b9d66f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3)
                                             #3  0x00007fbf0b7b6f8a n/a (libgio-2.0.so.0 + 0x11ef8a)
                                             #4  0x00007fbf0b9ffad1 n/a (libglib-2.0.so.0 + 0x7bad1)
                                             #5  0x00007fbf0c504609 start_thread (libpthread.so.0 + 0x9609)
                                             #6  0x00007fbf0c640293 __clone (libc.so.6 + 0x122293)

                                             Stack trace of thread 64088:
                                             #0  0x00007fbf0c63989d syscall (libc.so.6 + 0x11b89d)
                                             #1  0x00007fbf0ba23746 g_cond_wait_until (libglib-2.0.so.0 + 0x9f746)
                                             #2  0x00007fbf0b9a6581 n/a (libglib-2.0.so.0 + 0x22581)
                                             #3  0x00007fbf0ba004ca n/a (libglib-2.0.so.0 + 0x7c4ca)
                                             #4  0x00007fbf0b9ffad1 n/a (libglib-2.0.so.0 + 0x7bad1)
                                             #5  0x00007fbf0c504609 start_thread (libpthread.so.0 + 0x9609)
                                             #6  0x00007fbf0c640293 __clone (libc.so.6 + 0x122293)

`

ElyaCherry commented 2 years ago

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. Both on Mint 20.2 I attached the logs from the first session logs_screensaver_crash.txt

codexp commented 2 years ago

This has happened to me too, with a fresh Linux Mint installation.

No crash reports.

And monitor does not switch off, even though it is set up: image

Notebook's and external monitor stay all night on.

Dude7017 commented 2 years ago

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: System Info Dump.zip

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

mfreeman72 commented 2 years ago

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.

LinuxOnTheDesktop commented 2 years ago

@mfreeman72

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.

KyleFromKitware commented 2 years ago

I am currently dealing with #417 which seems similar to this.

mfreeman72 commented 2 years ago

I haven't seen this problem since upgrading to Linux Mint 21! This makes me a happy boy! :)

tsoud commented 2 years ago

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:

System:
  Kernel: 5.15.0-47-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: Cinnamon 5.4.12
    tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X570-P v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 2812 date: 11/04/2020
CPU:
  Info: 16-core model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3 rev: 0 cache:
    L1: 1024 KiB L2: 8 MiB L3: 64 MiB
  Speed (MHz): avg: 2335 high: 3593 min/max: 2200/5083 boost: enabled cores: 1: 2047 2: 3589
    3: 2053 4: 2192 5: 2195 6: 2194 7: 2193 8: 2195 9: 2049 10: 2054 11: 2050 12: 3593 13: 2078
    14: 2052 15: 3586 16: 2050 17: 2049 18: 3589 19: 2047 20: 2051 21: 2049 22: 2049 23: 2050
    24: 2123 25: 2676 26: 2048 27: 2051 28: 2047 29: 3593 30: 2053 31: 2049 32: 2050
    bogomips: 217203
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GA102 [GeForce RTX 3080] vendor: Gigabyte driver: nvidia v: 470.141.03 pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 08:00.0 chip-ID: 10de:2206
  Device-2: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 3-3:2
    chip-ID: 046d:0825
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 7936x2304 s-dpi: 156
  Monitor-1: DP-4 pos: right res: 4096x2304 dpi: 174 diag: 685mm (27")
  Monitor-2: HDMI-1 pos: primary,left res: 3840x2160 dpi: 163 diag: 685mm (27")
  OpenGL: renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2 v: 4.6.0 NVIDIA 470.141.03
    direct render: Yes

Current screen saver and power settings are turn off inactive screen: 2 hrs, suspend: never, delay before starting screensaver: 30 min, lock when put to sleep: Yes, lock after screensaver starts: Yes.

bolson22 commented 2 years ago

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

tkrag commented 1 year ago

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.

mtwebster commented 1 year ago

Please have a look here: https://github.com/linuxmint/cinnamon-screensaver/issues/416#issuecomment-1256233029

Thanks

ikunat33 commented 10 months ago

This is happening to me a lot. I also have a Ryzen 7 with Radeon graphics. ROG Strix g513 (2022)

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?

ikunat33 commented 10 months ago

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.

tuxut commented 10 months ago

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. The text below the node says: activatable: yes, pid: 13670, cmd: cinnamon-screensaver Then I have only to simply wait for 30 seconds. The right field (Object path) closes and the the text "pid 13670, cmd: cinnamon-screensaver" disappears. When I click on or.cinnamon.ScreenSaver again, the pid has changed.

syslog: Nov 14 22:01:11 dalex dbus-daemon[1372]: [session uid=1000 pid=1372] Successfully activated service 'org.cinnamon.ScreenSaver' Nov 14 22:01:11 dalex org.cinnamon.ScreenSaver[136754]: Starting screensaver... Nov 14 22:01:11 dalex org.cinnamon.ScreenSaver[136754]: Cinnamon Screensaver support not found in current theme - adding some... Nov 14 22:01:11 dalex cinnamon-session[1373]: WARNING: t+55221,10493s: Detected that screensaver has appeared on the bus Nov 14 22:01:11 dalex org.cinnamon.ScreenSaver[136754]: Successfully using logind Nov 14 22:01:41 dalex cinnamon-session[1373]: WARNING: t+55251,10807s: Detected that screensaver has left the bus]

SweeTeaRex commented 1 week ago

I am experiencing this issue and cannot find a solution.