Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 834824 - net-vpn/networkmanager-openvpn: warns without gtk
Summary: net-vpn/networkmanager-openvpn: warns without gtk
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-09 08:07 UTC by m1027
Modified: 2022-05-14 07:36 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m1027 2022-03-09 08:07:39 UTC
When networkmanager-openvpn is complied with USE="-gtk", then a valid
execution on the console like this

> nmcli connection up CONNECTIONNAME --ask

always issues the following warning:

> nm-WARNING **: Failed to spawn the auth dialogFailed to execute child process “/usr/libexec/nm-openvpn-auth-dialog” (No such file or directory)

The login works, though. It's just the warning that shouldn't be there. So,
this is a minor issue.

Thanks
Comment 1 Matt Turner gentoo-dev 2022-04-08 20:39:40 UTC
Looks like it's referenced in /usr/lib/NetworkManager/VPN/nm-openvpn-service.name

I'm unsure why you specifically called out <= 1.8.16 when there wasn't a newer version in the tree?
Comment 2 m1027 2022-04-10 10:22:05 UTC
(In reply to Matt Turner from comment #1)

Thanks for your reply.

> Looks like it's referenced in
> /usr/lib/NetworkManager/VPN/nm-openvpn-service.name

Looked up that file but don't really understand what to do with it.

> I'm unsure why you specifically called out <= 1.8.16 when there wasn't a
> newer version in the tree?

Right, probably by mistake. I've just edited the subject.

I have this issue with 1.8.16. And I tested it now against 1.8.18 with the same results.

Thanks
Comment 3 m1027 2022-05-14 07:36:21 UTC
The issue disappiered after updating networkmanager to 1.38.0.

As networkmanager 1.38.0 will stabilize soon I permit myself to close this issue.