Whatsie (whatsie-git 4.16.2.r0.gece2c55-1) not working

I’m suddenly having issues with the whatsie-git WhatsApp client. It will receive (most) new messages but sometimes it’ll not load a new message. It is unable to send new messages - they just hang without sending. When trying to log out of whatsie, that process also hangs. When logging in again, the QR code to link the client doesn’t display (just keeps loading). Linking by mobile phone number does work but then the above-mentioned issues resume. It looks like it might be some kind of connection or API problem. Until a few days ago, whatsie-git worked flawlessly. Any help would be appreciated.

## whatsie-git

Fast Light weight WhatsApp Client based on Qt's WebEngine, With lots of settings and packed goodies

|||
| --- | --- |
|URL|https://github.com/keshavbhatt/whatsie|
|Version|4.16.2.r0.gece2c55-1|
|Licenses|MIT|
|Provides|[whatsie](goto:whatsie)|
|Depends On|[qt5-base](goto:qt5-base) [qt5-declarative](goto:qt5-declarative) [qt5-location](goto:qt5-location) [qt5-webchannel](goto:qt5-webchannel) [qt5-webengine](goto:qt5-webengine)|
|Conflicts With|[whatsie](goto:whatsie)|
|Installed Size|44.99 MiB|
|Packager|Garuda Builder <team@garudalinux.org>|
|Architecture|x86_64|
|Build Date|Friday 25 October 2024 22:40:02 Central European Summer Time|
|Install Date|Wednesday 30 October 2024 09:06:47 Central European Standard Time|
|Install Reason|Explicitly installed|

garuda-inxi:

