Bug 830303

You are getting a: 

DBusException: org.freedesktop.UDisks.Error.PermissionDenied: Not Authorized

from udisks. 

What desktop are you in? How did you login?

(In reply to comment #1)
> You are getting a: 
> 
> DBusException: org.freedesktop.UDisks.Error.PermissionDenied: Not Authorized
> 
> from udisks. 

Yes.  But I was not getting this before, with Fedora 16.
I can even reproduce that (as long as I still have F16 systems, that is...)

> What desktop are you in? How did you login?

I'm running FVWM2.

And how are you logging in? gdm?

(In reply to comment #3)
> And how are you logging in? gdm?

Yes, gdm, no changes here; I'm just starting a FVWM session instead of GNOME ot anything else (well, after fixing Bug 714482, that is).

Is ConsoleKit installed?

What does 'ck-list-sessions' show?

(In reply to comment #5)
> Is ConsoleKit installed?

Yes:

-> rpm -q ConsoleKit
ConsoleKit-0.4.5-2.fc17.x86_64

> What does 'ck-list-sessions' show?

-> ck-list-sessions
Session2:
        unix-user = '0'
        realname = 'root'
        seat = 'Seat1'
        session-type = ''
        active = FALSE
        x11-display = ''
        x11-display-device = ''
        display-device = '/dev/ttyS0'
        remote-host-name = ''
        is-local = TRUE
        on-since = '2012-06-08T22:16:04.518496Z'
        login-session-id = '3'
        idle-since-hint = '2012-06-09T15:23:40.922120Z'
Session3:
        unix-user = '500'
        realname = 'Wolfgang Denk'
        seat = 'Seat3'
        session-type = ''
        active = FALSE
        x11-display = ':0'
        x11-display-device = ''
        display-device = ''
        remote-host-name = ''
        is-local = TRUE
        on-since = '2012-06-09T15:16:10.621790Z'
        login-session-id = '235'
->

ok, if you edit: 

/usr/share/xsessions/fvwm.desktop

and change: 

Exec=fvwm

to

Exec=ck-launch-session fvwm

and logout and back on and see if anything changes?

(In reply to comment #7)
> ok, if you edit: 
> /usr/share/xsessions/fvwm.desktop
> and change: 
> Exec=fvwm
> to
> Exec=ck-launch-session fvwm
> 
> and logout and back on and see if anything changes?

This changes something - it makes things worse.

Fvwm still gets started, but it does not start any of my Xlients -
similar as if my patch for Bug 714482 had not been aplied.

When I start calibre in this environment, it still fails to detect the
connected reader device, similar to what we had before.

So I reverted this change (or should I keep it?  If yes, then how do I
get the actions in my $HOME/.Xclients-default file run?).


BTW:  thanks for your quick help.  I really appreciate it!

ok, what happens if you use one of the fuller desktops? (Xfce, Gnome)? 

Does it work as expected there? or still fails?

(This will hopefully tell us if it's a issue with your hardware/setup somewhere or something particular to fvwm2). 

Also, can you (in fvwm2 without ck-launch-session), mount manually the device and see if calibre sees it then?

(In reply to comment #9)
> ok, what happens if you use one of the fuller desktops? (Xfce, Gnome)? 
> 
> Does it work as expected there? or still fails?

Hm... this is funny (actually not so).

So I did the following:

- I checked again running in fwvm - it didn't work.
- Logged out, log into gnome session.
- It works.
- Logged out, log into xfce session.
- It works.
- Logged out, log into KDE Plasma session.
- It works.
- Logged out, log into fwvm session.
- It works!!!
- Reboot, log into fwvm session.
- It works!!!

I cannot reproduce the problem any more.  It appears as if one of the
gnome, xfce, or KDE logins magically "fixed" something in a persistent
way, so that it even works after a reboot.

> (This will hopefully tell us if it's a issue with your hardware/setup
> somewhere or something particular to fvwm2). 

I don't think it is hardware rleated as it has always worked before
(i. e. in Fedora 15 and Fedora 16).  It stopped working after
upgrading to Fedora 17.

Note that up until now I had never loged in on Fedore 17 with either
of gnome, xfce, or KDE, so it may well be that one of these logins has
created any files, links, directories or whatever that now make it
work.

Although the problem appears fixed for me now I don;t feel happy as it
means the cause of the problem is still unknown.

> Also, can you (in fvwm2 without ck-launch-session), mount manually the
> device and see if calibre sees it then?

Where would I mount it?  I guess it needs some specific mount point?

Best regards,

Wolfgang Denk

Wow. I don't understand that. 

If you make a new user and only login to fvwm does it fail for them?

The mount can be anywhere... calibre just looks for the usb device strings, so it can figure out where you mounted it.

I tested with a newly created login, and it worked, too.
I also tested on another host, where I never tried this before,
and it worked as well.

I'm at the end of my wits - I cannot reproduce the problem any more.
I can only speculate that some configuration data must have been left
from earlier runs under Fedora 16 that blocked the access somehow,
and that got cleaned up when logging into Gnome.

Please feel free to close this bug - I can't reproduce it any more.

Yeah, bugs like these are always frustrating. ;( 

Do reopen or file a new one if you can see it happening again...

(In reply to comment #13)
> Yeah, bugs like these are always frustrating. ;( 

Indeed :-(

> Do reopen or file a new one if you can see it happening again...

Will do.  Thanks a lot for all your help!