Description of problem: Caps-lock does no longer work after upgrading to the last version Version-Release number of selected component (if applicable): tigervnc-server-1.0.90-0.13.20100420svn4030.fc13. How reproducible: Always, both on i686 and x86_64 Steps to Reproduce: 1. start a tigervnc server 2. use vncviewer to connect to that server 3. Set caps-lock and type whichever alphabetic character Actual results: Characters are never capitalized Expected results: Characters should be capitalized Additional info: It worked correctly until version tigervnc-1.0.90-0.12.20100420svn4030.fc13 included. Downgrading to tigervnc-1.0.90-0.12.20100420svn4030.fc13 restore the Caps-lock functionality
*** Bug 632076 has been marked as a duplicate of this bug. ***
*** Bug 634347 has been marked as a duplicate of this bug. ***
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
Created attachment 447806 [details] starce of "service vncserver start"
Created attachment 447807 [details] vnc configuration file
Stop it!! The server does not even start using tigervnc-1.0.90-0.14.20100420svn4030.fc13. On both i686 and x86_64 typing service vncserver start it fails with: [root@pcalfr alfredo]# service vncserver start Starting VNC server: 1:alfredo Ambiguous output redirect. [FAILED] I attach the full strace of service vncserver start as well as my config file
(In reply to comment #6) > Stop it!! The server does not even start using > tigervnc-1.0.90-0.14.20100420svn4030.fc13. On both i686 and x86_64 typing > > service vncserver start > > it fails with: > > [root@pcalfr alfredo]# service vncserver start > Starting VNC server: 1:alfredo Ambiguous output redirect. > [FAILED] > > I attach the full strace of service vncserver start as well as my config file I'm not able to reproduce this issue. Would it be possible to manually add "set -x" to the /etc/init.d/vncserver file, run `service vncserver start` again and attach output here, please? $ cat /etc/init.d/vncserver #!/bin/bash ... . /etc/init.d/functions set -x [ -r /etc/sysconfig/vncservers ] && . /etc/sysconfig/vncservers ...
Done. I am going to attach the output (vnc.out) in a moment. I also made a diff of the /etc/init.d/vncserver scripts, old and new, and clearly the only changed line (see diff.out attached as well in a moment) is the culprit. using the "old" /etc/init.d/vncserver with tigervnc-1.0.90-0.14.20100420svn4030.fc13, the server starts with no issue and a quick check seems to confirm that everything is fine (at least caps Lock is surely fine)
Created attachment 448428 [details] output of "service vncserver start" when set -x is added
Created attachment 448429 [details] diff between old and new /etc/init.d/vncserver
(In reply to comment #9) > Created attachment 448428 [details] > output of "service vncserver start" when set -x is added I think I've figured what's broken. Which shell is default for "alfredo" user? When you add "-s /bin/bash" parameter to the "runuser" command in the /etc/init.d/vncserver script (runuser -s /bin/bash -l ${USER} -c "...") does it solve your issue?
... tcsh and the answer is yes, with -s /bin/bash the server starts with no problem. Thanks!
.... oops... too quick to answer! Yes the server starts with no problem, but then the user is locked into bash, which obviously is very uncomfortable (all intializations, scripts etc broken...) to say the least
(In reply to comment #13) > .... oops... too quick to answer! Yes the server starts with no problem, but > then the user is locked into bash, which obviously is very uncomfortable (all > intializations, scripts etc broken...) to say the least tigervnc-1.0.90-0.15.20100420svn4030.fc13 should be fine, I've pushed it to -testing repo (http://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 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
I just installed the same package (0.15) on my 32 bit F-13 system and I can confirm the caps-lock still doesn't work for me. (In reply to comment #15) > 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
0.15 works fixes caps lock for me.
Looks like I didn't update the server, just the client. It works now for me too after updating the "tiger-server" package. The instruction below only did the client I noticed after double checking. (In reply to comment #16) > I just installed the same package (0.15) on my 32 bit F-13 system and I can > confirm the caps-lock still doesn't work for me. > (In reply to comment #15) > > 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.