On Tue, 2007-03-06 at 11:33 +0100, Matteo Semplice wrote: > Dear everybody, > I seem to have a problem with the hal daemon in Debian Sarge. I think that hald doesn't start or it dies immediately. [...] > If I do instead: > roccia:~# hald --daemon=no --drop-privileges --verbose=yes > 08:48:20.505 [I] hald.c:394: hal 0.4.7 > 08:48:20.505 [I] hald.c:398: Will not daemonize > 08:48:20.507 [I] linux/osspec.c:219: Mountpoint for sysfs is /sys > Segmentation fault > > Any comments? I found a bug report describing the behaviour above, but it happened with hal version 0.5.8.1-1 so I'm not sure it's relevant. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393670 Usually, the best way to track this down is make a debug package, capture a backtrace with gdb and file a bug report. See http://wiki.debian.org/?HowToGetABacktrace In your case, I would absolutely upgrade to etch first, I would be surprised if this problem wasn't fixed. > Domande: > 1) where does hald writes its logs? I read about an option --use-syslog , but it is not recognized on my system AFAIK, syslog, see /var/log/syslog > 2) is this a known dbus/udev/hal issue in Debian sarge? I don't think so. > 3) I am willing to upgrade to testing, but only if I am sure that this would solve the issue... I give no guarantees, but if it isn't, and you can provide a backtrace and other information, I'm sure it will be fixed quickly. HTH, -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22
Attachment:
signature.asc
Description: This is a digitally signed message part