Bug 633645
| Summary: | VNC init script is too verbose on stdout | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ambarish Sridharanarayanan <fedora> |
| Component: | tigervnc | Assignee: | Adam Tkac <atkac> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | atkac, extras-orphan, notting, ovasik |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | tigervnc-1.0.90-0.15.20100420svn4030.fc13 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-10-21 06:01:49 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: | |||
tigervnc-1.0.90-0.14.20100420svn4030.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/tigervnc-1.0.90-0.14.20100420svn4030.fc13 tigervnc-1.0.90-0.15.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: https://admin.fedoraproject.org/updates/tigervnc-1.0.90-0.15.20100420svn4030.fc13 tigervnc-1.0.90-0.15.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: Init scripts should not dump output on stdout and mess with the display. The vncserver initscript does. Version-Release number of selected component (if applicable): tigervnc-server-1.0.90-0.13.20100420svn4030.fc13.i686 How reproducible: Always Steps to Reproduce: 1. chkconfig vncserver on 2. Make sure there's a valid entry in /etc/sysconfig/vncservers 3. reboot and watch boot log Actual results: Starting SMB services: [ OK ] Starting VNC server: 1:foobar New 'myhostname:1 (foobar)' desktop is myhostname:1 Starting applications specified in /home/foobar/.vnc/xstartup Log file is /home/foobar/.vnc/myhostname:1.log [ OK ] Starting atd: [ OK ] Expected results: Starting SMB services: [ OK ] Starting VNC server: 1:foobar [ OK ] Starting atd: [ OK ]