gnome-shell issueshttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues2024-03-18T07:41:25Zhttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7469allow installing GNOME extensions from the command line without user interaction2024-03-18T07:41:25ZTrenton Fumakiallow installing GNOME extensions from the command line without user interaction### Feature summary
Currently, the only "official" way of installing GNOME extensions is by manually visiting https://extensions.gnome.org with a browser, browsing/searching for a desired extension there, then clicking on the blue "Inst...### Feature summary
Currently, the only "official" way of installing GNOME extensions is by manually visiting https://extensions.gnome.org with a browser, browsing/searching for a desired extension there, then clicking on the blue "Install" button on the extension's detail page. This will then (eventually) trigger a modal asking for installation confirmation.
**It is thereby currently not possible to automate an extension-enhanced GNOME desktop environment setup without resorting to workarounds.**
Also, extensions can only be installed one by one; therefore, in a typical productive/usable GNOME environment with multiple extensions, it requires a manual modal confirmation for each extension.
This is an issue/feature other users are also looking for:
* https://unix.stackexchange.com/q/617288/20230
* https://stackoverflow.com/q/72857634/923560
* https://stackoverflow.com/q/43357370/923560
* https://discussion.fedoraproject.org/t/how-to-install-gnome-extensions-globally-and-allow-automatic-updates/90895
* https://github.com/brunelli/gnome-shell-extension-installer
* https://www.reddit.com/r/gnome/comments/rbl85n/installing_gnomeshell_extensions_on_command_line/
* https://discourse.gnome.org/t/enable-gnome-extensions-without-session-restart/7936
#### How (manual) GNOME extension installation currently works
As an example, I use the extension [*Extension List* by grroot](https://extensions.gnome.org/extension/3088/extension-list/).
On that extension's detail page, clicking the blue *Install* button triggers an [undocumented *xdg-mime*/*xdg-open* integration with *gnome-browser-connector* (`org.gnome.BrowserConnector`) on the `gnome-extensions://`](https://gitlab.gnome.org/GNOME/gnome-browser-connector/-/blob/1ed2008a39acceaed153b8b3b865081ceba98ab2/contrib/org.gnome.BrowserConnector.desktop.in#L10).
For this example, the URL is gnome-extensions://extension-list%40tu.berry?action=install .
*gnome-browser-connector* will then delegate to `org.gnome.Shell.Extensions`'s method [`org.gnome.Shell.Extensions.InstallRemoteExtension`](https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/fc58f6f053ae0dd533b58c70ed1b34ed18ef5d6c/data/dbus-interfaces/org.gnome.Shell.Extensions.xml#L156). This is effectively as executing the following command:
```
gdbus call --session \
--dest org.gnome.Shell.Extensions \
--object-path /org/gnome/Shell/Extensions \
--method org.gnome.Shell.Extensions.InstallRemoteExtension \
"extension-list@tu.berry"
```
This method is implemented in `gnome-shell/js/ui/extensionDownloader.js`'s [`installExtension(...)`](https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/fc58f6f053ae0dd533b58c70ed1b34ed18ef5d6c/js/ui/extensionDownloader.js#L34) and will open an `InstallExtensionDialog extends ModalDialog.ModalDialog`. **Only by manually interacting with this modal's *Install* button, it is possible to install the extension (implemented in [`InstallExtensionDialog._onInstallButtonPressed()`](https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/fc58f6f053ae0dd533b58c70ed1b34ed18ef5d6c/js/ui/extensionDownloader.js#L300)**.
### How would you like it to work
Preferably, [`gnome-extensions install ...`](https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/main/subprojects/extensions-tool/man/gnome-extensions.txt#L200) would allow for installing (one or more) extensions by providing their IDs ("`uuid`" in gnome-extensions parlance), and would do so without requiring user interaction. E.g.: `gnome-extensions install 'extension-list@tu.berry'`. (Finding out some extension's `uuid` is not easy itself, as https://extensions.gnome.org doesn't show it...).
As an interim solution, it would probably be easier to just expose/export/make public a DBus method that delegates to what is done in [`InstallExtensionDialog._onInstallButtonPressed()`](https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/fc58f6f053ae0dd533b58c70ed1b34ed18ef5d6c/js/ui/extensionDownloader.js#L300).
### Relevant links, screenshots, screencasts etc.
![image](/uploads/a985b70378b647e30987735957f4b961/image.png)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7346Tray: Icons are pixelated2024-03-12T00:04:41ZMartinTray: Icons are pixelatedHello,
Starting from version 44 shell tray icons (from the shell API) are pixelated; this looks like a regression from
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2590/diffs
![Zrzut_ekranu_z_2024-01-25_18-47-07](/uploads...Hello,
Starting from version 44 shell tray icons (from the shell API) are pixelated; this looks like a regression from
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2590/diffs
![Zrzut_ekranu_z_2024-01-25_18-47-07](/uploads/1f4cf9277c31f57ebbd0311bb00f6559/Zrzut_ekranu_z_2024-01-25_18-47-07.png)
Can be tested in:
https://extensions.gnome.org/extension/2890/tray-icons-reloaded/
or https://github.com/hardpixel/unite-shell
### Affected version
* OS: Arch Linux
* GNOME Shell version: 45.3
* Appear in XOrg/XWayland
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7345Tray: Icons have a black background / missing transparency2024-03-12T00:04:29ZMartinTray: Icons have a black background / missing transparencyHello,
Starting from version 44 shell tray icons (from the shell API) lost transparency; this looks like a regression from
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2590/diffs
![Zrzut_ekranu_z_2024-01-25_18-47-07](/upl...Hello,
Starting from version 44 shell tray icons (from the shell API) lost transparency; this looks like a regression from
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2590/diffs
![Zrzut_ekranu_z_2024-01-25_18-47-07](/uploads/1f4cf9277c31f57ebbd0311bb00f6559/Zrzut_ekranu_z_2024-01-25_18-47-07.png)
Can be tested in:
https://extensions.gnome.org/extension/2890/tray-icons-reloaded/
or https://github.com/hardpixel/unite-shell
### Affected version
* OS: Arch Linux
* GNOME Shell version: 45.3
* Appear in XOrg/XWayland
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7013extensionSystem: Show notification after immediate update2023-09-15T12:51:03ZFlorian Müllnerfmuellner@gnome.orgextensionSystem: Show notification after immediate updateThe following discussion from !2951 should be addressed:
- [ ] @carlosg started a [discussion](https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2951#note_1845783): (+3 comments)
> Other than the minor comment LGTM. Perh...The following discussion from !2951 should be addressed:
- [ ] @carlosg started a [discussion](https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2951#note_1845783): (+3 comments)
> Other than the minor comment LGTM. Perhaps we could add a "Your extensions were updated" notification for the next cycle, to avoid possible misguided reported issues.Florian Müllnerfmuellner@gnome.orgFlorian Müllnerfmuellner@gnome.orghttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6826Gnome extensions not working after upgrading to gnome-shell 44.22024-03-12T00:06:37ZSKelemGnome extensions not working after upgrading to gnome-shell 44.2<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Provide at least the following information:
* OS: **Ubuntu 2...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Provide at least the following information:
* OS: **Ubuntu 23.04**
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions) **44.2**
* Does this issue appear in XOrg and/or Wayland? **I don't know what these are or how to exercise them.**
* Does this issue happen without extensions (please follow instructions below) **Yes, when all extensions are disabled, all extensions are still disabled.**
### Bug summary
After upgrading to gnome-shell 44.2, none of the extensions are working.
### Steps to reproduce
1. gnome-extensions-app shows all extensions as disabled and none can be enabled.
2. Browse to https://extensions.gnome.org/local/, it lets me flip the toggles for enabling individual extensions, but the extensions don't actually start running.
3. Alt-F2 brings up the "run a command" window. "r" no longer restarts X/gnome. It now says "command not found".
### What happened
None of the extensions work. None of the extensions can be enabled to run in gnome-extensions-app.
### What did you expect to happen
I expected :
- to have a 4x4 grid of workspaces. (Workspace Matrix: The most important productivity gnome-app!)
- that Dash to Dock work.
- to be able to hide the taskbar
- that the applications menu work
- that Bing Wallpaper work
- ....
### Relevant logs, screenshots, screencasts etc.
![gnome-extensions-app](/uploads/f707184c416033cebb0266a15c50b946/gnome-extensions-app.png)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6774Remember window size and position2023-06-16T12:02:19ZManuel TransfeldRemember window size and positionThe default window size allows me to see exactly 2 elements and the "Extension Updates Ready" bar at the bottom.
To scroll through the list and find what I'm looking for today is ridiculous even if I can see generous 3.5 list elements af...The default window size allows me to see exactly 2 elements and the "Extension Updates Ready" bar at the bottom.
To scroll through the list and find what I'm looking for today is ridiculous even if I can see generous 3.5 list elements after I began scrolling.
It would help to see 8-10 elements by default.
I also never want to have this window centered but on the left half of my screen because I a) open an extension's settings dialog or b) its webpage likely on the right half of my screen.
Remembering the window size and position would be awesome. Thank you.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6773List with only updatable Extensions / filter by attribute2023-06-16T12:05:42ZManuel TransfeldList with only updatable Extensions / filter by attribute## Feature 1: filter
Add the ability to **filter the extension list** by the following attributes:
- update-available
- enabled
- incompatible
- built-in
- will-become-compatible-on-update (reall important!)
### Idea 1:
use a horizontal...## Feature 1: filter
Add the ability to **filter the extension list** by the following attributes:
- update-available
- enabled
- incompatible
- built-in
- will-become-compatible-on-update (reall important!)
### Idea 1:
use a horizontal toggle button group
### Idea 2:
Search string like "/enabled=true"
## Feature 2: remember state or defaults
Remember last used search & filter when opening the dialog next time.
Or: set a default filter + show updatable if present
## Feature 3:
Show only updatable if opened via the update notification
## Background:
- I receive a notification: ~"2 updates available"
- I open gnome-extensions-app
- I scroll through 116* elements looking for 2 yellow stars being distracted from all those red incompatible icons scurrying past my eyes so I regularly scroll the list 3 times
- Let's avoid this by implementing one of my 2 ideas or any better idea from you guys
*gnome-extensions list | wc -l
---
I hope this is the right repo for gnome-extensions-app because its about window doesn't point to the right repo (at least I think so).https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6320auth process not reaped when establishing a VPN connection2023-11-22T13:59:33ZMichael Bieblauth process not reaped when establishing a VPN connectionWhen establishing a VPN connection, I get zombie processes like this:
```
michael 144728 0.0 0.0 0 0 ? Z 15:22 0:00 [nm-openvpn-auth] <defunct>
```
This only happens when certain extensions are active. In my cas...When establishing a VPN connection, I get zombie processes like this:
```
michael 144728 0.0 0.0 0 0 ? Z 15:22 0:00 [nm-openvpn-auth] <defunct>
```
This only happens when certain extensions are active. In my case it is dash-to-panel.
Related is likely https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.7/js/ui/components/networkAgent.js#L455
Now it's unclear whether this is a bug in GNOME Shell or the extension itself.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6019The window to modify parameters of an extension is too narrow2023-05-20T09:28:32ZAlexis LefebvreThe window to modify parameters of an extension is too narrow
### Affected version
- Ubuntu 22.04.1 LTS
- GNOME Shell 42.4
- Wayland
But other users affected may have other versions.
### Bug summary
The window to modify parameters of an extension is too narrow
### Steps to reproduce
1. Open ...
### Affected version
- Ubuntu 22.04.1 LTS
- GNOME Shell 42.4
- Wayland
But other users affected may have other versions.
### Bug summary
The window to modify parameters of an extension is too narrow
### Steps to reproduce
1. Open the Extensions app
2. Click on _Parameters_ for one extension
### What happened
The window is too narrow and some information is hidden, the vertical scrollbar is not obvious.
Users have to use horizontal scroll in order to change the settings, which is inconvenient.
### What did you expect to happen
The inner window should use all the available width.
### Relevant logs, screenshots, screencasts etc.
![image](/uploads/c615c711dc5154c126ee70298abd9360/image.png)
![image](/uploads/26dbdfce9aa569fb4205b7bc98379cb5/image.png)
([source](https://github.com/kgshank/gse-sound-output-device-chooser/issues/252#issuecomment-1191195863))
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5516Gnome extensions app: unable to enable/disable extesion when extension is broken2022-11-10T14:56:21ZPeder B. SundtGnome extensions app: unable to enable/disable extesion when extension is brokenWhen an extension is broken, the switch to enable/disable it is disabled. This is problematic if the attempt to start said extension has undesired side-effects.
Consequence: https://github.com/RensAlthuis/vertical-overview/issues/88#iss...When an extension is broken, the switch to enable/disable it is disabled. This is problematic if the attempt to start said extension has undesired side-effects.
Consequence: https://github.com/RensAlthuis/vertical-overview/issues/88#issuecomment-1134666192https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4526Repaint glitches in Gnome Shell Windows (due to Blur My Shell extension)2023-11-04T05:40:58ZgnoloooRepaint glitches in Gnome Shell Windows (due to Blur My Shell extension)I'm facing an issue in Ubuntu 21.04 with Gnome 3.38. Basically, some parts of the windows glitches. From my experience I think this parts are mostly the "updating" ones (animated icons or buttons, typing cursors etc).
I noticed also this...I'm facing an issue in Ubuntu 21.04 with Gnome 3.38. Basically, some parts of the windows glitches. From my experience I think this parts are mostly the "updating" ones (animated icons or buttons, typing cursors etc).
I noticed also this common behaviors in all them:
1. It happens regardless of shell or applications theme.
2. It only happens if there are no other open windows behind the window in use (or if they are running in background but minimized).
3. It doesn't happen if there are windows behind.
4. It disappears by moving, maximizing, minimizing or resizing the window in use.
5. It doesn't happen on all applications (I tested that this happens with all Gnome Apps, OBS, Telegram, VLC, but not Spotify, Chrome, Olive Video Editor).
P.S.: I face this issue in both Xorg and Wayland, so honestly I don't really know if this bugs are related to Gnome Shell or Mutter.
I don't really know how to describe what I see, so here's a brief video I did to show and explain it. Hoping it will help. (Here's also a link to the same video uploaded on YouTube, not listed so it's not public. https://youtu.be/CRE4-49wMTo If you want to see it in HD here you can - sorry for resolution but my PC has 1366x768 monitor so highest resolution on YT is only 720).
My PC specifications in case you need them:
Laptop Acer A315-21-90VF
Cpu AMD A9 with internal Radeon R5 Graphics
1TB SSD Sata
12GB Ram DDR4
![Gnome_Bugs](/uploads/23505ccca7d1731535a933b6a0471048/Gnome_Bugs.mp4)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4336Auto-install pending extension updates during reboot/log out event2022-01-24T13:14:07Zamitkul2Auto-install pending extension updates during reboot/log out event<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS an...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
-->
Fedora 34 / GNOME 40.1
### Bug summary
<!--
Provide a short summary of the bug you encountered.
-->
I am greeted with a notification from Extensions app, asking me to log out to install extension updates.
It usually happens when I log in after a restart.
It does not seem correct to have to ask the user to log out right after they log in.
### Steps to reproduce
<!--
1. Step one
2. Step two
3. ...
-->
0. sudo dnf update (probably not relevant)
1. Restart through gnome-shell menu or terminal
2. Log in
3. Be greeted with a notification from Extensions app, asking me to log out to install extension updates
### What happened
<!--
What did GNOME Shell do that was unexpected?
-->
Asked me to log out to install extension update right after I logged in
### What did you expect to happen
<!--
What did you expect GNOME Shell to do?
-->
If an extension update is available and is already downloaded, it should get installed during log out / restart event.
### Relevant logs, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
(I don't have a screenshot right now, will add it when I encounter it again)
Relevant Reddit thread:
https://www.reddit.com/r/gnome/comments/nihutj/401_autoupdating_extensions_before_user_logs_in/
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3803gnome-extensions enable doesn't indicate error2022-11-22T15:18:17ZJustin Donnellygnome-extensions enable doesn't indicate error<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
* GNOME OS Nightly
* GNOME 40 Beta
* Wayland
<!--
Provide at l...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
* GNOME OS Nightly
* GNOME 40 Beta
* Wayland
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version
* Does this issue appear in XOrg and/or Wayland
-->
### Bug summary
When running `gnome-extensions enable` results in an error, nothing is printed to STDOUT or STDERR, and a 0 exit code is returned.
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
1. Create a new extension: `gnome-extensions create --name="No Op" --description="Do nothing" --uuid=no-op@justinrdonnelly.github.com`
2. Change `shell-version` in `metadata.json` to be a shell other than the one you are using (or none at all)
3. Log out and back in
4. Attempt to enable the extension via CLI: `gnome-extensions enable no-op@justinrdonnelly.github.com`
- Nothing is printed to STDOUT or STDERR
- The return code (`echo $?`) is 0
You can use GNOME Extensions (flatpak) (`flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo && flatpak install gnome-nightly org.gnome.Extensions && flatpak run org.gnome.Extensions`) to see that the extension is not enabled, and cannot be enabled. You can also see the error message "The extension is incompatible with the current GNOME version".
<!--
1. Step one
2. Step two
3. ...
-->
### What happened
`gnome-extensions enable` printed nothing to STDOUT or STDERR, and returned a zero exit code even though it did not enable the extension
<!--
What did GNOME Shell do that was unexpected?
-->
### What did you expect to happen
`gnome-extensions enable` print an error message to STDERR, and return a non-zero exit code
<!--
What did you expect GNOME Shell to do?
-->
### Relevant logs, screenshots, screencasts etc.
N/A
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3383Extensions App - Expand/ Collapse All2020-11-12T01:56:43ZGabriel dos Reis MattosoExtensions App - Expand/ Collapse All<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
<!--
Describe what you would like to be able to do with GNOME...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
<!--
Describe what you would like to be able to do with GNOME Shell
that you currently cannot do.
-->
Collapse or expand all extension's description at once
### How would you like it to work
<!--
If you can think of a way GNOME Shell might be able to do this,
let us know here.
-->
By a click of a button I can hide or show all the extension's description.
Some ideas in the mock-ups bellow
### Relevant links, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation,
code, mockups or a similar feature in another desktop environments,
please provide them here.
-->
Some ideas:
#### - Header Bar: Button with Icon
![extensions-mockup-headerbar-button-icon](/uploads/c4f30775eef23d430aabe88796d52d5e/extensions-mockup-headerbar-button-icon.png)
#### - Menu: Button with icons
![extensions-mockup-menu-button-icon](/uploads/0b065a11f253a2959e1743a92097086e/extensions-mockup-menu-button-icon.png)
#### - Menu: Button with Text
![extensions-mockup-menu-button-text](/uploads/e6d6f57461c67a1c3b5e5dd9b05d2fcf/extensions-mockup-menu-button-text.png)
#### - Menu: Switch
![extensions-mockup-menu-expand](/uploads/bc4ae8c2405df8ce36a68ad40f46ecb5/extensions-mockup-menu-expand.png)
![extensions-mockup-menu-collapse](/uploads/2ab19a2d28fe5fe5c10dcd91630f899c/extensions-mockup-menu-collapse.png)
- Mockups file
[extensions-mockup.xcf](/uploads/05859135b3a114894eb7d9c71c6beb18/extensions-mockup.xcf)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2857Windows shadows causing artefacts with the new Shell.BlurEffect2023-11-04T05:40:45ZAurélien Hamyaunetx@yandex.comWindows shadows causing artefacts with the new Shell.BlurEffect### Affected version
Gnome 3.36.2, both Xorg and Wayland
### Bug summary
When using the integrated blur effect `Shell.BlurEffect` with a background blur mode, moving windows around the 'themed' widget is currently causing artefacts.
...### Affected version
Gnome 3.36.2, both Xorg and Wayland
### Bug summary
When using the integrated blur effect `Shell.BlurEffect` with a background blur mode, moving windows around the 'themed' widget is currently causing artefacts.
### Steps to reproduce
In the looking glass inspector (`Alt+f2`, `lg`):
1. Create a widget:
```js
blurred_widget = new St.Widget({
x: 0,
y: 0,
width: 100,
height: 100,
});
```
2. Create a blur effect with mode 1 (blurs the background):
```js
effect = new Shell.BlurEffect({
brightness: 0.6,
sigma: 30,
mode: 1
});
```
3. Add the effect to the widget and place the widget:
```js
blurred_widget.add_effect(effect);
Main.uiGroup.add_child(blurred_widget);
```
Exit the inspector (`esc`) and move windows around: when approaching from the widget, the windows shadows cause artefacts (even when not touching it entierely).
This is probably due to the effect not being repaint (?) because typing `effect.queue_repaint()` in the inspector resolves this problem temporarly and transforms that in a beautifully blurred widget.
I don't know if this is intended (after all, this effect is maybe not meant to be used this way), but it's sad because it is the only thing that prevents making an extension that adds "native" blur to the panel/dash (in dash to dock) or a lot of very interresting things.
### Relevant logs, screenshots, screencasts etc.
![VirtualBox_Fedora_01_06_2020_22_51_50](/uploads/7a9721f3ab63f1730f75ee2166a6e8c3/VirtualBox_Fedora_01_06_2020_22_51_50.png)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2689Extension installation?2022-09-29T18:54:36ZFlorian Müllnerfmuellner@gnome.orgExtension installation?The Extensions app handles extension configuration, updates and removal, but not installation. That is in line with the design outlined in #1968, which keeps the website/web-extension in charge of that.
Unfortunately that's not the end ...The Extensions app handles extension configuration, updates and removal, but not installation. That is in line with the design outlined in #1968, which keeps the website/web-extension in charge of that.
Unfortunately that's not the end of the story.
It turns out that the host integration works by registering a binary with the browser, which it then launches as necessary and communicates with the process via stdout. Which is extremely sandboxing-unfriendly to say the least:
- setting it up with the minimal permissions is [incredibly cumbersome](https://discussion.fedoraproject.org/t/firefox-flatpak-on-flathub-beta/17878/30?u=fmuellner)
- the alternative of registering a script that does `flatpak-spawn --host chrome-gnome-shell` is slightly less cumbersome, but requires permission to run random programs on the host (not great for browsers!)
This is a problem for *all* web exensions that use native messaging, so there's some pressure to come up with [a sandboxable replacement](https://bugzilla.mozilla.org/show_bug.cgi?id=1591387#c36). Maybe that means we can just wait it out :shrug:
But I don't like standing in the way of flatpak adoption, in particular for browsers where sandboxing is particularly desirable.
Off-hand I see two options around the issue:
- change the website to drop the whole plugin/management stuff and expose simple "Install" buttons that use something like `gnome-extension:foobar@extensions.example.com`, then have a simple schema handler that translates that to the corresponding D-Bus call
Compelling from a gnome-shell perspective, as most of the work would be on the website; but it's somewhat less nice (the site no longer knows whether an extension is already installed or not), and the change would either render the web extension obsolete (probably not popular with its developers) or make the website more complex if implementating the change as fallback when the plugin/connector aren't available or fail
- add extension browsing/search/installation in the Extensions app
Probably more appealing for users, but a big increase of the app scope.
Thoughts?
@adayhttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2621Extensions are not disabled on log out2023-09-08T18:14:32ZRomain VigierExtensions are not disabled on log out### Affected version
At least GNOME Shell 3.34 on Fedora 31 and 3.36 on Arch Linux, but maybe older shell versions as well.
### Bug summary
When logging out of the session, extensions do not get disabled.
### What happened
I'm the w...### Affected version
At least GNOME Shell 3.34 on Fedora 31 and 3.36 on Arch Linux, but maybe older shell versions as well.
### Bug summary
When logging out of the session, extensions do not get disabled.
### What happened
I'm the writer of a GNOME Shell extension and a user filed an issue that prompted me to look at the extension's behavior when logging out and back in. From my extension's debug output, it seems that extensions are not disabled on log out.
### What did you expect to happen
From the `extension.js` `disable()` function documentation on the [GNOME Wiki](https://wiki.gnome.org/Projects/GnomeShell/Extensions/Writing#extension.js_.28Required.29) (emphasis mine):
> This function could be called after your extension is uninstalled, disabled in GNOME Tweaks, **when you log out** or when the screen locks.
I relied on this behavior in my code as I have to reset some user settings before the extension gets enabled again when logging in. That is the cause of the bug my user reported.
Should the shell disable extensions on log out (and is currently not doing that) or is the documentation not up-to-date with what is really happening?
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2514Add option to disable extension updates2023-12-13T00:45:16ZTorbenAdd option to disable extension updatesI have an extension which works, when I install it directly from the GitHub sources, but is broken, when I install it from the GNOME extensions page. For some reason the version on GNOME extensions is newer than the one on GitHub.
Since...I have an extension which works, when I install it directly from the GitHub sources, but is broken, when I install it from the GNOME extensions page. For some reason the version on GNOME extensions is newer than the one on GitHub.
Since extensions are automatically upgraded to the latest version on the GNOME extensions page, I always end up with a broken extension after a login.
It would be great, if there is an option to disable automatic extension updates. Either individually for each extension or globally for all.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2512Segfault when running `pack -o non_existent_dir`2020-03-28T18:25:20ZAndy HolmesSegfault when running `pack -o non_existent_dir`Pretty self-explanitory; running `gnome-extensions pack -o` for an output dir that doesn't exist segfaults in the error callback.
Sorry, I'm not sure if this is the canonical repository for the tool or if it's now a part of gnome-shell....Pretty self-explanitory; running `gnome-extensions pack -o` for an output dir that doesn't exist segfaults in the error callback.
Sorry, I'm not sure if this is the canonical repository for the tool or if it's now a part of gnome-shell.
```c
Thread 1 "gnome-extension" received signal SIGSEGV, Segmentation fault.
0x000055555555c180 in on_error (compressor=<optimized out>, error=<optimized out>, data=0x0) at ../src/extensions-tool/command-pack.c:268
268 *((GError **)data) = g_error_copy (error);
Missing separate debuginfos, use: dnf debuginfo-install gvfs-client-1.42.2-1.fc31.x86_64 pcre2-10.34-5.fc31.x86_64
(gdb) bt
#0 0x000055555555c180 in on_error (compressor=<optimized out>, error=<optimized out>, data=0x0) at ../src/extensions-tool/command-pack.c:268
#1 0x00007ffff7929aa8 in ffi_call_unix64 () at ../src/x86/unix64.S:76
#2 0x00007ffff79292a4 in ffi_call (cif=cif@entry=0x7fffffffcb90, fn=fn@entry=0x55555555c170 <on_error>, rvalue=<optimized out>, avalue=avalue@entry=0x7fffffffcae0)
at ../src/x86/ffi64.c:525
#6 0x00007ffff7d9e3ae in <emit signal ??? on instance 0x5555555a8850 [AutoarCompressor]>
(instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=<optimized out>) at ../gobject/gsignal.c:3397
#3 0x00007ffff7d8224d in g_cclosure_marshal_generic
(closure=closure@entry=0x5555555a81f0, return_gvalue=return_gvalue@entry=0x0, n_param_values=n_param_values@entry=2, param_values=param_values@entry=0x7fffffffcdb0, invocation_hint=invocation_hint@entry=0x7fffffffcd30, marshal_data=marshal_data@entry=0x0) at ../gobject/gclosure.c:1500
#4 0x00007ffff7d81742 in g_closure_invoke (closure=0x5555555a81f0, return_value=0x0, n_param_values=2, param_values=0x7fffffffcdb0, invocation_hint=0x7fffffffcd30)
at ../gobject/gclosure.c:810
#5 0x00007ffff7d95604 in signal_emit_unlocked_R
(node=node@entry=0x5555555a6f20, detail=detail@entry=0, instance=instance@entry=0x5555555a8850, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffffffcdb0) at ../gobject/gsignal.c:3641
#7 0x00007ffff7c3470f in autoar_common_g_signal_emit (instance=0x5555555a8850, in_thread=0, signal_id=34, detail=0) at gnome-autoar/autoar-private.c:204
#8 0x00007ffff7c35aff in autoar_compressor_signal_error (self=0x5555555a8850 [AutoarCompressor]) at gnome-autoar/autoar-compressor.c:673
#9 0x00007ffff7c37ce6 in autoar_compressor_run (self=0x5555555a8850 [AutoarCompressor]) at gnome-autoar/autoar-compressor.c:1561
#10 0x00007ffff7c37d9c in autoar_compressor_start (self=0x5555555a8850 [AutoarCompressor], cancellable=0x0) at gnome-autoar/autoar-compressor.c:1589
#11 0x000055555555d0e6 in extension_pack_compress (error=0x7fffffffd2c8, overwrite=0, outdir=<optimized out>, pack=0x555555574700) at ../src/extensions-tool/command-pack.c:313
#12 pack_extension
(gettext_domain=<optimized out>, podir=<optimized out>, schemas=<optimized out>, extra_sources=<optimized out>, force=0, dstdir=<optimized out>, srcdir=0x555555573da0 "working-extension@test") at ../src/extensions-tool/command-pack.c:422
#13 handle_pack (argc=<optimized out>, argv=<optimized out>, do_help=0) at ../src/extensions-tool/command-pack.c:513
#14 0x00007ffff7a421a3 in __libc_start_main () at /lib64/libc.so.6
#15 0x0000555555559b5e in _start () at /usr/include/glib-2.0/glib/glib-autocleanups.h:28
```https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2513There is no notice that Gnome Shell must be restarted after gnome-extensions ...2022-10-11T17:40:17ZFeldworThere is no notice that Gnome Shell must be restarted after gnome-extensions install.I tried to install some extensions in a multiple ways as the examples below shows.
Via direct online link.
```
gnome-extensions install https://extensions.gnome.org/extension-data/extensionsabteil.org.v10.shell-extension.zip
```
And th...I tried to install some extensions in a multiple ways as the examples below shows.
Via direct online link.
```
gnome-extensions install https://extensions.gnome.org/extension-data/extensionsabteil.org.v10.shell-extension.zip
```
And the offline way.
```
vaidas@vaidas-SATELLITE-L855:~/Downloads$ gnome-extensions install extensionsabteil.org.v10.shell-extension.zip
```
Everything is alright, except that for the newly installed extensions to show up in the `gnome-extensions list` the whole gnome-shell must be restarted via **ALT+F2 and R**.
The same goes for `gnome-extensions enable` - the gnome-shell must be restarted for the extension to be enabled/take effect on gnome-shell for the first time.
Also `gnome-extensions info` and `gnome-extensions show` does not show any information after installation, if you do not restart gnome-shell.
However `gnome-extensions disable` and `gnome-extensions uninstall` seems to work flawlessly, since they are always used after gnome-shell restart.