Tips and tricks for ConsoleKit, PolicyKit, and udev helpers

[DancesWithWords]

I can not find this option in my 2.6.36-r5 or 2.6.38 kernels CONFIG_USB_SUSPEND=y
What am I missing?

[darkice]

go in "Power Management and ACPI options", there's "Run-time PM core functionality"

it must be set , so it will appear the right option under Usb section

By the way, i'm having this issue with thunar...it doesn't mount anything and now i've not hal (as i've read here, i've uninstalled and removed the flag)...i don't know what to try, it keeps saying "Failed to mount mycdromname - Not Authorized"

sob...i'll be forced to ask to some people in the italian section of this forum...

[VoidMage]

darkice, as the thread title says, most likely a consolekit problem.
Check if your session is listed as active and if udisks is able to mount from a terminal.

[rigolot]

Hi, I'm going crazy with my problem.
I've done several time the tuto in the first page, but still complaining with "Not Authorized". As you guess I'm under Xfce4. I can see auto-mounted drives on the sidebar of thunar so udisks works. I've removed slim to force the ck-launch-session startxfce4 after login. But ck-list-sessions always tell me that my session is ACTIVE = FALSE. I also check if the kernel options are set correctly, removed hal, etc...

Now, I don't now what to do.

Do you have any suggestion ?

[tbart]

you can use stable slim, it works flawlessly with e17 here and people use it with xfce as well.
you just have to make sure that

a) you run ck-launch-session
b) you have a login shell
c) your /etc/pam.d/system-login has

Code: Select all

session     optional    pam_ck_connector.so

without the "nox11" at the end.

Most people in this thread having problems do/did not have a login shell. Just put some variable in your ~/.bashrc, login with your favourite DM and see whether the variable is set. It doesn't help to set a lot of things in your profile if it does not get sourced.

The best way for realizing a) IMHO is this:
- leave /etc/slim.conf like it is

Code: Select all

login_cmd           exec /bin/bash -login /usr/share/slim/Xsession %session

so you don't have to change it with every update.
- edit your Xsession so it contains the needed things for CK:

Code: Select all

blackknight ~ # cat /etc/X11/Sessions/enlightenment 
#!/bin/bash
exec ck-launch-session dbus-launch /usr/bin/enlightenment_start

(or adapt for your favourite DE like XFCE)

This should get you a maintainable config that works.

I am still struggling with eSATA and ntfs-3g/utf-8 so if anyone has a solution I am open to suggestions.

[engil]

@tbart : Thanks for that ! Works flawlessly (using e17) !

[shallpion]

Thank you for the detailed explanation. I am running gnome on ~amd64 and I just did what you suggested step by step. everthing is fine except now I am not able to bring up the root password dialog window when I clicked on the icon of an NTFS partition in nautilus. Only a small window saying "Authentication is required" popped up. I did emerged the agent polkit-gnome. I had no problem in mounting USB devices. Is there any configuration I have to make about polkit-gnome so the authentication dialog can pop up as before when I had hal?

Thank you.

[SamuliSuominen]

Thank you for the detailed explanation. I am running gnome on ~amd64 and I just did what you suggested step by step. everthing is fine except now I am not able to bring up the root password dialog window when I clicked on the icon of an NTFS partition in nautilus. Only a small window saying "Authentication is required" popped up. I did emerged the agent polkit-gnome. I had no problem in mounting USB devices. Is there any configuration I have to make about polkit-gnome so the authentication dialog can pop up as before when I had hal?

Thank you.

Well, you should see /usr/libexec/polkit-gnome-authentication-agent-1 running in `ps`.

Like this:

$ ps -C polkit-gnome-authentication-agent-1
PID TTY TIME CMD
28377 tty1 00:00:00 polkit-gnome-authentication-agent-1

It's normally autostarted by this file:

/etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop

And if it's not, then you need to add:

/usr/libexec/polkit-gnome-authentication-agent-1 &

Somewhere in your desktops starting scripts. Propably users of Fluxbox, Openbox, and such will need to do this because they don't support the .desktop autostart files, like GNOME or Xfce does.

[shallpion]

Well, you should see /usr/libexec/polkit-gnome-authentication-agent-1 running in `ps`.

Like this:

