Ubiquity (GTK) hangs for 90 seconds before showing its GUI for zh_CN/zh_TW installs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
scim (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
ubiquity (Ubuntu) |
Fix Released
|
Medium
|
Colin Watson |
Bug Description
When Chinese (simplified or traditional) is selected on the startup menu (isolinux, gfxboot) of Ubuntu 8.04 (Hardy) Desktop official Live CD (tested on i386), once in GNOME, upon double-clicking on the the Installer icon (ubiquity gtk_ui), it would take over 90 seconds until the first welcome screen appears.
/var/log/syslog shows the following:
May 22 21:48:51 ubuntu ubiquity[7667]: Ubiquity 1.8.7
May 22 21:48:56 ubuntu ubiquity[7667]: log-output -t ubiquity laptop-detect
May 22 21:48:58 ubuntu ubiquity[7667]: log-output -t ubiquity fontconfig-voodoo --auto --force --quiet
May 22 21:50:26 ubuntu ubiquity[7667]: switched to page stepLanguage
May 22 21:50:28 ubuntu localechooser: info: Locale has been preseeded to zh_CN
May 22 21:50:28 ubuntu localechooser: info: Set languagechooser
May 22 21:50:28 ubuntu localechooser: info: Set countrychooser/
May 22 21:50:28 ubuntu localechooser: info: Set debian-
May 22 21:50:28 ubuntu ubiquity[7667]: switched to page stepLanguage
Note the 88-second gap between the fontconfig-voodoo run and the next output? When preseeded with locales other than zh_CN or zh_TW, the gap is only a few seconds.
Well, the problem is not with fontconfig-voodoo, but further down on line 477: self.live_
As far as I know, this only affects the GTK+ frontend and not the KDE frontend in Kubuntu.
Thanks,
Anthony
Changed in ubiquity: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in ubiquity: | |
assignee: | nobody → kamion |
status: | Confirmed → Fix Committed |
strace shows that it's trying to talk to /tmp/scim- panel-socket: 0-root. It seems to be hard to fool scim about the user name; it uses getuid() rather than the effective user ID (presumably has to in order to support "ordinary" setuid-root X applications), which will always be 0 in ubiquity, and there's no higher-priority override. We might just have to add one.