Arch Linux User Repository

Please note the following requirements for AWS VPN Client:

• If you depend on DNS servers from VPN you need to have a running systemd-resolved.service. Please ensure it does not conflict with any other DNS resolver service or configuration you may use. sudo systemctl --now enable systemd-resolved.service

• You have to enable and start the awsvpnclient.service after installation: sudo systemctl --now enable awsvpnclient

For troubelshooting its worth checking first the logs:

/home/$USER/.config/AWSVPNClient/
/var/log/aws-vpn-client/$USER/

See also the official docs: https://docs.aws.amazon.com/vpn/latest/clientvpn-user/client-vpn-connect-linux.html

If you face any other problem please check the troubleshooting guide (DNS issues): https://docs.aws.amazon.com/vpn/latest/clientvpn-user/linux-troubleshooting.html#aws-provided-client

Hello @project0,

Thanks for maintaining this unstable package for us!

I've experimented upgrading to 1.0.3 with the following change on the PKGBUILD

-pkgver=1.0.2
+pkgver=1.0.3
 pkgrel=1
 pkgdesc="AWS VPN Client"
 arch=('x86_64')
@@ -11,7 +11,7 @@ source=(
   'awsvpnclient.desktop.patch'
 )
 sha512sums=(
-  '4d0dd6a83400d25245f07a31a76f11217738452a413c45fb36898b8de7284a8940bfbaec1bb918b767f74a1f30e3cdaec37befe0a6608b2b848936e35cd4642e'
+  'f9ba448324f04134b36259c0c0dc982d79e8d396bc673d663f8c724648d15b2f22f5ec9c2d45f64a5cb4e4f22de6e5a1683d3aab9253998741a9380c9c000d27'

At first running the VPN client GTK I had the following crash:

$ /opt/awsvpnclient/AWS\ VPN\ Client

(AWS VPN Client:649930): dbind-WARNING **: 16:06:44.115: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-obhGyQF0T5: No such file or directory

(AWS VPN Client:649930): Gtk-WARNING **: 16:06:44.180: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../gtk/gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Adwaita/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Bail out! Gtk:ERROR:../gtk/gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Adwaita/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
[1]    649930 IOT instruction (core dumped)  /opt/awsvpnclient/AWS\ VPN\ Client

With the following command it seems to fixed it:

pacman -S shared-mime-info

I reverted the package to 1.0.2, i was hoping the next update will work again but 2.0.0 is broken as well.

Looks like I need 2.0.0 to connect with my organisation, and that version also crashes with a segfault :/

@spurgelaurels check out these instructions to get your own 1.0.2-1:

$ git clone https://aur.archlinux.org/awsvpnclient.git
$ cd awsvpnclient
$ git checkout f8455bf
$ makepkg
$ sudo pacman -U ./awsvpnclient-1.0.2-1-x86_64.pkg.tar.zst

^^^ this works perfectly for me

then apply metrics sqlite db fix with chmod-ing awsvpnclientmetrics.db to 000.

$ chmod 000 ~/.config/AWSVPNClient/awsvpnclientmetrics.db

Same segfault on my end. Was going to downgrade, but noticed that the previous version points to a non-versioned .deb file, which tells me that this issue is upstream from AWS.

Wondering if anyone has a previous version .deb that can help downgrade this package to 1.0.2?

Reverting to 1.0.2 works like a charm <3 thanks @K5HV

@aemonge: Yes I do. Version 1.0.3-1 doesn't work on my side either, I'm still on 1.0.2-1. Problem with awsvpnclientmetrics.db (when on 1.0.2-1) can be solved using the damentz method.

As of the current date, the problem is not with the aforementioned awsvpnclientmetrics.db but with /opt/awsvpnclient/SQLite.Interop.dll itself.

/opt/awsvpnclient/AWS VPN Client crashes even before trying to open openDatabase (zFilename=0x7fff58218650 "~/.config/AWSVPNClient/awsvpnclientmetrics.db" in the following position:

/*
** Initialize the memory allocation subsystem.
*/
int sqlite3MallocInit(void){
  int rc;
  if( sqlite3GlobalConfig.m.xMalloc==0 ){
    sqlite3MemSetDefault();
  }
  ...
  rc = sqlite3GlobalConfig.m.xInit(sqlite3GlobalConfig.m.pAppData); // <---- segfault

at https://github.com/sqlite/sqlite/blob/master/src/malloc.c#L170.

Why? Because sqlite3GlobalConfig.m == NULL.

But how sqlite3GlobalConfig.m can be equal to NULL? if it is initialized by the sqlite3MemSetDefault call right before it.

The answer is a wrong build: there is an instance of SQLite in the /opt/awsvpnclient/SQLite.Interop.dll AND also in the dynamically loaded /usr/lib/libsqlite3.so.

So that there are exists multiple instances of the global variables like sqlite3Config and functions. At some point of the callstack the execution of SQLite.Interop.dll dynamically resolves a function in libsqlite3.so and jumps in. But they observe different instances of the same global variables. So segfaults after writing to another .m.

#0  sqlite3MemSetDefault () at ../core/sqlite3-see.c:24401
#1  0x00007fff562f60d5 in sqlite3MallocInit () at ../core/sqlite3-see.c:28040
#2  0x00007fff563bd682 in sqlite3_initialize () at ../core/sqlite3-see.c:165762
#3  0x00007fff563c1ca9 in openDatabase ...

$ vmmap 0x00007fff562f60d5
Start              End                Perm  Name
0x00007fff562e2000 0x00007fff56470000 r-xp  /opt/awsvpnclient/SQLite.Interop.dll

// but the call to the sqlite3_config resolves to

0x00007ffff1723440 in sqlite3_config () from /usr/lib/libsqlite3.so.0
gdb-peda$ vmmap 0x00007ffff1723440
Start              End                Perm  Name
0x00007ffff16ac000 0x00007ffff178c000 r-xp  /usr/lib/libsqlite3.so.0.8.6

I don't have ideas yet on how to fix it. Anyway, this looks just wrong.

Hi @damentz, I can't find the awsvpnclientmetrics.db file anywhere to apply your solution.

I've seen so far, Arch Linux is a bit more problematic. I've tried all your comment so far, and I haven't been successful.

@K5HV Are you working with Arch ? If so, can you please let me know how did you manage to run this ?