-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
wayland: mate-panel needs restart after adding notification-area applet #1380
Comments
First of all, THANK YOU for testing and finding this. In my own testing I wasn't able to duplicate this on adding the applet, but DID get the same problem some but not all of the time on removing the applet. I got this warning message on removing the notification area in wayland, implying one or more signals not being properly disconnected:
|
Yes, I have this message too when I delete applet from the panel. |
In my installation the panel crashes when i remove the notification area. But gdb gives me a stacktrace.
stacktrace for better reading in editor: https://www.dropbox.com/scl/fi/5ksvqlezj6t99itk6yf1x/debug_mate_panel?rlkey=xcjqtdnk64l9ki643ap10n4hc&dl=0 |
Same crash happens in x11 too. |
I get only the warning, looks like we are not disconnecting signals properly as it's trying to do something with icon size after the applet has been destroyed |
See #1393 for a fix. With this applied I could repeatedly add and remove the applet in x11 or wayland without getting warnings in a terminal the panel was running from or an unresponsive panel in wayland |
Same crash with 1.26 branch :/ |
Expected behaviour
notification-area
applet should appears right after pressing Add buttonActual behaviour
After adding
notification-area
applet it does not appear in the panel, until panel is restarted (e.g. relogin to session)Steps to reproduce the behaviour
--with-in-process-applets=all
optionMATE general version
1.26
Package version
master
Linux Distribution
Debian 12
Link to bugreport of your Distribution (requirement)
n/a
The text was updated successfully, but these errors were encountered: