compiz.real crashed with SIGSEGV in glXBindTexImageEXT()

[Jonathan Wheare]

Binary package hint: compiz

Crash occured while using alt+tab to move out of fullscreen World of Warcraft running under wine.
Ubuntu release Karmic alpha 5, x86-64

expected result:smooth cange in screens
actual result: long pause. apport popup, compiz restarted

ProblemType: Crash
Architecture: amd64
CompizPlugins: [core,ccp,dbus,place,mousepoll,gnomecompat,move,resize,decoration,png,svg,imgjpeg,text,neg,video,wall,snap,animation,scale,scaleaddon,expo,staticswitcher,regex,resizeinfo,workarounds,ezoom,vpswitch,extrawm,fade,session]
CurrentDmesg:
 Error: command ['sh', '-c', 'dmesg | comm -13 /var/log/dmesg -'] failed with exit code 1: [ 27.757525] eth0: no IPv6 routers present
 [ 9319.957760] npviewer.bin[4100]: segfault at ff99cd48 ip 00000000ff99cd48 sp 00000000ffa70f9c error 14
 comm: file 2 is not in sorted order
 [27764.046293] npviewer.bin[6579]: segfault at ff99cd48 ip 00000000ff99cd48 sp 00000000ff80cd2c error 14
 [30630.951404] compiz.real[6341]: segfault at 10 ip 00007fe7a77bef07 sp 00007fff30e5f6a8 error 4 in libGLcore.so.185.18.36[7fe7a6cc8000+dda000]
Date: Sun Sep 6 20:43:26 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/compiz.real
MachineType: Gigabyte Technology Co., Ltd. P35-DS3P
NonfreeKernelModules: nvidia
Package: compiz-core 1:0.8.2-0ubuntu16
PccardctlIdent:

PccardctlStatus:

PciDisplay: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G92 [GeForce 8800 GTS 512] [10de:0600] (rev a2)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-9-generic root=/dev/sdb1 ro quiet splash
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --sm-client-id 10de1b27a1b1d055b9125223232440063900000061990022 --loose-binding gconf core ccp
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3
 libdrm2 2.4.12+git20090801.45078630-0ubuntu1
 xserver-xorg-video-intel 2:2.8.1-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7fe7a77bef07: mov 0x10(%rdi),%rax
 PC (0x7fe7a77bef07) ok
 source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? () from /usr/lib/libGLcore.so.1
 ?? () from /usr/lib/libGLcore.so.1
 ?? () from /usr/lib/libGLcore.so.1
 ?? () from /usr/lib/libGLcore.so.1
 glXBindTexImageEXT () from /usr/lib/libGL.so.1
Title: compiz.real crashed with SIGSEGV in glXBindTexImageEXT()
Uname: Linux 2.6.31-9-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/07/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: P35-DS3P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd09/07/2007:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
system: distro = Ubuntu, architecture = x86_64, kernel = 2.6.31-9-generic

[Apport retracing service (apport)]

StacktraceTop:?? () from /usr/lib/libGLcore.so.1
?? () from /usr/lib/libGLcore.so.1
?? () from /usr/lib/libGLcore.so.1
?? () from /usr/lib/libGLcore.so.1
glXBindTexImageEXT () from /usr/lib/libGL.so.1

[Travis Watkins (amaranth)]

This is crashing deep inside the nvidia driver.

[PaulW (paulw)]

In response to Travis Watkins...

This seems to be happening to me too, but under mutter...

[ 158.817344] mutter[2701]: segfault at 10 ip 00007fc350097f07 sp 00007fff1039fa88 error 4 in libGLcore.so.185.18.36[7fc34f5a1000+dda000]
[ 1708.958019] mutter[4335]: segfault at 10 ip 00007ff5e3815f07 sp 00007fffea2cc878 error 4 in libGLcore.so.185.18.36[7ff5e2d1f000+dda000]

