Created attachment 180894 [details] Kscreen crash report SUMMARY Since the latest KDE Plasma version, kscreen and kscreen-doctor are unable to set a 4k resolution @60hz to my HDMI 4k TV. The setup never changed and worked in KDE Plasma 6.2.x Other resolutions like 1080p @60hz or 1440p @60hz works fine. STEPS TO REPRODUCE 1. Open kscreen and activate the TV HDMI output 2. Set a resolution of 3840x2160 at 60hz Alternatively use kscreen-doctor with the following command: kscreen-doctor output.HDMI-A-1.priority.1 output.HDMI-A-1.mode.3840x2160@60 OBSERVED RESULT Under Kscreen: crash (kcrash file in attachement) and no display. Under kscreen-doctor: the following message appears: kscreen-doctor output.HDMI-A-1.priority.1 output.HDMI-A-1.mode.3840x2160@60 applying config failed! Driver rejected output configuration. EXPECTED RESULT: Display set at 3840x2160 @60hz resolution SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 42 KDE Spin KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.9.0 ADDITIONAL INFORMATION Mesa drivers info: Devices: ======== GPU0: apiVersion = 1.4.305 driverVersion = 25.0.4 vendorID = 0x1002 deviceID = 0x744c deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU deviceName = AMD Radeon RX 7900 XTX (RADV NAVI31) driverID = DRIVER_ID_MESA_RADV driverName = radv driverInfo = Mesa 25.0.4 conformanceVersion = 1.4.0.0 deviceUUID = 00000000-0300-0000-0000-000000000000 driverUUID = 414d442d-4d45-5341-2d44-525600000000 GPU1: apiVersion = 1.4.305 driverVersion = 0.0.1 vendorID = 0x10005 deviceID = 0x0000 deviceType = PHYSICAL_DEVICE_TYPE_CPU deviceName = llvmpipe (LLVM 20.1.2, 256 bits) driverID = DRIVER_ID_MESA_LLVMPIPE driverName = llvmpipe driverInfo = Mesa 25.0.4 (LLVM 20.1.2) conformanceVersion = 1.3.1.1 deviceUUID = 6d657361-3235-2e30-2e34-000000000000 driverUUID = 6c6c766d-7069-7065-5555-494400000000 Kscreen-doctor infos: Output: 1 DP-1 enabled connected priority 1 DisplayPort Modes: 1:3440x1440@144! 2:3440x1440@60 3:3440x1440@160* 4:3440x1440@100 5:1920x1200@144 6:1920x1080@75 7:1920x1080@60 8:1920x1080@60 9:1920x1080@60 10:1920x1080@50 11:1600x1200@144 12:1680x1050@60 13:1600x900@60 14:1280x1024@75 15:1280x1024@60 16:1440x900@144 17:1280x800@60 18:1152x864@60 19:1280x720@60 20:1280x720@60 21:1280x720@60 22:1280x720@50 23:1024x768@60 24:800x600@60 25:720x576@50 26:720x480@60 27:720x480@60 28:640x480@60 29:640x480@60 30:640x480@60 31:1600x1200@60 32:1280x1024@60 33:1024x768@60 34:1920x1200@60 35:2560x1440@60 36:1920x1080@60 37:1600x900@60 38:1368x768@60 39:1280x720@60 Geometry: 0,0 3440x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown HDR: disabled Wide Color Gamut: disabled ICC profile: none Color profile source: sRGB Color power preference: prefer efficiency and performance Brightness control: supported, set to 15% and dimming to 100% Output: 2 DP-3 enabled connected priority 2 DisplayPort Modes: 40:1920x1080@60*! 41:1920x1080@60 42:1920x1080@60 43:1920x1080@50 44:1680x1050@60 45:1280x1024@75 46:1280x1024@70 47:1280x1024@60 48:1440x900@60 49:1280x800@60 50:1152x864@75 51:1280x720@60 52:1280x720@60 53:1280x720@60 54:1280x720@50 55:1024x768@75 56:1024x768@70 57:1024x768@60 58:800x600@75 59:800x600@72 60:800x600@60 61:720x576@50 62:720x576@50 63:720x576@50 64:720x480@60 65:720x480@60 66:720x480@60 67:720x480@60 68:720x480@60 69:640x480@75 70:640x480@73 71:640x480@60 72:640x480@60 73:640x480@60 74:720x400@70 75:1280x1024@60 76:1024x768@60 77:1280x800@60 78:1920x1080@60 79:1600x900@60 80:1368x768@60 81:1280x720@60 Geometry: 3440,180 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none Color profile source: sRGB Color power preference: prefer efficiency and performance Brightness control: supported, set to 14% and dimming to 100% Output: 3 HDMI-A-1 disabled connected priority 0 HDMI Modes: 82:3840x2160@60*! 83:4096x2160@60 84:4096x2160@60 85:4096x2160@50 86:4096x2160@30 87:4096x2160@30 88:4096x2160@25 89:4096x2160@24 90:4096x2160@24 91:3840x2160@60 92:3840x2160@60 93:3840x2160@50 94:3840x2160@30 95:3840x2160@30 96:3840x2160@25 97:3840x2160@24 98:3840x2160@24 99:2560x1440@120 100:1920x1200@60 101:1920x1080@120 102:1920x1080@120 103:1920x1080@100 104:1920x1080@60 105:1920x1080@60 106:1920x1080@60 107:1920x1080@50 108:1920x1080@30 109:1920x1080@30 110:1920x1080@25 111:1920x1080@24 112:1920x1080@24 113:1600x1200@60 114:1680x1050@60 115:1280x1024@60 116:1440x900@60 117:1360x768@60 118:1280x800@60 119:1152x864@60 120:1280x720@60 121:1280x720@60 122:1280x720@50 123:1024x768@60 124:800x600@60 125:720x576@50 126:720x480@60 127:720x480@60 128:720x480@60 129:720x480@60 130:640x480@60 131:640x480@60 132:640x480@60 133:720x400@70 134:1600x1200@60 135:1280x1024@60 136:1024x768@60 137:2560x1600@60 138:1920x1200@60 139:1280x800@60 140:3840x2160@60 141:3200x1800@60 142:2880x1620@60 143:2560x1440@60 144:1920x1080@60 145:1600x900@60 146:1368x768@60 147:1280x720@60 Geometry: 5360,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: disabled Wide Color Gamut: disabled ICC profile: none Color profile source: sRGB Color power preference: prefer efficiency and performance Brightness control: supported, set to 100% and dimming to 100%
> applying config failed! Driver rejected output configuration. It means what it says: your GPU driver didn't like this combination of settings for some reason. This must be a change from the past, but it's a change in the GPU driver. You'll need to report this upstream at https://docs.mesa3d.org/bugs.html. That said, the KCM shouldn't crash, and we should fix that. Backtrace: Thread 1 (Thread 0x7fe047e10400 (LWP 7106)): [KCrash Handler] #4 0x00007fdffc003cb0 in ?? () #5 0x00007fe04e293640 in drmHandleEvent () from /lib64/libdrm.so.2 #6 0x00007fe05194cc9c in KWin::DrmGpu::dispatchEvents() () from /lib64/libkwin.so.6 #7 0x00007fe04eb6033a in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt6Core.so.6 #8 0x00007fe04eb6ee83 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt6Core.so.6 #9 0x00007fe04eb6f65b in QSocketNotifier::event(QEvent*) () from /lib64/libQt6Core.so.6 #10 0x00007fe04fe3d7af in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt6Widgets.so.6 #11 0x00007fe04eaf5fa8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt6Core.so.6 #12 0x00007fe04ecc0667 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () from /lib64/libQt6Core.so.6 #13 0x00007fe04ecc0fb9 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt6Core.so.6 #14 0x00007fe04f8d2e42 in QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt6Gui.so.6 #15 0x00007fe04eb03783 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt6Core.so.6 #16 0x00007fe04eaff229 in QCoreApplication::exec() () from /lib64/libQt6Core.so.6 #17 0x00005642de403fbb in main ()
That backtrace shows KWin crashing, not the KCM. I think that crash will already be fixed in 6.3.5 though. Please attach the output of > env | grep KWIN and > drm_info so that we can make sure
I'll report the issue to mesa drivers then, i wasn't sure the communication was well done between kscreen and the driver itself. No KWIN env variables set. drm_info output (see file attached)
Created attachment 181023 [details] drm_info
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
hmm, that's not using legacy modesetting, so I'm not certain the crash is actually fixed. As 6.3.5 is out, can you check if the crash still happens with that?
It'd be great to have a backtrace with debug symbols. Any chance that you could install debug packages for kwin or perhaps debuginfod? (not sure what's the proper way to get debug symbols on fedora)
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.