[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: SOLVED Re: dmesg reports connection of mass storage device but no kde pop-up nor device file created



Florian Kulzer wrote, on 02/04/08 03:42:
On Tue, Apr 01, 2008 at 07:59:36 -0500, Ron Johnson wrote:
On 04/01/08 04:11, Arthur Marsh wrote:
[snip]

If one shouldn't need to restart debian for the purging of
hal-device-manager to take effect, should I have run /etc/init.d/hal
restart ?
That seems reasonable...

When I see weird behavior of KDE with respect to devices (this happens
only very rarely), I do this:

- log out/close the KDE session
- restart udev
- restart dbus (which, among other things, restarts hal)
- log in/start KDE again

More generally speaking, you can use "checkrestart" from the
"debian-goodies" package to find out which services need to be restarted
after upgrades or other library-related changes to your system.


Thanks, I've just installed debian-goodies.

I filed a bug report on hal (#473755) that hal-device-manager should be listed as a "conflicts" item.

Regards,

Arthur.


Reply to: