On Mon, Nov 28, 2011 at 12:58, Myra Nelson <myra.nelson@xxxxxxxxxx> wrote: > > > On Mon, Nov 28, 2011 at 12:23, Myra Nelson <myra.nelson@xxxxxxxxxx> wrote: > >> >> >> On Mon, Nov 28, 2011 at 11:19, Madhurya Kakati <mkakati2805@xxxxxxxxx>wrote: >> >>> On Saturday, November 26, 2011, Clive Cooper wrote: >>> >>> > On 25 November 2011 15:12, Madhurya Kakati <mkakati2805@xxxxxxxxx >>> <javascript:;>> >>> > wrote: >>> > > Well what I said is true. When I first started using arch I didn't >>> mind >>> > > when stuff broke. But now after setting up the OS according to my >>> tastes >>> > I >>> > > want it to stay as it is. So I want it to be stable. But I also don't >>> > want >>> > > to sacrifice the freedom if using arch. >>> > > And I made this my primary work OS and it really is hurting >>> productivity >>> > as >>> > > I tend to work on a lot of removal drives. >>> > > On Nov 25, 2011 6:00 PM, "Tom Gundersen" <teg@xxxxxxx<javascript:;>> >>> > wrote: >>> > > >>> > >> On Fri, Nov 25, 2011 at 1:22 PM, Madhurya Kakati < >>> mkakati2805@xxxxxxxxx<javascript:;> >>> > > >>> > >> wrote: >>> > >> > After a recent update, I am unable to mount any drives by clicking >>> > their >>> > >> > names in nautilus side panel like I used to do before. I use >>> awesome >>> > wm >>> > >> and >>> > >> > start it via slim which itself is started via the inittab method. >>> > >> >>> > >> Are you able to reproduce the problem if you use GDM in stead of >>> slim >>> > >> and start it using the rc-script rather than inittab? >>> > >> >>> > >> > I have dbus installed and it starts up automatically at boot. >>> Also in >>> > my >>> > >> > .xinitrc file I have ck-launch-session and dbus-launch before >>> awesome. >>> > >> >>> > >> This sounds like it should work, but I don't use your precise setup >>> so >>> > >> cannot confirm it. I seem to remember other people having similar >>> > >> problems and replacing SLIM with something else fixed it (but I >>> don't >>> > >> remember the details so I might be wrong). >>> > >> >>> > >> > Everything used to work fine like this before the update. Now >>> when I >>> > try >>> > >> to >>> > >> > mount a drive I get the error not authorized. I am also in the >>> group >>> > >> > storage. >>> > >> >>> > >> ConsoleKit, UDisks and PolicyKit should be responsible for this >>> > >> working and you should not need to be in any particular group. >>> > >> >>> > >> > I really like arch Linux but these stuff breaking on updates is >>> what >>> > >> pisses >>> > >> > me off. >>> > >> > Please help me as this is affecting my productivity on my machine. >>> > >> >>> > >> Pro tip: You'd be more likely to get help if you skipped these kind >>> of >>> > >> comments... >>> > >> >>> > >> -t >>> > >> >>> > > >>> > >>> > I had this happen once quite some time ago now.What I found was that a >>> > library file went missing. >>> > Try this...ldd /usr/lib/gvfs/gvfs-gdu-volume-monitorSee if it tells >>> > you that a file is missing and if so then just install the required >>> > package. >>> > Outside of that installing devmon from AUR could solve the problem. >>> > Clive-- >>> > Infinity: A concept for those who cannot comprehend the big picture. >>> > >>> > () Arch Linux - For movers and shakers. () >>> > >>> >>> Here is the output for the command >>> ldd /usr/lib/gvfs/gvfs-gdu-volume-monitor >>> >>> linux-vdso.so.1 => (0x00007fff73fff000) >>> libgdu.so.0 => /usr/lib/libgdu.so.0 (0x00007f479ed9b000) >>> libgudev-1.0.so.0 => /lib/libgudev-1.0.so.0 (0x00007f479eb91000) >>> libgvfscommon.so.0 => /usr/lib/libgvfscommon.so.0 (0x00007f479e979000) >>> libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f479e735000) >>> libpthread.so.0 => /lib/libpthread.so.0 (0x00007f479e518000) >>> libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00007f479e1d8000) >>> libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007f479df88000) >>> libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00007f479dd83000) >>> libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f479da8e000) >>> libc.so.6 => /lib/libc.so.6 (0x00007f479d707000) >>> libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007f479d503000) >>> libdbus-glib-1.so.2 => /usr/lib/libdbus-glib-1.so.2 (0x00007f479d2dc000) >>> librt.so.1 => /lib/librt.so.1 (0x00007f479d0d4000) >>> libgnome-keyring.so.0 => /usr/lib/libgnome-keyring.so.0 >>> (0x00007f479ceb2000) >>> libudev.so.0 => /lib/libudev.so.0 (0x00007f479cca4000) >>> libutil.so.1 => /lib/libutil.so.1 (0x00007f479caa1000) >>> /lib/ld-linux-x86-64.so.2 (0x00007f479efd6000) >>> libffi.so.5 => /usr/lib/libffi.so.5 (0x00007f479c899000) >>> libdl.so.2 => /lib/libdl.so.2 (0x00007f479c695000) >>> libpcre.so.0 => /lib/libpcre.so.0 (0x00007f479c43a000) >>> libz.so.1 => /usr/lib/libz.so.1 (0x00007f479c221000) >>> libresolv.so.2 => /lib/libresolv.so.2 (0x00007f479c00a000) >>> libgcrypt.so.11 => /lib/libgcrypt.so.11 (0x00007f479bd8d000) >>> libgpg-error.so.0 => /lib/libgpg-error.so.0 (0x00007f479bb8a000) >>> >>> I don't see any files that might be missing. >>> >> >> I'm experiencing the same problem and I use openbox, obdevicemenu, >> udisks, udiskie, and log in on tty0 then type startx. I plugged in a usb >> drive, couldn't mount it, then went to tty0 and found this error message: >> >> [ failed to mount /org/freedesktop/UDisks/dev/sdc1 >> org.freedesktop.UDisks.Error.Permission.Denied Not Authorized ] >> >> There is also an error message on tty0 from thunar-volman which is >> exactly the same. I went through all the logs and can't find any mention of >> it anywhere. One of the things I haven't yet learned to do is capture the >> output on tty0 to another terminal so I have to go back and forth >> occassionally to find these things. Hope I got the wording right. Seems >> like it's an error associated with the latest udev update. >> >> Myra >> >> -- >> Life's fun when your sick and psychotic! >> > > > Meaculpa. It's a permission error but its with Udisks. > > su > password > udisks --mount /dev/xxxx /media/xxxx > > works fine. > > I have the requisite > > udiskie requires permission for the > org.freedesktop.udisks.filesystem-mount action. This is usually granted > in sessions launched with ConsoleKit<http://www.freedesktop.org/wiki/Software/ConsoleKit>support. > If run outside a desktop manager with ConsoleKit<http://www.freedesktop.org/wiki/Software/ConsoleKit> > support, the permission can be granted using PolicyKit<http://www.freedesktop.org/wiki/Software/PolicyKit> > by creating a file called 10-udiskie.pkla in > /etc/polkit-1/localauthority/50-local.d with these contents: > > [udiskie] > Identity=unix-group:storage > Action=org.freedesktop.udisks.filesystem-mount > ResultAny=yes > > This configuration allows all members of the storage group to run udiskie. > I've tried the .pkla file as above and with two additional lines > > ResultInactive=no > ResultActive=yes > > Seems as though it may be a permissions issue that's handled within a > desktop environment. I'm unable to check that without installing a desktop > environment. Time to readup on consolekit and polkit. > > Myra > -- > Life's fun when your sick and psychotic! > The dangerous way place a file in /etc/polkit-1/nullbackend.conf 99-whatever-you-want-to-call-it.conf [Configuration] priority=1000 sudo /usrlib/polkit-1/polkitd restart , then I restarted openbox. This disables policykit. I got the idea from the following mailing list http://lists.freedesktop.org/archives/hal-commit/2009-February/004854.html. The name suggested for the files was 99-i-hate-policykit-conf At least it solves the problem for now. Myra -- Life's fun when your sick and psychotic!