$ ps -C polkit-gnome-authentication-agent-1
PID TTY TIME CMD
28377 tty1 00:00:00 polkit-gnome-authentication-agent-1

It's normally autostarted by this file:

/etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop

And if it's not, then you need to add:

/usr/libexec/polkit-gnome-authentication-agent-1 &

Somewhere in your desktops starting scripts. Propably users of Fluxbox, Openbox, and such will need to do this because they don't support the .desktop autostart files, like GNOME or Xfce does.

Thank you for your detailed explanations. Yes I think the problem is that polkit-gnome-authentication-agent-1 is not running here. I tried to put it in "Startup Applications" in gnome menu but it still refuses to run automatically after I login through gdm. I have to manually start it or put in somewhere in /etc/X11/xinit.d/... . But I am still curious, is there any reason why the program cannot be autostarted by gnome-autostart?

Thanks in advance.

[tbart]

@ssuominen:

Is this really the way to go?

My previous hal setup did not ask me for a password with ntfs-3g as I had this policy file in place:

Code: Select all

blackknight ~ # cat /etc/hal/fdi/policy/20-ntfs-as-user.fdi 
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> 

<deviceinfo version="0.2"> 
    <device> 
        <match key="volume.fstype" string="ntfs"> 
            <match key="@block.storage_device:storage.hotpluggable" bool="true"> 
                <merge key="volume.fstype" type="string">ntfs-3g</merge> 
                <merge key="volume.policy.mount_filesystem" type="string">ntfs-3g</merge> 
                <append key="volume.mount.valid_options" type="strlist">locale=</append> 
            </match> 
        </match> 
    </device> 
</deviceinfo>

