Ubuntu
kde-service-menu-fuseiso package

iso mount with kde-service-menu-fuseiso not working

Bug #626251 reported by crazydave
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kde-service-menu-fuseiso (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: kde-service-menu-fuseiso

I use Kubuntu Lynx with kde-service-menu-fuseiso 0.2ubuntu1.

In Dolphin when I right click on a ISO-File and choose "Action" - "Mount ISO images" I get the error that the file "file:///home/username/medie/isofile.iso" is not existing.

When I start Dolphin via Terminal I get the following output when I try to mount an ISO:

dolphin(2548) KDesktopFileActions::executeService: "mountiso" first url's path= "/home/username/isofile.iso" exec= "if [ ! -d "$HOME/media" ]; then mkdir "$HOME/media"; cp "/usr/share/kde4/apps/kde-service-menu-fuseiso/media.directory" "$HOME/media/.directory"; fi; fuseiso -p "%F" "$HOME/media/`basename "%F"`"; kde-open "$HOME/media/`basename "%F"`""
init: wrong standard identifier in volume descriptor 0, skipping..
init: wrong standard identifier in volume descriptor 1, skipping..
init: wrong standard identifier in volume descriptor 2, skipping..
init: wrong standard identifier in volume descriptor 3, skipping..
init: wrong standard identifier in volume descriptor 4, skipping..
init: wrong standard identifier in volume descriptor 5, skipping..
init: wrong standard identifier in volume descriptor 6, skipping..
init: wrong standard identifier in volume descriptor 7, skipping..
init: wrong standard identifier in volume descriptor 8, skipping..
init: wrong standard identifier in volume descriptor 9, skipping..
init: wrong standard identifier in volume descriptor 10, skipping..
init: wrong standard identifier in volume descriptor 11, skipping..
init: wrong standard identifier in volume descriptor 12, skipping..
init: wrong standard identifier in volume descriptor 13, skipping..
init: wrong standard identifier in volume descriptor 14, skipping..
init: wrong standard identifier in volume descriptor 15, skipping..
init: wrong standard identifier in volume descriptor 16, skipping..
init: wrong standard identifier in volume descriptor 17, exiting..
<unknown program name>(2565)/ ClientApp::doIt: Creating ClientApp
kioclient(2565) ClientApp::kde_open: KUrl("file:///home/username/media/isofile.iso")

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kde-service-menu-fuseiso (Ubuntu):
status: New → Confirmed
Revision history for this message
Shoalcreek5 (shoalcreek5) wrote :

First, make sure you are a member of the fuse group.

Next, this:

"if [ ! -d "$HOME/media" ]; then mkdir "$HOME/media"; cp "/usr/share/kde4/apps/kde-service-menu-fuseiso/media.directory" "$HOME/media/.directory"; fi; fuseiso -p "%F" "$HOME/media/`basename "%F"`"; kde-open "$HOME/media/`basename "%F"`""

from the "Exec=" line of /usr/share/kde4/services/ServiceMenus/fuseiso_mount.desktop should be moved into a shell script. For example, I put it in a script at /usr/local/bin/fuseisomount.sh

With my example, the "Exec=" line in fuseiso_mount.desktop would be changed to:

Exec=/usr/local/bin/fuseisomount.sh "%F"

The shell script will need to be changed so that it actually will execute. Here's the contents of mine:

/usr/local/bin/fuseisomount.sh:
#!/bin/bash

if [ ! -d "$HOME/media" ]
 then mkdir "$HOME/media"
 cp "/usr/share/kde4/apps/kde-service-menu-fuseiso/media.directory" "$HOME/media/.directory"
fi

MOUNTNAME="$HOME/media/`basename $1`"

fuseiso -p "$1" "$MOUNTNAME"

kde-open "$MOUNTNAME"
#eof

I'm not sure all of this is necessary in Ubuntu if you are a member of the fuse group, but it did help a lot in Debian Wheezy. Of course, when packaged in a .deb, the shell script should be put in /usr/bin instead of /usr/local/bin. It is awesome that Ubuntu developers are paying attention to things like this. With some modification, I made it work great on Debian. All of the other solutions I could find were much less than satisfactory.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.