Bug 143374

Summary: KInfoCenter Crashes when OpenGL is Selected
Product: [Unmaintained] kcontrol Reporter: Andrew <awfelske>
Component: kcminfoAssignee: Helge Deller <deller>
Status: RESOLVED DUPLICATE    
Severity: crash CC: petershepherd
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Andrew 2007-03-23 03:02:38 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
OS:                Linux

In KInfoCenter, when i click on the 'OpenGL' link in the left column, KInfoCenter crashes. I Tried to Reproduce the crash by Selecting 'OpenGL' again and it crashed again.
Comment 1 Philip Rodrigues 2007-03-24 14:37:26 UTC
Please paste the backtrace from the crash dialog
Comment 2 Maciej KokociƄski 2007-04-21 20:19:30 UTC
I've just installed Kubuntu 7.04 on my Asus Z96Jm with ATI X1600 and I have exactly the same thing, when I click 'OpenGL', KInfoCenter crashes. I have a VESA driver installed, maybe installing proprietary ati drivers will solve the problem...

Here's the 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 -1239238960 (LWP 7582)]
(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)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xffffe410 in __kernel_vsyscall ()
#7  0xb7cbbdf0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb7cbd641 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7cf19bb in ?? () from /lib/tls/i686/cmov/libc.so.6
#10 0x00000010 in ?? ()
#11 0xbfdb1da0 in ?? ()
#12 0x00000400 in ?? ()
#13 0x00000000 in ?? ()
Comment 3 Philip Rodrigues 2007-04-27 21:27:25 UTC
I'm afraid your KDE is built without debugging information, so the backtrace isn't very useful. Can you install the kdelibs-dbg and kdebase-dbg packages, and try again?
Comment 4 Little Girl 2007-05-18 17:40:50 UTC
Mine is Kubuntu 7.04 on an HP Pavilion ze5185 laptop. Same issue here, but in my case KInfoCenter crashes when I click on OpenGL only if I click on another category first. If I open KInfoCenter and click on OpenGL first, it opens just fine. In addition, if I click on OpenGL first, then click on another category, then click on OpenGL, KInfoCenter will crash. I can consistently repeat these crashes. I don't have the debugging packages installed, so my backtrace is similar to the one above.
Comment 5 Philip Rodrigues 2007-05-19 18:33:19 UTC
This will need a debug-enabled backtrace before anyone can investigate. Could you try getting one?
Comment 6 Little Girl 2007-06-30 16:55:47 UTC
Sorry this took so long. I was very new to Kubuntu when I first replied here. I saw your instructions to add kdelibs-dbg and kdebase-dbg packages and was hesitant to do it because of the listed conflicts.

Here's the backtrace with both installed. I loaded KInfoCenter, clicked on OpenGL successfully, then clicked on Network Interfaces successfully, and finally clicked on OpenGL unsuccessfully, resulting in a crash.

I can repeat this over and over substituting any of the other choices for Network Interfaces above. I am running Kubuntu Feisty Fawn with the 2.6.20-16-generic kernel on an HP Pavilion ze5185 laptop. I hope this helps!

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1239472432 (LWP 6500)]
[KCrash handler]
#6  0xb59d4d40 in ?? ()
#7  0xb5c02ab1 in __glXInitialize () from /usr/lib/libGL.so.1
#8  0xb5bfea71 in ?? () from /usr/lib/libGL.so.1
#9  0x083e5888 in ?? ()
#10 0xb6c9fab0 in ?? () from /usr/lib/libqt-mt.so.3
#11 0xbfac6cd8 in ?? ()
#12 0xb5cf3634 in ?? () from /usr/lib/kde3/kcm_info.so
#13 0x00000000 in ?? ()
Comment 7 Philip Rodrigues 2007-07-01 14:36:06 UTC
Hrm, that backtrace still looks like it's using non-debug packages. Are you sure you have kdelibs-dbg and kdebase-dbg installed? You might want to check on a kubuntu forum how to make sure
Comment 8 Little Girl 2007-07-02 00:06:41 UTC
As far as I can tell, they're installed. Here's the info I've gotten from my research:

--------------
If I type dpkg -s kdelibs-dbg I get:

