[Bug 213099] Re: gnome-screensaver freezes and does not bring up the password prompt if mouse/keyboard activity

2008-10-22 Thread pescio
I've got this too. Seldomly the screensaver hangs when I want to login back. It happens with more frequence if I leave an image moving, i.e. not a balck screen. I'm on an hardy, hp compaq d330 DT. kernel: 2.6.24-21-generic #1 SMP -- gnome-screensaver freezes and does not bring up the password

[Bug 25931] Re: Failed to initalize HAL.

2007-10-31 Thread pescio
Good news guys, I fixed it! Fixing the init scripts I saw that klogd was blocking the booting process. I googled for "starting kernel daemon" and came here https://bugs.launchpad.net/ubuntu/+bug/150006 Simply changing something on ldap.conf solved my problem. I'm on a ldap/AD managed lan. Rebo

[Bug 25931] Re: Failed to initalize HAL.

2007-10-31 Thread pescio
Kloudy can you please post your `ls /etc/rc2.d | sort`? I'm wondering if there's something missing on my box before dbus and hal starting.. thanks and regards -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu D

[Bug 25931] Re: Failed to initalize HAL.

2007-10-29 Thread pescio
Hi, I cannot have the system booting also giving '/usr/lib/hal/hald-generate-fdi-cache'. It's dbus that doesn't start now... I attach a strace output. If I boot normally I see the system blocked on a 'Starting dbus ...' of something like that. I have to boot into rescue mode. Then at prompt 'str

[Bug 25931] Re: Failed to initalize HAL.

2007-10-25 Thread pescio
After booting in single mode I tried to give a `strace /etc/init.d/dbus start` and after a few seconds it stops in a "wait4 (-1, " message. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which

[Bug 25931] Re: Failed to initalize HAL.

2007-10-22 Thread pescio
Same behaviour here. I tried to uninstall/reinstall hal dbus but nothing. Seems like anyway that if I boot ubuntu in rescue mode [single mode] I'm able to run and start dbus and hal. This *does not* happen instead with normal boot. Right now the steps I do to have my working gnome desktop are: 1