diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20120610/007749.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20120610/007749.html | 216 |
1 files changed, 216 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20120610/007749.html b/zarb-ml/mageia-discuss/20120610/007749.html new file mode 100644 index 000000000..8cd3186ea --- /dev/null +++ b/zarb-ml/mageia-discuss/20120610/007749.html @@ -0,0 +1,216 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] Cannot unmount media as user + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Cannot%20unmount%20media%20as%20user&In-Reply-To=%3CCAJWAV%2BFLpZuCOpo6JRk7ExAtgJbz_HAb9sapC3DDc%2BE0hhbmrg%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="007748.html"> + <LINK REL="Next" HREF="007750.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] Cannot unmount media as user</H1> + <B>RICHARD WALKER</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Cannot%20unmount%20media%20as%20user&In-Reply-To=%3CCAJWAV%2BFLpZuCOpo6JRk7ExAtgJbz_HAb9sapC3DDc%2BE0hhbmrg%40mail.gmail.com%3E" + TITLE="[Mageia-discuss] Cannot unmount media as user">richard.j.walker at ntlworld.com + </A><BR> + <I>Sun Jun 10 14:06:17 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="007748.html">[Mageia-discuss] Cannot unmount media as user +</A></li> + <LI>Next message: <A HREF="007750.html">[Mageia-discuss] Cannot unmount media as user +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7749">[ date ]</a> + <a href="thread.html#7749">[ thread ]</a> + <a href="subject.html#7749">[ subject ]</a> + <a href="author.html#7749">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>I can see from your ck-list-sessions output that you are correctly +identified as both "local" and "active". That rules out any problems +with the consolekit authentication mechanism I think. + +The most likely cause now, in my experience with this problem, is you +have competing sub-systems fighting over who gets to mount and unmount +USB drives. The likely culprits are HAL and udisks2. udisks2 _should_ +win, but having HAL on your system is complicating things. + +Try watching your system log while plugging and unplugging your drive. +You should see something like this when you plug in, mount (using your +file manager) and then unmount: + +[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">root at Bathtub</A> x86_64]# tailf /var/log/messages +<snip> +Jun 10 12:59:05 Bathtub kernel: usb 2-8.3: new high-speed USB device +number 11 using ehci_hcd +Jun 10 12:59:05 Bathtub kernel: usb 2-8.3: New USB device found, +idVendor=0951, idProduct=1625 +Jun 10 12:59:05 Bathtub kernel: usb 2-8.3: New USB device strings: +Mfr=1, Product=2, SerialNumber=3 +Jun 10 12:59:05 Bathtub kernel: usb 2-8.3: Product: DT 101 II +Jun 10 12:59:05 Bathtub kernel: usb 2-8.3: Manufacturer: Kingston +Jun 10 12:59:05 Bathtub kernel: usb 2-8.3: SerialNumber: +0019E06B0845F95067600260 +Jun 10 12:59:05 Bathtub kernel: scsi14 : usb-storage 2-8.3:1.0 +Jun 10 12:59:05 Bathtub kernel: scsi 14:0:0:0: Direct-Access +Kingston DT 101 II 1.00 PQ: 0 ANSI: 2 +Jun 10 12:59:05 Bathtub kernel: sd 14:0:0:0: [sdh] 7827392 512-byte +logical blocks: (4.00 GB/3.73 GiB) +Jun 10 12:59:05 Bathtub kernel: sd 14:0:0:0: [sdh] Write Protect is off +Jun 10 12:59:05 Bathtub kernel: sd 14:0:0:0: [sdh] Incomplete mode +parameter data +Jun 10 12:59:05 Bathtub kernel: sd 14:0:0:0: [sdh] Assuming drive +cache: write through +Jun 10 12:59:05 Bathtub kernel: sd 14:0:0:0: [sdh] Incomplete mode +parameter data +Jun 10 12:59:05 Bathtub kernel: sd 14:0:0:0: [sdh] Assuming drive +cache: write through +Jun 10 12:59:05 Bathtub kernel: sdh: sdh1 +Jun 10 12:59:05 Bathtub kernel: sd 14:0:0:0: [sdh] Incomplete mode +parameter data +Jun 10 12:59:05 Bathtub kernel: sd 14:0:0:0: [sdh] Assuming drive +cache: write through +Jun 10 12:59:05 Bathtub kernel: sd 14:0:0:0: [sdh] Attached SCSI removable disk +Jun 10 12:59:24 Bathtub udisksd[1653]: Cleaning up mount point +/run/media/richard/KINGSTON (device 8:113 is not mounted) +Jun 10 12:59:24 Bathtub udisksd[1653]: Unmounted /dev/sdh1 on behalf of uid 501 +Jun 10 13:00:01 Bathtub kernel: sdh: detected capacity change from +4007624704 to 0 + +Try this yourself and post the output here. + +A very similar bug was logged against Cauldron in Jan/Feb of this +year. It is still open, I believe. In any event, I still have the same +problem as you report unless I work around it by doing the following: + +If it is installed then remove udisks +If it is installed then remove hal; that will take away +perl-Hal-Cdroms too, which is ok +make sure you DO NOT have an entry in /etc/fstab for your CDROM + +ref: Bug 4642, Bug 3533, Bug 4645, Bug 5051 + +Richard + +On 10/06/2012, andre999 <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">andre999mga at laposte.net</A>> wrote: +><i> Len Lawrence a écrit : +</I>>><i> On 10/06/12 10:59, andre999 wrote: +</I>>>><i> Len Lawrence a écrit : +</I>>>>><i> Mageia 2 fully updated +</I>>>>><i> GNOME Classic +</I>>>>><i> +</I>>>>><i> This is probably a newbie question.... I am not sure when this +</I>>>>><i> started to happen but when, as a user, I try to unmount a USB drive +</I>>>>><i> via the desktop icon I am told that I am not authorized to perform +</I>>>>><i> that operation. After browsing bugzilla and the forums it looked +</I>>>>><i> like the best way to get past this would be to use sudo. However, +</I>>>>><i> editing the sudoers file always throws up a syntax error. I have +</I>>>>><i> tried various commands based on examples but cannot get any to work. +</I>>>>><i> +</I>>>>><i> e.g. +</I>>>>><i> +</I>>>>><i> ALL /bin/umount NOPASSWD +</I>>>>><i> %users /bin/umount NOPASSWD +</I>>>>><i> %users localhost=/bin/umount NOPASSWD +</I>>>>><i> +</I>>>>><i> What is the correct recipe? RTFM only makes my old brain spin. +</I>>>>><i> +</I>>>>><i> Len +</I>>>>><i> +</I>>>><i> +</I>>>><i> try : +</I>>>><i> +</I>>>><i> %users ALL=/bin/umount NOPASSWD: ALL +</I>>>><i> +</I>>>><i> or maybe : +</I>>>><i> +</I>>>><i> %users ALL=/bin/umount device NOPASSWD: ALL +</I>>>><i> +</I>>>><i> where "device" is whatever the usb drive is mounted as. +</I>>>><i> Not workable if "device" is variable. +</I>>>><i> +</I>>>><i> Alternately, you could do : +</I>>>><i> su +</I>>>><i> (enter password) +</I>>>><i> umount ... +</I>>>><i> +</I>>>><i> As to why you are having the problem : +</I>>>><i> It means that the drive was mounted with root privileges, or the +</I>>>><i> privileges of another user. +</I>>>><i> Thus it is requiring root privileges (or that of the other user) to +</I>>>><i> unmount. +</I>>>><i> +</I>>>><i> Was it plugged it when the system was booted ? That could cause it to +</I>>>><i> have root privileges. +</I>>>><i> Is it in a line the /etc/fstab file ? +</I>>>><i> (if so, you just have to add the option "users" in the +</I>>>><i> comma-separated list in the third position in the line.) +</I>>>><i> +</I>>>><i> Or it could be a bug. +</I>>>><i> +</I>>><i> A bug seems doubtful because there do not seem to be any other reports +</I>>><i> of this behaviour. I have been forced to take the direct su/password +</I>>><i> route. +</I>>><i> +</I>>><i> The medium was plugged in at boot time but has been removed and +</I>>><i> replugged a few times. I had not considered that point. What you are +</I>>><i> saying is that removable media are treated as fixed if already plugged +</I>>><i> in at boot time? This is starting to make sense. +</I>><i> +</I>><i> It has happened to me in the past, although currently I have no problem +</I>><i> with a dvd that I sometimes have inserted on boot. (I use Gnome as +</I>><i> well, but haven't yet updated to mga2.) +</I>><i> If that is the cause, either something is not configured right or not +</I>><i> installed, or it is a bug. +</I>><i> If you have systemd activated, a configuration problem is not unlikely. +</I>><i> +</I>>><i> Will investigate fstab, edit if necessary and reboot without the +</I>>><i> drive . And if that works, mend sudoers. +</I>><i> +</I>><i> For fstab, the "users" option lets any user unmount the drive, even if +</I>><i> they didn't mount it. As well as mount it. It is a good option to use +</I>><i> for removable media. +</I>>><i> +</I>>><i> Thanks +</I>>><i> +</I>>><i> Len +</I>>><i> +</I>>><i> +</I>><i> +</I>><i> +</I>><i> -- +</I>><i> André +</I>><i> +</I>><i> +</I></PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="007748.html">[Mageia-discuss] Cannot unmount media as user +</A></li> + <LI>Next message: <A HREF="007750.html">[Mageia-discuss] Cannot unmount media as user +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7749">[ date ]</a> + <a href="thread.html#7749">[ thread ]</a> + <a href="subject.html#7749">[ subject ]</a> + <a href="author.html#7749">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss +mailing list</a><br> +</body></html> |