* 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 <email address hidden> Tue, 3 Oct 2006 22:04:48 +0100
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 <email address hidden> Tue, 3 Oct 2006 22:04:48 +0100