|
From: Bill K. <nb...@so...> - 2022-11-28 22:24:33
|
On Mon, Nov 28, 2022 at 01:47:47PM +0900, Shin-ichi TOYAMA wrote: > Hi! > > According to the Apache log, only one person has downloaded the test build so far, and no report has come. > > # This makes me a little bit disappointing to me though. > > Anyway, as far as I can confirm on my PC and some Virtual Machines, the symptoms reported this time occur always and only when running the x86_64 version on "Windows 11 22H2". > > I could not pinpoint the cause of the problem as there are many updates in the latest build environment, including the compiler, but considering that the application of 22H2 are going to be phased in, I think it would be better to release the new builds of the x86_64 version and mention it on the "Known Issues" page as well. Done! (And thanks for mentioning that I misplaced the issue under 'macOS' on the Known Issues page -- I always work on this project far too late at night!) For those who have 64-bit Windows 11 with 22H2 update, please download 0.9.28-2 from here: https://tuxpaint.org/download/windows/ -bill! > > Thanks. > > On Tue, 22 Nov 2022 14:13:54 -0800, Bill Kendrick wrote: > >On Sun, Nov 20, 2022 at 08:57:51PM -0800, Bill Kendrick wrote: > >> > >> Three people have reported issues typing some characters (i, j, and s) > >> in Tux Paint's Text tool. One opened, and another commented on, > >> ticket #264 over on our SourceForge project. Another emailed me > >> directly, but didn't provide detail of their system, Tux Paint version, > >> etc. (I asked, but they haven't responded yet.) > > > > > >Shin-ichi of our project was able to reproduce this issue, and > >by rebuilding Tux Paint 0.9.28 seems to have addressed it. > >However, it'd be helpful if people could test this, especially > >if you're observing the issue with the version of 0.9.28 built in June. > > > >EXE installer and ZIP 'portable' versions, each for both 64-bit (x86_64) > >and 32-bit (i686) systems, have been posted to his site: > > > > https://z1.plala.jp/tuxpaint/testing/windows/0.9.28-2/ > > > > > >Below is his most recent post to the 'tuxpaint-users' mailing list: > > > >------------------------------------------------------------------------ > > Hi! > > > > New build on the latest MinGW/MSYS2 environment seems to fix this. > > Please see my post on https://sourceforge.net/p/tuxpaint/bugs/264/ > > > > On Mon, 21 Nov 2022 21:18:05 +0900, Shin-ichi TOYAMA wrote: > > > In addition, the problem does not happen with current git tree. > > > > > > We may be able to find the reason from the difference. > > > > > > On Mon, 21 Nov 2022 21:14:51 +0900, Shin-ichi TOYAMA wrote: > > > > Wow! > > > > > > > > The "s" problem reproduced on my Windows 11 laptop ! > > > > > > > > Considering that I have recently applied the 22H2 update, this > > > > might be the root of the evil. > > > > > > > > If we can ask the first reporter and confirm the correlation between > > > > the symptoms and the application of 22H2, I think we can clearly > > > > isolate the problem. > >------------------------------------------------------------------------ > > > > > >Thanks in advance! > > > >-bill! > > > > > >> > >> Has anyone else out here seen this behavior? I cannot reproduce it > >> under Linux. Pere tried under Windows 10 and cannot, either. > >> The person who commented on the ticket mentioned that it seemed to > >> begin after a Microsoft Update to her Windows 11 laptop. > >> > >> More info, and follow along, here: > >> > >> https://sourceforge.net/p/tuxpaint/bugs/264/ > >> > >> -- > >> -bill! > >> Sent from my computer > > > > > -- > Shin-ichi TOYAMA <dol...@wm...> > > > _______________________________________________ > Tuxpaint-users mailing list > Tux...@li... > https://lists.sourceforge.net/lists/listinfo/tuxpaint-users -- -bill! Sent from my computer |