(granted, I don't really see the line that really made the user able to mount with ntfs-3g, but hey, it worked!)

It also made utf8 possible with ntfs.
Isn't it possible to get this working right inside udisks without another daemon running? (preferably also solving the eSATA problem I mentioned earlier?)

That's the only thing left for a proper udisks setup, I think.

Isn't the equivalent of /etc/hal/fdi/policy/10-ntfs3g.fdi (gets installed by ntfs-3g) for udisks missing on ntfs.3g's side?

[SamuliSuominen]

@ssuominen:

Is this really the way to go?

My previous hal setup did not ask me for a password with ntfs-3g as I had this policy file in place:

Code: Select all

blackknight ~ # cat /etc/hal/fdi/policy/20-ntfs-as-user.fdi 
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> 

<deviceinfo version="0.2"> 
    <device> 
        <match key="volume.fstype" string="ntfs"> 
            <match key="@block.storage_device:storage.hotpluggable" bool="true"> 
                <merge key="volume.fstype" type="string">ntfs-3g</merge> 
                <merge key="volume.policy.mount_filesystem" type="string">ntfs-3g</merge> 
                <append key="volume.mount.valid_options" type="strlist">locale=</append> 
            </match> 
        </match> 
    </device> 
</deviceinfo>

(granted, I don't really see the line that really made the user able to mount with ntfs-3g, but hey, it worked!)

It also made utf8 possible with ntfs.
Isn't it possible to get this working right inside udisks without another daemon running? (preferably also solving the eSATA problem I mentioned earlier?)

That's the only thing left for a proper udisks setup, I think.

Isn't the equivalent of /etc/hal/fdi/policy/10-ntfs3g.fdi (gets installed by ntfs-3g) for udisks missing on ntfs.3g's side?

Well, I'm going to throw some ideas here... Maybe it will get you on right track...

Option 1, modifying original config directly. Please try Option 2. below first.:

/usr/share/polkit-1/actions/org.freedesktop.udisks.policy:

Code: Select all

 <action id="org.freedesktop.udisks.filesystem-mount-system-internal">
    <description>Mount a system-internal device</description>
    <message>Authentication is required to mount the device</message>
    <defaults>
      <allow_any>no</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>auth_admin_keep</allow_active>      <- THIS LINE:   Change "auth_admin_keep" to "yes"
    </defaults>
  </action>

Option 2, custom .pkla file:

See this manpage: man 8 pklocalauthority

It has examples at the bottom. Let me try to write one for your case (completely untested of course):

/etc/polkit-1/localauthority/50-local.d/org.freedesktop.udisks.pkla:

Code: Select all

          [Normal Staff Permissions]
           Identity=unix-group:wheel
           Action=org.freedesktop.udisks.*
           ResultAny=no
           ResultInactive=no
           ResultActive=yes

That should give group "wheel" permission to mount/umount drives freely for local users (see ResultActive=yes)
You could use something like unix-user:foobar that would give user foobar the same access too... Don't need to be group...

With this, and with 'man 8 pklocalauthority'... Should be rather easy.

[Catanduva]

N00b question here. I'm now using wmii window manager with only terminal/ncurses apps (centerim, rtorrent, midnight commander, moc), just firefox is in gtk.
I need consolekit, policykit, gvfs, udev, upower? I want to mannually mount my devices for now, i don't need automount anymore, what should i remove from my system?

[axlalf]

hiho

i have a problem. i cant get the consolekit session active.

Code: Select all

$ck-list-sessions  
Session1:
	unix-user = '1000'
	realname = '(null)'
	seat = 'Seat2'
	session-type = ''
	active = FALSE
	x11-display = ':0'
	x11-display-device = '/dev/tty7'
	display-device = '/dev/tty6'
	remote-host-name = ''
	is-local = FALSE
	on-since = '2011-04-03T18:33:49.414204Z'
	login-session-id = '2'

tried both suggested lines in the .xinitrc - neither worked

i am using enlightenment 0.17 on a x86_64 system, running the unstable 2.6.38 kernel.

sys-auth/consolekit-0.4.4 was built with the following:
USE="(multilib) pam policykit -debug -doc -test"

x11-wm/enlightenment-9999 was built with the following:
USE="acpi bluetooth e_modules_battery e_modules_clock e_modules_comp e_modules_conf-applications e_modules_conf-borders e_modules_conf-clientlist e_modules_conf-colors e_modules_conf-desk e_modules_conf-desklock e_modules_conf-desks e_modules_conf-dialogs e_modules_conf-display e_modules_conf-dpms e_modules_conf-edgebindings e_modules_conf-engine e_modules_conf-fonts e_modules_conf-icon-theme e_modules_conf-imc e_modules_conf-interaction e_modules_conf-intl e_modules_conf-keybindings e_modules_conf-menus e_modules_conf-mime e_modules_conf-mouse e_modules_conf-mouse-cursor e_modules_conf-mousebindings e_modules_conf-paths e_modules_conf-performance e_modules_conf-profiles e_modules_conf-scale e_modules_conf-screensaver e_modules_conf-shelves e_modules_conf-startup e_modules_conf-theme e_modules_conf-transitions e_modules_conf-wallpaper e_modules_conf-wallpaper2 e_modules_conf-window-display e_modules_conf-window-focus e_modules_conf-window-manipulation e_modules_conf-window-remembers e_modules_conf-winlist e_modules_connman e_modules_cpufreq e_modules_dropshadow e_modules_everything e_modules_everything-apps e_modules_everything-calc e_modules_everything-files e_modules_everything-settings e_modules_everything-windows e_modules_fileman e_modules_fileman_opinfo e_modules_gadman e_modules_ibar e_modules_ibox e_modules_illume2 e_modules_mixer e_modules_msgbus e_modules_pager e_modules_start e_modules_syscon e_modules_systray e_modules_temperature e_modules_winlist e_modules_wizard exchange (multilib) nls pam spell udev -doc -e_modules_illume -e_modules_ofono (-hal) -static-libs"

do anyone can help me to get my session active?

axlalf

[MamyPlijadur]

Required kernel options for sys-fs/udisks:

Code: Select all

CONFIG_USB_SUSPEND=y
CONFIG_IDE=n

Hi! I followed strictly this tuto and recompile with this kernel options but I got a "Kernel panic! cannot open root device 'hda1' " which is IDE. I recompiled with:

Code: Select all

 CONFIG_IDE=y

and works all fine, even "Restart" and "Shut Down" from Log Out Dialog of Xfce4 which never worked since I taked refuge from Ubuntu to Gentoo

[SamuliSuominen]

Required kernel options for sys-fs/udisks:

Code: Select all

CONFIG_USB_SUSPEND=y
CONFIG_IDE=n

Hi! I followed strictly this tuto and recompile with this kernel options but I got a "Kernel panic! cannot open root device 'hda1' " which is IDE. I recompiled with:

Code: Select all

 CONFIG_IDE=y

and works all fine, even "Restart" and "Shut Down" from Log Out Dialog of Xfce4 which never worked since I taked refuge from Ubuntu to Gentoo

There should be NO /dev/hd* anymore, those are obsolete. Should be at /dev/sd* when using the new PATA (Parallel ATA) based drivers.
You just broke sys-fs/udisks and sys-fs/udev by setting CONFIG_IDE=y.

[gcyoung]

Followed the instructions and all works fine ....EXCEPT... No cd/dvdwriter. k3b needs hal and brasero alleges that it's writing but it just destroys the disks now.

Any suggestions for an alternative writer, I want to keep this setup as I use e16 and gnome-light which means my usb, dvds and cdroms open automatically in nautilus. Previously I had to mount or pmount.

[MamyPlijadur]

There should be NO /dev/hd* anymore, those are obsolete. Should be at /dev/sd* when using the new PATA (Parallel ATA) based drivers.
You just broke sys-fs/udisks and sys-fs/udev by setting CONFIG_IDE=y.

Thank you for swift response OK! I know that but fisrt time I've installed gentoo on this machine from rescuecd my hdd was named /dev/sda fine, but many things were wrong, then I re-installed from Gentoo install CD and I found at this time /dev/sda changed to /dev/hda by which mystery ?

I tried, with the CONFIG_IDE=n kernel, to change from 'root=/dev/hda1' to 'root=/dev/sda1' at boot time in the Grub command line, but nothing changed When I tried to restore CONFIG_IDE=y, all right worked and auto-mount CDROM & USB disks even Shut Down from Xfce4... Which disaster can appear now? Where can I find and install the new PATA drivers ?
Thanks for clearing my befuddled brain

[VoidMage]

It doesn't need to be sda1, the order might be different.
As for the proper drivers, see which are you using now and select equivalent from the CONFIG_ATA list.

As for k3b, it doesn't really need hal, just a version of solid, that doesn't use hal anymore.

[gcyoung]

I suspect that MamyPlijadur has checked the ATA/ATAPI/MFM/RLL item in his kernel config file. Only the
Device Drivers >Serial ATA and Parallel ATA drivers should be used to get "sdX" driver notation.

Apropos k3b and using solid, an "emerge pv solid" indicated the need for a bloated kde install of 54 new (unwanted) files to my beautiful, lean, kde free system. I then remembered xcdroast from earlier linux days and have now installed that to deal with my cd/dvd writing needs.

[MamyPlijadur]

SATA PATA drivers was compiled as modules which was not loaded at boot time, therefore the kernel cannot mount root fs if CONFIG_IDE is disabled. I've re-compiled ATA drivers in the kernel and set CONFIG_IDE=n. This work fine with all disks as /dev/sdx now.
Thanks for all, wonderful staff

[axlalf]

ok, i was quite desperate while writing that... i am sorry for that.

but i could appreciate some help here

[waterloo2005]

what is the use of the post ?
Can you explain it ?

Thanks

[|Quantum|]

If just found out you also need to be in the polkituser group:

Code: Select all

passwd -a «USER» polkituser

ATM Restart and Shutdown are still greyed out, though.

[SamuliSuominen]

If just found out you also need to be in the polkituser group:

Code: Select all

passwd -a «USER» polkituser

ATM Restart and Shutdown are still greyed out, though.

Wrong. There is no such group or need for it. Such group is a relic from old "policykit", not used by "polkit". You can safely remove the group from your system.

[Flurp]

I have been having problems with consolekit authorisation using Qingy with XFCE. It turns out that on my systems at least, if Qingy is using the DirectFB frontend and starts the X server on the tty that it is running on (the default setting) then the session is inactive.

Changing:

Code: Select all

x_server_tty = qingy_tty

to

Code: Select all

x_server_tty = unused_tty

in /etc/qingy/settings fixes it

I was pointed in the right direction by the current bug in DirectFB-1.4.9 which stopped Qingy using DirectFB - if Qingy is running from the console then everything works correctly anyway.

HTH