Xorg problem (apport gave no details, sorry)

Bug #1281562 reported by thom
150
This bug affects 15 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Apport came up for unknown reason, bug seems to be in Xorg according to apport.
Everything seems to work OK though.

Sorry I can't be more clear

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-core 2:1.15.0-1ubuntu6
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic i686
ApportVersion: 2.13.2-0ubuntu4
Architecture: i386
Date: Tue Feb 18 13:13:34 2014
ExecutablePath: /usr/bin/Xorg
InstallationDate: Installed on 2014-01-09 (40 days ago)
InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha i386 (20140102)
ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
ProcEnviron:

Signal: 6
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
thom (tsk) wrote :
Revision history for this message
thom (tsk) wrote :

This happened on a machine that is only used for testing Lubuntu 14.04, therefore I am not restricted (and would be glad to help) to test things if needed.

Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #1174698. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 OsAbort () at ../../os/utils.c:1324
 AbortServer () at ../../os/log.c:773
 FatalError (f=f@entry=0xb76aca78 "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices\n") at ../../os/log.c:911
 xf86PostProbe () at ../../../../hw/xfree86/common/xf86Bus.c:564
 InitOutput (pScreenInfo=pScreenInfo@entry=0xb7730f20 <screenInfo>, argc=argc@entry=11, argv=argv@entry=0xbfad2824) at ../../../../hw/xfree86/common/xf86Init.c:603

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
thom (tsk) wrote :

Since Linux 3.13.0-11-generic #31-Ubuntu SMP Wed Feb 19 19:59:55 UTC 2014 i686 i686 i686 GNU/Linux
The error changed to:

[ 15.244749] microcode: CPU0 sig=0xf29, pf=0x8, revision=0x1a
[ 15.941360] platform microcode: Direct firmware load failed with error -2
[ 15.941367] platform microcode: Falling back to user helper
[ 16.636901] microcode: CPU1 sig=0xf29, pf=0x8, revision=0x1a
[ 16.636948] platform microcode: Direct firmware load failed with error -2
[ 16.636954] platform microcode: Falling back to user helper
[ 16.687842] microcode: Microcode Update Driver: v2.00 <email address hidden>, Peter Oruba
[ 18.151162] nouveau [ DRM] Loading NV17 power sequencing microcode

maybe this info adds something new ?

Revision history for this message
thom (tsk) wrote :

I think I found something:

Every update first installs the kernel (which triggers DKMS ?) and complains about kernel headers missing
Then it installs kernel headers, but probably too late.

This results in triggering apport complaining about firmware stuff.

If I re-install the kernel and reboot, everything runs (compiles?) okay.

Maybe Update should install kernel-headers first ?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg-server (Ubuntu):
status: New → Confirmed
information type: Private → Public
tags: added: bugpattern-needed
Revision history for this message
Ion Cebotari (anathemizatu) wrote :

I have a similar problem with Intel drivers on Dell Inspiron N5110. At startup, I get the error that you can see in the attached file. After the system is loaded, manually doing "sudo service lightdm start" works and X runs normally.
I am not sure if my problem is compatible with the posted bug, but if I can help with tracebacks of X server, please tell me how to do it.

Revision history for this message
Paul White (paulw2u) wrote :

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

18 duplicate bug reports (as per Apport Retracing) and no comments since
late April 2014 imply this issue was fixed along time ago.

Changed in xorg-server (Ubuntu):
status: Confirmed → Fix Released
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.