Bug 585930
| Summary: | vnc totally inop in F13 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Eric Frey <efrey> |
| Component: | vnc | Assignee: | Adam Tkac <atkac> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | atkac, ovasik, stickster |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | tigervnc-1.0.90-0.11.20100420svn4030.fc13 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-05-18 21:52:44 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: | |||
*** Bug 585895 has been marked as a duplicate of this bug. *** This seems like an issue with gcc, not sure yet. As a workaround let's build sources with "-fno-omit-frame-pointer", Xvnc seems fine when built with that option. Sorry for troubles. tigervnc-1.0.90-0.10.20100420svn4030.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/tigervnc-1.0.90-0.10.20100420svn4030.fc13 The new package appears to fix the problem for me (was bug 585895). tigervnc-1.0.90-0.10.20100420svn4030.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update tigervnc'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/tigervnc-1.0.90-0.10.20100420svn4030.fc13 tigervnc-1.0.90-0.11.20100420svn4030.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/tigervnc-1.0.90-0.11.20100420svn4030.fc13 tigervnc-1.0.90-0.11.20100420svn4030.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update tigervnc'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/tigervnc-1.0.90-0.11.20100420svn4030.fc13 tigervnc-1.0.90-0.11.20100420svn4030.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: Hitting any key on a tightvnc session connected to :40.0 causes immediate termination of the Xvnc process, with no apparent logging information in the system or the .vnc logs. System running under VMWare 7.1 Beta, Win 7 host system. Viewer is RealVNC Personal Edition VNC Viewer 4.4.3(r16583). F13 kept up to date with test updates on a daily basis. Version-Release number of selected component (if applicable): Occurred when I put in the Apr 23 07:11:14 Updated: tigervnc-server-1.0.90-0.9.20100420svn4030.fc13.x86_64 Apr 23 07:11:17 Updated: tigervnc-1.0.90-0.9.20100420svn4030.fc13.x86_64 Apr 23 07:11:17 Updated: tigervnc-server-module-1.0.90-0.9.20100420svn4030.fc13.x86_64 How reproducible: Steps to Reproduce: 1. Start vnc session with: vncserver -geometry 2000x1400 -depth 24 :40 2. connect vnc viewer to session; starts up OK. 3. Hit any key. Actual results: Expected results: Additional info: