I have a similar problem, not only with files that contain ampersand in
the path, but with all files. That is, if I add some files, audacious is
able to play them. When I close audacious and reopen, it's unable to
play any of the files in the list (which means that the "continue
playback on startup" doesn't work at all)... Maybe it's yet another
problem caused by gvfs.
...:~$ apt-cache policy audacious
audacious:
Installed: 1.5.0-2
Candidate: 1.5.0-2
Version table:
*** 1.5.0-2 0
500 http://us.archive.ubuntu.com hardy/universe Packages
100 /var/lib/dpkg/status
...:~$ apt-cache policy audacious-plugins
audacious-plugins:
Installed: 1.5.0-1ubuntu1
Candidate: 1.5.0-1ubuntu1
Version table:
*** 1.5.0-1ubuntu1 0
500 http://us.archive.ubuntu.com hardy/universe Packages
...:~$ apt-cache policy audacious-plugins-extra
audacious-plugins-extra:
Installed: 1.5.0-1ubuntu1
Candidate: 1.5.0-1ubuntu1
Version table:
*** 1.5.0-1ubuntu1 0
500 http://us.archive.ubuntu.com hardy/universe Packages
100 /var/lib/dpkg/status
...:~$ apt-cache policy gvfs
gvfs:
Installed: 0.2.3-0ubuntu4
Candidate: 0.2.3-0ubuntu4
Version table:
*** 0.2.3-0ubuntu4 0
500 http://us.archive.ubuntu.com hardy/main Packages
100 /var/lib/dpkg/status
--
audacious cannot read from files with certain characters in the path or
filename and has a high cpu load.
https://bugs.launchpad.net/bugs/198899
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