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#22455 - [gnome-screensaver] - screensaver starts when mplayer playback is active

Attached to Project: Arch Linux
Opened by John (graysky) - Sunday, 16 January 2011, 09:30 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 08 March 2011, 22:58 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Ionut Biru (wonder)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Ever since a recent update, mplayer is no longer able to disable gnome-screensaver and gnome-screensaver will start when mplayer is playing as a result. I have successfully used the following heartbeat command to have mplayer send a "poke" to gnome-screensaver via /usr/bin/gnome-screensaver-command:

Note that this is the recommended way to disable gnome-screensaver (from mplayer's FAQ).

$ cat ~/.mplayer/config
heartbeat-cmd="/usr/bin/gnome-screensaver-command -p > /dev/null" # for gnome-screensaver

I looked at my pacman.log to see what got upgraded, but I'm not sure which of these would affect either mplayer or gnome-screensaver (see list attached to bug report).

*Note that I can confirm that this is broken on two different machines.
*Note that I can verify that mplayer is sending the hearbeat command. I intentionally placed a typo in the ~/.mplayer/config and I can see that intentional mistake echoed to stdout while mplayer is playing.

Starting playback...
Movie-Aspect is 1.73:1 - prescaling to correct movie aspect.
VO: [vdpau] 1280x720 => 1280x720 Planar YV12
sh: gnome-screensaver-commanD: command not found
sh: gnome-screensaver-commanD: command not found
sh: gnome-screensaver-commanD: command not found 3% 2% 0.3% 0 0

Additional info:
* package version(s): gnome-screensaver 2.30.2-1
* link to discussion thread: https://bbs.archlinux.org/viewtopic.php?pid=878980
* config and/or log files etc. (ATTACHED)

Steps to reproduce:

1) Install both gnome-screensaver and mplayer and configure gnome-screensaver to turn on in 1 min of idle
2) Test to make sure gnome-screensaver starts
3) Edit ~/.mplayer/config to contain the line I showed above
4) Start mplayer viewing a file and just sit there waiting. After 1 min, gnome-screensaver should kick in ignoring the hearbeat command!
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 08 March 2011, 22:58 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Upstream decided to remove the poke feature from gnome-screensaver.
Comment by Ionut Biru (wonder) - Sunday, 16 January 2011, 10:30 GMT
remove the heartbeat-cmd from the config. it would work without any hacks
Comment by John (graysky) - Sunday, 16 January 2011, 10:37 GMT
@wonder - I commented out the heartbeat line but it had no effect - gnome-screensaver became active after the wait time. Can you confirm that it works on your system?
Comment by Ionut Biru (wonder) - Sunday, 16 January 2011, 10:41 GMT
 FS#20773  is implemented, mplayer supports that extension and it would work. Unless you are not using our packages.

try to pass -stop-xscreensaver to mplayer
Comment by John (graysky) - Sunday, 16 January 2011, 10:49 GMT
@wonder - both are from official repos.

If I manually added that to the shell, it does indeed keep the screensaver from starting.

$ mplayer -stop-xscreensaver /path/to/file

...but why does the ~/.mplayer/config heartbeat-cmd stop working all of a sudden? It has been working for years without problems... also, how can one adapt the "-stop-xscreensaver" to go into the config?
Comment by Ionut Biru (wonder) - Sunday, 16 January 2011, 10:53 GMT
maybe gnome-screensaver has a broken gnome-screensaver-command. i know i had to use the dbus wake call to work before enabling that option at ./configure.

this issue is not a packaging one. if you want to debug more,i'll say to check gnome-screensaver bugtracker.
Comment by John (graysky) - Sunday, 16 January 2011, 10:55 GMT
Hmm... I'll browse to that bugtracker, but looking at the pkgdates for both mplayer and gnome-screensaver, I find it hard to believe that the problem is related to either one of them. The behavior happened after I updated the system (partial pacman log shown above).
Comment by John (graysky) - Sunday, 16 January 2011, 16:37 GMT
Well, even running the poke command from a bash script on a 30 sec timer has no effect. I bugged it in gnome's tracker:

https://bugzilla.gnome.org/show_bug.cgi?id=639680
Comment by John (graysky) - Sunday, 16 January 2011, 17:18 GMT Comment by Ionut Biru (wonder) - Sunday, 16 January 2011, 17:28 GMT
i commented on that bug.

the idea was that you should test that patch and see if is working. If you don't know how, let me know and i'll provide testing packages
Comment by John (graysky) - Sunday, 16 January 2011, 17:43 GMT
@wonder - I think I applied it correctly. See my PKGBUILD here: http://pastebin.com/MWyTrbag
Unfortunately, after I restarted X and tested, it did not fix the problem.

EDIT: I just realized that YOU posted that in the gnome project! Wonder=Ionut Biru

<<head smack>>
Comment by John (graysky) - Sunday, 16 January 2011, 18:26 GMT
@wonder - just for the hell of it, I booted to a live ubuntu 10.10 disc and found that this bug doesn't affect it for some reason... that coupled with the fact that the problem started happening after my system update on the 13th (see log from first post) I have to think that whatever is causing this is related to one of those packages. Thoughts?

EDIT: I downgraded all of the packages and found no change :(
Comment by Jan de Groot (JGC) - Thursday, 20 January 2011, 23:57 GMT
That patch has nothing to do with it, it just makes the query function not launch the daemon trough dbus.
Can you attach your .mplayer/config? This doesn't sound very promising:
sh: gnome-screensaver-commanD: command not found
sh: gnome-screensaver-commanD: command not found
sh: gnome-screensaver-commanD: command not found
Comment by Jan de Groot (JGC) - Friday, 21 January 2011, 00:02 GMT
Ok, found it, from the source:
gs_monitor_simulate_user_activity (GSMonitor *monitor)
{
/* FIXME: reset the xsync timer? */

/* request that the manager unlock -
will pop up a dialog if necessary */
gs_manager_request_unlock (monitor->priv->manager);
}

The feature you want is commented as FIXME.
Comment by John (graysky) - Saturday, 22 January 2011, 16:32 GMT
@JGC - so the problem is in upstream?

Here is my ~/.mplayer/config

subfont-autoscale=1
osdlevel=3
nosub=1
heartbeat-cmd="gnome-screensaver-command -p &" # for gnome-screensaver
Comment by John (graysky) - Sunday, 06 March 2011, 08:12 GMT
Ah, some action: https://bugzilla.gnome.org/show_bug.cgi?id=579430

Looks like the problem lies with gnome-screensaver...
Comment by Ionut Biru (wonder) - Monday, 07 March 2011, 22:30 GMT
it's officially. they dropped the support in the future gnome-screensaver release

Loading...