Kinfocenter crashes when the "OpenGL" information panel is selected

Bug #58734 reported by phisrow
32
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Crash occurs in a clean install of edgy knot2 within a vmware virtual machine.

The crash occurs reliably when one opens Kinfocenter and selects the OpenGL pane.

Backtrace:

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1237604688 (LWP 4160)]
[KCrash handler]
#6 0xffffe410 in __kernel_vsyscall ()
#7 0xb7d59760 in *__GI_raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb7d5aee3 in *__GI_abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7d8eceb in __libc_message () from /lib/tls/i686/cmov/libc.so.6
#10 0xb7d96b2a in *__GI___libc_free () from /lib/tls/i686/cmov/libc.so.6
#11 0xb6582f5d in XFree () from /usr/lib/libX11.so.6
#12 0xb5e969b0 in __glXFreeContext () from /usr/lib/libGL.so.1
#13 0xb5e96b0f in __glXFreeContext () from /usr/lib/libGL.so.1
#14 0xb5f8b5c3 in get_gl_info (dpy=0x83b5340, scrnum=138105664,
    allowDirect=1, l1=0x83b0920, after=0x0)
    at /build/buildd/kdebase-3.5.4/./kcontrol/info/opengl.cpp:614
#15 0xb5f8ec1e in GetInfo_OpenGL (lBox=0x83b58e8)
    at /build/buildd/kdebase-3.5.4/./kcontrol/info/opengl.cpp:652
#16 0xb5f7fcba in KInfoListWidget::load (this=0x83c9968)
    at /build/buildd/kdebase-3.5.4/./kcontrol/info/info.cpp:366
#17 0xb5f86b14 in KInfoListWidget (this=0x83c9968, _title=@0xbf9cce98,
    parent=0x0, name=0xb5f97058 "kcminfo",
    _getlistbox=0xb5f8e8d0 <GetInfo_OpenGL(QListView*)>)
    at /build/buildd/kdebase-3.5.4/./kcontrol/info/info.cpp:430
#18 0xb5f90a47 in create_opengl (parent=0x0)
    at /build/buildd/kdebase-3.5.4/./kcontrol/info/main.cpp:135
#19 0xb7a37e01 in KCModuleLoader::load (mod=@0x8155550, libname=@0xbf9cd050,
    loader=0x81ad2a8, report=KCModuleLoader::None, parent=0x0,
    name=<value optimized out>, args=@0xbf9cd114)
    at /build/buildd/kdelibs-3.5.4/./kutils/kcmoduleloader.cpp:92
#20 0xb7a389f7 in KCModuleLoader::loadModule (mod=@0x8155550,
    report=KCModuleLoader::None, withfallback=true, parent=0x0, name=0x0,
    args=@0xbf9cd114)
    at /build/buildd/kdelibs-3.5.4/./kutils/kcmoduleloader.cpp:156
#21 0xb7a3b412 in KCModuleLoader::loadModule (mod=@0x8155550,
    withfallback=true, parent=0x0, name=0x0, args=@0xbf9cd114)
    at /build/buildd/kdelibs-3.5.4/./kutils/kcmoduleloader.cpp:118
#22 0xb7fa0464 in ConfigModule::module (this=0x8155528)
    at /build/buildd/kdebase-3.5.4/./kcontrol/kcontrol/modules.cpp:72
#23 0xb7fa0876 in ModuleWidget::load (this=0x81acf98, module=0x8155528)
    at /build/buildd/kdebase-3.5.4/./kcontrol/kcontrol/dockcontainer.cpp:116
#24 0xb7fa0934 in DockContainer::loadModule (this=0x8188820, module=0x8155528)
    at /build/buildd/kdebase-3.5.4/./kcontrol/kcontrol/dockcontainer.cpp:168
#25 0xb7fa0bd8 in DockContainer::dockModule (this=0x8188820, module=0x8155528)
    at /build/buildd/kdebase-3.5.4/./kcontrol/kcontrol/dockcontainer.cpp:222
#26 0xb7fa4f8e in TopLevel::activateModule (this=0x81439a0, mod=0x8155528)
    at /build/buildd/kdebase-3.5.4/./kcontrol/kcontrol/toplevel.cpp:426
#27 0xb7fa9295 in TopLevel::qt_invoke (this=0x81439a0, _id=73, _o=0xbf9cd324)
    at ./toplevel.moc:134
