[Desktop-packages] [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 Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Invalid Status in openbox package in Ubuntu: Confirmed Bug description: 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 [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 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: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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_un
Incomplete pending feedback on comment #3. ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, 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() Status in mutter package in Ubuntu: Incomplete Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell 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() Status in mutter package in Ubuntu: Incomplete Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/6ed60191b7b581604728fdae19728667e22ec160 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2012230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Invalid Status in openbox package in Ubuntu: Confirmed Bug description: 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 [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 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 Inst
[Desktop-packages] [Bug 2012225] Re: mutter-x11-frames crashed with SIGABRT in g_assertion_message() from g_assertion_message_cmpnum() ["assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) ==
** 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 Desktop Packages, which is subscribed to gtk4 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] Status in GTK+: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mutter. This problem was most recently seen with package version 44~rc-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7164cde08dbb940e13b49c4e92d4914b24e6c7dc 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2012225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Invalid Status in openbox package in Ubuntu: Confirmed Bug description: 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 [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 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:
[Desktop-packages] [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 Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Invalid Status in openbox package in Ubuntu: Confirmed Bug description: 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). 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 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: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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/
[Desktop-packages] [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 Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Invalid Status in openbox package in Ubuntu: Confirmed Bug description: 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). 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 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: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Triaged Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: [ 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. [ 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: Unable to focus Windows below system tray (wayland session) Status in gnome-shell package in Ubuntu: Incomplete Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Invalid Status in openbox package in Ubuntu: Confirmed Bug description: 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). 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 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: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995779] Re: [HP Pavilion All-in-One Desktop 27-ca1xxx] USB is broken on resume from suspend
** Summary changed: - Strange issues with suspend, Nvidia proprietary and X11 graphics + [HP Pavilion All-in-One Desktop 27-ca1xxx] USB is broken on resume from suspend ** Package changed: nvidia-graphics-drivers-520 (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Expired => New ** Package changed: xorg-server (Ubuntu) => linux-oem-6.1 (Ubuntu) ** Changed in: linux-oem-6.1 (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1995779 Title: [HP Pavilion All-in-One Desktop 27-ca1xxx] USB is broken on resume from suspend Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: New Bug description: Ubuntu: 22.04 jammy Computer: HP Pavilion All-in-One Desktop 27-ca1xxx So a desktop but with a hybrid GPU setup like a laptop. GPU: NVIDIA GeForce RTX 3050 Laptop GPU + Intel(R) Graphics (ADL-S GT1) GPU driver: This happens with all Nvidia proprietary drivers tested so far, 510, 515, 520. I reported it on the latest. Kernel: This happens with all kernels tested so far from 5.15 to 6.0 Desktop: This only happens with an X11 session! If I switch to Wayland it doesn't happen. Problem: When you suspend the computer a number of strange things may happen. Lose connection to keyboard and mouse. Lose connection to USB-C Audio speakers. Stuck on black VT terminal screen. Sometimes reproduced on first try, sometimes it takes 5 tries. Switching to Wayland allows to suspend/resume perfectly however. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Invalid Status in openbox package in Ubuntu: Confirmed Bug description: 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). 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 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: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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. Status in ibus: Unknown Status in nautilus package in Ubuntu: New Bug description: On my Lenovo Yoga 260 I have this annoying problem. At first I thought it was just my typing, but after carefully testing it, I find it is not my typing. You need to type the characters fairly quickly, but often when you do, they come on the search bar in a different order than you typed them. For example, I have a directory called LaserTag and so when I want to find it among all the others in my directory, I open the nautilus window and start typing Laser, but what is printed in the search bar is Lsaer. This may happen in some other programs. I am not sure about that, but it is at least most apparent in nautilus, and reproducible. For example, I did the test twice and got Lsaer twice just now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 15:26:45 2023 InstallationDate: Installed on 2019-04-19 (1407 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-25 (122 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2008532/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Invalid Status in openbox package in Ubuntu: Confirmed Bug description: 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). 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 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: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2008067 Title: To support Elan fp device [04F3:0C82] Status in OEM Priority Project: Fix Released Status in libfprint package in Ubuntu: Invalid Status in libfprint source package in Jammy: Fix Released Status in libfprint source package in Kinetic: Invalid Status in libfprint source package in Lunar: Invalid Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/2b760dfa380ceff152ff8105a2aad76d85ec1ddc This ID is included in upstream. [Impact] * Devices have Elan [04F3:0C82] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [04F3:0C82] will be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2008067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in Ubuntu: Fix Released Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the options to Restart and Shutdown the system are not working anymore. In Ubuntu 22.10 when you are in the gdm3 login screen and choose Restart or Shutdown it presents a dialog box saying that the action will be auto performed in 60 seconds, with two buttons, one to cancel and another to perform the action at once. In Ubuntu 23.04 choosing Restart or Shutdown does nothing at all... Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 Package: gdm3 43.0-3ubuntu2 PackageArchitecture: arm64 ProcVersionSignature: Ubuntu 5.19.0-1015.22-raspi 5.19.17 Tags: lunar Uname: Linux 5.19.0-1015-raspi aarch64 UpgradeStatus: Upgraded to lunar on 2023-03-20 (0 days ago) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-05-04T11:33:42 mtime.conffile..etc.gdm3.custom.conf: 2023-03-07T19:16:26 mtime.conffile..etc.pam.d.gdm-password: 2022-05-08T18:01:33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2012311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012426] Re: yaru-theme-icon package still contains icons to Amazon webstore
** Bug watch added: github.com/ubuntu/yaru/issues #3864 https://github.com/ubuntu/yaru/issues/3864 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/3864 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2012426 Title: yaru-theme-icon package still contains icons to Amazon webstore Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: New Status in yaru-theme package in Debian: New Bug description: This may be a holdover from the original Suru theme for Ubuntu Touch or related desktop Unity scope integration around that time. Suru was the basis for the Yaru theme icons. https://github.com/snwh/suru-icon-theme https://snwh.org/suru https://github.com/ubuntu/yaru /usr/share/icons/Yaru/48x48/apps/amazon-store.png /usr/share/icons/Yaru/scalable/apps/amazon-store-symbolic.svg /usr/share/icons/Yaru/256x256/apps/amazon-store.png /usr/share/icons/Yaru/16x16/apps/amazon-store.png /usr/share/icons/Yaru/48x48@2x/apps/amazon-store.png /usr/share/icons/Yaru/24x24@2x/apps/amazon-store.png /usr/share/icons/Yaru/32x32/apps/amazon-store.png /usr/share/icons/Yaru/24x24/apps/amazon-store.png /usr/share/icons/Yaru/256x256@2x/apps/amazon-store.png /usr/share/icons/Yaru/16x16@2x/apps/amazon-store.png /usr/share/icons/Yaru/32x32@2x/apps/amazon-store.png To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2012426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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() Status in evolution-data-server package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: evolution-data-server 3.47.3-1 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:25 2023 Disassembly: => 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: Mar 21 00:27:22 hostname gnome-control-c[178036]: No gedit is installed here. Colors won't be updated. Please fix your installation. Mar 21 00:27:25 hostname kernel: show_signal_msg: 1 callbacks suppressed ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify SegvAnalysis: Segfault happened at: 0x7f7332a444b0:Cannot access memory at address 0x7f7332a444b0 PC (0x7f7332a444b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2012294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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() Status in evolution-data-server package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: evolution-data-server 3.47.3-1 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:25 2023 Disassembly: => 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: Mar 21 00:27:22 hostname gnome-control-c[178036]: No gedit is installed here. Colors won't be updated. Please fix your installation. Mar 21 00:27:25 hostname kernel: show_signal_msg: 1 callbacks suppressed ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify SegvAnalysis: Segfault happened at: 0x7f7332a444b0:Cannot access memory at address 0x7f7332a444b0 PC (0x7f7332a444b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2012294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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() Status in evolution-data-server package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: evolution-data-server 3.47.3-1 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:25 2023 Disassembly: => 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: Mar 21 00:27:22 hostname gnome-control-c[178036]: No gedit is installed here. Colors won't be updated. Please fix your installation. Mar 21 00:27:25 hostname kernel: show_signal_msg: 1 callbacks suppressed ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify SegvAnalysis: Segfault happened at: 0x7f7332a444b0:Cannot access memory at address 0x7f7332a444b0 PC (0x7f7332a444b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2012294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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() Status in evolution-data-server package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: evolution-data-server 3.47.3-1 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:25 2023 Disassembly: => 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: Mar 21 00:27:22 hostname gnome-control-c[178036]: No gedit is installed here. Colors won't be updated. Please fix your installation. Mar 21 00:27:25 hostname kernel: show_signal_msg: 1 callbacks suppressed ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify SegvAnalysis: Segfault happened at: 0x7f7332a444b0:Cannot access memory at address 0x7f7332a444b0 PC (0x7f7332a444b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2012294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012295] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2012295/+attachment/5656422/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2012295/+attachment/5655970/+files/CoreDump.gz ** Changed in: ibus (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012295 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() Status in ibus package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:39 2023 Disassembly: => 0x7f4f395714b0: Cannot access memory at address 0x7f4f395714b0 ExecutablePath: /usr/libexec/ibus-extension-gtk3 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/ibus-extension-gtk3 SegvAnalysis: Segfault happened at: 0x7f4f395714b0:Cannot access memory at address 0x7f4f395714b0 PC (0x7f4f395714b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012295] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/2012295/+attachment/5656421/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012295 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() Status in ibus package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:39 2023 Disassembly: => 0x7f4f395714b0: Cannot access memory at address 0x7f4f395714b0 ExecutablePath: /usr/libexec/ibus-extension-gtk3 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/ibus-extension-gtk3 SegvAnalysis: Segfault happened at: 0x7f4f395714b0:Cannot access memory at address 0x7f4f395714b0 PC (0x7f4f395714b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012295] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2012295/+attachment/5656420/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012295 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() Status in ibus package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:39 2023 Disassembly: => 0x7f4f395714b0: Cannot access memory at address 0x7f4f395714b0 ExecutablePath: /usr/libexec/ibus-extension-gtk3 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/ibus-extension-gtk3 SegvAnalysis: Segfault happened at: 0x7f4f395714b0:Cannot access memory at address 0x7f4f395714b0 PC (0x7f4f395714b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012295] ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke()
StacktraceTop: ?? () g_closure_invoke (closure=0x560fe51cf560, return_value=0x0, n_param_values=2, param_values=0x7fffa6f160c0, invocation_hint=0x7fffa6f16040) at ../../../gobject/gclosure.c:832 signal_emit_unlocked_R.isra.0 (node=node@entry=0x560fe50a70f0, detail=detail@entry=795, instance=instance@entry=0x560fe515d2f0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffa6f160c0) at ../../../gobject/gsignal.c:3802 g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7fffa6f16280) 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 Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012295 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() Status in ibus package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:39 2023 Disassembly: => 0x7f4f395714b0: Cannot access memory at address 0x7f4f395714b0 ExecutablePath: /usr/libexec/ibus-extension-gtk3 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/ibus-extension-gtk3 SegvAnalysis: Segfault happened at: 0x7f4f395714b0:Cannot access memory at address 0x7f4f395714b0 PC (0x7f4f395714b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782033] Re: "Alias=" missing from NetworkManager.service
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1782033 Title: "Alias=" missing from NetworkManager.service Status in network-manager package in Ubuntu: Confirmed Bug description: Version: 1.10.6-2ubuntu1 Ubuntu release: 18.04 I've just had a fun few minutes wondering why I couldn't disable NM using "systemctl disable network-manager.service". Looks like the real unit file is NetworkManager.service, and the former is a symlink. Per systemd.unit(5), "unit files may specify aliases through the Alias= directive in the [Install] section" which allows the aliases to be used in systemctl disable etc. - so this might be a cleaner approach and would presumably solve the problem of lusers like me guessing unit names .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1782033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782033] Re: "Alias=" missing from NetworkManager.service
The network-manager package in Bionic and Focal install as symlink to NetworkManager.service correctly: https://packages.ubuntu.com/search?searchon=contents&keywords=network- manager.service&mode=exactfilename&suite=bionic&arch=any https://packages.ubuntu.com/search?searchon=contents&keywords=network- manager.service&mode=exactfilename&suite=focal&arch=any However this has gone missing from Jammy onward: https://packages.ubuntu.com/search?suite=jammy&arch=any&mode=exactfilename&searchon=contents&keywords=network- manager.service https://packages.ubuntu.com/search?suite=kinetic&arch=any&mode=exactfilename&searchon=contents&keywords=network- manager.service https://packages.ubuntu.com/search?suite=lunar&arch=any&mode=exactfilename&searchon=contents&keywords=network- manager.service This can potentially break historical scripts / workloads that use the network-manager.service name and would be nice to fix. Looking at Debian packages, this is present on Stretch (9), Buster (10) and Bullseye (11). It seems like it was dropped with Bookworm, however it was re-added back to Sid. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1782033 Title: "Alias=" missing from NetworkManager.service Status in network-manager package in Ubuntu: Confirmed Bug description: Version: 1.10.6-2ubuntu1 Ubuntu release: 18.04 I've just had a fun few minutes wondering why I couldn't disable NM using "systemctl disable network-manager.service". Looks like the real unit file is NetworkManager.service, and the former is a symlink. Per systemd.unit(5), "unit files may specify aliases through the Alias= directive in the [Install] section" which allows the aliases to be used in systemctl disable etc. - so this might be a cleaner approach and would presumably solve the problem of lusers like me guessing unit names .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1782033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995779] Re: Strange issues with suspend, Nvidia proprietary and X11 graphics
Still happening with Nvidia 525.85.05-0ubuntu0.22.04.1 and Linux 6.1.0-1007-oem. No sign of crashes anywhere. The journal contains the following sequence: Boot. Suspend. Resume. Xorg come up and everything works except the keyboard which is now dead. Suspend. Resume. Stuck on black VT terminal screen. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-520/+bug/1995779/+attachment/5656401/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1995779 Title: Strange issues with suspend, Nvidia proprietary and X11 graphics Status in nvidia-graphics-drivers-520 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: Ubuntu: 22.04 jammy Computer: HP Pavilion All-in-One Desktop 27-ca1xxx So a desktop but with a hybrid GPU setup like a laptop. GPU: NVIDIA GeForce RTX 3050 Laptop GPU + Intel(R) Graphics (ADL-S GT1) GPU driver: This happens with all Nvidia proprietary drivers tested so far, 510, 515, 520. I reported it on the latest. Kernel: This happens with all kernels tested so far from 5.15 to 6.0 Desktop: This only happens with an X11 session! If I switch to Wayland it doesn't happen. Problem: When you suspend the computer a number of strange things may happen. Lose connection to keyboard and mouse. Lose connection to USB-C Audio speakers. Stuck on black VT terminal screen. Sometimes reproduced on first try, sometimes it takes 5 tries. Switching to Wayland allows to suspend/resume perfectly however. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-520/+bug/1995779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870626] Re: /usr/lib/libxcb-atom.so.1 missing in Oneiric
** Changed in: xcb-util (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xcb-util in Ubuntu. https://bugs.launchpad.net/bugs/870626 Title: /usr/lib/libxcb-atom.so.1 missing in Oneiric Status in xcb-util package in Ubuntu: Invalid Bug description: No package in Oneiric provides /usr/lib/libxcb-atom.so.1, this was built from xcb-util in Natty. (Also was important enough to be in ia32-libs.) I found it when I tried to run World of Goo, it complains about a missing dependency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xcb-util/+bug/870626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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. Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: I have no idea what happened here. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 AssertionMessage: gnome-settings-daemon: ../../src/xcb_io.c:273: poll_for_event: Försäkran \"!xcb_xlib_threads_sequence_lost\" falsk. Date: Mon Mar 12 18:00:19 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon Signal: 6 SourcePackage: gnome-settings-daemon StacktraceTop: __assert_fail_base (fmt=, assertion=0x7fd243988b78 "!xcb_xlib_threads_sequence_lost", file=0x7fd243988e32 "../../src/xcb_io.c", line=, function=) at assert.c:94 __GI___assert_fail (assertion=0x7fd243988b78 "!xcb_xlib_threads_sequence_lost", file=0x7fd243988e32 "../../src/xcb_io.c", line=273, function=0x7fd243988f58 "poll_for_event") at assert.c:103 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 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. UpgradeStatus: Upgraded to precise on 2012-02-07 (34 days ago) UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin mythtv plugdev pulse-access sambashare tape users video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/953202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935070] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Released Bug description: [ Impact ] * Calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed, and make sure that alsa-utils is not installed. * Run the ubuntu-drivers list command. * Check that ubuntu-drivers does not complain about the missing aplay tool. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] - ___ ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-drivers-common/+bug/1935070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.6.3.2 --- ubuntu-drivers-common (1:0.9.6.3.2) kinetic; urgency=medium * UbuntuDrivers/detect.py: - Fix "882:5 local variable 'with_nvidia_kms' is assigned to but never used" FTBFS (triggered by tests/test_static.py). ubuntu-drivers-common (1:0.9.6.3.1) kinetic; urgency=medium [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers) (LP: #1935070). -- Alberto Milone Wed, 08 Mar 2023 15:57:25 + ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Released Bug description: [ Impact ] * Calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed, and make sure that alsa-utils is not installed. * Run the ubuntu-drivers list command. * Check that ubuntu-drivers does not complain about the missing aplay tool. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] - ___ ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-drivers-common/+bug/1935070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1993019] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Released Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzh
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.6.3.2 --- ubuntu-drivers-common (1:0.9.6.3.2) kinetic; urgency=medium * UbuntuDrivers/detect.py: - Fix "882:5 local variable 'with_nvidia_kms' is assigned to but never used" FTBFS (triggered by tests/test_static.py). ubuntu-drivers-common (1:0.9.6.3.1) kinetic; urgency=medium [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers) (LP: #1935070). -- Alberto Milone Wed, 08 Mar 2023 15:57:25 + ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Released Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2011383 Title: Slow down my system Status in gnome-shell package in Ubuntu: Incomplete Bug description: After update it's slow down my system. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 11:40:08 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-03 (859 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2023-01-25 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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_
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 Desktop Packages, 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() Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:44~alpha-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/bc1ff846df442e10c2163a5598d9e284da404c11 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2009913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012430] Re: attribute breaks dashes
Here is an example of a website where this bug causes dashes not to show: https://www.dontexist.de/ Firefox on Ubuntu incorrectly renders "MediaWiki-Startseite" as "MediaWiki Startseite". Other browsers and Firefox on other OSes correctly render "MediaWiki-Startseite". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2012430 Title: attribute breaks dashes Status in firefox package in Ubuntu: New Bug description: The attached HTML file should be rendered as two lines of text, one with dashes between the words and one with spaces. However, Firefox renders the file with no dashes whatsoever. Instead of dashes, it shows double-width spaces. The HTML renders correctly if lang="de-x-formal" attribute is changed to lang="de". Please note that de-x-formal is a valid language code, as verified with http://schneegans.de/lv/ and it is found in the HTML generated by MediaWiki when the language is set to de-formal. I also noticed that the extra wide spaces Firefox incorrectly shows instead of dashes are in the ori1Uni font while the regular letters are in DejaVu Serif. With lang="de", everything is in DejaVu Serif, including dashes which render correctly. This problem does not occur with Chromium on Ubuntu, nor with Firefox on Debian, nor Firefox on Windows. Ubuntu version: Ubuntu 22.04.2 LTS Firefox version: firefox 111.0-2 from snap Thank you very much for looking into this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2012430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Triaged Status in gnome-settings-daemon package in Ubuntu: Fix Committed Bug description: [ 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. [ 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Triaged Status in gnome-settings-daemon package in Ubuntu: Fix Committed Bug description: [ 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. [ 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gvfs: New Status in tracker-miners package in Ubuntu: Fix Released Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012430] [NEW] attribute breaks dashes
Public bug reported: The attached HTML file should be rendered as two lines of text, one with dashes between the words and one with spaces. However, Firefox renders the file with no dashes whatsoever. Instead of dashes, it shows double- width spaces. The HTML renders correctly if lang="de-x-formal" attribute is changed to lang="de". Please note that de-x-formal is a valid language code, as verified with http://schneegans.de/lv/ and it is found in the HTML generated by MediaWiki when the language is set to de-formal. I also noticed that the extra wide spaces Firefox incorrectly shows instead of dashes are in the ori1Uni font while the regular letters are in DejaVu Serif. With lang="de", everything is in DejaVu Serif, including dashes which render correctly. This problem does not occur with Chromium on Ubuntu, nor with Firefox on Debian, nor Firefox on Windows. Ubuntu version: Ubuntu 22.04.2 LTS Firefox version: firefox 111.0-2 from snap Thank you very much for looking into this. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: html rendering ** Attachment added: "test.html" https://bugs.launchpad.net/bugs/2012430/+attachment/5656390/+files/test.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2012430 Title: attribute breaks dashes Status in firefox package in Ubuntu: New Bug description: The attached HTML file should be rendered as two lines of text, one with dashes between the words and one with spaces. However, Firefox renders the file with no dashes whatsoever. Instead of dashes, it shows double-width spaces. The HTML renders correctly if lang="de-x-formal" attribute is changed to lang="de". Please note that de-x-formal is a valid language code, as verified with http://schneegans.de/lv/ and it is found in the HTML generated by MediaWiki when the language is set to de-formal. I also noticed that the extra wide spaces Firefox incorrectly shows instead of dashes are in the ori1Uni font while the regular letters are in DejaVu Serif. With lang="de", everything is in DejaVu Serif, including dashes which render correctly. This problem does not occur with Chromium on Ubuntu, nor with Firefox on Debian, nor Firefox on Windows. Ubuntu version: Ubuntu 22.04.2 LTS Firefox version: firefox 111.0-2 from snap Thank you very much for looking into this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2012430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990200] Update Released
The verification of the Stable Release Update for librest has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librest in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Invalid Status in librest package in Ubuntu: Fix Released Status in librest source package in Kinetic: Fix Released Bug description: * Impact The gnome-online-accounts sometime crash after resuming from suspend * Test case Install the librest update, restart your system and verify that configured online accounts keep working. Taking a Google account example, calendar events should show in gnome-calendar and the top panel widget, evolution should list your email account and nautilus should be able to browse your gdrive folder. We should also confirm that error reports stop with the library update * Regression potential The patch makes the code better handle an empty payload. The librest rdepends in the archive are gnome-initial-setup/gnome-online- accounts/gnome-maps so we should verify that those keep working as expected. - Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1990200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990200] Re: goa-daemon crashed with SIGABRT
This bug was fixed in the package librest - 0.9.1-2ubuntu1 --- librest (0.9.1-2ubuntu1) kinetic; urgency=medium * debian/patches/gitlab_goa_abort.patch: cherrypick a fix proposed upstream and already included in Fedora to fix gnome-online-account segfaulting sometime after suspend since libsoup3 (lp: #1990200) -- Sebastien Bacher Tue, 22 Nov 2022 13:51:01 +0100 ** Changed in: librest (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librest in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Invalid Status in librest package in Ubuntu: Fix Released Status in librest source package in Kinetic: Fix Released Bug description: * Impact The gnome-online-accounts sometime crash after resuming from suspend * Test case Install the librest update, restart your system and verify that configured online accounts keep working. Taking a Google account example, calendar events should show in gnome-calendar and the top panel widget, evolution should list your email account and nautilus should be able to browse your gdrive folder. We should also confirm that error reports stop with the library update * Regression potential The patch makes the code better handle an empty payload. The librest rdepends in the archive are gnome-initial-setup/gnome-online- accounts/gnome-maps so we should verify that those keep working as expected. - Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1990200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
And thanks for reporting it to ibus upstream too. :) ** Also affects: ibus via https://github.com/ibus/ibus/issues/2492 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ibus: Unknown Status in ardour package in Ubuntu: New Status in ibus package in Ubuntu: New Status in ardour package in Debian: Unknown Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 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: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
@enorrmann: The latter is valuable info. I submitted an ardour Debian bug, which you should have received a copy of. Please feel free to add relevant info to that bug, if you think that I missed something. ** Also affects: ardour (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1033293 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033293 ** Also affects: ardour (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033293 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ardour package in Ubuntu: New Status in ibus package in Ubuntu: New Status in ardour package in Debian: Unknown Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 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: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ardour/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
reported to ibus https://github.com/ibus/ibus/issues/2492 ** Bug watch added: github.com/ibus/ibus/issues #2492 https://github.com/ibus/ibus/issues/2492 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ardour package in Ubuntu: New Status in ibus package in Ubuntu: New Status in ardour package in Debian: Unknown Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 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: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ardour/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012426] [NEW] yaru-theme-icon package still contains icons to Amazon webstore
Public bug reported: This may be a holdover from the original Suru theme for Ubuntu Touch or related desktop Unity scope integration around that time. Suru was the basis for the Yaru theme icons. https://github.com/snwh/suru-icon-theme https://snwh.org/suru https://github.com/ubuntu/yaru /usr/share/icons/Yaru/48x48/apps/amazon-store.png /usr/share/icons/Yaru/scalable/apps/amazon-store-symbolic.svg /usr/share/icons/Yaru/256x256/apps/amazon-store.png /usr/share/icons/Yaru/16x16/apps/amazon-store.png /usr/share/icons/Yaru/48x48@2x/apps/amazon-store.png /usr/share/icons/Yaru/24x24@2x/apps/amazon-store.png /usr/share/icons/Yaru/32x32/apps/amazon-store.png /usr/share/icons/Yaru/24x24/apps/amazon-store.png /usr/share/icons/Yaru/256x256@2x/apps/amazon-store.png /usr/share/icons/Yaru/16x16@2x/apps/amazon-store.png /usr/share/icons/Yaru/32x32@2x/apps/amazon-store.png ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Affects: yaru-theme (Debian) Importance: Undecided Status: New ** Tags: bionic bloat jammy kinetic lunar yaru ** Also affects: yaru-theme (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2012426 Title: yaru-theme-icon package still contains icons to Amazon webstore Status in yaru-theme package in Ubuntu: New Status in yaru-theme package in Debian: New Bug description: This may be a holdover from the original Suru theme for Ubuntu Touch or related desktop Unity scope integration around that time. Suru was the basis for the Yaru theme icons. https://github.com/snwh/suru-icon-theme https://snwh.org/suru https://github.com/ubuntu/yaru /usr/share/icons/Yaru/48x48/apps/amazon-store.png /usr/share/icons/Yaru/scalable/apps/amazon-store-symbolic.svg /usr/share/icons/Yaru/256x256/apps/amazon-store.png /usr/share/icons/Yaru/16x16/apps/amazon-store.png /usr/share/icons/Yaru/48x48@2x/apps/amazon-store.png /usr/share/icons/Yaru/24x24@2x/apps/amazon-store.png /usr/share/icons/Yaru/32x32/apps/amazon-store.png /usr/share/icons/Yaru/24x24/apps/amazon-store.png /usr/share/icons/Yaru/256x256@2x/apps/amazon-store.png /usr/share/icons/Yaru/16x16@2x/apps/amazon-store.png /usr/share/icons/Yaru/32x32@2x/apps/amazon-store.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2012426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011697] Re: [FFe] Ubuntu Pro integration outside of the LTS
This bug was fixed in the package software-properties - 0.99.34 --- software-properties (0.99.34) lunar; urgency=medium [ Nathan Pratta Teodosio ] * Enable the Ubuntu Pro tab also in interim releases (FFe lp: #2011697) -- Sebastien Bacher Tue, 21 Mar 2023 10:49:45 +0100 ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2011697 Title: [FFe] Ubuntu Pro integration outside of the LTS Status in software-properties package in Ubuntu: Fix Released Bug description: The Ubuntu Pro tab of software-properties-gtk is currently only enabled on LTS series. We would like to activate with a modified UI (to match the restricted set of services available on the serie) for Lunar. There are no changes to the existing backend code compared to what is currently being used in LTS series and the action are done through the 'pro' client so the 'new code' is limited to the UI layout tweaks. The corresponding code changes can be found on https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/438549 and ppa is available which includes a package build with the changes on https://launchpad.net/~nteodosio/+archive/ubuntu/ubuntu-pro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2011697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive
I can confirm this is only present in ardour shipped with ubuntu 23.04 or by compiling ardour from source on ubuntu 23.04. If i run the binary provided by ardour.org, the issue is NOT present -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012146 Title: very high cpu usage, system unresponsive Status in ibus package in Ubuntu: New Bug description: may be related to Ardour 7.3, when I start ardour and start working with the app, the system slows down and htop shows 100% cpu usage for ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 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: Sat Mar 18 15:21:55 2023 InstallationDate: Installed on 2022-05-13 (308 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ibus UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956108] Re: gstreamer1.0-plugins-good requires libraw1394
** Tags added: kinetic lunar ** Also affects: gst-plugins-good1.0 (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1956108 Title: gstreamer1.0-plugins-good requires libraw1394 Status in gst-plugins-good1.0 package in Ubuntu: New Status in gst-plugins-good1.0 package in Debian: New Bug description: Gstreamer requires Firewire library libraw1394. In 2022~. 22.04 Jammy will be supported until 2027~ and until 2032~ under ESM. The official trade association site is shown at their LinkedIn below. https://www.linkedin.com/company/1394-trade-association It is now used to sell Instagram likes. In 2020, their website still listed copyright 2013. The news dates also have a 2013 ceiling. https://web.archive.org/web/20200731001915/http://1394ta.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1956108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2008067 Title: To support Elan fp device [04F3:0C82] Status in OEM Priority Project: Fix Committed Status in libfprint package in Ubuntu: Invalid Status in libfprint source package in Jammy: Fix Released Status in libfprint source package in Kinetic: Invalid Status in libfprint source package in Lunar: Invalid Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/2b760dfa380ceff152ff8105a2aad76d85ec1ddc This ID is included in upstream. [Impact] * Devices have Elan [04F3:0C82] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [04F3:0C82] will be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2008067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990527] Re: Testsuite timeouts on riscv
I guess this is not the case anymore, correct?
** Changed in: adsys (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/1990527
Title:
Testsuite timeouts on riscv
Status in adsys package in Ubuntu:
Incomplete
Bug description:
Please find below the output of the testsuite running on riscv: any
hint on what could be wrong?
=== RUN TestAddStdoutForwarderWithBlockedStdout
time="2022-09-20T13:56:30Z" level=warning msg="Failed to write to regular
output: write |1: file already closed"
panic: test timed out after 10m0s
goroutine 3 [running]:
testing.(*M).startAlarm.func1()
/usr/lib/go-1.19/src/testing/testing.go:2036 +0x8c
created by time.goFunc
/usr/lib/go-1.19/src/time/sleep.go:176 +0x50
goroutine 1 [chan receive]:
testing.(*T).Run(0x3f741881a0, {0x2ad4e93af2?, 0x2ad4ae53a0?}, 0x2ad503d8e8)
/usr/lib/go-1.19/src/testing/testing.go:1494 +0x34c
testing.runTests.func1(0x30?)
/usr/lib/go-1.19/src/testing/testing.go:1846 +0x78
testing.tRunner(0x3f741881a0, 0x3f7415dcf0)
/usr/lib/go-1.19/src/testing/testing.go:1446 +0x11c
testing.runTests(0x3f7414c500?, {0x2ad537b180, 0xa, 0xa}, {0x1?,
0x400ce8?, 0x2ad53c6c60?})
/usr/lib/go-1.19/src/testing/testing.go:1844 +0x408
testing.(*M).Run(0x3f7414c500)
/usr/lib/go-1.19/src/testing/testing.go:1726 +0x504
main.main()
_testmain.go:67 +0x1a8
goroutine 37 [semacquire]:
sync.runtime_Semacquire(0x3f7423e140?)
/usr/lib/go-1.19/src/runtime/sema.go:62 +0x34
sync.(*WaitGroup).Wait(0x3f7421a0d0)
/usr/lib/go-1.19/src/sync/waitgroup.go:139 +0x74
github.com/ubuntu/adsys/internal/stdforward.addWriter.func2()
/home/ubuntu/packages/adsys/adsys-0.9.2/obj-riscv64-linux-gnu/src/github.com/ubuntu/adsys/internal/stdforward/stdforward.go:1
14 +0x13c
github.com/ubuntu/adsys/internal/stdforward_test.TestAddStdoutForwarderWithBlockedStdout(0x3f740b0368?)
/home/ubuntu/packages/adsys/adsys-0.9.2/obj-riscv64-linux-gnu/src/github.com/ubuntu/adsys/internal/stdforward/stdforward_test
.go:273 +0x1e0
testing.tRunner(0x3f74234340, 0x2ad503d8e8)
/usr/lib/go-1.19/src/testing/testing.go:1446 +0x11c
created by testing.(*T).Run
/usr/lib/go-1.19/src/testing/testing.go:1493 +0x338
goroutine 38 [semacquire]:
sync.runtime_SemacquireMutex(0x3f740dc000?, 0x3?, 0x2ad4e924ba?)
/usr/lib/go-1.19/src/runtime/sema.go:77 +0x40
sync.(*RWMutex).RLock(...)
/usr/lib/go-1.19/src/sync/rwmutex.go:71
github.com/ubuntu/adsys/internal/stdforward.(*forwarder).Write(0x2ad53c69c0,
{0x3f74292000, 0x1c, 0x8000})
/home/ubuntu/packages/adsys/adsys-0.9.2/obj-riscv64-linux-gnu/src/github.com/ubuntu/adsys/internal/stdforward/stdforward.go:3
6 +0xe4
io.copyBuffer({0x2ad5041100, 0x2ad53c69c0}, {0x2ad50420c0, 0x3f7423c068},
{0x0, 0x0, 0x0})
/usr/lib/go-1.19/src/io/io.go:429 +0x1d8
io.Copy(...)
/usr/lib/go-1.19/src/io/io.go:386
github.com/ubuntu/adsys/internal/stdforward.addWriter.func1.1()
/home/ubuntu/packages/adsys/adsys-0.9.2/obj-riscv64-linux-gnu/src/github.com/ubuntu/adsys/internal/stdforward/stdforward.go:9
1 +0x80
created by github.com/ubuntu/adsys/internal/stdforward.addWriter.func1
/home/ubuntu/packages/adsys/adsys-0.9.2/obj-riscv64-linux-gnu/src/github.com/ubuntu/adsys/internal/stdforward/stdforward.go:8
9 +0x1b0
FAIL github.com/ubuntu/adsys/internal/stdforward 604.198s
? github.com/ubuntu/adsys/internal/testutils [no test files]
? github.com/ubuntu/adsys/internal/watchdservice [no test files]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1990527/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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_
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 Desktop Packages, 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() Status in gnome-control-center package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:44~alpha-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/bc1ff846df442e10c2163a5598d9e284da404c11 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2009913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gnome-control-center package in Ubuntu: Confirmed Bug description: What Happens All the line art in the Multitasking panel doesn't show up. These are .svg files. All the line art in the Mouse & Touchpad panels doesn't show up. These are .webm files. Other Info -- This is with a clean install of Ubuntu using the March 16 daily image and then updates applied. The art did show on my primary computer which is also running the same version of gnome-control-center but is not a clean install and has many other packages installed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~rc-1ubuntu1 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: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 16 12:42:50 2023 InstallationDate: Installed on 2023-03-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230316) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gvfs: New Status in tracker-miners package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER
*** This bug is a duplicate of bug 1620771 *** https://bugs.launchpad.net/bugs/1620771 > Small update: we have now merged a change that allows snaps to work on system where the users' home directories are not /home// but /home/// If you are running such a system, you are welcome to try out snapd from our > edge channel: >snap refresh --channel=latest/edge snapd sudo snap refresh --channel=latest/edge snapd error: snap "snapd" is not installed systemctl status snapd ● snapd.service - Snap Daemon Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2023-03-21 14:26:26 CET; 28min ago TriggeredBy: ● snapd.socket Main PID: 24213 (snapd) Tasks: 47 (limit: 4915) Memory: 421.5M CGroup: /system.slice/snapd.service └─24213 /usr/lib/snapd/snapd > Please report back on your (mis)fortunes. :-) They are manifold. Worst release upgrade experience ever. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776800 Title: Unable to start snap applications if user's home directory is not /home/$USER Status in snapd: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Confirmed Bug description: Users with home directories in /home/$USER can run snap application, but users in /home/users/$USER can't. nate@WorkstationC:~$ snap --version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-22-generic nate@WorkstationC:~$ echo $HOME /home/users/nate nate@WorkstationC:~$ which hello-world /snap/bin/hello-world nate@WorkstationC:~$ hello-world cannot create nate data directory: /home/users/nate/snap/hello-world/27: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
** Also affects: gsettings-desktop-schemas (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in gsettings-desktop-schemas package in Ubuntu: In Progress Status in subiquity package in Ubuntu: Won't Fix Status in gsettings-desktop-schemas package in Debian: New Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: Unable to focus Windows below system tray (wayland session) Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012288] Re: Ubuntu Gnome Settings / Chrome / CUPS (printing) communications
If not already clear, I cannot print properly -- this setuo is somehow preventing it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2012288 Title: Ubuntu Gnome Settings / Chrome / CUPS (printing) communications Status in cups package in Ubuntu: New Bug description: I am trying to print. Context :: printer - The network printer I have "HP LaserJet Professional M1217nfw MFP" announces itself via Bonjour, supports SLP Config, LPD Printing and WS-Discovery. The printer is wired to ethernet, and receives it's IP address in IPV4 and IPV6 from the router, set statically at the router. Client - The client machine, Ubuntu 22.10 , is either on wireless (192.168.2.X - DHCP assigned randomly) or wired ethernet (192.168.2.Y - DHCP assigned statically). Sometimes the machine has both interfaces as well as receiving IPV6 addresses for both of these interfaces. It's unclear how printing occurs for discovery, but for comparison - Android "just works", iPhone "just works" , and Windows 10 "just works". Only Ubuntu is the outlier here. When printing a PDF from Chrome, I see there is a mismatch between the printers that Chrome sees, and the printers that are registered with the gnome(?) printers configuration settings. This leads me to believe that these 2 parts of printing are not in sync with one another(!!). Additional, possibly related behavior: When I remove all printers listed. And simply watch the Gnome(?) Printers settings section then a new printer is added automatically exactly this text, yes the duplicate 'HP': "HP HP Laserjet Professional M1217nfw MFP, driverless". This may be a cause of issues since I have not configured an additional printer, yet it appears. When I DO attempt to print to this auto-added printer I receive a vague error after some kind of timeout "Stopped Please restart when the problem is resolved" --- what problem ? What is causing the issue ? This error does not help identify the issue. Can you help me understand what is happening here and how this can be resolved ? If auto-adding a printer is going to magically work , then please include detailed, actionable error messages. Attached -- screenshot of printer subsystems mismatch. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 11:54:41 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.19.0-31-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-35-generic, x86_64: installed nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-31-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (64 days ago) dmi.bios.date: 02/09/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET83W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dm
[Desktop-packages] [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 Desktop Packages, 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 Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the options to Restart and Shutdown the system are not working anymore. In Ubuntu 22.10 when you are in the gdm3 login screen and choose Restart or Shutdown it presents a dialog box saying that the action will be auto performed in 60 seconds, with two buttons, one to cancel and another to perform the action at once. In Ubuntu 23.04 choosing Restart or Shutdown does nothing at all... Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 Package: gdm3 43.0-3ubuntu2 PackageArchitecture: arm64 ProcVersionSignature: Ubuntu 5.19.0-1015.22-raspi 5.19.17 Tags: lunar Uname: Linux 5.19.0-1015-raspi aarch64 UpgradeStatus: Upgraded to lunar on 2023-03-20 (0 days ago) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-05-04T11:33:42 mtime.conffile..etc.gdm3.custom.conf: 2023-03-07T19:16:26 mtime.conffile..etc.pam.d.gdm-password: 2022-05-08T18:01:33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gnome-control-center package in Ubuntu: Confirmed Bug description: What Happens All the line art in the Multitasking panel doesn't show up. These are .svg files. All the line art in the Mouse & Touchpad panels doesn't show up. These are .webm files. Other Info -- This is with a clean install of Ubuntu using the March 16 daily image and then updates applied. The art did show on my primary computer which is also running the same version of gnome-control-center but is not a clean install and has many other packages installed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~rc-1ubuntu1 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: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 16 12:42:50 2023 InstallationDate: Installed on 2023-03-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230316) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
@slyon thanks, I have manually tested and seems to work. I've created https://github.com/snapcore/network-manager-snap/pull/15, let's see how tests go. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Invalid Status in network-manager package in Ubuntu: Triaged Bug description: *** Note: This bug is mostly about comment #10, now *** When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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() Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about
[Desktop-packages] [Bug 2003956] Re: package firefox 109.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2003956 Title: package firefox 109.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 Status in firefox package in Ubuntu: Confirmed Bug description: The upgrade from 20.04 to 22.04 failed which caused by can not upgrade firefox. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 109.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patten11134 F pulseaudio BuildID: 20230112150232 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Jan 26 21:17:07 2023 ErrorMessage: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-07-30 (1276 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 172.16.228.0/24 dev vmnet1 proto kernel scope link src 172.16.228.1 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600 192.168.142.0/24 dev vmnet8 proto kernel scope link src 192.168.142.1 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 109.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 UpgradeStatus: Upgraded to jammy on 2023-01-26 (0 days ago) dmi.bios.date: 03/21/2022 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd03/21/2022:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2003956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012371] Re: [FFe] ubuntu-proxy-manager and adsys
** Description changed: Ubuntu Proxy Manager is a D-Bus mediated service that allows for managing system proxy settings via multiple backends (APT, environment variables and GSettings). We request a FFe for this new source package (ubuntu-proxy-manager). As it's a new source package the risk of it breaking existing setups is non-existent as it must be explicitly opted into by users. The package is written in Go and benefits from an extensive test suite covering over 90% of the codebase. Additionally, we would like to request a FFe for adsys where we added a Suggests dependency on ubuntu-proxy-manager. We have taken great care on the adsys part to maintain backwards compatibility and not affect users who do not install the ubuntu-proxy-manager package. + Installing the ubuntu-proxy-manager package on its own has no impact to + the system. To benefit from its functionality adsys has to be upgraded + and correctly configured. + - Relevant URLs: 1. ubuntu-proxy-manager homepage: https://github.com/ubuntu/ubuntu-proxy-manager 2. ubuntu-proxy-manager implementation in ADSys: https://github.com/ubuntu/adsys/pull/637 3. LP build of ubuntu-proxy-manager: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562796/+listing-archive-extra 4. LP build of adsys: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562807/+listing-archive-extra -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2012371 Title: [FFe] ubuntu-proxy-manager and adsys Status in adsys package in Ubuntu: New Bug description: Ubuntu Proxy Manager is a D-Bus mediated service that allows for managing system proxy settings via multiple backends (APT, environment variables and GSettings). We request a FFe for this new source package (ubuntu-proxy-manager). As it's a new source package the risk of it breaking existing setups is non-existent as it must be explicitly opted into by users. The package is written in Go and benefits from an extensive test suite covering over 90% of the codebase. Additionally, we would like to request a FFe for adsys where we added a Suggests dependency on ubuntu-proxy-manager. We have taken great care on the adsys part to maintain backwards compatibility and not affect users who do not install the ubuntu-proxy-manager package. Installing the ubuntu-proxy-manager package on its own has no impact to the system. To benefit from its functionality adsys has to be upgraded and correctly configured. - Relevant URLs: 1. ubuntu-proxy-manager homepage: https://github.com/ubuntu/ubuntu-proxy-manager 2. ubuntu-proxy-manager implementation in ADSys: https://github.com/ubuntu/adsys/pull/637 3. LP build of ubuntu-proxy-manager: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562796/+listing-archive-extra 4. LP build of adsys: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562807/+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2012371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012371] [NEW] [FFe] ubuntu-proxy-manager and adsys
Public bug reported: Ubuntu Proxy Manager is a D-Bus mediated service that allows for managing system proxy settings via multiple backends (APT, environment variables and GSettings). We request a FFe for this new source package (ubuntu-proxy-manager). As it's a new source package the risk of it breaking existing setups is non-existent as it must be explicitly opted into by users. The package is written in Go and benefits from an extensive test suite covering over 90% of the codebase. Additionally, we would like to request a FFe for adsys where we added a Suggests dependency on ubuntu-proxy-manager. We have taken great care on the adsys part to maintain backwards compatibility and not affect users who do not install the ubuntu-proxy-manager package. - Relevant URLs: 1. ubuntu-proxy-manager homepage: https://github.com/ubuntu/ubuntu-proxy-manager 2. ubuntu-proxy-manager implementation in ADSys: https://github.com/ubuntu/adsys/pull/637 3. LP build of ubuntu-proxy-manager: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562796/+listing-archive-extra 4. LP build of adsys: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562807/+listing-archive-extra ** Affects: adsys (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2012371 Title: [FFe] ubuntu-proxy-manager and adsys Status in adsys package in Ubuntu: New Bug description: Ubuntu Proxy Manager is a D-Bus mediated service that allows for managing system proxy settings via multiple backends (APT, environment variables and GSettings). We request a FFe for this new source package (ubuntu-proxy-manager). As it's a new source package the risk of it breaking existing setups is non-existent as it must be explicitly opted into by users. The package is written in Go and benefits from an extensive test suite covering over 90% of the codebase. Additionally, we would like to request a FFe for adsys where we added a Suggests dependency on ubuntu-proxy-manager. We have taken great care on the adsys part to maintain backwards compatibility and not affect users who do not install the ubuntu-proxy-manager package. - Relevant URLs: 1. ubuntu-proxy-manager homepage: https://github.com/ubuntu/ubuntu-proxy-manager 2. ubuntu-proxy-manager implementation in ADSys: https://github.com/ubuntu/adsys/pull/637 3. LP build of ubuntu-proxy-manager: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562796/+listing-archive-extra 4. LP build of adsys: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562807/+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2012371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2011790 Title: Night Light doesn't work in gnome-shell 44.rc Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Bug description: 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the options to Restart and Shutdown the system are not working anymore. In Ubuntu 22.10 when you are in the gdm3 login screen and choose Restart or Shutdown it presents a dialog box saying that the action will be auto performed in 60 seconds, with two buttons, one to cancel and another to perform the action at once. In Ubuntu 23.04 choosing Restart or Shutdown does nothing at all... Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gdm3 gdm3: Instalados: 43.0-3ubuntu2 Candidato: 43.0-3ubuntu2 Tabla de versión: *** 43.0-3ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 Package: gdm3 43.0-3ubuntu2 PackageArchitecture: arm64 ProcVersionSignature: Ubuntu 5.19.0-1015.22-raspi 5.19.17 Tags: lunar Uname: Linux 5.19.0-1015-raspi aarch64 UpgradeStatus: Upgraded to lunar on 2023-03-20 (0 days ago) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-05-04T11:33:42 mtime.conffile..etc.gdm3.custom.conf: 2023-03-07T19:16:26 mtime.conffile..etc.pam.d.gdm-password: 2022-05-08T18:01:33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2012311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
