Issues updating the mullvad-vpn package with the mx-packageinstaller

[aspacegamer]

This is an issue that i have seen cropping on every time now i update mullvad-vpn for some reasons updating breaks the application completly i always have to completly uninstall and then reinstall it starting from a clean slate otherwise it won't be able to log back into my mullvad account and even if you log out of your account before and then try to log back in it will just stay at logging in for minutes without anything happening easiest fix i found is to completly uninstall the package and then reinstall it instead of updating still this behaviour is extremly weird and i wonder if others experience the same.

[fehlix]

Maybe post QSI, so we know what you are running. Also, IIRC, the "update" function never worked,
b/c of their special settings. "Upgrade"ing to a newer version should only be performed with
re-installation from MXPI-> Populare Apps->Network .>MullvadVPN.

[Mauser]

I use Mullvad and have learned how to update it since Mullvad is done completely differently in MX Linux than any other package. When Mullvad tells you there is an update you go to the MX Package Installer and go look under Popular Applications then Network. Reinstall Mullvad and then reboot your computer. Doing it any other way will cause problems.

[aspacegamer]

Code: Select all

System:
  Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: persist_all
    lang=de_AT quiet splasht nosplash
  Desktop: KDE Plasma v: 5.27.5 info: kdocker wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.2_KDE_x64
    Libretto July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: Dell product: Latitude E7470 v: N/A serial: <superuser required> Chassis:
    type: 9 serial: <superuser required>
  Mobo: Dell model: 0T6HHJ v: A00 serial: <superuser required> UEFI-[Legacy]: Dell v: 1.36.3
    date: 09/18/2022
Battery:
  ID-1: BAT0 charge: 44.5 Wh (100.0%) condition: 44.5/55.0 Wh (80.9%) volts: 8.3 min: 7.6
    model: SMP DELL MC34Y51 type: Li-poly serial: <filter> status: full
CPU:
  Info: model: Intel Core i7-6600U bits: 64 type: MT MCP arch: Skylake gen: core 6 level: v3
    note: check built: 2015 process: Intel 14nm family: 6 model-id: 0x4E (78) stepping: 3
    microcode: 0xF0
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 1200 min/max: 400/3400 scaling: driver: intel_pstate governor: powersave
    cores: 1: 1200 2: 1200 3: 1200 4: 1200 bogomips: 22399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Dell Latitude E7470 driver: i915 v: kernel
    arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:1916 class-ID: 0300
  Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-2:2
    chip-ID: 0bda:57c3 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: BOE Display 0x0653 built: 2015 res: 1920x1080 hz: 60 dpi: 158
    gamma: 1.2 size: 309x173mm (12.17x6.81") diag: 354mm (13.9") ratio: 16:9 modes: 1920x1080
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel HD Graphics 520 (SKL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell Latitude E7470 driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_skl bus-ID: 00:1f.3 chip-ID: 8086:9d70
    class-ID: 0403
  API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-LM vendor: Dell Latitude E7470 driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:156f class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:24f3 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  IF-ID-1: br-4c0dc9d500ae state: down mac: <filter>
  IF-ID-2: br-dad4ecd66ca9 state: down mac: <filter>
  IF-ID-3: docker0 state: down mac: <filter>
  IF-ID-4: wwan0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-8:5
    chip-ID: 8087:0a2b class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 5 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: peripheral accept
Drives:
  Local Storage: total: 1.14 TiB used: 542.23 GiB (46.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Intel model: SSDSCKKF256H6 SATA 256GB size: 238.47 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: D16N
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Extreme 55AE size: 931.48 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 3001 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 10 GiB used: 1.33 GiB (13.3%) priority: -2
    file: /live/boot-dev/swap-file
Sensors:
  System Temperatures: cpu: 60.0 C pch: 46.5 C mobo: 40.0 C
  Fan Speeds (RPM): cpu: 0
Repos:
  Packages: 2919 pm: dpkg pkgs: 2859 libs: 1379 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 60
  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 bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/docker.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/debian bookworm stable
  Active apt repos in: /etc/apt/sources.list.d/microsoft-prod.list
    1: deb [arch=amd64,arm64,armhf signed-by=/usr/share/keyrings/microsoft-prod.gpg] https://packages.microsoft.com/debian/12/prod bookworm main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://mxrepo.com/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/spotify.list
    1: deb http://repository.spotify.com stable non-free
  No active apt repos in: /etc/apt/sources.list.d/steam-beta.list
  Active apt repos in: /etc/apt/sources.list.d/steam-stable.list
    1: deb [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
    2: deb-src [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
  Active apt repos in: /etc/apt/sources.list.d/vscode.list
    1: deb [arch=amd64,arm64,armhf signed-by=/etc/apt/keyrings/packages.microsoft.gpg] https://packages.microsoft.com/repos/code stable main
Info:
  Processes: 301 Uptime: 4h 44m wakeups: 6 Memory: 7.44 GiB used: 5.19 GiB (69.8%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

[aspacegamer]

I use Mullvad and have learned how to update it since Mullvad is done completely differently in MX Linux than any other package. When Mullvad tells you there is an update you go to the MX Package Installer and go look under Popular Applications then Network. Reinstall Mullvad and then reboot your computer. Doing it any other way will cause problems.

That does sound a lot like the issues i was facing trough in my case my workaround was to completly uninstall and then reinstall is it possible that the service doesn't get stopped correctly during update and it runs the outdated daemon?

[Mauser]

I use Mullvad and have learned how to update it since Mullvad is done completely differently in MX Linux than any other package. When Mullvad tells you there is an update you go to the MX Package Installer and go look under Popular Applications then Network. Reinstall Mullvad and then reboot your computer. Doing it any other way will cause problems.

That does sound a lot like the issues i was facing trough in my case my workaround was to completly uninstall and then reinstall is it possible that the service doesn't get stopped correctly during update and it runs the outdated daemon?

I know something goes amiss if you just reinstall it without rebooting. Rebooting fixes it.

[indielinuxpower]

...Also, IIRC, the "update" function never worked,
b/c of their special settings. "Upgrade"ing to a newer version should only be performed with
re-installation from MXPI-> Populare Apps->Network .>MullvadVPN.

Mullvad now has a repository for Debian (and other Linux distros). Could that be integrated into MXPI so there would be no need press the reinstall button in MXPI to upgrade Mullvad? https://mullvad.net/en/blog/introducing ... and-fedora

[fehlix]

...Also, IIRC, the "update" function never worked,
b/c of their special settings. "Upgrade"ing to a newer version should only be performed with
re-installation from MXPI-> Populare Apps->Network .>MullvadVPN.

Mullvad now has a repository for Debian (and other Linux distros). Could that be integrated into MXPI so there would be no need press the reinstall button in MXPI to upgrade Mullvad? https://mullvad.net/en/blog/introducing ... and-fedora

Maybe they added similar adjustments which are done within MXPI to make it work
when booted with SysVinit also.
Perhaps try your suggestions, and report whether it works.
In case you got something similar like this famous show-stopper:
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
you are encouraged to contact Mullvad support to suggest to apply patches
similar as made to their deb-package installer within MXPI "MX Package Installer".
Until they fix their package and as long as MX also supports SysVinit,
I'm affraid reinstalll-through MXPI would be needed.
But if you always boot with systemd, you can follow their installation instructions
and keep mullvad-repo enabled.