Funnily enough (or not) I have the same problem. Never really bothered
to check why though as my system seems fine and I though it was just me.
Now I know there might be something to it I had a look..
Startup fails here :
+ /bin/bash -c 'ulimit -S -c 0 >/dev/null 2>&1 ; hald --retain-privileges'
+ '[' 1 -eq 0 ']'
+ failure 'haldaemon startup'
+ rc=1
+ '[' color '!=' verbose -a -z '' ']'
+ echo_failure
Running an strace over the process shows _many_ of these :
[pid 19360] fcntl64(585, F_SETFD, FD_CLOEXEC) = -1 EBADF (Bad file
descriptor)
[pid 19360] fcntl64(586, F_SETFD, FD_CLOEXEC) = -1 EBADF (Bad file
descriptor)
[pid 19360] fcntl64(587, F_SETFD, FD_CLOEXEC) = -1 EBADF (Bad file
descriptor)
[pid 19360] fcntl64(588, F_SETFD, FD_CLOEXEC) = -1 EBADF (Bad file
descriptor)
[pid 19360] fcntl64(589, F_SETFD, FD_CLOEXEC) = -1 EBADF (Bad file
descriptor)
[pid 19360] fcntl64(590, F_SETFD, FD_CLOEXEC) = -1 EBADF (Bad file
descriptor)
[pid 19360] fcntl64(591, F_SETFD, FD_CLOEXEC) = -1 EBADF (Bad file
descriptor)
[pid 19360] fcntl64(592, F_SETFD, FD_CLOEXEC) = -1 EBADF (Bad file
descriptor)
Along with about a few million lines of other output which I have no
idea the meaning of.
leon wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
Hal fail to start on system boot. Does anyone has similar experience?
I'm going to file a bug if anyone confirm. And gnome powermanager applet
failed too. It might have to do with hal.
Run `/etc/init.d/haldaemon restart' gives:
Stopping HAL daemon: [FAILED]
Starting HAL daemon: [FAILED]
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
