Writing to the gtk textview buffer crashes xorg

Bug #49834 reported by Florian Köberle
186
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.15 (Ubuntu)
Invalid
Undecided
Unassigned
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Woraround: Use the opensource or the nvidia-legacy driver

Activate the description expander in update-manager to get a crash.

---

Kernel 2.6.15-25-386, nvidia-glx 1.0.8762+2.6.15.11-2, update-manager 0.42.2ubuntu22.
Xorg.log reads:

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x86) [0x80b4a56]
1: [0xffffe420]
2: /usr/bin/X [0x813bd86]
3: /usr/bin/X [0x813e70e]
4: /usr/bin/X(Dispatch+0x19e) [0x8085d26]
5: /usr/bin/X(main+0x47c) [0x806e0a8]
6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7d23ea2]
7: /usr/bin/X(FontFileCompleteXLFD+0x81) [0x806d611]

Fatal server error:
Caught signal 11. Server aborting

Revision history for this message
Florian Köberle (iflo) wrote :

the only package wich is marked for update is kate. Maybe the kate update has a desciption text which crash the xserver. (the update function has worked yesterday)

Revision history for this message
Florian Köberle (iflo) wrote :

the update manager has two tabs:
"Änderungen" (changes) and "Beschreibung" (description)

When I click on "Beschreibung" tab before the changes text is loaded then the xserver doesn't crash. After this i can click the "Änderungen" tab without a crash.

Revision history for this message
Martin Pitt (pitti) wrote :

This is most likely a bug in the graphic driver. Which one do you use? Do you use a binary-only driver like fglrx or nvidia?

Revision history for this message
Florian Köberle (iflo) wrote :

I use still the Package nvidia-glx as grapthic driver. (See comment in: https://launchpad.net/distros/ubuntu/+source/xserver-xorg/+bug/47122)

Revision history for this message
Florian Köberle (iflo) wrote :

When i use nv as graphic driver it works without crash.

Revision history for this message
Martin Pitt (pitti) wrote :

Hm, there is little we can do then, I'm afraid.

Revision history for this message
Florian Köberle (iflo) wrote :

with the current (2006-07-06) update it is the same. ("Clicking the description tab" to avoid the x-Server works here too)

packages marked for update: login, passwd, ppp

Changed in nvidia-glx:
status: Needs Info → Unconfirmed
description: updated
Revision history for this message
Florian Köberle (iflo) wrote : Re: Crash if the expander in update-manager gets activated

"Activate the description expander in update-manager to get a crash."

Thats not true for me!!!!!!!!! (The Reporter of the Bug)

It doesn't crash when I click on the description expander! (thats the way how to avoid this bug)

The only thing I have to do to produce the crash is starting the updatemanager. (when i am fast and click the description expander it doesn't crash. Even when I click later on the changes expander.)

Revision history for this message
Pieter Nagel (pieter-equinox) wrote :

It seems this bug has been reported to upstream at http://www.nvnews.net/vbulletin/showthread.php?t=73033. AFAIK those are the "official" Nvidia/Linux forums.

From that post, it seems this bug is actually a duplicate #47122

Revision history for this message
Lukas Winter (webmaster-geloescht) wrote :

After switching to nvidia-glx-legacy instead of nvidia-glx, the crash disappeared for me (both drivers support my card). So the older driver did not have this bug.

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: [Bug 49834] Re: Writing to the gtk textview buffer crashes xorg

 unsubscribe ubuntu-security

Revision history for this message
Ajay (ajay-s-linux) wrote :

Lonni from Nvidia gave a super quick reply after I shot of a mail to linux-bugs, after filing a report here (turned out to be a dupe of this report, dont know how I missed this one)

There is a post on nvnews tracking the status of this bug, so I tought it relevant to post a link to it here

http://www.nvnews.net/vbulletin/showthread.php?t=73033

description: updated
Revision history for this message
Onno Timmerman (onno-filosofie) wrote :

Today I got again this bug. Seems each time some packedes from KDE are involved. Updating via apt-get. I believe each time it happens something of KDE needs to be updated!

Instellen van kdelibs-data (3.5.2-0ubuntu18.1) ...

Instellen van kdelibs-bin (3.5.2-0ubuntu18.1) ...
Instellen van kdelibs4c2a (3.5.2-0ubuntu18.1) ...

Revision history for this message
David Planella (dpm) wrote :

I don't think it's got anything to do with kde packages.

Although I got the same issue yesterday when upgrading the kde packages, last time I saw this, it happened to me when updating a kernel package.

Revision history for this message
Alan (alanrr-sr-yahoo) wrote :

I am getting this error to...same steps as decribed by Florian Köberle:
- click on the update icon
- enter your password
- wait unitl it is loaded
- without doing anything, you should get now the login promt (xserver has crashed)

The error is not continum for me. It happens a lot of time, but sometimes everything works fine.
Extra detail: Nvidia user too and 2 Xservers.

Revision history for this message
Christian Reis (kiko) wrote :

Fixing up package name, but note that this bug was originally reported on the nvidia-glx binary package.

Revision history for this message
Florian Köberle (iflo) wrote :

When it is the same bug like this:
https://launchpad.net/distros/ubuntu/+bug/47122

then there are three ways of avoiding this bug:
- install the most current NVIDA driver( >= 1.0-8776): http://www.nvidia.com/object/linux_display_ia32_1.0-8776.html
- install the beta driver of NVIDIA(>= 1.0-9625):
http://www.nzone.com/object/nzone_downloads_linux_display_x86_1.0-9625.html
- use the "nv" driver instead of "nvida"

If this is the case, then there is a exploit for this bug!

Revision history for this message
Phil Bull (philbull) wrote :

Have there been any developments with this bug? Does anyone still have this issue?

I'm rejecting this bug for now, as it seems to be due to a closed-source package we have no control over. Please feel free to reopen the bug if you have any further information.

Changed in xorg:
status: Unconfirmed → Rejected
Changed in linux-restricted-modules-2.6.15:
status: Unconfirmed → Rejected
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.