Bug 209817

Summary: Cannot access to screensavers panel
Product: [Applications] systemsettings Reporter: Francesco <muziofg>
Component: kcm_screensaverAssignee: kscreensaver bugs tracking <kscreensaver-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: muziofg
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Francesco 2009-10-08 00:33:35 UTC 
Application that crashed: systemsettings
Version of the application: 1.0
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30 i686
Distribution: Debian GNU/Linux testing (squeeze)

What I was doing when the application crashed:
When i try to change my screensavers the systemsettings program crash

Crash also if i try the command: kcmshell4 screensaver



 -- Backtrace:
Application: Impostazioni di sistema (systemsettings), signal: Segmentation fault
[KCrash Handler]
#6  0xb66187e7 in XVisualIDFromVisual () from /usr/lib/libX11.so.6
#7  0xb734355e in qt_x11_getX11InfoForWindow (xinfo=0x868346c, a=...) at kernel/qwidget_x11.cpp:400
#8  0xb734814e in QWidgetPrivate::create_sys (this=0x8683378, window=54528713, initializeWindow=false, destroyOldWindow=true) at kernel/qwidget_x11.cpp:545
#9  0xb730da11 in QWidget::create (this=0x84d2900, window=54528713, initializeWindow=223, destroyOldWindow=<value optimized out>) at kernel/qwidget.cpp:1253
#10 0xb44e9219 in KSWidget (this=0x84d2900, parent=0x840a970, wf=...) at ../../../kcontrol/screensaver/kswidget.cpp:66
#11 0xb44d9ed4 in KSSMonitor (this=0x84b5800) at ../../../kcontrol/screensaver/kssmonitor.h:9
#12 KScreenSaver::slotPreviewExited (this=0x84b5800) at ../../../kcontrol/screensaver/scrnsave.cpp:607
#13 0xb44da3a8 in KScreenSaver::setMonitor (this=0x84b5800) at ../../../kcontrol/screensaver/scrnsave.cpp:588
#14 0xb44dbb2f in KScreenSaver::findSavers (this=0x84b5800) at ../../../kcontrol/screensaver/scrnsave.cpp:575
#15 0xb44dc333 in KScreenSaver::qt_metacall (this=0x84b5800, _c=QMetaObject::InvokeMetaMethod, _id=11, _a=0xbfd62858) at ./scrnsave.moc:98
#16 0xb6de3b33 in QMetaObject::activate (sender=0x845adf8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#17 0xb6de4782 in QMetaObject::activate (sender=0x845adf8, m=0xb6ebfde4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#18 0xb6e1f177 in QTimer::timeout (this=0x845adf8) at .moc/release-shared/moc_qtimer.cpp:128
#19 0xb6de9e9e in QTimer::timerEvent (this=0x845adf8, e=0xbfd62cdc) at kernel/qtimer.cpp:261
#20 0xb6ddebcf in QObject::event (this=0x845adf8, e=0xbfd62cdc) at kernel/qobject.cpp:1074
#21 0xb72b5814 in QApplicationPrivate::notify_helper (this=0x8075a70, receiver=0x845adf8, e=0xbfd62cdc) at kernel/qapplication.cpp:4056
#22 0xb72bd97e in QApplication::notify (this=0xbfd62f74, receiver=0x845adf8, e=0xbfd62cdc) at kernel/qapplication.cpp:3603
#23 0xb7cfe4ad in KApplication::notify (this=0xbfd62f74, receiver=0x845adf8, event=0xbfd62cdc) at ../../kdeui/kernel/kapplication.cpp:302
#24 0xb6dce9cb in QCoreApplication::notifyInternal (this=0xbfd62f74, receiver=0x845adf8, event=0xbfd62cdc) at kernel/qcoreapplication.cpp:610
#25 0xb6dfd361 in QCoreApplication::sendEvent (this=0x8077ab4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#26 QTimerInfoList::activateTimers (this=0x8077ab4) at kernel/qeventdispatcher_unix.cpp:572
#27 0xb6df9900 in timerSourceDispatch (source=0x8077a80) at kernel/qeventdispatcher_glib.cpp:165
#28 0xb63bbe98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#29 0xb63bf623 in ?? () from /lib/libglib-2.0.so.0
#30 0xb63bf7a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#31 0xb6df9858 in QEventDispatcherGlib::processEvents (this=0x8058140, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#32 0xb7354fd5 in QGuiEventDispatcherGlib::processEvents (this=0x8058140, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#33 0xb6dcd01a in QEventLoop::processEvents (this=0xbfd62f00, flags=...) at kernel/qeventloop.cpp:149
#34 0xb6dcd462 in QEventLoop::exec (this=0xbfd62f00, flags=...) at kernel/qeventloop.cpp:201
#35 0xb6dcf8b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#36 0xb72b5697 in QApplication::exec () at kernel/qapplication.cpp:3525
#37 0x08052e64 in main (argc=1, argv=0xbfd63094) at ../../../systemsettings/app/main.cpp:51

Reported using DrKonqi
Comment 1 Christoph Feck 2009-10-08 07:05:06 UTC 

*** This bug has been marked as a duplicate of bug 188623 ***
Comment 2 Francesco 2009-10-08 19:14:47 UTC 
No! it is not a duplicate of the bug of /usr/share/kde4/services/ScreenSavers directory

my directory is already chmod a+rx but the problem persists 

The systemsettings (and kcmshell4 screensaver) chrash also if I create a new empty /usr/share/kde4/services/ScreenSavers with chmod a+rx, but works well if I delete/reneame the directory (systemsettings show an empty list of screensavers)
Comment 3 Francesco 2009-10-08 19:16:53 UTC 
ops.... wrong status
Comment 4 Francesco 2009-10-11 22:10:51 UTC 
If I try to show a screensavers list after the command 

chmod 744  /usr/share/kde4/services/ScreenSavers

I see an empty List and systemsettings works well

On another machine with debian (same version) there aren't crash , but the list contains duplicates of some screensavers

I think something.... KDE create and save to disk a files who contains a list of screensavers anytime I invoke the systemsettings ? If yes, where is this files? maybe to be not writable
Comment 5 Christoph Feck 2009-10-13 17:49:20 UTC 
Francesco, it is the same bug, it crashes inside Qt when calling XVisualIDFromVisual() while creating a widget. Workarounds may work for one, but not for the other. The bug depends on X11 and graphics drivers and version also. It may also be a Qt bug.

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