crashing xorg. unstable behaviour

Bug #64331 reported by gcranston
4
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.22 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-glx

Running edgy on Dell Inspiron 2650, with nVidia GeForce2 Go. Running TwinView

Many stability problems in X/gnome which only present when running accelerated graphics.

1. Gnome doesn't start properly on both monitors. Have to kill gdm and restart it. Otherwise, secondary (built in) screen displays two gray bars and nothing else but still exists (I can move my mouse off the primary screen). Restarting gdm allows for functioning TwinView.

2. Cannot use consoles. ctrl-alt-fX goes to console, but type is so dim it cannot be read. Cannot switch back to console 7 (xorg)

3. Cannot shutdown properly. Gnome appears to unload, then second screen goes black, primary screen goes black then displays a number of coloured blocks

I will attach photos of this behaviour since I can't screendump. Also my xorg logs (all).

I realise you probably need more info than this so point me in the right direction and I'll try to get it.

Using latest edgy packages. Behaviour has been present since Dapper at least, if not Breezy. Never reported before because I didn't know enough about the problem to explain it.

Revision history for this message
gcranston (gcranston) wrote :

xorg logs

Revision history for this message
gcranston (gcranston) wrote :

xorg logs

Revision history for this message
gcranston (gcranston) wrote :

config

Revision history for this message
gcranston (gcranston) wrote :

Correction:

Switching to console produces the same behaviour as shutdown. Coloured blocks and system hangs. Must be forced shut down.

Revision history for this message
gcranston (gcranston) wrote :
Revision history for this message
Wolvie (richard-smetco) wrote :

Hi,

I'm also seeing exactly the same behavior when using nvidia-glx drivers on my Inspiron 2650 running Ubuntu Edgy (and Dapper).

While it is possible to use X with these drivers (by restarting GDM), the additional problems when changing to consoles, and on shutting down the computer really are a pain (to say the least).

It would be really great to find a fix to this.

Please let me know if you need any further information from me.

Thanks.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Old bug, most likely fixed in a newer release.

Changed in linux-restricted-modules-2.6.17:
status: New → Invalid
Revision history for this message
gcranston (gcranston) wrote :

Old, yes. Fixed, NO!

Please don't close this bug or call it invalid; I still have this unstable behaviour in Gutsy.

Nothing has been fixed. Given that the both reported instances were on a Dell 2650, I'm guessing this is a hardware specific problem. Wolvie do you still have this problem? Do you still have that machine?

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

you need to try Hardy, and if it's still broken then we'll reopen this.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

hmm you are using gutsy, so bumping the version. Btw, Wolvie is not subscribed to this bug.

Changed in linux-restricted-modules-2.6.17:
status: Invalid → Incomplete
Revision history for this message
Connor Imes (ckimes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
gcranston (gcranston) wrote :

I have retired the (laptop) machine that exhibited this behaviour. I certainly haven't seen it with my new(er) machine, running Hardy. I'm thinking it was a hardware specific problem. Given that machine is 6 years old, you may not see any more reports for this one. I do have an identical machine running Hardy, but not TwinView that I could try to see if I still get those problems, but it may take some time.

Revision history for this message
Connor Imes (ckimes) wrote :

OK, I will close this bug since you can't provide information as to whether this is fixed, and nobody else has confirmed it with the same hardware in any Ubuntu release. Please reopen it if you can give us the missing information (like if you try the TwinView with your other identical laptop and find it has the same problem), 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!

Changed in linux-restricted-modules-2.6.22:
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.