Bug 274816 - krdc vnc becomes extremely slow after a few seconds
Summary: krdc vnc becomes extremely slow after a few seconds
Status: RESOLVED WORKSFORME
Alias: None
Product: krdc
Classification: Applications
Component: VNC (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-03 10:42 UTC by Dennis Schridde
Modified: 2023-01-31 05:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Schridde 2011-06-03 10:42:43 UTC
Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

After a few seconds into a vnc connection it will become very slow. The cursor follows the mouse hardly, until it stops almost completely (and/or updates only after tens of seconds) and mouse/key presses will only have an effect after minutes. In addition the visible area is only updated very very slowly: I first see half of the screen, then a few blocks more, and after some minutes the full screen, until the process starts freshly.

The downstream Ubuntu-bug #792251 is at https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/792251 , providing more information on installed software.

Reproducible: Always
Comment 1 Dennis Schridde 2011-06-03 10:43:52 UTC
P.S: This appears to be a bug in KDE, since gvncviewer (using gtk-vnc) is extremely fast. The network connection is 1Gbps Ethernet.
Comment 2 Urs Wolfer 2011-06-03 10:50:14 UTC
Can you please check if there is high CPU load when KRDC gets slow? Memory ussage?
Comment 3 Dennis Schridde 2011-06-03 12:11:58 UTC
CPU utilisation is at maximum (2.6GHz AMD Athlon64 X2) and memory usage is VIRT:375M RES:32M SHR:22M (retrieved via htop).
Comment 4 Urs Wolfer 2011-08-05 19:17:44 UTC
Can you reproduce this issue all the time? Do you have a slow connection?
Comment 5 Dennis Schridde 2011-08-09 08:57:36 UTC
The connection is gigabit LAN and the problem was [1] reproducible every time.
The server was provided by Xen running on a x86_64 RHEL 5.6.

[1] I did not try again since reporting the bug, but until then it was reproducible for several weeks.
Comment 6 Jamie Smith 2012-02-04 06:10:56 UTC
KRFB and KRDC seem to function fairly well as a pair after kde 4.8.0. I think the issue may have been in kwin.
Comment 7 Dennis Schridde 2012-02-04 12:36:10 UTC
(In reply to comment #6)
> KRFB and KRDC seem to function fairly well as a pair after kde 4.8.0. I think
> the issue may have been in kwin.
The issue did not appear in conjunction with KRFB, but with the Xen VNC server. Does the KRFB/KRDC combination use VNC at all?
Comment 8 Jamie Smith 2012-02-06 08:50:32 UTC
On Saturday February 4 2012 12:36:10 PM Dennis Schridde wrote:
> https://bugs.kde.org/show_bug.cgi?id=274816
> 
> 
> 
> 
> 
> --- Comment #7 from Dennis Schridde <devurandom gmx net>  2012-02-04
> 12:36:10 --- (In reply to comment #6)
> 
> > KRFB and KRDC seem to function fairly well as a pair after kde 4.8.0. I
> > think the issue may have been in kwin.
> 
> The issue did not appear in conjunction with KRFB, but with the Xen VNC
> server. Does the KRFB/KRDC combination use VNC at all?

I often confuse krdc / krfb but the server uses vnc and the client uses rdp 
and vnc.
Comment 9 Urs Wolfer 2012-12-30 18:16:18 UTC
Can you still reproduce this issue with xen vnc and a recent version of KRDC?
Comment 10 Dennis Schridde 2012-12-30 20:10:41 UTC
(In reply to comment #9)
> Can you still reproduce this issue with xen vnc and a recent version of KRDC?
I did not try in a long time. We use Vinagre now.
Comment 11 Andrew Crouthamel 2018-11-09 01:09:54 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 12 Andrew Crouthamel 2018-11-20 04:05:09 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 13 Justin Zobel 2023-01-01 04:19:41 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 14 Bug Janitor Service 2023-01-16 05:13:00 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 15 Bug Janitor Service 2023-01-31 05:05:17 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!