Happens quite regularly too, so I'm guessing its something the nvidia driver is having issues with in regards to compositing...

[Victor (psycovic)]

This happens to me whenever I undock my laptop. VERY annoying having to restart compiz all the time.

[Luke J Militello (kilahurtz)]

Was searching for an answer to this problem since we were getting know response from another bug and I stumbled upon this one. So I tagged the bug I was working off of as a duplicate of this one. https://bugs.launchpad.net/ubuntu/+bug/495121

I, as well as others, confirm this IS a problem.

[Luke J Militello (kilahurtz)]

Tagged another as a duplicate: https://bugs.launchpad.net/ubuntu/+bug/454057

[Luke J Militello (kilahurtz)]

I'm currently running Nvidia's driver for this and still having an issue (190.53). I'm going to upgrade to 195.36.15 tomorrow and test that out and see how it goes.

[Luke J Militello (kilahurtz)]

Upgraded to 195.36.15 and all is going well so far.

[Luke J Militello (kilahurtz)]

Nvidia driver 195.36.15 seems to be working so far. When coming out of the screensaver it stalls for maybe 3-5 seconds, but I'll take that over a crash. Can anyone else test this out?

[Luke J Militello (kilahurtz)]

Had a crash the other day using 192.36.15. :(

[Cory Coager (ccoager)]

Luke - Did you upgrade to Lucid Lynx to test driver version 192.36.15?

[Luke J Militello (kilahurtz)]

No, installed the driver straight from Nvidia. Still running Karmic as Lucid will "break" a lot of things...waiting for at least 10.04.1 before I upgrade.

[Cory Coager (ccoager)]

I gave up on waiting and just upgraded to Lucid Lynx, hopefully this release doesn't have the same issue.

[Cory Coager (ccoager)]

Just got a crash in 10.04.

[Luke J Militello (kilahurtz)]

I'm confirming this for Lucid. I just experienced a crash also on 10.04. It seems no one from the dev team would acknowledge this when it was brought to attention as a problem with Karmic. Now, since we are on an LTS, this NEEDS ATTENTION!!!

[Luke J Militello (kilahurtz)]

Really getting tired of this...why is it that no one seems to care or help with this issue? I leave my machine on and it completely sucks when I unlock my screen to discover compiz has crashed and all my windows have been dumped to one screen. I then have to close everything, logout, login and set every back up they way I had it before. This is a pain especially when I have numerous windows open while in the middle of working on a project...PLEASE HELP!!!

[Pebas (pebasmisc)]

I upgraded to lucid (switched back to 32bits) and compiz stop crashing (tested for over a month now).
I don't know if it has something to do, but I didn't install package compiz-fusion-plugins-extra this time.

Hope it helps.

Currently using Lucid Lynx 10.04 32bits 2.6.32-22-generic, Compiz 1:0.8.4-0ubuntu15, NVIDIA Driver Version: 195.36.15

[Cory Coager (ccoager)]

Upgraded to nvidia 195.36.24 yesterday, will see how it goes.

[Cory Coager (ccoager)]

Got another crash this morning on nvidia 195.36.24.

[Luke J Militello (kilahurtz)]

You shouldn't have to revert to 32-bit or opt not to install a package to get it to function properly. Although, your efforts will help in locating where the problem is; the bottom line is someone needs to acknowledge this and fix it. Someone obviously wrote the bad code and needs to take ownership and fix it. I'm not trying to down talk anyone here as this is all open source and created based on people donating their time and their expertise, but I have been plagued by this problem since the release of Karmic. And since it has been confirmed by others in Lucid (an LTS), I would think someone would want to help us resolve this issue.

On a personal note, I think Ubuntu is getting to far ahead of itself. In the recent releases, I believe there has been far too many new things added (including new bugs) and not enough fixing of the existing problems. This is taking away from what Ubuntu was originally promised to be, a user-friendly rock-solid operating system. I'm almost to the point to where I might switch to back Debian. To date, I believe Hardy is, was, and always will be the best Ubuntu release unless things start to change.

[Hans Riba (heinzketchup)]

Luke,

two things:

1.) I also have that issue, but on a Debian system. Todays up-to-date sid, but having it since half a year or so. Very annoying.

