[Bug 2011751] Re: openbox crashed with SIGABRT
(One extra bit of info that I realized was left out - according to the comment on the Arch Linux forums here: https://bbs.archlinux.org/viewtopic.php?pid=2090270#p2090270 the first loop iteration succeeds. It's not until the second iteration (after the list has been modified) that the crash occurs. Thus why I believe the one-item case to be safe. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012100] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive(mime_type="text/html") from ffi_call_unix64()
Incomplete pending feedback on comment #3. ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- 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/2012100 Title: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive(mime_type="text/html") from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012100] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive()
See also bug 2012230 ** Information type changed from Private to Public ** Description changed: - https://errors.ubuntu.com/problem/6ed60191b7b581604728fdae19728667e22ec160 - I have this error when I'm connecting to nym-connect (nymtech.net) ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 Uname: Linux 5.19.0-21-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 17 18:10:09 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1677216555 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/judemont ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users ** No longer affects: gnome-shell (Ubuntu) ** Summary changed: - gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() + gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64() ** Summary changed: - gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64() + gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive(mime_type="text/html") from ffi_call_unix64() ** Tags added: lunar ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- 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/2012100 Title: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive(mime_type="text/html") from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012230] Re: /usr/bin/gnome-shell:11:meta_wayland_compositor_get_context:display_from_offer:destroy_data_offer:destroy_resource:for_each_helper
See also bug 2012100 ** This bug is no longer a duplicate of bug 2012100 gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() ** Summary changed: - /usr/bin/gnome-shell:11:meta_wayland_compositor_get_context:display_from_offer:destroy_data_offer:destroy_resource:for_each_helper + gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from destroy_data_offer() from destroy_resource() from for_each_helper() ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2716 https://gitlab.gnome.org/GNOME/mutter/-/issues/2716 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/mutter/-/issues/2716 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/2012230 Title: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from destroy_data_offer() from destroy_resource() from for_each_helper() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2012230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
Aaron asked me to test his version via PPA As noted in the original bug report; this bug was annoying... as was hitting me often enough I stopped using Lubuntu & used Xfce & GNOME instead while, before returning to LXQt though I replaced `openbox` as WM with `xfwm4` (to avoid issues). (note: times are likely AEST as I'm getting this detail from my hexchat IRC logs; but if verification/UTC times are needed read https://irclogs.ubuntu.com/2023/03/20/%23lubuntu-devel.txt etc where 13:09:35 is recorded as [02:09] on irclogs.ubuntu.com) Mar 20 12:53:24 OK, will push to a PPA and have available for testing shortly. Mar 20 12:54:19:) (but also followed by a rather quick :( as that'll require me to make a change (to test) & then LOGOUT so I can re-login; the logout is the :( ) Mar 20 13:09:35 https://launchpad.net/~arraybolt3/+archive/ubuntu/openbox I installed the patched version on Aaron's PPA --- openbox: Installed: 3.6.1-10ubuntu1~ppa1 Candidate: 3.6.1-10ubuntu1~ppa1 Version table: *** 3.6.1-10ubuntu1~ppa1 500 500 https://ppa.launchpadcontent.net/arraybolt3/openbox/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3.6.1-10 500 500 http://archive.ubuntu.com/ubuntu lunar/universe amd64 Packages --- Selected copy/pastes from my hexchat log --- Mar 20 14:35:17quick play and no crashes (or FIRES!) arraybolt3 ; I'll use normally; but I was getting openbox crash maybe hourly as I recall prior to fix (why I switched to other DEs then swapped out openbox).. currently using 3.6.1-10ubuntu1~ppa1 Mar 21 09:38:45fyi arraybolt3 , have had no openbox crashes... Mar 22 13:14:28arraybolt3, another day & no openbox crashes... (last was @Mar 16 09:46 my local time; then I switched to other DEs... then back to LXQt but xfwm4 instead of openbox... been using openbox again since your PPA) --- I've been using my primary system since then without issue. My usage is normal, I suspend at night then resume in the morning. I rebooted system earlier today, logged in and returned to normal usage. I have experienced no issues, system has been stable as I expect from Lubuntu :) --- guiverc@d7050-next:~$ neofetch --off guiverc@d7050-next -- OS: Lubuntu Lunar Lobster (development branch) x86_64 Host: OptiPlex 7050 Kernel: 6.1.0-16-generic Uptime: 2 hours, 59 mins Packages: 3100 (dpkg), 12 (snap) Shell: bash 5.2.15 Resolution: 1680x1050, 1920x1080, 1920x1080 DE: LXQt 1.2.0 WM: Openbox Theme: Arc-Darker [GTK2/3] Icons: oxygen [GTK2/3] Terminal: qterminal Terminal Font: Ubuntu Mono 14 CPU: Intel i5-6500 (4) @ 3.600GHz GPU: Intel HD Graphics 530 Memory: 7864MiB / 15852MiB -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012225] Re: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMP
** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #5687 https://gitlab.gnome.org/GNOME/gtk/-/issues/5687 ** Changed in: gtk Remote watch: gitlab.gnome.org/GNOME/gtk/-/issues #5392 => gitlab.gnome.org/GNOME/gtk/-/issues #5687 -- 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/2012225 Title: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE): (0x8cdd == 0x8cd5)"] from gsk_gl_command_queue_create_render_target() [gskglcommandqueue.c:1279] To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2012225/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
** Description changed: Lubuntu lunar (primary box) on - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915) I experienced a crash yesterday (openbox) but tend to ignore the first crashes... Whilst using the machine again today a crash occurred. This is my primary box, so my setup is pretty consistent - featherpad (restored session) - hexchat (irc) - qterminal (only single tab today; usually many) - firefox (snap, most sites excluding google related) - chromium (snap, used for anything google related) - telegram (snap) - element I was using chromium full screen (trying to read my gmail inbox) when borders around windows disappeared & I lost the capacity to switch between windows; mouse would move, but keyboard appeared mostly dead (it wasn't, more I think windows weren't responding, inc. clicks with mouse - though that's likely inconsistent; I could work out how to describe it - yesterday, but todays is almost identical). + though that's likely inconsistent; I could [not] work out how to + describe it yesterday, but todays is almost identical). I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used - ctrl+alt+t to open new terminal - openbox & session returned to what I expect... ** expected outcome Openbox doesn't crash ** actual outcome all windows lost borders, and i lost ability to switch between windows I appeared to have minimal control (not true, more a fraction of what I expect) ** How to get crash For me, - I used chromium (browser) - make chromium full screen (ie. F11) - - click on something & right-click to open in new window + - click on link/something & right-click to open in new window OPENBOX CRASH. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: openbox 3.6.1-10 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: LXQt Date: Thu Mar 16 09:46:22 2023 ExecutablePath: /usr/bin/openbox ExecutableTimestamp: 1643543619 InstallationDate: Installed on 2023-01-25 (49 days ago) InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/openbox ProcCwd: /home/guiverc RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: openbox StacktraceTop: () at /lib/x86_64-linux-gnu/libobt.so.2 () at /lib/x86_64-linux-gnu/libc.so.6 client_calc_layer () () () at /lib/x86_64-linux-gnu/libobt.so.2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
OK, so I'm not entirely sure testing the one item case is even possible since the crash happens when switching from a fullscreen window (which implies that there are at least two windows). However, this is what I did, and everything was successful (no crashes). 1. Boot a Lubuntu Lunar ISO, and install the patched Openbox into it. 2. Log out. 3. Log in, but with a plain Openbox session. No desktop, no panel, no LXQt, just Openbox. 4. Open a terminal emulator, and run "firefox &" followed by "diswon ". Then close the terminal emulator. 5. Fullscreen Firefox with F11. 6. Attempt to "switch" out of Firefox with Alt+Tab. No crashes occur. 7. Open Wikipedia. 8. Right-click on a link and click "Open in new window". No crashes occur (this is what was able to reliably trigger the crash before). 9. Switch between the fullscreen and non-fullscreen window with Alt+Tab. Still no crashes. 10: Fullscreen the second Firefox window and switch between them with Alt+Tab. Still no crashes. 11: Take both Firefox windows out of fullscreen and switch between them. Still no crashes. I did a bit more than that, but that should cover the one-item and two-item test cases. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
Thank you, Seb! ** Description changed: [ Impact ] - * Sometimes on devices with WWAN card, whenever user presses the + * Sometimes on devices with WWAN card, whenever user presses the wireless function key (Fn+F8) or turn on the airplane mode radio button in Settings, the airplane mode will not be enabled, and the airplane mode icon is not shown in the status bar. - * There is a unmerged upstream merge request that delivers the fix: + * There is a unmerged upstream merge request that delivers the fix: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/merge_requests/310 It works perfectly well on several Lenovo laptops with WWAN cards. The root causes is that the value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should listen to "g-properties-changed" instead of "g-signal" now. [ Test Plan ] - 1. Find a machine which has WWAN card. - 2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not use rfkill to unblock the WWAN, and reboot. - 3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio button in Settings. - 4. The airplane mode should be enabled, but actually not. + 1. Find a machine which has WWAN card. + 2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not use rfkill to unblock the WWAN, and reboot. + 3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio button in Settings. + 4. The airplane mode should be enabled, but actually not. [ Where problems could occur ] - * When user is using a very low version network-manager that still + * When user is using a very low version network-manager that still broadcasting DBUS "PropertiesChanged" events on "g-signal" instead of the concurrent "g-properties-changed", the airplane mode will sometimes not be able to enable. + + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853#75fe48a78c4af7f7fb18988e15e27dcba51d0d06 [ Other Info ] 1. About Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Kernel: 6.1.0-1007-oem 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and manager->wwan_enabled is set to the correct value. 4. Actual: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the initial value of manager->wwan_enabled is true, it will never be able to switch to airplane mode. ** Description changed: [ Impact ] * Sometimes on devices with WWAN card, whenever user presses the wireless function key (Fn+F8) or turn on the airplane mode radio button in Settings, the airplane mode will not be enabled, and the airplane mode icon is not shown in the status bar. * There is a unmerged upstream merge request that delivers the fix: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/merge_requests/310 It works perfectly well on several Lenovo laptops with WWAN cards. The root causes is that the value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should listen to "g-properties-changed" instead of "g-signal" now. [ Test Plan ] 1. Find a machine which has WWAN card. 2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not use rfkill to unblock the WWAN, and reboot. 3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio button in Settings. 4. The airplane mode should be enabled, but actually not. [ Where problems could occur ] - * When user is using a very low version network-manager that still - broadcasting DBUS "PropertiesChanged" events on "g-signal" instead of - the concurrent "g-properties-changed", the airplane mode will sometimes - not be able to enable. + * When user is using a very low version network-manager (< 1.20) that + still broadcasting DBUS "PropertiesChanged" events on "g-signal" instead + of the concurrent "g-properties-changed", the airplane mode will + sometimes not be able to enable. - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853#75fe48a78c4af7f7fb18988e15e27dcba51d0d06 + [1]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853 + [2]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f [ Other Info ] 1. About Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Kernel: 6.1.0-1007-oem 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/
[Bug 2011751] Re: openbox crashed with SIGABRT
@dbungert: While the patch that simply copies the list is a possible way of doing things, a very experienced user on the Arch Linux forums had concerns about doing things that way, see https://bbs.archlinux.org/viewtopic.php?pid=2090570#p2090570 "But creating a copy of the list is inefficient and only glosses over the actual problem (and probably will cause X11 errors and/or behavioral differences - maybe maintain them b/c of the status quo ante)" In the two-item case, as long as the rest of Openbox code keeps the list consistent after removing *and adding* an item (because keep in mind the code doesn't just remove stuff, it also adds stuff), everything should be fine. itPrev->next should point to a valid item unless the underlying list has become corrupted. In the one item case, the first iteration through the loop works, and with only one item, there will only be one iteration through the loop, so presumably the crash won't happen unless the one item case triggers a crash in some other way. I'll test both and report back what happens. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
This bug was fixed in the package gnome-settings-daemon - 44~rc-1ubuntu2 --- gnome-settings-daemon (44~rc-1ubuntu2) lunar; urgency=medium * debian/patches/gitlab_nmsignal_deprecated.patch: - cherrypick a change in review upstream to fix airplane mode on some Lenovo laptops (lp: #2011770) -- Sebastien Bacher Tue, 21 Mar 2023 21:30:20 +0100 ** Changed in: gnome-settings-daemon (Ubuntu) Status: Fix Committed => Fix Released -- 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/2011770 Title: [gsd-rfkill] WwanEnabled never get synced To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012388] Re: Unable to focus Windows below system tray (wayland session)
Looks like we've leaked a picking rectangle/actor from either an indicator or the aggregate menu. Please try: gnome-extensions disable ubuntu-appindicat...@ubuntu.com gnome-extensions disable gTile@vibou gnome-extensions disable caffe...@patapon.info and possibly others from 'gnome-extensions list' :) You might also be able to find out what the rectangle *is* by: 1. Alt+F2 2. Type: lg 3. Click the target icon 4. Move the mouse over the problematic area ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2012388 Title: Unable to focus Windows below system tray (wayland session) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012388/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
Partial review of the patch so far. I haven't read much openbox code so take this with a grain of salt. https://bugzilla.icculus.org/show_bug.cgi?id=6669#c9 mentions a concern that itPrev may still be pointing to invalid data. I share this concern. I think some interesting testcases are what happens with lists that have one or two elements, which then are modified by this function. In the single element case, I believe your itPrev now points to the deleted item, and in the two element case, itPrev may be ok but itPrev->prev or itPrev->next are both probably not valid. https://bugzilla.icculus.org/show_bug.cgi?id=6669#c5 mentions a work branch. I suggest tracking that down and considering it. It's presumably this patch https://bugzilla.icculus.org/attachment.cgi?id=3646&action=diff. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
I don't have upload access to this package yet (it's not in the Lubuntu packageset apparently) so I'm uploading the patch here so that it can be sponsored. ** Patch added: "glib_crash_bugfix.patch" https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011751/+attachment/5656433/+files/glib_crash_bugfix.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
** Changed in: openbox (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008532] Re: Typing a filename in a nautilus window, and the letters are not in the order I typed them.
This is not strictly a Nautilus bug, it's way bigger than that, it potentially affects all GTK4 applications when the system is under stress. I was told it's an ibus bug rather than GTK, so I filed it here, and I would really appreciate it if your team can help investigate or fix it: https://github.com/ibus/ibus/issues/2486 ** Bug watch added: github.com/ibus/ibus/issues #2486 https://github.com/ibus/ibus/issues/2486 ** Also affects: nautilus via https://github.com/ibus/ibus/issues/2486 Importance: Unknown Status: Unknown ** Project changed: nautilus => ibus -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2008532 Title: Typing a filename in a nautilus window, and the letters are not in the order I typed them. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2008532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008067] Re: To support Elan fp device [04F3:0C82]
** Changed in: oem-priority Status: Fix Committed => Fix Released -- 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/2008067 Title: To support Elan fp device [04F3:0C82] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2008067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012311] Re: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04
** No longer affects: gnome-shell (Ubuntu) ** Package changed: gdm3 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Fix Released -- 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/2012311 Title: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2012311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012294] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2012294/+attachment/5656419/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2012294/+attachment/5655961/+files/CoreDump.gz ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2012294 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2012294/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012294] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/2012294/+attachment/5656418/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2012294 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2012294/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012294] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2012294/+attachment/5656417/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2012294 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2012294/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012294] evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke()
StacktraceTop: ?? () g_closure_invoke (closure=0x564dafb6e6d0, return_value=0x0, n_param_values=2, param_values=0x7ffe7baf0340, invocation_hint=0x7ffe7baf02c0) at ../../../gobject/gclosure.c:832 signal_emit_unlocked_R.isra.0 (node=node@entry=0x564dafa40b80, detail=detail@entry=552, instance=instance@entry=0x564dafac44a0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffe7baf0340) at ../../../gobject/gsignal.c:3802 g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7ffe7baf0500) at ../../../gobject/gsignal.c:3555 g_signal_emit (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3612 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2012294 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2012294/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999884] Re: gdm-smartcard not passing successful authentication to desktop at system logon
Nathan, when using `sssd-gdm-smartcard-pam-auth-tester.sh` it does all the checks that were failing before of this fix. It doens't use the gdm UI directly, because there's no need for it, but it indeed uses the gdm-smartcard PAM configuration that was the buggy one. So if the script works for you, it's a good sign :) Using the WAIT mode also requires a smartcard to be properly configured or to use the script from another machine so that you can insert the credentials it expects from the virtual smartcard. However, marking it as resolved in jammy as per Orion report. ** 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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1999884 Title: gdm-smartcard not passing successful authentication to desktop at system logon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1999884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 953202] Re: gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:273: poll_for_event: Försäkran \"!xcb_xlib_threads_sequence_lost\" falsk.
** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Invalid -- 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/953202 Title: gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:273: poll_for_event: Försäkran \"!xcb_xlib_threads_sequence_lost\" falsk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/953202/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011383] Re: Slow down my system
The extension should not slowdown anymore when loading such icons, as that's now handled by the shell itself, so while an icon could be missing we don't do much IO from extension level. -- 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/2011383 Title: Slow down my system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009913] Re: gnome-control-center crashed with SIGSEGV in gtk_widget_in_destruction() from gcm_prefs_list_box_row_selected_cb() from g_cclosure_marshal_VOID__OBJECTv() from _g_closure_invoke_va()
Fixed in https://gitlab.gnome.org/GNOME/gnome-control- center/-/commit/4b400736bc7374d0c74b498c1f60dedaa5fe9c4b ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Tags added: fixed-in-gcc-44.1 fixed-upstream -- 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/2009913 Title: gnome-control-center crashed with SIGSEGV in gtk_widget_in_destruction() from gcm_prefs_list_box_row_selected_cb() from g_cclosure_marshal_VOID__OBJECTv() from _g_closure_invoke_va() from g_signal_emit_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2009913/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
I've uploaded to lunar now, once confirm to work there we will SRU -- 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/2011770 Title: [gsd-rfkill] WwanEnabled never get synced To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => High ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed => Fix Committed -- 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/2011770 Title: [gsd-rfkill] WwanEnabled never get synced To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
This bug was fixed in the package tracker-miners - 3.4.3-1ubuntu1 --- tracker-miners (3.4.3-1ubuntu1) lunar; urgency=medium [ Denison Barbosa ] * debian/patches/ubuntu-fix-tracker-extract-start-order.patch: Fix tracker-extract.service WantedBy target so that gvfsd has access to KRB5CCNAME. (LP: #1779890) -- Didier Roche Tue, 21 Mar 2023 15:04:35 +0100 ** Changed in: tracker-miners (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008067] Re: To support Elan fp device [04F3:0C82]
This bug was fixed in the package libfprint - 1:1.94.3+tod1-0ubuntu2~22.04.04 --- libfprint (1:1.94.3+tod1-0ubuntu2~22.04.04) jammy; urgency=medium [ Andy Chi ] * debian/patches/elanmoc-add-PID-0x0c82.patch (LP: #2008067) -- Marco Trevisan (Treviño) Fri, 03 Mar 2023 16:44:02 +0100 ** Changed in: libfprint (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 libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2008067 Title: To support Elan fp device [04F3:0C82] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2008067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012309] Re: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04
Didn't realize that. I'll wait for final release. -- 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/2012309 Title: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012309] Re: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04
Here's the other thing you haven't considered: gdm3: Version table: 43.0-3ubuntu2 Ubuntu 23.04 is expected to have gdm3 44 before release, and we haven't even approached beta yet. Maybe you just need to wait? -- 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/2012309 Title: gdm3: autostart folder for .desktop files is not working in Ubuntu 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012309/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009913] Re: gnome-control-center crashed with SIGSEGV in gtk_widget_in_destruction() from gcm_prefs_list_box_row_selected_cb() from g_cclosure_marshal_VOID__OBJECTv() from _g_closure_invoke_va()
Valgrind confirms: ==22708== Invalid read of size 1 ==22708==at 0x505CC0B: gtk_widget_in_destruction (gtkwidget.c:10643) ==22708==by 0x189553: gcm_prefs_list_box_row_selected_cb (cc-color-panel.c:1708) ==22708==by 0x4A61714: g_cclosure_marshal_VOID__OBJECTv (gmarshal.c:1910) ==22708==by 0x4A5E148: _g_closure_invoke_va (gclosure.c:895) ==22708==by 0x4A784F3: g_signal_emit_valist (gsignal.c:3462) ==22708==by 0x4A78722: g_signal_emit (gsignal.c:3612) ==22708==by 0x4F5B121: gtk_list_box_remove (gtklistbox.c:2420) ==22708==by 0x4F5B222: gtk_list_box_dispose (gtklistbox.c:439) ==22708==by 0x4A63338: g_object_unref (gobject.c:3891) ==22708==by 0x4EAA994: gtk_box_dispose (gtkbox.c:230) ==22708==by 0x4A63338: g_object_unref (gobject.c:3891) ==22708==by 0x4EAA994: gtk_box_dispose (gtkbox.c:230) ==22708== Address 0xfeb2 is not stack'd, malloc'd or (recently) free'd ==22708== ==22708== ==22708== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==22708== Access not within mapped region at address 0xFEB2 ==22708==at 0x505CC0B: gtk_widget_in_destruction (gtkwidget.c:10643) ==22708==by 0x189553: gcm_prefs_list_box_row_selected_cb (cc-color-panel.c:1708) ==22708==by 0x4A61714: g_cclosure_marshal_VOID__OBJECTv (gmarshal.c:1910) ==22708==by 0x4A5E148: _g_closure_invoke_va (gclosure.c:895) ==22708==by 0x4A784F3: g_signal_emit_valist (gsignal.c:3462) ==22708==by 0x4A78722: g_signal_emit (gsignal.c:3612) ==22708==by 0x4F5B121: gtk_list_box_remove (gtklistbox.c:2420) ==22708==by 0x4F5B222: gtk_list_box_dispose (gtklistbox.c:439) ==22708==by 0x4A63338: g_object_unref (gobject.c:3891) ==22708==by 0x4EAA994: gtk_box_dispose (gtkbox.c:230) ==22708==by 0x4A63338: g_object_unref (gobject.c:3891) ==22708==by 0x4EAA994: gtk_box_dispose (gtkbox.c:230) ==22708== If you believe this happened as a result of a stack ==22708== overflow in your program's main thread (unlikely but ==22708== possible), you can try to increase the size of the ==22708== main thread stack using the --main-stacksize= flag. ==22708== The main thread stack size used in this run was 8388608. -- 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/2009913 Title: gnome-control-center crashed with SIGSEGV in gtk_widget_in_destruction() from gcm_prefs_list_box_row_selected_cb() from g_cclosure_marshal_VOID__OBJECTv() from _g_closure_invoke_va() from g_signal_emit_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2009913/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011849] Re: gnome-control-center 44rc is missing graphics for Multitasking and Mouse & Touchpad
We've a workaround in https://salsa.debian.org/gnome- team/gtk4/-/merge_requests/12 to include gstreamer player inside gtk so that we don't have to depend on gstreamer bad. Also test packages in https://launchpad.net/~3v1n0/+archive/ubuntu/gtk4-gstreamer -- 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/2011849 Title: gnome-control-center 44rc is missing graphics for Multitasking and Mouse & Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011849/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
** Package changed: gvfs (Ubuntu) => tracker-miners (Ubuntu) ** Changed in: tracker-miners (Ubuntu) Assignee: (unassigned) => Denison Barbosa (justdenis) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012388] [NEW] Unable to focus Windows below system tray (wayland session)
Public bug reported: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "window-focus-01.png" https://bugs.launchpad.net/bugs/2012388/+attachment/5656306/+files/window-focus-01.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/2012388 Title: Unable to focus Windows below system tray (wayland session) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012388/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012311] Re: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04
> Seems like I had the bug yesterday but it's fixed today? Same here. It doesn't work but just worked after installing these updates: libadwaita-1-0:arm64 (1.3.1-1ubuntu1) gir1.2-adw-1:arm64 (1.3.1-1ubuntu1) mutter-common:arm64 (44.0-1ubuntu1) mutter-common-bin:arm64 (44.0-1ubuntu1) libmutter-12-0:arm64 (44.0-1ubuntu1) gir1.2-mutter-12:arm64 (44.0-1ubuntu1) gnome-control-center:arm64 (1:44.0-1ubuntu1) gnome-control-center-data:arm64 (1:44.0-1ubuntu1) gnome-control-center-faces:arm64 (1:44.0-1ubuntu1) I've checked the changelog of these updates without finding the concrete one that fixed the problem. But it's fixed... so we're happy :D -- 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/2012311 Title: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011849] Re: gnome-control-center 44rc is missing graphics for Multitasking and Mouse & Touchpad
I can confirmed installing libgtk-4-media-gstreamer re-appearing the graphic -- 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/2011849 Title: gnome-control-center 44rc is missing graphics for Multitasking and Mouse & Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011849/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012021] Re: gnome-shell crashed with SIGSEGV in __strcmp_avx2() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist()
This bug was fixed in the package gnome-shell - 44.0-2ubuntu1 --- gnome-shell (44.0-2ubuntu1) lunar; urgency=medium * Merge with debian, containing a new upstream release * debian/patches: Reload shell theme on color scheme changes * debian/patches: Do not crash on st settings updates (LP: #2012021) * debian/patches: Refresh * Remaining changes with debian: - Add some Recommends: + ubuntu-session (| gnome-session) to have the ubuntu session available + ubuntu-wallpapers + xserver-xorg-legacy + yaru-theme-gnome-shell for the default ubuntu theming - Move some Recommends to Suggests: + chrome-gnome-shell + gnome-backgrounds - Update debian/gbp.conf with Ubuntu settings - debian/ubuntu-session-mods/ubuntu.json: Use Yaru's gnome-shell icons - debian/patches: Do not hang & crash if fingerprint service fails to start (LP: #1962566) - ubuntu/desktop_detect.patch: + add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. - ubuntu/lightdm-user-switching.patch: + Allow user switching when using LightDM. - ubuntu/lock_on_suspend.patch + Respect Ubuntu's lock-on-suspend setting. - ubuntu/background_login.patch + Change default background color as we modified the default GDM color for our ubuntu session. - ubuntu/gdm_alternatives.patch + Add support for GDM3 theme alternatives - main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: + Improve debug JS tracing for crash reports - ubuntu/smarter_alt_tab.patch: + quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: + Show monitor scaled cursor when magnifier is enabled - ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: + stop searches when requested from UI - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch - u/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch - ubuntu/resolve_alternate_theme_path.patch - ubuntu/secure_mode_extension.patch - ubuntu/keep-ubuntu-logo-bright-lp1867133-v1.patch - ubuntu/configure_login_screen.patch - ubuntu/layout-Make-starting-in-the-overview-optional.patch: + Makes dock replace overview easier - ubuntu/layout-Try-to-allocate-before-getting-size-of-tracke.patch: + Ensure windows don't get maximized under the panels / dock - debian/patches: Compute system background color from theme (LP: #1965727) - ubuntu/configure-login-screen.patch: Use bg color for initial system bg (LP: #1965727) - debian/patches: Ensure St.Entry's `selected-color` CSS property is honored (LP: #1878998) - ubuntu/support-loading-Yaru-variants: Handle dark/light variants better - d/p/use-favorites-strings: Only apply this to ubuntu session - debian/patches: Support configuring icons resource to use for mode - Revert-st-Apply-css-foreground-color-to-text-as-a-PangoAt.patch: + Ensure selected-text foreground color is preserved - ubuntu/sessionMode-Add-support-for-configuring-an-icons-resource.patch: + Support loading iconsResourceName from session file - ubuntu/main-Support-loading-multiple-Yaru-theme-variants.patch, - ubuntu/darkMode-Add-support-to-Yaru-theme-color-variants.patch: + Support loading Yaru theme variants (for accent color) - ubuntu/Revert-dash-Use-pin-instead-of-favorites gnome-shell (44.0-2) experimental; urgency=medium * debian/control: Bump dependency on mutter 44 gnome-shell (44.0-1) experimental; urgency=medium * New upstream release * debian/patches: Refresh * debian/patches: Cherry-pick upstream fixes * debian/rules: Create a cache home folder for dconf -- Marco Trevisan (Treviño) Tue, 21 Mar 2023 05:41:22 +0100 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- 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/2012021 Title: gnome-shell crashed with SIGSEGV in __strcmp_avx2() from update_current_theme() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012021/+subscriptions -
[Bug 2011851] Re: FFe: Sync epiphany-browser 44~rc-1 (universe) from Debian experimental
** Changed in: epiphany-browser (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/2011851 Title: FFe: Sync epiphany-browser 44~rc-1 (universe) from Debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/2011851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011790] Re: Night Light doesn't work in gnome-shell 44.rc
** Changed in: mutter (Ubuntu) Status: Fix Committed => 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/2011790 Title: Night Light doesn't work in gnome-shell 44.rc To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2011790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012311] Re: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04
Seems like I had the bug yesterday but it's fixed today? ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- 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/2012311 Title: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012311] Re: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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/2012311 Title: gdm3: Restart and Shutdown options doesn't work in Ubuntu 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
