Bug 400426 - System Settings crash after saving keyboard shortcuts and closing
Summary: System Settings crash after saving keyboard shortcuts and closing
Status: RESOLVED DUPLICATE of bug 380114
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.12.6
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
Keywords: drkonqi
Depends on:
Reported: 2018-10-28 18:03 UTC by chuck.eastus
Modified: 2018-11-01 22:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Note You need to log in before you can comment on or make changes to this bug.
Description chuck.eastus 2018-10-28 18:03:30 UTC
Application: systemsettings5 (5.12.6)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-36-generic x86_64
Distribution: Ubuntu 18.04.1 LTS

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

I had just applied changes to four shortcuts and closed the System Settings window. Shortcuts were Quick Tile Window to the left, QT window right, QT window bottom, and Maximize Window.

The crash does not seem to be reproducible.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe54a3ee800 (LWP 32119))]

Thread 2 (Thread 0x7fe52e2cc700 (LWP 32136)):
#0  0x00007fe545e2e0b4 in __GI___libc_read (fd=7, buf=0x7fe52e2cbb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x00007fe53fcdaa00 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe53fc95f27 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe53fc963e0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fe53fc9654c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fe54677b90b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fe5467209ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fe54653f22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fe548085d45 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x00007fe54654416d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fe541fe66db in start_thread (arg=0x7fe52e2cc700) at pthread_create.c:463
#11 0x00007fe545e3f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fe54a3ee800 (LWP 32119)):
[KCrash Handler]
#6  0x0000560fd522bac0 in  ()
#7  0x00007fe535bb5606 in  () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#8  0x00007fe535bb56a9 in  () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#9  0x00007fe54674f19b in QObjectPrivate::deleteChildren() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fe5467589cb in QObject::~QObject() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007fe535b8f579 in  () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#12 0x00007fe545d61041 in __run_exit_handlers (status=0, listp=0x7fe546109718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108
#13 0x00007fe545d6113a in __GI_exit (status=<optimized out>) at exit.c:139
#14 0x00007fe545d3fb9e in __libc_start_main (main=0x560fd34f9a40, argc=1, argv=0x7ffd5f8414a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd5f841498) at ../csu/libc-start.c:344
#15 0x0000560fd34f9eca in _start ()

Reported using DrKonqi
Comment 1 Nate Graham 2018-11-01 18:34:52 UTC
Un-symbolicated crash log; nothing we can do here to understand what's going on. Please install debug symbols, reproduce the crash, and attach a new symbolicated backtrace. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Comment 2 Christoph Feck 2018-11-01 22:06:09 UTC

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