Bug 114063
| Summary: | vncconfig -connect fails | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Franks <john> | ||||||
| Component: | vnc | Assignee: | Tim Waugh <twaugh> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 1 | ||||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | 4.0-0.beta4.8 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2004-01-23 17:24:25 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
John Franks
2004-01-22 01:41:43 UTC
Hmm, I don't see this here. Could you please run 'strace -p PID 2>log' (with the process ID of Xvnc substituted for PID) just before running vncconfig, and stop it with Ctrl-C once the connection fails? Then please attach the 'log' file. It'll be that some signal interrupts the connect() system call, but depending on who set the signal (us, or X) we can either fix the signal set up or try the connection again. Created attachment 97163 [details]
Output of strace of Xvnc
As requested this was generated by
strace -p Xvnc_PID 2>log
After starting strace I ran
vncconfig -display :1 -connect <hostname>
I think this might be fixed in vnc-4.0-0.beta4.7, which should show up in rawhide in the next day or two. Please let me know. http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/Fedora/RPMS/ Well, it is not fixed, but improved. Using vnc-4.0.0.beta4.7 a connection can be made about every third try. It is at least usable now as I can always connect in two or three tries. The failures appear identical to the previous situation. I think the vnc-restart.patch file should use EINTR instead of ERESTART. I'll build a new package. Created attachment 97212 [details]
Revised vnc-restart.patch
You seem to be right! I downloaded the beta4.7.src rpm and revised
your patch replacing
if (e == ERESTART)
with
if ((e == ERESTART) || (e == EINTR))
and built a binary rpm. The result works like a charm.
The revised vnc-restart.patch is attached.
Great. Just to be sure, could you please try these packages?: http://cyberelk.net/tim/data/tmp/vnc-4.0-0.beta4.8.i386.rpm http://cyberelk.net/tim/data/tmp/vnc-server-4.0-0.beta4.8.i386.rpm They simple replace ERESTART with EINTR. I don't think that the application is ever meant to see ERESTART. I tried 4.0-0.beta4.8 and it works fine. The problem seems to be solved. Thanks. Great. Patch submitted upstream. |