Bug#350762: hal 0.5.6-2 still broken
Sjoerd Simons wrote: >> Please wait. I tried to restart udev and tried to restart hal in all >> ways, >> >>tried to restart whole system with no success: lshal always reports the same >>errors and hald dies after a few minutes. >> >> > >This bug is another issue than the one you reported, please keep these problems >apart :) > > > >>Am I the only one experiencing these problems? >> >> > >Your currently the only one that has reported it. > > Sjoerd > > Sorry Sjoerd, you're right Mau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350762: hal 0.5.6-2 still broken
On Tue, Feb 07, 2006 at 07:43:09PM +0100, Mau wrote: > > > Could you try to restart the udev daemon (/etc/init.d/udev restart)? > > > It worked. My bad I suppose: i really didn't think about restarting udev > > after HAL upgrade. > > > Thanks for your help, I suppose the bug can be really closed now. > > Please wait. I tried to restart udev and tried to restart hal in all ways, > tried to restart whole system with no success: lshal always reports the same > errors and hald dies after a few minutes. This bug is another issue than the one you reported, please keep these problems apart :) > Am I the only one experiencing these problems? Your currently the only one that has reported it. Sjoerd -- GREAT MOMENTS IN HISTORY (#7): April 2, 1751 Issac Newton becomes discouraged when he falls up a flight of stairs. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350762: hal 0.5.6-2 still broken
> > Could you try to restart the udev daemon (/etc/init.d/udev restart)? > It worked. My bad I suppose: i really didn't think about restarting udev > after HAL upgrade. > Thanks for your help, I suppose the bug can be really closed now. Please wait. I tried to restart udev and tried to restart hal in all ways, tried to restart whole system with no success: lshal always reports the same errors and hald dies after a few minutes. Am I the only one experiencing these problems? Thanks - Mau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350762: hal 0.5.6-2 still broken
Sjoerd Simons wrote:
Which hack ?
This one:
In file /etc/udev/hal.rules change
ENV{SEQNUM}=="[0-9]*", ENV{UDEVD_EVENT}=="1",
RUN+="/usr/lib/hal/hal.hotplug"
with
ENV{SEQNUM}=="[0-9]*", ENV{UDEVD_EVENT}=="1",
RUN+="/usr/lib/hal/hal.hotplug $env{SUBSYSTEM}"
Debian Sid on AMD64, hal 0.5.6-2 and udev 0.084-1.
Does /etc/udev/hal.rules contain
``RUN+="socket:/org/freedesktop/hal/udev_event"'' ?
Yes it does:
[EMAIL PROTECTED]:~$ cat /etc/udev/hal.rules
# Have udev pass data over a socket to hal
RUN+="socket:/org/freedesktop/hal/udev_event"
# unmount block devices when they are removed
SUBSYSTEM=="block",ACTION="remove", RUN+="/usr/lib/hal/hal-unmount.sh"
Could you try to restart the udev daemon (/etc/init.d/udev restart)?
It worked. My bad I suppose: i really didn't think about restarting udev
after HAL upgrade.
Thanks for your help, I suppose the bug can be really closed now.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350762: hal 0.5.6-2 still broken
On Mon, Feb 06, 2006 at 12:05:37AM +0100, Mau wrote:
> > Does /etc/udev/hal.rules contain
> >``RUN+="socket:/org/freedesktop/hal/udev_event"'' ?
>
> My /etc/udev/hal.rules:
>
> # Have udev pass data over a socket to hal
> RUN+="socket:/org/freedesktop/hal/udev_event"
>
> # unmount block devices when they are removed
> SUBSYSTEM=="block",ACTION="remove", RUN+="/usr/lib/hal/hal-unmount.sh"
>
> >> Could somebody please explain again the "$env{SUBSYSTEM} hack"?
> >> I haven't really found where to add that thing.
> >Which hack ?
>
> When I wrote about the "$env{SUBSYSTEM} hack" I meant the suggestion
> that Kay Sievers gave to make hal 0.5.5.1-5 work some posts before:
> sorry if the words I used were confusing.
That's not applicable anymore as we've switched to using the socket to
communicate.
Could you check that hald actually has the socket open ? (netstat -p -x | grep
freedesktop)
Sjoerd
--
After a number of decimal places, nobody gives a damn.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350762: hal 0.5.6-2 still broken
> Does /etc/udev/hal.rules contain
>``RUN+="socket:/org/freedesktop/hal/udev_event"'' ?
My /etc/udev/hal.rules:
# Have udev pass data over a socket to hal
RUN+="socket:/org/freedesktop/hal/udev_event"
# unmount block devices when they are removed
SUBSYSTEM=="block",ACTION="remove", RUN+="/usr/lib/hal/hal-unmount.sh"
>> Could somebody please explain again the "$env{SUBSYSTEM} hack"?
>> I haven't really found where to add that thing.
>Which hack ?
When I wrote about the "$env{SUBSYSTEM} hack" I meant the suggestion
that Kay Sievers gave to make hal 0.5.5.1-5 work some posts before:
sorry if the words I used were confusing.
Mau
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350762: hal 0.5.6-2 still broken
On Sat, Feb 04, 2006 at 10:15:14AM +0100, Fabio Rosciano wrote:
> I'd like to confirm that hal 0.5.6-2 doesn't handle mounting properly.
>
> I started hald like this:
>
> # hald --daemon=no --verbose=yes
>
> and plugging in a USB thumbdrive (/dev/sdc as I have two SATA drives)
> does not trigger *any* events.
>
> The device is correctly created by udev:
>
> nostromo:~# ls -l /dev/ | grep sdc
> brw-rw 1 root floppy8, 32 2006-02-04 10:12 sdc
> brw-rw 1 root floppy8, 33 2006-02-04 10:12 sdc1
>
> And /dev/sdc1 is mountable by hand.
>
> Could somebody please explain again the "$env{SUBSYSTEM} hack"?
> I haven't really found where to add that thing.
Which hack ?
> Debian Sid on AMD64, hal 0.5.6-2 and udev 0.084-1.
Does /etc/udev/hal.rules contain
``RUN+="socket:/org/freedesktop/hal/udev_event"'' ?
Could you try to restart the udev daemon (/etc/init.d/udev restart)?
Sjoerd
--
The world is moving so fast these days that the man who says it can't be
done is generally interrupted by someone doing it.
-- E. Hubbard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350762: hal 0.5.6-2 still broken
I'd like to confirm that hal 0.5.6-2 doesn't handle mounting properly.
I started hald like this:
# hald --daemon=no --verbose=yes
and plugging in a USB thumbdrive (/dev/sdc as I have two SATA drives)
does not trigger *any* events.
The device is correctly created by udev:
nostromo:~# ls -l /dev/ | grep sdc
brw-rw 1 root floppy8, 32 2006-02-04 10:12 sdc
brw-rw 1 root floppy8, 33 2006-02-04 10:12 sdc1
And /dev/sdc1 is mountable by hand.
Could somebody please explain again the "$env{SUBSYSTEM} hack"?
I haven't really found where to add that thing.
Debian Sid on AMD64, hal 0.5.6-2 and udev 0.084-1.
Thanks.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
