Just in case it's a useful point in the graph; I just found this bug
report having got the exact same error message in a fresh new install
of Etch. In between the clean install and getting the error message,
I'd taken the machine apart and moved some drives around. Then I
double-clicked in Nautilus on a new icon that had shown up for a drive
I'd added (a single, ext3-formatted partition-disk that showed up as
"111.8 GB Volume", as I'd have expected.) And I got the error,
exactly as shown, "libhal-storage.c 1401 : info: called
libhal_free_dbus_error but dbuserror was not set..."
This error message was reproducible every time, and persisted through
a reboot.
It turned out I'd replaced an old CD-ROM with the new drive, and there
was an existing /etc/fstab entry for /dev/hdc (the new disk) as a
standard CD-ROM mount point, i.e. an fstab entry that looked like:
/dev/hdc /media/cdrom1 udf,iso9660 user,noauto 0 0
I replaced that entry in /etc/fstab with the right kind of entry for a
real disk (i.e. /dev/hdc1 /data ext3 etc. etc.) and the error message
disappeared, and the drive now mounts perfectly.
So, I'm wondering whether there's something odd going on with
Nautilus, HAL, and /etc/fstab entries -- I hope this isn't a complete
red herring, and that it might help shed some light on the problem.
Linux slave 2.6.18-6-486 #1 Tue Jun 17 20:57:16 UTC 2008 i686 GNU/Linux
un libdbus-1-1 <none> (no description available)
ii libdbus-1-3 1.0.2-1+etch1 simple interprocess messaging system
ii libdbus-glib-1 0.71-3 simple interprocess messaging system
(GLib-bun libdbus0 <none> (no description available)
ii libhal-storage 0.5.8.1-9etch1 Hardware Abstraction Layer - shared
library
ii libhal1 0.5.8.1-9etch1 Hardware Abstraction Layer - shared
library
Cheers,
Matt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
