https://bugs.kde.org/show_bug.cgi?id=470590
--- Comment #2 from Firlaev-Hans <firlaevhans.fi...@protonmail.com> --- (In reply to Nate Graham from comment #1) > A couple of questions: > > 1. Is the affected screen plugged into the dock via an HDMI cable or > DisplayPort, or something else? > > 2. When this happens and the external screen is in this state, can you paste > the output of `kscreen-doctor -o` in a terminal window, Then, when you fix > it by unplugging and re-plugging the screen, can you paste the output of > that command a second time? 1. The screen is plugged into the thunderbolt dock via (Mini) Display Port 2.) Output of kscreen-doctor -o while in bad state: Output: 1 eDP-1 enabled connected priority 2 Panel Modes: 0:2240x1400@60*! 1:2240x1400@48 2:1600x1200@60 3:1280x1024@60 4:1024x768@60 5:1920x1200@60 6:1280x800@60 7:1920x1080@60 8:1600x900@60 9:1368x768@60 10:1280x720@60 Geometry: 122,1440 2240x1400 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic Output: 2 DP-4 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60*! 1:1920x1440@60 2:2560x1080@60 3:2560x1080@60 4:2560x1080@50 5:1920x1080@60 6:1920x1080@60 7:1920x1080@60 8:1920x1080@50 9:1600x1200@60 10:1680x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1280x800@60 15:1152x864@75 16:1280x720@60 17:1280x720@60 18:1280x720@60 19:1280x720@50 20:1024x768@75 21:1024x768@70 22:1024x768@60 23:832x624@75 24:800x600@75 25:800x600@72 26:800x600@60 27:800x600@56 28:720x576@50 29:720x480@60 30:720x480@60 31:720x480@60 32:720x480@60 33:720x480@60 34:640x480@75 35:640x480@73 36:640x480@67 37:640x480@60 38:640x480@60 39:640x480@60 40:720x400@70 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic Output after reconnecting the monitor, returning to normal state: Output: 1 eDP-1 enabled connected priority 2 Panel Modes: 0:2240x1400@60*! 1:2240x1400@48 2:1600x1200@60 3:1280x1024@60 4:1024x768@60 5:1920x1200@60 6:1280x800@60 7:1920x1080@60 8:1600x900@60 9:1368x768@60 10:1280x720@60 Geometry: 122,1440 2240x1400 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic Output: 2 DP-5 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60*! 1:1920x1440@60 2:2560x1080@60 3:2560x1080@60 4:2560x1080@50 5:1920x1080@60 6:1920x1080@60 7:1920x1080@60 8:1920x1080@50 9:1600x1200@60 10:1680x1050@60 11:1600x900@60 12:1280x1024@75 13:1280x1024@60 14:1280x800@60 15:1152x864@75 16:1280x720@60 17:1280x720@60 18:1280x720@60 19:1280x720@50 20:1024x768@75 21:1024x768@70 22:1024x768@60 23:832x624@75 24:800x600@75 25:800x600@72 26:800x600@60 27:800x600@56 28:720x576@50 29:720x480@60 30:720x480@60 31:720x480@60 32:720x480@60 33:720x480@60 34:640x480@75 35:640x480@73 36:640x480@67 37:640x480@60 38:640x480@60 39:640x480@60 40:720x400@70 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic So for some reason the display gets a different number (DP4 vs DP5) when this error happens. I also noticed that most of the time then running kscreen-doctor, it aborts abnormally. I don't know if this is related at all. Unfortunately I couldn't generate a good backtrace for some reason, the kscreen debuginfo package it complains about *is* installed: malloc_consolidate(): unaligned fastbin chunk detected Thread 1 "kscreen-doctor" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 Downloading source file /usr/src/debug/glibc-2.37-4.fc38.x86_64/nptl/pthread_kill.c 44 return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; Missing separate debuginfos, use: dnf debuginfo-install libkscreen-qt5-5.27.5-1.fc38.x86_64 -- You are receiving this mail because: You are watching all bug changes.
