The Kubuntu 9.10 install failed at the point of seeing the startup splash with the disk drive image, just as the toolset is begining to fade in on the troubled computer. Searching the Web suggested it was some kind of video driver issue. Fedora 12 KDE failed to launch the live CD at the same point.

I scrounged up another desktop computer and got Kubuntu 9.10 installed (fresh download on Feb 2, 2010) and was able to get a good install. Did software updates.

Krfb runs. It accepts the request to MAKE an invitation. But at the guest computer, after entering the IP address:5900 a dialog box pops up to say "VNC server closed connection".

Web searches about Krfb seem to suggest it is unreliable/buggy. I'm wondering what the Krfb page should say right now.

If the software doesn't work, should the UserBase docs be up front about it?
Is a developer fixing it? The KDE4 desktop computer is running 4:4.3.2-0ubuntu4 (i386). Interestingly, the Krfb program itself doesn't have an "about" menu item. I had to get the package information from Kpackagekit.

On the Fedora gnome system, I installed the TigerVNC server to do my initial testing of the Krdc client, for what that's worth. The client works great, and maybe the Userbase documents should suggest using a VNC server supported on KDE4/distribution until this issue gets closure.

The KDE3 Krdc client won't connect to KDE4 server Krfb, either, though the message is different.

The good news: I've figured out how to get Krfb to work from my Kubuntu 9.10 install.
The bad news: It is not a completely straightforward process. There are currently some details that need to be done carefully.

I'll be able to begin writing the Krfb page, but I'll put some cautions in, for sure.

I think I've found the main developer, as listed in the "about" which I also located. I'll try to contact him.

Some feedback on Identi.ca !KDE suggests that the 4.4 SC version of Krfb is being worked on.

Give me a couple of days to get my notes together, then check back on my Userbase page to check my progress.

I'm away from home until late-ish Monday, and using an open wifi. I'll get back to you when I'm home. You sound to be coping quite will with a difficult situation. As a principle I think we have to follow the lines of 'this is how it's supposed to work. Unfortunately with version x.x there is a problem with.....' then try to remember to update the entry when a fix comes out. Hope that helps.

I was going to suggest that we try to contact the developer(s) but I see you already have that in hand. I've seen the work on your user page and it looks to be coming along very well. I'm looking forward to trying this, when you tell me that it's ready.

It's a shame about the install problems you have had, but I know some people have seen such issues caused by display drivers. Since you've found a work-around I won't pursue that any further at the moment. If you want help with it later, contact me by email (annew at kde dot org)

@annew,

I responded to your comment about a firewall tutorial on my user talk page, but thought might bring it up here, too. It relates to the issue of "when to stop". Clearly we who are in the aftermath of a Klassroom course are using your expertise to help us, and I'm glad for your help.

I agree that a firewall tutorial would be helpful, but it goes beyond the direct use of Krfb/Krdc. I think it should be a separate tutorial page. I'll look around to find simple firewall tutorials, but as I said, there are many ways to deal with them. Most Linux firewalls use iptables, I think, but what I've read is that it is typical to use some simplified interface to make the forwarding rules. The Fedora 12 GUI firewall tool was easy. It offered selection of common ports to open, but others, like the Ubuntu tool are command-line/terminal based.

Since the primary users of Krfb/Krdc will be novices getting help from "experts", it seems that a firewall tutorial would be directed toward those experts, and it wouldn't be good for the basic Krfb/Krcd pages.

This, is, of course, just my opinion. You have been at this longer than I have.

Maybe, too, this is a case where somebody with even more expert knowledge can be called in to do a firewall tutorial. I certainly felt that I was stumbling around during the preparation for these pages. I don't want others to need to stumble around...possibly giving up. Up to this point, I've been ignorant of firewalls. My Ubuntu/Kubuntu machines don't enable one by default. I only used the Fedora 12 as an interim step to getting a KDE4 setup to work. Writing up my Fedora experience is going to take these KDE4 Userbase pages in an odd direction.

I just did a quick search of the Userbase for "firewall" and only found a short page related to Kopete, so maybe a general tutorial about firewalls is a good idea. If some other expert doesn't step up, I'll keep digging around.

Therefore, if you think the Krfb/Krdc pages are basically ready, I'd like to transfer them. (I noticed that somebody has translated my placeholder information into Danish...wow.)

I agree that we can't, and shouldn't, include a firewall tutorial in this page. I think it might be useful to comment that many people use applications such as Shorewall, Firestarter or Webmin to control their firewall, since many distros include these applications. As to whether we should do a tutorial separately, that hits the 'advanced users' sector, and currently we don't have many people willing to write for that. I will look into it, though at the moment my time seems somewhat limited.

Sometime this week I hope to try out your tutorial. Thanks for doing it. I'll let you know how it goes.

Yes, our Danish, Chinese and Russian translators are working hard, though we are distinctly short of volunteers for the other languages.

We now have a new space in klassroom, viewtopic.php?f=71&t=85944, where any follow-up work or questions can take place.