keshavbhatt / whatsie

Feature rich WhatsApp Client for Desktop Linux
MIT License
1.98k stars 59 forks source link

Stuck on "Loading your messages" #170

Closed firubat closed 5 months ago

firubat commented 7 months ago

Every once in a while Whatsie gets stuck on the "Loading your messages" screen, after it seemed it has finished loading (showing 100% or full progress bar). Restarting the app doesn't help, I have to unlink and relink (sometimes even that doesn't work on the first go).

I use linux Mint 21.2, whatsie version 4.14.2 as flatpak.

Edit: as I wrote this I realized last time it happened it might have been after installing some flatpak updates, but not exactly sure. I'll try to pay more attention to this.

mbluett88 commented 7 months ago

I am experiencing the exact same situation with Whatsie 4.14.2 flatpak when running on Linux Mint 12.3 with Cinnamon.

I re-installed the app and then re-linked and now it loads up properly.

AndreGorny commented 7 months ago

I'm having the same issue here. I've already removed (--purge) the app, reinstalled and relinked, but still the same problem.

Any sugestions?

I'm using Ubuntu 22.04 with Cinnamon interface. It always worked properly, than today it starts stucking.

AndreGorny commented 7 months ago

I've tried to open it via terminal and recieved the following message:

/$ whatsie Gtk-Message: 17:17:19.122: Failed to load module "xapp-gtk3-module" Qt: Session management error: Could not open network socket propsReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.143\" (uid=1000 pid=9082 comm=\"/snap/whatsie/148/usr/bin/whatsie \" label=\"snap.whatsie.whatsie (enforce)\") interface=\"org.freedesktop.DBus.Properties\" member=\"GetAll\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=768 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")" nmReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.143\" (uid=1000 pid=9082 comm=\"/snap/whatsie/148/usr/bin/whatsie \" label=\"snap.whatsie.whatsie (enforce)\") interface=\"org.freedesktop.NetworkManager\" member=\"GetDevices\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=768 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")" "Object path cannot be empty"/$ whatsie Gtk-Message: 17:17:19.122: Failed to load module "xapp-gtk3-module" Qt: Session management error: Could not open network socket propsReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.143\" (uid=1000 pid=9082 comm=\"/snap/whatsie/148/usr/bin/whatsie \" label=\"snap.whatsie.whatsie (enforce)\") interface=\"org.freedesktop.DBus.Properties\" member=\"GetAll\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=768 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")" nmReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.143\" (uid=1000 pid=9082 comm=\"/snap/whatsie/148/usr/bin/whatsie \" label=\"snap.whatsie.whatsie (enforce)\") interface=\"org.freedesktop.NetworkManager\" member=\"GetDevices\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=768 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")" "Object path cannot be empty"

Could it be the problem? If it is, any idieas about how to fix it?

evdbovenkamp commented 5 months ago

I have the same problem on Ubuntu 23.10 (snap)

prury commented 5 months ago

i know its not ideal, but for me it was solved when i changed to latest version on snap store instead of last stable version, using Ubuntu 24.04.

keshavbhatt commented 5 months ago

Please verify and reopen this ticket if this still happens in new version 4.15 of Whatsie.

AshkanArabim commented 1 month ago

I have the same issue on my AUR install (version 4.16.0-1) I haven't checked snap yet.

EDIT: snap version works! (v4.16.0.91e1812)

Where should I open an issue to report the AUR problem?

image