Bug 320096 - System-Settings crashed after closing Display-Settings (Screensaver)
Summary: System-Settings crashed after closing Display-Settings (Screensaver)
Status: RESOLVED INTENTIONAL
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_screensaver (other bugs)
Version First Reported In: 4.10.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-21 14:14 UTC by Dominik Müller
Modified: 2015-09-26 10:33 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 Dominik Müller 2013-05-21 14:14:06 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.10.2
Qt Version: 4.8.4
Operating System: Linux 3.8.0-21-generic x86_64
Distribution: Ubuntu 13.04

-- Information about the crash:
- What I was doing when the application crashed: I closed the Screensaver-Settings. Then the Programm crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Systemeinstellungen (systemsettings), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f062a9017c0 (LWP 2791))]

Thread 2 (Thread 0x7f060e794700 (LWP 2792)):
#0  0x00007f0627a1b3cd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f0620a4d1dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0620a4d304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f06281a0036 in QEventDispatcherGlib::processEvents (this=0x7f06080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f062817038f in QEventLoop::processEvents (this=this@entry=0x7f060e793d90, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f0628170618 in QEventLoop::exec (this=this@entry=0x7f060e793d90, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f0628072410 in QThread::exec (this=this@entry=0x1937350) at thread/qthread.cpp:542
#7  0x00007f0628151edf in QInotifyFileSystemWatcherEngine::run (this=0x1937350) at io/qfilesystemwatcher_inotify.cpp:256
#8  0x00007f0628074bec in QThreadPrivate::start (arg=0x1937350) at thread/qthread_unix.cpp:338
#9  0x00007f0620f1ff8e in start_thread (arg=0x7f060e794700) at pthread_create.c:311
#10 0x00007f0627a27e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f062a9017c0 (LWP 2791)):
[KCrash Handler]
#6  0x00007f060d749210 in ?? ()
#7  0x00007f0622d8acb2 in XCloseDisplay (dpy=0x1368600) at ../../src/ClDisplay.c:65
#8  0x00007f0628e4293e in qt_cleanup () at kernel/qapplication_x11.cpp:2772
#9  0x00007f0628ddcf8e in QApplication::~QApplication (this=0x7fff944b1040, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1195
#10 0x000000000040aa3d in main (argc=5, argv=0x7fff944b1188) at ../../../systemsettings/app/main.cpp:49

Possible duplicates by query: bug 264705, bug 259206.

Reported using DrKonqi
Comment 1 Jens Müller 2013-10-05 16:33:01 UTC
I got the same crash when closing the "Display" settings. Apparently this is not specific to  	kcm_screensaver
Comment 2 Albert Astals Cid 2015-09-26 10:33:00 UTC
kcm_screensaver reached it's end of life with Plasma 4, whose last bugfix release was last August 2015, we are sorry we did not get to fix this bug.

In Plasma 5 we support screen lockers instead of screen savers.

Sorry again we could not fix your bug.