Closed GoogleCodeExporter closed 8 years ago
The inhibiting works here (Fedora 15).. the screen saver is controlled using
the session manager. If you self build gnome-mplayer can you post your
configure output?
Original comment by kdeko...@gmail.com
on 30 Aug 2011 at 4:03
Do you want I self build gnome-mplayer and post the configure output, or you
ask me if I use a self build gnome-mplayer?
I use the default package on Ubuntu repositories.
Also, if I test with mplayer on a terminal:
$ mplayer my-video
the screensaver is inhibited, but if I test with gnome-mplayer:
$ gnome-mplayer my-video
the screensaver isn't inhibited.
Regards.
Original comment by cont...@jpfleury.net
on 30 Aug 2011 at 4:18
You might try enabling this option if available
Edit->Preferences->Interface
Use X Screen Saver control over Gnome Power Manager
Original comment by kdeko...@gmail.com
on 30 Aug 2011 at 4:24
I already tried, but it doesn't help.
Original comment by cont...@jpfleury.net
on 30 Aug 2011 at 4:34
Is the version of gnome-mplayer you have built on the os you are using it on?
There is some logic in the build that detects if it should use
gnome-session-manager or gnome-power-manager and it is possible that your build
is using the wrong method.
I find it odd that mplayer works, as when the X Screen Saver control is used
gnome-mplayer is using the same technique as mplayer to suspend the screen. Did
you restart gnome-mplayer after selecting this option?
Original comment by kdeko...@gmail.com
on 30 Aug 2011 at 4:39
I didn't build anything. I use the packages provided by Ubuntu:
http://packages.ubuntu.com/oneiric/mplayer
http://packages.ubuntu.com/oneiric/gnome-mplayer
Yes, I restarted gnome-mplayer after selecting "Use X Screen Saver control over
Gnome Power Manager", and I tried more than one time. mplayer always inhibits
screensaver, but gnome-mplayer never inhibits it.
Original comment by cont...@jpfleury.net
on 30 Aug 2011 at 4:52
I'll contact the package maintainer.
Original comment by kdeko...@gmail.com
on 30 Aug 2011 at 4:58
I looked at the package build logs and they are building gnome-mplayer wrong.
So hopefully they will fix these issues and it will fix your issue.
Original comment by kdeko...@gmail.com
on 1 Sep 2011 at 2:45
Must I fill a report on Launchpad about that?
Original comment by cont...@jpfleury.net
on 1 Sep 2011 at 3:00
No, I am working directly with the package maintainer
Original comment by kdeko...@gmail.com
on 1 Sep 2011 at 3:03
I have the same problem on gentoo. I have gnome-mplayer-1.0.5 on top of the
mplayer-20120105 (probably the trunk version at that date). I also use gnome3.
How can I check if my configure is correct? Configure log is in attach.
I also noticed that mplayer is launched with "-nostop-xscreensaver" by
gnome-mplayer. Can it be the cause? The full command line is as such:
mplayer -vo gl_nosw -vf-add screenshot -vc
ffmpeg2crystalhd,ffdivxcrystalhd,ffwmv3crystalhd,ffvc1crystalhd,ffh264crystalhd,
ffodivxcrystalhd, -ao pulse -channels 2 -af-add
export=/tmp/mplayer-af_exportpwseuo:512 -quiet -slave -noidle
-noconsolecontrols -nostop-xscreensaver -identify -volume 100 -softvol
-msglevel all=5 -osdlevel 0 -delay 0,000000 -subdelay 0,000000 -subpos 0
-sub-fuzziness 0 -wid 0x2800023 -brightness 0 -contrast 0 -hue 0 -saturation 0
-alang English,eng,en -slang English,eng,en -nomsgcolor -nomsgmodule
-nokeepaspect -ass -embeddedfonts -ass-font-scale 1,00 -ass-color ffffff00
-subcp CP1251 -cache 10784 <file>
Original comment by Radist.M...@gmail.com
on 8 Jan 2012 at 5:55
Attachments:
please post the output of your configure command after that I can give some
recommendations. Normally it is caused by either gnome-power-manager not being
detected or the XScrnSaver not being included in and not being enabled.
We do not want mplayer managing the screensaver, as gnome-mplayer should be
doing it for mplayer.
Original comment by kdeko...@gmail.com
on 8 Jan 2012 at 7:32
The configure log is in attach of my previous message. Is it not accessible or
something?
Original comment by Radist.M...@gmail.com
on 9 Jan 2012 at 2:01
I missed it...
Anyway, it looks like everything is correct there. I don't see why it should
not be inhibited.
Do you see anything when you run gnome-mplayer with the -v option on the
terminal?
Original comment by kdeko...@gmail.com
on 9 Jan 2012 at 2:28
Here's the log
Original comment by Radist.M...@gmail.com
on 9 Jan 2012 at 10:17
Attachments:
Does it work if you disable crystalHD support?
Original comment by kdeko...@gmail.com
on 9 Jan 2012 at 10:35
After some extensive testing with various configs, gnome-mplayer started to
inhibit screensaver when the corresponding checkbox is unchecked (previously,
both checked and unchecked had no effect). Is this a correct behavior?
Original comment by Radist.M...@gmail.com
on 9 Jan 2012 at 11:36
By default gnome-mplayer talks to gnome-session-manager, but if you are not
using gnome-session-manager to manage your screen. You can check the use
XscrnSaver option when running under KDE or other desktops. That option should
be disabled by default, so it should have worked right away under gnome
Original comment by kdeko...@gmail.com
on 10 Jan 2012 at 1:31
Original issue reported on code.google.com by
cont...@jpfleury.net
on 30 Aug 2011 at 3:50Attachments: