Please backport gdm and language-selector to Lucid and Maverick
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Lucid Backports |
Fix Released
|
Wishlist
|
Unassigned | ||
maverick-backports |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Ever since the Ubuntu language support feature was changed to distinguish between language for message translation and non-language locales such as date formats, it has not played well with GDM's language chooser. Example: People who want date formats, default paper sizes etc. match their current geographical location, while using some other locale for controlling message translation, have encountered confusing, unexpected behavior.
Detailed descriptions and discussion can be found at bug 553162, and fixes have been released in Natty. The four branches, to which I have linked below, contain equivalent fixes for Lucid and Maverick, and I suggest that those branches are used to build packages for lucid-backports and maverick-backports. The branches were uploaded to my PPA, and the resulting builds have been tested successfully.
https:/
Hence I give this bug the status "Confirmed".
I was about to nominate the fixes for SRUs, but was told that they include too much of changed behavior to qualify. Nevertheless, the rationale and discussion on regression risk at the top of the description of bug 553162 apply to this backports request as well.
Please let me know if there is anything else I can do to help process this request.
Changed in lucid-backports: | |
status: | New → Confirmed |
Changed in maverick-backports: | |
status: | New → Confirmed |
description: | updated |
Changed in maverick-backports: | |
status: | In Progress → Fix Released |
Changed in lucid-backports: | |
status: | In Progress → Fix Released |
Natty's language-selector won't work in lucid/maverick, as this was moved from pygtk2 to python gobject- introspection. This needs a custom upload then.
natty's gdm should work fine on lucid/maverick (I haven't tested it, though).
I don't think that this is a feature which is very important to have on a stable release; people who have used those for a long time already will have learned how to deal with the situation, and it actually brings some intrusive changes (for example, LC_MESSAGES will be exported through ssh and cause a lot of locale problems on remote sites). But that shouldn't preclude a backport, of course.