2.) The nvidia drivers are NOT open source. Fixing of this bug solely depends on the mercy of NVIDIA. This sucks and this is why this proprietary crap sucks. If it were open source, Ubuntu or Debian or other people could help you. Now they can't. Blame it on NVIDIA. (Or, indirectly, on Ubuntu, for including this crap. By not including it, the pressure on NVIDIA would be higher to release the stuff as open source, which would have ultimately already fixed this issue. For all of us.)

[Luke J Militello (kilahurtz)]

I hate sounding like a broken record, down talking the community and the last thing I want to do is sound like an @$$hole, but this is sort of what I wanted to here. That this IS confirmed as an issue with NVidia and not and issue with compiz itself. If that is the case, that's all someone had to say. Wish I would have gotten a straight answer like this months ago. Guess I'll just keep updating NVidia drivers until, hopefully, one fixes it. I greatly appreciate your reply and for taking the time to explain it. Thanks! :)

[Hans Riba (heinzketchup)]

Well, in order to give this straight answer and confirm the problem, people have to reproduce it. Maybe not so many people could, and you can't blame anyone for that. Plus, since this is proprietary crap, people don't try so hard. Why should they, they can't fix it anyway. So why waste time by debugging closed source stuff? This may have downgraded priority further.

Finally, one needs to sign up at launchpad for comments here (unlike the Debian bug tracking system where a mail is enough). I didn't have an account here before. I just wasted a couple of minutes creating one because I saw you are so desperate.

Good luck with your(our) problem. Do you have some work around? Some other screensaver or sth. that works instead?

[Luke J Militello (kilahurtz)]

Thanks again. Nope, no workaround other than not using compiz or not using a screensaver. The latter I view as a security vulnerability, so I guess I have to live with the crashing...compiz --replace does not work either. :(

[Luke J Militello (kilahurtz)]

I upgraded to v256.44 tonight,...we shall see how it goes...

[Luke J Militello (kilahurtz)]

It appears this version (v256.44) has fixed all my problems. I'll give it another month to be sure, but I haven't had a single crash since my last post!

[Cory Coager (ccoager)]

I upgraded to v195.36.24-0ubuntu1. I had a couple crashes but its much more stable than previous versions.

[Luke J Militello (kilahurtz)]

Sadly, I just had a crash. :(

Although, it is very rare as compared to before. In fact this was the only time I moved the mouse to wake it up. Every other time has been via keyboard. Perhaps, once again, mouse movement has something to do with it. I will test this out over the next few weeks.

[Cory Coager (ccoager)]

So its been a month now and no crashes. This one may be fixed now!

[u-foka (ufooka)]

Sadly I have same crashes on maverick :(

[Luke J Militello (kilahurtz)]

So I haven't had any problems since switching to a non-OpenGL screensaver and running v260.19.21. I can live with this. As long as the screen locks, screensaver runs and compiz doesn't crash -- I'm happy.

[u-foka (ufooka)]

But I don't have an OpenGL screensaver, and never had... :(

[Alin Andrei (nilarimogard)]

This has not been fixed in Maverick either... it still crashes.

[u-foka (ufooka)]

Hy!

Here is my backtrace [1] and valgrind log [2] of a (seems) similar problem but with nvidia drivers 260 from maverick...

[1]: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/670592/comments/15
[2]: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/670592/comments/16

[jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount)]

Hi, any that are affected. Is this issue still present in newer Ubuntu versions?

Also, since this crash occurs with Mutter as well, it's obviously not compiz's issue. If it is still existant, please raise this issue up to nvidia (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14.

Thanks!

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.