FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux General Discussion

 
 
LinkBack Thread Tools
 
Old 11-25-2011, 11:30 AM
Tom Gundersen
 
Default Mounting drives via nautilus stopped working after update.

On Fri, Nov 25, 2011 at 1:22 PM, Madhurya Kakati <mkakati2805@gmail.com> 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
 
Old 11-25-2011, 02:12 PM
Madhurya Kakati
 
Default Mounting drives via nautilus stopped working after update.

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@jklm.no> wrote:

> On Fri, Nov 25, 2011 at 1:22 PM, Madhurya Kakati <mkakati2805@gmail.com>
> 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
>
 
Old 11-25-2011, 08:13 PM
Clive Cooper
 
Default Mounting drives via nautilus stopped working after update.

On 25 November 2011 15:12, Madhurya Kakati <mkakati2805@gmail.com> 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@jklm.no> wrote:
>
>> On Fri, Nov 25, 2011 at 1:22 PM, Madhurya Kakati <mkakati2805@gmail.com>
>> 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. ()
 
Old 11-28-2011, 04:19 PM
Madhurya Kakati
 
Default Mounting drives via nautilus stopped working after update.

On Saturday, November 26, 2011, Clive Cooper wrote:

> On 25 November 2011 15:12, Madhurya Kakati <mkakati2805@gmail.com<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@jklm.no <javascript:;>>
> wrote:
> >
> >> On Fri, Nov 25, 2011 at 1:22 PM, Madhurya Kakati <mkakati2805@gmail.com<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.
 
Old 11-28-2011, 05:23 PM
Myra Nelson
 
Default Mounting drives via nautilus stopped working after update.

On Mon, Nov 28, 2011 at 11:19, Madhurya Kakati <mkakati2805@gmail.com>wrote:

> On Saturday, November 26, 2011, Clive Cooper wrote:
>
> > On 25 November 2011 15:12, Madhurya Kakati <mkakati2805@gmail.com
> <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@jklm.no <javascript:;>>
> > wrote:
> > >
> > >> On Fri, Nov 25, 2011 at 1:22 PM, Madhurya Kakati <
> mkakati2805@gmail.com<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!
 
Old 11-28-2011, 05:58 PM
Myra Nelson
 
Default Mounting drives via nautilus stopped working after update.

On Mon, Nov 28, 2011 at 12:23, Myra Nelson <myra.nelson@hughes.net> wrote:

>
>
> On Mon, Nov 28, 2011 at 11:19, Madhurya Kakati <mkakati2805@gmail.com>wrote:
>
>> On Saturday, November 26, 2011, Clive Cooper wrote:
>>
>> > On 25 November 2011 15:12, Madhurya Kakati <mkakati2805@gmail.com
>> <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@jklm.no <javascript:;>>
>> > wrote:
>> > >
>> > >> On Fri, Nov 25, 2011 at 1:22 PM, Madhurya Kakati <
>> mkakati2805@gmail.com<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!
 
Old 11-28-2011, 06:47 PM
Myra Nelson
 
Default Mounting drives via nautilus stopped working after update.

On Mon, Nov 28, 2011 at 12:58, Myra Nelson <myra.nelson@hughes.net> wrote:

>
>
> On Mon, Nov 28, 2011 at 12:23, Myra Nelson <myra.nelson@hughes.net> wrote:
>
>>
>>
>> On Mon, Nov 28, 2011 at 11:19, Madhurya Kakati <mkakati2805@gmail.com>wrote:
>>
>>> On Saturday, November 26, 2011, Clive Cooper wrote:
>>>
>>> > On 25 November 2011 15:12, Madhurya Kakati <mkakati2805@gmail.com
>>> <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@jklm.no<javascript:;>>
>>> > wrote:
>>> > >
>>> > >> On Fri, Nov 25, 2011 at 1:22 PM, Madhurya Kakati <
>>> mkakati2805@gmail.com<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!
 
Old 11-28-2011, 09:49 PM
Myra Nelson
 
Default Mounting drives via nautilus stopped working after update.

On Mon, Nov 28, 2011 at 14:10, Leonid Isaev <lisaev@umail.iu.edu> wrote:

> On Mon, 28 Nov 2011 13:47:12 -0600
> Myra Nelson <myra.nelson@hughes.net> wrote:
>
> > On Mon, Nov 28, 2011 at 12:58, Myra Nelson <myra.nelson@hughes.net>
> wrote:
> >
> > >> 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
>
> None of your emails make sense to me. You should check whether your dbus is
> running and you are connected to it (ck-list-sessions, ps -e u | grep dbus,
> your .xinitrc). You don't need udiskie, pkla files, storage group, gvfs or
> thunar-volman. Plain udisks from terminal should work if your ck-session
> is set
> up correctly.
>
> --
> Leonid Isaev
> GnuPG key ID: 164B5A6D
> Key fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
>

Leonid:

