After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 423538 - Power-manager plugin
Power-manager plugin
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: Plugins (other)
HEAD
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-28 00:36 UTC by Bastien Nocera
Modified: 2018-05-24 12:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2007-03-28 00:36:21 UTC 
The current power-manager patch in Rhythmbox forbids going to sleep when Rhythmbox is playing.

Peter Jones (CC:'ed) wrote this (hacky by his own admission) plugin:
http://people.redhat.com/pjones/rhythmbox-pm.tar.bz2
that will pause playback when going to sleep, and restart when waking up.

I prefer the latter option, which should be the default, unless Rhythmbox is in fullscreen (fullscreen visualisation, that is what Totem does), or in "Party" mode.
Comment 1 pjones 2007-03-28 17:25:33 UTC 
Actually my version doesn't restart -- I originally had it doing that, but quickly I found that I was usually didn't want playback to automatically restart on resume.  At least with my usage pattern of listening through headphones at one place, suspending, and then resuming in a different (often public) location, it can actually be somewhat embarrassing on occasion.
Comment 2 Bastien Nocera 2008-01-09 12:41:26 UTC 
I've made the power-manager not be builtin and disabled by default in Fedora, as I've had reports of the behaviour not being appreciated.
Comment 3 GNOME Infrastructure Team 2018-05-24 12:28:32 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/349.