Bug 433133
| Summary: | vncserver fails to work when $HOME includes space characters. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Anthony Stuckey <anthonystuckey> |
| Component: | vnc | Assignee: | Adam Tkac <atkac> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 8 | CC: | ovasik |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-01-09 07:39:40 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: | |||
Would it be possible test proposed update, please? You can download your arch from http://koji.fedoraproject.org/koji/taskinfo?taskID=578538. Thanks This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12 Description of problem: -bash-3.2$ /usr/bin/vncserver xauth: timeout in locking authority file /Network/Servers/mark.bme.utexas.edu/Volumes/Mark sh: /Network/Servers/mark.bme.utexas.edu/Volumes/Mark: Permission denied New 'miles.bme.utexas.edu:1 (astuckey)' desktop is miles.bme.utexas.edu:1 Starting applications specified in /Network/Servers/mark.bme.utexas.edu/Volumes/Mark Data/Users/astuckey/.vnc/xstartup Log file is /Network/Servers/mark.bme.utexas.edu/Volumes/Mark Data/Users/astuckey/.vnc/miles.bme.utexas.edu:1.log -bash-3.2$ df -k /Network/Servers/mark.bme.utexas.edu/Volumes/Mark\ Data/Users Filesystem 1K-blocks Used Available Use% Mounted on mark.bme.utexas.edu:/Volumes/Mark Data/Users 1464886912 1109081888 355805024 76% /Network/Servers/mark.bme.utexas.edu/Volumes/Mark Data/Users -bash-3.2$ ps auwwx | grep astuckey root 16475 0.1 1.0 17172 11364 ? Ss 11:40 0:00 sshd: astuckey [priv] astuckey 16481 0.0 0.9 17172 9852 ? S 11:40 0:00 sshd: astuckey@pts/3 astuckey 16482 0.0 0.1 4872 1412 pts/3 Ss 11:40 0:00 -bash astuckey 16522 3.0 0.0 4696 868 pts/3 R+ 11:51 0:00 ps auwwx astuckey 16523 0.0 0.0 4044 672 pts/3 S+ 11:51 0:00 grep astuckey -bash-3.2$ Having reviewed the vncserver source, the problem appears to be that $HOME is used unquoted in several places. Given the methods for which it is used, it appears that multiple different forms of quoting would be required to ensure proper behavior. Version-Release number of selected component (if applicable): vnc-4.1.2-23.fc8 How reproducible: Always Steps to Reproduce: 1. Create a user where the home directory path includes spaces. 2. Attempt to start vncserver. 3. Boom Actual Results: No VNC session was started. Expected Results: A VNC session should be accessible to the user. Additional info: