reload after remerge: uranus ~ # /etc/init.d/halevt restart * Caching service dependencies ... /var/lib/init.d/depcache: line 2245: keyword: command not found * Can't find service 'mount-ro' needed by 'nut.powerfail'; continuing... [ ok ] * Stopping Automounter ... [ ok ] * Starting Automounter ... manager.c:356 (main) Using configuration file /etc/halevt/halevt.xml hal_interface.c:480 (halevt_run_command) Running: halevt-mount -u /org/freedesktop/Hal/devices/volume_uuid_3230_5553 -o sync -m 002 [ ok ] uranus ~ # and when inserting a USB stick: Jun 23 13:10:19 uranus kernel: sde: sde1 Jun 23 13:10:19 uranus kernel: sd 13:0:0:0: [sde] Assuming drive cache: write through Jun 23 13:10:19 uranus kernel: sd 13:0:0:0: [sde] Attached SCSI removable disk Jun 23 13:10:19 uranus kernel: halevt[27577]: segfault at 147a ip 0000000000406150 sp 00007fffca13cc60 error 4 in halevt[400000+a000] This happens since I updated this WE. No more auto-mounting. [ebuild R ] sys-apps/hal-0.5.13-r2 USE="X acpi apm consolekit crypt disk-partition doc laptop -debug -dell -policykit (-selinux)" 0 kB [ebuild R ] sys-apps/halevt-0.1.6.1 USE="nls -rpath" 0 kB
Created attachment 236315 [details] /tmp/emerge--info
Before, when i plugged my USB Stick, messages looked like this: Jun 24 02:58:48 uranus dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.13" (uid=1000 pid=13260 comm="/usr/lib/enlightenment/utils/enlightenment_fm) interface="org.freedesktop.Hal.Device" member="QueryCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=6794 comm="/usr/sbin/hald)) Jun 24 02:58:48 uranus dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.13" (uid=1000 pid=13260 comm="/usr/lib/enlightenment/utils/enlightenment_fm) interface="org.freedesktop.Hal.Device" member="QueryCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=6794 comm="/usr/sbin/hald)) Jun 24 02:58:48 uranus kernel: halevt[7052]: segfault at 147a ip 0000000000406150 sp 00007fffdf483390 error 4 in halevt[400000+a000] Jun 24 02:58:48 uranus dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.13" (uid=1000 pid=13260 comm="/usr/lib/enlightenment/utils/enlightenment_fm) interface="org.freedesktop.Hal.Device" member="QueryCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=6794 comm="/usr/sbin/hald)) Jun 24 02:58:48 uranus dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.13" (uid=1000 pid=13260 comm="/usr/lib/enlightenment/utils/enlightenment_fm) interface="org.freedesktop.Hal.Device" member="QueryCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=6794 comm="/usr/sbin/hald)) I have been said to rebuild halevt with debuging info: FEATURE=splitdebug CFLAGS="-O2 -march=athlon64 -pipe -ggdb" remerge halevt then uranus ~ # /etc/init.d/halevt stop * Caching service dependencies ... /var/lib/init.d/depcache: line 2245: keyword: command not found * Can't find service 'mount-ro' needed by 'nut.powerfail'; continuing [ ok ] * Stopping Automounter ... [ ok ] uranus ~ # /etc/init.d/halevt start * Starting Automounter ... manager.c:356 (main) Using configuration file /etc/halevt/halevt.xml [ ok ] uranus ~ # uranus ~ # gdb halevt 27649 warning: Can not parse XML syscalls information; XML support was disabled at compile time. GNU gdb (Gentoo 7.0.1 p1) 7.0.1 Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". For bug reporting instructions, please see: <http://bugs.gentoo.org/>... Reading symbols from /usr/bin/halevt...Reading symbols from /usr/lib64/debug/usr/bin/halevt.debug...done. (no debugging symbols found)...done. Attaching to program: /usr/bin/halevt, process 27649 Reading symbols from /usr/lib/libxml2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libxml2.so.2 Reading symbols from /usr/lib/libboolstuff-0.1.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libboolstuff-0.1.so.0 Reading symbols from /usr/lib/libhal.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libhal.so.1 Reading symbols from /usr/lib/libdbus-1.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libdbus-1.so.3 Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib/libpthread.so.0 Reading symbols from /usr/lib/libdbus-glib-1.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libdbus-glib-1.so.2 Reading symbols from /usr/lib/libglib-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libglib-2.0.so.0 Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.1 Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.3/libstdc++.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.3/libstdc++.so.6 Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /usr/lib/libgobject-2.0.so.0...(no debugging symbols found)...done. Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.5-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace Loaded symbols for /usr/lib/libgobject-2.0.so.0 Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_compat.so.2 Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_nis.so.2 Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_files.so.2 0x00007ffcae97185f in poll () from /lib/libc.so.6 (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. halevt_run_command (exec=0x60ffb0, udi=<value optimized out>, device=<value optimized out>) at hal_interface.c:449 449 hal_interface.c: No such file or directory. in hal_interface.c (gdb) ********************************************** I did cont first, then tail -f messages, then, plug a stick. After plugging it, i got the segfault in my console only, not in messages.
Created attachment 236537 [details] /var/log/portage/sys-apps:halevt-0.1.6.1:20100625-173648.log
Created attachment 236539 [details] /var/log/portage/sys-apps:halevt-0.1.6.1:20100625-173732.log
I catched the boot message: * Starting Hardware Abstraction Layer daemon ... [ ok ] * Starting Automounter ... manager.c:356 (main) Using configuration file /etc/halevt/halevt.xml [ ok ] * Starting hddtemp daemon ... [ ok ] The checkfs part is offtopic, and dealt in bug 325693
Could you try 0.1.6.2? I just pushed it on portage Here is the upstream changelog: *bugfix of the enhancement release *properly initialize property values to avoid a segfault when the property is not set (report and analysis from Marcin Gryszkalis) *really iterate over a str_list when copying it
* Starting Hardware Abstraction Layer daemon ... [ ok ] * Starting Automounter ... manager.c:357 (main) Using configuration file /etc/halevt/halevt.xml [ ok ] * Starting hddtemp I dislike very much this message; but, 0.1.6.2 works better: when i plug stuff, it's mounted (cripts are run). The segfault issue is fixed. Do i need to open a new bug for this message ?
Whats wrong with that message? Better to ask upstream to hide it if you want. I don't see a reason to patch the source code to hide the message
It's the only service showing a message; and previous versions did not do it. It does not look like a sysinit, or openrc message. If the daemon has something to say, it shall say it to syslogd. It mangles console output. It breaks the standard behaviour. It pushes OK on the next line. It breaks the beauty of Gentoo init system. I asked quiet output; even in verbose mode, I would not accept this. Unless i misconfigured sth; but elogv did not say anything significant about HAL.
This this behavior should be reported upstream imho
(In reply to comment #9) > It's the only service showing a message; and previous versions did not do it. > It does not look like a sysinit, or openrc message. > > If the daemon has something to say, it shall say it to syslogd. It mangles > console output. It breaks the standard behaviour. It pushes OK on the next > line. It breaks the beauty of Gentoo init system. > > I asked quiet output; even in verbose mode, I would not accept this. Unless i > misconfigured sth; but elogv did not say anything significant about HAL. > Ok you convinced me :) Fixed on -r1 :)
Upstream fixed it; but did not say in which version: http://lists.nongnu.org/archive/html/halevt-dev/2010-06/index.html http://lists.nongnu.org/archive/html/halevt-dev/2010-06/msg00010.html > Indeed, it it does that all the time, and the reason is that the output > function is called before daemonizing, that's why it is not sent to > syslog while it should have. I have a fix ready, I'll commit it soon. -r1 does it for me. Thanks. So, maybe 0.1.6.3 for official :) check upstream for rev bumb.