borgbase/vorta

New Issue

Closed this issue · 6 comments

Unbehandelter Fehler, bitte melde dies mit diesem Text auf
https://github.com/borgbase/vorta/issues/new
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/vorta/application.py", line 185, in set_borg_details_result
self.scheduler.reload_all_timers() # Start timer after Borg version is set.
File "/usr/lib/python3/dist-packages/vorta/scheduler.py", line 121, in reload_all_timers
self.set_timer_for_profile(profile.id)
File "/usr/lib/python3/dist-packages/vorta/scheduler.py", line 111, in set_timer_for_profile
timer.setInterval(int(timer_ms))
OverflowError: argument 1 overflowed: value must be in the range -2147483648 to 2147483647

Vorta Version 0.8.3
Ubuntu 22.04.5 LTS
64-bit
GNOME Version 42.9

@un5887
It seems the interval value you set exceeds the limit for QTimer.setInterval(), which expects a 32-bit signed integer. This likely caused an overflow.

Could you give us more info on how you encountered this issue and what could be done to reproduce this? Also give a meaningful issue title.

m3nu commented

I believe this is already fixed. The user is on a very old version. Due to limited resources, we can only address bugs in the current master branch of the app or last released version.

Thanks for your quick help!

I installed vorta via terminal (sudo apt update, sudo apt upgrade, then sudo apt install vorta), so I guess I got the default version for my system.

After installation, I set up two profiles to save to OneDrive. One day later, I set up a third profile for backup on external HDD and since then this error comes up at every reboot. I'll change the interval from 4 weeks to 2 weeks to see if it solves the probelm.

Looks like changing the backup interval from 4 to 2 weeks solved the problem. No crashes or freezes since yesterday.
There are better ways to tell the user that backups should be made more often;)

Glad to hear that!
The error does seem to be resolved in the latest version of Vorta.

if timer_ms < 2**31 - 1:
logger.debug('Scheduling next run for %s', next_time)

I'm closing this as this issue seems to be resolved.