pidgin-musictracker should allow status messages when music has stopped

Bug #242137 reported by Ezra Morris
2
Affects Status Importance Assigned to Milestone
pidgin-musictracker
Fix Released
Undecided
Jon TURNEY
pidgin-musictracker (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: pidgin-musictracker

You can't set the status message if musictracker is enabled. Obviously when music is playing, it uses the status message, but when it is stopped ( and there is nothing in the stopped message) it should display the set status message.

Ubuntu 8.04

ezra@ezra-laptop:~$ apt-cache policy pidgin-musictracker
pidgin-musictracker:
  Installed: 0.4.1-1
  Candidate: 0.4.1-1
  Version table:
 *** 0.4.1-1 0
        500 http://gb.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status

Revision history for this message
Hew (hew) wrote :

Musictracker has a new upstream, and is now known as pidgin-musictracker. Changing sourcepackage.

You should be able to edit your status just fine when music is stopped. Please test with 0.4.11-1 in Jaunty (once it builds and you are able), and also check your pidgin-musictracker plugin preferences to make sure the "Stopped/Off" message is blank.

Changed in musictracker:
status: New → Incomplete
Revision history for this message
Ezra Morris (ezramorris) wrote :

So this isn't going to get fixed in Intrepid then?

Revision history for this message
Hew (hew) wrote :

Fixes are first made to the development release, please read https://wiki.ubuntu.com/StableReleaseUpdates . However, I just said that you should already be able to change your status message when stopped, this should be possible with 0.4.1-1. Please check your plugin preferences like I asked, and test with 0.4.11-1 in Jaunty if it's a real problem on Intrepid. Thanks.

Changed in pidgin-musictracker:
importance: Undecided → Low
Revision history for this message
Ezra Morris (ezramorris) wrote :

OK, that's fine. It won't change when the Stopped/Off message is blank in the current version.

Revision history for this message
Hew (hew) wrote :

Is this still a problem with pidgin-musictracker 0.4.12-1 in Jaunty?

Revision history for this message
Ezra Morris (ezramorris) wrote :

Yes. In Jaunty, pidgin-musictracker 0.4.12-1 displays the last song played after (for example) Rhythmbox is closed.

Revision history for this message
Jon TURNEY (jon-turney) wrote :

Ezra, I'm confused

> OK, that's fine. It won't change when the Stopped/Off message is blank in the current version.

Does this mean it does or doesn't revert to the status message set in the pidgin UI? Does 'current' there mean 0.4.1?

> Yes. In Jaunty, pidgin-musictracker 0.4.12-1 displays the last song played after (for example) Rhythmbox is closed.

This a different problem if it's not even going to the 'stopped/off' message when the player is closed. Can you attach an excerpt from the pidgin debug log (pidgin -d or Help/Debug Widow) showing this problem? (You may wish to sanitize the debug log if it contains your IM account names)

Revision history for this message
Hew (hew) wrote :

As Jon mentioned, this is not the same problem you originally reported. This bug report is about not being able to change the status while the musictracker plugin is enabled, but there is no music being played. I cannot reproduce this problem in the latest version. It even reverts back to the active status message when music is stopped, for me.

Your new problem is that the song status does not clear itself if Rhythmbox is closed while playing. I cannot reproduce this problem either. Using both XMPP status and MSN 'Now Listening', I closed Rhythmbox while it was playing and displaying a song. After the usual 5s delay, all my account statuses were cleared.

Please ensure you are correctly running the latest versions of pidgin and pidgin-musictracker on Jaunty. Ask a friend or use a second client and account to verify your status while you are testing. If you still believe a problem exists, you should first clarify what the problem is (it should be related to the bug as originally reported). It would be helpful to know which protocol/s you are having the problem with. It would also be helpful if you could attach the debug log as Jon mentioned. Thanks again.

Revision history for this message
Ezra Morris (ezramorris) wrote :

Sorry I didn't get back sooner.

To clarify: on 2008-11-25 I meant the current upstream release worked correctly; with pidgin changing back to the personal message when music was stopped.

However, using Ubuntu Jaunty, with the package from the repository, the existing song is still displayed after the music is stopped. This was using Rhythmbox, not sure about anything else.

Also, my mistake; it does revert when Rhythmbox is closed completely.

Log coming soon.

Revision history for this message
Ezra Morris (ezramorris) wrote :
Revision history for this message
Ezra Morris (ezramorris) wrote :
Revision history for this message
Jon TURNEY (jon-turney) wrote :

Thanks for the screencast, very helpful in understanding what you are seeing. Thank you for taking the time to make it.

I think there are a few issues interacting here leading to what you are seeing:

1) You are only pausing the player, not stopping it. I think the only way rhythmbox can get into the stopped state is to arrive at the end of your play queue.

2) When the player is paused, musictracker (a) generates a personal status message according to the "paused" format configured, (b) continues to set the "now playing" status with the paused track information

3) Pidgin displays the personal status message under the contact, but when the personal status message is empty, pidgin now displays the "now playing" status (if the contact has one) [this is a relatively recent change, although I'm not sure exactly what version it happened in]

If you experiment with turning off and on musictracker's "Don't change status message if protocol has 'now listening'" setting or set a status message on that contact, and hover the mouse over the contact in the paused state and look at the tooltip, it might make it a bit clearer what is going on

2(b) is probably a bug, I'll have a think about how to fix that :-)

Revision history for this message
Jon TURNEY (jon-turney) wrote :

I've created an upstream bug for the behaviour described by 2(b) at
http://code.google.com/p/pidgin-musictracker/issues/detail?id=92

This is now fixed upstream and it should show up in my PPA tomorrow if you would like to test it.

Changed in pidgin-musictracker:
assignee: nobody → jon-turney
status: New → Fix Committed
Revision history for this message
Hew (hew) wrote :

Fixed upstream as of 0.4.15

Changed in pidgin-musictracker (Ubuntu):
status: Incomplete → Triaged
Changed in pidgin-musictracker:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.