Re: tigervnc and fltk

This is a multi-part message in MIME format...

------------=_1781460366-1253-35652
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 6/14/26 12:14 AM, Pierre Labastie ([email protected] via 
blfs-dev Mailing List) wrote:
> On Sat, 2026-06-13 at 21:48 -0500, Bruce Dubbs wrote:
>> I've been working on updating tigervnc today.  Right now we have an
>> instruction to
>> allow it to be built with fltk-1.4.  However vncviewer does not work
>> properly with
>> that version.  I downgraded to fltk-1.3 and vncviewer works properly.
>>
>> We have a couple of options.  We can leave fltk at version 1.4 and
>> tell users to
>> build gnome-connections to access a vnc or we can downgrade fltk to
>> version 1.3.11.
>>
>> Looking at BLFS we have three packages that use fltk:
>>
>> pinentry   -- optional
>>      This package does look for fltk-1.4 but according to configure
>> fltk-1.3 is OK.
>>
>> alsa-tools -- recommended for hdspconf and hdspmixer)
>>      hdspconf is a gui app to control hw settings and internal routing
>> for
>>        RME Hammerfall DSP (HDSP) audio interfaces
>>      hdspmixer is a gui app to control hw mixing for HDSP audio
>> interfaces.
>>
>> tigervnc - required
>>
>> I looked at Arch and they have both fltk-1.4 and fltk-1.3
>> instructions.  The
>> difference is that version 1.4 supports HighDPK displays and 1.3 does
>> not.
>>
>> For both alsa-tools and tigervnc Arch uses fltk-1.3.  They do not
>> mention fltk for
>> pinentry at all.
>>
>> My feeling is that the need for tigervnc's vncviewer is the greatest
>> for BLFS.
>>
>> There may be other non-BLFS packages that really need fltk-1.4.
>>
>> I want to get opinions on how to go on this.  What do you think?
> 
> I'm somewhat amazed that we discover just now that the move to fltk-
> 1.4.x broke vncviewer; the move occurred in January 2025!
> 
> A more recent change is the move to nettle-4.x. There are instructions
> to adapt to it. I added those instructions, but couldn't test at the
> time (then I forgot about it, sorry...). So isn't the problem with
> nettle rather?
> 
> For the main question, I have no strong feelings...
> 
> Pierre
> 
> 
Hi Pierre!

The Nettle stuff affects vncserver itself, not vncviewer. Other VNC 
clients such as KRDC, gnome-connections, and RealVNC Viewer work 
perfectly with the server component :)

vncviewer on my system as well against FLTK 1.4 causes the window to 
spawn in a bad place and not be interactable in some places, and the 
right click doesn't work either...

I'm also on board with dropping back to FLTK 1.3 due to this for now 
since upstream will need to properly adjust to it.

-- 
- Doug

------------=_1781460366-1253-35652
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page
------------=_1781460366-1253-35652--