GNOME Bugzilla – Bug 691529
Gnome-shell silently fails to install any extensions
Last modified: 2021-07-05 14:21:06 UTC
I've Gnome 3.6 running under Gentoo Linux. When I'm trying to install extensions from extensions.gnome.org popup appears asking if I'm allow to install. Then I click "Install" button and nothing happens. Gnome just creates empty directory in .local/share/gnome-shell/extensions and extension switch turns to "ON" state - and thats all. When I'm updating extension page switch resets to "OFF" state. There is no any messages in .xsession-errors or /var/log/gdm/* I've tried empty HOME but without any success. Manually installed extensions works.
Check ~/.cache/gdm/session.log
Yeah, I've got error message: JS ERROR: !!! Exception was: TypeError: message.response_body.flatten().get_as_bytes is not a function JS ERROR: !!! message = '"message.response_body.flatten().get_as_bytes is not a function"' JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/ui/extensionDownloader.js"' JS ERROR: !!! lineNumber = '85' JS ERROR: !!! stack = '"gotExtensionZipFile([object _private_Soup_SessionAsync],[object _private_Soup_Message],"user-theme@gnome-shell-extensions.gcampax.github.com",[object _private_unknown_GLocalFile],callback,errback)@/usr/share/gnome-shell/js/ui/extensionDownloader.js:85 ([object _private_Soup_SessionAsync],[object _private_Soup_Message])@/usr/share/gnome-shell/js/ui/extensionDownloader.js:257 But I don't even realize what to do with that. It doesn't look descriptive.
It seems that you have an outdated libsoup.
Ok, I'm going to update to 2.40.2 from 2.38.1 But I think that gnome-shell should not SILENTLY fail in such case. Some useful diagnostic message should be given to user.
Hooray, updating libsoup to 2.40.2 solved my problem.
I can't really see a reason why this bug was resolved, because in repository the libsoup dependencies are still not fixed. In both 'gnome-3-6' and master branches configure.ac still only looks for 'libsoup-2.4' and doesn't specify minimum version.
Runtime dependencies aren't specified as built-time dependencies.
(In reply to comment #7) > Runtime dependencies aren't specified as built-time dependencies. o_O When you google for '_private_Soup_SessionAsync' then you can see that this same issue isn't specific to Gentoo, it's a wide-spread issue that can be easily solved by requiring libsoup version that works during build.
(In reply to comment #8) > (In reply to comment #7) > > Runtime dependencies aren't specified as built-time dependencies. > > o_O > > When you google for '_private_Soup_SessionAsync' then you can see that this > same issue isn't specific to Gentoo, it's a wide-spread issue that can be > easily solved by requiring libsoup version that works during build. Sorry, I exaggerated a bit, but the issue is that extension downloader uses 'soup_buffer_get_as_bytes' function which is only available since libsoup-2.40.
Created attachment 233293 [details] [review] libsoup-2-40-requirements-master.patch
(In reply to comment #10) > Created an attachment (id=233293) [details] [review] > libsoup-2-40-requirements-master.patch Same patch applies fine to gnome-3-6 branch with `git am <file>`.
Yeah-yeah, also what about descriptive diagnostic message instead of silent error supressing?
That's waiting on better logging facilities, e.g. the systemd journal. We already return the GError to the page over DBus, and look out for common errors from the page itself, but we haven't added support for that error yet.
Why not to introduce "Unknown error, look for the logs" message for all the unhandled and unknown errors?
You admitted it yourself that the log wasn't something that helped you. In the short term, it might just be easier to require libsoup at build time. We've swung a few ways about buildtime vs. runtime dependencies.
But why not just to inform user that something went wrong? Not supress error?
*** Bug 704826 has been marked as a duplicate of this bug. ***
*** Bug 709828 has been marked as a duplicate of this bug. ***
*** Bug 755534 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab-test.gnome.org/fmuellner/gnome-shell-extensions/issues/96.
Sorry for the noise, I "found" a bug in the migration script: https://gitlab.gnome.org/External/bugzilla-to-gitlab-migrator/issues/2
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.