System:
Kernel: 6.11.5-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=983f8cbe-fd3d-48e2-a068-52fc8d3e1126 rw rootflags=subvol=@
quiet resume=UUID=808f17a0-f0f6-4fec-b509-5d7fc3d2cba3 loglevel=3 splash
ibt=off
Desktop: KDE Plasma v: 6.2.2 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 20NKS0UU2M v: ThinkPad T495
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: 20NKS0UU2M v: SDK0J40697 WIN serial: <filter>
part-nu: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
uuid: 4fd7234c-308f-11b2-a85c-dac9ac5f22ff UEFI: LENOVO v: R12ET64W(1.34 )
date: 02/23/2024
Battery:
ID-1: BAT0 charge: 36.4 Wh (85.0%) condition: 42.8/50.5 Wh (84.9%)
volts: 12.4 min: 11.5 model: SMP 02DL008 type: Li-poly serial: <filter>
status: not charging cycles: 713
CPU:
Info: model: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx socket: FP5
bits: 64 type: MT MCP arch: Zen/Zen+ note: check gen: 1 level: v3
note: check built: 2019 process: GF 12nm family: 0x17 (23)
model-id: 0x18 (24) stepping: 1 microcode: 0x8108109
Topology: cpus: 1x dies: 1 clusters: 1 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB
desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1400 min/max: 1400/2100 boost: enabled
base/boost: 2100/3700 scaling: driver: acpi-cpufreq governor: schedutil
volts: 1.2 V ext-clock: 100 MHz cores: 1: 1400 2: 1400 3: 1400 4: 1400
5: 1400 6: 1400 7: 1400 8: 1400 bogomips: 33535
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Picasso/Raven 2 [Radeon Vega
Series / Radeon Mobile Series] vendor: Lenovo driver: amdgpu v: kernel
arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3
speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1
bus-ID: 06:00.0 chip-ID: 1002:15d8 class-ID: 0300 temp: 53.0 C
Device-2: Bison Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 4-2.1:4 chip-ID: 5986:2130
class-ID: 0e02
Display: unspecified server: X.Org v: 24.1.4 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :1 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: ChiMei InnoLux 0x14d6 built: 2016 res: 1366x768
hz: 60 dpi: 112 gamma: 1.2 size: 309x173mm (12.17x6.81") diag: 354mm (13.9")
ratio: 16:9 modes: max: 1366x768 min: 640x480
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.5-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Vega 8 Graphics
(radeonsi raven LLVM 18.1.8 DRM 3.59 6.11.5-zen1-1-zen)
device-ID: 1002:15d8 memory: 1.95 GiB unified: no
API: Vulkan v: 1.3.295 layers: 3 device: 0 type: integrated-gpu name: AMD
Radeon Vega 8 Graphics (RADV RAVEN) driver: mesa radv v: 24.2.5-arch1.1
device-ID: 1002:15d8 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 18.1.8 256 bits) driver: mesa llvmpipe v: 24.2.5-arch1.1 (LLVM
18.1.8) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP
Audio vendor: Lenovo driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 06:00.1 chip-ID: 1002:15de class-ID: 0403
Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor
vendor: Lenovo driver: snd_pci_acp3x v: kernel alternate: snd_rn_pci_acp3x,
snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps,
snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
snd_sof_amd_acp63 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 06:00.5
chip-ID: 1022:15e2 class-ID: 0480
Device-3: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
vendor: Lenovo driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 16 bus-ID: 06:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.11.5-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.6 status: n/a (root, process) 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 Wi-Fi 5 Wireless-AC 9x6x [Thunder Peak] driver: iwlwifi
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 01:00.0
chip-ID: 8086:2526 class-ID: 0280
IF: wlp1s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: 3400 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0f0 state: down mac: <filter>
Device-3: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: 2000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp4s0 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel Wireless-AC 9260 Bluetooth Adapter driver: btusb v: 0.8
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 4-1:2
chip-ID: 8087:0025 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
Local Storage: total: 238.47 GiB used: 58.61 GiB (24.6%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKKF256G8L
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: L15P temp: 40.9 C scheme: GPT
SMART: yes health: PASSED on: 306d 13h cycles: 2,195
read-units: 101,667,745 [52.0 TB] written-units: 46,626,657 [23.8 TB]
Partition:
ID-1: / raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
used: 57.43 GiB (25.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 17.2 MiB (5.8%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
maj-min: 259:1
ID-3: /home raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
used: 57.43 GiB (25.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-4: /var/log raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
used: 57.43 GiB (25.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-5: /var/tmp raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
used: 57.43 GiB (25.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 5.67 GiB used: 5.56 GiB (98.2%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8
dev: /dev/zram0
ID-2: swap-2 type: partition size: 8.8 GiB used: 1.16 GiB (13.2%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 53.0 C mobo: N/A gpu: amdgpu temp: 53.0 C
Fan Speeds (rpm): fan-1: 3200 fan-2: 3200
Info:
Memory: total: 6 GiB available: 5.67 GiB used: 4.14 GiB (73.0%)
Processes: 339 Power: uptime: 20h 46m states: freeze,mem,disk
suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 2.24 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1582 libs: 480 tools: octopi,paru Compilers:
clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi (sudo) default: Bash v: 5.2.37
running-in: konsole inxi: 3.3.36
Garuda (2.6.26-1):
System install date:     2024-09-28
Last full system update: 2024-10-31 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

It is important to notice that despite it being a Whatsapp client, it is an unofficial whatsapp client.
The best place to lodge an issue would be at

To do:

  1. You could try the Flatpak version (if it fails)
  2. Try other clients such as (zapzap) that is working for me.

See how the devs from the whatsie,will respond to your error.

If any one else knows how to help you, hope they will.

4 Likes

Thanks for the ZapZap tip, that app indeed works flawlessly. It’ll work just fine for me until WhatSie gets fixed. The only thing I don’t like about it is that its icon doesn’t adhere to the neon theme… But there must be a way to “fix” that, right? Down another rabbit hole I go! :smiley:

It’s funny, when a WhatsApp wrapper app stops working for me I move to another one. There were 3 on Flathub but one has been removed in recent months. When the next one breaks I move to another. Sometimes two didn’t work for me. Usually one does though.

1 Like

Yes i been having similar problems as you, and now use Atlas, already for some time, and found it to be more reliable, and best of all the dictionary works.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.