Visual glitch on update #73

Closed
opened 2026-08-02 14:44:42 +00:00 by NooneAtAll3 · 2 comments
NooneAtAll3 commented 2026-08-02 14:44:42 +00:00 (Migrated from codeberg.org)

I apologize that I can't show a picture of it, as I've already closed the updater

After progress bar finishes and program starts displaying "Start Update" button, it actually displays 1.5 buttons. Half of a button below the real one. Same text on both. Bottom half-button is drawn on top of "Schedule a task for automatic update..." text below

My guess is that it first draws the button below displayed text about downloading an update, then removes the text and redraws the button in new location...

I apologize that I can't show a picture of it, as I've already closed the updater After progress bar finishes and program starts displaying "Start Update" button, it actually displays 1.5 buttons. Half of a button below the real one. Same text on both. Bottom half-button is drawn on top of "Schedule a task for automatic update..." text below My guess is that it first draws the button below displayed text about downloading an update, then removes the text and redraws the button in new location...
ltguillaume commented 2026-08-02 15:47:50 +00:00 (Migrated from codeberg.org)

double-update-button

Yeah, I'm aware of this issue. I can sometimes reproduce it, it's not so easy to test. I was afraid it's just some race condition that isn't in my script, but in the AutoHotkey code, but because of your guess I tried something else (just switching the move task set text and the add button operation) and I have failed to reproduce it since.

The change is implemented in 1.18.2.

Could you please test this version (quite a few of times, ideally) to see if it fixes the issue?

  1. To test, you'll need to download and install a previous version from here: x64 version (default) or arm64 version
  2. Then, just run the updater
  3. See if the button is duplicated and close it without clicking the update button
  4. Then run it again (like 20 times)
    Hold off on starting LibreWolf until you actually updated again.
![double-update-button](/attachments/bd114cda-eaaf-48ff-9df5-d241111f15f0) Yeah, I'm aware of this issue. I can _sometimes_ reproduce it, it's not so easy to test. I was afraid it's just some race condition that isn't in my script, but in the AutoHotkey code, but because of your guess I tried something else (just switching the move task set text and the add button operation) and I have failed to reproduce it since. The change is implemented in [1.18.2](https://codeberg.org/librewolf/winupdater/releases/tag/1.18.2). Could you please test this version (quite a few of times, ideally) to see if it fixes the issue? 1. To test, you'll need to download and install a previous version from here: [x64 version (default)](https://dl.librewolf.net/librewolf/153.0-3/librewolf-153.0-3-windows-x86_64-setup.exe) or [arm64 version](https://dl.librewolf.net/librewolf/153.0-3/librewolf-153.0-3-windows-arm64-setup.exe) 2. Then, just run the updater 3. See if the button is duplicated and close it without clicking the update button 4. Then run it again (like 20 times) **Hold off on starting LibreWolf until you _actually_ updated again.**
ltguillaume commented 2026-08-03 17:03:20 +00:00 (Migrated from codeberg.org)

Yeah, this is fixed now. Thanks for reporting!

Yeah, this is fixed now. Thanks for reporting!
Sign in to join this conversation.
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
librewolf/winupdater#73
No description provided.