search

Qubes-Community / Contents

Community documentation, code, links to third-party resources, ... See the issues and pull requests for pending content. Contributions are welcome !
258 stars 98 forks source link

qubes-vpn-handler.sh not working on fedora-36 TemplateVM #211

Closed 5wnUinZa5VUp closed 2 years ago

5wnUinZa5VUp commented 2 years ago

The scripts package works well on previous fedora TemplateVM, but when fedora-36 based, it fails. After a little debugging, i found this error message within openvpn logs: [....] 2022-09-18 07:21:10 us=929515 net_addr_v4_add: 10.39.2.20/24 dev tun0 2022-09-18 07:21:10 us=929995 sitnl_send: checking for received messages 2022-09-18 07:21:10 us=930004 sitnl_send: rtnl: received 36 bytes 2022-09-18 07:21:10 us=930020 qubes-vpn-handler.sh up tun0 1500 1587 10.39.2.20 255.255.255.0 init Failed to execute child process “dbus-launch” (No such file or directory) 2022-09-18 07:21:11 us=13836 WARNING: Failed running command (--up/--down): external program exited with error status: 1 2022-09-18 07:21:11 us=13858 Exiting due to fatal error Failed to execute child process “dbus-launch” (No such file or directory)

The qubes-vpn-handler.sh is crashing the openvpn setup. When not called (commented within openvpn.conf file), it works perfectly.

ghost commented 2 years ago

Hi, Which f36 template do you use ? dbus-launch is provided by the dbus-x11 package but from your error msg it looks like it's missing (or can't be found) ; could you check that this package is installed in your template ? I don't have a default f36 to try myself - FWIW I have it installed on my custom "full" fedora template, but not in my "minimal" template.

5wnUinZa5VUp commented 2 years ago

oh stupid me. Indeed, you are absolutely right. Sorry for this issue and thank you for your answer :)

ghost commented 2 years ago

no problem, glad I could help !