-
Notifications
You must be signed in to change notification settings - Fork 14
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
One category button does crash the extension #54
Comments
Hello @jasursadikov! Thank you for reporting this bug! I'm sorry for taking too long to see this issue 😅 If yes, can you take a look at the logs, please?
|
Hi! Sorry for long pause. I do not see anything valuable comming to the logs when I run the debug session. I can do the screen recording and share with you if you want to. You can see that I do not have the extension on my main session and I do have it on my debug session. I've tried to reproduce the issue, but nothing really happened in the log :) |
Hi, buddy! Yeah it's running, and I think I can see some error messages in your terminal from the Screen Shot. |
Here is the log:
|
Hello, buddy! Thanks for sending the complete logs! 🔍 Well, that's pretty strange, the second missing file error just today! hahaha Let's investigate this: 🤔 But that still seems strange, this file should not be missing like that... Taking a look at these lines: (gnome-shell:14366): GNOME Shell-CRITICAL **: 19:27:34.859: Could not load extension Emoji-Copy: Error: Missing metadata.json
Stack trace:
createExtensionObject@resource:///org/gnome/shell/ui/extensionSystem.js:384:19
_loadExtensions/extensionObjects<@resource:///org/gnome/shell/ui/extensionSystem.js:771:34
_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:755:49
async*_enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:792:48
_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:827:20
async*init@resource:///org/gnome/shell/ui/extensionSystem.js:76:14
_initializeUI@resource:///org/gnome/shell/ui/main.js:303:22
start@resource:///org/gnome/shell/ui/main.js:175:11
@resource:///org/gnome/shell/ui/init.js:12:47
@resource:///org/gnome/shell/ui/init.js:21:20 This line tells us that the extension is not even loading, and this error seems to be directly from the Extensions application. This doesn't seems to be linked with the original error you reported, because this time, the extension is not even being loaded 😕 So, can you try pulling the latest changes from the master branch? Then re-run the command?
I'll be happy to know the results! 🙏 |
I do not know why, but it works perfectly with me an I experience no issues :) |
Bug Report
Current Behavior
The highlighted button does crash the extension:
Expected behavior/code
I am not sure how what it is supposed to do.
Environment
The text was updated successfully, but these errors were encountered: