search

mate-desktop / mate-screensaver

MATE screen saver and locker
https://mate-desktop.org
GNU General Public License v2.0
48 stars 40 forks source link

System freezes after resuming from hibernation #76

Open apnegrao opened 9 years ago

apnegrao commented 9 years ago

After resuming from hibernation my system freezes before the login window shows up and the only way to get the system back to working is to log into a TTY and kill mate-screensaver. Every time this happens, syslog shows the following messages:

Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_drawable_get_colormap: assertion 'GDK_IS_DRAWABLE (drawable)' failed
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_colormap_alloc_colors: assertion 'GDK_IS_COLORMAP (colormap)' failed
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_drawable_get_colormap: assertion 'GDK_IS_DRAWABLE (drawable)' failed
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_window_set_background: assertion 'GDK_IS_WINDOW (window)' failed
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_window_clear: assertion 'GDK_IS_WINDOW (window)' failed
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-WARNING **: /build/gtk+2.0-czQfyJ/gtk+2.0-2.24.25/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
Aug  3 08:29:46 localhost org.mate.ScreenSaver[1460]: (mate-screensaver:16305): Gdk-CRITICAL **: IA__gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

I'm running Mate 1.8.1 on Debian Jessie and this problem started after I upgraded from wheezy.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/25345046-system-freezes-after-resuming-from-hibernation?utm_campaign=plugin&utm_content=tracker%2F1635706&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1635706&utm_medium=issues&utm_source=github).
GiedriusS commented 9 years ago

Is mate-screensaver using all of the cpu when it "freezes" after hibernation?

apnegrao commented 9 years ago

I have more information about this issue: it turns out the freeze doesn't happen only when returning from hibernation, it happens on both hibernation and suspension if I have an external monitor plugged and unplug it while the system is in suspension/hibernation. To be clear, I can reproduce the freeze by doing the following: 1-Plug external VGA monitor (haven't tried with other connections) 2-Suspend/Hibernate 3-Unplug external monitor 4-Resume the system

@GiedriusS, neither mate-screensaver nor any other process is consuming all CPU, every thing is normal in that regard.

tmancill commented 9 years ago

I wanted to confirm that I am experiencing this same issue. I'm using a Dell docking station + DVI, but the general issue sounds like it's the same. For me, the key issue is that if I suspend while not docked and then dock the laptop, I'm not able to login via the external monitor. I have to get to a TTY and kill mate-screensaver. This sequence used to work until some point in the release cycle for Debian jessie.

olympic1337 commented 8 years ago

I'm experiencing the same error running debian stretch with mate 1.10.2. Is there any news about this behaviour or even a fix?

raveit65 commented 8 years ago

My experience is that hibernate is in general broken with systemd ;)

ghost commented 3 years ago

Issue still exist on version 1.24 release

rcusnir commented 1 year ago

Still the same.

When I close lid (mate is configured to suspend), after open lid, desktop is freeze. Sometome it display login window, but not able to type password, sometime login window is even not visible.

Worst thing is that I am on Fedora 36, and here Openlinig tty terminal with Ctrl+Alt+Fn is not working, I have to force poweroff.

raveit65 commented 1 year ago

Which graphic driver?

raveit65 commented 1 year ago

Btw. f36 has reached EOL since several weeks. I am using f38 and suspend-to-ram and suspend-to-disk is working here with amd grahics driver and Ryzen 5000 cpu.

rcusnir commented 1 year ago

Btw. f36 has reached EOL since several weeks. I am using f38 and suspend-to-ram and suspend-to-disk is working here with amd grahics driver and Ryzen 5000 cpu. on mine is hybrid intel+nvidia (I have planned upgrade, need to find time, but I am afraid that it will not change things)

+++ System Info System = HP HP ZBook Fury 15 G7 Mobile Workstation BIOS = S92 Ver. 01.13.00 OS Release = Fedora Linux 36 (MATE-Compiz)

+++ Processor CPU model = Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz

+++ Intel Graphics /sys/class/drm/card0/device/driver = i915

/sys/class/drm/card0/power/rc6_enable = 1 (enabled) /sys/kernel/debug/dri/0/i915_fbc_status = FBC enabled /sys/module/i915/parameters/enable_psr = -1 (use per-chip default)

/sys/class/drm/card0/gt_min_freq_mhz = 350 [MHz] /sys/class/drm/card0/gt_max_freq_mhz = 1150 [MHz] /sys/class/drm/card0/gt_boost_freq_mhz = 1150 [MHz] /sys/class/drm/card0/gt_RPn_freq_mhz = 350 [MHz] (GPU min) /sys/class/drm/card0/gt_RP0_freq_mhz = 1150 [MHz] (GPU max)

+++ Nvidia Graphics /sys/class/drm/card1/device/driver = nvidia

+++ Wireless bluetooth = off (software) nfc = none (no device) wifi = on wwan = none (no device)

Forgot to mention, X11 is running on nvidia. at least, nvidia-smi is reporting that. Also, I have compiz enalbed. I know it is outdated, but it have some nice features which with I got so common, that I can't work without them :(

rcusnir commented 1 year ago

Just upgraded to F38, still again happen.

System is configured to happen this when I close lid.

but looks like it is happen randomly, and bad thing is that, when I need it, it hang. Also, switch to tty console shorcut key is not working.

any advice to detect what can be the real problem?

raveit65 commented 1 year ago

Can you check if it happens with systemctl suspend/hibernate

Edit: i guess hibernate won't work without configure diskspace for it.

lukefromdc commented 1 year ago

I've not had the freezes and do not have hibernation (suspend to disk) set up, but got no problems resuming after suspending with systemctl suspend

rcusnir commented 1 year ago

When I manually send system to suspend, it is not happen. HIbernate(yes, I have it configured) had similar issue on F36, I have to try hibernate.

What I pay attention, is if I close lid, and open it immediately, looks like all is OK.

If I close lid for 1-2 hours, system freeze. Even can't co to TTY.

One more thing after upgrade, not related, volume control applet in F36 was asking to reload, when it loose connection to dbus, now it just moving volume, but nothing happen. and this happen after manual suspend.

May be it is related to dbus in some way?