Totem DBus pause method doesn't work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
totem (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
The Play() method works, as does the PlayPause() method, but the Pause() method does nothing. I'm writing an application that uses the Pause() method for media players, and Rhythmbox and VLC work fine, but Totem requires the workaround that Pause() be replaced by PlayPause().
If you're using qdbusviewer or something like that, you can locate the bug here:
Session Bus
Service: org.mpris.
Object: /org/mpris/
Interface: org.mpris.
Method: Pause
Relevant files:
/usr/lib/
I tried to fix the bug by changing the contents of the Pause(self) method to
@dbus.
def Pause (self):
if not self.totem.
return
because the Play and PlayPause methods work fine, but this wasn't successful.
Related problems:
* Totem's Unity right-click menu is inconsistent with Rhythmbox's.
Totem's menu has play/pause as one entry
Rhythmbox lists play and pause separately, but play does nothing if Rhythmbox is playing and pause does nothing if Rhythmbox is already paused.
* Totem doesn't have DBus enabled by default.
* Totem's DBus integration is nonstandard (Bug #642172)
Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: totem-plugins 3.6.3-0ubuntu6
ProcVersionSign
Uname: Linux 3.8.0-21-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Mon May 20 18:59:31 2013
InstallationDate: Installed on 2012-12-22 (149 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
SourcePackage: totem
UpgradeStatus: Upgraded to raring on 2013-02-03 (106 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.