-
Notifications
You must be signed in to change notification settings - Fork 171
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
Shell 46 Beta error occurred in AboutToShow #502
Comments
Also, there is this. Let me know if you want a separate issue opened for it:
|
I'm on Gnome-Shell 45.4, extension version 57, Fedora 39 and observed the following error in my journal:
|
@jbicha I have this same error, and I tracked it to mattermost. It seems that it doesn't implement the answer for AboutToShow... |
@jbicha I have this same error, and I tracked it to mattermost. It seems that it doesn't implement the answer for AboutToShow... Specifically, it is sending that call to the object /com/canonical/dbusmenu with the interface com.canonical.dbusmenu. Clicking on the mattermost's appindicator to show the menu triggers this. It looks more like a bug in the mattermost client. About the other error, it is also (in my case) from mattermost. The extension tries to get the object properties by calling the Get method from the /StatusNotifierItem object, interface org.freedesktop.DBus.Properties, but it fails for some reason... |
Ok, clearly mattermost doesn't export the com.canonical.dbusmenu. In fact, it exports nothing... |
Also, I found a bug in gjs overrides: the DBus promise doesn't trigger an exception, it just shows the error message in the journal but resolves the promise. I'll fix this tomorrow. |
My fault: the DBus promise does trigger an exception; the problem is that it returns a generic DBus error, so we can't detect this specific case. I think that the only way of fixing this is to send a patch for mattermost. Anyway, I think that a good idea is to add some extra debugging info (the called method and the destination DBus address, object and method) to allow to better detect the culprit in these cases. I'll prepare a patch for that. |
I'm not using Mattermost directly, but through Ferdium as a Flatpak. Is this making a difference? |
Probably not. If the mattermost code is the same, the bug is also in flatpak. It's not really a problem, because the calls are just "informative" (they are used to notify the app that the menu has been shown). |
It's not defined in all the implementations, so in case that we have not, let's just ignore the error and avoid calling it again Fixes: #502
It's not defined in all the implementations, so in case that we have not, let's just ignore the error and avoid calling it again Fixes: #502
It's not defined in all the implementations, so in case that we have not, let's just ignore the error and avoid calling it again Fixes: #502
Closing this as per #525. Note that this has never been a problem or a crash, just a log message with extended stack trace. |
My systemd journal shows the below error. The extension seems to work though.
This guide was recently published:
https://gjs.guide/extensions/upgrading/gnome-shell-46.html
The text was updated successfully, but these errors were encountered: