Re: [Bug 403509] New: hal-kernel-includes patch does not apply cleany

[Peter <sw98234 hotmail com>]

On Sat, 03 Feb 2007 00:41:15 +0100, guenther wrote:

snip....

> 
> Since neither Joseph nor me got any Slackware system, we need your guys
> help and opinion. We sure prefer not to ship any distro-specific hack,
> if possible. Worse, shipping a broken patch...
> 
> 
> Any opinion welcome, discussion much appreciated. ;)  Thanks...
> 
>   guenther

Interestingly, if I compile the hal sources (with all the garnome
patches) in the Slack environment, hal crashes on loading! Slack uses
udev-097 and libvolumeid-0.69. I posted this to the hal group, but like
usual, no response.

---------
$ hald --daemon=no
.....
/usr/libexec/hald-probe-storage exited
Run started hald-probe-volume (10000) (0)
!  full path is '/usr/libexec/hald-probe-volume', program_dir is '/usr/libexec'
Warning: Error while wite r->input () to stdin_v.
/usr/libexec/hald-probe-volume exited
Run started hald-probe-volume (10000) (0)
!  full path is '/usr/libexec/hald-probe-volume', program_dir is '/usr/libexec'
Warning: Error while wite r->input () to stdin_v.
/usr/libexec/hald-probe-volume exited
Segmentation fault

hald-runner is not listed in ps ax.

Now, when compiling the identical hal version, same patches
with garnome -- which uses libvolume_id from udev 0.104 --
hald-runner loads and hald runs fine.

So my question is, is there a problem with udev 0.97?
libvolume_id = 0.69
whereas
libvolube_id = 0.74 with udev 104.
------------

However, when hal, dbus, etc. are compiled in garnome, hal works fine.

In any event, I don't see the need for the slackware kernel patch. I would
like to know what keeps hal from working.


-- 
Peter