Bug 376678 - Fonts system settings crash when apply is clicked
Summary: Fonts system settings crash when apply is clicked
Status: RESOLVED UPSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
: 385669 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-02-19 16:18 UTC by Enver Balalic
Modified: 2018-02-14 23:51 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 Enver Balalic 2017-02-19 16:18:04 UTC
Application: kcmshell5 (5.9.2)

Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-rc8-g7089db84e356 x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Change a setting.
Click apply.
Popup that says that the settings will apply to newly opened apps is shown, press ok.
Crash.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings Module (kcmshell5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3ac4aec800 (LWP 1892))]

Thread 2 (Thread 0x7f3aaf0ab700 (LWP 1893)):
#0  0x00007f3ac1bc51b0 in QElapsedTimer::clockType() () at /usr/lib/libQt5Core.so.5
#1  0x00007f3ac1bc51c9 in QElapsedTimer::isMonotonic() () at /usr/lib/libQt5Core.so.5
#2  0x00007f3ac1bc3f0e in QTimerInfoList::repairTimersIfNeeded() () at /usr/lib/libQt5Core.so.5
#3  0x00007f3ac1bc3f83 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5
#4  0x00007f3ac1bc563e in  () at /usr/lib/libQt5Core.so.5
#5  0x00007f3abc6eac8d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0
#6  0x00007f3abc6eb6cb in  () at /usr/lib/libglib-2.0.so.0
#7  0x00007f3abc6eb8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#8  0x00007f3ac1bc606b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#9  0x00007f3ac1b6f89a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#10 0x00007f3ac1991a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#11 0x00007f3ac3575125 in  () at /usr/lib/libQt5DBus.so.5
#12 0x00007f3ac19966d8 in  () at /usr/lib/libQt5Core.so.5
#13 0x00007f3abe910454 in start_thread () at /usr/lib/libpthread.so.0
#14 0x00007f3ac44f27df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f3ac4aec800 (LWP 1892)):
[KCrash Handler]
#6  0x00007f3ac20caa7b in QWindowPrivate::deliverUpdateRequest() () at /usr/lib/libQt5Gui.so.5
#7  0x00007f3ab3379992 in QtWaylandClient::QWaylandWindow::frameCallback(void*, wl_callback*, unsigned int) () at /usr/lib/libQt5WaylandClient.so.5
#8  0x00007f3ab287b1c8 in ffi_call_unix64 () at /usr/lib/libffi.so.6
#9  0x00007f3ab287ac2a in ffi_call () at /usr/lib/libffi.so.6
#10 0x00007f3ab311308e in  () at /usr/lib/libwayland-client.so.0
#11 0x00007f3ab310fd20 in  () at /usr/lib/libwayland-client.so.0
#12 0x00007f3ab3110f74 in wl_display_dispatch_queue_pending () at /usr/lib/libwayland-client.so.0
#13 0x00007f3ab3376d72 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /usr/lib/libQt5WaylandClient.so.5
#14 0x00007f3ac1b9cd49 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5
#15 0x00007f3ac1bc608e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#16 0x00007f3ac1b6f89a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#17 0x00007f3ac1b77de4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#18 0x00007f3ac47aff93 in kdemain () at /usr/lib/libkdeinit5_kcmshell5.so
#19 0x00007f3ac442a291 in __libc_start_main () at /usr/lib/libc.so.6
#20 0x000000000040066a in _start ()

Reported using DrKonqi
Comment 1 Christoph Feck 2017-02-21 03:23:09 UTC
Crash is in QtWayland. If this is reproducible, please report this issue directly to Qt developers via https://bugreports.qt.io/
Comment 2 Kurt Hindenburg 2018-02-14 23:51:49 UTC
*** Bug 385669 has been marked as a duplicate of this bug. ***