Bug 347597 - kcmshell4 crash on close and settings lost after reboot.
Summary: kcmshell4 crash on close and settings lost after reboot.
Status: RESOLVED DUPLICATE of bug 339310
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-05-12 11:04 UTC by V1KT0P
Modified: 2015-05-12 16:18 UTC (History)
0 users

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 V1KT0P 2015-05-12 11:04:58 UTC
Application: kcmshell4 (4.14.5)
KDE Platform Version: 4.14.6
Qt Version: 4.8.6
Operating System: Linux 3.19.0-16-generic x86_64
Distribution: Ubuntu 15.04

-- Information about the crash:
- What I was doing when the application crashed:

Open "Audio and video settings", then close. 100% crash.
Also all audio changes restored after reboot.

The crash can be reproduced every time.

-- Backtrace:
Application: Модуль настройки KDE (kcmshell4), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f924c4f5780 (LWP 3619))]

Thread 3 (Thread 0x7f922ef7c700 (LWP 3620)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007f9232a823a4 in ?? () from /usr/lib/nvidia-346-updates/libGL.so.1
#2  0x00007f923062b400 in ?? () from /usr/lib/nvidia-346-updates/libnvidia-glcore.so.346.59
#3  0x00007f9232a8248c in ?? () from /usr/lib/nvidia-346-updates/libGL.so.1
#4  0x00007f92474586aa in start_thread (arg=0x7f922ef7c700) at pthread_create.c:333
#5  0x00007f924be3deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f922e53f700 (LWP 3622)):
#0  0x00007f924be328dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f9246924ebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f9246924fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f924a9f182e in QEventDispatcherGlib::processEvents (this=0x7f92200008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x00007f924a9c0cd1 in QEventLoop::processEvents (this=this@entry=0x7f922e53ee00, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f924a9c1035 in QEventLoop::exec (this=this@entry=0x7f922e53ee00, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f924a8b4e89 in QThread::exec (this=this@entry=0x140b550) at thread/qthread.cpp:538
#7  0x00007f924a9a1443 in QInotifyFileSystemWatcherEngine::run (this=0x140b550) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007f924a8b76ff in QThreadPrivate::start (arg=0x140b550) at thread/qthread_unix.cpp:349
#9  0x00007f92474586aa in start_thread (arg=0x7f922e53f700) at pthread_create.c:333
#10 0x00007f924be3deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f924c4f5780 (LWP 3619)):
[KCrash Handler]
#6  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
#7  0x00007f924911b757 in XrmDestroyDatabase (db=0x125d620) at ../../src/Xrm.c:2653
#8  0x00007f9249103813 in _XFreeDisplayStructure (dpy=dpy@entry=0x1267e50) at ../../src/OpenDis.c:618
#9  0x00007f92490f161f in XCloseDisplay (dpy=0x1267e50) at ../../src/ClDisplay.c:72
#10 0x00007f9249d78cc1 in qt_cleanup () at kernel/qapplication_x11.cpp:2774
#11 0x00007f9249d0a83c in QApplication::~QApplication (this=0x7ffff9849f10, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1195
#12 0x00007f924c109681 in ~KCMShell (this=0x7ffff9849f10, __in_chrg=<optimized out>) at ../../kcmshell/main.h:32
#13 kdemain (_argc=<optimized out>, _argv=<optimized out>) at ../../kcmshell/main.cpp:195
#14 0x00007f924bd57a40 in __libc_start_main (main=0x4006d0 <main(int, char**)>, argc=2, argv=0x7ffff984a058, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffff984a048) at libc-start.c:289
#15 0x00000000004006fe in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 339310.

Possible duplicates by query: bug 340858, bug 339310.

Reported using DrKonqi
Comment 1 Christoph Feck 2015-05-12 16:18:59 UTC

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