[r300] GL screen saver locks up entire system

Thanks for your bug report. The first one on the list, do you mean the "4D Hypertorus" ?
From bug #58963:
This could be a problem with some 3D screensavers taking down your machine. It is probably nothing wrong with gnome-screensaver itself, but your video drivers. What kind of hardware (esp. graphic card) do you have?

Can you please try running "/usr/lib/xscreensaver/hypertorus" in a Terminal window, and see if it crashes your machine?

Hello from Pensacola FL,

Radeon 9700 Pro, and running hypertorus manually works fine. (Nice looking too! & Now I have some better troubleshooting knowledge). Any individual Screensaver selected (below Random) locks me up. Have to reboot & go into the (finally found) Configuration Editor to reset the selection to Blank or Random, or the system will also lockup when the screensaver operates on time. (I was beginning to think only the system could select individual screensavers and the list was just to let you know what would show up Randomly!)

DES
  ----- Original Message -----
  From: Tormod Volden
  To: <email address hidden>
  Sent: Thursday, October 19, 2006 3:02 PM
  Subject: [Bug 60438] Re: Changing Screen Saver locks up entire system

  Thanks for your bug report. The first one on the list, do you mean the "4D Hypertorus" ?
  >From bug #58963:
  This could be a problem with some 3D screensavers taking down your machine. It is probably nothing wrong with gnome-screensaver itself, but your video drivers. What kind of hardware (esp. graphic card) do you have?

  Can you please try running "/usr/lib/xscreensaver/hypertorus" in a
  Terminal window, and see if it crashes your machine?

  ** Changed in: gnome-screensaver (Ubuntu)
         Status: Unconfirmed => Needs Info

  --
  Changing Screen Saver locks up entire system
  https://launchpad.net/bugs/60438

Does for instance "Deco" also crash ? (One surely without 3D graphics). Can you please look through /var/log/syslog to see if there were any error messages? Please attach /var/log/Xorg.0.log.old just after rebooting from the crash.

OK, as per instructed just after rebooting from crash (don't see any Error messages in syslog) here's the other.

I ran antspotlight in the Terminal and got this there...

*******************WARN ONCE**********************
file r300_state.c function r300Enable line 456
TODO - double side stencil!
**************************************************
no ctx->FragmentProgram._Current!!
*******************WARN ONCE**********************
file r300_render.C function r300_get_num_verts line 193
user error: 33 is not a valid number of vericles for primitive QS!
***************************************************

As best jotted down by hand, system was locked (mouse moves!).

And thinking gee, if Random means getting one that can crash the system I'll just set it to hypertorus which worked. I did, and it was looking good in the sample display (thumbnail, whatever you call it). Then it stopped moving and had locked up as I said originally. Just took a while this time!

Hope this helps? DES

  ----- Original Message -----
  From: Tormod Volden
  To: <email address hidden>
  Sent: Thursday, October 19, 2006 5:25 PM
  Subject: [Bug 60438] Re: Changing Screen Saver locks up entire system

  Does for instance "Deco" also crash ? (One surely without 3D graphics).
  Can you please look through /var/log/syslog to see if there were any
  error messages? Please attach /var/log/Xorg.0.log.old just after
  rebooting from the crash.

  --
  Changing Screen Saver locks up entire system
  https://launchpad.net/bugs/60438

Does Deco crash? And we are still waiting for that /var/log/Xorg.0.log.old :)

No Deco doens't crash.

Sent Xorg.0.log.old as attachment this afternoon in reply to your pervious message together with error reflected in terminal from trying antspotlight that locked system. Message bounced, took as acknolegement. And I see that message posted @ bug report. Also sent Harware Manager images, syslog, & previous Xorg.0.log.old earlier, no indication of this message at all? Attachments are being stripped? Some messages get through some don't? Advise how to get these to you as this work is typically deleted after sending and will now have to be repeated.

DES
  ----- Original Message -----
  From: Tormod Volden
  To: <email address hidden>
  Sent: Friday, October 20, 2006 3:09 PM
  Subject: [Bug 60438] Re: Changing Screen Saver locks up entire system

  Does Deco crash? And we are still waiting for that
  /var/log/Xorg.0.log.old :)

  --
  Changing Screen Saver locks up entire system
  https://launchpad.net/bugs/60438

Please try the web interface, it has a Add comment/attachment button at the bottom.

OK... here's that log, just after locking up with antspotlight as above. (I only have to switch back to WinXP and log in here in IE! As FF won't log in in either OS? A bit rediculous, but whatever.)

And you'd ask about hardware earlier. Here's an image from the WIndow's Device Manager. All this is hooked to an Asus P4T533C MB.

It is already bad enough that Launchpad is proprietary software, but that you have to use proprietary software to access it, that's too much :) Maybe you have to clean out some cookies in Firefox?

For the hardware summary, it would be even better if you run "lspci > lspci.txt" and attach lspci.txt, as this gives more precise information. Thanks for the log!

You will probably get rid of the crashes if you add: Option "NoDRI"
to the "Device" section of your /etc/X11/xorg.conf . Can you please try that?

What a goof! New to FF too you see, and Cookie Management, while vastly improved over IE & Webroot's WindowWasher Cookie Keeper function requires 'different logic'. Ah, Launchpad now Unblocked! (To be fair though, FF won't Logon to Much, even my own Linksys router!)

Back on track... suggested addition to xorg.conf "Device" section Option "No DRI" changes nothing. Would you then leave this modification, or remove it?

DES

There might be a bug in the driver so that it doesn't honour the "NoDRI" option. Can you comment out (add a # in front of) the Load "dri" and Load "glx" lines in your xorg.conf? And attach the Xorg.0.log from after restarting X (log out and press ctrl-alt-backspace), so that we can check that DRI is disabled.

That might save you from the crashes. The downside is that the fancy screeensavers (and other 3D applications) won't be fancy anylonger...

Won't run at all you mean:

des421@El-Diablo:~$ /usr/lib/xscreensaver/antspotlight
Xlib: extension "GLX" missing on display ":0.0".
(14 times)
antspotlight: display ":0.0" does not support the GLX extension.
des421@El-Diablo:~$

Advise on removing or keeping these now 3 changes before something gets seriousyu goofed.

Donald, do you experience the same issues in 7.04?

Never updated passed the Dapper Drake.
  ----- Original Message -----
  From: Tormod Volden
  To: <email address hidden>
  Sent: Tuesday, June 05, 2007 1:09 PM
  Subject: [Bug 60438] Re: [r300] GL screen saver locks up entire system

  Donald, do you experience the same issues in 7.04?

  ** Changed in: xserver-xorg-video-ati (Ubuntu)
       Assignee: (unassigned) => Tormod Volden

  --
  [r300] GL screen saver locks up entire system
  https://bugs.launchpad.net/bugs/60438
  You received this bug notification because you are a direct subscriber
  of the bug.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!