From c5314bed7f3001996c10458145cc5ba4a0ebaad8 Mon Sep 17 00:00:00 2001 From: zenkuro <42751749+zenkuro@users.noreply.github.com> Date: Thu, 5 Jan 2023 22:57:18 -0500 Subject: [PATCH 1/3] 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. --- user/troubleshooting/vpn-troubleshooting.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/user/troubleshooting/vpn-troubleshooting.md b/user/troubleshooting/vpn-troubleshooting.md index d63bbe0c..d06eb5d1 100644 --- a/user/troubleshooting/vpn-troubleshooting.md +++ b/user/troubleshooting/vpn-troubleshooting.md @@ -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. From a65a507db57fc5166163f05c4f1244edcd5bf3fa Mon Sep 17 00:00:00 2001 From: zenkuro <42751749+zenkuro@users.noreply.github.com> Date: Sat, 7 Jan 2023 02:47:34 -0500 Subject: [PATCH 2/3] Update vpn-troubleshooting.md Fix typo --- user/troubleshooting/vpn-troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/troubleshooting/vpn-troubleshooting.md b/user/troubleshooting/vpn-troubleshooting.md index d06eb5d1..4671066c 100644 --- a/user/troubleshooting/vpn-troubleshooting.md +++ b/user/troubleshooting/vpn-troubleshooting.md @@ -43,7 +43,7 @@ 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. +You should see `info` message appear on the top of your screen. 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 From 55441615bfc082426c4f3b57e45c106afbedbd7e Mon Sep 17 00:00:00 2001 From: unman Date: Fri, 2 May 2025 00:24:26 +0000 Subject: [PATCH 3/3] Fix reference to /var/logs/syslog, and add journalctl. Update link from Qubes-Community to Forum guides. Minor changes. --- user/troubleshooting/vpn-troubleshooting.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/user/troubleshooting/vpn-troubleshooting.md b/user/troubleshooting/vpn-troubleshooting.md index 4671066c..dbf2ccd4 100644 --- a/user/troubleshooting/vpn-troubleshooting.md +++ b/user/troubleshooting/vpn-troubleshooting.md @@ -30,11 +30,11 @@ 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. +To figure out the root of the problem, check the VPN logs in `/var/log/syslog` or use `journalctl`. The logs 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: +[Some VPN guides](https://forum.qubes-os.org/t/configuring-a-proxyvm-vpn-gateway/19061) use complex scripts that include a call to `notify-send`, yet some images may not contain this tool or may not have it working properly. +For instance calling `notify-send` on a `fedora-36` template VM gives: ``` Failed to execute child process “dbus-launch” (No such file or directory) ``` @@ -43,8 +43,8 @@ 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 screen. -If that is the case then, `notify-send` is not the issue. +You should see the `info` message appear on the top of your screen. +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. +1. Remove all calls to `notify-send` from scripts you are using to start VPN +2. Use another template qube that has a working `notify-send` or find proper guide and make your current template run `notify-send` work properly.