Landscape daemons fail to start when too many groups are available
Bug #456124 reported by
Thomas Herve
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
High
|
Thomas Herve | ||
landscape-client (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Intrepid |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned | ||
Karmic |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Due to a bug in Twisted (http://
We should workaround this problem in Landscape by patching the twisted.python.util to use the real initgroups call.
Related branches
tags: | added: needs-testing |
Changed in landscape-client (Ubuntu Lucid): | |
status: | New → Fix Committed |
status: | Fix Committed → Fix Released |
tags: | removed: verification-needed |
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I built new packages based on this branch and installed them on my test machine where landscape-client was failing to start. With the new packages, it starts up just fine.
qa + 1