You are not logged in.

#1 2011-01-26 16:32:10

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,080

udisksvm GUI UDisks wrapper without writing udev rules

The scripts udisksvm and traydvm are now written in python and use the gobject introspection approach.

Here is the link in AUR:
https://aur.archlinux.org/packages/udisksvm/

Here is the README content for explanations:

The 'udisksvm' and 'traydvm' scripts operate between udisks2 and a window
manager with a mouse and a system tray available. They listen to events and act
accordingly with removable media.
The 'traydvm' GUI utility displays a systray icon showing a plugged-in device,
with a right-click menu to perform actions on it.
The icon represents a file system/partition on the disk; so if there are
several partitions, there are one icon for each file system on them.
With a MBR partition table, only primary partitions are managed presently.

udisks2------>udisksvm----------->traydvm--------->systray icon
                 |                                     |
                 |                                     |
                 V                                     V
           (automounting)                       right-click menu
       (non optical disks only)                        |
                                                       |
                                                       V
                                            commands to device media
                                                       |
                                                       |
                                                       V
                                                  notification

The automounting feature is disabled by default.
It can be enabled for non-optical disks with the '-a', '--auto' command line
option.
The old '-n', '--noauto' option is still recognized but not used anymore.

A notification pops up after a 'Mount' or 'Unmount' action  by the right-click
menu.
This feature is enabled by default, and can be disabled by the '-s',
'--silent' command line option.

In its present form there are only three actions : 'Mount', 'Unmount', 'Eject'
The 'Mount' action operates on data optical disks, and on block devices with
plain partitions, ie not a container of other partitions or not contained in
another partition.
The 'Eject' action is only activated for an unmounted optical disk.
And only one CD/DVD drive at /dev/sr0 is considered.

The tooltip when the mouse pointer hovers over the icon gives the device name,
the label or the UUID and the state of the device, with the mountpoint, normally
in /run/media/<user_name>, where the mounted media can be accessed in a file
manager.

The 'traydvm' utility has no configuration file: the popup menu and the actions
are predefined in the script.

The 'udisksvm' and 'traydvm' scripts use the UDisks2 DBus API.
If used in a systemd configuration (default in Arch Linux) they also need to
be ran in an active systemd-logind session:

        loginctl show-session $XDG_SESSION_ID

should have a line with 'Active=yes'

For example, in Openbox and Tint2 with systray enabled, only add this line in
$HOME/.config/openbox/autostart to launch udisksvm with default options and
without text output:

        udisksvm >/dev/null &

To see output and errors from the script, run it in a console without the
redirection to /dev/null;
for more verbosity, run it with the '-d' or '--debug' option.

The file system types and mount options are controlled by UDisks2.
UDisks2 is rather restrictive presently:
'flush' is available for 'vfat' file system,
'sync' for 'ext2' file system.
These options are included in the scripts.

The traydvm script ignores all changes made to partitions or file
system types or label, while it is running; if such changes are made
on a device, while traydvm is running on it, the device has first to be
plugged out/in to re-launch traydvm on it.

These scripts can be extended to develop a more complete management of
removable media in a GUI oriented approach.
But they can simply be used as is, to automount, unmount or re-mount a USB
memory stick or an external disk, or for accessing data on optical CD/DVD
disks, only with mouse clicks.

They can also be used to only show system tray icons, with other tools to do
automounting or manual mounting/unmounting.

Edit for up to date infos with the 2.3.0 release.

See also other comments at the #58 post

Last edited by berbae (2013-12-18 15:20:57)

Offline

#2 2011-01-26 16:46:44

Inxsible
Forum Fellow
From: Chicago
Registered: 2008-06-09
Posts: 9,059

Re: udisksvm GUI UDisks wrapper without writing udev rules

Very nice. I'll try it out later tonight.

If you have the time, you should also create a wiki page and then link that page under Automounting on the Udev page or under the sub-heading "Mount CDs"

https://wiki.archlinux.org/index.php/Ud … SB_devices


That way, users will have yet another option to automount stuff including CD/DVDs


Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

Offline

#3 2011-01-26 19:23:41

IgnorantGuru
Member
Registered: 2009-11-09
Posts: 640
Website

Re: udisksvm GUI UDisks wrapper without writing udev rules

