Patkos Csaba Posted February 24, 2007 Report Share Posted February 24, 2007 [sOLUTION: I reinstalled the original version of dbus and libdbus from the install DVD] SO: mandriva 2007.0 powerpack Just made an update from the update sources configured for urpmi. There were lot of updates includeing HAL, avahi, (and dbus I think). After update, hal, dbus, udev starts with no error, but automount deosn't work anymore. Klick on Konqueror media:/hdc (my dvd drive) returns this error: "Feature only available with HAL" After manual mount, like: mount /mnt/cdrom2, I can click and access media:/hdc Unmount, eject options from Konqueror returns same error. I tried to insert my linux dvd and do a "rpmi --install --replacepkgs --force /mnt/cdrom2/.../hal...rpm" This way I replaced (reinstalled) all dbus, hal, avahi packages I could find. Now dbus works, udev works, BUT avahi and hal fails. Basicly I would like you to help me make a clean reinstall of these packages from the original dvd. Just for the rekord: old (original) version of HAL: 0.5.7.1-7mdv2007 new version was (I think): 0.5.7.1-9mdv2007 Please help, I can mount cd's manualy, but others useing my pc .... can't.... :( Quote Link to comment Share on other sites More sharing options...
scarecrow Posted February 24, 2007 Report Share Posted February 24, 2007 I guess HAL is running as a system daemon, or not? dbus doesn't have to- every time HAL needs to do something it will call dmus itself. Quote Link to comment Share on other sites More sharing options...
Patkos Csaba Posted February 24, 2007 Author Report Share Posted February 24, 2007 Current situation is: With mandriva control center I installed all updates again. HAL daemon still not starts. Avahi same. I tryed stop udev and start hal - same result. I tryed stop messagebus and start hal - same result. Udev and messagebus runs OK as daemons, no errors. I tryed a "service haldaemon start --debug", here are the parts of the output which were marked in red: + gprintf FAILED + '[' -x /bin/gettext -a -n FAILED ']' + '[' -n en_US.UTF-8 ']' ++ LC_ALL=en_US.UTF-8 ++ LANGUAGE=en_US.UTF-8:en_US:en ++ gettext -e --domain=initscripts -- FAILED + local TEXT=FAILED + '[' FAILED ']' + shift + printf -- FAILED FAILED+ '[' color = color ']' + echo -en '\033[0;39m' after these lines follosws written in white (grey): + echo -n ']' ]+ echo -ne '\r' + return 1 + '[' -w /var/gdm/.gdmfifo ']' + return 1 + unset LD_PRELOAD + return 1 + RETVAL=1 + echo + '[' 1 -eq 0 ']' + exit 1 + exit 1 [root@localhost ~]# Hope this helps you figure out my problem. But still, please explain me, how to reinstall these packages and everything related. I tryed uninstalling hal from control center, but it told me that other about 50 applications must be removed in order to satisfy dependencies ... this solution is not acceptable. Quote Link to comment Share on other sites More sharing options...
Patkos Csaba Posted February 24, 2007 Author Report Share Posted February 24, 2007 After some digging ... I tried to start hal in this way: /usr/sbin/hald --daemon=no --verbose=yes After a long output of all kind of interfaces and devices it crashes. These are the las few lines: 22:40:14.587 [D] hald_dbus.c:1192: udi=/org/freedesktop/Hal/devices/temp/103, key=volume.fsusage 12910: 22:40:14.588: probe-volume.c:118: volume.fsusage = 'filesystem' 22:40:14.588 [D] hald_dbus.c:1192: udi=/org/freedesktop/Hal/devices/temp/103, key=volume.fstype 12910: 22:40:14.588: probe-volume.c:121: volume.fstype = 'iso9660' 22:40:14.589 [D] hald_dbus.c:1192: udi=/org/freedesktop/Hal/devices/temp/103, key=volume.uuid 12910: 22:40:14.589: probe-volume.c:127: volume.uuid = '' 22:40:14.589 [D] hald_dbus.c:1192: udi=/org/freedesktop/Hal/devices/temp/103, key=volume.label 12910: 22:40:14.589: probe-volume.c:133: volume.label = '2007.0-Powerpack-i586-disc1' 22:40:14.590 [D] hald_dbus.c:1192: udi=/org/freedesktop/Hal/devices/temp/103, key=info.product 22:40:14.594 hald_dbus.c:3173: Client to local_server was disconnected 22:40:14.594 hald_dbus.c:3183: unregistered /usr/lib/hald-probe-volume exited 22:40:14.596 blockdev.c:377: entering; exit_type=0, return_code=0 22:40:14.596 blockdev.c:252: * found mounts dev rootfs (3:3) 22:40:14.596 blockdev.c:263: match /org/freedesktop/Hal/devices/volume_label_2007_0_Powerpack_i586_disc1 (22:0) 22:40:14.596 blockdev.c:252: * found mounts dev /dev/root (3:3) 22:40:14.596 blockdev.c:263: match /org/freedesktop/Hal/devices/volume_label_2007_0_Powerpack_i586_disc1 (22:0) 22:40:14.596 blockdev.c:252: * found mounts dev /dev/hda7 (3:7) 22:40:14.596 blockdev.c:263: match /org/freedesktop/Hal/devices/volume_label_2007_0_Powerpack_i586_disc1 (22:0) 22:40:14.596 blockdev.c:252: * found mounts dev /dev/hda1 (3:1) 22:40:14.596 blockdev.c:263: match /org/freedesktop/Hal/devices/volume_label_2007_0_Powerpack_i586_disc1 (22:0) 22:40:14.598 blockdev.c:291: set /org/freedesktop/Hal/devices/volume_label_2007_0_Powerpack_i586_disc1 to unmounted 22:40:14.607 device_info.c:1427: *** Matched file /usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi 22:40:14.608 blockdev.c:141: Add callouts completed udi=/org/freedesktop/Hal/devices/volume_label_2007_0_Powerpack_i586_disc1 22:40:14.608 hald.c:82: Added device to GDL; udi=/org/freedesktop/Hal/devices/volume_label_2007_0_Powerpack_i586_disc1 22:40:14.608 hald.c:616: Device probing completed 22:40:14.608 hald_dbus.c:3251: entering 22:40:14.608 [E] hald_dbus.c:3258: dbus_bus_get(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Sent kill to 12884 Sent kill to 12900 Sent kill to 12902 Sent kill to 12889 /usr/lib/hald-addon-storage exited /usr/lib/hald-addon-acpi exited /usr/lib/hald-addon-keyboard exited /usr/lib/hald-addon-storage exited So, as I understand all these ... I may look after dbus (messagebus service) to find out my problem. It seems that it more related to dbus, it is? About this line in the above text: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory Ofcourse the file exists. [root@localhost log]# ls -l /var/run/dbus total 0 srwxrwxrwx 1 root root 0 Feb 24 15:54 system_dbus_socket= Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.