Summary: | Connection quality selection is not performed | ||
---|---|---|---|
Product: | [Applications] krdc | Reporter: | Martin Schnieders <kde> |
Component: | general | Assignee: | Urs Wolfer <uwolfer> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | komputes |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Screenshot |
Description
Martin Schnieders
2008-07-15 23:31:19 UTC
Maybe the vnc server does not support different qualities.. Could you please try with another vnc server? I tried this with a former version of krdc (3.5.9) and it worked properly (Server is the XServer of OpenSuse 10.2) Does it also not make a difference if you select medium-quality? It behaves in the same way: High-Quality only Additional information: The problem also occurs with Kde 4.1 RC1 I have no idea how to debug this issue. I cannot reproduce here. Can you please start KRDC from konsole and post the output here? I think the server probably ignores some settings. I can also reproduce it with OpenSuSE 10.2 (XServer ) Starting KRDC from konsole only produces krdc(7531) KBookmarkManager::notifyChanged: KBookmarkManager::notifyChanged ( "" ) Any hidden debug parameter? I forgot the Xserver version: xorg-x11 7.2-28. Ok, your KRDC (KDE) is not compiled in debug mode. Then it produces less debug output in konsole. You could try to install debug packages if these are available. See http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports for informations how to install such packages. Probably you can also try with tightvnc server to see if you can reproduce there. Created attachment 26435 [details]
Screenshot
This is a screenshot taken from KRDC, using "low-quality" settings, connected
to a vnc4server (4.1.1) on Kubuntu 7.10
by the way: A connection using krfb 3.5.8 on kubuntu 7.10 seems to work properly using gdb with krdc and the connection mentioned in #7 does not produce any useful debug output. It does not produce useful output in GDB because there are no debug symbols are commpiled in. You would need debug packages / binaries for that. KRDC in KDE 3.5 uses a very old version of the VNC library, so it can not compared to the new version. Most probably the issue is in the VNC library (LibVNCClient). I do always the same in KRDC, and with my connections it seems to work. So I think it's an issue with some specific VNC servers plus libvncclient. I think, there is some kind of misunderstanding ;): KRFB of 3.5.8 is only offering the connection. As client, I'm using KRDC of KDE 4.1 RC1 all the time. The package manager is not offering any krdc-dbg or kdelibs-dbg package for Kubuntu 8.04. Ahh, sorry. But still, it seems some problem with some vnc servers... I have no idea about kde debug packages in kubuntu... In Kubuntu 8.04 the debugging symbols would be in the kdenetwork-kde4-dbg package. Either that or kdenetwork-dbg-kde4. 8.04 was a long time ago. In Kubuntu 8.10 you can find the debugging symbols in the kdenetwork-dbg package. It would probably be worth mentioning the downstream bug report too: https://launchpad.net/bugs/311092 Running the following combination allows compression through pixelation (instead of through color stripping). vino 2.26.0-0ubuntu1 krdc 4:4.2.1-0ubuntu1 I think we can close this since the issue was with the vino server. It's most probably a bug in some VNC servers and / or libvncclient. KRDC handles things correctly here. |