failed to initialize HAL : gdm init script priority should be at least equal to dbus one
Bug #81670 reported by
Robbie Groenewoudt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dbus (Ubuntu) |
In Progress
|
High
|
Martin Pitt | ||
Edgy |
Confirmed
|
High
|
Unassigned | ||
gdm (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Edgy |
New
|
Undecided
|
Unassigned | ||
update-notifier (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Edgy |
Invalid
|
Undecided
|
Unassigned |
Bug 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
description: | updated |
Changed in gdm: | |
status: | Unconfirmed → Confirmed |
description: | updated |
Changed in gdm: | |
importance: | Undecided → High |
importance: | Undecided → High |
status: | Unconfirmed → Confirmed |
Changed in update-notifier: | |
status: | Unconfirmed → Rejected |
Changed in gdm: | |
assignee: | nobody → pitti |
status: | Confirmed → In Progress |
To post a comment you must log in.
Attached lspci.
There are more people with this problem. See http:// beans.seartipy. com/2006/ 11/25/ubuntu- 610-annoyance- failed- to-initialize- hal-error/