With all due respect flipefr, the fact that you haven't needed to do
something by no means that others do not.
Personally, I have never been in a car accident of the type that I can
say a seatbelt saved my life. If someone pointed out that a car had no
seatbelts, I wouldn't blow them off as you
Public bug reported:
Binary package hint: rhythmbox
Version 0.12.5-0ubuntu5.2
Karmic Koala 32bit
Essentially, rhythmbox requires the play command twice in order to play
a song which is not in its music library. This breaks any compatibility
with software that would use it as an audio player
I came to post the same bug. It seems that while producing the little
info bubble popup that displays the network speed, the applet is
incapable of also tracking the actual network traffic! I noticed it
first on an AMD64 system, but now I am using 32bit and the behavior is
the same.
--
System
Eventually I was able to get it to work.
After several failed tries, the drive was not visible in nautilus, but
was still visible in usb-creator. This was not the case in previous
attempts. I select sdb1, rather than sdb and it worked.
--
Fails repeatably with DBus error
I believe this has to do with the VBRI headers in many mp3 files today.
I installed mp3diags and had it strip out the VBRI header and replace it
with the Xing headers and now the length is fine. Just thought I'd
share.
--
variable rate mp3 have wrong length
I have discovered that no daap capable music software is working on my
setup, so I think maybe the issue is mine. Can someone answer a couple
questions for me so I can confirm where the issue is and update the bug
report?
Does Rhythmbox automagically discover Dapp shares? In other words, is
the
Public bug reported:
Binary package hint: rhythmbox
Rhythmbox no longer remembers daap shares. I have a Hardy box and a
gutsy server. The guts server has a firefly daap share that shares
music with all of my machines. Every time I open Rhythmbox I have to
manually connect to the Daap share by