Package: kdelibs-dbg
Status: install ok installed
Priority: extra
Section: libdevel
Installed-Size: 72524
Maintainer: Jonathan Riddell <jriddell@ubuntu.com>
Architecture: i386
Source: kdelibs
Version: 4:3.5.6-0ubuntu14
Replaces: kdelibs4-dbg, kdelibs4c2-dbg, kdelibs4c2a-dbg
Depends: kdelibs4c2a (= 4:3.5.6-0ubuntu14)
Conflicts: kdelibs4-dbg, kdelibs4c2-dbg, kdelibs4c2a-dbg
Description: debugging symbols for kdelibs
 This package contains the debugging symbols associated with kdelibs.
 They will automatically be used by gdb for debugging kdelibs-related
 issues.
Original-Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
--------------
If I type dpkg -s kdebase-dbg I get:

Package: kdebase-dbg
Status: install ok installed
Priority: extra
Section: libdevel
Installed-Size: 90548
Maintainer: Jonathan Riddell <jriddell@ubuntu.com>
Architecture: i386
Source: kdebase
Version: 4:3.5.6-0ubuntu20.1
Depends: libkonq4 (= 4:3.5.6-0ubuntu20.1)
Description: debugging symbols for kdebase
 This package contains the debugging symbols associated with kdebase.
 They will automatically be used by gdb for debugging kdebase-related
 issues.
Original-Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
--------------
If I type dpkg -L  kdelibs-dbg I get a huge list.
If I type dpkg -L  kdebase-dbg I get a huge list.

The entries of both lists are similar to these:

/usr/lib/debug/usr/bin/kappfinder
/usr/lib/debug/usr/bin/kate
/usr/lib/debug/usr/bin/kwrite
/usr/lib/debug/usr/bin/kaccess
/usr/lib/debug/usr/bin/kcontrol
/usr/lib/debug/usr/bin/keditfiletype

The one striking thing about these lists is that kinfocenter isn't on either of them.
--------------

Is there a way to add it so that it, too, will use kdelibs-dbg and kdebase-dbg? 
I thought I'd also add that the mode I run kinfocenter in has no bearing on whether it crashes or not. Let me know if there's anything further I can do to help!

Comment 9 Philip Rodrigues 2007-07-03 23:51:13 UTC
Odd. I have no idea what could be going on, sorry. You could try running kinfocenter in gdb, and try to get a backtrace that way. See http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB
Comment 10 Little Girl 2007-07-04 18:59:14 UTC
If I follow the first instructions, I get this:
------------------------
my@prompt:~$ gdb kinfocenter
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/kinfocenter
[Thread debugging using libthread_db enabled]
[New Thread -1238997296 (LWP 6972)]

Program exited normally.
(gdb) KCrash: Application 'kinfocenter' crashing...
(gdb) backtrace
No stack.
(gdb)q
my@prompt:~$
------------------------

If, when doing this, I view the backtrace that kinfocenter provides, it's identical to the one I already posted above. Viewing the kinfocenter backtrace and not viewing it makes no difference to the gdb results.


If I launch kinfocenter normally and then follow the instructions for attaching gdb to an existing process, when I send:
$ kill -SEGV pid
I get a magnificent ongoing crash with no feedback whatsoever, the mouse pointer is similar to the one in Firefox browser when a page is loading, and I get occasional disk activity. This appears to be a neverending crash which I finally end by clicking the X in the upper right-hand corner of kinfocenter and receiving a warning that all unsaved information will be lost. It closes successfully. No backtrace whatsoever is possible when this happens. It's possible I'm being too impatient on this one. How long should I allow the crash to continue in this mode?
Comment 11 Haeber 2007-07-07 14:11:16 UTC
I can confirm this crash, it happens with a 2nd click on OpenGl after I switched (after the first click) into another tab.

Here is my crash output with SuSE 10.2 and newest packages (KDE 3.5.7 - release 47.1):

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1237420336 (LWP 13010)]
[KCrash handler]
#9  0xb5917160 in ?? ()
#10 0xb5b204e1 in __glXInitialize () from /usr/lib/libGL.so.1
#11 0xb5b1c4b1 in GetGLXPrivScreenConfig () from /usr/lib/libGL.so.1
#12 0xb5b1df81 in glXChooseVisual () from /usr/lib/libGL.so.1
#13 0xb5c161fe in mesa_hack () from /opt/kde3/lib/kde3/kcm_info.so
#14 0xb5c26c71 in GetInfo_OpenGL () from /opt/kde3/lib/kde3/kcm_info.so
#15 0xb5c17cca in KInfoListWidget::load () from /opt/kde3/lib/kde3/kcm_info.so
#16 0xb5c1eeda in KInfoListWidget::KInfoListWidget ()
   from /opt/kde3/lib/kde3/kcm_info.so
