Bug 435251 - System Settings crashed when I enabled the option to see what has changed.
Summary: System Settings crashed when I enabled the option to see what has changed.
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: generic-crash (show other bugs)
Version: 5.21.3
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi, wayland
Depends on:
Blocks:
 
Reported: 2021-04-02 07:41 UTC by Antonio Maciej Matamoros Ochman
Modified: 2021-12-07 15:42 UTC (History)
5 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 Antonio Maciej Matamoros Ochman 2021-04-02 07:41:22 UTC
Application: systemsettings5 (5.21.3)

Qt Version: 5.15.2
Frameworks Version: 5.80.0
Operating System: Linux 5.11.11-300.fc34.x86_64 x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.3
Distribution: "Fedora release 34 (Thirty Four)"

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

I was trying to set some custom shortcuts. Before the crash, a custom shortcut I had set earlier was not working. I decided to see what had changed in the shortcuts menu using the button in the lower left corner of the setting menu. A couple of seconds after pressing the button, the system settings app crashed. After that, I opened it again and pressed the button. It worked, and I could see which shortcuts had changed with respect to the defaults (marked with a little orange dot which did not apper before the app crashed). Also, strangely the custom shortcut I had set was working again.

The crash can be reproduced sometimes.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Aborted

[KCrash Handler]
#4  0x00007f95a75f3292 in raise () from /lib64/libc.so.6
#5  0x00007f95a75dc8a4 in abort () from /lib64/libc.so.6
#6  0x00007f95a7a5542d in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5
#7  0x00007f95a58c0ef3 in QtWaylandClient::QWaylandDisplay::checkError() const [clone .cold] () from /lib64/libQt5WaylandClient.so.5
#8  0x00007f95a58cf6fa in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5
#9  0x00007f95a7c534fd in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#10 0x00007f95a7c6f78b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#11 0x00007f95a7c219b2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#12 0x00007f95a7c29544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#13 0x0000562df113cd4c in main ()
[Inferior 1 (process 6185) detached]

Possible duplicates by query: bug 435153, bug 435116, bug 435025, bug 434732, bug 434623.

Reported using DrKonqi
Comment 1 David Edmundson 2021-10-03 20:22:05 UTC
>Can you #7  0x00007f95a58c0ef3 in QtWaylandClient::QWaylandDisplay::checkError() const [clone .cold] () from /lib64/libQt5WaylandClient.so.5

Can you reproduce?

If so, can you run WAYLAND_DEBUG=1 systemsettings5
Comment 2 David Edmundson 2021-12-06 23:03:36 UTC
Marking as needsinfo as per #1
Comment 3 Antonio Maciej Matamoros Ochman 2021-12-07 09:27:46 UTC
(In reply to David Edmundson from comment #2)
> Marking as needsinfo as per #1

Hello,

no I cannot reproduce it. Sorry, and thanks for the help. It seems OK now for some months. This can be closed.

Best regards
Comment 4 Nate Graham 2021-12-07 15:42:16 UTC
OK, thanks!