On 25 Jan 2020 at 7:00, Ed Greshko wrote:
From: Ed Greshko <ed.greshko(a)greshko.com>
Subject: Re: F8 key not workingwith vncviewer??
To: Fedora <users(a)lists.fedoraproject.org>
Date sent: Sat, 25 Jan 2020 07:00:56 +0800
Send reply to: Community support for Fedora users
<users(a)lists.fedoraproject.org>
On 2020-01-25 06:52, Ed Greshko wrote:
> On 2020-01-25 03:07, Michael D. Setzer II via users wrote:
>> Not sure when it stopped working, since don't use it often.
>> Had noticed that start of connections it was listing F8^M key??
>> Was trying to use it when connected to a windows machine, and nothing
>> happens. Then tried it on one of my other Fedora machines, and from a
>> terminal window it puts out a ~ each time the key was pressed, but no menu.
>> Connected to the same machines using a windows machine with tightvnc's
>> vncviewer, and the F8 key works perfectly.
>> I'v seen a similar problem with something in the past, where the files where
>> using the DOS CR/LF instead of the linux LF. In that case, just used the
>> dos2unix on source code and rebuilt.
>>
>> This is a Fedora 30 machine fully updated.
>> The man and help for vncviewer doesn't appear to show any contact
>> addresses.
>>
>> Did note that the default file in the .vnc directory was in DOS format, but
>> running dos2unix on it made no difference.
>>
>> Note sure where to report this. Currently have to reboot machine into old
>> Windows 7 OS that was originally on notebook to use the F8 key..
>>
>> Thanks.
> My vncserver is running on a rawhide instance tigervnc-server-1.10.1-2.
> The viewer is run from an updated F31 system tigervnc-1.10.1-1.
>
> When I connect to the sever and a connection is open the F8 keep pops up a menu as
it
> is supposed to.
>
>
Oh, I should add that my server and client are both running KDE and using the Xorg
server.
Are you running your vncviewer in GNOME/Wayland?
Finally figured the problem. The .vnc directory had a default.tigervnc file in it
that was in the DOS CR/LF formated text file. It had been there for some
time, and didn't cause an issue. At some point it caused the F8^M to show
up, but didn't use the key so never looked into it.
Had changed it with dos2unix, but still got the same result. Problem was I
was in root mode, so it was using the .vnc default.tiger, which was in the
/root/.vnc directory. After fixing that one as well it is working.
Not sure what created that file. Setup vnc on another user account, and the
file was not created. Also, tried renaming it, and it works fine with out it. Might
be that it was created with a previous version. Options seem to be default
values, but being in DOS format caused the ^M.
--
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned: 19,471
Processing time: 32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)
BOINC@HOME CREDITS
ROSETTA 66311323.990119 | ABC 16613838.513356
SETI 109804121.703177 | EINSTEIN 141859222.999240