promeneur wrote:a last idea : iceauth and xauth ?
what are these components ?
Nope.
From their spec files:
The iceauth program is used to edit and display the authorization information used in connecting with ICE
The xauth program is used to edit and display the authorization information used in connecting to the X server. This program is usually used to extract authorization records from one machine and merge them in on another (as is the case when using remote logins or granting access to other users)
They have nothing to do directly with KDE and access to storage devices, AFAICT...
another idea : a version dbus pb ?
Perhaps, but if you are with 2010.3 you already have the latest dbus we backported (the same I'm using on the build machine) so I cannot see how it could be involved.
In a such case, however, you should also find error messages in /var/log/messages or dmesg or .xsessio-errors (the string "org.freedesktop.hal.storage.xxx" I cited above is indeed an example of DBus related message destination: you should find similar strings scattered in your logs...).
is there a way to trace messages from kde device notifier as wjen we launch in konsole an app ?
You should play with the kdebugdialog utility: it allows you to enable/disable selectively debug messages from KDE components and installed programs...
It is not immediately clear, however, what debug messages enable (and there is a lot of them...):
you can only go by a trial and error process, I fear...
Looking at the list displayed on my PC, I would try:
180 kdecore / 297 kdeui (KnotificationRestrictions) / 297 kdeui (KNotification) / 920 Solid (kdelibs) / 1205 kdesud / 1206 kdesu / 1440 Solid (HAL) / Polkit1AuthAgent / Storage Debug / dolphin /kdesu (kdelibs) / policykit1-kde
After reloading KDE and another test there is still nothing in your log file?
And, before trying this I would also make sure that is not a configuration problem of the Device Notifier: does the problem happen also with a fresh created test user?
If so you should try to remove the old configuration file (I don't know where to look for it, though).
GvM