Re: What prevents mounting of USB devices?
On Tue, Apr 13, 2010 at 01:09:03 +0200, Clive McBarton wrote: Florian Kulzer wrote: [...] Another thing to try is to activate the desktop icons for removable devices and test if users can mount the devices by clicking on the icons. Sorry to sound stupid, but how do I activate those? Right now I don't see any icons on the desktop when plugging devices in. As far as I remember, the icons can be activated in the KDE Control Center Desktop Behavior Device Icons dialog; one has to check both the option for unmounted and mounted removable devices. -- Regards,| Florian | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100414212926.ga5...@isar.localhost
Re: What prevents mounting of USB devices?
On Sun, Apr 11, 2010 at 14:57:01 +0200, Clive McBarton wrote: Florian Kulzer wrote: On Sat, Apr 10, 2010 at 19:20:42 +0200, Clive McBarton wrote: I run KDE and normally mount usb devices with the Storage Media applet in the task bar. Recently I have been getting strange errors and mounting failed: Which version of KDE, 3.x or 4.x? (I don't remember a task bar applet for mounting removable media from my KDE 3.x days - I always triggered mounting via the icons that appeared on the desktop for removable media - but I might simply not know about alternatives.) 3.x, Lenny default. Probably 3.5.10 if I see correctly. The task bar applet is called Storage Media or Media Applet. The right-click options in the taskbar are Move Storage Media, Remove Storage Media, Configure Storage Media, About Storage Media. When I bring up its preferences it has different ideas about its name and now says Media Applet Preferences - KDE Panel. The About says using KDE 3.5.10. Did you have any security upgrades lately or did you install packages from backports or volatile, or any non-Debian stuff? I am surprised that a stable system should exhibit such a sudden regression. Another thing to try is to activate the desktop icons for removable devices and test if users can mount the devices by clicking on the icons. Mounting worked for you earlier, so I assume that your users are all members of the plugdev group already. Yes they are. I would like to see the output of: awk '/policy group=plugdev/,/\/policy/' /etc/dbus-1/system.d/hal.conf Here: policy group=plugdev allow send_interface=org.freedesktop.Hal.Device.Volume send_destination=org.freedesktop.Hal/ allow send_interface=org.freedesktop.Hal.Device.Volume.Crypto send_destination=org.freedesktop.Hal/ /policy By looking at the modify time, I see that this file has not been modified since I installed Debian, so it must still be in the default state. AFAIK, that is exactly how it should be for Lenny, so all members of the plugdev group should be able to send dbus messages to hal. Absence of such permissions is a very common reason for point-click mounting to go wrong, but that does not seem to be the case for you. [...] And the UUID of the usb stick is even listed in /etc/fstab so that it is supposed to mount automatically when plugged in (though that does not seem to work). But that may be an unrelated issue. AFAIK, you should not have any entries in fstab for removable devices that you want to be handled by KDE/Gnome/whatever_other_DE via the dbus/hal mechanism. In any case, I would avoid trying to mix different approaches. I would avoid that too, if any single one of them would work, but neither did. I did not try pmount so far, that would actually have worked. I suspect that the fstab entry is not really a problem. Maybe you can setup pmount for the individual users so that it is more convenient. Unfortunately I do not understand what else your dbus error message is trying to tell us. I would run lshal --monitor, then plug in a USB stick and try to mount it; maybe that will turn up something useful. Seeing what hal knows about a USB stick might also help; hal can be queried like this: lshal -u $(hal-find-by-property --key block.device --string /dev/sdX) lshal -u $(hal-find-by-property --key block.device --string /dev/sdX1) (Replace sdX as is appropriate) -- Regards,| Florian | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100412192523.ga8...@isar.localhost
Re: What prevents mounting of USB devices?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florian Kulzer wrote: Did you have any security upgrades lately Sure, I install them regularly. Doesn't everybody? or did you install packages from backports or volatile I do have the following as part of my sources.conf: deb http://volatile.debian.org/debian-volatile lenny/volatile main contrib non-free deb-src http://volatile.debian.org/debian-volatile lenny/volatile main contrib non-free deb http://www.debian-multimedia.org lenny main I am not sure if I actually installed anything from volatile. or any non-Debian stuff? Yes, from debian-multimedia.org. Presumably that counts as non-Debian. Another thing to try is to activate the desktop icons for removable devices and test if users can mount the devices by clicking on the icons. Sorry to sound stupid, but how do I activate those? Right now I don't see any icons on the desktop when plugging devices in. I suspect that the fstab entry is not really a problem. Maybe you can setup pmount for the individual users so that it is more convenient. Yes, the pmount works fine now, it did not even require setting anything up. Unfortunately I do not understand what else your dbus error message is trying to tell us. I would run lshal --monitor, then plug in a USB stick and try to mount it; maybe that will turn up something useful. Seeing what hal knows about a USB stick might also help; hal can be queried like this: lshal -u $(hal-find-by-property --key block.device --string /dev/sdX) lshal -u $(hal-find-by-property --key block.device --string /dev/sdX1) (Replace sdX as is appropriate) Thanks for showing and explaining lshal to me. I'll explore with it and report if I find something interesting. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvDqA4ACgkQ+VSRxYk4408SyACeLV3a1tt3VKgvTwya+oBz71Nu IgQAn0hgk+w/0ykMQB/vtjNRf1oeLyib =3B0A -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bc3a80f.5010...@web.de
Re: What prevents mounting of USB devices?
On Sat, Apr 10, 2010 at 19:20:42 +0200, Clive McBarton wrote: I run KDE and normally mount usb devices with the Storage Media applet in the task bar. Recently I have been getting strange errors and mounting failed: Which version of KDE, 3.x or 4.x? (I don't remember a task bar applet for mounting removable media from my KDE 3.x days - I always triggered mounting via the icons that appeared on the desktop for removable media - but I might simply not know about alternatives.) Rejected send message, 3 matched rules; type=method_call, sender=:1.21 (uid=101 pid=13921 comm=kded [kdeinit] --new-startup ) interface=org.freedesktop.Hal.Device.Volume member=Mount error name=(unset) requested_reply=0 destination=org.freedesktop.Hal (uid=0 pid=11879 comm=/usr/sbin/hald )) Mounting worked for you earlier, so I assume that your users are all members of the plugdev group already. I would like to see the output of: awk '/policy group=plugdev/,/\/policy/' /etc/dbus-1/system.d/hal.conf Mounting as root on the commandline still works, but it's a hassle for the user who wants to simple use their usb stick. It would be interesting to know if regular users can mount USB sticks using pmount or pmount-hal on the command line. And the UUID of the usb stick is even listed in /etc/fstab so that it is supposed to mount automatically when plugged in (though that does not seem to work). But that may be an unrelated issue. AFAIK, you should not have any entries in fstab for removable devices that you want to be handled by KDE/Gnome/whatever_other_DE via the dbus/hal mechanism. In any case, I would avoid trying to mix different approaches. Another (possibly also unrelated) issue is that when several X are running (different users, all with KDE) then it seems that only one of them can mount and unmount, usually the wrong user. I have seen that complaint before, also for systems on which mounting worked perfectly for single-user sessions, and I am not sure if a satisfactory solution exists. (I have no need for running multiple KDE sessions on the same machine, therefore I do not know much about this issue.) Is it worth digging into hal to correct this? Given that hal won't be in Debian much longer. Well, it is a problem for you right now, so why not try to solve it? Besides, udisks has the same main developer as hal, so I doubt that it will be so radically different that hal know-how will become useless. I have played around a bit with udisks yesterday, it seems to follow the same basic concepts as hal. AFAICT, udisks-daemon is simply an upgraded version of hald that is specialized on block devices, as one part of a more modular approach to hardware abstraction. -- Regards,| Florian | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100411081621.ga4...@isar.localhost
Re: What prevents mounting of USB devices?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florian Kulzer wrote: On Sat, Apr 10, 2010 at 19:20:42 +0200, Clive McBarton wrote: I run KDE and normally mount usb devices with the Storage Media applet in the task bar. Recently I have been getting strange errors and mounting failed: Which version of KDE, 3.x or 4.x? (I don't remember a task bar applet for mounting removable media from my KDE 3.x days - I always triggered mounting via the icons that appeared on the desktop for removable media - but I might simply not know about alternatives.) 3.x, Lenny default. Probably 3.5.10 if I see correctly. The task bar applet is called Storage Media or Media Applet. The right-click options in the taskbar are Move Storage Media, Remove Storage Media, Configure Storage Media, About Storage Media. When I bring up its preferences it has different ideas about its name and now says Media Applet Preferences - KDE Panel. The About says using KDE 3.5.10. Mounting worked for you earlier, so I assume that your users are all members of the plugdev group already. Yes they are. I would like to see the output of: awk '/policy group=plugdev/,/\/policy/' /etc/dbus-1/system.d/hal.conf Here: policy group=plugdev allow send_interface=org.freedesktop.Hal.Device.Volume send_destination=org.freedesktop.Hal/ allow send_interface=org.freedesktop.Hal.Device.Volume.Crypto send_destination=org.freedesktop.Hal/ /policy By looking at the modify time, I see that this file has not been modified since I installed Debian, so it must still be in the default state. It would be interesting to know if regular users can mount USB sticks using pmount or pmount-hal on the command line. Good idea. I never used pmount before. I just tried it with one user (insert USB stick, pmount it as the user) and it works. Thanks! Meanwhile, the KDE applet would not have worked, it does not even display an icon indicating that the USB stick has been plugged in at all. And the UUID of the usb stick is even listed in /etc/fstab so that it is supposed to mount automatically when plugged in (though that does not seem to work). But that may be an unrelated issue. AFAIK, you should not have any entries in fstab for removable devices that you want to be handled by KDE/Gnome/whatever_other_DE via the dbus/hal mechanism. In any case, I would avoid trying to mix different approaches. I would avoid that too, if any single one of them would work, but neither did. I did not try pmount so far, that would actually have worked. Another (possibly also unrelated) issue is that when several X are running (different users, all with KDE) then it seems that only one of them can mount and unmount, usually the wrong user. I have seen that complaint before, also for systems on which mounting worked perfectly for single-user sessions, and I am not sure if a satisfactory solution exists. (I have no need for running multiple KDE sessions on the same machine, therefore I do not know much about this issue.) That is why I made the fstab entries, so I can write the correct user in it, in the case when a certain device is known to belong to a particular user. I was hoping that they could mount it then. Is it worth digging into hal to correct this? Given that hal won't be in Debian much longer. Well, it is a problem for you right now, so why not try to solve it? Besides, udisks has the same main developer as hal, so I doubt that it will be so radically different that hal know-how will become useless. I have played around a bit with udisks yesterday, it seems to follow the same basic concepts as hal. AFAICT, udisks-daemon is simply an upgraded version of hald that is specialized on block devices, as one part of a more modular approach to hardware abstraction. Good to know. So far, I was always staying far away from hal for fear of completely wasting my time. But if hal knowledge will still be useful after hal is gone, that makes me reconsider. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvBxx0ACgkQ+VSRxYk44089ogCeOClzg2MfMnr8M0mX15UbT8cs XBcAoMC7SiK54cGFhVz01AkuXNNJvqG7 =QeCR -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bc1c71d.8020...@web.de