The solution is on the wiki (
https://wiki.archlinux.org/index.php/Xinitrc), I read it the other
night, I didn't read far enough, and I applied the
fix backwards because I didn't read the xfce manually page. It has to do
with https://bugs.archlinux.org/task/25031, for which you have a comment.
I crafted my .xinitrc file like this

[ numlockx &
autocutsel -fork &
autocutsel -selection PRIMARY -fork &

# Source scripts in /etc/X11/xinit/xinitrc.d/
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
exec openbox-session ]

Instead of like this:

[ numlockx &
autocutsel -fork &
autocutsel -selection PRIMARY -fork &

# Source scripts in /etc/X11/xinit/xinitrc.d/
#if [ -d /etc/X11/xinit/xinitrc.d ]; then
# for f in /etc/X11/xinit/xinitrc.d/*; do
# [ -x "$f" ] && . "$f"
# done
# unset f
#fi
exec ck-launch-session dbus-launch openbox-session ]

The first way udisks also fails for a normal user on the console. The
second way everything works right. My bad. Meaculpa. Sorry for the noise.

before change

[myra@gandalf /media]:/usr/bin/ck-list-sessions | ps -e u | grep xinitrc
myra 3680 0.0 0.0 15732 836 tty1 S+ 11:49 0:00 xinit
/home/myra/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth
/tmp/serverauth.RnDioa9aqT

after change
[myra@gandalf ~]:/usr/bin/ck-list-sessions | ps -e u | grep xinitrc
myra 1866 0.0 0.0 15732 832 tty1 S+ 16:24 0:00 xinit
/home/myra/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth
/tmp/serverauth.ijpyBJwqre

Myra
--
Life's fun when your sick and psychotic!
 
Old 11-28-2011, 10:45 PM
Myra Nelson
 
Default Mounting drives via nautilus stopped working after update.

On Mon, Nov 28, 2011 at 17:19, Leonid Isaev <lisaev@umail.iu.edu> wrote:

> On Mon, 28 Nov 2011 16:49:21 -0600
> Myra Nelson <myra.nelson@hughes.net> wrote:
> >
> > Leonid:
> >
> > The solution is on the wiki (
> > https://wiki.archlinux.org/index.php/Xinitrc), I read it the other
> > night, I didn't read far enough, and I applied the
> > fix backwards because I didn't read the xfce manually page. It has to do
> > with https://bugs.archlinux.org/task/25031, for which you have a
> comment.
> > I crafted my .xinitrc file like this
> >
> > [ numlockx &
> > autocutsel -fork &
> > autocutsel -selection PRIMARY -fork &
> >
> > # Source scripts in /etc/X11/xinit/xinitrc.d/
> > if [ -d /etc/X11/xinit/xinitrc.d ]; then
> > for f in /etc/X11/xinit/xinitrc.d/*; do
> > [ -x "$f" ] && . "$f"
> > done
> > unset f
> > fi
> > exec openbox-session ]
> >
> > Instead of like this:
> >
> > [ numlockx &
> > autocutsel -fork &
> > autocutsel -selection PRIMARY -fork &
> >
> > # Source scripts in /etc/X11/xinit/xinitrc.d/
> > #if [ -d /etc/X11/xinit/xinitrc.d ]; then
> > # for f in /etc/X11/xinit/xinitrc.d/*; do
> > # [ -x "$f" ] && . "$f"
> > # done
> > # unset f
> > #fi
> > exec ck-launch-session dbus-launch openbox-session ]
> >
> > The first way udisks also fails for a normal user on the console. The
> > second way everything works right. My bad. Meaculpa. Sorry for the
> noise.
> >
> > before change
> >
> > [myra@gandalf /media]:/usr/bin/ck-list-sessions | ps -e u | grep xinitrc
> > myra 3680 0.0 0.0 15732 836 tty1 S+ 11:49 0:00 xinit
> > /home/myra/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth
> > /tmp/serverauth.RnDioa9aqT
> >
> > after change
> > [myra@gandalf ~]:/usr/bin/ck-list-sessions | ps -e u | grep xinitrc
> > myra 1866 0.0 0.0 15732 832 tty1 S+ 16:24 0:00 xinit
> > /home/myra/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth
> > /tmp/serverauth.ijpyBJwqre
> >
> > Myra
>
> In any normal desktop, the job of the starter scripts is to setup the
> session by
> calling dbus-launsh with appropriate arguments. However, openbox is quite
> limited in this sense and does none of the above. That is why you need
> dbus-launch in your .xinitrc. And that is also why the wiki is completely
> wrong.
>
> Finally, why on earth did you pipe ck-list-sessions to ps??? I meant these
> as
> separate commands. I just wanted to see whether you have dbus-launch
> running,
> like this:
>
> $ ps -e u | gr dbus
> dbus 769 0.0 0.0 13124 1084 ? Ss 09:27 0:00 /usr/bin/dbus-daemon --system
>
> lisaev 26173 0.0 0.0 20000 584 pts/0 S 09:38 0:00 dbus-launch --sh-syntax
> --exit-with-session
>
> lisaev 26174 0.0 0.0 13264 1304 ? Ss 09:38 0:00 /usr/bin/dbus-daemon --fork
> --print-pid 5 --print-address 7 --session
>
> --
> Leonid Isaev
> GnuPG key ID: 164B5A6D
> Key fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
>

Leonid

Please forgive my error on the commands. I don't always sort things out
right. I'm still recovering from a long hospital stay from CO2 poisioning,
self inflicted from copd and I simply forget to breathe. It's been almost a
year and I still not right. I was thinking after my last post that I don't
seem to communicate my thoughts well anymore, unless it's one of my rants.
It may be a generational thing, I'm not sure, since my golden (lol) years
have arrived. It may be my adhd coupled with early onset dementia from the
CO2 episode. I know all I can do is keep trying until I get it right.

That may be too much info for the ml. I know I sometimes seem muddled but
there is a reason for it. I'm only hoping it goes away or I'll be back to
using an os that does everything for me, UGH.

Thanks for everyone's patienence.

Myra
--
Life's fun when your sick and psychotic!
 
Old 11-29-2011, 10:18 AM
Madhurya Kakati
 
Default Mounting drives via nautilus stopped working after update.

Sorry to break the flow here, but how do I solve my problem.
 

Thread Tools




All times are GMT. The time now is 10:53 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org