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

Teams crashes when it tries to popup a notification (and other problems) #166

Open
nfp0 opened this issue Nov 5, 2024 · 3 comments
Open
Labels
has workaround There is an alternative solution to the issue.

Comments

@nfp0
Copy link

nfp0 commented Nov 5, 2024

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.

@intgr
Copy link
Owner

intgr commented Nov 6, 2024

Thanks for the detailed report!

I haven't had much time to improve ego recently, but one of these days I hope to get back to it.

libnotify-WARNING **: 13:53:41.092: Failed to connect to proxy

I haven't used any applications that send desktop notifications. Will have to investigate how libnotify works.

It's surprising that Teams crashes with such a fatal failure mode simply because it can't connect to notification daemon. Not sure if it's possible to easily proxy notifications to the main desktop, or just suppress the notifications.

@intgr
Copy link
Owner

intgr commented Nov 7, 2024

Apparently it's possible to run a custom daemon that handles desktop notifications. Many are documented here: https://wiki.archlinux.org/title/Desktop_notifications#Standalone

Some of them segfault when running in an ego shell. But I managed to get Arch package xfce4-notifyd working. Just run /usr/lib/xfce4/notifyd/xfce4-notifyd & in an ego shell, and you can test it by running notify-send "Hi, this is a test notification".

Also mate-notification-daemon worked.

This is a work-around at best though.

@intgr intgr added the has workaround There is an alternative solution to the issue. label Nov 7, 2024
@nfp0
Copy link
Author

nfp0 commented Nov 8, 2024

Thank you for finding this workaround!
I'll give it a try later when I get the chance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has workaround There is an alternative solution to the issue.
Projects
None yet
Development

No branches or pull requests

2 participants