Some more information about this problem; "adept" downloaded some upgrades this morning. Among them were some 'hal' files (hald, hal-device-manager, and a couple of others). After installing these updates, I rebooted my laptop and tried to pass the --retain-privileges argument to hald (e.g. sudo hald --daemon=yes --retain-privileges). The result was that the hald still barked at me for using the --retain-privileges argument. BUT, the hald man page reports that --retain-privileges IS a valid argument, however running 'hald --help' reports that --retain-privileges is NOT a valid argument. Obviously there's something going on here that needs to be fixed. If I go to http://freedesktop.org/wiki/Software_2fHalTraces, I should be able to use the --retain-privileges argument. My version of hald is 0.5.7. Anyway, it looks like a bug. Someone reported bug #44770 against hald in the ubuntu bug tracking system and it's new, only a few days old. It's very similar to what I've found. There's a comment in the bug report, from a developer or maintainer, that says the --retain-privileges was never valid for the ubuntu hal...oh well.... -Chuck Chuck Noyes wrote:
Hi All
I upgraded by laptop from 'breezy' to 'dapper'. It looks like the hald does not accept the --retain-privileges argument, even though the upgrade tool added it to the /etc/default/hal file. Now the hald won't start. Also, my USB thumb drives won't automount. I'm thinking it may be related to the hald problem.
If I run 'sudo hald --retain-privileges restart', the command fails with the help screen for the command.
Has anyone else out there seen this problem? Anyone got a fix?
I can always comment out the 'DAEMON-OPT=--retain-privileges' line in the /etc/default/hal file, so the hald starts without error, but the USB drives still don't automount.
Thanks, -Chuck _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug