Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doesnt recieve/send messages #145

Open
karesosis opened this issue Nov 18, 2023 · 6 comments
Open

doesnt recieve/send messages #145

karesosis opened this issue Nov 18, 2023 · 6 comments

Comments

@karesosis
Copy link

ui works fine while the background is freeze. after reloading in tray of with f5 its gets the messages and i am able to send in the first 10 secs or whatsoever after that back to freeze. idk if the terminal output is related or not. (using ubuntu22.04)

whatsie 
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.433\" (uid=1000 pid=30962 comm=\"/snap/whatsie/146/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=763 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.433\" (uid=1000 pid=30962 comm=\"/snap/whatsie/146/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=763 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")"
"Object path cannot be empty"
@ABSounds
Copy link

I'm getting exactly the same behavior on 23.10.

@karesosis
Copy link
Author

in my case the problem started right after i updated whatsapp within the snap. "Update available : Click to update Whatsapp >"
i did uninstall/install the snap and this time skipped the update, things went well for couple of hours then i assume it updated by itself now the issue occurred again.

@iuridiniz
Copy link

flatpak has the same issue (I have booth)

@iuridiniz
Copy link

flatpak

iuri@GTR:~$ com.ktechpit.whatsie 
Gtk-Message: 09:12:56.789: Failed to load module "canberra-gtk-module"                                                                                                                
Gtk-Message: 09:12:56.789: Failed to load module "canberra-gtk-module"                                                                                                                
qt.qpa.qgnomeplatform: Could not find color scheme  ""                                                                                                                                
Qt: Session management error: Could not open network socket    

snap

iuri@GTR:~$ whatsie 
/usr/share/libdrm/amdgpu.ids: No such file or directory
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.186\" (uid=1000 pid=59472 comm=\"/snap/whatsie/146/org.freedesktop.NetworkManager\" (uid=0 pid=4742 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.186\" (uid=1000 pid=59472 comm=\"/snap/whatsie/146/usrorg.freedesktop.NetworkManager\" (uid=0 pid=4742 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")"
"Object path cannot be empty"

in both, the app open, but I can't send messages

@keshavbhatt
Copy link
Owner

The issue is not related to what is being reported in the stdout. They are unrelated.
There are some issue with session being cached and not validated later by the remote. Clearing the session could help but is not best solution since user need to re-login after every application quit.

@flosoft
Copy link

flosoft commented Jan 6, 2024

I've been having the same issue. It's now gotten to a level where the issue happens immediately after relaunching.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants