Bug#237293: krfb: solved!

2004-04-18 Thread Kyler Laird
Package: krfb Version: 4:3.2.2-1 Severity: normal Followup-For: Bug #237293 This issue seems to have been fixed in the latest upgrade. Thank you. --kyler -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kern

Bug#237293: krfb: fixed in upstream

2004-04-08 Thread Kyler Laird
Package: krfb Version: 4:3.2.1-1 Severity: normal Followup-For: Bug #237293 This problem has been solved "in HEAD and the 3.2 branch" of the upstream version. http://bugs.kde.org/show_bug.cgi?id=77412#c32 Can we get a fixed version in Debian? Thank you. --kyler

Bug#237391: kdelibs-bin: Invocation of krfb omits socket.

2004-03-11 Thread Kyler Laird
Package: kdelibs-bin Version: 4:3.2.1-1 Severity: normal Bug #237293 (filed against krfb) appears to be caused by a problem with kdeinit. Please do not copy me on updates. Thank you. --kyler -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'uns

Bug#237293: krfb: bad file descriptor

2004-03-10 Thread Kyler Laird
Package: krfb Version: 4:3.2.1-1 Severity: normal Followup-For: Bug #237293 more digging... The incoming krfb port is monitored by kdeinit. An incoming request is handled by calling /usb/bin/krfb with arguments such as "--kinetd 17". >From the strace output, it appears that krfb expects to see /

Bug#237293: krfb: socket not open

2004-03-10 Thread Kyler Laird
Package: krfb Version: 4:3.2.1-1 Severity: normal Followup-For: Bug #237293 O.k., I think I've determined all that I can without diving into the source. I got on a KDE 3.1 machine and monitored calls to krfb. I discovered that two socket file descriptors are availble to krfb. The one that is sp

Bug#237293: krfb: fails on incoming connection

2004-03-10 Thread Kyler Laird
Package: krfb Version: 4:3.2.1-1 Severity: grave Justification: renders package unusable After upgrading to 3.2, remote desktop sharing fails on two machines. On the first attempt to connect to port 5900, the connection is made, there is a short pause, and the connection is dropped (with no RFB pr