#17 0xb5c28aa7 in create_opengl () from /opt/kde3/lib/kde3/kcm_info.so
#18 0xb79e2001 in KCModuleLoader::load () from /opt/kde3/lib/libkutils.so.1
#19 0xb79e24f7 in KCModuleLoader::loadModule ()
   from /opt/kde3/lib/libkutils.so.1
#20 0xb79e4d32 in KCModuleLoader::loadModule ()
   from /opt/kde3/lib/libkutils.so.1
#21 0xb7f6fb48 in ConfigModule::module ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#22 0xb7f6ff76 in ModuleWidget::load ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#23 0xb7f70034 in DockContainer::loadModule ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#24 0xb7f702d8 in DockContainer::dockModule ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#25 0xb7f7463e in TopLevel::activateModule ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#26 0xb7f78965 in TopLevel::qt_invoke ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#27 0xb6c97f1d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb7f6661e in IndexWidget::moduleActivated ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#29 0xb7f74931 in IndexWidget::moduleSelected ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#30 0xb7f74f9e in IndexWidget::qt_invoke ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#31 0xb6c97f1d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0xb7f66b8e in ModuleTreeView::moduleSelected ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#33 0xb7f66bf7 in ModuleTreeView::slotItemSelected ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#34 0xb7f66cfc in ModuleTreeView::qt_invoke ()
   from /opt/kde3/lib/libkdeinit_kcontrol.so
#35 0xb6c97f1d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0xb6fe6ba1 in QListView::clicked () from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0xb6d7db72 in QListView::contentsMouseReleaseEventEx ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#38 0xb6d7e274 in QListView::contentsMouseReleaseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#39 0xb74b4e53 in KListView::contentsMouseReleaseEvent ()
   from /opt/kde3/lib/libkdeui.so.4
#40 0xb6dafd01 in QScrollView::viewportMouseReleaseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#41 0xb6dacfaf in QScrollView::eventFilter ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#42 0xb6d7ad86 in QListView::eventFilter () from /usr/lib/qt3/lib/libqt-mt.so.3
#43 0xb6c9781c in QObject::activate_filters ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#44 0xb6c9788b in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#45 0xb6cd050c in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#46 0xb6c389c7 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#47 0xb6c39909 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#48 0xb72f2ca2 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#49 0xb6bd7f57 in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#50 0xb6bd70ff in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#51 0xb6be798a in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#52 0xb6c4f7f0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#53 0xb6c4f686 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#54 0xb6c3857f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#55 0xb7f7a0f5 in kdemain () from /opt/kde3/lib/libkdeinit_kcontrol.so
#56 0x080484d2 in main ()

My hardware:
Intel Centrina i855, 2 Gig RAM and 2 Ghz Pentium M.

Ask for more information!

Best Regards
Thomas
Comment 12 Bram Schoenmakers 2007-07-07 18:35:34 UTC
*** Bug 147627 has been marked as a duplicate of this bug. ***
Comment 13 Jacques CHAILLET 2007-08-13 14:03:15 UTC
I have the same problem with my config :
Sempron xp3200+ flag: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr-opt lm 3dnowext 3dnow up pni cx16 lahf-lm cr8legacy ts fid vid ttp tm stc

my mother card: Asus M2V-MX <GREEN>
VGA graphic cheap: VIA K8M890
Driver VESA

(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 -1239431472 (LWP 15501)]
(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)
(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  0xb7c8cdf0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb7c8e641 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7cc29bb in ?? () from /lib/tls/i686/cmov/libc.so.6
#10 0x0000000e in ?? ()
#11 0xbfa101c0 in ?? ()
#12 0x00000400 in ?? ()
#13 0x00000000 in ?? ()

POSTED BY: Jacques CHAILLET
j.chaillet@tiscali.fr
august 15th 2007
Comment 14 Helge Deller 2007-08-21 21:06:59 UTC

*** This bug has been marked as a duplicate of 139792 ***