Thunar-volman fails to recognize/mount any removable drive and media.
It was working perfectly well with Xfce 4.6, but not at all after upgrading
to 4.8.
This is the stdout after pluging in any removable drives or inserting removable
media:
thunar-volman: Unsupported USB device type.
thunar-volman: Unsupported USB device type.
thunar-volman: Unknown block device type.
thunar-volman: Could not detect the volume corresponding to the device.
-- System Information:
Debian Release: wheezy/sid
Architecture: i386 (i686)
Kernel: Linux 2.6.38.1 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages thunar-volman depends on:
ii exo-utils 0.6.0-3 Utility files for libexo
ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib
ii libexo-1-0 0.6.0-3 Library with extensions for Xfce
ii libglib2.0-0 2.28.6-1 The GLib library of C routines
ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface
ii libgudev-1.0-0 167-3 GObject-based wrapper library for
ii libnotify1 [libnotify1-gtk2.1 0.5.0-2 sends desktop notifications to a n
ii libpango1.0-0 1.28.3-6 Layout and rendering of internatio
ii libxfce4ui-1-0 4.8.0-2 widget library for Xfce
ii libxfce4util4 4.8.1-2 Utility functions library for Xfce
ii libxfconf-0-2 4.8.0-3 Client library for Xfce4 configure
ii thunar 1.2.1-5 File Manager for Xfce
thunar-volman recommends no packages.
thunar-volman suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Then you need to take care of running consolekit/policykit yourself and
be sure it's configured properly. Some help can be found in
README.Debian of xfce4 and xfce4-session but basically what you need is
to be sure in order to have a complete Xfce experience is:
* that Debian Xsession.d scripts are run (so they can setup the various
agent needed, like consolekit and stuff like that)
* that startxfce4 is run (and not directly xfce4-session) (so
xscreensaver, xrdb config etc. are properly set).
I don't know about rungetty so you'll have to adapt, but for people
logging in from console, the proper (and only, afaict) way is to:
* remove any .xinitrc
* add 'exec startxfce4' in .xsessionrc
* use startx (alone, without any argument)
In your case, it seems that rungetty will use startx so you just have to
check that you don't have any .xinitrc, that rungetty doesn't add any
arg and then put the correct line in .xsessionrc.
> Mounting from Thunar itself does not work, the devices don't even show up
> there.
Yup, I really think it's consolekit related, and that you don't have the
permissions. That's something you can check by using pkaction and
ck-list-sessions (in case it still doesn't work, please attach the
output of those commands in the bug report).
Regards,
--
Yves-Alexis
On Thu, Apr 21, 2011 at 07:57:56AM +0200, Yves-Alexis Perez wrote:
> On mer., 2011-04-20 at 21:56 +0200, Yves-Alexis Perez wrote:
> > How do you login? Is udisks installed and running?
>
> And does mounting/unmounting from Thunar itself work?
I don't use xdm/gdm etc. I use rungetty to invoke startx.
Udisks is installed and running, at least it seams like it is running because
it replys on dbus:
dbus-send --system \
> --print-reply \
> --dest=org.freedesktop.UDisks \
> /org/freedesktop/UDisks \
> org.freedesktop.DBus.Properties.Get \
> string:org.freedesktop.UDisks \
> string:DaemonVersion
method return sender=:1.15 -> dest=:1.14 reply_serial=2
variant string "1.0.2"
Mounting from Thunar itself does not work, the devices don't even show up
there.
Regards,
Sebastian
No idea about xdm, I wouldn't advise it. My reference test environments
are gdm (2.20) and pure console (with .xsessionrc and startx).
>
> Output from ck-listsessions:
> unix-user = '1000'
> realname = ''
> seat = 'Seat1'
> session-type = ''
> active = FALSE
> x11-display = ''
> x11-display-device = ''
> display-device = '/dev/tty1'
> remote-host-name = ''
> is-local = TRUE
> on-since = '2011-04-21T12:10:30.262757Z'
> login-session-id = ''
Here, your session is only a console session, not a graphical session,
and is marked as inactive. I'm not too sure about the xdm setup but it
might be worth installing the pam connector (libpam-ck-connector) and
retrying.
Pure console is what I prefer to use, xdm was just for testing purposes,
I've now tried gdm (see below).
> Here, your session is only a console session, not a graphical session,
> and is marked as inactive. I'm not too sure about the xdm setup but it
> might be worth installing the pam connector (libpam-ck-connector) and
> retrying.
libpam-ck-connector was already installed.
This is ck-list-sessions after booting with gdm:
unix-user = '1000'
realname = ''
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2011-04-21T13:12:30.160505Z'
login-session-id = ''
The ck-Session is now marked active and has x11-display properly set,
but behaviour/output from thunar/thunar-volman didn't change.
Out of desperation I also ran the X/Xfce session as root, still no difference.
Could it be that there's something else missing (e.g. thunar-volman dosn't
recommend or suggest udisks, should I file a seperate bug about that?)?
Regards,
Sebastian
Ok.
>
> > Here, your session is only a console session, not a graphical session,
> > and is marked as inactive. I'm not too sure about the xdm setup but it
> > might be worth installing the pam connector (libpam-ck-connector) and
> > retrying.
>
> libpam-ck-connector was already installed.
Ok.
>
> This is ck-list-sessions after booting with gdm:
> unix-user = '1000'
> realname = ''
> seat = 'Seat1'
> session-type = ''
> active = TRUE
> x11-display = ':0'
> x11-display-device = '/dev/tty7'
> display-device = ''
> remote-host-name = ''
> is-local = TRUE
> on-since = '2011-04-21T13:12:30.160505Z'
> login-session-id = ''
>
> The ck-Session is now marked active and has x11-display properly set,
Ok, that's a pre-requesite.
> but behaviour/output from thunar/thunar-volman didn't change.
Grmbl. What exactly is the result of trying to access a usb key or
something from Thunar?
>
> Out of desperation I also ran the X/Xfce session as root, still no difference.
Things are really starting to look fishy.
>
> Could it be that there's something else missing (e.g. thunar-volman dosn't
> recommend or suggest udisks, should I file a seperate bug about that?)?
Thunar already recommends: gvfs but it might recommends gvfs-bin too
(which will bring udisks).
Regards,
--
Yves-Alexis
*facedesk*
This bug can get closed now.
I didnt't have gvfs installed.
mea culpa
But:
A little update on documentation and dependencies could make it easier for
other users who will run into problems like that to figure out what's wrong
Thunar still tells (in /usr/share/doc/html) that it needs HAL for purposes
of removable media. udisks isnt't recommended by thunar, thunar-volman,
gvfs and also gvfs-bin (but gvfs-bin isn't nessecary for thunar-volman anyway).
The README.Debian of thunar says that you need gvfs, but I didn't find it,
because I looked for that kind of information in the docs of thunar-volman,
because this was the package I had trouble with; so thunar-volman could maybe
use a little Readme.Debian as well. Since Thunar can do it's job well without
gvfs, but thunar-volman can't do anything at all without it, it might not be
the worst idea to add it as "recommends" or hard dependency to thunar-volman,
and even maybe lower it for Thunar to "suggests".
Haha, no problem :)
> mea culpa
> But:
> A little update on documentation and dependencies could make it easier for
> other users who will run into problems like that to figure out what's wrong
> Thunar still tells (in /usr/share/doc/html) that it needs HAL for purposes
> of removable media. udisks isnt't recommended by thunar, thunar-volman,
> gvfs and also gvfs-bin (but gvfs-bin isn't nessecary for thunar-volman anyway).
Yeah, the upstream documentation is quite outdated :/ The problem with
gvfs is that it'll pull gconf and thus I'm not a huge fan of having it
forced onto every Xfce user.
> The README.Debian of thunar says that you need gvfs, but I didn't find it,
> because I looked for that kind of information in the docs of thunar-volman,
> because this was the package I had trouble with; so thunar-volman could maybe
> use a little Readme.Debian as well. Since Thunar can do it's job well without
> gvfs, but thunar-volman can't do anything at all without it, it might not be
> the worst idea to add it as "recommends" or hard dependency to thunar-volman,
> and even maybe lower it for Thunar to "suggests".
Yeah, the dependencies will need a bit more tuning, I think (and this
kind of bug helps for that, too).
Regards,
--
Yves-Alexis
Please provide similar infos then.
> Immediatly after a fresh boot removable drives are recognized and mounted,
> both from desktop and thunar but no longer after a new login of the xfce
> session.
Looks like a permission problem the second time you start Xfce.
> In the new session I get 'Failed to mount ..., Not Authorized' in desktop
> and thunar.
> I have udisks,gvfs and libpam-ck-connector installed!
Please provide the various info I asked Sebastian for.
Regards,
--
Yves-Alexis