Mullvad VPN version 2023.4 will not run under MX Linux 19.4

[bwhawk]

I used MXPI to upgrade Mullvad VPN from 2023.3 to the latest version (2023.4). It installed without errors, but mullvad-daemon won't run. The error is:

mullvad-daemon: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by mullvad-daemon)

The latest version of GLIBC I could find in the repos is 2.28. I don't know if 2.29 will run under 19.4. If so, could it be added to the Test repo? Or if not, would it be possible to modify the Mullvad installation script to stop at version 2023.3?

Code: Select all

System:    Kernel: 5.10.0-15mx-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-15mx-amd64 root=UUID=<filter> ro quiet 
           splash 
           Desktop: KDE Plasma 5.14.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-19.4_KDE_x64 patito feo August 16  2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ZOTAC model: ZBOX-CI622/CI642/CI662NANO v: XX serial: <filter> UEFI: American Megatrends 
           v: B418P104 date: 03/03/2020 
CPU:       Info: Quad Core model: Intel Core i5-10210U bits: 64 type: MT MCP arch: Kaby Lake note: check family: 6 
           model-id: 8E (142) stepping: C (12) microcode: F4 cache: L2: 6 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 33599 
           Speed: 700 MHz min/max: 400/4200 MHz Core speeds (MHz): 1: 700 2: 700 3: 700 4: 700 5: 700 6: 700 7: 700 8: 700 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds mitigation: TSX disabled 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: ZOTAC driver: i915 v: kernel bus-ID: 00:02.0 
           chip-ID: 8086:9b41 class-ID: 0300 
           Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: loaded: modesetting unloaded: fbdev,vesa 
           display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.0x22.5") s-diag: 1165mm (45.9") 
           Monitor-1: DP-1 res: 3840x2160 dpi: 157 size: 621x341mm (24.4x13.4") diag: 708mm (27.9") 
           OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel Comet Lake PCH-LP cAVS vendor: ZOTAC driver: snd_hda_intel v: kernel alternate: snd_sof_pci 
           bus-ID: 00:1f.3 chip-ID: 8086:02c8 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-15mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 12.2 running: yes 
Network:   Device-1: Intel Comet Lake PCH-LP CNVi WiFi driver: iwlwifi v: kernel modules: wl port: 5000 bus-ID: 00:14.3 
           chip-ID: 8086:02f0 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel port: 4000 bus-ID: 01:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel port: 3000 bus-ID: 02:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth1 state: down mac: <filter> 
           IF-ID-1: wg-mullvad state: unknown speed: N/A duplex: N/A mac: N/A 
Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-10:6 chip-ID: 8087:0aaa class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: N/A rfk-block: hardware: no software: no 
           address: <filter> 
           Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: slave accept 
Drives:    Local Storage: total: 1.82 TiB used: 828.66 GiB (44.5%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 2TB size: 1.82 TiB block-size: physical: 512 B 
           logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 4B6Q scheme: GPT 
Partition: ID-1: / raw-size: 20 GiB size: 19.58 GiB (97.90%) used: 15.69 GiB (80.1%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 
           ID-2: /boot/efi raw-size: 100 MiB size: 98.4 MiB (98.45%) used: 258 KiB (0.3%) fs: vfat dev: /dev/sda1 maj-min: 8:1 
           ID-3: /home raw-size: 40 GiB size: 39.2 GiB (98.00%) used: 14.52 GiB (37.0%) fs: ext4 dev: /dev/sda3 maj-min: 8:3 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda6 maj-min: 8:6 
Sensors:   System Temperatures: cpu: 42.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: 2684 note: see --pkg apt: 2673 lib: 1481 flatpak: 11 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/megasync.list 
           1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_10.0/ ./
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ buster main non-free
           2: deb http://la.mxrepo.com/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/spotify.list 
           Active apt repos in: /etc/apt/sources.list.d/sublime-text.list 
           1: deb https://download.sublimetext.com/ apt/stable/
           Active apt repos in: /etc/apt/sources.list.d/teams.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb [arch=amd64] http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 293 Uptime: 3m wakeups: 1 Memory: 31.14 GiB used: 2.87 GiB (9.2%) Init: SysVinit v: 2.93 runlevel: 5 
           default: 5 tool: systemctl Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in default: Bash v: 5.0.3 
           running-in: quick-system-in inxi: 3.3.06 

[fehlix]

I used MXPI to upgrade Mullvad VPN from 2023.3 to the latest version (2023.4). It installed without errors, but mullvad-daemon won't run. The error is:

mullvad-daemon: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by mullvad-daemon)

The latest version of GLIBC I could find in the repos is 2.28. I don't know if 2.29 will run under 19.4. If so, could it be added to the Test repo? Or if not, would it be possible to modify the Mullvad installation script to stop at version 2023.3?

Yes.
Would you try this:
Make sure you have current/latest version of mx-packainstaller and mx-packainstaller-pkglist installed.
Open terminal as normal user and run:

Code: Select all

sudo sed -i 's/*_amd64/*2023.3_amd64/' /usr/share/mx-packageinstaller-pkglist/mullvadvpn.pm

Open MX Package Installer "MXPI" and within Populare Apps,
perhabs re-install MullVad VPN ( or de-install and install fresh)

Please let us know if that works.
Thanks
+++EDIT+++
Opps adjusted "sed -i" for inreplace change

[bwhawk]

I was about to post that it didn't work, and that I couldn't see how it would work since sed wasn't changing the file. But you edited your post first! And it works! Version 2023.3 was downloaded and installed over the non-functioning 2023.4.

Thank you, fehlix!

[CharlesV]

I was about to post that it didn't work, and that I couldn't see how it would work since sed wasn't changing the file. But you edited your post first! And it works! Version 2023.3 was downloaded and installed over the non-functioning 2023.4.

Thank you, fehlix!

@bwhawk So your now running on 2023.4 ? (or it reverted back to 2023.3)

[fehlix]

I was about to post that it didn't work, and that I couldn't see how it would work since sed wasn't changing the file. But you edited your post first! And it works! Version 2023.3 was downloaded and installed over the non-functioning 2023.4.

Thank you, fehlix!

Thanks, we will prepare an adjustement for MX Package Installer on mx19.4... asap.

[bwhawk]

@bwhawk So your now running on 2023.4 ? (or it reverted back to 2023.3)

It reverted to 2023.3. I don't think 2023.4 will work unless GLIBC 2.29 can be ported to 19.4. Or if there's some way to trick the mullvad app into thinking that GLIB 2.28 is equivalent to 2.29.

[CharlesV]

@bwhawk So your now running on 2023.4 ? (or it reverted back to 2023.3)

It reverted to 2023.3. I don't think 2023.4 will work unless GLIBC 2.29 can be ported to 19.4. Or if there's some way to trick the mullvad app into thinking that GLIB 2.28 is equivalent to 2.29.

K.. thats what I thought but wanted to clarify. Thank you.