Bug 355574 - kcmshell5,Segmentation fault when changing font size.
Summary: kcmshell5,Segmentation fault when changing font size.
Status: RESOLVED DUPLICATE of bug 348414
Alias: None
Product: frameworks-knotifications
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Martin Klapetek
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-11-19 07:49 UTC by wintonian
Modified: 2015-11-23 21:07 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 wintonian 2015-11-19 07:49:05 UTC
Application: kcmshell5 (5.4.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.6-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

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

I alterd the font size in KDE control module, clicked "apply".

-- Backtrace:
Application: KDE Control Module (kcmshell5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f67f64f5900 (LWP 8198))]

Thread 2 (Thread 0x7f67d859e700 (LWP 8199)):
#0  0x00007f67f1fd5fdd in poll () from /lib64/libc.so.6
#1  0x00007f67eed69272 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x00007f67eed6aee7 in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x00007f67dbb4fda9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5
#4  0x00007f67f2bf23ce in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#5  0x00007f67efd5660a in start_thread () from /lib64/libpthread.so.0
#6  0x00007f67f1fe1a7d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f67f64f5900 (LWP 8198)):
[KCrash Handler]
#5  0x00007f67d70041c4 in KNotification::flags() const () from /lib64/libKF5Notifications.so.5
#6  0x00007f67d7029285 in NotifyByAudio::onAudioFinished() () from /lib64/libKF5Notifications.so.5
#7  0x00007f67d702f625 in NotifyByAudio::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libKF5Notifications.so.5
#8  0x00007f67f2e022ea in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5
#9  0x00007f67d642fcb5 in Phonon::MediaObject::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libphonon4qt5.so.4
#10 0x00007f67f2e031b1 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#11 0x00007f67f3ac341c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#12 0x00007f67f3ac88e6 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#13 0x00007f67f2dd377b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#14 0x00007f67f2dd5b76 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5
#15 0x00007f67f2e29ae3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#16 0x00007f67ee608e3a in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#17 0x00007f67ee6091d0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#18 0x00007f67ee60927c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#19 0x00007f67f2e29eef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#20 0x00007f67f2dd0f0a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#21 0x00007f67f3cbe40d in QDialog::exec() () from /lib64/libQt5Widgets.so.5
#22 0x00007f67f61a6ce9 in kdemain () from /lib64/libkdeinit5_kcmshell5.so
#23 0x00007f67f1eff580 in __libc_start_main () from /lib64/libc.so.6
#24 0x0000561d951de9d9 in _start ()

Possible duplicates by query: bug 354518, bug 354451, bug 353597, bug 351073, bug 351019.

Reported using DrKonqi
Comment 1 Martin Klapetek 2015-11-23 21:07:12 UTC
Thanks for the report

This is fixed in frameworks release 5.13, please update your frameworks packages.

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