Thanks for sharing - that's some nice coding.  I just started writing a script to use udisks for this, minus the tray manager.  I like the way you handled the monitoring - very efficient.

Last edited by IgnorantGuru (2011-01-27 22:19:47)

Offline

#4 2011-01-27 12:37:17

Dieter@be
Forum Fellow
From: Belgium
Registered: 2006-11-05
Posts: 1,958
Website

Re: udisksvm GUI UDisks wrapper without writing udev rules

how does this compare to udiskie?


< Daenyth> and he works prolifically
4 8 15 16 23 42

Offline

#5 2011-01-27 23:01:41

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,080

Re: udisksvm GUI UDisks wrapper without writing udev rules

Dieter@be wrote:

how does this compare to udiskie?

The accent of udisksvm is on the traydevice usage for its icons in the systray and its integrated right-click menu which is entirely configurable.

BTW the right-click menu can be extended to launch other actions than mounting/unmounting on devices, adding entries in the default.xml configuration file with other associated actions.

But I admit that the xml format of the configuration file is not so practical to use than another scripting langage.

But it can be done to integrate as many choices of actions as wished by the user.

Diversity of solutions is better than only one, so each one chooses what s/he likes.

Thanks to Inxsible, IgnorantGuru, falconindy for your nice post.

Last edited by berbae (2011-01-27 23:14:08)

Offline

#6 2011-01-27 23:41:09

IgnorantGuru
Member
Registered: 2009-11-09
Posts: 640
Website

Re: udisksvm GUI UDisks wrapper without writing udev rules

@Dieter@be
One other advantage to this approach over udiskie is that it is written in bash - very lightweight, whereas udiskie is python.  If you have python loaded for other purposes all the time, then it doesn't matter much.  But if you're loading python just to run a little background utility, that's a lot of resources.  That was why I didn't go with udiskie.

@berbae
I encountered one problem when testing your code.  To get it to work I had to change

