nonfunctional root desktop after oem config

Bug #153648 reported by Martin Pitt on 2007-10-17
Affects Status Importance Assigned to Milestone
oem-config (Ubuntu)

Bug Description

Binary package hint: oem-config

Kubuntu alternate amd64, Gutsy final, OEM mode installation: After performing the 4-step OEM configuration, the computer was busy for a while, then left me with just a blue background, no panels at all. I can open a context menu which indicates that this is half of a KDE session for root. Logging out complains about "cannot connect to the session manager" and does not work.

After killing the X server with Ctrl+Alt+Del, I get an error "X failed to restart" (I attach a screenshot), VT1 has a root shell, but is dead.

I logged in on VT2, restarted kdm, and now everything is happy.

Martin Pitt (pitti) wrote :
Roy Jamison (xteejx) wrote :

Hi Martin, just a quick nudge, I know this was reported in Gutsy, I don't suppose it was ever reproduced in Hardy onwards was it? Is it safe to close this? Thanks.

Changed in oem-config (Ubuntu):
status: New → Incomplete
Martin Pitt (pitti) wrote :

Indeed, nevermind that one. CDs regularly get tested, and a problem like this would come up.

Changed in oem-config (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments