[GH-ISSUE #20] 🐞 Bug: After updating Pegaprox, it keeps showing a popup saying the update I just installed is available again #13

Closed
opened 2026-03-02 15:47:12 +03:00 by kerem · 2 comments
Owner

Originally created by @PhiGi87 on GitHub (Jan 29, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/20

Hello again :-)

after I updated Pegaprox to the latest version, I repeatedly get a popup stating that the newly installed update is available. It looks like Pegaprox does not detect that the update was already applied.

The updater in the UI also seems to not recognize the installed version and continues to offer the same update: https://streamable.com/ewwmkz

regards,
Phil

Originally created by @PhiGi87 on GitHub (Jan 29, 2026). Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/20 Hello again :-) after I updated Pegaprox to the latest version, I repeatedly get a popup stating that the newly installed update is available. It looks like Pegaprox does not detect that the update was already applied. The updater in the UI also seems to not recognize the installed version and continues to offer the same update: [https://streamable.com/ewwmkz](https://streamable.com/ewwmkz) regards, Phil
kerem 2026-03-02 15:47:12 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@mkellermann97 commented on GitHub (Jan 29, 2026):

Hi @PhiGi87 ,

thank you for the bug reports!
I looked into it the PegaProx Service user itself can't execute as it seems "systemctl restart pegaprox"
Please run this in your VM and 90% of the bugs will disappear. (The frontend got updated but not the backend. Thats why this strange behavior occurs.)

We will bring today also a fix for it out.
Regards,
Marcus

<!-- gh-comment-id:3816179730 --> @mkellermann97 commented on GitHub (Jan 29, 2026): Hi @PhiGi87 , thank you for the bug reports! I looked into it the PegaProx Service user itself can't execute as it seems "systemctl restart pegaprox" Please run this in your VM and 90% of the bugs will disappear. (The frontend got updated but not the backend. Thats why this strange behavior occurs.) We will bring today also a fix for it out. Regards, Marcus
Author
Owner

@PhiGi87 commented on GitHub (Jan 29, 2026):

Fixed ;-) Thanks

<!-- gh-comment-id:3816338597 --> @PhiGi87 commented on GitHub (Jan 29, 2026): Fixed ;-) Thanks
Sign in to join this conversation.
No milestone
No project
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
starred/project-pegaprox-PegaProx#13
No description provided.