Bug 193411 - System Settings crash after double clicking on "Desktop"
Summary: System Settings crash after double clicking on "Desktop"
Status: RESOLVED DUPLICATE of bug 188623
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_screensaver (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-20 21:47 UTC by L. Alberto Giménez
Modified: 2009-05-20 23:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description L. Alberto Giménez 2009-05-20 21:47:26 UTC
Version:           unknown (using 4.2.2 (KDE 4.2.2), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.26-2-686

Hi, I'm using KDE 4.2.2 from Debian Testing (upgraded today).

The System Settings application crashes whenever I try to double click the "Desktop" icon. i got the following window dialog:

Application: System Settings (systemsettings), signal SIGSEGV

Thread 1 (Thread 0xb5e6d930 (LWP 5082)):
#0  0xb7eed424 in __kernel_vsyscall ()
#1  0xb6883360 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb688319e in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7acf738 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()

If I execute "systemsettings" from console, I get this output (only pasted the meaningful part):
systemsettings(6288) MainWindow::selectionChanged: Selected item:  "Desktop"
systemsettings(6288) MainWindow::selectionChanged: Comment:        ""
systemsettings(6288) MainWindow::selectionChanged: adding
systemsettings(6288) MainWindow::selectionChanged: adding
systemsettings(6288) MainWindow::selectionChanged: Selected item:  "Desktop"
systemsettings(6288) MainWindow::selectionChanged: Comment:        ""
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode: 1 (X_CreateWindow)
  Resource id:  0x65
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 7 (X_ReparentWindow)
  Resource id:  0x5000c6d
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 3 (X_GetWindowAttributes)
  Resource id:  0x5000c6d
KCrash: Application 'systemsettings' crashing...
sock_file=/home/agimenez/.kde/socket-bart/kdeinit4__0

Thanks,
L. Alberto Giménez
Comment 1 Dario Andres 2009-05-20 21:49:53 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? 
You need to install the "kdebase-workspace-dbg" package 
Thanks
Comment 2 L. Alberto Giménez 2009-05-20 22:39:00 UTC
Sure, here it is:

Application: System Settings (systemsettings), signal SIGSEGV

Thread 1 (Thread 0xb5f0b930 (LWP 7679)):
[KCrash Handler]
#6  0xb648ea97 in XVisualIDFromVisual () from /usr/lib/libX11.so.6
#7  0xb6ca54ce in qt_x11_getX11InfoForWindow (xinfo=0x8d616e4, a=@0xbffa664c) at kernel/qwidget_x11.cpp:400
#8  0xb6caa11e in QWidgetPrivate::create_sys (this=0x8d615f0, window=79694169, initializeWindow=false, destroyOldWindow=true) at kernel/qwidget_x11.cpp:545
#9  0xb6c6f68c in QWidget::create (this=0x8d640f8, window=79694169, initializeWindow=false, destroyOldWindow=<value optimized out>) at kernel/qwidget.cpp:1252
#10 0xb464a289 in KSWidget (this=0x8d640f8, parent=0x8951ca0, wf={i = -1074108104}) at ../../../kcontrol/screensaver/kswidget.cpp:65
#11 0xb463ad04 in KScreenSaver::slotPreviewExited (this=0x897eb28) at ../../../kcontrol/screensaver/kssmonitor.h:9
#12 0xb463b208 in KScreenSaver::setMonitor (this=0x897eb28) at ../../../kcontrol/screensaver/scrnsave.cpp:585
#13 0xb463c90f in KScreenSaver::findSavers (this=0x897eb28) at ../../../kcontrol/screensaver/scrnsave.cpp:572
#14 0xb463d113 in KScreenSaver::qt_metacall (this=0x897eb28, _c=QMetaObject::InvokeMetaMethod, _id=11, _a=0xbffa6bf8) at ./scrnsave.moc:97
#15 0xb7625b98 in QMetaObject::activate (sender=0x8c8df58, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3120
#16 0xb7626822 in QMetaObject::activate (sender=0x8c8df58, m=0xb7701ae4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3194
#17 0xb76615d7 in QTimer::timeout (this=0x8c8df58) at .moc/release-shared/moc_qtimer.cpp:128
#18 0xb762b67e in QTimer::timerEvent (this=0x8c8df58, e=0xbffa707c) at kernel/qtimer.cpp:261
#19 0xb762004f in QObject::event (this=0x8c8df58, e=0xbffa707c) at kernel/qobject.cpp:1082
#20 0xb6c167bc in QApplicationPrivate::notify_helper (this=0x8924250, receiver=0x8c8df58, e=0xbffa707c) at kernel/qapplication.cpp:4057
#21 0xb6c1eace in QApplication::notify (this=0xbffa7408, receiver=0x8c8df58, e=0xbffa707c) at kernel/qapplication.cpp:3604
#22 0xb7afdb7d in KApplication::notify (this=0xbffa7408, receiver=0x8c8df58, event=0xbffa707c) at ../../kdeui/kernel/kapplication.cpp:307
#23 0xb760fa2b in QCoreApplication::notifyInternal (this=0xbffa7408, receiver=0x8c8df58, event=0xbffa707c) at kernel/qcoreapplication.cpp:610
#24 0xb763ee41 in QTimerInfoList::activateTimers (this=0x8926794) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#25 0xb763b440 in timerSourceDispatch (source=0x8926760) at kernel/qeventdispatcher_glib.cpp:164
#26 0xb62cb718 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb62cec7b in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x08926000 in ?? ()
#29 0x00000000 in ?? ()


If you need another kind of backtrace (i.e. valgrind as the link you supplied says), don't hesitate to ask it to me.

Thanks.
Comment 3 Dario Andres 2009-05-20 22:47:57 UTC
Thanks. This seems to be a duplicate of bug 188623. Regards

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