[Bug 2067661] Re: Login Qr code text is not readable in the lockscreen when using a light theme
Oh, actually was just Noble, but my brain is not yet used to do
last_lts=${last_lts/jammy/noble} :)
** No longer affects: gnome-shell (Ubuntu Jammy)
** No longer affects: yaru-theme (Ubuntu Jammy)
** Also affects: gnome-shell (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: yaru-theme (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: yaru-theme (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: yaru-theme (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: gnome-shell (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: gnome-shell (Ubuntu Noble)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: yaru-theme (Ubuntu Noble)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Tags added: noble
** Tags added: oracular
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2067661
Title:
Login Qr code text is not readable in the lockscreen when using a
light theme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2067661/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2067661] Re: Login Qr code text is not readable in the lockscreen when using a light theme
Yaru side at https://github.com/ubuntu/yaru/pull/4090 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2067661 Title: Login Qr code text is not readable in the lockscreen when using a light theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2067661/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2067661] Re: Login Qr code text is not readable in the lockscreen when using a light theme
** Description changed: [ Impact ] When using the light theme the qr code dialog in the lockscreen is not visible: https://imgur.com/USKxSbl.png [ Test case ] 0. Using the default theme variant (any light color) 1. Configure authd to use a broker that supports web authentication 2. Lock the screen 3. Try to unlock the screen using a QrCode for authenticating [ Regression potential ] - Lockscreen dialog is not properly visible in GDM (at login phase) + Lockscreen dialog is not properly visible in GDM (at login phase), or it + may have wrong or not visible colors ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu) Status: New => In Progress ** Changed in: yaru-theme (Ubuntu Jammy) Status: New => In Progress ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Medium ** Changed in: yaru-theme (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: yaru-theme (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2067661 Title: Login Qr code text is not readable in the lockscreen when using a light theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2067661/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2067661] [NEW] Login Qr code text is not readable in the lockscreen when using a light theme
Public bug reported: [ Impact ] When using the light theme the qr code dialog in the lockscreen is not visible: https://imgur.com/USKxSbl.png [ Test case ] 0. Using the default theme variant (any light color) 1. Configure authd to use a broker that supports web authentication 2. Lock the screen 3. Try to unlock the screen using a QrCode for authenticating [ Regression potential ] Lockscreen dialog is not properly visible in GDM (at login phase) ** Affects: gnome-shell (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: gnome-shell (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2067661 Title: Login Qr code text is not readable in the lockscreen when using a light theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2067661/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2067610] [NEW] GNOME Shell qrcode generator may create invalid QR code images
Public bug reported: [ Impact ] When creating QR Code images for long(er) URIs we may end up creating qr codes whose size isn't matching the expected one and this may lead to a wrongly generated texture (and potential memory access errors). An example: https://i.imgur.com/x3P4dzQ.png [ Test case ] In order to test this from GNOME shell, many components have to be set up that are harder to check so this can be easily simulated using a simple test program that replicates what the shell does to generate the image: https://www.pastery.net/uyzeca/ 1. Download and run the test script: $ wget -O /tmp/shell-qrcode-tester.py https://www.pastery.net/uyzeca/raw 2. Run it with: $ python3 /tmp/shell-qrcode-tester.py 3. The qrcode should open in a new window and display correctly as https://imgur.com/dddTL6u.png (pointing to https://bugs.launchpad.net/ubuntu/+source/gnome-shell) [ Regression potential ] QrCodes are used only during web authentication that is not something that is generally exposed to users, but this may potentially lead to wrong or missing qr codes textures. ** Affects: gnome-shell (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Committed ** Affects: gnome-shell (Ubuntu Noble) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Committed ** Also affects: gnome-shell (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Noble) Status: New => Fix Committed ** Changed in: gnome-shell (Ubuntu Noble) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Noble) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2067610 Title: GNOME Shell qrcode generator may create invalid QR code images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2067610/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023572] Re: SRU gjs 1.72.4 to jammy
** Changed in: gjs (Ubuntu Jammy) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
** Changed in: gjs (Ubuntu Jammy) Status: Fix Released => Triaged ** Changed in: gjs (Ubuntu Jammy) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066315] [NEW] Users who upgraded to rejected SRU 1.72.4-0ubuntu0.22.04.1 aren't restored
Public bug reported: [ Impact ] Users who have upgraded to gjs 1.72.4-0ubuntu0.22.04.1 as part of the SRU process are not restored to 1.72.2 version. gjs: Installato: 1.72.4-0ubuntu0.22.04.1 Candidato: 1.72.4-0ubuntu0.22.04.1 Tabella versione: *** 1.72.4-0ubuntu0.22.04.1 100 100 /var/lib/dpkg/status 1.72.2-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 1.72.0-1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [ Test case ] Ensure that the test cases below will still pass: - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Memory leaks fixed as part of 1.72.4 (LP: #2012978) will be back. ** Affects: gjs (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Won't Fix ** Affects: gjs (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Changed in: gjs (Ubuntu) Status: Triaged => Won't Fix ** Also affects: gjs (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gjs (Ubuntu Jammy) Status: New => In Progress ** Changed in: gjs (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2066315 Title: Users who upgraded to rejected SRU 1.72.4-0ubuntu0.22.04.1 aren't restored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2066315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2058442] Re: FP fingerprints are not deleted when user is removed
Opened an upstream issue too. https://gitlab.gnome.org/GNOME/gnome- control-center/-/issues/3060 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #3060 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3060 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2058442 Title: FP fingerprints are not deleted when user is removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2058442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066288] Re: /usr/libexec/gsd-smartcard segfaults in → sync_initial_tokens_from_driver → watch_smartcards_from_module_async → on_modules_initialized:g_task_return_now → complete_in_idle_cb
** Summary changed: - /usr/libexec/gsd-smartcard:11:sync_initial_tokens_from_driver:watch_smartcards_from_module_async:on_modules_initialized:g_task_return_now:complete_in_idle_cb + /usr/libexec/gsd-smartcard segfaults in → sync_initial_tokens_from_driver → watch_smartcards_from_module_async → on_modules_initialized:g_task_return_now → complete_in_idle_cb ** Summary changed: - /usr/libexec/gsd-smartcard segfaults in → sync_initial_tokens_from_driver → watch_smartcards_from_module_async → on_modules_initialized:g_task_return_now → complete_in_idle_cb + /usr/libexec/gsd-smartcard segfaults in → sync_initial_tokens_from_driver → watch_smartcards_from_module_async → on_modules_initialized → g_task_return_now → complete_in_idle_cb -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2066288 Title: /usr/libexec/gsd-smartcard segfaults in → sync_initial_tokens_from_driver → watch_smartcards_from_module_async → on_modules_initialized → g_task_return_now → complete_in_idle_cb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2066288/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
gnome-shell-extension-appindicator: Installato: 58-1 Candidato: 57-1 Tabella versione: *** 58-1 500 500 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 57-2 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages The qt applications are properly showing the indicators menus when launched after the shell has been started. In case the app is launched before the shell and under X11 indicators aren't shown but this is is a qt issue as explained in #3. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065066] Re: gnome-shell crashes in meta_wayland_popup_grab_get_top_popup
❯ apt-cache policy libmutter-10-0 libmutter-10-0: Installato: 42.9-0ubuntu8 Candidato: 42.9-0ubuntu8 Tabella versione: *** 42.9-0ubuntu8 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu7.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 42.0-3ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages Test case didn't lead to a crash nor any popup issue has been noticed ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2065066 Title: gnome-shell crashes in meta_wayland_popup_grab_get_top_popup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2065066/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061153] Re: No login prompt or user list on login screen [JS ERROR: TypeError: this._button is undefined]
Elad, can you provide the log of journalctl -b0 /usr/bin/gnome-shell ? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2061153 Title: No login prompt or user list on login screen [JS ERROR: TypeError: this._button is undefined] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061153/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892456] Re: [MIR] malcontent
Please also include libpam-malcontent since that would allow to support session-max-usage time when logging in from gdm. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to malcontent in Ubuntu. https://bugs.launchpad.net/bugs/1892456 Title: [MIR] malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/malcontent/+bug/1892456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065070] Re: Keyboard accessibility dialogs not working
Was released to jammy as part of ubuntu/42.9-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2065070 Title: Keyboard accessibility dialogs not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2065070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065070] [NEW] Keyboard accessibility dialogs not working
Public bug reported: [ Impact ] Enabling a keyboard accessibility feature using the keyboard (like, e.g. keeping a modifier pressed for 8 secs, or pressing a modifier 5 times in a row) used to trigger a dialog in the shell to confirm the change. In GNOME 42 this is no longer the case. Upstream issue: https://gitlab.gnome.org/GNOME/mutter/-/issues/2306 [ Test case ] - Keep Shift pressed for 8 seconds - A shell dialog popin up showing: Slow Keys Turned On You just held down the Shift key for 8 seconds. This is the shortcut for the Slow Keys feature, which affects the way your keyboard works. Output of journalctl /usr/bin/gnome-shell Should not contain TypeError: Clutter.KeyboardA11yFlags is undefined [ Regression potential ] Mutter does not compile (this change only implies different includes) or introspection data is missing ** Affects: mutter (Ubuntu) Importance: Medium Status: Fix Released ** Affects: mutter (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell (Ubuntu) ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Status: New => In Progress ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Description changed: [ Impact ] Enabling a keyboard accessibility feature using the keyboard (like, e.g. keeping a modifier pressed for 8 secs, or pressing a modifier 5 times in a row) used to trigger a dialog in the shell to confirm the change. In GNOME 42 this is no longer the case. Upstream issue: https://gitlab.gnome.org/GNOME/mutter/-/issues/2306 [ Test case ] - Keep Shift pressed for 8 seconds - A shell dialog popin up showing: - Slow Keys Turned On + Slow Keys Turned On You just held down the Shift key for 8 seconds. This is the shortcut for the Slow Keys feature, which affects the way your keyboard works. - - Output of - journalctl /usr/bin/gnome-shell + Output of + journalctl /usr/bin/gnome-shell Should not contain - TypeError: Clutter.KeyboardA11yFlags is undefined + TypeError: Clutter.KeyboardA11yFlags is undefined + + [ Regression potential ] + + Mutter does not compile (this change only implies different includes) or + introspection data is missing ** Changed in: mutter (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2065070 Title: Keyboard accessibility dialogs not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2065070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2065066] [NEW] gnome-shell crashes in meta_wayland_popup_grab_get_top_popup
Public bug reported: [ Impact ] Upstream issue https://gitlab.gnome.org/GNOME/mutter/-/issues/2563 with various reproducers. Fixed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2940 #9 0x7f548a442476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #10 0x7f548a4287f3 in __GI_abort () at ./stdlib/abort.c:79 #11 0x7f548b70bb57 in g_assertion_message (domain=, file=, line=, func=0x7f548a9b3480 <__func__.0.lto_priv.120> "meta_wayland_popup_grab_get_top_popup", message=) at ../../../glib/gtestutils.c:3253 #12 0x7f548b76570f in g_assertion_message_expr (domain=domain@entry=0x7f548a98d6aa "libmutter", file=file@entry=0x7f548a9b2d20 "../src/wayland/meta-wayland-popup.c", line=line@entry=233, func=func@entry=0x7f548a9b3480 <__func__.0.lto_priv.120> "meta_wayland_popup_grab_get_top_popup", expr=expr@entry=0x7f548a9b2cf8 "!wl_list_empty (>all_popups)") at ../../../glib/gtestutils.c:3279 #13 0x7f548a9386f0 in meta_wayland_popup_grab_get_top_popup (grab=) at ../src/wayland/meta-wayland-popup.c:233 #14 meta_wayland_popup_grab_get_top_popup (grab=0x5602a0ec8f70) at ../src/wayland/meta-wayland-popup.c:229 #15 0x7f548a94c930 in meta_wayland_pointer_get_top_popup (pointer=) at ../src/wayland/meta-wayland-pointer.c:1348 #16 finish_popup_setup (xdg_popup=0x56029dfe48f0) at ../src/wayland/meta-wayland-xdg-shell.c:1086 #17 meta_wayland_xdg_popup_apply_state (surface_role=0x56029dfe48f0, pending=0x7f5470089630) at ../src/wayland/meta-wayland-xdg-shell.c:1184 #18 0x7f548a945bc5 in meta_wayland_surface_role_apply_state (pending=0x7f5470089630, surface_role=) at ../src/wayland/meta-wayland-surface.c:1935 #19 meta_wayland_surface_apply_state (surface=, state=) at ../src/wayland/meta-wayland-surface.c:873 #20 0x7f548a946fb7 in meta_wayland_surface_commit (surface=0x56029fb11a10) at ../src/wayland/meta-wayland-surface.c:1029 #21 wl_surface_commit (client=, resource=) at ../src/wayland/meta-wayland-surface.c:1187 #22 0x7f5489f5be2e in () at /lib/x86_64-linux-gnu/libffi.so.8 #23 0x7f5489f58493 in () at /lib/x86_64-linux-gnu/libffi.so.8 #24 0x7f548b636260 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0 #25 0x7f548b63a474 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0 #26 0x7f548b638eea in wl_event_loop_dispatch () at /lib/x86_64-linux-gnu/libwayland-server.so.0 #27 0x7f548a92b44b in wayland_event_source_dispatch (base=, callback=, data=) at ../src/wayland/meta-wayland.c:110 #28 0x7f548b742d3b in g_main_dispatch (context=0x56029df478f0) at ../../../glib/gmain.c:3419 #29 g_main_context_dispatch (context=0x56029df478f0) at ../../../glib/gmain.c:4137 #30 0x7f548b798258 in g_main_context_iterate.constprop.0 (context=0x56029df478f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4213 #31 0x7f548b7422b3 in g_main_loop_run (loop=0x5602a05cf790) at ../../../glib/gmain.c:4413 #32 0x7f548a8d0b69 in meta_context_run_main_loop (context=, error=0x7ffdd91f9ce8) at ../src/core/meta-context.c:437 #33 0x56029d1fff12 in () #34 0x7f548a429d90 in __libc_start_call_main (main=main@entry=0x56029d1ffa70, argc=argc@entry=1, argv=argv@entry=0x7ffdd91f9e88) at ../sysdeps/nptl/libc_start_call_main.h:58 #35 0x7f548a429e40 in __libc_start_main_impl (main=0x56029d1ffa70, argc=1, argv=0x7ffdd91f9e88, init=, fini=, rtld_fini=, stack_end=0x7ffdd91f9e78) at ../csu/libc-start.c:392 #36 0x56029d2001b5 in () [ Test case ] - Install gnome-console - Run and maximize it - Move the cursor all the way to the left and right clicking in two different locations. - GNOME SHell should not crash [ Regression potentials ] Popup menus may not be properly placed on screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 Uname: Linux 6.8.7-zabbly+ x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 7 15:42:35 2024 DisplayManager: gdm3 InstallationDate: Installed on 2010-07-10 (5050 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2020-06-14 (1422 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Medium Status: Won't Fix ** Affects: mutter (Ubuntu) Importance: Medium Status: Fix Released ** Affects: mutter (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Tags: amd64 apport-bug jammy third-party-packages wayland-session ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Jammy) Status: New =
[Bug 2019776] Re: If gnome-shell is started directly (instead of through gnome-session), it might deadlock with no output to the screen
** Also affects: gnome-shell (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2019776 Title: If gnome-shell is started directly (instead of through gnome-session), it might deadlock with no output to the screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2019776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2019776] Re: If gnome-shell is started directly (instead of through gnome-session), it might deadlock with no output to the screen
This is handled via https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/3293 ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2019776 Title: If gnome-shell is started directly (instead of through gnome-session), it might deadlock with no output to the screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2019776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
** Description changed: + [ Impact ] + In ubuntu jammy and previous releases, right clicking on appindicator icons brings up the menu below the appindicator with appropriate gnome theming. In ubuntu noble, right clicking on some appindicator icons (example: barrier) results in the menu appearing on the left side of the screen without proper theming. See attached image. + + [ Test case ] + + Note: this only tests the appindicator-side that may have lead to + "activating" the application, it's not something that will fix the + applications issues that is a QT bug. + + 1. Start a QT application with indicator +(after gnome-shell has started; e.g. clementine, barrier...) + 2. The applindicator menu with shell theme should appear + 3. No activation happens on the application (e.g. the window is not opened) + + [ Regression potential ] + + Mouse events aren't properly exposed to the indicators ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Fix Committed ** Also affects: gnome-shell (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: qtbase-opensource-src (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-appindicator (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039543] Re: Miss placed Hexchat icon when switching workspaces
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2039543 Title: Miss placed Hexchat icon when switching workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2039543/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039543] Re: Miss placed Hexchat icon when switching workspaces
** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2039543 Title: Miss placed Hexchat icon when switching workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2039543/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059818] Re: Regression: Jammy to Noble, set_label no longer functions
** Description changed: + [ Impact ] + In ubuntu jammy and previous releases, set_label can be used to set the text to display instead of an appindicator icon. In ubuntu noble set_label no longer functions at all. https://gjs-docs.gnome.org/appindicator301~0.1/appindicator3.indicator#method-set_label + + [ Test Case ] + + - Download the test indicator and its dependencies: + * wget https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js + * apt install gir1.2-appindicator3-0.1 + + - Run the test indicator: + gjs -m testTool.js + + - Ensure the indicator icon shows up (it has an ubuntu icon) + - Click on it and activate the "Set Label" item + - A random numeric label should show next to the icon + + [ Regression potential ] + + The icon is not visible anymore -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059818 Title: Regression: Jammy to Noble, set_label no longer functions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2059818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042844] Re: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow
** Description changed: + [ Impact ] + With several indicator icons (Chrome, Slack, 1Password) a GDBus.Error systemd error message appears with each iteration of a left-click of any impacted indicator icon prior to the icon's menu appearing. Ubuntu Mantic 23.10, gnome-shell 45.0-1ubuntu2, gnome-shell-extension- appindicator 57-1 Also reported upstream here: https://github.com/ubuntu/gnome-shell- extension-appindicator/issues/445 Nov 06 08:32:20 ubuntu-mantic gnome-shell[3927]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow - _promisify/proto[asyncFunc]/ Fix Committed ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: gnome-shell-extension-appindicator (Ubuntu Noble) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2042844 Title: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2042844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059818] Re: Regression: Jammy to Noble, set_label no longer functions
** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059818 Title: Regression: Jammy to Noble, set_label no longer functions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2059818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993054] Re: USB key eject does not eject
Handled as https://github.com/micheleg/dash-to-dock/pull/2200 ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Noble) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1993054 Title: USB key eject does not eject To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061985] Re: Other users are also highlighted although unselected
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Opinion ** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2061985 Title: Other users are also highlighted although unselected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061985/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2062178] Re: Disable location services in gnome-control-center
> Nightcolor uses geoclue which is disabled by default and I guess users will have to use the google option when the time comes ( not necessarily easy, but an option. ) We do not have location settings in systemsettings. Using google for example is an option but that requires admin access, while the g-c-c side controls whether applications have permit to access to geoclue -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2062178 Title: Disable location services in gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2062178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060659] Re: X11 fractional scaling support is missing in 46.0
fossfreedom, probably magpie should use a different schema name though and *always* conflict with mutter, no? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060659 Title: X11 fractional scaling support is missing in 46.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magpie/+bug/2060659/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2062178] Re: Disable location services in gnome-control-center
> Unfortunately, there does not appear to be any suitable replacement for our typical desktop and laptop users. When mozilla service is not used, GeoIP is used instead. It's not perfect (especially if using a VPN) but it's good enough to provide features such as automatic-timezone and night light. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2062178 Title: Disable location services in gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2062178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061985] Re: Other users are also highlighted although unselected
Well that's the focus ring, IIRC Is there also without yaru so it doesn't seem a downstream (only) bug (if any to me): https://imgur.com/N6E5R1q.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2061985 Title: Other users are also highlighted although unselected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061985/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060659] Re: X11 fractional scaling support is missing in 46.0
** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2060659 Title: X11 fractional scaling support is missing in 46.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060659/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2062078] [NEW] Mouse animations do not follow accent colors
Public bug reported: This is a regression from previous releases, the mouse animations do not follow the user-selected accent color The missing assets needs to be regenerated with this script: - https://gitlab.gnome.org/-/snippets/5549 Sources are: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/commits/master/mouse-and-touchpad/src/mouse-touchpad-v2.blend ** Affects: gnome-control-center (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2062078 Title: Mouse animations do not follow accent colors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2062078/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061729] Re: Ubuntu Dock icon highlight is practically invisible when a white or grey window is behind it
** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: yaru-theme (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2061729 Title: Ubuntu Dock icon highlight is practically invisible when a white or grey window is behind it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2061729/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060816] Re: App grid icon is Ubuntu logo, need to find override
FYI we're going to provide a way to override this by defining a new
gnome shell session (you can inherit the ubuntu one) and the icon should
be named `view-app-grid-${currentMode}-symbolic` e.g. `view-app-grid-
edubuntu-symbolic`, otherwise the default (view-app-grid-symbolic) will
be used
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => In Progress
** Changed in: yaru-theme (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock
in Ubuntu.
https://bugs.launchpad.net/bugs/2060816
Title:
App grid icon is Ubuntu logo, need to find override
To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/2060816/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061153] Re: No login prompt or user list on login screen [JS ERROR: TypeError: this._button is undefined]
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2061153 Title: No login prompt or user list on login screen [JS ERROR: TypeError: this._button is undefined] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061153/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-keyring (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061216] Re: Everything freezes when I alt+tab from a fullscreen application
It could be ibus-related Also try to get a backtrace following (the last part of) this: - https://wiki.gnome.org/Projects/GnomeShell/Debugging#Acquiring_a_backtrace_of_a_running_GNOME_Shell_in_automated_mode Then provide the logs -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2061216 Title: Everything freezes when I alt+tab from a fullscreen application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061216/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061153] Re: No login prompt after installing in HyperV
** Changed in: gnome-shell (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2061153 Title: No login prompt after installing in HyperV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061153/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061355] Re: fractional scaling does not work on X11
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2061355 Title: fractional scaling does not work on X11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2061355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
Sorry, I missed the previous comments. > Do I read the gnome-settings-daemon patches correctly, and this actually just entirely drops support for auth via NSS? So the regression potential is that if someone has set up auth via a custom system nss database, this *will* break login for them? Well, yes that's a regression potential that may indeed be mentioned, it's also something that we never supported though, since that required some extra setup in various places (write a gdm pam configuration, create the NSS database and configure pam-pkcs11/pam_sss). But indeed it could potentially affect someone who went through all this. However... The SSSD side of this (lp:1905790), if one had configured a NSS database in the canonical location, it will be migrated (using this tool https://github.com/3v1n0/nss-database-pem-exporter). So, it's quite a remote possibility but worth to mention in a clearer way (it was somewhat written already). > Unrelatedly, patches like smartcard-Use-autopointers.patch and smartcard-manager-Use-mutex-auto-lockers-when-convenient.patch are the sort of refactoring patches that we prefer not to see in SRUs. I don't think they're a blocker, but they make reviewing more difficult Let me know if I should drop them, one reason why they were added is that they were part of the upstream changes too, and so it made easier to ensure that we're both in the same line if problems may happen, making easier to backport patches in future if needed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
By default GDM switches to smartcard mode once one is plugged in, smartcard auth can be disabled at gdm level though, by changing the gsettings. sudo -u gdm env -u XDG_RUNTIME_DIR -u DISPLAY DCONF_PROFILE=gdm dbus-run-session \ gsettings set org.gnome.login-screen enable-smartcard-authentication false -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033688] Re: [mantic] gnome-shell fails to follow accent colours
** Description changed: - When accent colors are selected in gnome-control-center, gnome-shell - fails to follow with the exception of blue and orange. Screenshots - attached. + Impact + -- + When accent colors are selected in gnome-control-center, gnome-shell fails to follow with the exception of blue and orange. Screenshots attached. Test Case - 1. Open the Settings app 2. Switch to the Appearance page 3. Choose the Purple color 4. Click the quick settings area in the far right side of GNOME Shell's top bar 5. The highlights should be purple What Happens Instead The highlights are still orange - ProblemType: Bug - DistroRelease: Ubuntu 23.10 + Regression Potential + + Themes for default accent color or for high-contrast theme are not generated properly. + + + --- + + ProblemType: BugDistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 31 13:50:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-04 (180 days ago) InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230304) - RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1 - SourcePackage: gnome-shell + RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2033688 Title: [mantic] gnome-shell fails to follow accent colours To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2033688/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033688] Re: [mantic] gnome-shell fails to follow accent colours
** Changed in: gnome-shell (Ubuntu Mantic) Status: Triaged => Won't Fix ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu) Status: New => Triaged ** Changed in: yaru-theme (Ubuntu) Status: Triaged => In Progress ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2033688 Title: [mantic] gnome-shell fails to follow accent colours To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2033688/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2038783] [NEW] Exit code of locations mount script is not respecting error
Public bug reported: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js /foo/bar/baz echo $? An error should be shown and the return code should be 15 Doing instead gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js $HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2038783 Title: Exit code of locations mount script is not respecting error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2038783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2030959] Re: Cursor sometimes stutters after heavy shell animations in 42.9
** Changed in: mutter (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2030959 Title: Cursor sometimes stutters after heavy shell animations in 42.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Description changed: [ Impact ] the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated --- Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): - https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a + https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ - sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin + sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh - - sudo sssd-gdm-smartcard-pam-auth-tester.sh + - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh + - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh The script will generate some fake CA authority, issue some certificates, will install them in some software-based smartcards (using softhsm2) and test that they work properly to login with gdm-smartcard. Using `WAIT` environment variable set (to any value) will make it to restart gdm at each iteration so that an user can try to access, using the username that launched the script and the pin of 123456. [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
Andreas: - I've now added SSSD to the bug - I had not uploaded the remaining bits yet as I was waiting for SSSD to hit the queue first - GNOME settings daemon is also uploaded now to the queue - GDM will be uploaded soon by Jeremy The bug has now been updated to have a proper SRU template, with all the tests required to check all the 3 packages. ** Also affects: sssd (Ubuntu) Importance: Undecided Status: New ** Changed in: sssd (Ubuntu) Status: New => In Progress ** Changed in: sssd (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** No longer affects: gdm3 (Ubuntu Focal) ** No longer affects: gnome-settings-daemon (Ubuntu Focal) ** Also affects: gnome-settings-daemon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: sssd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Focal) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-settings-daemon (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: gnome-settings-daemon (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: sssd (Ubuntu Focal) Status: New => In Progress ** Changed in: sssd (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gdm3 (Ubuntu Focal) Status: New => In Progress ** Changed in: gnome-settings-daemon (Ubuntu Focal) Status: New => In Progress ** Changed in: sssd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Description changed: + [ Impact ] + the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. - ProblemType: Bug - DistroRelease: Ubuntu 18.04 + [ Test case ] + + 1. When in GDM, insert a smartcard + 2. The GDM interface should require for an user + 3. The user should be set (or empty may be provided, +depending on sssd configuration) + 4. The smartcard PIN should be requested and once introduce the +user must login. + + Note that this requires configuring sssd before, a simple local + configuration could require having sssd.conf filled with: + + ```ini + [sssd] + enable_files_domain = True + services = pam + + [certmap/implicit_files/$USER] + matchrule = .*YOUR CARD IDENTIFIER* + + [pam] + pam_cert_auth = True + ``` + + The UI authentication can also be simulated via pamtester: + + # Must be ran as user + sudo apt install pamtester + pamtester -v gdm-smartcard $USER authenticate + + Expected output is + + pamtester -v gdm-smartcard ubuntu authenticate + pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) + pamtester: performing operation - authenticate + PIN for Test Organization Sub Int Token: + pamtester: successfully authenticated + + [ Regression potential ] + + Smartcard authentication using custom methods using via a custom + configured system nss database may not work anymore. + + --- + + ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) - InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) - SourcePackage: gdm3 + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 ** Description changed: [ Impact ] the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, -depending on sssd configuration) + depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the -user must login. + user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated + --- + + Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): + https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a + + - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ + sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin + - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh + - sudo sssd-gdm-smartcard-pam-auth-tester.sh + + The script will generate some fake CA authority, issue some + certificates, will install them in some software-based smartcards (using + softhsm2) and test that they work properly to login with gdm-smartcard. + + Using `WAIT` environment variable set (to any value) will make it to + restart gdm at each iteration so that an user can try to access, using + the username that launched the script and the pin of 123456. + [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4
[Bug 2034121] Re: Support goodix fingerprint [27c6:633C]
** Changed in: libfprint (Ubuntu) Status: New => Fix Released ** Also affects: libfprint (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2034121 Title: Support goodix fingerprint [27c6:633C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2018672] Re: Gnome 44: GDM background configurable with gsettings
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: gnome-shell (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2018672 Title: Gnome 44: GDM background configurable with gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031406] Re: [MIR] libei
> #7 Help upstream to resolve the s390x endianess issues, so we can re-enable > all tests https://gitlab.freedesktop.org/libinput/libei/-/issues/41 I've done some analisys there of the remaining issue, we should be green soon! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2031406 Title: [MIR] libei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libei/+bug/2031406/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2032357] Re: /usr/bin/gjs-console aborts @ pthread_kill -> raise:abort -> mem_error -> slab_allocator_free_chunk
*** This bug is a duplicate of bug 2032361 *** https://bugs.launchpad.net/bugs/2032361 ** Summary changed: - /usr/bin/gjs-console:6:pthread_kill:raise:abort:mem_error:slab_allocator_free_chunk + /usr/bin/gjs-console aborts @ pthread_kill -> raise:abort -> mem_error -> slab_allocator_free_chunk ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Also affects: gjs (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu Jammy) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 2032361 /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2032357 Title: /usr/bin/gjs-console aborts @ pthread_kill -> raise:abort -> mem_error -> slab_allocator_free_chunk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2032357/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2032361] Re: /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload
** Summary changed: - /usr/bin/gjs-console:6:mem_error:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:thread_memory_magazine2_unload + /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Also affects: gjs (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2032361 Title: /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2032361/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2032370] Re: /usr/bin/gjs-console:6:mem_error:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:private_thread_memory_cleanup
*** This bug is a duplicate of bug 2032361 *** https://bugs.launchpad.net/bugs/2032361 ** This bug has been marked a duplicate of bug 2032357 /usr/bin/gjs-console aborts @ pthread_kill -> raise:abort -> mem_error -> slab_allocator_free_chunk ** This bug is no longer a duplicate of bug 2032357 /usr/bin/gjs-console aborts @ pthread_kill -> raise:abort -> mem_error -> slab_allocator_free_chunk ** This bug has been marked a duplicate of bug 2032361 /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2032370 Title: /usr/bin/gjs- console:6:mem_error:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:private_thread_memory_cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2032370/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2032372] Re: /usr/bin/gjs-console:11:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:thread_memory_magazine2_unload:g_slice_free1
*** This bug is a duplicate of bug 2032361 *** https://bugs.launchpad.net/bugs/2032361 ** This bug has been marked a duplicate of bug 2032357 /usr/bin/gjs-console aborts @ pthread_kill -> raise:abort -> mem_error -> slab_allocator_free_chunk ** This bug is no longer a duplicate of bug 2032357 /usr/bin/gjs-console aborts @ pthread_kill -> raise:abort -> mem_error -> slab_allocator_free_chunk ** This bug has been marked a duplicate of bug 2032361 /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2032372 Title: /usr/bin/gjs- console:11:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:thread_memory_magazine2_unload:g_slice_free1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2032372/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031872] Re: Support Elan fp device [04F3:0C99]
** Changed in: libfprint (Ubuntu) Status: New => Fix Released ** Also affects: libfprint (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2031872 Title: Support Elan fp device [04F3:0C99] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2031872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942204] Re: gjs-console assert failure: double free or corruption (out)
*** This bug is a duplicate of bug 2027986 *** https://bugs.launchpad.net/bugs/2027986 ** Changed in: gjs (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu) Status: New => Fix Released ** This bug has been marked a duplicate of bug 2027986 gjs-console running Extensions Manager crashes with free(): invalid pointer -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1942204 Title: gjs-console assert failure: double free or corruption (out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1942204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1981678] Re: /usr/bin/gjs-console:double free or corruption (out)
*** This bug is a duplicate of bug 2027986 *** https://bugs.launchpad.net/bugs/2027986 ** This bug is no longer a duplicate of bug 1942204 gjs-console assert failure: double free or corruption (out) ** This bug has been marked a duplicate of bug 2027986 gjs-console running Extensions Manager crashes with free(): invalid pointer -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1981678 Title: /usr/bin/gjs-console:double free or corruption (out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1981678/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027986] Re: gjs-console running Extensions Manager crashes with free(): invalid pointer
Tested new version, it works without errors ❯ apt-cache policy libgtk-4-1 libgtk-4-1: Installed: 4.6.9+ds-0ubuntu0.22.04.1 Candidate: 4.6.9+ds-0ubuntu0.22.04.1 Version table: *** 4.6.9+ds-0ubuntu0.22.04.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.6.6+ds-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 4.6.2+ds-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages Before upgrading: ❯ gjs -m /tmp/error.js (gjs:8879): Gjs-CRITICAL **: 10:47:25.041: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. (gjs:8879): Gjs-CRITICAL **: 10:47:25.041: The offending callback was ScaleFormatValueFunc(). == Stack trace for context 0x5634d50d9180 == (gjs:8879): Pango-WARNING **: 10:47:25.041: Invalid UTF-8 string passed to pango_layout_set_text() free(): invalid pointer [1]8879 IOT instruction (core dumped) gjs -m /tmp/error.js marco-ThinkPad-X1-Carbon-7th ~ 8sSIGIOT(6) 10:47:27 ❯ apt-cache policy libgtk-4-1 libgtk-4-1: Installed: 4.6.6+ds-0ubuntu1 Candidate: 4.6.6+ds-0ubuntu1 Version table: 4.6.9+ds-0ubuntu0.22.04.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages *** 4.6.6+ds-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 4.6.2+ds-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2027986 Title: gjs-console running Extensions Manager crashes with free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2027986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028005] [NEW] Update gtk4 to 4.6.9
Public bug reported: Impact -- There is a new point release in the stable GTK 4.6 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.9/NEWS Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- sudo apt install gnome-shell-extensions-prefs gnome-shell-extensions-prefs GNOME Shell extensions can be configured and managed, the program can run without crashing both during runtime and shutdown. What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. The other gtk4 apps installed by default in Ubuntu are gnome-chess and gnome-shell-extension-prefs. gtk4 is part of core GNOME and is in my latest proposed update to the microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/42 gtk4 has extensive build tests and autopkgtests. ** Affects: gtk4 (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: gtk4 (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gtk4 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu Jammy) Status: New => In Progress ** Changed in: gtk4 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gtk4 (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2028005 Title: Update gtk4 to 4.6.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2028005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027986] Re: gjs-console running Extensions Manager crashes with free(): invalid pointer
** Description changed:
- Some JS traces I see are:
+ [ Impact ]
+
+ gnome-shell-extensions-prefs may crash during shutdown because of wrong
+ memory access:
Jul 14 18:52:30 zerocool gjs[114030]: Attempting to run a JS callback during
garbage collection. This is most likely caused by destroying a Clutter actor or
GTK widget with ::destroy signal connected, or using the destroy(), dispose(),
or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul 14 18:52:30 zerocool gjs[114030]: The offending callback was
ScaleFormatValueFunc().
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: == Stack trace
for context 0x55d05b7f6170 ==
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #0 55d05b87d5b8
i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (3d87eaadaab0 @
257)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #1 55d05b87d510
i resource:///org/gnome/Shell/Extensions/js/main.js:22 (3d87eaada4c0 @ 97)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #2 55d05b87d478
i resource:///org/gnome/gjs/modules/script/package.js:206 (3d87eaac82e0 @ 45)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #3 55d05b87d3f0
i resource:///org/gnome/gjs/modules/script/package.js:190 (3d87eaac8290 @ 37)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #4 55d05b87d360
i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (3d87eaac80b0 @ 52)
Jul 14 18:52:30 zerocool gjs[114030]: Invalid UTF-8 string passed to
pango_layout_set_text()
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: free(): invalid
pointer
- ---
+
+ [ Test case ]
+
+ 1. Add this script to a file (i.e. /tmp/test-gtk.js)
+
+ import Gtk from 'gi://Gtk?version=4.0';
+ const app = new Gtk.Application();
+ app.connect('activate', () => {
+ const scale = new Gtk.Scale({drawValue: true});
+ scale.set_format_value_func(() => '');
+ new Gtk.Window({application: app, child: scale}).present();
+ });
+ app.run([]);
+
+
+ 2. Run it via:
+
+ gjs -m /tmp/test-gtk.js
+
+ A new window should snow
+
+ 3. Close the window, it should exit normally with no errors.
+
+
+ [ Regression potential ]
+
+ None known, the fix
+ (https://gitlab.gnome.org/GNOME/gtk/-/commit/8b76cc841) only ensures
+ that we're using the adjustment property if really was used.
+
+
+ ---
+
+ Other triggers:
7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]:
unable to update icon for software-update-available
7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]:
unable to update icon for livepatch
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Attempting to run a JS
callback during garbage collection. This is most likely caused by destroying a
Clutter actor or GTK widget with ::destroy signal connected, or using the
destroy(), dispose(), or remove() vfuncs. Because it would crash the
application, it has been blocked.
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: The offending callback was
ScaleFormatValueFunc().
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: ==
Stack trace for context 0x55674f538170 ==
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #0
55674f5c27f8 i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186
(330fd64daab0 @ 257)
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #1
55674f5c2750 i resource:///org/gnome/Shell/Extensions/js/main.js:22
(330fd64da4c0 @ 97)
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #2
55674f5c26b8 i resource:///org/gnome/gjs/modules/script/package.js:206
(330fd64c82e0 @ 45)
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #3
55674f5c2630 i resource:///org/gnome/gjs/modules/script/package.js:190
(330fd64c8290 @ 37)
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #4
55674f5c25a0 i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1
(330fd64c80b0 @ 52)
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Invalid UTF-8 string passed
to pango_layout_set_text()
- 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]:
free(): invalid pointer
+ 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]:
free(): invalid pointer
---
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gjs. This problem was most recently seen with package version 1.74.0-1, the
problem page at
https://errors.ubuntu.com/problem/2c4ff471793184d6a5b3a47cee9dcbe517920a3a
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
--
You received this bug notification because you are a member of Ubuntu
[Bug 2027986] Re: gjs-console running Extensions Manager crashes with free(): invalid pointer
As per further analysis it seems that this bug has always been there in 42 series, however the traces are normally caused by some extensions settings, for example: - https://github.com/micheleg/dash-to-dock/issues/1743 - https://github.com/home-sweet-gnome/dash-to-panel/issues/1783 While something like this had already been fixed for some cases in GLib (included in 1.72, part of gnome 42 and so jammy): https://gitlab.gnome.org/GNOME/gjs/-/issues/445 The has been found in gtk, though. And fixed by https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5061 ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1743 https://github.com/micheleg/dash-to-dock/issues/1743 ** Bug watch added: github.com/home-sweet-gnome/dash-to-panel/issues #1783 https://github.com/home-sweet-gnome/dash-to-panel/issues/1783 ** Bug watch added: gitlab.gnome.org/GNOME/gjs/-/issues #445 https://gitlab.gnome.org/GNOME/gjs/-/issues/445 ** Changed in: gtk4 (Ubuntu) Status: Triaged => Fix Released ** Changed in: gtk4 (Ubuntu) Importance: Undecided => High ** Changed in: gtk4 (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2027986 Title: gjs-console running Extensions Manager crashes with free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2027986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027986] Re: gjs-console running Extensions Manager crashes with free(): invalid pointer
** Changed in: gjs (Ubuntu) Status: Triaged => Won't Fix ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu) Status: New => Triaged ** Also affects: gjs (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gtk4 (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: gjs (Ubuntu Jammy) ** Changed in: gtk4 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2027986 Title: gjs-console running Extensions Manager crashes with free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2027986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027986] Re: gjs-console running Extensions Manager crashes with free(): invalid pointer
** Changed in: gjs (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2027986 Title: gjs-console running Extensions Manager crashes with free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2027986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gnome-shell (Ubuntu Jammy) Status: Confirmed => Won't Fix ** Changed in: gjs (Ubuntu Jammy) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1991709 Title: gnome-shell memory leak (when Ubuntu AppIndicators is enabled) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1991709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027986] Re: /usr/bin/gjs-console:free(): invalid pointer
This doesn't seems something easy to understand, because `org.gnome.Shell.Extensions` could be loading *ANY* kind of javascript code that is imported from gnome extensions. Some of this code is definitely setting a wrong pango text, and gjs thus doesn't free it properly. It could be also an issue due to wrong JS-string -> C-string mapping in gjs but it's very hard to reproduce for me. ** Description changed: + Some JS traces I see are: + + + Jul 14 18:52:30 zerocool gjs[114030]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. + Jul 14 18:52:30 zerocool gjs[114030]: The offending callback was ScaleFormatValueFunc(). + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: == Stack trace for context 0x55d05b7f6170 == + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #0 55d05b87d5b8 i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (3d87eaadaab0 @ 257) + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #1 55d05b87d510 i resource:///org/gnome/Shell/Extensions/js/main.js:22 (3d87eaada4c0 @ 97) + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #2 55d05b87d478 i resource:///org/gnome/gjs/modules/script/package.js:206 (3d87eaac82e0 @ 45) + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #3 55d05b87d3f0 i resource:///org/gnome/gjs/modules/script/package.js:190 (3d87eaac8290 @ 37) + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #4 55d05b87d360 i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (3d87eaac80b0 @ 52) + Jul 14 18:52:30 zerocool gjs[114030]: Invalid UTF-8 string passed to pango_layout_set_text() + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: free(): invalid pointer + + --- + The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.74.0-1, the problem page at https://errors.ubuntu.com/problem/2c4ff471793184d6a5b3a47cee9dcbe517920a3a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Summary changed: - /usr/bin/gjs-console:free(): invalid pointer + gjs-console crashes with free(): invalid pointer ** Description changed: Some JS traces I see are: - Jul 14 18:52:30 zerocool gjs[114030]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Jul 14 18:52:30 zerocool gjs[114030]: The offending callback was ScaleFormatValueFunc(). Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: == Stack trace for context 0x55d05b7f6170 == Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #0 55d05b87d5b8 i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (3d87eaadaab0 @ 257) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #1 55d05b87d510 i resource:///org/gnome/Shell/Extensions/js/main.js:22 (3d87eaada4c0 @ 97) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #2 55d05b87d478 i resource:///org/gnome/gjs/modules/script/package.js:206 (3d87eaac82e0 @ 45) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #3 55d05b87d3f0 i resource:///org/gnome/gjs/modules/script/package.js:190 (3d87eaac8290 @ 37) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #4 55d05b87d360 i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (3d87eaac80b0 @ 52) Jul 14 18:52:30 zerocool gjs[114030]: Invalid UTF-8 string passed to pango_layout_set_text() Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: free(): invalid pointer --- + 7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]: unable to update icon for software-update-available + 7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]: unable to update icon for livepatch + 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. + 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: The offending callback was ScaleFormatValueFunc(). + 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: == Stack trace for context 0x55674f538170 == + 7月 17
[Bug 2019477] Re: Sliders temporary hide when hovered
Sliders are properly rendered also when hovered. ❯ apt-cache policy yaru-theme-gtk yaru-theme-gtk: Installed: 22.04.5 Candidate: 22.04.5 Version table: *** 22.04.5 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status 22.04.4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages ** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => yaru- theme (Ubuntu) ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2019477 Title: Sliders temporary hide when hovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2019477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
❯ apt-cache policy gjs
gjs:
Installed: 1.72.4-0ubuntu0.22.04.1
Candidate: 1.72.4-0ubuntu0.22.04.1
Version table:
*** 1.72.4-0ubuntu0.22.04.1 400
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
1.72.2-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
1.72.0-1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
No variant leak (the other detected is a mozjs issue, but likely a wrong
valgrind detection):
❯ env G_SLICE=always-malloc valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
==356489== Memcheck, a memory error detector
==356489== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==356489== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==356489== Command: gjs -c const\ GLib=imports.gi['GLib'];function\
leak(){const\ l=GLib.Variant['new']('i',1)};leak();imports.system.gc();
==356489==
==356489== Warning: set address range perms: large range [0x2204b34b7000,
0x2205330b7000) (noaccess)
==356489== Warning: set address range perms: large range [0x2204b34b7000,
0x2205330b7000) (noaccess)
==356489==
==356489== HEAP SUMMARY:
==356489== in use at exit: 193,115 bytes in 2,445 blocks
==356489== total heap usage: 19,931 allocs, 17,486 frees, 9,251,399 bytes
allocated
==356489==
==356489== 352 bytes in 1 blocks are possibly lost in loss record 1,965 of 2,008
==356489==at 0x484DA83: calloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==356489==by 0x40147D9: calloc (rtld-malloc.h:44)
==356489==by 0x40147D9: allocate_dtv (dl-tls.c:375)
==356489==by 0x40147D9: _dl_allocate_tls (dl-tls.c:634)
==356489==by 0x5008834: allocate_stack (allocatestack.c:430)
==356489==by 0x5008834: pthread_create@@GLIBC_2.34 (pthread_create.c:647)
==356489==by 0x5A36794: mozilla::TimeStamp::ComputeProcessUptime() (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==356489==by 0x5A36856: mozilla::TimeStamp::ProcessCreation(bool*) (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==356489==by 0x5444A7F: JS::detail::InitWithFailureDiagnostic(bool) (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==356489==by 0x48A2363: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0)
==356489==by 0x400647D: call_init.part.0 (dl-init.c:70)
==356489==by 0x4006567: call_init (dl-init.c:33)
==356489==by 0x4006567: _dl_init (dl-init.c:117)
==356489==by 0x40202E9: ??? (in
/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2)
==356489==by 0x2: ???
==356489==by 0x1FFEFFFBBE: ???
==356489==
==356489== LEAK SUMMARY:
==356489==definitely lost: 0 bytes in 0 blocks
==356489==indirectly lost: 0 bytes in 0 blocks
==356489== possibly lost: 352 bytes in 1 blocks
==356489==still reachable: 77,254 bytes in 965 blocks
==356489== suppressed: 97,829 bytes in 1,292 blocks
==356489== Reachable blocks (those to which a pointer was found) are not shown.
==356489== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==356489==
==356489== For lists of detected and suppressed errors, rerun with: -s
==356489== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)
-
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
==357068== Warning: set address range perms: large range [0xbabd0a0c000,
0xbac5060c000) (noaccess)
==357068==
==357068== HEAP SUMMARY:
==357068== in use at exit: 231,169 bytes in 3,087 blocks
==357068== total heap usage: 155,879 allocs, 152,792 frees, 28,688,797 bytes
allocated
==357068==
==357068== 0 bytes in 1 blocks are definitely lost in loss record 1 of 2,526
==357068==at 0x4848899: malloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==357068==by 0x4005A22: malloc (rtld-malloc.h:56)
==357068==by 0x4005A22: _dl_find_object_update (dl-find_object.c:791)
==357068==by 0x400ECCF: dl_open_worker_begin (dl-open.c:735)
==357068==by 0x4EC0C27: _dl_catch_exception (dl-error-skeleton.c:208)
==357068==by 0x400DF99: dl_open_worker (dl-open.c:782)
==357068==by 0x4EC0C27: _dl_catch_exception (dl-error-skeleton.c:208)
==357068==by 0x400E34D: _dl_open (dl-open.c:883)
==357068==by 0x4DDC6BB: dlopen_doit (dlopen.c:56)
==357068==by 0x4EC0C27: _dl_catch_exception (dl-error-skeleton.c:208)
==357068==by 0x4EC0CF2: _dl_catch_error (dl-error-skeleton.c:227)
==357068==by 0x4DDC1AD: _dlerror_run (dlerror.c:138)
==357068==by 0x4DDC747: dlopen_implementation (dlopen.c:71)
==357068==by 0x4DDC747: dlopen@@GLIBC_2.34
[Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102
Removing `block-proposed-jammy` given that there's no 1.74 in jammy proposed and otherwise we'd block the landing of 1.72.4-0ubuntu0.22.04.1 ** Tags removed: block-proposed-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023572] Re: SRU gjs 1.72.4 to jammy
** Tags removed: verification-needed ** Tags added: verification-done ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1294015] Re: gjs-console crashed with signal 5 in g_settings_bind_with_mapping()
** Changed in: gjs (Ubuntu) Status: Confirmed => Incomplete ** No longer affects: gjs (Ubuntu Trusty) ** No longer affects: gjs (Ubuntu Utopic) ** No longer affects: gnome-settings-daemon (Ubuntu Trusty) ** No longer affects: gnome-settings-daemon (Ubuntu Utopic) ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1294015 Title: gjs-console crashed with signal 5 in g_settings_bind_with_mapping() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1294015/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023572] Re: SRU gjs 1.72.4 to jammy
** Summary changed: - SRU gjs 1.72.3 to jammy + SRU gjs 1.72.4 to jammy ** Description changed: [ Impact ] That's the GNOME 42 stable update, including some fixes: - https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.3 + https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023571] Re: Update to gjs 1.76.2 and SRU it
This bug was fixed in the package gjs - 1.76.2-1 gjs (1.76.2-1) experimental; urgency=medium * New upstream release (LP: #2023571) * Drop all patches: applied in new release -- Jeremy Bícha Wed, 14 Jun 2023 18:44:22 -0400 ** Summary changed: - Update to gjs 1.76.1 and SRU it + Update to gjs 1.76.2 and SRU it ** Description changed: [ Impact ] There is a new bugfix release in the stable series associated with GNOME 44 - https://gitlab.gnome.org/GNOME/gjs/-/blob/1.76.1/NEWS + https://gitlab.gnome.org/GNOME/gjs/-/blob/1.76.2/NEWS [ Test case ] Complete the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] GNOME Shell is the heart of the Ubuntu desktop experience. gjs is a key component of GNOME Shell. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu (it is used by even GDM, the login screen). Smaller bugs could interrupt people's workflows. This update changed fundamentally the memory management of some objects and containers (especially GVariant's), but these changes were already part of gjs released in ubuntu lunar (1.76.0-3). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023571 Title: Update to gjs 1.76.2 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023572] Re: SRU gjs 1.72.3 to jammy
** Changed in: gjs (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.3 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
** Description changed:
[ Impact ]
High Memory Usage 3.1gb in 2h after reboot
[ Test case ]
Run:
- env G_SLICE=always-malloc valgrind --leak-check=full \
- --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
- gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
+ env G_SLICE=always-malloc valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
No leak should be detected
+
+ Running more installed tests under valgrind should output no leaks
+ (unless those caused by gobject-introspection):
+
+ sudo apt install gjs-tests
+ env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ /usr/libexec/installed-tests/gjs/minijasmine \
+ /usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
+
+ There may be only two leaks caused by
+ gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one
+ after a ObjectInstance::prop_setter_impl call (these are leaks in the
+ test library that are expected with gobject-introspection 42, but fixed
+ in later versions).
+
+ env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ /usr/libexec/installed-tests/gjs/minijasmine \
+ /usr/libexec/installed-tests/gjs/js/testRegress.js
+
+ No leak expected
[ Regression potential ]
Gjs applications (including gnome Shell) using GVariant may misbehave
+ ---
ProblemType: BugDistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 6.2.8-060208-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 22:46:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-25 (366 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)
** Changed in: gjs (Ubuntu Kinetic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2012978
Title:
Memory leak
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1986522] Re: Using a Gio.DesktopAppinfo().launch with context freezes GJS
It seems the problem is quite old, let's move at https://gitlab.gnome.org/GNOME/gjs/-/issues/553 ** Bug watch added: gitlab.gnome.org/GNOME/gjs/-/issues #553 https://gitlab.gnome.org/GNOME/gjs/-/issues/553 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1986522 Title: Using a Gio.DesktopAppinfo().launch with context freezes GJS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1986522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016906] Re: Inactive zombie ghost icons left behind on desktop when copying files
** Package changed: gjs (Ubuntu) => gnome-shell-extension-desktop-icons- ng (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2016906 Title: Inactive zombie ghost icons left behind on desktop when copying files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987445] Re: After upgrade to 22.04 from 20.x execution of the shell fails to start the application
** Changed in: gjs (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1987445 Title: After upgrade to 22.04 from 20.x execution of the shell fails to start the application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1987445/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2007739] Re: gjs-console crashed with SIGABRT
*** This bug is a duplicate of bug 2012287 ***
https://bugs.launchpad.net/bugs/2012287
** This bug has been marked a duplicate of bug 2012287
gjs-console crashed with signal 6 in g_assertion_message("assertion failed:
(!priv->is_realized)") from g_assertion_message_expr() from
gsk_renderer_dispose() from gsk_renderer_dispose() from g_object_unref()
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2007739
Title:
gjs-console crashed with SIGABRT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2007739/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023572] [NEW] SRU gjs 1.72.3 to jammy
Public bug reported: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). ** Affects: gjs (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: gjs (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gjs (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu Jammy) Status: New => In Progress ** Changed in: gjs (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gjs (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.3 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023571] Re: Update to gjs 1.76.1 and SRU it
** Changed in: gjs (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gjs (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023571 Title: Update to gjs 1.76.1 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023571] [NEW] Update to gjs 1.76.1 and SRU it
Public bug reported: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gjs/-/commits/1.76.1 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). This update changed fundamentally the memory management of some objects and containers (especially GVariant's), but these changes were already part of gjs released in ubuntu lunar (1.76.0-3). ** Affects: gjs (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: gjs (Ubuntu Lunar) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gjs (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: gjs (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: gjs (Ubuntu Lunar) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gjs (Ubuntu Lunar) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023571 Title: Update to gjs 1.76.1 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2019751] Re: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation
Script tested with new version, no failure: apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.2.1 Candidate: 72~ubuntu5.22.04.2.1 Version table: *** 72~ubuntu5.22.04.2.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 72~ubuntu5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2019751 Title: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2019751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983456] Re: Context menu options are shown under dock panel and can not be chosen in Wayland sessions
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => Triaged ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1983456 Title: Context menu options are shown under dock panel and can not be chosen in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1983456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2017523] Re: Launched application in second to last position in dock
See also https://github.com/micheleg/dash-to- dock/issues/2010#issuecomment-1570138224 Fixed in https://github.com/micheleg/dash-to-dock/pull/2021/ ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => In Progress ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => Triaged ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided => Low ** Bug watch added: github.com/micheleg/dash-to-dock/issues #2010 https://github.com/micheleg/dash-to-dock/issues/2010 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2017523 Title: Launched application in second to last position in dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2017523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
Handled in https://github.com/micheleg/dash-to-dock/pull/2020 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
I've been able to find a case in which this was not fixed for me too, and I've now handled it upstream. So we need to respin the SRU update. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-failed-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Fix Released => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over window after resuming from blank screen
Sadly this is a mutter bug that is not as easy to handle because it may break other cases. However we're doing some work on it at https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3014 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2019751] Re: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation
Also tested the same in lunar, all working as expected following the test case script: ❯ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 79ubuntu2.23.04.1 Candidate: 79ubuntu2.23.04.1 Version table: *** 79ubuntu2.23.04.1 400 400 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu lunar-proposed/main i386 Packages 100 /var/lib/dpkg/status ** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2019751 Title: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2019751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2019751] Re: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation
After installing the update the nested shell is perfectly usable, and there are not un-clickable areas or invisible areas in the screen. ❯ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.2 Candidate: 72~ubuntu5.22.04.2 Version table: *** 72~ubuntu5.22.04.2 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2019751 Title: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2019751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over window after resuming from blank screen
So, that "fix" won't probably be accepted. We've worked on a solution that works for some cases, but still missing few edge ones. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2018672] Re: Gnome 44: GDM background configurable with gsettings
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Didier Roche-Tolomelli (didrocks) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2018672 Title: Gnome 44: GDM background configurable with gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over window after resuming from blank screen
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2019751] [NEW] Shell startup animation may not complete on early resolution changes
Public bug reported: [ Impact ] GNOME Shell startup animation may not complete during startup, leading to a non-functional GNOME shell because the workarea could be clipped or input events are ignored. [ Test case ] 1. Run this script: https://gitlab.gnome.org/3v1n0/gnome-shell/-/snippets/5749 2. It's expected to launch a gnome-shell nested instance and perform monitor changes 3. The shell should animate to the final state and everything should be usable: - Clicking in shell widgets should work - No area is hidden or clipped [ Regression potential ] GNOME Shell may not start properly, input events are ignored and/or the desktop area is clipped. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu Lunar) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Triaged ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Lunar) Status: New => Triaged ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided => High ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Lunar) Importance: Undecided => High ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Lunar) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Description changed: [ Impact ] GNOME Shell startup animation may not complete during startup, leading to a non-functional GNOME shell because the workarea could be clipped or input events are ignored. [ Test case ] 1. Run this script: https://gitlab.gnome.org/3v1n0/gnome-shell/-/snippets/5749 2. It's expected to launch a gnome-shell nested instance and perform monitor changes 3. The shell should animate to the final state and everything should be usable: -- Clicking in shell widgets should work -- No area is hidden or clipped + - Clicking in shell widgets should work + - No area is hidden or clipped [ Regression potential ] - GNOME Shell may not start up anymore. + GNOME Shell may not start properly, input events are ignored and/or the + desktop area is clipped. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2019751 Title: Shell startup animation may not complete on early resolution changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2019751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012978] Re: Memory leak
** Changed in: gjs (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
