Activity log for bug #62814
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2006-09-28 15:42:48 | Marc Tardif | bug | added bug | ||
| 2006-09-29 05:24:50 | towsonu2003 | None: statusexplanation | |||
| 2006-09-29 21:51:08 | Simon Law | oem-config: status | Unconfirmed | Confirmed | |
| 2006-09-29 21:51:08 | Simon Law | oem-config: importance | Undecided | High | |
| 2006-09-29 21:51:08 | Simon Law | oem-config: statusexplanation | oem-config-dm points out that it can't find the display. Perhaps it fires up before X is ready? | ||
| 2006-09-29 22:14:00 | Matt Zimmerman | oem-config: statusexplanation | oem-config-dm points out that it can't find the display. Perhaps it fires up before X is ready? | ||
| 2006-10-03 15:29:59 | Colin Watson | oem-config: assignee | kamion | ||
| 2006-10-03 21:12:41 | Colin Watson | oem-config: status | Confirmed | Fix Released | |
| 2006-10-03 21:12:41 | Colin Watson | oem-config: statusexplanation | oem-config (1.7) edgy; urgency=low * Add oem-config-udeb/frontend question, defaulting to gtk; preseed this to install a different oem-config frontend on the target system (closes: Malone #62777). * Wait more or less properly by means of SIGUSR1 for the X server to start up, rather than arbitrarily sleeping for five seconds. * Don't actually import the frontend module in oem-config-dm; merely check whether it exists. Otherwise, at least gtk will try to contact the X server at import time and get very confused when it predictably isn't there (closes: Malone #62814). -- Colin Watson <cjwatson@ubuntu.com> Tue, 3 Oct 2006 22:04:48 +0100 |
