Version: (using KDE KDE 3.2.1) Installed from: SuSE RPMs OS: Linux After upgrading to KDE 3.2.1, krfb/remote desktop sharing/vnc no longer works. Via the Control Center, I have krfb running on port 3389 allowing uninvited connections without confirmation, etc. This worked fine up until 3.2.1. After the upgrade, I can no longer make these connections. I've tried changing and re-appying the config via Control Center. "Something" appears to still be listening on 3389, but I get nothing when using a VNC client, and when telneting I get: linux:~ # telnet 127.0.0.1 3389 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. Connection closed by foreign host. <--- Happen IMMMEDTIATLY Normally I'd get something like: linux:~ # telnet 127.0.0.1 3389 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. RFB 0.000 <--Not the real numbers, I don't remember them. I also seem to remember that previous to 3.2.1, there would be an Xvnc process running, this is no longer present. I use krfb a lot, for a lot of things. I would really appreciate some assistance here. Thank you, Dave M
Xvnc is a very different server and had nothing to do with krfb. You can find out which process is listening on that port using netstat. Enter "netstat -pnl | grep 3389" as root. if krfb is running you should see "kdeinit: kded" or "kded". If kded is listening, the next step is to check whether krfb is actually enabled. Executed with your regular user account, "dcop kded kinetd isEnabled krfb" should return "true" and "dcop kded kinetd port krfb" should return your port, 3389.
Thanks Tim, here are the results: netstat -pnl | grep 3389" "tcp 0 0 :::3389 :::* LISTEN 2661/kdeinit: kded" dcop kded kinetd isEnabled krfb: "ERROR: Couldn't attach to DCOP server!" Thank you for your continued assistance. It really is appreciated. --Dave
Did you run the DCOP command with your regular user account? (if DCOP is really broken you would have a much larger problem, other apps wont work as well) If you run it as root without using a command like 'sux' it can't work.
I know that I will probably get a beating for this, but I always run as root, never as another user. Also, excuse my apparent ignorance, but I am not familiar with the sux command or it's syntax and there is no man page for it. I haven't noticed any other issues, but this all did work right up until I upgraded from 3.2.0 to 3.2.1. Thank you, Dave
Ok, I did this, hopefully this is accurate: "linux:~ # dcop --user root kded kinetd isEnabled krfb true" "linux:~ # dcop --user root kded kinetd port krfb 3389" Like I said, I know I will get slammed, but I only use root, for KDE, shell, everything. So it looks like it is enabled and has the right port... Any other ideas? Thanks, Dave
Oh, if you're coming from 3.2.0 this is really odd, because there hasnt been a single change since 3.2.0. The last one was between 3.2.0b1 and 3.2.0b2. Can you run "krfb"? (When kinetd accepts a connection, it calls krfb, which handles the connection and also prints the "RFB 0.00..." string)
When I drop to shell and run krfb I get the graphical "Invitation/Welcome to..." menu. Nothing in the shell. --Dave
That's ok, just wanted to know whether the file is in the path. It also checks whether DCOP communication is working ok. Can you connect to the HTTP server at http://localhost:5800/ , or access it using telnet? Or does it also close the connection?
Nope. In Konqueror I get the ol' "Connection to localhost is broken" message or it just times out. Telnetting gets me this: linux:~ # telnet localhost 5800 Trying ::1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host --Dave
Ok, then it seems like kinet can't find the apps. This can be confirmed by starting the Control Center (kcontrol), Sound & Multimedia, System Notifications. Select event source "KInetD" and turn on the "Could not call process..." option (I wonder why it's not turned on by default, i should do this). The best notification is certainly the pop-up dialog, just click in the 'i' column or go to 'More options' to select its checkbox. If kded can't find krfb: how do you start KDE? Do you have KDEDIR or KDEDIRS set, and is the PATH correct at the time kded is started?
Ok... Here's what I've got: 1. I turned this on, and I haven't seen anything yet, even when trying to make the connection into my PC. 2. KDE is started however SuSE normally sets it up, I guess. I but the partition, KDM is started and I select KDE off the menu and enter un/pw. 3. There is no KDEDIR or KDEDIRS set, but PATH seems correct. --Dave
I don't know if this is helpful, but I just noticed it so I figured I'd mention it... Normally, when KRFB was working, an icon was displayed in the tray when there was a connection. Now, though, if I try telnetting to 3389, I see something flash onto and off of the tray really quickly. Too quickly to make out what it is, but maybe it means something. *shrugs* Thanks again, Dave
Oh, yes, the icon means something: that krfb is actually started. But it makes me wonder why not even the HTTP server works, which is as simple as a kinetd invoked service could be... i think i need to come up with a script that shows more error messages...
I would appreciate it greatly, as I do everything you've done to help thus far. Thanks, Dave
I did some research into this. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=237293 It's *not* that "kinet can't find the apps". It's a problem of not giving the app a socket. --kyler
Thanks, that's good to know. Well, actually not that good, because it means that something is closing the sockets when starting the new process. As krfb_http (a bash script) is also working, it must be done by KProcess. I'll try to check whether there were any changes in KProcess, and maybe I have to replace it with direct libc calls.
Kyler, thanks for the input, anything that helps resolve this issue is very much appreciated. I too have become quite dependant on krfb and this issue isn't making things very much fun. Tim, thanks. (Once you've looked into a possible KProcess issue) Were you able to find out anything helpful? I'll be forever in your debt if we can get this issue canned soon. :) Thanks everyone, Dave
Just for the sake of it being said... This is definitly not a one or two person issue. Searching google shows a lot of reports of the problem, sadly no solutions. :( --Dave
Hey Tim, any chance of getting a status update on this? Were you able to figure anything out? Not trying to be pushy or anything, just wondering where this is at, I miss my krfb-coolness, heh. --Dave
No, couldnt find anything in KProcess, nor any kdelibs changes between 3.2.0 and 3.2.1 that may have caused it.
Well, that's disappointing... Any advice? Should I wait or will I need to muck my way through a downgrade? I use my PC via krfb almost as much as I do locally. Clearly at this point this is an actual issue, not something specific to me. Thanks, Dave
i can't make any promises on this point, and even if I could, I don't know when the next set of suse rpms appears.
Well, I'm definitely not asking for promises. I'm not going to hold anything you say against you, heh. If you have anything that to add that isn't 100%, I'd still be interested. In any case, lets take this approach... Will the issue continue to be looked into, or is it going to get put on the back burner? --Dave
It's currently my no1 bug, but it's hard to work on a bug that you can't reproduce. So right now I am trying to reproduce it by updating my local installation. I also try out ideas, e.g. i checked the KServerSocket class a few hours ago.
Thanks Tim! I don't doubt you have worked on it, just didn't know if it was a priority or not. Glad to know it is! :) --Dave
Tim, just checking in to see if there have been any new developments... Did updating your local installation help? Thanks in advance. --Dave
yes, i can reproduce it locally now (with kdecvs, after updating only kdelibs and kdebase). didnt have the time to work on it, but i hope to find it this weekend.
Hey Tim... Just checking in. How has the investigation gone since the 19th? Anything new to report? Thanks again! --Dave
Any pre-weekend updates? Even if it's just status, I would love to be kept in the loop a little, even if it's a very outer loop, heh. :) --Dave
Not much to say, can't find the kdelibs change that caused this, i will now try to rewrite that part that starts krfb, deadline is april 3rd (because that's when 3.2.2 is tagged).
Just want to let you know I'm also experiencing this problem. I'll update my KDE installation to CVS HEAD as soon as this is solved :)
After begging for hints on kde-core-devel Waldo Bastian came up with the solution (http://lists.kde.org/?l=kde-core-devel&m=108076716300296&w=2). Bug fixed in HEAD and the 3.2 branch. Thanks for all the reports and comments.
Tim... I would like to thank you for all your efforts. I cannot wait until 3.2.2 comes so I can once again use the VNC client on my horrid Windows PC at work to get to my home computer. Thanks, Dave.
Very nice :) Thanks Tim and Waldo. I'm doing a "cvs update -d" in my KDE tree at the moment.
*** Bug 78699 has been marked as a duplicate of this bug. ***