-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 15 Jun 2021 01:18:26 +0200 Source: gnome-shell-extension-appindicator Built-For-Profiles: noudeb Architecture: source Version: 40-1 Distribution: experimental Urgency: medium Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org> Changed-By: Marco Trevisan (Treviño) <marco@ubuntu.com> Changes: gnome-shell-extension-appindicator (40-1) experimental; urgency=medium . [ Marco Trevisan (Treviño) ] * New upstream release: - statusNotifierWatcher: Emit StatusNotifierHostRegistered (and Unregistered) signals. Other signals we were missing for long time, the specs includes these signals and they should be emitted when the watcher appears/disappears So do this, although it seems that Qt apps are still ignoring it. - indicatorStatusIcon: add polyfill for versionCheck in GNOME 40 - iconCache: Do not dispose the icon when clearing the cache. The icon can be a property of the Gio.EmblemedIcon and we should not dispose it as its parent doesn't support handling the child removal - metadata: Remove 40.beta as supported given we support 40 already. - promiseUtils: Promptly remove a source if was already cancelled - promiseUtils: Disconnect cancellable when the promise is resolved. In CancellablePromise we were connecting to the cancellable in order to monitor its cancellation, however we never disconnected from it and this was causing gjs to keep a reference on the promise itself, being the scope of the cancellable callback, and thus never garbaging collecting both the promise and its children (such as GSources). So, connect earlier to the signal and once we've resolved the promise, disconnect form the cancellable. - promiseUtils: Disconnect cancellation signal after resolving or rejecting. As per the previous commit we do disconnect from cancellation, but this happens too early so the cancellation event isn't ever tracked. We need in fact to handle it after that the promise is resolved or rejected. In the rejected case, we need to be extra careful though, as in case the cancellation happens as per cancellation's ::cancelled signal callback we need to do this in the next idle cycle or we'll deadlock. - prefs: Use es6 class and support Gtk4. GNOME 40 requires it - appIndicator: Do not lower opacity on versions after GNOME 40. There's no such effect upstream anymore so we don't want to switch that - appIndicator: Also toggle desaturate effect on mouse hover - settingsManager: Move gsettings initializtion to SettingsManager. Quite simple class for now but it avoids us to initialize a new gsettings instance for each indicator - appIndicator: Track hover status using native StWidget's hover property - IndicatorStatusIcon: Bind hover property with child IconActor. Whatever happens during hover on the whole indicator (including label) should affect also the icon, so we can just bind the hover property - appIndicator: Use more consistent names for settings updates - appIndicator: Cleanup emission of icon signal on status changes. We were handling this already in a common place, so let's move there - appIndicator: Get and expose the accessibility name. Some indicators (such as the Ayatana appindicator based) may include accessible descriptions so read and expose them if any or fallback with the indicator title otherwise. - appIndicator: Do not reload icons when updating the effects applied to it. Those are just effects that are not dependent on the icon content, so we can just update the icon without having check the effects all the times. - trayIconsManager: Move handling of legacy tray icons into a nicer class. Also move more into the wrapper AppIndicatorsIndicatorTrayIcon, and use Shell.TrayManager's unmanage_screen() in newer versions of the shell instead of relying on the ugly (and unreliable) tray unset + garbage collector invocation. - indicatorStatusIcon: Use the accessible name or WM class for a11y. We wrongly passed the indicator unique id as the accessible name to the shell for ages, we must instead use something that the screen readers may use for that. So, on appindicators we can use the exposed accessible name while for tray icons we can try use the wm class, even if it could be very generic - indicatorStatusIcon: Do not create a menu for tray icons - util: Wait for display opened only on X11 setup. This is actually only relevant for wayland sessions with Xwayland, as it may lead to opening the X11 display with some delay. But let's keep it to be a bit more conservative, and unblock the case for setups with no-x11 at all. - appIndicator: Use custom theme icon based on Shell one as default theme. Especially under wayland we should avoid to get the theme from the default gtk one as it may be always unset, as it depends on the Gdk Screen that is undefined in such scenario. So add an helper function to create a new Gtk theme using the shell's gtk icon theme and try to use it when no default gtk theme is available. We could probably do this in all the cases, but for now let's keep X11 environment as it is. * debian/gbp.conf: Do not use patch numbers * debian/patches: Refresh * debian/control: Add full support to gnome-shell 40 * debian/control: Update extension description * debian/patches: Use meson based build system * debian/control: Build depend on jq and meson * debian/rules: Do not install compiled schemas * debian/control: Add suggestions on extension prefs and libappindicator * debian/upstream/metadata: Add upstream references * debian/control: Use dh-sequence-gnome. In this way we also get for free ubuntu-specific tools such as dh-translations without having to do an ubuntu-specific fork . [ Fini Jastrow ] * Add icon opacity, size, position and other effects settings. The icons can be very colorful. Some people might not like it and older icons do not blend too well with newer monochrome ones. Add settings to configure multiple values of the icons and in particular: - Icons position in the panel - Icon size - Opacity - Desaturation - Brightness - Contrast As per this a new preference dialog is provided to configure such values * appIndicator: Fix resizing pixmap icons Icons created from pixmaps can not be resized (properly). When we create a icon from a pixmap we actually crate the icon in the native size. For example if the smallest available pixmap is 22 px the icon will also be 22 px, regardless of requested icon size. This is ok if the pixmap is by chance the requested size. But this is not always the case, especiually if the icon size is user selectable. So after creating the pixmap image we tell it how big it shall be. . [ jingi_jeong ] * feature: Add topicons-plus extension logic. To add support to legacy tray, merge topicons-plus extension logic. Create topicons.js file and connect with original appindicator code. Checksums-Sha1: e29e4bd74ddfc7b273c7d44dd16e8448901c319b 2370 gnome-shell-extension-appindicator_40-1.dsc 8d439fff311af263589bb6289d49f6a3b8373334 48664 gnome-shell-extension-appindicator_40.orig.tar.gz 2b281f24cad42b203a8619e4520b9dfd56bcca70 12200 gnome-shell-extension-appindicator_40-1.debian.tar.xz abe15758c5595433455cde22344b9c60b4811dae 12217 gnome-shell-extension-appindicator_40-1_source.buildinfo Checksums-Sha256: ce7b0437179a366acef1adb6ea19cca2b4a91f4538a81e94426f95dd501f3312 2370 gnome-shell-extension-appindicator_40-1.dsc 7cbe6ad03b31ab61233215386841cd5530e2d9b54f5b4dfb79f75da77c8c5cd4 48664 gnome-shell-extension-appindicator_40.orig.tar.gz c442d065bc5b7fd4f6e24f2432284d1a64c47c651b5f9d0c2b440fa57c5dc5d8 12200 gnome-shell-extension-appindicator_40-1.debian.tar.xz 2320118633f813cb38b0613d5b8f8c592dd960a3f58d896045ac7aa89f2c363c 12217 gnome-shell-extension-appindicator_40-1_source.buildinfo Files: 4ee3166a77c749a5f2392d1da858f29a 2370 gnome optional gnome-shell-extension-appindicator_40-1.dsc 74b5f2a389e25349b519c1d73ef9c520 48664 gnome optional gnome-shell-extension-appindicator_40.orig.tar.gz c541b6af7edc0ba245d43fcca8fd0a15 12200 gnome optional gnome-shell-extension-appindicator_40-1.debian.tar.xz f7087a2f3444c00a617720a37f551f75 12217 gnome optional gnome-shell-extension-appindicator_40-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE1MUB2kjreXoIF1CTlEnC9QmWY18FAmDH49QACgkQlEnC9QmW Y19JAA/8D2VhRm4n3m2kOXwCafHj4T9hAGuiNDijOGnEufrqmlmjwC8ozVPkHA/Y fAa/Ryfnmi5GaoFqm+ipTupBh6P7OopxBNFEKnS0PNTU9uXDhmpJRQWZsSYcVdT/ ghJniLDfu3JVQ7tic93K0PJdS9iiRwfzs4cKMp4iOJr37HSi21pJRAeGMBobb5Gy 4OIVjCuISloFphQfJFnhjsI0Bxm10ktX17JLvTTof7/Ws8dXEK7a06DCyOAIWNOK Y4AxGycv+yPmapMpYodIvt0m3i0QB9wkm5Cp5aTizzTF1jdQF4wZ5vy6nT7mNrXN 7d+HhM+FClFKL1QwJjHLVCvOYk5UBdCwZ2vkElvyYEkwL/EgZaYBTuYOLH8tGLMG sTSVrMUPWwWOc7u8l7/m7+T9mxNJyzunh7HluznQjH/sE2S2MNE5joKZLm0ltnjf 1Mf54yOeht+pvFlO1BE4GI8DDX0lSv4ldQ1JYdiTdRbXtYoS0LlPeq/sBF9tY6tr ozvjIEXSxrLQn7dr8tUyiSrwoK9EsE4ZC3KaOuJyGIp4p8b0cNyDwb6/tDv76rss 96TG8/VH5qB1GN9vY0ypXyoX811A8+Xsjk99aLdL7RGT6H1oKNgMcQXQl2J0vSla ISvCj8IhDdysseydbxuMxNRWxG1VZE/wpmtlU/v1CWnpSTT/tLY= =3WHy -----END PGP SIGNATURE-----