hal starts too late
Bug #127913 reported by
Martin Pitt
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| hal (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Bug Description
Binary package hint: hal
hal now starts at S24, thus much later than S13gdm. This is the reason why sometimes the gnome session doesn't have a running hal yet, especially on the live CD. We need to migrate hal's priority to "12.5" (in between S12dbus and S13gdm).
Related branches
| Changed in hal: | |
| assignee: | nobody → pitti |
| importance: | Undecided → High |
| status: | New → In Progress |
Revision history for this message
| Martin Pitt (pitti) wrote | #1 |
| Changed in hal: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
hal (0.5.9.1-1ubuntu2) gutsy; urgency=low
* debian/rules:
- Start hal init script at priority 12 instead of 24, so that it starts
right after dbus, and before gdm. This fixes the race condition of
gnome-session sometimes not having hal ready. (LP: #127913)
- Do not stop hal in levels 0 and 6, it's not necessary (multiuser-like
change).
* debian/hal.preinst: Fix rc symlink priority on upgrades. Since Feisty did
not yet have its own rc symlinks, this only needs to be kept for
intra-gutsy updates and thus should disappear around the beta release.
-- Martin Pitt <email address hidden> Tue, 24 Jul 2007 12:47:38 +0200