Summary: | In KDE settings, changing screen resolution and then discarding the change leads to crash | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | linuxmetel |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bugseforuns, webh4x |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.17.5 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
linuxmetel
2020-08-29 02:26:27 UTC
(Translation)
> - What I was doing when the application crashed:
>
> I changed the screen resolution setting in KDE - Display and Monitor
> - Display Configuration - Resolution, and then I discarded the change.
> Afterwards, it crashed.
possibly duplicate of bug 419625 *** This bug has been marked as a duplicate of bug 419625 *** Created attachment 132595 [details]
New crash information added by DrKonqi
systemsettings5 (5.17.5) using Qt 5.14.2
- What I was doing when the application crashed:
I changed the screen resolution, then I changed section discarding the changes and the crash happened. It happens every time I test with every kind of display setting by the way, even if I try doing the same thing with the screen orientation for example.
-- Backtrace (Reduced):
#4 0x00007fa729eb5695 in QQuickWindowPrivate::queryPointerEventInstance(QQuickPointerDevice*, QEvent::Type) const () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5 0x00007fa729eb5804 in QQuickWindow::mouseGrabberItem() const () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6 0x00007fa729eb7c3b in QQuickWindowPrivate::removeGrabber(QQuickItem*, bool, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7 0x00007fa729ea2b9f in QQuickItemPrivate::derefWindow() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8 0x00007fa729ea3b66 in QQuickItem::~QQuickItem() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
(In reply to webh4x from comment #4) Can you please try the latest KDE release? According to Bug 419625 the issue is fixed in 5.19. |