From 5e67fd457379d645a3d5b42acf1eb2a1f3d0acc2 Mon Sep 17 00:00:00 2001 From: Ell Bradshaw Date: Wed, 17 Dec 2025 00:37:57 -0800 Subject: [PATCH] Remove wrapper lambda from this connection signal I think this was causing weird lifetime issues, where the lambda wasn't getting deleted so it caused this signal to still exist after the page was deleted --- src/vorta/views/schedule_page.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/vorta/views/schedule_page.py b/src/vorta/views/schedule_page.py index d020a012d..0a1c4ad07 100644 --- a/src/vorta/views/schedule_page.py +++ b/src/vorta/views/schedule_page.py @@ -61,7 +61,7 @@ def __init__(self, parent=None): lambda new_val, attr='compaction_weeks': self.save_profile_attr(attr, new_val) ) - self.app.scheduler.schedule_changed.connect(lambda pid: self.draw_next_scheduled_backup()) + self.app.scheduler.schedule_changed.connect(self.draw_next_scheduled_backup) self.populate_from_profile() # Listen for events @@ -110,7 +110,7 @@ def populate_from_profile(self): self.draw_next_scheduled_backup() - def draw_next_scheduled_backup(self): + def draw_next_scheduled_backup(self, pid=None): status = self.app.scheduler.next_job_for_profile(self.profile().id) if status.type in ( ScheduleStatusType.SCHEDULED,