Bug 184693 - Program crash when choosing Systemverwaltung --> Anzeige
Summary: Program crash when choosing Systemverwaltung --> Anzeige
Status: RESOLVED DUPLICATE of bug 169470
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_randr (show other bugs)
Version: 4.2.0
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-17 19:02 UTC by ete
Modified: 2009-02-18 21:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ete 2009-02-17 19:02:56 UTC
Version:            (using KDE 4.2.0)
Compiler:          GCC 4.1.2 
OS:                Linux
Installed from:    Gentoo Packages

As soon "Anzeige" is klickt on systemsettings crashes and signal 11 SIGSEGV apears. 

I tried to get better backtrace, but even with Gentoo's debug option turned on and fomit-frame-pointer removed I still don't get debugging symbols 
sorry



This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(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 0x7ff9befbf700 (LWP 5457)]
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00007ff9bb830a70 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (process 5457)]

Thread 1 (Thread 0x7ff9befbf700 (LWP 5457)):
#0  0x00007ff9bb830a70 in nanosleep () from /lib/libc.so.6
#1  0x00007ff9bb8308c4 in sleep () from /lib/libc.so.6
#2  0x00007ff9bde3a844 in ?? () from /usr/lib64/libkdeui.so.5
#3  0x00007ff9bde3af3a in KCrash::defaultCrashHandler () from /usr/lib64/libkdeui.so.5
#4  <signal handler called>
#5  0x00007ff9b4df31cb in ?? () from /usr/lib64/kde4/kcm_randr.so
#6  0x00007ff9b4df14b9 in ?? () from /usr/lib64/kde4/kcm_randr.so
#7  0x00007ff9bde6f5af in KCModule::qt_metacall () from /usr/lib64/libkdeui.so.5
#8  0x00007ff9bd28b326 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4
#9  0x00007ff9bc44ce6d in QWidget::event () from /usr/lib64/qt4/libQtGui.so.4
#10 0x00007ff9bc4041ae in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4
#11 0x00007ff9bc40a2c2 in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4
#12 0x00007ff9bdde0ac1 in KApplication::notify () from /usr/lib64/libkdeui.so.5
#13 0x00007ff9bd27b424 in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4
#14 0x00007ff9bd27c6b9 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib64/qt4/libQtCore.so.4
#15 0x00007ff9bd2a4a23 in QEventDispatcherUNIX::processEvents () from /usr/lib64/qt4/libQtCore.so.4
#16 0x00007ff9bc48452b in ?? () from /usr/lib64/qt4/libQtGui.so.4
#17 0x00007ff9bd27a6b5 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4
#18 0x00007ff9bd27a826 in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4
#19 0x00007ff9bd27ca5e in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4
#20 0x00000000004126f7 in ?? ()
#21 0x00007ff9bb7b64a4 in __libc_start_main () from /lib/libc.so.6
#22 0x000000000040dcc9 in _start ()
#0  0x00007ff9bb830a70 in nanosleep () from /lib/libc.so.6
Comment 1 Dario Andres 2009-02-17 23:36:11 UTC
Did you rebuild kdebase-workspace with debug symbols ?
Comment 2 ete 2009-02-18 19:33:07 UTC
Ok. I figured it out. Gentoo strips the symbols even if I use the "debug" option if not told otherwise. So I rebuild systemsettings and got this

Application: System Settings (systemsettings), signal SIGSEGV
0x00007f356d35da70 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7f3570aec700 (LWP 22403)):
[KCrash Handler]
#5  RandRDisplay::isValid (this=0x100000004) at /var/tmp/portage/kde-base/systemsettings-4.2.0/work/systemsettings-4.2.0/kcontrol/randr/randrdisplay.cpp:110
#6  0x00007f35669201d7 in LegacyRandRConfig::load (this=0x1307280) at /var/tmp/portage/kde-base/systemsettings-4.2.0/work/systemsettings-4.2.0/kcontrol/randr/legacyrandrconfig.cpp:67
#7  0x00007f356691e4b9 in KRandRModule::load (this=0x1162c40) at /var/tmp/portage/kde-base/systemsettings-4.2.0/work/systemsettings-4.2.0/kcontrol/randr/krandrmodule.cpp:106
#8  0x00007f356f99c5af in KCModule::qt_metacall () from /usr/lib64/libkdeui.so.5
#9  0x00007f356edb8326 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007f356df79e6d in QWidget::event () from /usr/lib64/qt4/libQtGui.so.4
#11 0x00007f356df311ae in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4
#12 0x00007f356df372c2 in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4
#13 0x00007f356f90dac1 in KApplication::notify () from /usr/lib64/libkdeui.so.5
#14 0x00007f356eda8424 in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4
#15 0x00007f356eda96b9 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib64/qt4/libQtCore.so.4
#16 0x00007f356edd1a23 in QEventDispatcherUNIX::processEvents () from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007f356dfb152b in ?? () from /usr/lib64/qt4/libQtGui.so.4
#18 0x00007f356eda76b5 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4
#19 0x00007f356eda7826 in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4
#20 0x00007f356eda9a5e in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4
#21 0x00000000004126f7 in main (argc=1, argv=0x7fff78b23a18) at /var/tmp/portage/kde-base/systemsettings-4.2.0/work/systemsettings-4.2.0/systemsettings/main.cpp:67

I will rebuild the whole KDE with debug symbols, but thats going to take a couple of hours. Till than that's all I have.
Comment 3 Dario Andres 2009-02-18 21:24:26 UTC
Thanks

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