mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-10-01 01:25:40 -04:00
Eetend VPN troubleshooting by notify-send case
There are guides and scripts on internet that are helping to configure and run VPN service on QubesOS This record provides explanation how to identify and what to do to fix possible issues with notify-send that being used by this guides.
This commit is contained in:
parent
6fae0a1adb
commit
c5314bed7f
@ -31,3 +31,20 @@ After suspend/resume, OpenVPN may not automatically reconnect. In order to get i
|
||||
After setting up OpenVPN and restarting the VM, you may be repeatedly getting the popup "Ready to start link", but the VPN isn't connected.
|
||||
|
||||
To figure out the root of the problem, check the VPN logs in `/var/logs/syslog`. The log may reveal issues like missing OpenVPN libraries, which you can then install.
|
||||
|
||||
## `notify-send` induced failure
|
||||
[Some VPN guides](https://github.com/Qubes-Community/Contents/blob/master/docs/configuration/vpn.md) use complex scripts that by themselves include call of `notify-send`, yet some images may not contain this tool or may not have it working properly.
|
||||
For instance calling `notify-send` on `fedora-36` template VM gives:
|
||||
```
|
||||
Failed to execute child process “dbus-launch” (No such file or directory)
|
||||
```
|
||||
|
||||
To check this tool is working properly run:
|
||||
```bash
|
||||
sudo notify-send "$(hostname): Test notify-send OK" --icon=network-idle
|
||||
```
|
||||
You should see `info` message appear on the top of your scree.
|
||||
If that is the case then, `notify-send` is not the issue.
|
||||
If it is not, and you have an error of some sort you can:
|
||||
1. Remove all calls of `notify-send` from scripts you are using to start VPN
|
||||
2. Use other template VM that have `notify-send` working or find proper guide and make your current template VM run `notify-send` work properly.
|
||||
|
Loading…
Reference in New Issue
Block a user