[apport] oem-config-dm crashed with XStartupError in run()

Bug #96435 reported by miked
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: oem-config

Fresh install i386/i686.iso Alternative Install Ubuntu 7.04 Beta-The Feisty Fawn -(Herd6) with updates and upgrades.

ProblemType: Crash
Architecture: i386
Date: Mon Mar 26 02:58:32 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/sbin/oem-config-dm
InterpreterPath: /usr/bin/python2.5
Package: oem-config 1.12
PackageArchitecture: i386
ProcCmdline: /usr/bin/python /usr/sbin/oem-config-dm vt7 :0 /usr/sbin/oem-config
ProcCwd: /
ProcEnviron: PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/sbin:/usr/sbin
PythonArgs: ['/usr/sbin/oem-config-dm', 'vt7', ':0', '/usr/sbin/oem-config']
SourcePackage: oem-config
Uname: Linux Ubuntu704BetaHerd6 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

Tags: oem-config
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report.

Changed in oem-config:
importance: Undecided → Medium
Revision history for this message
miked (miked11) wrote :

I have some updates and upgrades yet to do.

Revision history for this message
miked (miked11) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

Could you attach /var/log/oem-config.log and /var/log/Xorg.0.log to this bug report, please?

Changed in oem-config:
assignee: nobody → kamion
status: Unconfirmed → Needs Info
Revision history for this message
Nanley Chery (nanoman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in oem-config:
status: Incomplete → Invalid
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :

Sorry about lack of info, I don't yet have a handle on all the bug stuff, also If I don't keep getting the crash I figure it is fixed. I am now using a fresh install of Ubuntu Gusty Gibbon Beta 7.10 i3x86.iso Alternative Install with up to the moment updates and dist-upgrades. I have also installed as many of the add/remove applications to help try to get the bugs weeded out before Gamma Product Release. I have added most recent xorg.log files and oem-config.log file as requested. I have a matchbox virtual keyboard that doesn't remove off the webpage browser windows in mozilla firefox, my computer no longer shutsdown, unless I go into terminal and give it a shutdown command and then It turns off to the will now halt dialog, and turns off something inside the computer but the display remains. I also have to <Ctrl>-<Alt>-<F1>or <F2>thru <F8> to get a terminal to login and run a StartX,. I sometimes have to reconfig the display which is a dual head display with only a 15-pin VGA monitor connected. When my computer starts up I get a invalid mode error message asking me to pick a mode or press the <spacebar> or wait 30 seconds to continue. I might of also missed responding to this bug because once I lose the ability to see the OS on my computer because of a display bug, not always knowing the StartX, GDM, KDM, and xorg.conf options in a terminal it's game over for me, and I need to reinstall the OS, switch computers, or wait till the next release and hope the bug is fixed. Which can be challenging when the release schedule changes which I have seen twice in the last two beta releases which I would think is one of the worst times to skip a release. Anyway please reopen this bug, if it's self imposed please let me know, I'm new to most of this and am willing to try to send more info as requested but I am Beta testing this OS on 3 very different computers.

Changed in oem-config:
status: Invalid → New
Revision history for this message
miked (miked11) wrote :
Nanley Chery (nanoman)
Changed in oem-config:
status: New → Confirmed
Revision history for this message
Luke has no name (lukehasnoname) wrote :

This was an OEM install, next to a vista partition, with /boot on it's own, and the other linux partitions on an LVM on top of an encrypted volume.

 After running through the install process, I booted into Ubuntu with the oem user. I clicked "Prepare for end user config"
on the desktop. After that ran, I ran all software updates and installed the binary nvidia driver (177) for my 8800M laptop card. I then rebooted. I didn't get the
vbe error as above at the time, but I did get an error after the logo and boot screen.

Blank screen for a little, then:

Traceback: From last call:
-File /usr/sbin/oem-config-dm, line 136 in <module>
--sys.exit(dm.run(*sys.argv[3:]))
-File /usr/sbin/oem-config-dm, line 66 in run
--raise.XStartupError, "X server failed to start after 60 seconds"
__main__.XStartupError, "X server failed to start after 60 seconds"

Colin Watson (cjwatson)
affects: oem-config (Ubuntu) → ubiquity (Ubuntu)
tags: added: oem-config
Colin Watson (cjwatson)
Changed in ubiquity (Ubuntu):
assignee: Colin Watson (cjwatson) → nobody
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.