You are not logged in.
Pages: 1
I keep getting hit with this issue ... the screen will not blank on my 2nd computer. I thought I had it working at one point, but it was actually the system power setting which was going into suspend ... which disabled the ethernet which wasn't exactly what I wanted.
So, I'm trying to get the screen saver/blanker running.
First, I have checked and the gnome screen saver is not running.
Second, I have my xfce4 screen saver via the GUI power manager display set for 5/10/20 (blank/sleep/off). And the on/off switch is blue == on.
Following another thread here I've done some dumps and have the following:
1. xfce-power-manager:
*-display
description: VGA compatible controller
product: Stoney [Radeon R2/R3/R4/R5 Graphics]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
2. xfce4-query -c xfce4-power-manager -lv
/xfce4-power-manager/blank-on-ac 2
/xfce4-power-manager/blank-on-battery 3
/xfce4-power-manager/brightness-level-on-ac 69
/xfce4-power-manager/brightness-on-ac 9
/xfce4-power-manager/brightness-on-battery 9
/xfce4-power-manager/brightness-switch 0
/xfce4-power-manager/brightness-switch-restore-on-exit 1
/xfce4-power-manager/critical-power-action 4
/xfce4-power-manager/critical-power-level 5
/xfce4-power-manager/dpms-enabled true
/xfce4-power-manager/dpms-on-ac-off 16
/xfce4-power-manager/dpms-on-ac-sleep 10
/xfce4-power-manager/dpms-on-battery-off 12
/xfce4-power-manager/dpms-on-battery-sleep 11
/xfce4-power-manager/inactivity-on-ac 14
/xfce4-power-manager/inactivity-on-battery 14
/xfce4-power-manager/lock-screen-suspend-hibernate false
/xfce4-power-manager/logind-handle-lid-switch false
/xfce4-power-manager/power-button-action 3
3. Xset -q
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000000
XKB indicators:
00: Caps Lock: off 01: Num Lock: off 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 500 repeat rate: 20
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 2/1 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 120 cycle: 600
Colors:
default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/Type1,built-ins
DPMS (Energy Star):
Standby: 600 Suspend: 0 Off: 960
DPMS is Enabled
Monitor is On
This was working before the recent automatic upgrade from Ubuntu 19.04 to 19.10.
Suggestions more than welcome!!!
Offline
I'd getting quite desperate trying to track down this problem! I've done a few other things here at my end ... all with no success.
1. Entered into the Ubuntu desktop. Same problem, never turns off the screen
2. Watched my xfce session. Seems that when I set the "turn off screen" setting to 1 minute it does work. But, after 13 seconds it turns the screen back on. I think that after about 2 minutes it turns it off again for another brief period.
3. Tried as a different user. No change.
4. Unplugged my wireless mouse and used one with a real tail. No change.
Suggestions???
Offline
Run the power manager in debug mode:
xfce4-power-manager -q && xfce4-power-manager --no-daemon --debug
...then change the Blank After to 1 mintue and wait (you should see an entry in the debug output indicating that the value changed).
After enough time has passed (wait maybe 2 minutes), post back the output from the debug command above.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
Okay, not sure if there is anything informative there. It took a bit of fiddling to set the timer as you can see (went from 2 to 4 to 6 back back), but no messages after that. But, as always, it turned off after a minute and then came back on 15 seconds later. Here's the log:
d:~$ xfce4-power-manager -q && xfce4-power-manager --no-daemon --debug
** (xfce4-power-manager:7089): WARNING **: 13:42:40.406: Failed to get name owner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.freedesktop.PowerManagement': no such name
** (xfce4-power-manager:7089): WARNING **: 13:42:40.407: Failed to get name owner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.xfce.PowerManager': no such name
TRACE[xfpm-main.c:210] xfpm_start(): Starting the power manager
TRACE[xfpm-xfconf.c:651] xfpm_xfconf_init(): lock screen FALSE
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for general-notification
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for show-brightness-popup
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for handle-brightness-keys
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for show-tray-icon
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for hibernate-button-action
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for sleep-button-action
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for battery-button-action
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for lid-action-on-ac
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for lid-action-on-battery
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for brightness-level-on-battery
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for brightness-slider-min-level
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for dpms-sleep-mode
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for inactivity-sleep-mode-on-ac
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for inactivity-sleep-mode-on-battery
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for network-manager-sleep
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for logind-handle-power-key
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for logind-handle-suspend-key
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for logind-handle-hibernate-key
TRACE[xfpm-xfconf.c:164] xfpm_xfconf_load(): Using default configuration for heartbeat-command
(xfce4-power-manager:7089): GLib-GIO-CRITICAL **: 13:42:40.456: g_dbus_proxy_new_for_bus_sync: assertion 'g_variant_is_object_path (object_path)' failed
(xfce4-power-manager:7089): GLib-GObject-WARNING **: 13:42:40.457: ../../../gobject/gsignal.c:2529: signal 'Changed' is invalid for instance '0x5593ee20bde0' of type 'GDBusProxy'
TRACE[xfpm-polkit.c:284] xfpm_polkit_init_data(): Using unix session polkit subject
TRACE[xfpm-polkit.c:342] xfpm_polkit_check_auth_intern(): polkit request: (('unix-process', {'pid': <uint32 7089>, 'start-time': <uint64 835680>}), 'org.freedesktop.login1.power-off', @a{ss} {}, uint32 0, '')
TRACE[xfpm-polkit.c:363] xfpm_polkit_check_auth_intern(): Action=org.freedesktop.login1.power-off is authorized=TRUE
TRACE[xfpm-polkit.c:342] xfpm_polkit_check_auth_intern(): polkit request: (('unix-process', {'pid': <uint32 7089>, 'start-time': <uint64 835680>}), 'org.freedesktop.login1.reboot', @a{ss} {}, uint32 0, '')
TRACE[xfpm-polkit.c:363] xfpm_polkit_check_auth_intern(): Action=org.freedesktop.login1.reboot is authorized=TRUE
TRACE[xfpm-polkit.c:342] xfpm_polkit_check_auth_intern(): polkit request: (('unix-process', {'pid': <uint32 7089>, 'start-time': <uint64 835680>}), 'org.freedesktop.login1.suspend', @a{ss} {}, uint32 0, '')
TRACE[xfpm-polkit.c:363] xfpm_polkit_check_auth_intern(): Action=org.freedesktop.login1.suspend is authorized=TRUE
TRACE[xfpm-polkit.c:342] xfpm_polkit_check_auth_intern(): polkit request: (('unix-process', {'pid': <uint32 7089>, 'start-time': <uint64 835680>}), 'org.freedesktop.login1.hibernate', @a{ss} {}, uint32 0, '')
TRACE[xfpm-polkit.c:363] xfpm_polkit_check_auth_intern(): Action=org.freedesktop.login1.hibernate is authorized=FALSE
TRACE[xfpm-power.c:937] xfpm_power_get_power_devices(): Power device detected at : /org/freedesktop/UPower/devices/ups_hiddev0
TRACE[xfpm-power.c:895] xfpm_power_add_device(): 'ups' device added
TRACE[xfpm-power.c:904] xfpm_power_add_device(): Battery device type 'ups' detected at: /org/freedesktop/UPower/devices/ups_hiddev0
TRACE[xfpm-button.c:182] xfpm_button_xevent_key(): Grabbed key 124 : ((XfpmButtonKey) BUTTON_POWER_OFF)
(xfce4-power-manager:7089): xfce4-power-manager-WARNING **: 13:42:40.487: could not map keysym 1008ffa8 to keycode
TRACE[xfpm-button.c:182] xfpm_button_xevent_key(): Grabbed key 213 : ((XfpmButtonKey) BUTTON_HIBERNATE)
TRACE[xfpm-button.c:182] xfpm_button_xevent_key(): Grabbed key 150 : ((XfpmButtonKey) BUTTON_SLEEP)
TRACE[xfpm-button.c:182] xfpm_button_xevent_key(): Grabbed key 233 : ((XfpmButtonKey) BUTTON_MON_BRIGHTNESS_UP)
TRACE[xfpm-button.c:182] xfpm_button_xevent_key(): Grabbed key 232 : ((XfpmButtonKey) BUTTON_MON_BRIGHTNESS_DOWN)
TRACE[xfpm-button.c:182] xfpm_button_xevent_key(): Grabbed key 244 : ((XfpmButtonKey) BUTTON_BATTERY)
TRACE[xfpm-button.c:182] xfpm_button_xevent_key(): Grabbed key 238 : ((XfpmButtonKey) BUTTON_KBD_BRIGHTNESS_UP)
TRACE[xfpm-button.c:182] xfpm_button_xevent_key(): Grabbed key 237 : ((XfpmButtonKey) BUTTON_KBD_BRIGHTNESS_DOWN)
TRACE[xfpm-power.c:937] xfpm_power_get_power_devices(): Power device detected at : /org/freedesktop/UPower/devices/mouse_hidpp_battery_0
TRACE[xfpm-power.c:895] xfpm_power_add_device(): 'mouse' device added
TRACE[xfpm-power.c:904] xfpm_power_add_device(): Battery device type 'mouse' detected at: /org/freedesktop/UPower/devices/mouse_hidpp_battery_0
TRACE[xfpm-power.c:210] xfpm_power_check_polkit_auth(): using logind suspend backend
TRACE[xfpm-polkit.c:342] xfpm_polkit_check_auth_intern(): polkit request: (('unix-process', {'pid': <uint32 7089>, 'start-time': <uint64 835680>}), 'org.freedesktop.login1.suspend', @a{ss} {}, uint32 0, '')
TRACE[xfpm-polkit.c:363] xfpm_polkit_check_auth_intern(): Action=org.freedesktop.login1.suspend is authorized=TRUE
TRACE[xfpm-polkit.c:342] xfpm_polkit_check_auth_intern(): polkit request: (('unix-process', {'pid': <uint32 7089>, 'start-time': <uint64 835680>}), 'org.freedesktop.login1.hibernate', @a{ss} {}, uint32 0, '')
TRACE[xfpm-polkit.c:363] xfpm_polkit_check_auth_intern(): Action=org.freedesktop.login1.hibernate is authorized=FALSE
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 10
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 10
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 10
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 1
TRACE[xfpm-manager.c:647] xfpm_manager_inhibit_sleep_systemd(): Inhibiting systemd sleep: handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch
(xfce4-power-manager:7089): GLib-CRITICAL **: 13:42:40.517: g_error_free: assertion 'error != NULL' failed
(xfce4-power-manager:7089): xfce4-power-manager-WARNING **: 13:42:40.523: It seems the kernel brightness switch handling value was not restored properly on exit last time, xfce4-power-manager will try to restore it this time.
xfce4-power-manager-Message: 13:42:40.558: Set kernel brightness switch to 0
TRACE[xfpm-backlight.c:254] xfpm_backlight_brightness_on_ac_settings_changed(): Alarm on ac timeout changed 9
TRACE[xfpm-backlight.c:275] xfpm_backlight_brightness_on_battery_settings_changed(): Alarm on battery timeout changed 9
(xfce4-power-manager:7089): xfce4-power-manager-WARNING **: 13:42:40.563: Failed to get keyboard max brightness level : GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.UPower.KbdBacklight” on object at path /org/freedesktop/UPower/KbdBacklight
TRACE[xfpm-polkit.c:241] xfpm_polkit_free_data(): Destroying Polkit data
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 4
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 3
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 2
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 1
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 6
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 5
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 4
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 3
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 2
TRACE[xfpm-power.c:1446] xfpm_update_blank_time(): Timeout: 1
ToZ: Added code tags
Last edited by ToZ (2020-02-24 21:18:14)
Offline
But, as always, it turned off after a minute and then came back on 15 seconds later.
This comment has me confused. It sounds like the screen does turn off as it is supposed to, but then something wakes it up. Is this correct?
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
Yes. Turns off and I think "great". But, 15 seconds later the screen comes back on.
That is why I changed the mouse from wireless to chorded. But, no change.
And, all the hardware is the same anyway from before the latest ubuntu upgrade.
It's a simple box with one SSD and not much more.
Offline
Is your keyboard a wired one or a wireless one?
Can you also post back the results of:
journalctl -b 0 | grep wake
...and:
cat /proc/acpi/wakeup
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
Sure. Here's more data
I had to sudo this one 'cause I'm using ssh to access. I don't think that makes a difference?
sudo journalctl -b 0 | grep wake
[sudo] password for val:
Feb 24 11:23:26 Minorwood kernel: rtc_cmos 00:03: RTC can wake from S4
This is without sudo. Should be fine since it's just a file:
cat /proc/acpi/wakeup
Device S-state Status Sysfs node
GPP2 S4 *disabled
BCM5 S4 *disabled
GPP4 S4 *disabled pci:0000:02:00.0
EHC1 S3 *enabled pci:0000:00:12.0
XHC0 S3 *enabled pci:0000:00:10.0
Offline
Are you ssh'd into the system when this is happening? If so, does the problem exist when you are logged directly into the computer as well?
Is your keyboard wired or wireless?
Can you try:
sudo journalctl | grep wake
...so we can see if there is more.
Edit: also just unplug the mouse and see what happens. If its wireless, remove the dongle as well.
Last edited by ToZ (2020-02-25 00:19:40)
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
Keyboard is wired.
I did remove the wireless mouse and used a wired model. No help.
Problem of not sleeping (blanking screen) is there without ssh. I only did a ssh to grab yesterday's requested info.
$: sudo journalctl | grep wake
Feb 22 14:03:14 Minorwood NetworkManager[791]: <info> [1582405394.0651] manager: sleep: wake requested (sleeping: yes enabled: yes)
<cut about 100 identical lines>
Feb 22 14:53:54 Minorwood NetworkManager[791]: <info> [1582408434.1114] manager: sleep: wake requested (sleeping: yes enabled: yes)
Feb 22 22:39:48 Minorwood kernel: rtc_cmos 00:03: RTC can wake from S4
Feb 23 17:51:42 Minorwood kernel: rtc_cmos 00:03: RTC can wake from S4
Feb 24 11:23:26 Minorwood kernel: rtc_cmos 00:03: RTC can wake from S4
Feb 25 09:38:33 Minorwood kernel: rtc_cmos 00:03: RTC can wake from S4
Helpful?
Offline
As a further test to isolate the potential problem, can you, while sitting in front of the computer, disable the NetworkManager and then see if the wakeup still happens?
Also, can you post back the results of :
xrandr
If we can't fix the problem we might be able to put together a workaround that would suffice.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
Neither disabling or unplugging the network has any effect on this. And, there is no wireless card on the computer.
xrandr:
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 509mm x 286mm
1920x1080 60.00*+ 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 70.00 60.02
1440x900 59.90
1280x800 60.00
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
720x576 50.00
720x480 60.00 59.94
640x480 75.00 72.81 60.00 59.94
720x400 70.08
Any other ideas?
Offline
I'm not sure what is waking up your screen. There is nothing in the logs to identify the cause.
As a workaround option, can you try the script below to see if it helps. First, disable display management in the xfce4-power-manager properties and make sure no screensaver is running. Then, copy the content of this script into a file, and make it executable. And then, assign it to a keyboard shortcut. What this script will do is use xrandr to toggle the screen on and off.
#!/bin/bash
MONITOR="HDMI-A-0"
/usr/bin/xrandr --listactivemonitors | /bin/grep -q "$MONITOR" 1>/dev/null 2>&1
if test "$?" -eq 0; then
xrandr --output "$MONITOR" --off
else
xrandr --output "$MONITOR" --auto
fi
Press the keyboard shortcut, and the screen should turn off. Press it again and it should turn on. See if this works.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
Cautiously, I think I fixed the problem I pulled an unused monitor out of my office and put it on Honey's desk. It's a bit bigger ... which with aging eyes is always good! ... but it sleeps!!!
I have a hard time wrapping my head around this. Especially since it was working before the recent 19.04 -> 19.10 "upgrade". Kernel differences? I have no idea.
I'll leave this open for now and report back after a few days.
Cheers.
Offline
I'm going to say that the problem is fixed. Since exchanging monitors the system has worked flawlessly.
Now, it makes no sense: before the upgrade it worked as well So, I'm going to assume that this is a kernel issue. And, it's most likely not an XFCE issue either since it didn't work under Ubuntu Desktop either.
Thanks all for the help! I see another thread or two on similar issues ... could be that I'm not the only one with a screwy monitor?
Offline
Hi Mellowbob.
If you're interested in more sleuthing, you might want to see if the "fix" in this Mint forum thread which points to this post also works for you.
I'm suspecting this could be the cause from one of your earlier outputs:
XHC0 S3 *enabled pci:0000:00:10.0
I don't know that this will make any difference for you, or even if you want to see if it'll work. Just throwing it out there as it looks quite similar.
Offline
Pages: 1
[ Generated in 0.011 seconds, 7 queries executed - Memory usage: 664.55 KiB (Peak: 697.4 KiB) ]