Bug 282990

Summary: Trying to access screensaver controls results in crash
Product: [Unmaintained] kscreensaver Reporter: Jim <jwagner>
Component: generalAssignee: kscreensaver bugs tracking <kscreensaver-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: FreeBSD Ports   
OS: FreeBSD   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jim 2011-09-28 20:50:47 UTC
Version:           unspecified (using KDE 1.2) 
OS:                FreeBSD

Whenever I try to configure a screen saver on my system, the application crashes and my desktop background (gradient color) goes to black for a few seconds, then comes back.  It does not matter whether I access this by right-clicking on my desktop, picking Configure Desktop, and then clicking on Screen Saver or using the K Control Center.  When accessing through the Control Center, there is an error box that pops up which does not when done via the Configure Desktop application though - information on this is listed in the additional information below.

This system is dual-core P4 server board with 4 gig of RAM installed with FreeBSD 8.2-RELEASE amd-64.  The / file system is installed on a file system that's mirrored via gmirror to 2 partitions on different drives.  The /home file system is installed on a raidz (RAID-5) ZFS file system.  It was freshly installed and kde 3.5.10 built from the kde-lite port.  I tried building & installing the xscreensaver-kde port in the hopes that it was just a dependency missing from the kde-lite port, but that didn't have any effect.

Reproducible: Always

Steps to Reproduce:
Try to access the screen saver configuration screen using any of a variety of steps.

Actual Results:  
Program used to access the screen saver configuration crashes; kde stays running.

Expected Results:  
Not crashed. :)

[New Thread 8050041c0 (LWP 100238)]
[Switching to Thread 8050041c0 (LWP 100238)]
[KCrash handler]
#6  0x0000000802edd620 in XVisualIDFromVisual ()
   from /usr/local/lib/libX11.so.6
#7  0x00000008022d08ac in QWidget::create () from /usr/local/lib/libqt-mt.so.3
#8  0x0000000806e1e582 in KSWidget::KSWidget ()
   from /usr/local/lib/kde3/kcm_screensaver.so
#9  0x0000000806e151b1 in KScreenSaver::slotPreviewExited ()
   from /usr/local/lib/kde3/kcm_screensaver.so
#10 0x0000000806e16945 in KScreenSaver::findSavers ()
   from /usr/local/lib/kde3/kcm_screensaver.so
#11 0x0000000806e16d0d in KScreenSaver::qt_invoke ()
   from /usr/local/lib/kde3/kcm_screensaver.so
#12 0x00000008023544fc in QObject::activate_signal ()
   from /usr/local/lib/libqt-mt.so.3
#13 0x0000000802354c94 in QObject::activate_signal ()
   from /usr/local/lib/libqt-mt.so.3
#14 0x0000000802373225 in QTimer::event () from /usr/local/lib/libqt-mt.so.3
#15 0x00000008022fdc5d in QApplication::internalNotify ()
   from /usr/local/lib/libqt-mt.so.3
#16 0x00000008022fe6d8 in QApplication::notify ()
   from /usr/local/lib/libqt-mt.so.3
#17 0x000000080148c72d in KApplication::notify ()
   from /usr/local/lib/libkdecore.so.6
#18 0x00000008022f42ac in QEventLoop::activateTimers ()
   from /usr/local/lib/libqt-mt.so.3
#19 0x00000008022b2e5d in QEventLoop::processEvents ()
   from /usr/local/lib/libqt-mt.so.3
#20 0x00000008023123f3 in QEventLoop::enterLoop ()
   from /usr/local/lib/libqt-mt.so.3
#21 0x00000008023122a2 in QEventLoop::exec ()
   from /usr/local/lib/libqt-mt.so.3
#22 0x0000000805336301 in kdemain ()
   from /usr/local/lib/libkdeinit_kcontrol.so
#23 0x0000000000407cba in execpath_avoid_loops ()
#24 0x00000000004084e9 in execpath_avoid_loops ()
#25 0x00000000004089fd in execpath_avoid_loops ()
#26 0x00000000004092ea in main ()
Comment 1 Christoph Feck 2011-09-28 22:32:08 UTC

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