Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18097 - [xorg-server] screen blanks while not idle

Attached to Project: Arch Linux
Opened by Hinrich Harms (hinrich) - Sunday, 31 January 2010, 23:12 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 23 March 2010, 15:56 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
After some random interval (sometimes 10 minutes, sometimes a lot more), my monitor goes to standby (DPMS) while mouse and keyboard are in use. A next key press or mouse move wakes it up again -- very annoying though... After that, there's an icon in my gnome panel with a message you can see below. No information can be found in the log files. The two patches specified at the URL should've been incorporated upstream at x.org server for some while already. Anybody an idea? Where can I look for further troubleshooting?

Additional info:
* Gnome panel icon: "Session active, not inhibited, screen idle. If you can see this text, your display server is broken and you should notify your distributor. Please see http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/ for more information."

Packet versions:
* xorg-server 1.7.4.901-1 (happened with 1.7.3, too)
* gnome-desktop 2.28.2-1
* nvidia 190.53-3
* compiz-core 0.8.4-3

Steps to reproduce:
* Actively use the desktop environment for some time (time span varies)
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 23 March 2010, 15:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  Looks like this is fixed. Reopen if it reappears.
Comment by Hinrich Harms (hinrich) - Sunday, 31 January 2010, 23:25 GMT
After digging deeper into the logs I found some (serious sounding) errors. They happened some hours before the actual problem occured:

/var/log/Xorg.0.log:
(II) Jan 31 19:25:35 NVIDIA(0): Setting mode "DFP:1920x1080_50+0+0"
(II) Jan 31 19:25:47 NVIDIA(0): Setting mode "DFP:1920x1080_50+0+0"
(II) Jan 31 19:25:47 NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) Jan 31 19:25:47 NVIDIA(0): may not be running or the "AcpidSocketPath" X
(II) Jan 31 19:25:47 NVIDIA(0): configuration option may not be set correctly. When the
(II) Jan 31 19:25:47 NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
(II) Jan 31 19:25:47 NVIDIA(0): try to use it to receive ACPI event notifications. For
(II) Jan 31 19:25:47 NVIDIA(0): details, please see the "ConnectToAcpid" and
(II) Jan 31 19:25:47 NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) Jan 31 19:25:47 NVIDIA(0): Config Options in the README.
Comment by Hinrich Harms (hinrich) - Sunday, 31 January 2010, 23:50 GMT
xorg.conf is the unchanged one generated by nvidia (see attachement)
   xorg.conf (1.6 KiB)
Comment by Jan de Groot (JGC) - Friday, 05 February 2010, 12:09 GMT
You could try to install acpid to see if it solves your problem. I also have this problem at my workstation at the office, but haven't seen it on other machines yet.
Comment by Hinrich Harms (hinrich) - Sunday, 07 February 2010, 09:06 GMT
Thanks, that did the trick. I wasn't aware that the standard settings make acpid mandatory. Setting ConnectToAcpid to false seems to work as well.
Comment by Hinrich Harms (hinrich) - Monday, 08 February 2010, 22:52 GMT
Disabling ConnectToAcpid did not work, after some time the screen was blanking again. With acpid installed, it seems to work well, though.
Comment by Hinrich Harms (hinrich) - Tuesday, 09 February 2010, 20:19 GMT
Sorry guys, despite my last comments this is not resolved at all. Even with acpid installed and running the problem still occurs. I can't figure out any pattern of when it happens, it just seems random, sometimes only once a day. No errors are in the log files. Xorg log says (after loading the desktop):

(II) Open ACPI successful (/var/run/acpid.socket)

And the acpid log states this while the problem occured:

Feb 9 20:59:04 ArchPC acpid: client 3667[0:0] has disconnected
Feb 9 20:59:04 ArchPC acpid: client 3667[0:0] has disconnected
Feb 9 20:59:04 ArchPC acpid: client connected from 3667[0:0]
Feb 9 20:59:04 ArchPC acpid: 1 client rule loaded
Feb 9 20:59:04 ArchPC acpid: client connected from 3667[0:0]
Feb 9 20:59:04 ArchPC acpid: 1 client rule loaded
Feb 9 20:59:35 ArchPC acpid: client 3667[0:0] has disconnected
Feb 9 20:59:35 ArchPC acpid: client 3667[0:0] has disconnected
Feb 9 20:59:35 ArchPC acpid: client connected from 3667[0:0]
Feb 9 20:59:35 ArchPC acpid: 1 client rule loaded
Feb 9 20:59:35 ArchPC acpid: client connected from 3667[0:0]
Feb 9 20:59:35 ArchPC acpid: 1 client rule loaded

Anybody any ideas?
Comment by italyanker (italyanker) - Saturday, 20 February 2010, 11:32 GMT
Same problem, same packages...
Comment by Hinrich Harms (hinrich) - Saturday, 20 February 2010, 22:00 GMT
Glad I'm not the only one with that problem. I didn't come forth in finding the bug, whether its a packaging related issue (as the error message implies) or a bug in the X server as there're not really any meaningful error messages in the logs... (apart from the ones I posted). Arch Linux seems to be the only distribution having this problem with the updated/fixed version of X server (with the patches from the URL above). At least I haven't found anything with Google...
Comment by Michael Laß (Bevan) - Monday, 22 February 2010, 00:19 GMT
Same problem here on Arch x86_64 with
- xorg-server 1.7.5-1
- nvidia 190.53-4
- compiz-core 0.8.4-3
- acpid 1.0.10-3
Comment by italyanker (italyanker) - Monday, 22 February 2010, 15:08 GMT
Oh, I forgot to say that i have the same packages Michael has except acpid...
Comment by Arjan Nieuwenhuis (arjann) - Wednesday, 24 February 2010, 13:17 GMT
Same problem here on Arch x86_64 with
- xorg-server 1.7.5-1
- nvidia 190.53-4
- acpid 1.0.10-3
Comment by Ray Rashif (schivmeister) - Saturday, 06 March 2010, 19:18 GMT
I used to get rid of this with "xset s off -dpms", but I'm getting these again.
Comment by italyanker (italyanker) - Saturday, 06 March 2010, 23:59 GMT
I'm in error or nvidia-195.X was replaced in favor of nvidia-190.X in community repo???
Comment by italyanker (italyanker) - Sunday, 07 March 2010, 00:03 GMT
Exactly nvidia-190.53-1 instead of nvidia-195.36.08-1 of the past days...We will se if have the same problem of nvidia-190.53-3
Comment by Hinrich Harms (hinrich) - Tuesday, 23 March 2010, 15:49 GMT
At some point I stopped getting these messages, maybe a new xorg-server version (I can't exactly track it back, as it happened only randomly). Is somebody else still having the problem? If not, I'd suggest to mark it "miraculously resolved" ;)
Comment by Jan de Groot (JGC) - Tuesday, 23 March 2010, 15:55 GMT
It actually solved itself here also. Don't know what fixed it, but haven't seen anything special in changelogs.

Loading...