hald does not start

salamo alikom
due to power cut , i lost my rc.conf (by way i forget to fsck my sys :D before i start it again ) ,so i start a new one with this :
Code:
hald_enable="YES"
dbus_enable="YES"
moused_enable="YES"
moused_port="/dev/psm0"
moused_type="auto"
after reboot sys i found my mouse does not move ,investing process i found hald does not start even i start it manually !
 
No need to fsck manually. Automatic fsck starts after 60 seconds.

Is the mouse not moving under the shell or under X/GNOME?

Try removing (or commenting out) moused entries.

How are you starting HALd manually (what command)?
Is it giving you any error?
Try forcestarting it instead.
 
Is the mouse not moving under the shell or under X/GNOME?
under GNOME .
Try removing (or commenting out) moused entries.
i did .
How are you starting HALd manually (what command)?
rc.conf do it for me ,but i did manualy when i stop and start it again :
Code:
/etc/rc.d/hald start
Is it giving you any error?
i try this :
Code:
hald --daemon=no --verbose=yes
Script started on Fri Jan  8 12:13:47 2010
12:13:47.652 [I] hald.c:680: hal 0.5.13
12:13:47.652 [I] hald.c:681: using child timeout 250s
12:13:47.652 [I] hald.c:746: Will not daemonize
12:13:47.654 [I] hald_dbus.c:5421: local server is listening at unix:path=/var/run/hald/dbus-jCItkSnskH,guid=74c55782fb3d166cbfb74c124b47136b
12:13:47.658 [I] ck-tracker.c:391: got seat '/org/freedesktop/ConsoleKit/Seat1'
12:13:47.659 [I] ck-tracker.c:342: Got all sessions on seat '/org/freedesktop/ConsoleKit/Seat1'
12:13:47.659 [I] ck-tracker.c:418: Got seats
12:13:47.659 [I] ck-tracker.c:816: Got seats and sessions
Runner started - allowed paths are '/usr/local/libexec:/usr/local/libexec/hal/scripts:/usr/local/bin'
12:13:47.669 [I] hald_runner.c:301: Runner has pid 786
12:13:47.669 [I] hald_runner.c:182: runner connection is 0x286236c0
[WARN   785] polkit-error.c:143:polkit_error_get_error_message(): error != NULL
 Not built with -rdynamic so unable to print a backtrace
*** [DIE] hald.c:main():797 : Could not init PolicyKit context: (null)
 
i found the problem was that var does not mounted yet :D ,now it start and every think fine .
problem solved .
 
Back
Top