| 2007-01-26 14:42:14 |
Robbie Groenewoudt |
bug |
|
|
added bug |
| 2007-01-26 14:43:41 |
Robbie Groenewoudt |
bug |
|
|
added attachment 'lspci.txt' (lspci of my system) |
| 2007-01-26 14:56:00 |
Robbie Groenewoudt |
description |
I'm getting the error 'failed to initialize HAL' when I enable automated login Administration -> Login Window.
The error doesn't occur when timed login is used.
No difference with or without any USB devices |
I'm getting the error 'failed to initialize HAL' when I enable automated login Administration -> Login Window.
The error doesn't occur when timed login is used.
No difference with or without any USB devices
Ubuntu Edgy with latest updates |
|
| 2007-02-11 18:30:59 |
Anders Kaseorg |
None: statusexplanation |
|
|
|
| 2007-02-11 18:31:37 |
Anders Kaseorg |
bug |
|
|
assigned to hal (Ubuntu) |
| 2007-02-12 14:59:23 |
Florent Mertens |
update-notifier: status |
Unconfirmed |
Rejected |
|
| 2007-02-12 14:59:23 |
Florent Mertens |
update-notifier: statusexplanation |
|
I don't see any reason why it should be update-notifier fault :
There is a real problem if hal is started after gnome, what seams to be the case |
|
| 2007-02-12 15:05:51 |
Florent Mertens |
hal: statusexplanation |
|
I think this bug is due to a problem in the init script priority :
- gdm start with S13
- dbus (and so hal) start with S20
In the majority of the case there is no problem. But if you use automated login and if there a script between the 2 that take some time, it might fail.
I suggest that priority of gdm should be at least the same as dbus (20) or, to be more safe, greeter (21 or something) |
|
| 2007-02-12 15:14:12 |
Florent Mertens |
title |
failed to initialize HAL with automated login |
failed to initialize HAL : gdm init script priority should be at least equal to dbus one |
|
| 2007-02-12 16:39:53 |
C de-Avillez |
gdm: status |
Unconfirmed |
Confirmed |
|
| 2007-02-12 16:39:53 |
C de-Avillez |
gdm: statusexplanation |
I think this bug is due to a problem in the init script priority :
- gdm start with S13
- dbus (and so hal) start with S20
In the majority of the case there is no problem. But if you use automated login and if there a script between the 2 that take some time, it might fail.
I suggest that priority of gdm should be at least the same as dbus (20) or, to be more safe, greeter (21 or something) |
|
|
| 2007-02-12 18:20:12 |
C de-Avillez |
description |
I'm getting the error 'failed to initialize HAL' when I enable automated login Administration -> Login Window.
The error doesn't occur when timed login is used.
No difference with or without any USB devices
Ubuntu Edgy with latest updates |
I'm getting the error 'failed to initialize HAL' when I enable automated login Administration -> Login Window.
The error doesn't occur when timed login is used.
No difference with or without any USB devices
Ubuntu Edgy with latest updates
|
|
| 2007-02-23 22:41:14 |
Pascal De Vuyst |
gdm: importance |
Undecided |
High |
|
| 2007-02-23 22:42:25 |
Pascal De Vuyst |
gdm: status |
Unconfirmed |
Confirmed |
|
| 2007-02-23 22:42:25 |
Pascal De Vuyst |
gdm: importance |
Undecided |
High |
|
| 2007-02-23 22:42:25 |
Pascal De Vuyst |
gdm: statusexplanation |
|
|
|
| 2007-02-23 22:42:53 |
Pascal De Vuyst |
update-notifier: status |
Unconfirmed |
Rejected |
|
| 2007-02-23 22:42:53 |
Pascal De Vuyst |
update-notifier: statusexplanation |
|
|
|
| 2007-03-02 13:07:38 |
Martin Pitt |
gdm: statusexplanation |
|
Indeed we should either start gdm later or dbus earlier, whichever suits better. |
|
| 2007-03-06 19:23:07 |
Pascal De Vuyst |
bug |
|
|
added attachment 'hal.log' (hal debug log) |
| 2007-03-08 12:13:48 |
Martin Pitt |
gdm: status |
Confirmed |
In Progress |
|
| 2007-03-08 12:13:48 |
Martin Pitt |
gdm: assignee |
|
pitti |
|
| 2007-03-08 12:13:48 |
Martin Pitt |
gdm: statusexplanation |
Indeed we should either start gdm later or dbus earlier, whichever suits better. |
|
|
| 2007-03-08 12:22:01 |
Martin Pitt |
marked as duplicate |
|
25931 |
|
