Linux

47994 readers

1554 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

(partially solved, will update when completed) Please help with an xfce/powerup bug: black screen after suspend/hibernate (programming.dev)

submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]

22 comments fedilink hide all child comments

MX Linux, Xfce 4.18

Closing the laptop lid suspends the system, opening it resumes it, but the screen is black. I'm guessing it's related to powerup because suspending through the logout menu and systemctl suspend both work as expected. When it's black, switching to a different tty works, as well as C-M-Backspace to logout.

Same results with both lightdm and sddm, when replacing suspend with hibernate, and I've tried a few solutions like disabling lock on sleep.

Seems like this issue has been around for years, but had a whole bunch of different causes since every other thread has a different solution.

XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon > /tmp/xf.log 2>&1

ps -ef | grep -E 'screen|lock'

xfconf-query -c xfce4-power-manager -lv

dmesg, cleared it before trying to suspend

updates:

I'm not seeing a black screen, instead it turns on the display and then turns it off.

Additionally, I tried closing and opening the lid a few times, and it woke up correctly.

I tried it in i3wm with the xfce power manager to suspend after closing the lid. It woke up correctly 10 times in a row.

Solution: start an xrandr config and the monitor turns back on.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 6 months ago (1 children)

I wonder if your monitor is showing black or actually off/standby (as in backlight off)?

It actually starts, and then turns off. I didn't notice it before you drew my attention.

The command doesn't do anything, but I was able to type sudo reboot and it rebooted.

It would also be interesting to know if this problem also happens outside of XFCE

I can't install anything new, but I just tried starting power manager in i3 and using it to go to standby when i close the lid. It woke up 10 times in a row without an issue. So it's most likely a purely xfce issue that's been around for like a decade in different forms.

[–] [email protected] 3 points 6 months ago* (last edited 6 months ago) (1 children)

It actually starts, and then turns off. I didn’t notice it before you drew my attention.

That does sound like DPMS ("vesa display power management signaling") shenanigans though.

Maybe you can disable XFCE's display power management stuff completely? Systemd's logind (/etc/systemd/logind.conf) can do (and does by default I think) suspend on lid-close without any window manager involvement at all, works fine with i3 here. So disabling XFCE's stuff probably "only" messes with your monitor not going standby after a while, and you can maybe use xset or xscreensaver and set this by hand (after making sure it's actually properly disabled in XFCE, so XFCE doesn't override that stuff).

Found this about how to stop xfce4-power-manager and disable DPMS:

xfce4-power-manager -q
xset -dpms

Try doing that and see if lid close works afterwards.

[–] [email protected] 3 points 6 months ago* (last edited 6 months ago) (1 children)

I found a different solution: trigger an xrandr config. I'm leaving automating it for tomorrow.

The funniest thing is that I was trying to help out some other lemmy user fix their own xrandr issues, and accidentally came across a thread mentioning it when I went back to fixing my own.

Thanks for the help anyways

[–] [email protected] 2 points 6 months ago (1 children)

OK glad you found some workaround!

[–] [email protected] 2 points 6 months ago

I found it because you pointed out the monitor might be turning off. Changed search terms and found the recommendation in a Reddit thread. The full solution wasn't great though.