! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
xfce4-powermanager 4.12 does not wake up monitor after sleep
Status:
RESOLVED: INVALID
Product:
Xfce4-power-manager
Component:
General

Comments

Description John 2015-03-01 21:19:38 CET
Upon updating to 4.12 my monitor does not wake up from sleep.  The only solution is to drop to a tty and manually restart lxdm.  This is consistent (confirmed 3 times in a tow).

My monitor is connected via the display port, not the standard HDMI so I don't know if that plays into it or not.  I don't see anything relevant in dmesg.
Comment 1 Simon Steinbeiss editbugs 2015-04-03 10:22:07 CEST
I presume you're talking about the timed blanking/sleeping of the display in your running session, not the lock screen, right?

The power manager uses X11 directly to do all these power saving things, what you can do to test is uninstall or kill xfce4-power-manager in the running session and control the DPMS timeouts via xset in the terminal. (Run "xset -q" to see the currently set DPMS values, for further reading on how this works look e.g. here: https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling#Modifying_DPMS_and_screensaver_settings_using_xset)
Comment 2 Mukundan Ragavan 2015-04-24 03:28:15 CEST
(In reply to Simon Steinbeiss from comment #1)
> I presume you're talking about the timed blanking/sleeping of the display in
> your running session, not the lock screen, right?
> 


Simon, I am (only) guessing here - I also seeing monitor not waking up after the *system* (laptop, no external display) goes to sleep. I can enter my password and reboot the system - all without seeing the screen and system reboots fine.

Would it be pertinent to test with xset in this case as well?

This is Fedora 22.
Comment 3 Simon Steinbeiss editbugs 2015-04-24 12:04:49 CEST
(In reply to Mukundan Ragavan from comment #2)

That is likely a different issue – or multiple. We've had a lot of complaints about this sort of bug previously, some issues turned out to be hardware/kernel related, others related to the screen locker and I'm not sure whether xfce4-power-manager ever played a part in that. However, if you're sure that it is the culprit, then please submit a new bugreport so that we can track it independently of this issue.
Comment 4 Amayita 2015-06-05 12:43:26 CEST
Hey there, 
I'm seeing this issue on Debian (unstable, xfce4-power-manager 1.4.4) and I stopped seeing it when I switched window managers. I'm not sure this is the right component of xfce, but I'm sure it's a bug somewhere in xfce.
(See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787241)

Thanks for your time!
Comment 5 John 2015-06-05 14:59:50 CEST
For me, the solution is to NOT use the display port and instead use an HDMI cable.  To others reporting the issue, are you connecting via the display port?
Comment 6 Amayita 2015-06-07 10:02:18 CEST
(In reply to John from comment #5)
> For me, the solution is to NOT use the display port and instead use an HDMI
> cable.  To others reporting the issue, are you connecting via the display
> port?

I'm afraid I'm using HDMI
Comment 7 Benjamin 2015-09-19 23:39:52 CEST
I'm having the same problems under Gentoo. When I suspend or hibernate using the power action buttons in the panel, everything works fine. But when I select suspend/hibernate under XFCE Power Manager -> "When laptop lid is closed", and I re-open the lid, my laptop display remains turned off. I have to switch to another tty and restart the login manager or stay on the tty where XFCE was initially running and kill X (this will basically restart my login manager, if one is running). 
The same happens also without a login manger when XFCE is started with startx from the console.
Version xfce4-power-manager 1.5.2
Comment 8 Anton Chevychalov 2015-12-15 15:01:21 CET
(In reply to John from comment #5)
> For me, the solution is to NOT use the display port and instead use an HDMI
> cable.  To others reporting the issue, are you connecting via the display
> port?

Seams to me that this is a clue of that problem. Have the same on one of office emploeeys PC. He is using Ubuntu LTS with XFCE 4.10, but has the same trouble.

But he has dual monitor configuration and only DP1 is blank, but not VGA1.

So because he has one monitor alive he can do more debug whith xrandr:

Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 32767 x 32767
VGA1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm
   1280x1024      60.0*+   75.0  
   1152x864       75.0  
   1024x768       75.1     70.1     60.0  
   832x624        74.6  
   800x600        72.2     75.0     60.3     56.2  
   640x480        75.0     72.8     66.7     60.0  
   720x400        70.1  
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 connected (normal left inverted right x axis y axis)
   1920x1080      60.0 +   50.0     59.9  
   1680x1050      60.0  
   1400x1050      60.0  
   1600x900       60.0  
   1280x1024      75.0     60.0  
   1440x900       59.9  
   1280x960       60.0  
   1280x800       59.8  
   1152x864       75.0  
   1280x720       60.0     50.0     59.9  
   1024x768       75.1     70.1     60.0  
   832x624        74.6  
   800x600        72.2     75.0     60.3     56.2  
   720x576        50.0  
   720x480        60.0     59.9  
   640x480        75.0     72.8     66.7     60.0     59.9  
   720x400        70.1  
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

You can see that DP1 has no mode activated. (It should have "*" simbol in a line "1920x1080      60.0 + ")

You can check if we have same trouble with that small script:

LOG=/tmp/xrandr.log; while ( true ); do date>>$LOG; xrandr >> $LOG; sleep 20;done;

* Connect over DisplayPort
* Open terminal 
* run command above (it would get xrandr info every 20 second) 
* allow it go to blank
* restart session as you did before 
* check /tmp/xrandr.log for lost '*' simbol (at the end of log)

Currently it seems to me like bug in Xorg or xrandr or maybe in driver, but for some reason only XFCE affected, while other user with Unity, same monitors and same PC is fine. So addiotinal information from will be usefull.
Comment 9 Anton Chevychalov 2015-12-15 15:11:15 CET
But perhaps xfce lost control of xrand when DP goes into deep energy saving or something like this?
Comment 10 phil n 2016-01-11 03:12:01 CET
I have the same problem on a Compaq CQ50 laptop. The video card is an NVIDIA GeForce 8200MG using the nouveau driver.

When I shut the lid on my Compaq CQ50 laptop xfce won't 'wake-up'.

When I open the lid the first time the screen will flash what seems to be the session I was in, then it just goes black. Wait for a while, close the lid again, wait for a while, open the lid again, the screen flashes then the session comes up and everything is back to normal. Once I had to push the power button on the second opening to get it going.

This suggestion got it kludged:

Create a keyboard shortcut for the command:

xrandr --auto

On resume from suspend, press the keyboard shortcut.
Comment 11 John 2016-03-04 20:51:04 CET
This has been fixed for me if I am running the kernel 4.3.x series.  However, if I run the 4.4.x series, it is back.  I have opened a new report since this one is technically fixed.  For reference: https://bugzilla.xfce.org/show_bug.cgi?id=12480
Comment 12 David L. Johnson 2016-05-03 03:53:26 CEST
I am having the same problem since I upgraded my debian testing this past week.  Xfce version 4.12, debian testing current as of 4/29/16.  Machine is a gigabyte Brix GB_BXi3-4010 which has one HDMI and one mini-DP connection.  Originally both monitors performed perfectly, but wit the latest update of the OS (debian testing, as mentioned, kernel 4.5.0-1, amd64), every time I wake the machine up from suspend or from the monitors being blanked, only the HDMI-connected monitor works, and I have to go into the xfce setup to re-enable the monitor.  It often takes more than one go to wake the damn thing up.  I tried  xrandr --auto with no effect.  I will try more of the suggestions on this thread to see if anything helps.  

Suggestions are welcome.  To be clear, I use the mini-DP for the second monitor since my machine has only one HDMI port, and the mini-DP port.  I did fiddle with the xscreensaver, and now it locks the screen even though I did not select that. The first monitor wakes up fine, the second does not, and takes several (2-3 attempts to reactivate it with the xfce display app to get it to go again.

I have very quickly become addicted to having two monitors, so need a fix.  I will also try updates of the OS to see if and when that is fixed.
Comment 13 John 2016-05-03 21:02:54 CEST
@David - Did you try the patch?
Comment 14 David L. Johnson 2016-05-04 20:49:01 CEST
(In reply to John from comment #13)
> @David - Did you try the patch?

Do you mean the patch from bug #11107, comment number 53?  No, I haven't tried that yet. However, I re-booted under my old kernel (4.3) and it works as it should.  

By the way, I ran xrandr and got essentially the same response as comment #8.
Comment 15 John 2016-05-04 22:22:26 CEST
Try the patch which has been reported to fix the issue rather than adding more info to the bug report that may not be on topic for this specific bug.
Comment 16 Alexis Huxley 2016-08-17 16:01:06 CEST
For the sake of other googlers, I wanted to add:

* I'm using Ubuntu 16.04

* if I wiggle the mouse (to ensure screen saver not about to kick in), power off the monitor (which is a Samsung TV), immediately power on the monitor again, then the screen is black (except for the TV saying "Check HDMI connection").

* The best workaround I could come up with was to run:

   xfconf-query -c xfce4-keyboard-shortcuts -p '/commands/custom/<Alt>F3' -n -t string -s 'xrandr --auto'

* Thereafter ALT-F3 will wake the monitor, at least this works on mine.
Comment 17 Anton Chevychalov 2016-08-17 16:50:05 CEST
As a final solution of that problem we just take DP to DVI adapter. In that case it detected like HDMI1.

So If you have that problem with XFCE and your monitor connected ov DP then just try to connect it over something else.
Comment 18 Nathan McCorkle 2017-09-06 06:07:26 CEST
(In reply to Alexis Huxley from comment #16)
> For the sake of other googlers, I wanted to add:
> 
> * I'm using Ubuntu 16.04
> 
> * if I wiggle the mouse (to ensure screen saver not about to kick in), power
> off the monitor (which is a Samsung TV), immediately power on the monitor
> again, then the screen is black (except for the TV saying "Check HDMI
> connection").
> 
> * The best workaround I could come up with was to run:
> 
>    xfconf-query -c xfce4-keyboard-shortcuts -p '/commands/custom/<Alt>F3' -n
> -t string -s 'xrandr --auto'
> 
> * Thereafter ALT-F3 will wake the monitor, at least this works on mine.

Thanks Alexis! This test aligns with my issue, and the workaround works!

Hopefully ubuntu 16.04 will get an update to fix this soon
Comment 19 Simon Steinbeiss editbugs 2020-05-26 23:23:31 CEST
Ok, so this sounds like a bug, but not like one that is really in the power manager...

Bug #11627

Reported by:
John
Reported on: 2015-03-01
Last modified on: 2020-05-26

People

Assignee:
Ali Abdallah
CC List:
12 users

Version

Attachments

Additional information