Bug 773324 - "Not Authorized" when trying to mount media in dolphin or through the notification pop-up
Summary: "Not Authorized" when trying to mount media in dolphin or through the notific...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-workspace
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-11 14:37 UTC by Andreas Bierfert
Modified: 2012-01-11 17:14 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-11 17:10:18 UTC
Type: ---


Attachments (Terms of Use)
yum log (14.30 KB, text/plain)
2012-01-11 17:11 UTC, Andreas Bierfert
no flags Details

Description Andreas Bierfert 2012-01-11 14:37:09 UTC
Description of problem:
When trying to mount e.g. a cd-rom/usb stick etc. "Not Authorized" message is displayed and the media is not mounted. Worked fine in f16 before upgrading to rawhide last weekend.

Version-Release number of selected component (if applicable):

kdm-4.7.97-1.fc17.x86_64
kdebase-workspace-4.7.97-1.fc17.x86_64
polkit-kde-0.99.0-3.fc17.x86_64
polkit-0.104-2.fc17.x86_64
ConsoleKit-0.4.5-1.fc15.x86_64
kernel-3.2.0-2.fc17.x86_64
glibc-2.15-1.fc17.x86_64

ck-list-sessions
Session1:
	unix-user = '1000'
	realname = 'Andreas Bierfert'
	seat = 'Seat1'
	session-type = ''
	active = TRUE
	x11-display = ':0'
	x11-display-device = '/dev/tty1'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2012-01-11T08:05:53.440754Z'
	login-session-id = '4294967295'

Comment 1 Lukáš Tinkl 2012-01-11 14:43:04 UTC
Looks like a polkit problem...

Comment 2 Rex Dieter 2012-01-11 14:49:51 UTC
pinging polkit folks for advice, comment.  I recall seeing a recent blog about adding systemd session handling.  Do DE's need to adapt to that, or is the polkit/consolekit functionality expected to continue to work as before.

Comment 3 David Zeuthen 2012-01-11 16:26:46 UTC
(In reply to comment #2)
> pinging polkit folks for advice, comment.  I recall seeing a recent blog about
> adding systemd session handling.  Do DE's need to adapt to that, or is the
> polkit/consolekit functionality expected to continue to work as before.

Nope, no changes are required on the desktop side for this.

Comment 4 Kevin Kofler 2012-01-11 16:33:49 UTC
Is this related to the demise of polkit-desktop-policy?

Comment 5 David Zeuthen 2012-01-11 16:41:25 UTC
Hard to say. Better feedback / error messages from the reporter would be helpful. 

Would also be helpful to try to check with pkcheck(1) and manually running "/usr/libexec/polkit-1/polkitd -r" from a root shell and paste the debug output

Comment 6 Andreas Bierfert 2012-01-11 17:10:18 UTC
Hm, something from todays upgrade seems to fix this issue for me. I did a couple of reboots after the upgrade to make sure the behavior is consistent.

Other polkit related things now seem to work again as well (VirtualBox related stuff).

I will attach the transaction log. A quick downgrade of systemd (which I would have suspected) did not bring back the original bug.

I will close and reopen if it comes up again.

Comment 7 Andreas Bierfert 2012-01-11 17:11:09 UTC
Created attachment 552174 [details]
yum log

Comment 8 David Zeuthen 2012-01-11 17:14:23 UTC
The polkit upgrade to 0.104 or later definitely needs a reboot or at the very least a restart of the polkit authentication agent (e.g. restart your desktop session). Maybe that's why you ran into problems.


Note You need to log in before you can comment on or make changes to this bug.