-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Let me first thank you for this fantastic tool! I'm shocked that there's only one tool (to my knowledge) that allows to open Wayland apps with another user.
But I've been having this problem:
When using teams-for-linux (on Arch installed from the AUR) it mostly works fine, but when it tries to present a notification, the window turns black and I see this output on the console:
(teams-for-linux:23641): libnotify-WARNING **: 13:53:41.092: Failed to connect to proxy
(teams-for-linux:23641): libnotify-WARNING **: 13:54:06.118: Failed to connect to proxy
(teams-for-linux:23641): libnotify-WARNING **: 13:54:41.681: Failed to connect to proxy
[23641:1105/135506.707108:ERROR:libnotify_notification.cc(50)] notify_notification_show: domain=1110 code=24 message="Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached"
The only way to get it back to normal is to kill it and reopen.
Before that I also see these errors repeating when started from ego, even when it's working normally:
[50753:1105/142310.434568:ERROR:browser_main_loop.cc(283)] Gtk: gtk_widget_add_accelerator: assertion GTK_IS_ACCEL_GROUP (accel_group)' failed
These don't show up when started without ego.
On a normal startup (without ego), I see this printed that never shows up on ego:
14:23:40.698 › Running under Wayland, switching to PipeWire...
But that might be because perhaps ego does not support PipeWire.
Please tell me if you need any additional help or logs to troubleshoot this issue.