#28 0xb693982f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#29 0xb7f97c51 in IndexWidget::moduleActivated (this=0x8174320, t0=0x8155528)
    at ./indexwidget.moc:124
#30 0xb7fa5281 in IndexWidget::moduleSelected (this=0x8174320, m=0x8155528)
    at /build/buildd/kdebase-3.5.4/./kcontrol/kcontrol/indexwidget.cpp:66
#31 0xb7fa58ee in IndexWidget::qt_invoke (this=0x8174320, _id=52,
    _o=0xbf9cd414) at ./indexwidget.moc:147
#32 0xb693982f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#33 0xb7f97e5e in ModuleTreeView::moduleSelected (this=0x81cbb60,
    t0=0x8155528) at ./moduletreeview.moc:107
#34 0xb7f97ec7 in ModuleTreeView::slotItemSelected (this=0x81cbb60,
    item=0x81c3a68)
    at /build/buildd/kdebase-3.5.4/./kcontrol/kcontrol/moduletreeview.cpp:218
#35 0xb7f97fcc in ModuleTreeView::qt_invoke (this=0x81cbb60, _id=106,
    _o=0xbf9cd4f8) at ./moduletreeview.moc:126
#36 0xb693982f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#37 0xb6cddc7b in QListView::clicked () from /usr/lib/libqt-mt.so.3
#38 0xb6a36b1d in QListView::contentsMouseReleaseEventEx ()
   from /usr/lib/libqt-mt.so.3
#39 0xb6a36df8 in QListView::contentsMouseReleaseEvent ()
   from /usr/lib/libqt-mt.so.3
#40 0xb7b8ec13 in KListView::contentsMouseReleaseEvent (this=0x81cbb60,
    e=0xbf9cd7ac) at /build/buildd/kdelibs-3.5.4/./kdeui/klistview.cpp:878
#41 0xb6a6eec7 in QScrollView::viewportMouseReleaseEvent ()
   from /usr/lib/libqt-mt.so.3
#42 0xb6a7045e in QScrollView::eventFilter () from /usr/lib/libqt-mt.so.3
#43 0xb6a386f6 in QListView::eventFilter () from /usr/lib/libqt-mt.so.3
#44 0xb6938ddc in QObject::activate_filters () from /usr/lib/libqt-mt.so.3
#45 0xb6938e5a in QObject::event () from /usr/lib/libqt-mt.so.3
#46 0xb6970533 in QWidget::event () from /usr/lib/libqt-mt.so.3
#47 0xb68d0a98 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#48 0xb68d2c56 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#49 0xb75e4fe2 in KApplication::notify (this=0xbf9ce344, receiver=0x81bf7f8,
    event=0xbf9cdd30)
    at /build/buildd/kdelibs-3.5.4/./kdecore/kapplication.cpp:550
#50 0xb68633fd in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#51 0xb6862062 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#52 0xb686014c in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#53 0xb6877320 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#54 0xb68eb16e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#55 0xb68eaf7e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#56 0xb68d2641 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#57 0xb7faaa0c in kdemain (argc=7, argv=0xbf9ce4f4)
    at /build/buildd/kdebase-3.5.4/./kcontrol/kcontrol/main.cpp:151
#58 0x08048482 in main (argc=) at kcontrol.la.cpp:2
#59 0xb7d458cc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#60 0x080483d1 in _start ()

Revision history for this message
Anthony Mercatante (tonio) wrote :

Impossible to reproduce here with an up2date edgy...

Revision history for this message
Anthony Mercatante (tonio) wrote :

Hum sorry, didn't saw at the vmware thing ;)

Revision history for this message
Thehound (tehhellhound) wrote :

I can 100% confirm it with Edgy on VMWare Workstation 5.5.2. Not sure who is at fault: VMWare or (K)ubuntu. I use Kubuntu Edgy 6.10 for the record. We could use a little more information from you like which VMWare version you're using. 5.5.3 is the latest but I have not bothered updating because it works perfectly but for this and a little skew in the clock that's easily correctable(known VMWare issue with any OS that uses 1000HZ interrupt rate). Have you ever used Dapper or anything within VMWare? If so, does it happen with that? I'm hoping this could be nailed down to either Edgy or a bug in VMWare. I'd be happy to hear if anyone has a solution as I like to have things run perfectly.

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

What video driver are you using and does OpenGL work in your setup? Does glxinfo work?

