[i845] xio fatal error 104 on compiz --replace on intel i830

Bug #286524 reported by jerryb
6
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I tried to startup compiz with compiz --replace command but it caused an endless loop going to the login screen then crashing again and again. The only way I knew it was going to the login screen is because of the sound. The screen remained blank the whole time

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/Xorg
Package: xserver-xorg-core 2:1.5.2-2build1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
ProcEnviron:
 PATH=/sbin:/bin:/usr/sbin:/usr/bin
 LANG=en_CA.UTF-8
ProcVersion: Linux version 2.6.27-7-generic (buildd@palmer) (gcc version 4.3.2 (Ubuntu 4.3.2-1hostname10) ) #1 SMP Fri Oct 17 22:24:21 UTC 2008

Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 DRICloseScreen ()
 I830WaitLpRing ()
 I830Sync () from /usr/lib/xorg/modules/drivers//intel_drv.so
 ?? () from /usr/lib/xorg/modules/drivers//intel_drv.so
 ?? () from /usr/lib/xorg/modules/drivers//intel_drv.so
Title: Xorg crashed with SIGSEGV in DRICloseScreen()
Uname: Linux 2.6.27-7-generic i686
UserGroups:

xkbcomp:

Revision history for this message
jerryb (gerald-britton) wrote :
tags: added: need-i386-retrace
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed, since the report is ill-formed. Perhaps the report data got
modified?

  need more than 1 value to unpack

If you encounter the crash again, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

Changed in xorg-server (Ubuntu):
status: New → Invalid
tags: removed: need-i386-retrace
Revision history for this message
jerryb (gerald-britton) wrote : Re: xio fatal error 104 on compiz --replace on intel i830

When I first filed this report, almost eight months ago, I submitted more than 4 megabytes of tracebacks, configs, logs and associated data. Now, almost eight months later, I am being asked for an i386-retrace, whatever that is and however one produces such a thing. It frankly challenges my credibility that there is nothing useful in the previously-submitted tracebacks and I am very frustrated by the eight-month time gap.

What specific part of the report is ill-formed? I just read each attachment from my October posting without issue.

Changed in xorg-server (Ubuntu):
status: Invalid → New
Bryce Harrington (bryce)
tags: added: crash
Changed in xorg-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

There have been a number of changes to the intel graphics stack, touching the kernel, mesa, libdrm and xserver-xorg-video-intel. You should test 9.10 alpha3 to see if compiz works there. Seeing that your chip is 845 might still mean that it's a 'no'.

visibility: private → public
affects: xorg-server (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Incomplete
summary: - xio fatal error 104 on compiz --replace on intel i830
+ [i845] xio fatal error 104 on compiz --replace on intel i830
Bryce Harrington (bryce)
tags: added: intrepid
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → Invalid
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.