Summary: | sys-apps/hal-0.5.9-r1 does not call callout scripts | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | takken <d.h.j.takken> |
Component: | [OLD] Core system | Assignee: | Project Gentopia <gentopia> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | d.h.j.takken |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
takken
2007-07-28 21:40:19 UTC
Would you mind attaching the log and a script? Excellent. You say it's lying and provide no logs or details. I'll file this bug away where it belongs until you can provide some details since, this works for me. I have a bash script in /usr/share/hal/scripts/test, which looks like this: ---------------------------------------------- #!/bin/bash beep echo "Callout Successful." ---------------------------------------------- The script is registered as a callout script by inserting this file in /usr/share/hal/fdi/information/20thirdparty/ : ---------------------------------------------- <?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <match key="info.category" string="volume"> <append key="info.callouts.add" type="strlist">/usr/share/hal/scripts/test</append> <append key="info.callouts.remove" type="strlist">/usr/share/hal/scripts/test</append> </match> </device> </deviceinfo> ---------------------------------------------- When I insert a USB memory stick, hald says: Run started hald-probe-storage (10000) (0) ! full path is '/usr/libexec/hald-probe-storage', program_dir is '/usr/libexec' /usr/libexec/hald-probe-storage exited Run started hald-addon-storage (0) (0) ! full path is '/usr/libexec/hald-addon-storage', program_dir is '/usr/libexec' Run started hald-probe-volume (10000) (0) ! full path is '/usr/libexec/hald-probe-volume', program_dir is '/usr/libexec' /usr/libexec/hald-probe-volume exited Run started /usr/share/hal/scripts/test (10000) (0) ! full path is '/usr/share/hal/scripts/test', program_dir is '(null)' No beep is produced, and the 'test' script does not print any message. When I revert to hal version 0.5.7.1-r5 and insert the same USB memory stick, hald says: ---------------------------------------------------- Run started hald-probe-storage (10000) (0) ! full path is '/usr/libexec/hald-probe-storage', program_dir is '/usr/libexec' /usr/libexec/hald-probe-storage exited Run started hald-addon-storage (0) (0) ! full path is '/usr/libexec/hald-addon-storage', program_dir is '/usr/libexec' ************************************************** ************************************************** Doing addon-storage for /dev/sdb (bus usb) (drive_type disk) (udi /org/freedesktop/Hal/devices/storage_serial_Kingston_DT_Elite_HS_2_0_0790FC407003090F_0_0) ************************************************** ************************************************** Run started hald-probe-volume (10000) (0) ! full path is '/usr/libexec/hald-probe-volume', program_dir is '/usr/libexec' /usr/libexec/hald-probe-volume exited Run started /usr/share/hal/scripts/test (10000) (0) ! full path is '/usr/share/hal/scripts/test', program_dir is '/usr/share/hal/scripts' Callout Successful. /usr/share/hal/scripts/test exited ---------------------------------------------------- It produces a nice beep and the message in the log. Note that the log of hal 0.5.9-r1 shows that the 'program_dir' value is 'null', and there is no message of the 'test' script exiting. This shows that hal 0.5.9-r1 fails to run the script, while hal 0.5.7.1-r5 runs it just fine. I hope you don't mind I re-opened the bug, because I can still reproduce it, and I proveded information about how to reproduce it. Callouts belong in /usr/libexec, not in /usr/share/hal/scripts For example the file: /usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi contains: <append key="info.callouts.add" type="strlist">hal-storage-cleanup-all-mountpoints</append> |