Comment 15 for bug 387161

Hello,

I think that the problem is not caused by the executable /usr/lib/devicekit-disks/devkit-disks-daemon. Here is why:

I am now using jaunty, but I tried to generate the trace like Martin Pitt suggested. So I temporarily added the karmic repositories to sources.list and installed these packages:
[INSTALL, DEPENDENCIES] libatasmart0
[INSTALL, DEPENDENCIES] libeggdbus-1-0
[INSTALL, DEPENDENCIES] libgudev-1.0-0
[INSTALL, DEPENDENCIES] libparted1.8-12
[INSTALL, DEPENDENCIES] libpolkit-backend-1-0
[INSTALL, DEPENDENCIES] libpolkit-gobject-1-0
[INSTALL, DEPENDENCIES] libsgutils2-2
[INSTALL] devicekit-disks

And I tried to run /usr/lib/devicekit-disks/devkit-disks-daemon, but there was this error:

/usr/lib/devicekit-disks/devkit-disks-daemon: symbol lookup error: /usr/lib/libgudev-1.0.so.0: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype

So, if I understand correctly, something prevents this application from start and it is not possible to start it until the problem is resolved.

But when I tried to connect my USB hard drive, there were again the same errors as there were with karmic and working devkit-disks-daemon.

So, I assume that this means that this executable is not the cause of the errors - just because it was not running when the problem appeared.

And I am sorry for no trace. The 'undefined symbol' error might be a problem with library versions or something like that. But I don't know which library to look at and to eventually upgrade / downgrade in order to make it working. And I am not that concerned to install karmic again, I am really sorry.

Have a nice day!