GNOME Bugzilla – Bug 364311
telling it to open the playing file doesn't do anything
Last modified: 2007-08-26 18:13:05 UTC
Please describe the problem: If Totem is idle then double-clicking on a media file (or launching another instance of Totem to play another file) does nothing. Steps to reproduce: 1. Launch Totem and play a media file 2. Disable 'Repeat Mode' 3. Let the file finish playing 4. In a terminal, run 'totem some-other-file.mp3' Actual results: Nothing Expected results: Totem should play some-other-file.mp3 Does this happen every time? Yes Other information:
Works fine for me. Any errors on the command-line? Could you get an strace of the original process after the first file has finished playing, and of the other instance of totem launching another file? Do you get a file called /tmp/totem.<username>.<randomnumber> ?
Nothing on the command line and no files in /tmp. Strace output to follow...
Created attachment 75234 [details] strace of parent process
Created attachment 75235 [details] strace of launcher totem process Oh, I do have /tmp/user/1000/totem.sam.3686746664 which appears to be the socket that Totem uses to communicate with the original process
Where did you get your Totem from? That's certainly not the file that libbacon uses, your distribution is probably carrying a (broken) patch for that.
You mean the socket file? It probably lives there because I'm using pam-tmpdir. It creates /tmp/user/1000 (1000 being my uid) and sets the TMP and TMPDIR environment variables to point to that directory. I just did a fresh test with TMP and TMPDIR unset, and have the same problem.
From the parent process: lstat64("/home/sam/Final_Fantasy_10_How_Much_Longer_OC_ReMix.mp3", {st_mode=S_IFREG|0644, st_size=3420160, ...}) = 0 It seems to be working fine, until it tries to do some fu on the recent files. Does Totem hang, do nothing, whatever, when you launch the other command? Does it add it to the recent-files? Does it remove the existing playlist? Does it add it to a new playlist?
Right, what I didn't realise when I filed this bug was that Totem only ignores the request to play a new file when it is the _same_ file. So I guess that Totem checks that the requested file name is the same as the one that is already in the playlist, and if so does nothing. Perhaps it should only do the check if it currently playing (not stopped or paused)?
(In reply to comment #8) > Right, what I didn't realise when I filed this bug was that Totem only ignores > the request to play a new file when it is the _same_ file. Lies in the summary then ;)
Added a note in totem.c's playlist_changed_cb(): //FIXME we shouldn't compare the 2 URLs // http://bugzilla.gnome.org/show_bug.cgi?id=364311 This obviously needs proper testing...
2007-08-26 Bastien Nocera <hadess@hadess.net> * src/totem-playlist.c: (treeview_row_changed), (totem_playlist_get_playing): * src/totem-playlist.h: * src/totem.c: (playlist_changed_cb): Fix activation (adding to the playlist, switching opened files, etc.) when 2 of the items in the playlist have the same MRL, see bug for details (Closes: #364311)