vorta
vorta copied to clipboard
Warnings when running Vorta
Description
2024-03-29 14:00:57,116 - vorta.scheduler - WARNING - Failed to connect to DBUS interface to detect sleep/resume events
Each time I run Vorta on my POP_OS laptop I receive the above warning. When I run it on my POP_OS I do not receive the warning. Ostensibly, both machines run the same. This started occurring in December 2023. Otherwise the backup appears to be functioning properly.
Reproduction
- [X] I tried to reproduce the issue.
- [ ] I was able to reproduce the issue.
OS
POP_OS
Version of Vorta
0.9.1
What did you install Vorta with?
Flatpak
Version of Borg
1.2.4
Logs
/home/herb/.var/app/com.borgbase.Vorta/.local/state/Vorta/log/vorta.log
I think the problem lies in that you are using the Flatpak version of Vorta. Flatpak apps are usually unable to connect with the system as well because of sandboxing. I'd suggest you download Vorta from pip or apt.
Alternatively, you can try disabling sandboxing in flatpaks. But this will take more efforts. https://www.reddit.com/r/flatpak/comments/thu9g8/what_does_sandboxing_in_flatpak_even_mean/
Sam,
Thanks for the advice. I will see what happens with the apt option.
Herb
On Wed, Apr 3, 2024 at 12:49 PM Sam @.***> wrote:
I think the problem lies in that you are using the Flatpak version of Vorta. Flatpak apps are usually unable to connect with the system as well because of sandboxing. I'd suggest you download Vorta from pip or apt.
Alternatively, you can try disabling sandboxing in flatpaks. But this will take more efforts. https://www.reddit.com/r/flatpak/comments/thu9g8/what_does_sandboxing_in_flatpak_even_mean/
— Reply to this email directly, view it on GitHub https://github.com/borgbase/vorta/issues/1978#issuecomment-2035450165, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHPO4K5ZX3QNO4HYIKM6GTLY3RMN7AVCNFSM6AAAAABFQXRYTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVGQ2TAMJWGU . You are receiving this because you authored the thread.Message ID: @.***>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue was closed because it has been stalled for 7 days with no activity.