Re: [TCLCORE] 9.0b3rc0 test results / bugs

[Harald O. <har...@el...>]

Francois,
thank for bringing this into our attention and sorry for the annoying 
situation. The ticket you mentioned is indeed fixed for me (but not for 
Ashok).

But this ticket is new and Ashok fixed it with light speed. Please look 
to the description here:
https://core.tcl-lang.org/tk/info/d233f01e2a8b3b68
including the IMHO great fix.

Thanks for all your work !
Harald


Am 26.07.2024 um 19:22 schrieb Francois Vogel:
> This is reported for each and every release candidate. It's the 
> following ticket:
> 
> https://core.tcl-lang.org/tk/tktview/ee397e0a55
> 
> Jan has set it to Pending+Fixed but it isn't fixed as you noticed once 
> more, and I'm wondering it's pending what.
> 
> Since we stepped on each other's toes with Jan on this ticket (see 
> discussion there), I have abandoned solving this almost one year ago.
> 
> Regards,
> 
> Francois
> 
> Le 26/07/2024 à 15:53, Harald Oehlmann a écrit :
>> Ashok,
>> great tests, I appreciate !
>>
>> Am 26.07.2024 um 15:38 schrieb apnmbx-public--- via Tcl-Core:
>>> Tk – shows usual “Clipboard busy errors”.
>>>
>>> More important, tktest90 crashes on exit (I think). Narrowed it down 
>>> to winClipboard.test (or at least this file by itself triggers the 
>>> crash unlike other test files). Anyone testing will likely need to 
>>> enable the JIT debugger on Windows else you will not notice the crash 
>>> as it happens while exiting. Alternatively, check the Windows 
>>> Application log where the crash is reported. My VS Studio debugger 
>>> reports it cannot determine crash location because the unhandled 
>>> exception is .NET 4.0 and the debugger only supports 2.0. I don't 
>>> even know where .NET enters the picture (does Tk use any UI features 
>>> from .NET) ?
>>
>> I suppose, another application written in .NET4 running on your 
>> computer and holding the clipboard is crashing due to the Tk clipboard 
>> requests.
>>
>> Clipboard is a shared resource and specially terminal programs 
>> (UltraVNC, Windows Remote Desktop or any virtualisation software may 
>> mess this up). Also, I have seen that in Windows 11, there is an 
>> extension to get an extended cliboard with a history list.
>>
>> I can reproduce the "usual Clipboard busy errors" with UltraVNC.
>> It you have "Windows Remote Desktop" active, there is an option when 
>> setting it up: press Options on the first connection screen, then 
>> choose "local resources", then Keyboard. Choose "on this computer" 
>> there. Also uncheck the clipboard checkbox.
>>
>> Just arbitrary guesses and eventually only noise but anyway,
>> Harald