Changed in kdebase:
status: Unconfirmed → Needs Info
Revision history for this message
Ryan Kavanagh (ryanakca) wrote :

I can confirm on Kubuntu feisty fawn, daily build, Live CD. Video driver: vesa (according to /etc/X11/xorg.conf ... see attachment for more details).

glxinfo does not work (from what I see..)

name of display: :0.0
X Error of failed request: BadAlloc (insufficient resources for operation)
  Major opcode of failed request: 142 (GLX)
  Minor opcode of failed request: 3 (X_GLXCreateContext)
  Serial number of failed request: 16
  Current serial number in output stream: 17

however, I get good FPS with glxgears:
ubuntu@ubuntu:~$ glxgears
3578 frames in 5.0 seconds = 711.974 FPS
4200 frames in 5.1 seconds = 828.454 FPS

feisty-desktop-amd64.iso 22-Feb-2007 06:33 703M Desktop CD for 64-bit PC (AMD64) computers (standard download)
Qt: 3.3.7
KDE: 3.5.6
KDE Info Center: 3.5.6

Revision history for this message
Ryan Kavanagh (ryanakca) wrote :
Revision history for this message
Ryan Kavanagh (ryanakca) wrote :
Changed in kdebase:
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Kieran Hogg (xerosis) wrote :

The same action restarts X for me.

Revision history for this message
Marnen Laibow-Koser (marnen) wrote :

Still a problem in Feisty. Hardware DB ID is cb8a4fe0b84bb72b952025a92fc53bd4 . Backtrace is as follows:
-----begin backtrace-----
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1238812976 (LWP 6034)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xffffe410 in __kernel_vsyscall ()
#7 0xb7d23df0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb7d25641 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7d599bb in ?? () from /lib/tls/i686/cmov/libc.so.6
#10 0x0000000c in ?? ()
#11 0xbfdefdc0 in ?? ()
#12 0x00000400 in ?? ()
#13 0x00000000 in ?? ()
------end backtrace------

Revision history for this message
sillyg00se (jessestewart) wrote :

I have a Dell Dimension E520 desktop /w Intel 82G965 graphics chipset. When I click the OpenGL item in KInfoCenter my X crashed and restarted itself... googled and found this thread. Anyone know what could cause this?

Revision history for this message
Ryan Kavanagh (ryanakca) wrote :

It seems to be a vesa thing, based on the comments / attachments. Anybody experiencing the same problem with a different driver?

Revision history for this message
vonHalenbach (lustik) wrote :

I am sure, that i had this exact same bug with feisty fawn, too. I had made several updates and i can't confirm this bug anymore. I get a normal error message, when i press on this button in kinfocenter.
This bug seems to be bound to the original vesa driver in connection with the original feisty kernel.
I had changed my driver to the propritary old nvidia driver and had no problems since then.
Now i use the vesa driver again with an updated kernel.

stefan@cipy:~$ uname -a
Linux cipy 2.6.20-15-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 GNU/Linux

stefan@cipy:/media/ibm/inkscape$ glxinfo
name of display: :0.0
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual

   visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
 id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
0x21 24 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
0x39 32 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Still an issue in Intrepid?

Changed in kdebase:
importance: Medium → Low
status: Confirmed → Incomplete
Revision history for this message
Kevin (raccoonstrait) wrote : Re: [Bug 58734] Re: Kinfocenter crashes when the "OpenGL" information panel is selected

Hi,

Sorry about the delay in response. I am no longer getting Kinfocenter crashes. I was able to build the index recently. I am not sure what Intrepid is. System is up to date with software updates.

Regards

Kevin

--- On Sat, 9/20/08, Jonathan Thomas <email address hidden> wrote:
From: Jonathan Thomas <email address hidden>
Subject: [Bug 58734] Re: Kinfocenter crashes when the "OpenGL" information panel is selected
To: <email address hidden>
Date: Saturday, September 20, 2008, 3:57 PM

Still an issue in Intrepid?

** Changed in: kdebase (Ubuntu)
   Importance: Medium => Low
       Status: Confirmed => Incomplete

--
Kinfocenter crashes when the "OpenGL" information panel is selected
https://bugs.launchpad.net/bugs/58734
You received this bug notification because you are a direct subscriber
of a duplicate bug.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Intrepid is the codename of the next (K)ubuntu release, Kubuntu 8.10.
Thanks for testing. Since you've reported that the problems has been resolved I'll close this as fixed.

Changed in kdebase:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.