Details
-
Bug
-
Resolution: Fixed
-
P1: Critical
-
6.7.2, 6.7.3, 6.8.0
-
None
-
Linux/X11
-
f8aa1c423 (dev), e8b1644d4 (6.8)
Description
We got several crash reports about this at
https://crash-reports.kde.org/organizations/kde/issues/75375
libQt6XcbQpa.so.6.7.2 +0x073c79 QXcbScreen::setMonitor (qxcbscreen.cpp:657) libQt6XcbQpa.so.6.7.2 +0x0429c7 QXcbConnection::updateScreen_monitor (qxcbconnection_screens.cpp:251) libQt6XcbQpa.so.6.7.2 +0x044b15 QXcbConnection::initializeScreensFromMonitor (qxcbconnection_screens.cpp:519) libQt6XcbQpa.so.6.7.2 +0x04619e QXcbConnection::initializeScreens (qxcbconnection_screens.cpp:317) libQt6XcbQpa.so.6.7.2 +0x03b9ef QXcbConnection::handleXcbEvent (qxcbconnection.cpp:590) libQt6XcbQpa.so.6.7.2 +0x03c196 QXcbConnection::processXcbEvents (qxcbconnection.cpp:1087)
In setMonitor, {{crtc std::unique_ptr<struct xcb_randr_get_crtc_info_reply_t> =
{get() = 0x0}}}
https://crash-reports.kde.org/organizations/kde/issues/75375/events/f0d8fcf9ac2c42d7bfb9dd2bf8735395