This has been fixed in trunk and can be back-ported into branches/1.1.x
if needed.
On 6/15/12 1:51 AM, Paul Melis wrote:
> On 06/15/2012 07:09 AM, DRC wrote:
>> Can you determine exactly what resource file was causing the issue? If
>> the TightVNC DEB is, for instance, installing a file called Vncviewer in
>> the resources directory (typically /usr/share/X11/app-defaults), then
>> TurboVNC is probably reading that.
> Yes, that seems to be the case:
>
> paulmlocal@saralt0169:~$ strace -o out -f /opt/TurboVNC/bin/vncviewer
> localhost:1
> Connected to RFB server, using protocol version 3.8
> Enabling TightVNC protocol extensions
> Performing standard VNC authentication
> [...]
>
> paulmlocal@saralt0169:~$ grep app-defaults out
> 3206 access("/usr/lib/X11/en_US.utf8/app-defaults/Vncviewer", R_OK) =
> -1 ENOENT (No such file or directory)
> 3206 access("/usr/lib/X11/en/app-defaults/Vncviewer", R_OK) = -1 ENOENT
> (No such file or directory)
> 3206 access("/usr/lib/X11/app-defaults/Vncviewer", R_OK) = -1 ENOENT
> (No such file or directory)
> 3206 access("/etc/X11/en_US.utf8/app-defaults/Vncviewer", R_OK) = -1
> ENOENT (No such file or directory)
> 3206 access("/etc/X11/en/app-defaults/Vncviewer", R_OK) = -1 ENOENT (No
> such file or directory)
> 3206 access("/etc/X11/app-defaults/Vncviewer", R_OK) = 0
> 3206 stat("/etc/X11/app-defaults/Vncviewer", {st_mode=S_IFREG|0644,
> st_size=3198, ...}) = 0
> 3206 open("/etc/X11/app-defaults/Vncviewer", O_RDONLY) = 4
>
> paulmlocal@saralt0169:~$ dpkg-query -L xtightvncviewer
> [...]
> /etc/X11/app-defaults
> /etc/X11/app-defaults/Vncviewer
>
>
>> The solution would be to change our resource name to something else,
>> like Turbovncviewer instead of Vncviewer. It represents a minor
>> backward compatibility break from previous releases, but people override
>> the resources so rarely that I'm OK with that.
>
> I think that would be a good idea, this problem really confused me for
> some time.
>
> Regards,
> Paul
>
>>
>>
>> On 6/14/12 2:37 AM, Paul Melis wrote:
>>> Hi,
>>>
>>> I just debugged a really weird issue, perhaps this info is useful for
>>> someone. I've got TurboVNC 1.1 installed on my Ubuntu system, using the
>>> official 64-bit .deb package:
>>>
>>> root@saralt0169:~# dpkg -l |grep turbovnc
>>> ii turbovnc 1.1-20120524
>>> A highly-optimized version of VNC that can b
>>>
>>> root@saralt0169:~# /opt/TurboVNC/bin/vncviewer --help
>>> TurboVNC Viewer 64-bit v1.1 (build 20120524)
>>> [...]
>>>
>>> Now, when I ran the viewer executable ($ /opt/TurboVNC/bin/vncviewer) and
>>> connected to a VNC server *the menu bar of the viewer identified itself as
>>> TightVNC*, e.g. it said "TightVNC: ....". Furthermore, the menu you can
>>> call up with F8 seemed to be broken, as some of the widgets weren't
>>> properly aligned, and I was sure there's options missing (e.g. request
>>> lossless refresh). See attached screenshot.
>>>
>>> I really did not understand what was going on here. I even tried building
>>> TurboVNC from source, using the resulting executable gave me the same
>>> confusing result. Looking at the code the window title is set using an X
>>> resource. It turned out that of the package xtightvncviewer that I had
>>> apt-get remove-d still had some config files left, and those probably got
>>> read by TurboVNC at startup. apt-get purge-ing xtightvncviewer solved the
>>> problem.
>>>
>>> Regards,
>>> Paul
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users
