[nvidia] GL xscreensavers crashed

It happened a second time (I still wasn't there, but how much interaction would I have with a screensaver anyway)
I have a second core dump though

Here's another dump

Setting to Critical priority due to large number of dupes. It has a fairly obvious and effective workaround (disable xscreensaver) but it is likely whatever the root cause is may afflict other GL apps as well.

I think this is unlikely to receive a fix until 8.04.1 at the earliest, but I'm milestoning to 8.04 so we can give it some priority attention before Hardy to at least understand *why* it is failing. Once we understand the issue and have a plan of attack, the bug can be re-milestoned to 8.04.1 for the actual fix.

The one other piece of information needed to begin troubleshooting is a backtrace. Can someone who is experiencing this bug please install the xserver debug packages, and then obtain a full backtrace? Directions are available at http://wiki.ubuntu.com/X/Backtracing.

per the description, then, milestoning this for 8.04.1 rather than 8.04 and targetting to hardy.

If nobody beats me to this, I will attempt to obtain a backtrace from this this weekend.

No promises, as it's not guaranteed to crash. :/

Is anyone still having this bug with the released Hardy?

Another thing to check is to try running a newer version of -nvidia. If we know for certain that a newer -nvidia fixes this issue, it could potentially be considered for 8.04.1.

I haven't seen it since release - the only time I saw it was straight after the upgrade from gutsy.

Oh yes, I have. As of yesterday, it is still happening.

I have the latest Hardy, but after some hours of leaving the computer unattended, the process compiz.real gobbles up a shitload of memory (~ 0,5 - 1 GB) and the X system gets so slow that it's unusable.

My quick fix is to switch to the console, kill -9 compiz.real and switch back to X, but it this not satisfying.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Pat Leamon
Sent: Wednesday, April 30, 2008 10:03 AM
To: <email address hidden>
Subject: [Bug 110125] Re: [nvidia] GL xscreensavers crashed

I haven't seen it since release - the only time I saw it was straight
after the upgrade from gutsy.

--
[nvidia] GL xscreensavers crashed
https://bugs.launchpad.net/bugs/110125
You received this bug notification because you are a direct subscriber
of a duplicate bug.

I do have the bug, but I'll try to upgrade the -nvidia to see if it's still there.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Bryce Harrington
Sent: Wednesday, April 30, 2008 9:05 AM
To: <email address hidden>
Subject: [Bug 110125] Re: [nvidia] GL xscreensavers crashed

Is anyone still having this bug with the released Hardy?

Another thing to check is to try running a newer version of -nvidia. If
we know for certain that a newer -nvidia fixes this issue, it could
potentially be considered for 8.04.1.

--
[nvidia] GL xscreensavers crashed
https://bugs.launchpad.net/bugs/110125
You received this bug notification because you are a direct subscriber
of a duplicate bug.

I have "a" bug....not sure if it is the same thing....but when switching hacks my x-server restarts ever since i installed the nvidia drivers.
It appears to be the GL hacks that r doing it.
And on a side note, games that worked before are now not working.
Therefore i believe that whatever problem there is it is affecting the other GL apps.

PS: This is my first linux: 8.04 so I dont know much about anything yet. (and to make matters worse i have no programming knowledge)

No problem anymore. It happened only once just after update from Gutsy to Hardy.

Hmm, ok sounds like for at least some people the issue is resolved. emk2203, I'm curious if you have the crash after fully updating Hardy - you mentioned upgrading -nvidia, do you mean to Hardy's latest or to a newer version from nVidia?

Merlin, I can't say for sure if you have the same issue as everyone else, although it does sound roughly similar. It's possible we have more than one bug going around though.

Anyway, given that it seems the issue has resolved for at least some people, I'm going to drop the milestone. I suspect we have a case of a core main issue plus some similar secondary issues, and that the main issue resolved.

I'm having the same problem with ALL GL/GLX apps: screen savers, games, compiz... I have a fully updated Hardy installation, using an nVidia GeForce 5200 AGP card w/ 128MB RAM. I'm using the EnvyNG nvidia installation & drivers since using the standard restricted nvidia drivers was a disaster (screen locked in at 800x600 res and the monitor wasn't properly recognized. The EnvyNG installation seems to have effectively installed and configured the video system utilizing the latest drivers, but the GL functions simply don't work.

As an example, when I was using the generic 'nv' video driver immediately after performing a clean Hardy install, all of the screen savers worked, but some were very slow. After installing the nVidia drivers utilizing EvnyNG none of the GL screen savers worked. Also, I recently checked the '3D' tab on the included Chess program (which was working just fine in 2D); the Chess program attempts to load, and then immediately shuts down without showing the game board.

I suspect the problem is with software, and not hardware, since this is a dual-boot machine and the accelerated video in WinXP works perfectly.

my laptop hp 6220br is also "Freeze" locking on several different occasions

Can you enable the hardy-proposed and hardy-updates repositories, install EnvyNG so as to install the latest release of the driver?

If it doesn't solve the problem, you should report the problem here:
http://www.nvnews.net/vbulletin/forumdisplay.php?f=14

Heya who_cares,

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.