Summary: | QtWidgets-based apps crash in QXcbBackingStoreImage::flushPixmap when connecting/disconnecting external screen | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Gábor Katona <katonag> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | katonag, krusader-bugs-null, nate, nicolas.fella, o.malek.cz |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
URL: | https://bugreports.qt.io/browse/QTBUG-109226 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Gábor Katona
2023-01-31 09:43:02 UTC
Created attachment 156084 [details]
New crash information added by DrKonqi
krusader (2.8.0 "A New Day") using Qt 5.15.8
Krusader crash when connecting external screen via usb-c dock
-- Backtrace (Reduced):
#5 0x00007efe206373ba in memmove (__len=262112, __src=0x7ef95d9fe810, __dest=<optimized out>) at /usr/include/bits/string_fortified.h:36
#8 QXcbBackingStoreImage::flushPixmap (this=0x55ea709d3e60, region=..., fullRegion=<optimized out>) at qxcbbackingstore.cpp:669
#9 0x00007efe206379b9 in QXcbBackingStoreImage::flushPixmap (fullRegion=false, region=..., this=0x55ea709d3e60) at qxcbbackingstore.cpp:627
#10 QXcbBackingStoreImage::put (this=0x55ea709d3e60, dst=79691797, region=..., offset=...) at qxcbbackingstore.cpp:741
#11 0x00007efe206382f9 in QXcbBackingStore::flush (this=this@entry=0x7efe10009c60, window=window@entry=0x55ea70836e30, region=..., offset=...) at /usr/src/debug/qtbase-everywhere-src-5.15.8+kde160/src/plugins/platforms/xcb/qxcbwindow.h:120
*** Bug 465146 has been marked as a duplicate of this bug. *** Almost certainly a Qt bug. *** Bug 467419 has been marked as a duplicate of this bug. *** *** Bug 469264 has been marked as a duplicate of this bug. *** Thank you for checking. Should I file a Qt bug report, or is it better, if you or someone similarly competent file the bug based on the crash reports? If needed, I can produce such crash reports several times a week. Unfortunately. I think this Qt bug is the same: https://bugreports.qt.io/browse/QTBUG-109226 Looks like it, yeah. I see that it's already fixed in more recent versions of Qt. *** This bug has been marked as a duplicate of bug 473602 *** |