Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12346 - pmount: pmount-hal doesn't mount volumes and returns an error

Attached to Project: Arch Linux
Opened by Filip Wojciechowski (fwojciec) - Thursday, 04 December 2008, 21:48 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 06 March 2009, 13:56 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Problem:
When trying to mount a volume with "pmount-hal" command -- it fails with the following error:

$ pmount-hal /dev/sdc1
process 7690: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details.
Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection.
D-Bus not built with -rdynamic so unable to print a backtrace
Aborted

The volume is not mounted.

The regular "pmount" command works fine, though.

Fix:
I built a vanilla version of pmount 0.9.18 package and the problem disappeared.

Additional info:
* package version(s)
pmount 0.9.17-1
(I have testing enabled, in case it makes a difference)

Steps to reproduce:
Try to mount a volume with pmount-hal command.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 06 March 2009, 13:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.9.19-1
Comment by Jan de Groot (JGC) - Friday, 05 December 2008, 11:31 GMT
Is this with the hal package from testing?
Comment by Filip Wojciechowski (fwojciec) - Friday, 05 December 2008, 16:02 GMT
Yes -- I have testing enabled and the system is fully up to date.
Comment by Jan de Groot (JGC) - Friday, 05 December 2008, 17:58 GMT
What's the output of ck-list-sessions?
Comment by Filip Wojciechowski (fwojciec) - Friday, 05 December 2008, 19:49 GMT
$ ck-list-sessions
Session8:
unix-user = '1000'
realname = ''
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ''
x11-display-device = ''
display-device = '/dev/vc/1'
remote-host-name = ''
is-local = TRUE
on-since = '2008-12-05T05:50:52.186752Z'
login-session-id = ''
idle-since-hint = '2008-12-05T05:51:22.004462Z'
Session9:
unix-user = '1000'
realname = ''
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/tty4'
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2008-12-05T05:50:54.101332Z'
login-session-id = ''

---
One more thing: I'm using a custom kernel -- I don't think this makes any difference, since pmount 0.9.18 works without any issues, but just in case I'm attaching kernel configuration as well.
(application/octet-stream)    kernelconfig.gz (14.1 KiB)
Comment by Jan de Groot (JGC) - Friday, 05 December 2008, 20:24 GMT
Ah, I was thinking about a duplicate of the infamous hal/policykit/consolekit issues some of our users are having here. Didn't take notice of your message about 0.9.18 in the initial bugrepor.
Comment by hamelg (hamelg) - Saturday, 06 December 2008, 18:16 GMT
Same thing here.
I'm running core/kernel26 2.6.27.7-1.
Any possible workaround ?
Comment by hamelg (hamelg) - Saturday, 06 December 2008, 21:04 GMT
Same thing here.
I'm running core/kernel26 2.6.27.7-1.
Any possible workaround ?
Comment by Filip Wojciechowski (fwojciec) - Saturday, 06 December 2008, 21:49 GMT
The workaround, in my case, was to build pmount 0.9.18 using ABS and use that.

Loading...