devpath=${devpath/#*\//\/dev\/}

to

devpath="/dev/${devpath##*/}"

or else $devpath was escaped as "\/dev\/" and wouldn't pass the [ -e $devpath ] test.

Also, as it is it tries to mount blank media, which you might want to disregard, although I suppose it doesn't matter.

Offline

#7 2011-01-28 16:34:30

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,080

Re: udisksvm GUI UDisks wrapper without writing udev rules

Thanks IgnorantGuru for the tests you made and your feedback.

devpath="/org/freedesktop/UDisks/devices/sdb1"
devpath=${devpath/#*\//\/dev\/}
echo $devpath
/dev/sdb1

So on my machine the code I use works as expected (if not so, I would have changed it).
I use bash 4.1.009-3 .
It's wierd it doesn't work for you.

Concerning the blank optical disks, I modified the udisksvm script and the default.xml file to check that parameter now.

I still call traydevice for a blank optical disk, but there is no attempt to mount it now.
The traydevice menu offers only the Eject optical disk choice for a blank optical disk, but other choices could be added for other actions on it.
That's why I still call traydevice.

I precise again that this automounting method is GUI oriented for its usage, it is destined to mouse click adepts when in use.
But it is intended to be enriched by editing (in CLI or other) especially the default.xml file, to add other choices of actions on specific devices and conditions (all the parameters of udisks are accessible in it --see the link at the top of the file--, and more complex conditions can be elaborated)

The udisksvm script can be changed to modify the mount options and to add file system types with specific mount options.

It is rather a starting point or a blueprint opened to changes, to adapt to the wishes and choices of the users.
I present it not as a entirely ready-made solution but a method to get exactly what is wanted, freedom of choice.

Last edited by berbae (2011-01-28 16:36:18)

Offline

#8 2011-01-29 02:11:17

IgnorantGuru
Member
Registered: 2009-11-09
Posts: 640
Website

Re: udisksvm GUI UDisks wrapper without writing udev rules

berbae wrote:

So on my machine the code I use works as expected (if not so, I would have changed it).
I use bash 4.1.009-3 .
It's wierd it doesn't work for you.

I know I put an echo in there to figure out the problem and it returned "\/dev\/sr0", which is why I changed it.  But now I can't reproduce it, so it is weird.  Possible human error.  smile

I think your script is a great starting point for people looking to write their own - nice design, readable, and short.  And I agree more choices are better.  Thanks again.

By the way, do you recommend SIGHUP be added to the trap, or is it better not?

Last edited by IgnorantGuru (2011-01-29 02:13:03)

Offline

#9 2011-03-09 18:23:45

CPUnltd
Member
From: Milwaukee, WI
Registered: 2009-12-05
Posts: 470
Website

Re: udisksvm GUI UDisks wrapper without writing udev rules

berbae wrote:

The script called udisksvm uses the udisks command and the traydevice package in AUR.

...
In $HOME/.config/openbox/autostart.sh there are these lines, among other commands:

# D-bus
if which dbus-launch >/dev/null 2>&1 && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
    eval $(dbus-launch --sh-syntax --exit-with-session)
fi

if ! pgrep -lf "udisks-daemon: polling /dev/sr0"; then
    udisks --poll-for-media /dev/sr0
fi

udisksvm >/dev/null &

...

First, does HAL have to be turned off for this to work?

Second, the code above... is that all necessary for invoking udisksvm, or can I just run it with 'udisksvm &' added to .xinitrc?

Been looking for something like this, as it is a GREAT addition to a standalone Compiz desktop!!! big_smile


Help grow the dev population... have your tech trained and certified!

Offline

#10 2011-03-09 22:57:55

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,080

Re: udisksvm GUI UDisks wrapper without writing udev rules

CPUnltd wrote:

First, does HAL have to be turned off for this to work?

Yes hal will conflict with udisks for the device detection.

CPUnltd wrote:

Second, the code above... is that all necessary for invoking udisksvm, or can I just run it with 'udisksvm &' added to .xinitrc?

If a session bus instance is already started at the start of Compiz (with 'exec ck-launch-session dbus-launch command'), the D-bus part of the shown code is not required.

The 'udisks --poll-for-media /dev/sr0' is required to detect insertion of optical media.

The 'udisksvm >/dev/null &' can be run from .xinitrc after the start of Compiz.
(the redirection to /dev/null prevent text outputs when used in daemon mode).
But in this case, take care that the 'exec command' format should be the last command in .xinitrc. Nothing else after it is executed.
You can try these lines in .xinitrc :

(sleep 30 && exec udisksvm >/dev/null) &
exec ck-launch-session dbus-launch command

I don't know if Compiz has the equivalent of the autostart.sh script in Openbox. If so it is preferable to use that instead, to be sure commands run after the start of Compiz.

Yes I think it's nice to see systray icons of devices and to operate on them with mouse clicks only.
That's the reason of this script along with automounting.

Last edited by berbae (2011-03-11 15:44:39)

Offline

#11 2011-03-12 01:59:35

CPUnltd
Member
From: Milwaukee, WI
Registered: 2009-12-05
Posts: 470
Website

Re: udisksvm GUI UDisks wrapper without writing udev rules

ok, so if I understand this correctly... in the example you used above:

(sleep 30 && exec udisksvm >/dev/null) &
exec ck-launch-session dbus-launch command

I don't need the DBUS portion of the code from the original post because of the [exec ck-launch dbus-launch] portion of .xinitrc (or any script that is the last thing to be executed at startup).

still wrapping my head around scripting and the nuances that are part of the process, so please bare with my noob questions... tongue


Help grow the dev population... have your tech trained and certified!

Offline

#12 2011-03-12 16:13:46

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,080

Re: udisksvm GUI UDisks wrapper without writing udev rules

Yes, in fact I removed now the D-bus part in my autostart.sh and I have in .xinitrc :

exec ck-launch-session dbus-launch openbox-session

In autostart.sh, I have :

# Detection of insertion of an optical disk
if ! pgrep -lf "udisks-daemon: polling /dev/sr0"; then
    udisks --poll-for-media /dev/sr0
fi

udisksvm >/dev/null &

As long as a ConsoleKit session is opened (ck-launch-session) and a session dbus instance is started (dbus-launch) at the start of the WM, udisks and udisksvm should work correctly.

As apparently you don't use an autostart.sh script for Compiz, you need to write everything in your .xinitrc file.

If you don't have or use optical medias, you don't need the udisks polling command. But if you want insertion detection of CD/DVD you need it.
So in your .xinitrc file you can try these lines (I have not tested that as I use Openbox WM) :

# Detection of insertion of an optical disk
if ! pgrep -lf "udisks-daemon: polling /dev/sr0"; then
    udisks --poll-for-media /dev/sr0
fi

(sleep 30 && exec udisksvm >/dev/null) &
exec ck-launch-session dbus-launch command-to-launch-Compiz

You spoke of a script to be the last thing to be executed at startup, can you precise that point ?

Offline

#13 2011-03-12 16:57:53

CPUnltd
Member
From: Milwaukee, WI
Registered: 2009-12-05
Posts: 470
Website

Re: udisksvm GUI UDisks wrapper without writing udev rules

the script I spoke of is for use with SLiM login manager.  The script allows me to choose my WM/DE by hitting F1 before I log in and that scrolls through the list of WMs/DEs I have told SLiM that I have installed.  Once I select one, the script is called by .xinitrc, detects my selection and starts the WM/DE of my choice.  THAT is what I was talking about in my last post.

What I ended up doing for myself (since all I really use now is custom WMs) is make a script that I called "udisk-mount" and placed it in /usr/bin as an executable, then added THAT to my custom WM scripts (so that the scripts stay simple and clean) which are called by SLiM's script when I choose my WM.  I could put it in .xinitrc, but I think it would conflict with the mounting features of the other DEs I use (e17 and XFCE)... even if it didn't, I don't think it would be necessary to have 2 programs running at once that handled disk mounting.  So I only added it where I need it. 

THANKS for this, as it is exactly what I needed to complete my custom WMs! big_smile  It's also a nice touch to have the mount point/name show with the mouseover... very nice!


Help grow the dev population... have your tech trained and certified!

Offline

#14 2011-04-18 02:45:11

jaydoc
Member
From: Chennai/Birmingham,AL
Registered: 2008-12-30
Posts: 86

Re: udisksvm GUI UDisks wrapper without writing udev rules

Hi there

I am using openbox, and using .xinitrc with exec ck-launch-session openbox-session to launch it using startx command. I have dbus added to modules in rc.conf and added

# D-bus
if which dbus-launch >/dev/null 2>&1 && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
    eval $(dbus-launch --sh-syntax --exit-with-session)
fi

if ! pgrep -lf "udisks-daemon: polling /dev/sr0"; then
    udisks --poll-for-media /dev/sr0
fi

udisksvm >/dev/null &

added to .config/openbox/autostart.sh

I also have installed both packages from the AUR. Still when I insert an USB drive, i cannot see it being mounted nor is there any tray icon.

Any idea what I have done wrong..?

Thanks


It takes a very unusual mind to undertake the analysis of the obvious - A N Whitehead

Offline

#15 2011-04-18 06:05:22

CPUnltd
Member
From: Milwaukee, WI
Registered: 2009-12-05
Posts: 470
Website

Re: udisksvm GUI UDisks wrapper without writing udev rules

well, the way I did it was to take the code and put it in it's own script named "udisk-mount"... dropped that in /usr/bin, did a  chmod 755 and added it (udisk-mount &) to my custom desktop script (running compiz standalone with cairo-dock) which is executed by .xinitrc... but my setup is slightly elaborate because of my custom desktop.  I don't recall being able to ever get it to run by just putting it in .xinitrc... so I'd suggest making it into it's own script, making it executable and having .xinitrc call the script itself.  Works flawlessly for me on my laptop and desktop.


Help grow the dev population... have your tech trained and certified!

Offline

#16 2011-04-18 09:45:55

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,080

Re: udisksvm GUI UDisks wrapper without writing udev rules

jaydoc wrote:

I also have installed both packages from the AUR. Still when I insert an USB drive, i cannot see it being mounted nor is there any tray icon.

Any idea what I have done wrong..?

From the README file:

----------------------------------------------------------------------------------------------------------------------
BEFORE USING THE SCRIPT the configuration file for traydevice MUST BE COPIED INTO $HOME/.config/traydevice directory :

        install -D -m 644 /usr/share/udisksvm/default.xml $HOME/.config/traydevice/default.xml

----------------------------------------------------------------------------------------------------------------------

Have you done that ?
Because traydevice seeks a default configuration file in $HOME/.config/traydevice/ not in /usr/share/udisksvm/

CPUnltd wrote:

I don't recall being able to ever get it to run by just putting it in .xinitrc...

There is no problem to use it like that on my machine, but I use a standard desktop only, not a 'custom' one.

Edit: I answered too quickly to CPUnltd, see following post, sorry.

Last edited by berbae (2011-04-18 12:41:15)

Offline

#17 2011-04-18 12:38:59

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,080

Re: udisksvm GUI UDisks wrapper without writing udev rules

Edit from my preceding remark to CPUnltd :

In fact I don't run udisksvm from .xinitrc but from inside the $HOME/.config/openbox/autostart.sh script.

I think it is important to run it after the 'exec ck-launch-session dbus-launch openbox-session' command in .xinitrc script.

And, as nothing can be launched after the 'exec ...' command, a simple way to run it at the right time is to use the autostart.sh script for Openbox, or an equivalent file for another WM.

I have no problem using the script in that manner.

Offline

#18 2011-05-14 04:39:49

alleyoopster
Member
From: Cape Town
Registered: 2006-11-19
Posts: 92

Re: udisksvm GUI UDisks wrapper without writing udev rules

Thanks berbae, works very well. I've been looking for something like this.

Is there a way of having the device volume label or the mount path reflected in the icons tooltips rather than the unhelpful uuid currently displayed?

Last edited by alleyoopster (2011-05-14 04:48:49)

Offline

#19 2011-05-14 05:18:55

CPUnltd
Member
From: Milwaukee, WI
Registered: 2009-12-05
Posts: 470
Website

Re: udisksvm GUI UDisks wrapper without writing udev rules

curious, berbae... why do you feel it's so important to run it AFTER the WM/DE is already up and running? (and for a custom DE, would it not suffice to put it at the back end of a script initiating all the parts/pieces of the 'custom' desktop, or is that not quite a good enough equivelant?)


Help grow the dev population... have your tech trained and certified!

Offline

#20 2011-05-14 15:45:05

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,080

Re: udisksvm GUI UDisks wrapper without writing udev rules

alleyoopster wrote:

Is there a way of having the device volume label or the mount path reflected in the icons tooltips rather than the unhelpful uuid currently displayed?

The "DeviceMountPaths" property is an array of strings rather than a single string.
So if I use in default.xml :

      <tooltip executable="/bin/echo"> 
        <arg>-n</arg>
        <ref>DeviceMountPaths</ref>
      </tooltip>

I get a wrong format of text.
Initially I used a script named "echo-mount" instead of "/bin/echo" to reformat the output of the string array:

#!/bin/bash
# echo-mount script
MOUNTPATH=$(echo $1 |cut -d \' -f 2)
echo -n $MOUNTPATH

That gives something like /dev/sdb1 as tooltip text.
But I removed that to have something simpler.

Concerning the "IdLabel" property, it is not always there; if no label is set, the string is empty.
So I chose to use the "IdUuid" property which should be always available and is a single string.
It seemed easier to use and it is also the name of the folder in /media where udisks mounts the device.

But the default.xml configuration file could surely be modified to show the Label when it is available, something like :

    <icon icon="gtk.STOCK_HARDDISK">
      <displayed_if>
       <and>
        <match key="DeviceIsPartition" bool="true"/>
        <match key="DeviceIsMounted" bool="true"/>
        <not>
         <match key="IdLabel" string=""/>
        </not>
       </and>
      </displayed_if>
      <!--
    Tooltip text is "IdLabel" when it is mounted with a label.
      -->
      <tooltip executable="/bin/echo"> 
        <arg>-n</arg>
        <ref>IdLabel</ref>
      </tooltip>
    </icon>
    <icon icon="gtk.STOCK_HARDDISK">
      <displayed_if>
       <and>
        <match key="DeviceIsPartition" bool="true"/>
        <match key="DeviceIsMounted" bool="true"/>
        <match key="IdLabel" string=""/>
       </and>
      </displayed_if>
      <!--
    Tooltip text is "IdUuid" when it is mounted without a label
      -->
      <tooltip executable="/bin/echo"> 
        <arg>-n</arg>
        <ref>IdUuid</ref>
      </tooltip>
    </icon>

I didn't test it yet on my machine.
But if you test it, can you tell me please if it works as expected ?
So I could incoporate the change more quickly in the AUR package.
Thanks for your contribution.

Last edited by berbae (2011-05-14 15:46:53)

Offline

#21 2011-05-15 16:45:06

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,080

Re: udisksvm GUI UDisks wrapper without writing udev rules

I release udisksvm 1.2 with the preceding post modifications, to use the Label name, if available, in the tooltip text.
It's better like that, because when a Label is set, udisks will mount the device in /media/Label not /media/Uuid
So the tooltip now always gives where the device is really mounted in /media.

I also now use the -c option of traydevice to fetch the configuration file, which is now :

/usr/share/udisksvm/udisksvm.xml

So there is no need to copy one file to $HOME/.config/traydevice as before.
And so no risk to forget to do that.

To modify it, it is only writable as root, and, if changed,  it will be backed up by pacman during an update.

Offline

#22 2011-05-15 16:48:00

alleyoopster
Member
From: Cape Town
Registered: 2006-11-19
Posts: 92

Re: udisksvm GUI UDisks wrapper without writing udev rules

That's great! thanks berbae

Offline

#23 2011-05-15 17:29:03

CPUnltd
Member
From: Milwaukee, WI
Registered: 2009-12-05
Posts: 470
Website

Re: udisksvm GUI UDisks wrapper without writing udev rules

very nice!


Help grow the dev population... have your tech trained and certified!

Offline

#24 2011-06-24 08:35:56

swanson
Member
From: Sweden
Registered: 2011-02-05
Posts: 759

Re: udisksvm GUI UDisks wrapper without writing udev rules

I've tried everything to make it function at login time;
(sleep 30 && udisksvm > /dev/null & ) in .xinitrc with exec ck-launch-session openbox-session
Also all the above recommenden code in separate script started the same way from .xinitrc.
I've tried the code from autostart.sh. The script IS started as seen with ps aux. But not working.

nemo      1870  0.0  0.2   6324  1396 pts/0    S    10:40   0:00 /bin/bash /usr/bin/udisksvm
nemo      1871  0.0  0.3   7296  1564 pts/0    S    10:40   0:00 udisks --monitor
root      1947  0.1  0.6  15392  3216 ?        Sl   10:41   0:00 /usr/lib/udisks/udisks-daemon
root      1948  0.0  0.1   5856   668 ?        S    10:41   0:00 udisks-daemon: polling /dev/sdb /dev/sd

By the first install tests I did I started udisksvm from terminal and it worked! Automounting and traydevice in fbpanel and all! If I start just traydevice it pops up in fbpanel with menu, but mounting doesn't work.

DEBUG:Executing:['/bin/echo', '-n', 'KINGSTON']
DEBUG:Result:(0, ('KINGSTON', ''))
DEBUG:Executing:['/usr/bin/udisks', '--mount', '/dev/sdc1']
DEBUG:Result:(0, ('Mount failed: Not Authorized\n', '')

I'm stumped but really keen to get it working since this is a clean install on an Acer netbook with 512MB ram and 8GB disk. Thunar is nice but gvfs would be nice to avoid on this machine.

Offline

#25 2011-06-24 21:55:46

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,080

Re: udisksvm GUI UDisks wrapper without writing udev rules

Do you have a session dbus instance launched with openbox ?

You should have something like that as running processes :

berbae    1738  1654  0 10:28 tty1     00:00:00 -bash
berbae    1745  1738  0 10:28 tty1     00:00:00 /bin/sh /usr/bin/startx
berbae    1762  1745  0 10:28 tty1     00:00:00 xinit /home/berbae/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth /tmp/serverauth.kmpfc4
root      1763  1762  0 10:28 tty7     00:05:18 /usr/bin/X -nolisten tcp :0 -auth /tmp/serverauth.kmpfc4LoDZ
berbae    1768  1762  0 10:28 tty1     00:00:00 ck-launch-session dbus-launch openbox-session
berbae    1777  1768  0 10:28 tty1     00:00:02 /usr/bin/openbox
berbae    1781     1  0 10:28 ?        00:00:06 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
root      1790     1  0 10:28 ?        00:00:00 /usr/lib/udisks/udisks-daemon
root      1791  1790  0 10:28 ?        00:00:01 udisks-daemon: polling /dev/sr0
berbae    1797  1777  0 10:28 tty1     00:00:00 /bin/bash /usr/bin/udisksvm
berbae    1815  1797  0 10:28 tty1     00:00:00 udisks --monitor

Both a console kit session and a dbus instance session are required there.

Offline

Board footer

Powered by FluxBB