Bug 466740

Summary:	wayland: 2 monitor setup with 175%/100% scaling: enable preview in dolphin (F11) destroys dolphin window contents
Product:	[Applications] dolphin	Reporter:	slartibart70
Component:	view-engine: general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	dolphin-bugs-null, kde, nate, plasma-bugs-null
Priority:	NOR
Version First Reported In:	22.12.2
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Bug Depends on:	466683
Bug Blocks:

Description slartibart70 2023-03-02 21:11:51 UTC

+++ This bug was initially created as a clone of Bug #466683 +++

Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz
Memory: 31,1 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630

Setup:
Laptop with 2K Laptop screen and a fullhd screen (1920x1080) connected by displayPort
Use fullHD monitor as 'primary' and perform all tests on the fullHD monitor (ignore laptop screen)

Go to systemsettings > display config
and set 175% scale for 2K laptop screen, 100% for fullhd screen.
This makes apps/windows on both monitors the same visual size.

Problem:

- in dolphin, open the /usr/share/wallpapers/Next/contents/images/ dir and press F11 to show the (initially hidden) image preview. This destroys the whole dolphin window contents (making it unusable because of missing buttons/list-panels or symbols) until you close/reopen dolphin. Then it works ok.

Comment 1 Nate Graham 2023-03-06 17:50:27 UTC

Cannot reproduce with an identical setup (excepting the small differences that my external screen is HDMI not DP, my Intel iGPU is a 620, and my CPU is a i7-10510U).

Comment 2 slartibart70 2023-03-06 22:33:13 UTC

i must admit that i cannot reproduce this either (i already updated in the meantime, maybe the kf5 22.12.3 update had an impact?)
I'd say... let's close this issue for now