![]() Wed May 25 09:34:27.838 Warning: propsReply "An AppArmor policy prevents this sender from sending this message to this recipient type=\"method_call\", sender=\":1.174\" (uid=1000 pid=11559 comm=\"WickrMe \" label=\" (enforce)\") interface=\"\" member=\"GetAll\" error name=\"(unset)\" requested_reply=\"0\" destination=\"\" (uid=0 pid=895 comm=\"/usr/sbin/NetworkManager -no-daemon \" label=\"unconfined\")" ![]() Wed May 25 09:34:27.763 Info: SWITCHBOARD SERVICE: Started. Wed May 25 09:34:27.684 Info: Application "WickrMe" for "Wickr, LLC" Wed May 25 09:34:27.389 Warning: Qt: Session management error: Could not open network socket Here’s the full output from starting Wickrme from the terminal after a fresh install (before fiddling with any permissions) Gtk-Message: 09:34:27.050: Failed to load module "xapp-gtk3-module" I’ve tried allowing all permissions too, but this also makes no difference. ![]() I’ve tried installing each of these via the Snap Store and via the terminal. This time however I’ve tried the Stable, Candidate, Beta and Edge versions and all are resulting in the application not loading and a “Aborted (Core Dumped” error. This was the advice on the Wickr website too actually. Last time this similar issue happened I got round it by reverting to the Candidate version which worked fine and then waited for the Stable version to update, and once it had, all worked as expected. I’ll come back and post the full output in a little while, but I recall there was another error in the terminal output "Failed to load module … " Starting from the terminal results in an error “Aborted (Core Dumped)” and a graphical window for Wickr kinda begins to appear and then vanishes. Starting Wickrme from the menu results in absolutely nothing. A similar issue to this raised its head a while ago - in fact I think Wickr even posted something on their website about it at the time.
0 Comments
Leave a Reply. |