Bug#623496: [Pkg-xfce-devel] Bug#623496: Bug#623496: thunar-volman: Fails to recognize removable drives
On mer., 2011-04-20 at 21:56 +0200, Yves-Alexis Perez wrote: On mer., 2011-04-20 at 20:12 +0200, Sebastian Dalfuß wrote: Package: thunar-volman Version: 0.6.0-3 Severity: grave Tags: sid Justification: renders package unusable 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. How do you login? Is udisks installed and running? And does mounting/unmounting from Thunar itself work? Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#623496: [Pkg-xfce-devel] Bug#623496: Bug#623496: thunar-volman: Fails to recognize removable drives
On jeu., 2011-04-21 at 10:41 +0200, Sebastian Dalfuß wrote: Hi, 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: 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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623496: [Pkg-xfce-devel] Bug#623496: Bug#623496: thunar-volman: Fails to recognize removable drives
Hi, 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 signature.asc Description: Digital signature
Bug#623496: [Pkg-xfce-devel] Bug#623496: Bug#623496: thunar-volman: Fails to recognize removable drives
Hi, I manually invoked startx with startxfce4 like you suggested, didn't make any difference. To verify the wy og login isn't the problem, I then used a default inittab and installed/used xdm to login. That didn't help either. 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 = '' Output from pkaction: org.freedesktop.consolekit.system.restart: description: Restart the system message: System policy prevents restarting the system vendor: vendor_url: icon: implicit any: no implicit inactive: no implicit active: yes org.freedesktop.consolekit.system.restart-multiple-users: description: Restart the system when multiple users are logged in message: System policy prevents restarting the system when other users are logged in vendor: vendor_url: icon: implicit any: no implicit inactive: no implicit active: auth_admin_keep org.freedesktop.consolekit.system.stop: description: Stop the system message: System policy prevents stopping the system vendor: vendor_url: icon: implicit any: no implicit inactive: no implicit active: yes org.freedesktop.consolekit.system.stop-multiple-users: description: Stop the system when multiple users are logged in message: System policy prevents stopping the system when other users are logged in vendor: vendor_url: icon: implicit any: no implicit inactive: no implicit active: auth_admin_keep org.freedesktop.policykit.exec: description: Run programs as another user message: Authentication is required to run a program as another user vendor:The PolicyKit Project vendor_url:http://hal.freedesktop.org/docs/PolicyKit/ icon: implicit any: auth_admin implicit inactive: auth_admin implicit active: auth_admin org.freedesktop.policykit.lockdown: description: Configure lock down for an action message: Authentication is required to configure lock down policy vendor:The PolicyKit Project vendor_url:http://hal.freedesktop.org/docs/PolicyKit/ icon: implicit any: no implicit inactive: no implicit active: auth_admin annotation:org.freedesktop.policykit.exec.path - /usr/bin/pklalockdown org.freedesktop.udisks.cancel-job-others: description: Cancel a job initiated by another user message: Authentication is required to cancel a job initiated by another user vendor:The udisks Project vendor_url:http://udisks.freedesktop.org/ icon: drive-removable-media implicit any: no implicit inactive: no implicit active: auth_admin org.freedesktop.udisks.change: description: Modify a device message: Authentication is required to modify the device vendor:The udisks Project vendor_url:http://udisks.freedesktop.org/ icon: drive-removable-media implicit any: no implicit inactive: no implicit active: yes org.freedesktop.udisks.change-system-internal: description: Modify a system-internal device message: Authentication is required to modify the device vendor:The udisks Project vendor_url:http://udisks.freedesktop.org/ icon: drive-removable-media implicit any: no implicit inactive: no implicit active: auth_admin_keep org.freedesktop.udisks.drive-ata-smart-refresh: description: Refresh ATA SMART data message: Authentication is required to refresh ATA SMART data vendor:The udisks Project vendor_url:http://udisks.freedesktop.org/ icon: drive-removable-media implicit any: no implicit inactive: no implicit active: yes org.freedesktop.udisks.drive-ata-smart-retrieve-historical-data: description: Retrieve historical ATA SMART data message: Authentication is required to retrieve historical ATA SMART data vendor:The udisks Project vendor_url:http://udisks.freedesktop.org/ icon: drive-removable-media implicit any: no implicit inactive: no implicit active: yes org.freedesktop.udisks.drive-ata-smart-selftest: description: Run ATA SMART Self Tests message: Authentication is required to run ATA SMART self tests vendor:The udisks Project vendor_url:http://udisks.freedesktop.org/
Bug#623496: [Pkg-xfce-devel] Bug#623496: Bug#623496: thunar-volman: Fails to recognize removable drives
severity 623496 minor thanks On jeu., 2011-04-21 at 14:32 +0200, Sebastian Dalfuß wrote: Hi, I manually invoked startx with startxfce4 like you suggested, didn't make any difference. To verify the wy og login isn't the problem, I then used a default inittab and installed/used xdm to login. That didn't help either. 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. Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
