[i965GM] X crashed when running a shockwave test file in Firefox 3.5 within wine.

[Dave Uggla]

Binary package hint: xserver-xorg-video-intel

I installed Firefox 3.5 into wine from Mozilla download page, then installed the Adobe Shockwave Player ( not Flash).

When I loaded the page http://www.adobe.com/shockwave/welcome/ to test the Shockwave player, the page displayed briefly with the Shockwave test, but X immediately crashed.

The information from the xserver package is included in this report.

Dave Uggla

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-video-intel 2:2.6.3-0ubuntu9.3
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-15-generic (buildd@yellow) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009
SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.28-15-generic x86_64

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
     Subsystem: Gateway 2000 Device [107b:0690]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03)
     Subsystem: Gateway 2000 Device [107b:0690]

[Dave Uggla (dave-uggla)]

FYI, the X crash is reproducible on the same machine by accessing the same test web page using Firefox under wine. I have not tried other kernel or Ubuntu versions, but can if there is any suspicion that some other version is better.

Dave Uggla

[Geir Ove Myhr (gomyhr)]

Could you try to get a full backtrace? There is some explanation for how to do this (it's a bit messy, since there are many ways to do it and not all will work in all situations). My favourite way is to do
sudo /etc/init.d/gdm stop
ulimit -c unlimited
sudo /etc/init.d/gdm start
from a VT to enable core files (see under post-mortem backtrace)
and then analyze the core file with
sudo gdb /usr/bin/Xorg /etc/X11/core 2>&1 | tee gdb-Xorg.txt
(gdb) backtrace full
(gdb) quit
And then upload then upload the file gdb-Xorg.txt.
If you are not able to create a core file you may try some of the other tricks mentioned on that page.

[Geir Ove Myhr (gomyhr)]

Actually, I didn't see before that this bug is reported for Jaunty. At this point in time we don't give priority to do troubleshooting for Jaunty issues, since we're working to make Karmic as bug free as possible. Could you check if this bug is still present in Karmic? You may download alpha-6 from http://cdimage.ubuntu.com/releases/9.10/ and use a LiveSession instead of installation if you'd like.

[Dave Uggla (dave-uggla)]

I have already tried to reproduce with alpha-6, AMD64, live session, and the problem was not seen.

For other reasons, alpha-6 is not a good working environment for me yet, so I will just be careful what I do in Jaunty. If you would still like a backtrace for the problem in Jaunty, just let me know and I will work on getting it.

[Dave Uggla (dave-uggla)]

I have now upgraded to Karmic and am experiencing a different X bug (Bug 472271) which occurs randomly without wine or other large applications running. So I am no longer concerned with this bug in Jaunty.

Thanks

[Geir Ove Myhr (gomyhr)]

This bug report has been inactive for quite some time and in the meantime Ubuntu has moved along. I hope the reported problem has been resolved in the current version of Ubuntu. If it has not and there are people willing to follow up with information collecting and testing, it is best to file a new bug report with the latest Ubuntu development version (10.04 still works, but soon 10.10 is better), using the ubuntu-bug command if possible. Feel free to mention the bug number of this bug.

We are sorry that we are not always have the capacity to look at all reported bugs in a timely manner. Occasionally we have to purge old bug reports where no progress has been made, whether it is due to reporter not being able to respond or lack of manpower on the Ubuntu side, in order to keep our list of "active" bugs current. Sorry for the inconvenience this may cause.

Here are a few tips that will make it easier for triagers and developers to process your bug:
* Read https://wiki.ubuntu.com/X/Reporting
* Browse https://wiki.ubuntu.com/X and see if there is some relevant information for you problem
* Respond quickly to questions from triagers
* Try changing things to see if the behaviour changes, e.g.
  * A new mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D (more information at https://wiki.ubuntu.com/KernelTeam/MainlineBuilds)
  * The xorg-edgers PPA: https://launchpad.net/~xorg-edgers/+archive/ppa
  * Various options in `/etc/X11/xorg.conf` (see `man intel`)
* Browse other bug reports to see if you find a similar one and provide the information that is being asked for there.