Indicator stops refreshing and cannot connect after OpenVPN3 session manager restarts
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- linux, python
- Domain
- desktop, networking
Research direction
The traceback points to openvpn3_indicator/application.py, in refresh_sessions, which calls FetchAvailableSessions; start by reading that method and how the session manager proxy is created and used. Reproduce the reported sequence by restarting the net.openvpn.v3.sessions backend while running openvpn3-indicator --debug. Done means the indicator reconnects and can start VPN sessions after the backend restarts, without repeated refresh failures.
Written by the indexing model from the issue text.
Description
Thank you for your work on this project, it mostly works great for me! However, I've had issues with the indicator seemingly not working any more a few times. Restarting the indicator fixes it, but that's annoying.
I tried to track it down, and it seems to be after the OpenVPN3 session manager restarts. I reproduced it as follows:
- I started
openvpn3-indicator --debug - then I killed the
net.openvpn.v3.sessionsbackend - then reactivated it with
openvpn3 sessions-list
afterwards the indicator could not be used any more to start vpn sessions and the following debug messages start appearing:
WARNING:root:Session list refresh failed
DEBUG:root:Schedule
DEBUG:root:Traceback (most recent call last):
File "/usr/bin/openvpn3-indicator/openvpn3_indicator/application.py", line 312, in refresh_sessions
for session in self.session_manager.FetchAvailableSessions():
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/lib/python3/dist-packages/openvpn3/SessionManager.py", line 586, in FetchAvailableSessions
self.__ping()
~~~~~~~~~~~^^
File "/usr/lib/python3/dist-packages/openvpn3/SessionManager.py", line 647, in __ping
raise RuntimeError("Could not establish contact with the Session Manager")
RuntimeError: Could not establish contact with the Session Manager
I only looked at the code a little bit, could it be something like the indicator creating its session-manager D-Bus proxy at startup and continuing to use it after the backend acquires a new D-Bus owner? Maybe it could recreate the proxy and refresh its state when that owner changes?
- Dominant language
- Python
- Stars
- 120
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenVPN/openvpn3-indicator
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
OpenVPN/openvpn3-indicator#44 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
OpenVPN/openvpn3-indicator#39 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
OpenVPN/openvpn3-indicator#5 · 14 comments ·
All issues in OpenVPN/openvpn3-indicator
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 89/100
Maintainers usually reply within 1 day
-
DoRA magnitude vectors are not loaded by Transformers load_adapter / from_pretrained(adapter_dir)Openpost-v1
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
huggingface/peft#4208 · 1 comment ·
Maintainers usually reply within 1 day
-
approved correction metadata
Difficulty 1/5 Under an hour Newbie friendliness 76/100
acl-org/acl-anthology#10996 · 2 comments ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
gke-labs/kube-agents#6620 ·
Maintainers usually reply within 1 day