Bug 434908 - [wayland] VNC not usable
Summary: [wayland] VNC not usable
Status: RESOLVED DUPLICATE of bug 436650
Alias: None
Product: krdc
Classification: Applications
Component: VNC (show other bugs)
Version: 20.12.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-24 21:11 UTC by Jürgen Richtsfeld
Modified: 2021-05-31 11:40 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
chrome screenshot (45.74 KB, image/png)
2021-05-24 20:22 UTC, Dmitry Misharov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jürgen Richtsfeld 2021-03-24 21:11:02 UTC
SUMMARY
I'm accessing a tightvnc server running in the local net. I can connect, parts of the window is recognizable, but colors are (somehow wrong) and additionally parts of the vnc window are flickering. Contained text is partly readable.
All of that worked very nice when I was on X. When using gvncviewer to acccess the same tightvnc server the UI looks ok (but I'd prefer krdc for a lot of reasons)

STEPS TO REPRODUCE
1. have some tightvnc server and connect to it
2. observe UI glitches



OBSERVED RESULT
UI glitches and flicker which renders the application unusable.

EXPECTED RESULT
Correct remote UI just like on X.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.8-arch1-1
OS Type: 64-bit
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8705G CPU @ 3.10GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630
Comment 1 Dmitry Misharov 2021-05-24 20:22:56 UTC
Created attachment 138754 [details]
chrome screenshot

I faced that issue today. I have a container with a running VNC server and Google Chrome. When I tried to connect using krdc it's hard to recognize anything.
Comment 2 Patrick Silva 2021-05-31 11:40:35 UTC
*** This bug has been marked as a duplicate of bug 436650 ***