tag 351296 +pending
thanks,
On Thu, Feb 09, 2006 at 11:19:14PM +0100, Mau wrote:
> Interesting:
>
> # ps aux | grep hald
> [no output]
> # modprobe -r ide-floppy
> # lsmod | grep floppy
> floppy 56036 0
> # /etc/dbus-1/event.d/20hal start
> # ps aux | grep hald
> hal 9122
Interesting:
# ps aux | grep hald
[no output]
# modprobe -r ide-floppy
# lsmod | grep floppy
floppy 56036 0
# /etc/dbus-1/event.d/20hal start
# ps aux | grep hald
hal 9122 0.0 0.3 5316 3868 ?Ss 22:48 0:00
/usr/sbin/hald
root 9123 0.0 0.0 2728 968
On Tue, Feb 07, 2006 at 11:01:30PM +0100, Mau wrote:
> Sjoerd Simons wrote:
>
> >Ok, full stop. This means it's not a communication with udev problem or
> >anything like that. Could you send a strace and ltrace from hald ?
> >
> > Sjoerd
> >
> >
> Here are some [sl]traces; a strace -f output i
On Tue, Feb 07, 2006 at 02:13:40PM -0700, John A. Schmidt wrote:
> On Tue, Feb 07, 2006 at 02:08:38PM -0700, John A. Schmidt wrote:
> > Package: hal
> > Version: 0.5.6-2
> > Followup-For: Bug #351296
> >
> >
> > hald hangs right after probing for an ATAPI zip drive. The relevant
> > section of t
On Tue, Feb 07, 2006 at 02:08:38PM -0700, John A. Schmidt wrote:
> Package: hal
> Version: 0.5.6-2
> Followup-For: Bug #351296
>
>
> hald hangs right after probing for an ATAPI zip drive. The relevant
> section of the output from hald --daemon=no --verbose=yes is shown
> below:
>
Attached are
Package: hal
Version: 0.5.6-2
Followup-For: Bug #351296
hald hangs right after probing for an ATAPI zip drive. The relevant
section of the output from hald --daemon=no --verbose=yes is shown
below:
11:54:47.863 [I] hald.c:95: Started addon hald-addon-storage for udi
/org/freede
sktop/Hal/device
On Mon, Feb 06, 2006 at 11:19:15PM +0100, Mau wrote:
> Sjoerd Simons wrote:
>
> >On Fri, Feb 03, 2006 at 11:04:24PM +0100, Mau wrote:
> >
> >
> > [...]
> >
> >Does hal actually work after that (For example lshal shows a listing)?
> >
> > Sjoerd
> >
> >
> no, it doesn't work:
>
> # lshal
> er
Sjoerd Simons wrote:
>On Fri, Feb 03, 2006 at 11:04:24PM +0100, Mau wrote:
>
>
> [...]
>
>Does hal actually work after that (For example lshal shows a listing)?
>
> Sjoerd
>
>
no, it doesn't work:
# lshal
error: libhal_ctx_init: (null): (null)
Could not initialise connection to hald.
Normal
On Fri, Feb 03, 2006 at 11:04:24PM +0100, Mau wrote:
> Package: hal
> Version: 0.5.6-2
> Severity: important
>
>
> After update to 0.5.6-2 the /etc/dbus-1/event.d/20hal script locks up:
> start-stop-daemon waits for hald process fork which apparently doesn't
> occur.
> /usr/sbin/hald actually for
Some more info - I noticed that hald dies after some minutes; tried to
start hald manually by running
# /etc/dbus-1/event.d/20hal start
the process hangs at
Starting Hardware abstraction layer: hald (no dot after this text)
output of ps aux | grep hald first:
root 5818 0.0 0.0 3216
Package: hal
Version: 0.5.6-2
Severity: important
After update to 0.5.6-2 the /etc/dbus-1/event.d/20hal script locks up:
start-stop-daemon waits for hald process fork which apparently doesn't
occur.
/usr/sbin/hald actually forks but it seems unable to detach completely,
even when explicitly calli
11 matches
Mail list logo