Bug 1222019 - krdc can not connect to VNC hosts in plasma 6
Summary: krdc can not connect to VNC hosts in plasma 6
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Applications (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-26 17:58 UTC by Luca Billi
Modified: 2024-07-13 13:55 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Luca Billi 2024-03-26 17:58:19 UTC 
After upgrading to Plasma 6, krdc can not connect to VNC hosts anymore.

When trying to connect, krdc goes straight to a blue screen.
After that, if trying to disconnect, the program freezes and the only way out is to kill the application.

The behavior is the same regardless of what string is typed in the address field: i.e. the lock must happen quite early in the program.

This still happens in tw 20240325 with krdc 24.02.1.

A workaround so far is to use an alternative VNC viewer, such as tigervnc.
Comment 1 Pablo Sanchez 2024-03-28 01:40:03 UTC 
This was also reported upstream - https://bugs.kde.org/show_bug.cgi?id=484608
Comment 2 Christophe Marin 2024-03-28 09:01:04 UTC 
> 
> When trying to connect, krdc goes straight to a blue screen.
> After that, if trying to disconnect, the program freezes and the only way
> out is to kill the application.
> 

> This still happens in tw 20240325 with krdc 24.02.1.
> 

I can't reproduce the freeze when disconnecting (the blue screen issue is still present)
Comment 3 Pablo Sanchez 2024-03-28 13:08:47 UTC 
The previous bug is a duplicate.  This is the main upstream bug - 
https://bugs.kde.org/show_bug.cgi?id=482950
Comment 4 Luca Billi 2024-06-18 00:28:55 UTC 
The latest tumbleweed 20240614 with krdc 24.05.1 fixed the issue for me.
Comment 5 Luca Billi 2024-07-13 13:55:36 UTC 
Fixed in krdc 24.05.1