Packages

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bug Report
  • Category Stable
  • Assigned To
    Emulatorman
    g4jc
  • Operating System All
  • Severity Medium
  • Priority Medium
  • Reported Version Any
  • Due in Version Starfix
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Packages
Opened by fablamar78 - 04/09/2018
Last edited by g4jc - 22/09/2019

FS#1163 - [udisks2] Impossible to mount ISO or IMG file

When I try to mount an ISO file or IMG file (with right-click, “open with disk image mounter” on XFCE4) it fails, the following error message appears :

GDBus.Error.org.freedesktop.UDisks2.Error.Failed: Error opening /dev/loop-control: No such file or directory (udisks-error-quark, 0)

Thanks for your help

Closed by  g4jc
22.09.2019 14:33
Reason for closing:  Invalid
Additional comments about closing:  

Invalid per original report, needs loop module to work.

I realized "loop" module was not loaded.
Very strange as I have the line :

modules="loop"

in

/etc/conf.d/modules

and I ran :

mkinitcpio -p linux-libre-lts

Still, it is not loading at boot...

Anyway, I loaded the module "loop" manually and now I have :

brw-rw---- 1 root disk  7,   0  4 sept. 17:48 /dev/loop0
brw-rw---- 1 root disk  7,   1  4 sept. 17:48 /dev/loop1
brw-rw---- 1 root disk  7,   2  4 sept. 17:48 /dev/loop2
brw-rw---- 1 root disk  7,   3  4 sept. 17:48 /dev/loop3
brw-rw---- 1 root disk  7,   4  4 sept. 17:48 /dev/loop4
brw-rw---- 1 root disk  7,   5  4 sept. 17:48 /dev/loop5
brw-rw---- 1 root disk  7,   6  4 sept. 17:48 /dev/loop6
brw-rw---- 1 root disk  7,   7  4 sept. 17:48 /dev/loop7
crw-rw---- 1 root disk 10, 237  4 sept. 17:48 /dev/loop-control

But when I right click on a ISO or IMG and select "open with disk image mounter", nothing happens.. Not even an error message. The image is not mounted at all even though /dev/loop-control is here

Hello, any update ? It is really annoying not being able to mount iso files.
Thanks

Admin
But when I right click on a ISO or IMG and select "open with disk image mounter", nothing happens.. Not even an error message. The image is not mounted at all even though /dev/loop-control is here

Did you try add dbus user to disk group?

I did.
Thanks for the hint though.. Because I realized that on an other laptop, loop module was correctly loaded (and mount work) so.. I compared the two setup carefully and realized that on my main desktop, dbus service was not active. If I enable it :

rc-update add dbus default

then loop module correctly loads and I'm able to mount isos !

I don't know why it was disabled. I think I read somewhere it wasn't needed hence the reason why. What do you think ?

Mmh, forget what I have just said.
I've thought dbus service was active on the working latop but it wasn't the case. It was disabled just as on my main desktop.
So I ran "rc-status" :

On the laptop, it shows :

Dynamic Runlevel: needed/wanted
 sysfs                                                             [  started  ]
 devfs                                                             [  started  ]
 lvmetad                                                           [  started  ]
 fsck                                                              [  started  ]
 localmount                                                        [  started  ]
 dbus                                                              [  started  ]
 virtlogd                                                          [  started  ]
 termencoding                                                      [  started  ]
Dynamic Runlevel: manual

but on the main desktop :

Dynamic Runlevel: needed/wanted
 sysfs                                                             [  started  ]
 devfs                                                             [  started  ]
 lvmetad                                                           [  started  ]
 fsck                                                              [  started  ]
 localmount                                                        [  started  ]
 rpc.pipefs                                                        [  started  ]
 rpcbind                                                           [  started  ]
 rpc.statd                                                         [  started  ]
 rpc.idmapd                                                        [  started  ]
 virtlogd                                                          [  started  ]
 termencoding                                                      [  started  ]
Dynamic Runlevel: manual

It doesn't.

I don't know if it is dbus related.
I just don't understand why the loop module loads correctly on my laptop but not on my desktop.
On both :

modules="loop"

in

/etc/conf.d/modules

is correctly set.
Any idea where to look ?

Thanks

So, it seems to work I add loop in MODULES in mkinitcpio.conf

MODULES="loop"

Then it is correctly loaded..and mount work.
Very strange because I don't need that on my laptop, modules="loop" in /etc/conf.d/modules is enough.. Should I worry ?

Admin
Very strange because I don't need that on my laptop, modules="loop" in /etc/conf.d/modules is enough.. Should I worry ?

Both (mkinitcpio and /etc/conf.d/modules) are our alternative ways to define our modules to load at boot, so you shouldn't worry about it.

Sometimes modules work better in mkinitcpio instead of /etc/conf.d/modules in some machines because it depends on the configuration made by user in certain machines (never both machines contain the same configurations, at least if you clone a installed system from a machine to another one).

Thanks for the information André. Indeed, the setup are different. This could explain why I need to load the loop module on my desktop.

*in initramfs

Date User Effort (H:M)
watch my effort tracking timers

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing