Intrepid, but got the bug at Hardy too.

And what do you mean with the consistency? The bug triggers sometimes
(most of the times a double click just launches rhythmbox, and sometimes
the file actually starts playing), and is consistent with other media
files (files without spaces etc too).

So in fact I'd rather think (after having a second look at the strace
log) that rhythmbox does fail at starting playback for the song, rather
than parsing the command-line arguments.

** Summary changed:

- Rhythmbox not parsing command-line arguments properly
+ Rhythmbox fails at starting playback on doubleclick / argument passing

** Description changed:

  Binary package hint: rhythmbox
  
  Rhythmbox doesn't always react properly when trying to open a file by
- passing it as an argument.
+ passing it as an argument (or by double-clicking a media file, which in
+ fact works the same way).
  
  Example file:
  [EMAIL PROTECTED]:~/Bureaublad$ file "2 Many Dj's & Soulwax @ StuBru 
08-09-2008.mp3" 
  2 Many Dj's & Soulwax @ StuBru 08-09-2008.mp3: MPEG ADTS, layer III, v1,  96 
kbps, 44.1 kHz, JntStereo
  
- Argument passing1:
+ Used command:
  [EMAIL PROTECTED]:~/Bureaublad$ rhythmbox "2 Many Dj's & Soulwax @ StuBru 
08-09-2008.mp3" 
  OR
  [EMAIL PROTECTED]:~/Bureaublad$ rhythmbox 2\ Many\ Dj\'s\ \&\ Soulwax\ @\ 
StuBru\ 08-09-2008.mp3 
  
  Result: most of the times (80% of all cases), the file does NOT start 
playing, it doesn't even get queued up.
  This h is highly annoying as a double-click action on any media files results 
in argument passing as described. So I cannot play files in rhythmbox by 
double-clicking on them!
  
- Rhythmbox debug log added.
+ The log included is a rhythmbox debug log when a file gets passed to
+ rhythmbox, but playback does not start. A close look indicates that
+ rhythmbox does in fact properly parse the given arguments, but fails at
+ starting playback.

-- 
Rhythmbox fails at starting playback on doubleclick / argument passing
https://bugs.launchpad.net/bugs/270523
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to