| Summary: | System Settings Crashing | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | contionmig |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | higgins.alex0, nate, renszarv07, vvvbbbcz |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.18.7 | ||
| Target Milestone: | --- | ||
| Platform: | Mint (Ubuntu based) | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
Grey display New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
contionmig
2022-01-02 11:13:44 UTC
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following that we need to figure out exactly what's going wrong. Could you 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 Thanks again! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Created attachment 146473 [details]
New crash information added by DrKonqi
systemsettings5 (5.18.4) using Qt 5.12.8
- What I was doing when the application crashed:
I was initially opening display settings from KRunner. After noticing the crash, I attempted to open Settings through the menu and it, too, crashed.
- Unusual behavior I noticed:
Prior to the crash, one of my three monitors went completely grey. The content underneath is still present and the monitor is still detected as a display. This is a frequent occurence (one that I remedy by disabling and enabling the affected display) and a different bug but could potentially be related to this due to the timing.
-- Backtrace (Reduced):
#6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7 0x00007f924ac09859 in __GI_abort () at abort.c:79
#8 0x00007f924b03daad in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#11 0x00007f924a9d9036 in QQuickWidget::resizeEvent(QResizeEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#12 0x00007f924bd37947 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
Created attachment 146474 [details]
Grey display
Center display grey at the time of crashes.
managed to fix it by upgrading my kernel to the latest version Created attachment 146523 [details]
New crash information added by DrKonqi
systemsettings5 (5.18.7) using Qt 5.12.8
- What I was doing when the application crashed:
Just tried to start system settings, and it crashed instantly. I can repeat as many time, the same crash and same stack trace are there
-- Backtrace (Reduced):
#6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7 0x00007f1a4cdcd859 in __GI_abort () at abort.c:79
#8 0x00007f1a4d201aad in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#11 0x00007f1a4cb9d036 in QQuickWidget::resizeEvent(QResizeEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#12 0x00007f1a4defb947 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! Created attachment 149065 [details]
New crash information added by DrKonqi
systemsettings5 (5.18.7) using Qt 5.12.8
- What I was doing when the application crashed:
Installing Deepin Wine 6 and QQ.
I added the Deepin Store apt source.
- Custom settings of the application:
I don't know.
-- Backtrace (Reduced):
#6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7 0x00007fa6f50b4859 in __GI_abort () at abort.c:79
#8 0x00007fa6f54ebaad in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#11 0x00007fa6f4e87036 in QQuickWidget::resizeEvent(QResizeEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#12 0x00007fa6f61e5947 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
|