Red Hat Bugzilla – Bug 133791
Want a wrapper for cdda uri handler
Last modified: 2013-03-05 22:41:26 EST
It would be nice if g-v-m shipped with a handler that took a cdda://
uri as argument, read the g-v-m audio setting and launched the command
This would allow us to set the default cdda handler to be this
wrapper, and audio cd icons from gnome-vfs would work.
Sounds good to me. I'll look into it.
This should be pretty easy (couple of hours at most), and without it
we currently generate audio cd icons on the desktop that don't work.
How does this look? Should I put it in gvm or will it be packaged
#get the application to use from gnome-volume-manager
#sanitize the device by escaping forward slashes
DEVICE=`echo $1 | /bin/sed -e "s/%/%25/g"`
DEVICE=`echo $DEVICE | /bin/sed -e "s#/#%2f#g"`
#expand the command by replacing %d with the device and unescape it
EXPANDED_CMD=`echo $CMD | /bin/sed -e "s/%d/$DEVICE/"`
EXPANDED_CMD=`echo $EXPANDED_CMD | /bin/sed -e "s#%2f#/#g"`
EXPANDED_CMD=`echo $EXPANDED_CMD | /bin/sed -e "s/%25/%/g"`
#run the command
New gnome-volume-manager built into Rawhide now gives us woking audio
cd launchers. Please test.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Closing per lack of response to previous request for information. This bug was
originally filed against FC3 and has remained in NEEDINFO state for quite some
time. Many packages and bugfixes have been made since the last substantive bug
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.