*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When restoring displays the wallpaper appears in the upper left of the display (probably 640x480 rectangle on 2560x1440 display). STEPS TO REPRODUCE 1. lock your screens. Here the primary in DP (1440) and the secondary HDMI (1080) 2. Either move the mouse or press a key to wake the displays OBSERVED RESULT the wall paper is displayed in what is probably a 640x480 rectangle in the upper left, the rest of the display is black,. Desktop right clicks only work when the mouse is clicked on the wallpaper. Other windows are displayed correctly. Alt+f2 (so far) causes the wallpaper to be resized to 2560x1440. This does not happen all the time. possibly related to 484037. EXPECTED RESULT the display should restore with the correct wallpaper size SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.9.5 (available in About System) KDE Plasma Version: 6.1.0 (arch extra-testing) KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION in one case, the display was all black with no wallpaper and two mouse pointers on the display, neither working. Using Alt+f2 displayed nothing, but blind typing kscreen-doctor output.DP-1.mode.1 restored the display.
Created attachment 170658 [details] log off lock and wake with wallpaper issue journalctl -b --user -f in addition the system log showed during wake: Jun 19 22:10:12 grover kernel: HDR SB:01 1a 02 00 d8 82 d8 3c 5c 36 f0 80 54 1e 97 0c Jun 19 22:10:12 grover kernel: HDR SB:3a 3d 47 40 b4 01 d8 04 b4 01 b4 01 00 00 00 00 Jun 19 22:10:12 grover kernel: HDR SB:01 1a 02 00 d8 82 d8 3c 5c 36 f0 80 54 1e 97 0c Jun 19 22:10:12 grover kernel: HDR SB:3a 3d 47 40 b4 01 d8 04 b4 01 b4 01 00 00 00 00 Jun 19 22:10:12 grover kernel: HDR SB:01 1a 02 00 d8 82 d8 3c 5c 36 f0 80 54 1e 97 0c Jun 19 22:10:12 grover kernel: HDR SB:3a 3d 47 40 b4 01 d8 04 b4 01 b4 01 00 00 00 00 Jun 19 22:10:12 grover org_kde_powerdevil[2105]: Sleep event. connector=card1-HDMI-A-2, dref not set Jun 19 22:10:14 grover wireplumber[1859]: wplua: [string "alsa.lua"]:182: attempt to concatenate a nil value (local 'node_name') stack traceback: [string "alsa.lua"]:182: in function <[string "alsa.lua"]:175> Jun 19 22:10:14 grover kernel: HDR SB:01 1a 02 00 d8 82 d8 3c 5c 36 f0 80 54 1e 97 0c Jun 19 22:10:14 grover kernel: HDR SB:3a 3d 47 40 b4 01 d8 04 b4 01 b4 01 00 00 00 00 Jun 19 22:10:14 grover root[203298]: ACPI group/action undefined: jack/lineout / LINEOUT Jun 19 22:10:14 grover root[203300]: ACPI group/action undefined: jack/lineout / LINEOUT Jun 19 22:10:14 grover root[203302]: ACPI group/action undefined: jack/videoout / VIDEOOUT Jun 19 22:10:14 grover root[203304]: ACPI group/action undefined: jack/videoout / VIDEOOUT Jun 19 22:10:14 grover org_kde_powerdevil[2105]: Emitting DDCA_Display_Status_Event( 106785.411: DDCA_EVENT_DPMS_AWAKE, card1-DP-1, dref: Display_Ref[bus /dev/i2c-6], io_path:/dev/i2c-6] Jun 19 22:10:14 grover org_kde_powerdevil[2105]: Executed 1 registered callbacks. Jun 19 22:10:14 grover org_kde_powerdevil[2105]: Emitting DDCA_Display_Status_Event( 106785.411: DDCA_EVENT_DPMS_AWAKE, card1-HDMI-A-2, dref: Display_Ref[NULL], io_path:/dev/i2c-5] Jun 19 22:10:14 grover org_kde_powerdevil[2105]: Executed 1 registered callbacks. Jun 19 22:10:14 grover root[203306]: ACPI group/action undefined: jack/lineout / LINEOUT Jun 19 22:10:14 grover org_kde_powerdevil[2105]: dh=Display_Handle[i2c-6: fd=32], Keeping adjusted sleep multiplier 1.30 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS Jun 19 22:10:14 grover root[203313]: ACPI group/action undefined: jack/videoout / VIDEOOUT Jun 19 22:10:14 grover kmix[2499]: org.kde.kmix: No such icon "audio-card-analog-pci" Jun 19 22:10:14 grover kmix[2499]: adding 4 mixers Jun 19 22:10:14 grover kmix[2499]: mixer "PulseAudio::Playback_Devices:1" "Playback Devices" Jun 19 22:10:14 grover kmix[2499]: PulseAudio adding 1 devices Jun 19 22:10:14 grover kmix[2499]: mixer "PulseAudio::Capture_Devices:1" "Capture Devices" Jun 19 22:10:14 grover kmix[2499]: PulseAudio adding 0 devices Jun 19 22:10:14 grover kmix[2499]: mixer "PulseAudio::Playback_Streams:1" "Playback Streams" Jun 19 22:10:14 grover kmix[2499]: PulseAudio adding 1 devices Jun 19 22:10:14 grover kmix[2499]: mixer "PulseAudio::Capture_Streams:1" "Capture Streams" Jun 19 22:10:14 grover kmix[2499]: PulseAudio adding 0 devices Jun 19 22:10:14 grover root[203315]: ACPI group/action undefined: jack/lineout / LINEOUT Jun 19 22:10:14 grover root[203317]: ACPI group/action undefined: jack/videoout / VIDEOOUT Jun 19 22:10:14 grover kernel: amdgpu 0000:03:00.0: [drm] Adding stream 00000000e1fe3102 to context failed with err 28! Jun 19 22:10:14 grover kernel: amdgpu 0000:03:00.0: [drm] Adding stream 00000000e1fe3102 to context failed with err 28! Jun 19 22:10:14 grover kernel: amdgpu 0000:03:00.0: [drm] Adding stream 00000000e1fe3102 to context failed with err 28! Jun 19 22:10:14 grover kernel: amdgpu 0000:03:00.0: [drm] Adding stream 00000000e1fe3102 to context failed with err 28! Jun 19 22:10:14 grover kernel: HDR SB:01 1a 02 00 d8 82 d8 3c 5c 36 f0 80 54 1e 97 0c Jun 19 22:10:14 grover kernel: HDR SB:3a 3d 47 40 b4 01 d8 04 b4 01 b4 01 00 00 00 00
x11 or wayland?
(In reply to Marco Martin from comment #2) > x11 or wayland? wayland (sorry to have missing including that bit of info). btw, I have had numerous occurrences when the unlocked DP display is black with two copies of the cursor, fast way to 'fix' this is to relock the screen (I have a shortcut setup) and unlock it a second time. However the primary symptom remains the same.
Created attachment 171020 [details] Screen shot if display with wallpaper in left hand corner after unlock
The windows work normally. You can only get a desktop context menu by left clicking on the wallpaper in the upper left.
Similar to Bug 487717, which is fixed in Plasma 6.1.0 Also to Bug 484037, yeah.
*** This bug has been marked as a duplicate of bug 487717 ***