[Desktop-packages] [Bug 2011751] Re: openbox crashed with SIGABRT
One worry I am having with my patch now is, what happens if the first element is the one being modified? Then itPrev is a null pointer. I *think* from looking at the GLib code that g_list_next will then return null when it it handed itPrev, which means "it" will be set to null, which I believe will trigger the end of the loop. Assuming I know what I'm looking at, that could put Openbox in an unusual state that could cause problems later down the road. To get around that, I can add a check to see if itPrev is null, and if so, it will set "it" to stacking_list, which is where it is supposed to end up. (I'm trying to *not* use the patch from Arch Linux's forums, since I really hate the fact that it has to loop through a bunch of the list every time it modifies an element. That seems quite inefficient.) -- 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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Fresh install of Ubuntu 22.04 and still happening WILL THIS EVER GET FIXED It's been FIVE YEARS since this first came up (other bugs), and SMB1 has been off for security reasons for many years now. This User eXperience is completely garbage, frankly. And no user should realistically be expected to have to open a cli and kill gvfsd-smb-browse just because we don't have a proper implementation for this. It truly begs the question, WHY DOES THIS WORK WHEN THAT PROCESS IS RESTARTED? If restarting it "fixers" it, then why on earth does it break in the first place? And why isn't this already fixed? For humans in the future, use this command for convenience: killall gvfsd-smb-browse And then ctrl+r for future quick recall (in the CLI of your desire). -- 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/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 2012556] Re: GNOME Magnifier: Performance issues with Pipewire and OBS
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2012556 Title: GNOME Magnifier: Performance issues with Pipewire and OBS Status in Mutter: Unknown Status in PipeWire: Unknown Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: Timeline: 1. (March 11, 2023) I have uploaded a video regarding the problems with GNOME Magnifier. https://odysee.com/@GraysonPeddie:6/gnome-mag-obs:5 2. (March 11, 2023) I filed a bug report on Pipewire. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3087 3. (March 14, 2023) I uploaded another short video with pw-top (Pipewire) running on the terminal. https://odysee.com/@GraysonPeddie:6/gnomemag-pwtop-obs-pipewire:d 4. (March 14, 2023) I filed a bug report on GNOME Mutter's issue tracker and referenced the two videos and a bug report from Pipewire, but I get no response from the Mutter team. https://gitlab.gnome.org/GNOME/mutter/-/issues/2698 Affected GNOME versions and why I am filing the bug here: This affects GNOME 42, GNOME 43, and GNOME 44. For GNOME 42 and 43, I used Nobara 36 and 37. Nobara is based on Fedora but includes patches for gaming and content creation. I wanted to try out GNOME 44 in Ubuntu 23.04 and I managed to run OBS with Pipewire Screen Sharing, but then the performance with GNOME Magnifier is very sluggish and it froze my entire computer. I've had to restart my computer, but for some reason, GNOME 44 won't load and I've had to go back to Nobara as that is my distro of choice for gaming. This issue with GNOME not loading is beyond the scope of the bug report. So in short, all the recent versions of GNOME (up to 44) are affected regardless of which Linux distribution I use. The reason why I need to file a bug here is because I do not get a response from the Mutter team and I'm at a standstill with Pipewire as they cannot diagnose the problem that I am having. I could test the issue in Ubuntu 22.04 and 22.10, but unfortunately, I do not have another computer to test. On top of that, even if I could install OBS in a live USB image of Ubuntu 22.04 and 22.10, I have an NVIDIA GPU and the GNOME Magnifier is sluggish with Nouveau driver, but again, that is beyond the scope of this issue that I am having. Specs: AMD Ryzen 9 5900X CPU 32GB of RAM NVIDIA GeForce RTX 3060 Ti Resolution: 3840x2160 at 60Hz What I'm Expecting to Happen: The performance with GNOME Magnifier and Pipewire screen capturing with OBS should be smooth. Actual Behavior: Please refer to the two videos in the Timeline section. Steps to Reproduce: In order to reproduce an issue, OBS needs to be installed. However, I am not sure if this is only related to OBS, but that is the only software I use for screen capturing and with support for JACK. 1. Open OBS. 2. Under Sources, press the Add (+) button. 3. Select "Screen Capture (Pipewire)." 4. Select the monitor and press "Share." The screen capture should show up on the preview area of OBS. 5. Open the Settings from either the Overview or the Quick Settings Menu. 6. Scroll down to Accessibility and turn on Zoom. Move your mouse around and you should see performance issues with GNOME Magnifier when doing screen capturing using Pipewire. This affects both Xorg and Wayland. Questions: Is there anything else that I am missing? Should I only test this in Ubuntu even though it's not Ubuntu-specific? Besides, the supported Ubuntu versions should all be affected by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012556/+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 2012556] Re: GNOME Magnifier: Performance issues with Pipewire and OBS
** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3087 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3087 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3087 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2698 https://gitlab.gnome.org/GNOME/mutter/-/issues/2698 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2698 Importance: Unknown Status: Unknown ** Tags added: nvidia performance -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2012556 Title: GNOME Magnifier: Performance issues with Pipewire and OBS Status in Mutter: Unknown Status in PipeWire: Unknown Status in mutter package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: Timeline: 1. (March 11, 2023) I have uploaded a video regarding the problems with GNOME Magnifier. https://odysee.com/@GraysonPeddie:6/gnome-mag-obs:5 2. (March 11, 2023) I filed a bug report on Pipewire. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3087 3. (March 14, 2023) I uploaded another short video with pw-top (Pipewire) running on the terminal. https://odysee.com/@GraysonPeddie:6/gnomemag-pwtop-obs-pipewire:d 4. (March 14, 2023) I filed a bug report on GNOME Mutter's issue tracker and referenced the two videos and a bug report from Pipewire, but I get no response from the Mutter team. https://gitlab.gnome.org/GNOME/mutter/-/issues/2698 Affected GNOME versions and why I am filing the bug here: This affects GNOME 42, GNOME 43, and GNOME 44. For GNOME 42 and 43, I used Nobara 36 and 37. Nobara is based on Fedora but includes patches for gaming and content creation. I wanted to try out GNOME 44 in Ubuntu 23.04 and I managed to run OBS with Pipewire Screen Sharing, but then the performance with GNOME Magnifier is very sluggish and it froze my entire computer. I've had to restart my computer, but for some reason, GNOME 44 won't load and I've had to go back to Nobara as that is my distro of choice for gaming. This issue with GNOME not loading is beyond the scope of the bug report. So in short, all the recent versions of GNOME (up to 44) are affected regardless of which Linux distribution I use. The reason why I need to file a bug here is because I do not get a response from the Mutter team and I'm at a standstill with Pipewire as they cannot diagnose the problem that I am having. I could test the issue in Ubuntu 22.04 and 22.10, but unfortunately, I do not have another computer to test. On top of that, even if I could install OBS in a live USB image of Ubuntu 22.04 and 22.10, I have an NVIDIA GPU and the GNOME Magnifier is sluggish with Nouveau driver, but again, that is beyond the scope of this issue that I am having. Specs: AMD Ryzen 9 5900X CPU 32GB of RAM NVIDIA GeForce RTX 3060 Ti Resolution: 3840x2160 at 60Hz What I'm Expecting to Happen: The performance with GNOME Magnifier and Pipewire screen capturing with OBS should be smooth. Actual Behavior: Please refer to the two videos in the Timeline section. Steps to Reproduce: In order to reproduce an issue, OBS needs to be installed. However, I am not sure if this is only related to OBS, but that is the only software I use for screen capturing and with support for JACK. 1. Open OBS. 2. Under Sources, press the Add (+) button. 3. Select "Screen Capture (Pipewire)." 4. Select the monitor and press "Share." The screen capture should show up on the preview area of OBS. 5. Open the Settings from either the Overview or the Quick Settings Menu. 6. Scroll down to Accessibility and turn on Zoom. Move your mouse around and you should see performance issues with GNOME Magnifier when doing screen capturing using Pipewire. This affects both Xorg and Wayland. Questions: Is there anything else that I am missing? Should I only test this in Ubuntu even though it's not Ubuntu-specific? Besides, the supported Ubuntu versions should all be affected by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012556/+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 1974293] Re: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
Hi @vanvugt, Sure, I changed this bug to public. ** Information type changed from Private to Public -- 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/1974293 Title: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 [Summary] User will be logged out to landing page automatically when performing the Media Control hotkey case. [Steps to reproduce] 1. Boot into OS 2. Run "checkbox-cli com.canonical.certification::keys/media-control" 3. Press the "play & pause" hotkey (next to the microphone mute key) 4. Press left arrow button to move the focus to the "skip" button and then press enter Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() 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/oem-priority/+bug/1974293/+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 2012569] Re: gnome-shell crashed with SIGSEGV in g_object_unref()
*** This bug is a duplicate of bug 1974293 *** https://bugs.launchpad.net/bugs/1974293 ** This bug is no longer a duplicate of private bug 2012502 ** This bug has been marked a duplicate of private bug 1974293 -- 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/2012569 Title: gnome-shell crashed with SIGSEGV in g_object_unref() Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crash many times ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 23 00:31:39 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-03-22 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230322) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-102.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012569/+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 2012556] Re: GNOME Magnifier: Performance issues with Pipewire and OBS
I'm not sure if this bug should be filed against the mutter package or the gnome-shell itself. ** Package changed: ubuntu => mutter (Ubuntu) -- 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/2012556 Title: GNOME Magnifier: Performance issues with Pipewire and OBS Status in mutter package in Ubuntu: New Bug description: Timeline: 1. (March 11, 2023) I have uploaded a video regarding the problems with GNOME Magnifier. https://odysee.com/@GraysonPeddie:6/gnome-mag-obs:5 2. (March 11, 2023) I filed a bug report on Pipewire. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3087 3. (March 14, 2023) I uploaded another short video with pw-top (Pipewire) running on the terminal. https://odysee.com/@GraysonPeddie:6/gnomemag-pwtop-obs-pipewire:d 4. (March 14, 2023) I filed a bug report on GNOME Mutter's issue tracker and referenced the two videos and a bug report from Pipewire, but I get no response from the Mutter team. https://gitlab.gnome.org/GNOME/mutter/-/issues/2698 Affected GNOME versions and why I am filing the bug here: This affects GNOME 42, GNOME 43, and GNOME 44. For GNOME 42 and 43, I used Nobara 36 and 37. Nobara is based on Fedora but includes patches for gaming and content creation. I wanted to try out GNOME 44 in Ubuntu 23.04 and I managed to run OBS with Pipewire Screen Sharing, but then the performance with GNOME Magnifier is very sluggish and it froze my entire computer. I've had to restart my computer, but for some reason, GNOME 44 won't load and I've had to go back to Nobara as that is my distro of choice for gaming. This issue with GNOME not loading is beyond the scope of the bug report. So in short, all the recent versions of GNOME (up to 44) are affected regardless of which Linux distribution I use. The reason why I need to file a bug here is because I do not get a response from the Mutter team and I'm at a standstill with Pipewire as they cannot diagnose the problem that I am having. I could test the issue in Ubuntu 22.04 and 22.10, but unfortunately, I do not have another computer to test. On top of that, even if I could install OBS in a live USB image of Ubuntu 22.04 and 22.10, I have an NVIDIA GPU and the GNOME Magnifier is sluggish with Nouveau driver, but again, that is beyond the scope of this issue that I am having. Specs: AMD Ryzen 9 5900X CPU 32GB of RAM NVIDIA GeForce RTX 3060 Ti Resolution: 3840x2160 at 60Hz What I'm Expecting to Happen: The performance with GNOME Magnifier and Pipewire screen capturing with OBS should be smooth. Actual Behavior: Please refer to the two videos in the Timeline section. Steps to Reproduce: In order to reproduce an issue, OBS needs to be installed. However, I am not sure if this is only related to OBS, but that is the only software I use for screen capturing and with support for JACK. 1. Open OBS. 2. Under Sources, press the Add (+) button. 3. Select "Screen Capture (Pipewire)." 4. Select the monitor and press "Share." The screen capture should show up on the preview area of OBS. 5. Open the Settings from either the Overview or the Quick Settings Menu. 6. Scroll down to Accessibility and turn on Zoom. Move your mouse around and you should see performance issues with GNOME Magnifier when doing screen capturing using Pipewire. This affects both Xorg and Wayland. Questions: Is there anything else that I am missing? Should I only test this in Ubuntu even though it's not Ubuntu-specific? Besides, the supported Ubuntu versions should all be affected by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012556/+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 2012556] [NEW] GNOME Magnifier: Performance issues with Pipewire and OBS
You have been subscribed to a public bug: Timeline: 1. (March 11, 2023) I have uploaded a video regarding the problems with GNOME Magnifier. https://odysee.com/@GraysonPeddie:6/gnome-mag-obs:5 2. (March 11, 2023) I filed a bug report on Pipewire. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3087 3. (March 14, 2023) I uploaded another short video with pw-top (Pipewire) running on the terminal. https://odysee.com/@GraysonPeddie:6/gnomemag-pwtop-obs-pipewire:d 4. (March 14, 2023) I filed a bug report on GNOME Mutter's issue tracker and referenced the two videos and a bug report from Pipewire, but I get no response from the Mutter team. https://gitlab.gnome.org/GNOME/mutter/-/issues/2698 Affected GNOME versions and why I am filing the bug here: This affects GNOME 42, GNOME 43, and GNOME 44. For GNOME 42 and 43, I used Nobara 36 and 37. Nobara is based on Fedora but includes patches for gaming and content creation. I wanted to try out GNOME 44 in Ubuntu 23.04 and I managed to run OBS with Pipewire Screen Sharing, but then the performance with GNOME Magnifier is very sluggish and it froze my entire computer. I've had to restart my computer, but for some reason, GNOME 44 won't load and I've had to go back to Nobara as that is my distro of choice for gaming. This issue with GNOME not loading is beyond the scope of the bug report. So in short, all the recent versions of GNOME (up to 44) are affected regardless of which Linux distribution I use. The reason why I need to file a bug here is because I do not get a response from the Mutter team and I'm at a standstill with Pipewire as they cannot diagnose the problem that I am having. I could test the issue in Ubuntu 22.04 and 22.10, but unfortunately, I do not have another computer to test. On top of that, even if I could install OBS in a live USB image of Ubuntu 22.04 and 22.10, I have an NVIDIA GPU and the GNOME Magnifier is sluggish with Nouveau driver, but again, that is beyond the scope of this issue that I am having. Specs: AMD Ryzen 9 5900X CPU 32GB of RAM NVIDIA GeForce RTX 3060 Ti Resolution: 3840x2160 at 60Hz What I'm Expecting to Happen: The performance with GNOME Magnifier and Pipewire screen capturing with OBS should be smooth. Actual Behavior: Please refer to the two videos in the Timeline section. Steps to Reproduce: In order to reproduce an issue, OBS needs to be installed. However, I am not sure if this is only related to OBS, but that is the only software I use for screen capturing and with support for JACK. 1. Open OBS. 2. Under Sources, press the Add (+) button. 3. Select "Screen Capture (Pipewire)." 4. Select the monitor and press "Share." The screen capture should show up on the preview area of OBS. 5. Open the Settings from either the Overview or the Quick Settings Menu. 6. Scroll down to Accessibility and turn on Zoom. Move your mouse around and you should see performance issues with GNOME Magnifier when doing screen capturing using Pipewire. This affects both Xorg and Wayland. Questions: Is there anything else that I am missing? Should I only test this in Ubuntu even though it's not Ubuntu-specific? Besides, the supported Ubuntu versions should all be affected by this issue. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- GNOME Magnifier: Performance issues with Pipewire and OBS https://bugs.launchpad.net/bugs/2012556 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. -- 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 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_no
This bug was fixed in the package gnome-control-center - 1:44.0-1ubuntu2 --- gnome-control-center (1:44.0-1ubuntu2) lunar; urgency=medium * Drop (again) update_region() call with NULL argument (LP: #2012552) -- Gunnar Hjalmarsson Wed, 22 Mar 2023 23:43:31 +0100 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2012552 Title: /usr/libexec/accounts- daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now Status in accountsservice package in Ubuntu: New Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding accountsservice. This problem was most recently seen with package version 22.08.8-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/8aec6774e070650ea5d4ded3cd3d4c0ebdbf9335 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/accountsservice/+bug/2012552/+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 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_no
I think I found it: https://salsa.debian.org/gnome-team/gnome-control- center/-/commit/5400a142 Uploaded g-c-c, but keeping the accountsservice task open for now until we see that the problem is no longer present. ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2012552 Title: /usr/libexec/accounts- daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now Status in accountsservice package in Ubuntu: New Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding accountsservice. This problem was most recently seen with package version 22.08.8-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/8aec6774e070650ea5d4ded3cd3d4c0ebdbf9335 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/accountsservice/+bug/2012552/+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 1998267] Re: glib not aware of snap confinement
** Changed in: glib2.0 (Ubuntu Kinetic) Status: New => Won't Fix -- 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/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: New Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+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 1998267] Re: glib not aware of snap confinement
** Description changed: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] + + (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. -- 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/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: New Status in glib2.0 source package in Kinetic: New Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+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 2012507] Re: No-change rebuilds needed for splix in lunar
This bug was fixed in the package splix - 2.0.0+svn315-7fakesync1build4 --- splix (2.0.0+svn315-7fakesync1build4) lunar; urgency=high * No change rebuild for jbigkit security update (LP: #2012507). -- Till Kamppeter Wed, 22 Mar 2023 20:29:10 +0100 ** Changed in: splix (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to splix in Ubuntu. https://bugs.launchpad.net/bugs/2012507 Title: No-change rebuilds needed for splix in lunar Status in splix package in Ubuntu: Fix Released Bug description: The last security update made to the jbigkit package introduced an ABI change. Package splix depends on jbigkit, and it declares variables and calls functions which are related to this ABI change. Because a few months have passed since the release of this jbigkit security update (2022-11), instead of reverting that change, it might be best to rebuild splix in lunar (Ubuntu 23.04), and have it be built considering the new jbigkit code, to avoid issues related to the ABI change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/2012507/+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 2012569] Re: gnome-shell crashed with SIGSEGV in g_object_unref()
*** This bug is a duplicate of bug 2012502 *** https://bugs.launchpad.net/bugs/2012502 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2012502, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2012569/+attachment/5656688/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2012569/+attachment/5656690/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2012569/+attachment/5656694/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2012569/+attachment/5656695/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2012569/+attachment/5656696/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2012569/+attachment/5656699/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2012569/+attachment/5656700/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 2012502 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/2012569 Title: gnome-shell crashed with SIGSEGV in g_object_unref() Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crash many times ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 23 00:31:39 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-03-22 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230322) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-102.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012569/+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 2012560] Re: nautilus crashing while copying files
related dmesg: [ 1641.397637] nautilus[6760]: segfault at 55aa ip 7f8d3162283b sp 7ffe1adc11e0 error 4 in libgobject-2.0.so.0.7503.0[7f8d3161d000+34000] likely on CPU 5 (core 1, socket 0) [ 1641.397649] Code: 0f 1e fa 41 54 55 53 48 81 ec d0 00 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 c8 00 00 00 31 c0 48 85 ff 0f 84 2d 02 00 00 <0f> b7 07 48 89 fb 66 25 ff 7f 0f 84 55 02 00 00 66 83 f8 01 75 05 [ 2384.346470] nautilus[9069]: segfault at 0 ip sp 7fff32198f98 error 14 likely on CPU 2 (core 2, socket 0) [ 2384.346478] Code: Unable to access opcode bytes at 0xffd6. [ 2495.219177] traps: nautilus[9749] general protection fault ip:7fe23390a556 sp:7fff3ea4df00 error:0 in libglib-2.0.so.0.7503.0[7fe2338ea000+9a000] [ 3551.817229] nautilus[9904]: segfault at 0 ip sp 7fff563e5268 error 14 in .glXX (deleted)[4029+2000] likely on CPU 3 (core 3, socket 0) [ 3551.817240] Code: Unable to access opcode bytes at 0xffd6. -- 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/2012560 Title: nautilus crashing while copying files Status in nautilus package in Ubuntu: New Bug description: nautilus crashing while copying files, no further details know. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44~rc-1ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 21:42:57 2023 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1426, 828)' InstallationDate: Installed on 2021-11-17 (490 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-03-15 (7 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.47.92-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2012560/+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 2012560] [NEW] nautilus crashing while copying files
Public bug reported: nautilus crashing while copying files, no further details know. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44~rc-1ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 21:42:57 2023 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1426, 828)' InstallationDate: Installed on 2021-11-17 (490 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-03-15 (7 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.47.92-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- 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/2012560 Title: nautilus crashing while copying files Status in nautilus package in Ubuntu: New Bug description: nautilus crashing while copying files, no further details know. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44~rc-1ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 21:42:57 2023 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1426, 828)' InstallationDate: Installed on 2021-11-17 (490 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-03-15 (7 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.47.92-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2012560/+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 2009944] Re: [BPO] libreoffice 7.4.6 for bionic, focal and jammy
Wow someone got crazy with the epoch, jumping from 1 to 4! Wonder what happened there... (not relevant to this backport, just surprising ;-) It LGTM, but the backport-from is still in kinetic-proposed (from lp: 2009354), so we need to wait for that to migrate into kinetic-updates first. Also for the backport to bionic, just keep in mind that after the bionic repo closes (in a month-ish), we won't be able to backport to it, so this might be the last version in bionic-backports. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2009944 Title: [BPO] libreoffice 7.4.6 for bionic, focal and jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: In Progress Status in libreoffice source package in Focal: In Progress Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2009354 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in bionic-/focal-backports [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.6-0ubuntu0.22.10.1 * Backport targets are the Bionic/18.04, Focal/20.04 and Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1717/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Bionic/18.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541804/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20230311_021721_5528d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20230311_022133_e8482@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20230311_034543_5547f@/log.gz * [i386l] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20230311_024716_6fc50@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20230311_013201_6dbb2@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20230311_013952_49140@/log.gz Focal/20.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541807/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20230311_001616_c1e3a@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20230310_164346_4ac1d@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20230311_052748_8b7c3@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20230310_151809_05c21@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20230310_190707_a5b67@/log.gz Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541810/+listing-archive-extra * [amd64]
[Desktop-packages] [Bug 2012547] Re: Please sync deja-dup 44.0-2 from Debain unstable
This bug was fixed in the package deja-dup - 44.0-2 Sponsored for Nathan Teodosio (nteodosio) --- deja-dup (44.0-2) unstable; urgency=medium * debian/control: - Suggests: python3-pydrive2 * debian/rules: - set -Dpydrive_pkgs=python3-pydrive2 since it's not available in Debian * debian/patches/disable-google-drive.patch: - removed, it's not needed anymore -- Sebastien Bacher Mon, 16 Jan 2023 16:51:50 +0100 ** Changed in: deja-dup (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/2012547 Title: Please sync deja-dup 44.0-2 from Debain unstable Status in deja-dup package in Ubuntu: Fix Released Bug description: The latest Debian version of Deja Dup is ---> deja-dup (44.0-2) unstable; urgency=medium * debian/control: - Suggests: python3-pydrive2 * debian/rules: - set -Dpydrive_pkgs=python3-pydrive2 since it's not available in Debian * debian/patches/disable-google-drive.patch: - removed, it's not needed anymore -- Sebastien Bacher Mon, 16 Jan 2023 16:51:50 +0100 <--- That was exactly the delta Ubuntu carried, except that Ubuntu had python3-pydrive while Debian, python3-pydrive2. But since Ubuntu already has the latter too, this can be synced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2012547/+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 2012554] [NEW] /usr/bin/nautilus:7:nautilus_view_model_get_item_from_file:on_clipboard_contents_received:g_task_return_now:complete_in_idle_cb:g_main_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:44~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/44bae1bf7681374aaef2d080a0e76f0a67b9e9a2 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/. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- 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/2012554 Title: /usr/bin/nautilus:7:nautilus_view_model_get_item_from_file:on_clipboard_contents_received:g_task_return_now:complete_in_idle_cb:g_main_dispatch Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:44~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/44bae1bf7681374aaef2d080a0e76f0a67b9e9a2 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/nautilus/+bug/2012554/+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 2012555] [NEW] /usr/bin/nautilus:ERROR:../src/nautilus-window-slot.c:3140:nautilus_window_slot_set_allow_stop: assertion failed: (NAUTILUS_IS_WINDOW_SLOT (self))
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:44~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/6d7d1ce4f09f98dd5f876dfd282d5d6d0ae811cd 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/. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- 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/2012555 Title: /usr/bin/nautilus:ERROR:../src/nautilus-window- slot.c:3140:nautilus_window_slot_set_allow_stop: assertion failed: (NAUTILUS_IS_WINDOW_SLOT (self)) Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:44~rc-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/6d7d1ce4f09f98dd5f876dfd282d5d6d0ae811cd 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/nautilus/+bug/2012555/+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 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_no
The package didn't change but the reports are new, perhaps a new side effect of https://gitlab.gnome.org/GNOME/glib/-/issues/2937 exposing an existing bug? ** Tags added: rls-ll-incoming ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2937 https://gitlab.gnome.org/GNOME/glib/-/issues/2937 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2012552 Title: /usr/libexec/accounts- daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now Status in accountsservice package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding accountsservice. This problem was most recently seen with package version 22.08.8-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/8aec6774e070650ea5d4ded3cd3d4c0ebdbf9335 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/accountsservice/+bug/2012552/+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 2012552] [NEW] /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding accountsservice. This problem was most recently seen with package version 22.08.8-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/8aec6774e070650ea5d4ded3cd3d4c0ebdbf9335 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/. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: lunar rls-ll-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2012552 Title: /usr/libexec/accounts- daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now Status in accountsservice package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding accountsservice. This problem was most recently seen with package version 22.08.8-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/8aec6774e070650ea5d4ded3cd3d4c0ebdbf9335 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/accountsservice/+bug/2012552/+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 2012506] Re: No-change rebuilds needed for foo2zjs in lunar
This bug was fixed in the package foo2zjs - 20200505dfsg0-2ubuntu3 --- foo2zjs (20200505dfsg0-2ubuntu3) lunar; urgency=medium * No change rebuild for jbigkit security update (LP: #2012506) -- Camila Camargo de Matos Tue, 21 Mar 2023 17:58:24 -0300 ** Changed in: foo2zjs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foo2zjs in Ubuntu. https://bugs.launchpad.net/bugs/2012506 Title: No-change rebuilds needed for foo2zjs in lunar Status in foo2zjs package in Ubuntu: Fix Released Bug description: The last security update made to the jbigkit package introduced an ABI change. Package foo2zjs depends on jbigkit, and it declares variables and calls functions which are related to this ABI change. Because a few months have passed since the release of this jbigkit security update (2022-11), instead of reverting that change, it might be best to rebuild foo2zjs in lunar (Ubuntu 23.04), and have it be built considering the new jbigkit code, to avoid issues related to the ABI change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/2012506/+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 2012550] [NEW] /usr/bin/gjs-console:6:g_assertion_message:g_assertion_message_expr:gsk_renderer_dispose:gsk_renderer_dispose:g_object_unref
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.75.90-1, the problem page at https://errors.ubuntu.com/problem/031c8ecfc5e8a51d75d6a028554e9c5354792705 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/. ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012550 Title: /usr/bin/gjs- console:6:g_assertion_message:g_assertion_message_expr:gsk_renderer_dispose:gsk_renderer_dispose:g_object_unref Status in gjs package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.75.90-1, the problem page at https://errors.ubuntu.com/problem/031c8ecfc5e8a51d75d6a028554e9c5354792705 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/gjs/+bug/2012550/+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 2012547] [NEW] Please sync deja-dup 44.0-2 from Debain unstable
Public bug reported: The latest Debian version of Deja Dup is ---> deja-dup (44.0-2) unstable; urgency=medium * debian/control: - Suggests: python3-pydrive2 * debian/rules: - set -Dpydrive_pkgs=python3-pydrive2 since it's not available in Debian * debian/patches/disable-google-drive.patch: - removed, it's not needed anymore -- Sebastien Bacher Mon, 16 Jan 2023 16:51:50 +0100 <--- That was exactly the delta Ubuntu carried, except that Ubuntu had python3-pydrive while Debian, python3-pydrive2. But since Ubuntu already has the latter too, this can be synced. ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Build log on Lunar of the synced package" https://bugs.launchpad.net/bugs/2012547/+attachment/5656641/+files/deja-dup-build.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/2012547 Title: Please sync deja-dup 44.0-2 from Debain unstable Status in deja-dup package in Ubuntu: New Bug description: The latest Debian version of Deja Dup is ---> deja-dup (44.0-2) unstable; urgency=medium * debian/control: - Suggests: python3-pydrive2 * debian/rules: - set -Dpydrive_pkgs=python3-pydrive2 since it's not available in Debian * debian/patches/disable-google-drive.patch: - removed, it's not needed anymore -- Sebastien Bacher Mon, 16 Jan 2023 16:51:50 +0100 <--- That was exactly the delta Ubuntu carried, except that Ubuntu had python3-pydrive while Debian, python3-pydrive2. But since Ubuntu already has the latter too, this can be synced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2012547/+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 2012540] Re: Please merge tiff 4.5.0-5 from Debian unstable
** Patch added: "Debdiff between tiff_4.5.0-5 and tiff_4.5.0-5ubuntu1" https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+attachment/5656640/+files/deb-ubu.diff ** Patch removed: "deb-ubu.diff" https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+attachment/5656639/+files/deb-ubu.diff ** Changed in: tiff (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/2012540 Title: Please merge tiff 4.5.0-5 from Debian unstable Status in tiff package in Ubuntu: Confirmed Bug description: Please merge tiff 4.5.0-5 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+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 2012540] Re: Please merge tiff 4.5.0-5 from Debian unstable
** Patch added: "debdiff between tiff_4.5.0-4ubuntu1 and tiff_4.5.0-5ubuntu1" https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+attachment/5656638/+files/ubu-ubu.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/2012540 Title: Please merge tiff 4.5.0-5 from Debian unstable Status in tiff package in Ubuntu: Confirmed Bug description: Please merge tiff 4.5.0-5 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+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 2012540] Re: Please merge tiff 4.5.0-5 from Debian unstable
** Patch added: "deb-ubu.diff" https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+attachment/5656639/+files/deb-ubu.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/2012540 Title: Please merge tiff 4.5.0-5 from Debian unstable Status in tiff package in Ubuntu: Confirmed Bug description: Please merge tiff 4.5.0-5 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+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 2012540] [NEW] Please merge tiff 4.5.0-5 from Debian unstable
Public bug reported: Please merge tiff 4.5.0-5 from Debian unstable. ** Affects: tiff (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/2012540 Title: Please merge tiff 4.5.0-5 from Debian unstable Status in tiff package in Ubuntu: Confirmed Bug description: Please merge tiff 4.5.0-5 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/2012540/+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
Thanks for your testing and confirmation! Looks like the spread test (GitHub action passed, too). I've also confirmed our autopkgtest is now passing, using this source package: https://git.launchpad.net/network-manager/log/?h=netplan/lunar- gu I confirmed our (previously failing) autopkgtest passes now for the OpenVPN duplicate connections fix: https://paste.ubuntu.com/p/FWTVxbjzC6/ (especially the TestNetplan.test_openvpn_connection case) So this will soon land in the "Netplan Everywhere" PPA: https://launchpad.net/~canonical- foundations/+archive/ubuntu/networkmanager-netplan ** Changed in: network-manager (Ubuntu) Status: Triaged => Fix Committed -- 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: Fix Committed 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 2012534] [NEW] JS ERROR: Error capturing screenshot
Public bug reported:
Steps to reproduce:
- run daily-live 20230322
- right click a window title bar and select "take screenshot" or hit
Alt+PrintScreen
- observe journal
The screenshot does appear on the disk but there's no notification which
might be related.
```
Mar 22 16:34:21 ubuntu gnome-shell[1752]: JS ERROR: Error capturing screenshot:
Error: Unable to construct struct type BookmarkFile since it has no default
constructor and cannot be allocated directly
saveRecentFile@resource:///org/gnome/shell/ui/screenshot.js:2079:27
_storeScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2139:23
captureScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2231:21
async*_buildMenu/item<@resource:///org/gnome/shell/ui/windowMenu.js:35:34
addAction/<@resource:///org/gnome/shell/ui/popupMenu.js:559:21
activate@resource:///org/gnome/shell/ui/popupMenu.js:197:14
vfunc_button_release_event@resource:///org/gnome/shell/ui/popupMenu.js:141:14
```
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.480
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 22 16:34:42 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disabled-extensions' b'@as []'
b'org.gnome.shell' b'enabled-extensions' b"['d...@rastersoft.com']"
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'44.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230322)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lunar
** Description changed:
Steps to reproduce:
- run daily-live 20230322
- right click a window title bar and select "take screenshot" or hit
Alt+PrintScreen
- - notice missing notification
- observe journal
+
+ The screenshot does appear on the disk but there's no notification which
+ might be related.
+
```
Mar 22 16:34:21 ubuntu gnome-shell[1752]: JS ERROR: Error capturing
screenshot: Error: Unable to construct struct type BookmarkFile since it has no
default constructor and cannot be allocated directly
-
saveRecentFile@resource:///org/gnome/shell/ui/screenshot.js:2079:27
-
_storeScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2139:23
-
captureScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2231:21
-
async*_buildMenu/item<@resource:///org/gnome/shell/ui/windowMenu.js:35:34
-
addAction/<@resource:///org/gnome/shell/ui/popupMenu.js:559:21
-
activate@resource:///org/gnome/shell/ui/popupMenu.js:197:14
-
vfunc_button_release_event@resource:///org/gnome/shell/ui/popupMenu.js:141:14
+
saveRecentFile@resource:///org/gnome/shell/ui/screenshot.js:2079:27
+
_storeScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2139:23
+
captureScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2231:21
+
async*_buildMenu/item<@resource:///org/gnome/shell/ui/windowMenu.js:35:34
+
addAction/<@resource:///org/gnome/shell/ui/popupMenu.js:559:21
+
activate@resource:///org/gnome/shell/ui/popupMenu.js:197:14
+
vfunc_button_release_event@resource:///org/gnome/shell/ui/popupMenu.js:141:14
```
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD
[Desktop-packages] [Bug 1545811] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()
** Tags added: lunar -- 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/1545811 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() Status in ibus package in Ubuntu: Confirmed Bug description: ubuntu 16.04 alpha. ibus-daemon crashed popped up after testing another bug ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: ibus 1.5.11-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 15 18:57:55 2016 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2013-09-28 (870 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim ProcEnviron: LANGUAGE=de_DE PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to xenial on 2016-02-11 (4 days ago) UserGroups: adm cdrom dip disk fax lp lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1545811/+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 2012532] Re: ibus-daemon crashed with SIGABRT
*** This bug is a duplicate of bug 1545811 *** https://bugs.launchpad.net/bugs/1545811 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1545811, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2012532/+attachment/5656616/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2012532/+attachment/5656618/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2012532/+attachment/5656621/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2012532/+attachment/5656622/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2012532/+attachment/5656623/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2012532/+attachment/5656624/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2012532/+attachment/5656625/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1545811 ibus-daemon crashed with SIGABRT in g_assertion_message() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/2012532 Title: ibus-daemon crashed with SIGABRT Status in ibus package in Ubuntu: New Bug description: Crash occurs shortly after login to desktop (no application started). 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: pass Date: Tue Mar 21 16:53:49 2023 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2022-12-13 (99 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) ProcCmdline: ibus-daemon --panel disable ProcEnviron: LANG=de_DE.UTF-8 Signal: 6 SourcePackage: ibus 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/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012532/+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 2012527] [NEW] gnome-control-center: mouse scroll direction images missing
*** This bug is a duplicate of bug 2011849 *** https://bugs.launchpad.net/bugs/2011849 Public bug reported: The new "Mouse & Touchpad" pane has a "Scroll Direction" section. The images to explain what the setting means are missing in 23.04. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2023-03-22 15-54-53.png" https://bugs.launchpad.net/bugs/2012527/+attachment/5656614/+files/Screenshot%20from%202023-03-22%2015-54-53.png -- 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/2012527 Title: gnome-control-center: mouse scroll direction images missing Status in gnome-control-center package in Ubuntu: New Bug description: The new "Mouse & Touchpad" pane has a "Scroll Direction" section. The images to explain what the setting means are missing in 23.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012527/+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 2012527] Re: gnome-control-center: mouse scroll direction images missing
*** This bug is a duplicate of bug 2011849 *** https://bugs.launchpad.net/bugs/2011849 ** This bug has been marked a duplicate of bug 2011849 gnome-control-center 44rc is missing graphics for Multitasking and Mouse & Touchpad -- 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/2012527 Title: gnome-control-center: mouse scroll direction images missing Status in gnome-control-center package in Ubuntu: New Bug description: The new "Mouse & Touchpad" pane has a "Scroll Direction" section. The images to explain what the setting means are missing in 23.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012527/+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 2012524] [NEW] character encoding combo box on open file dialog is glitchy
Public bug reported: This may be a Gnome or GTK specific issue not limited to gedit. This is just where I found it happening. When the dropdown combo box total entries would be longer than the bottom of the screen when expanded, all but the top or partial top entry is hidden. It expects you to hover over the arrow to slowly slide down instead of automatically positioning the entire contents upward, not just the dropdown outline. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Affects: gedit (Debian) Importance: Undecided Status: New ** Tags: bionic focal gedit gnome gtk jammy kinetic lunar ** Attachment added: "Visual example of glitch." https://bugs.launchpad.net/bugs/2012524/+attachment/5656613/+files/gedit.png ** Also affects: gedit (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/2012524 Title: character encoding combo box on open file dialog is glitchy Status in gedit package in Ubuntu: New Status in gedit package in Debian: New Bug description: This may be a Gnome or GTK specific issue not limited to gedit. This is just where I found it happening. When the dropdown combo box total entries would be longer than the bottom of the screen when expanded, all but the top or partial top entry is hidden. It expects you to hover over the arrow to slowly slide down instead of automatically positioning the entire contents upward, not just the dropdown outline. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2012524/+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 2012293] Re: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1
*** This bug is a duplicate of bug 2006744 *** https://bugs.launchpad.net/bugs/2006744 ** This bug has been marked a duplicate of bug 2006744 libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2012293 Title: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Status in mesa package in Ubuntu: New Bug description: unexpected crashed when login to x11 session ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.3.6-1ubuntu2 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 Date: Tue Mar 7 23:00:26 2023 DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: mesa Title: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2012293/+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 2012506] [NEW] No-change rebuilds needed for foo2zjs in lunar
Public bug reported: The last security update made to the jbigkit package introduced an ABI change. Package foo2zjs depends on jbigkit, and it declares variables and calls functions which are related to this ABI change. Because a few months have passed since the release of this jbigkit security update (2022-11), instead of reverting that change, it might be best to rebuild foo2zjs in lunar (Ubuntu 23.04), and have it be built considering the new jbigkit code, to avoid issues related to the ABI change. ** Affects: foo2zjs (Ubuntu) Importance: Undecided Status: New ** Summary changed: - No-change rebuilds needed for foo2zjs and splix in lunar + No-change rebuilds needed for foo2zjs in lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foo2zjs in Ubuntu. https://bugs.launchpad.net/bugs/2012506 Title: No-change rebuilds needed for foo2zjs in lunar Status in foo2zjs package in Ubuntu: New Bug description: The last security update made to the jbigkit package introduced an ABI change. Package foo2zjs depends on jbigkit, and it declares variables and calls functions which are related to this ABI change. Because a few months have passed since the release of this jbigkit security update (2022-11), instead of reverting that change, it might be best to rebuild foo2zjs in lunar (Ubuntu 23.04), and have it be built considering the new jbigkit code, to avoid issues related to the ABI change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/2012506/+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 2012507] [NEW] No-change rebuilds needed for splix in lunar
Public bug reported: The last security update made to the jbigkit package introduced an ABI change. Package splix depends on jbigkit, and it declares variables and calls functions which are related to this ABI change. Because a few months have passed since the release of this jbigkit security update (2022-11), instead of reverting that change, it might be best to rebuild splix in lunar (Ubuntu 23.04), and have it be built considering the new jbigkit code, to avoid issues related to the ABI change. ** Affects: splix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to splix in Ubuntu. https://bugs.launchpad.net/bugs/2012507 Title: No-change rebuilds needed for splix in lunar Status in splix package in Ubuntu: New Bug description: The last security update made to the jbigkit package introduced an ABI change. Package splix depends on jbigkit, and it declares variables and calls functions which are related to this ABI change. Because a few months have passed since the release of this jbigkit security update (2022-11), instead of reverting that change, it might be best to rebuild splix in lunar (Ubuntu 23.04), and have it be built considering the new jbigkit code, to avoid issues related to the ABI change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/2012507/+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 1989477] Re: Switching to dark mode in settings does not change shell theme.
The issue re-appeared on my laptop as well after an update. Update history below. "Start-Date: 2023-03-22 07:38:25 Commandline: /usr/bin/unattended-upgrade Upgrade: printer-driver-foo2zjs-common:amd64 (20200505dfsg0-2ubuntu2, 20200505dfsg0-2ubuntu2.22.10.1), printer-driver-foo2zjs:amd64 (20200505dfsg0-2ubuntu2, 20200505dfsg0-2ubuntu2.22.10.1) End-Date: 2023-03-22 07:38:30 Start-Date: 2023-03-22 07:38:33 Commandline: /usr/bin/unattended-upgrade Upgrade: libgraphicsmagick++-q16-12:amd64 (1.4+really1.3.38+hg16739-1, 1.4+really1.3.38+hg16739-1ubuntu0.1), libgraphicsmagick-q16-3:amd64 (1.4+really1.3.38+hg16739-1, 1.4+really1.3.38+hg16739-1ubuntu0.1) End-Date: 2023-03-22 07:38:34 Start-Date: 2023-03-22 08:00:48 Commandline: aptdaemon role='role-commit-packages' sender=':1.1579' Upgrade: libsnmp-base:amd64 (5.9.3+dfsg-1ubuntu1.3, 5.9.3+dfsg-1ubuntu1.4), libsnmp40:amd64 (5.9.3+dfsg-1ubuntu1.3, 5.9.3+dfsg-1ubuntu1.4), google-chrome-stable:amd64 (111.0.5563.64-1, 111.0.5563.110-1) End-Date: 2023-03-22 08:00:56 " -- 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/1989477 Title: Switching to dark mode in settings does not change shell theme. Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: Changing the "Style" in the "Appearance" section of "Settings" (gnome- control-center), does not update the shell theme. When I select dark mode from settings, Libadwaita apps respond to the changes, but the shell theme and GTK3 applications do not. This has been observed on both Wayland and X11. Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10 Package Version: 1:43~rc-1ubuntu2 What I Expected: Changing the style in settings will affect all the apps that support changing light/dark mode. The shell theme will also respond to the change. What happened instead: Only libadwaita apps are affected by changing the style in Settings. GTK3 apps and the shell theme do not change. When changing to dark mode via the quick settings menu, all the apps change their color scheme appropriately. However, there is not a smooth transition when switching the style from quick settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989477/+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 1993874] Re: Settings and Quick Menu apply Dark style differently
*** This bug is a duplicate of bug 1989477 *** https://bugs.launchpad.net/bugs/1989477 This Bug report is a duplicate. I can’t close it but please add any update/comment to the main bug report: https://bugs.launchpad.net/bugs/1989477 -- 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/1993874 Title: Settings and Quick Menu apply Dark style differently Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I just upgraded to Ubuntu 22.10 and noticed that some of my apps were no longer in Dark mode including gedit/chrome. When setting the style through the quick menu however, these apps go to Dark mode (presumably due to gtk theme being applied). Likewise for the quick menu itself, setting the style to Dark in gnome-control-settings doesn't change it to dark, it remains light. see screenshot attached, you will see that when setting the style to Dark in Settings, gedit and the quick menu remain light. I tried to logout in case it was an issue with how the settings are applied but it didn't help. it's also clear that the toggle in the quick menu works as intended so there seems to be an issue with the way gnome- control-center applies the Dark style. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 10:21:40 2022 InstallationDate: Installed on 2022-04-06 (198 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 2012201] Re: Requiring GnomeDesktop, version 3.0
It was resolved in https://launchpad.net/ubuntu/+source/gnome-shell- extension-desktop-icons-ng/46+really47.0.2-3 ** Project changed: ubuntu-desktop-installer => gnome-shell-extension- desktop-icons-ng (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/2012201 Title: Requiring GnomeDesktop, version 3.0 Status in subiquity: Invalid Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Bug description: Hello With this version lunar-desktop-amd64.iso 2023-03-19 09:074.4GDesktop image for 64-bit PC (AMD64) computers (standard download) sha256sum is good When i install, i can choose my language and after CPU is 100% Journalctl show this looop trace ar 19 17:34:36 ubuntu gnome-shell[2435]: Launching DING process Mar 19 17:34:36 ubuntu gnome-shell[2435]: DING: (gjs:9948): Gjs-CRITICAL **: 17:34:36.929: JS ERROR: Error: Requiring GnomeDesktop, version 3.0: Typelib file for namespace 'GnomeDesktop', version '3.0' not found Mar 19 17:34:36 ubuntu gnome-shell[2435]: DING: @/usr/share/gnome-shell/extensions/d...@rastersoft.com/thumbnails.js:19:22 Mar 19 17:34:36 ubuntu gnome-shell[2435]: DING: @/usr/share/gnome-shell/extensions/d...@rastersoft.com/desktopManager.js:37:20 Mar 19 17:34:36 ubuntu gnome-shell[2435]: DING: @/usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js:162:24 Mar 19 17:34:36 ubuntu gnome-shell[2435]: DING: (gjs:9948): Gjs-CRITICAL **: 17:34:36.929: Script /usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js threw an exception To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2012201/+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 2012201] [NEW] Requiring GnomeDesktop, version 3.0
You have been subscribed to a public bug: Hello With this version lunar-desktop-amd64.iso 2023-03-19 09:074.4GDesktop image for 64-bit PC (AMD64) computers (standard download) sha256sum is good When i install, i can choose my language and after CPU is 100% Journalctl show this looop trace ar 19 17:34:36 ubuntu gnome-shell[2435]: Launching DING process Mar 19 17:34:36 ubuntu gnome-shell[2435]: DING: (gjs:9948): Gjs-CRITICAL **: 17:34:36.929: JS ERROR: Error: Requiring GnomeDesktop, version 3.0: Typelib file for namespace 'GnomeDesktop', version '3.0' not found Mar 19 17:34:36 ubuntu gnome-shell[2435]: DING: @/usr/share/gnome-shell/extensions/d...@rastersoft.com/thumbnails.js:19:22 Mar 19 17:34:36 ubuntu gnome-shell[2435]: DING: @/usr/share/gnome-shell/extensions/d...@rastersoft.com/desktopManager.js:37:20 Mar 19 17:34:36 ubuntu gnome-shell[2435]: DING: @/usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js:162:24 Mar 19 17:34:36 ubuntu gnome-shell[2435]: DING: (gjs:9948): Gjs-CRITICAL **: 17:34:36.929: Script /usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js threw an exception ** Affects: subiquity Importance: Undecided Status: Invalid ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: Fix Released -- Requiring GnomeDesktop, version 3.0 https://bugs.launchpad.net/bugs/2012201 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. -- 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 the SRU to K and J now -- 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 (< 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. [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/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)
If you run 'xwininfo -all' and then click on the rectangle, what do you get? -- 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: Opinion 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 2012388] Re: Unable to focus Windows below system tray (wayland session)
I think it's worth exploring first by reporting a bug upstream to Anydesk. However you do that. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Opinion -- 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: Opinion 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 1993874] Re: Settings and Quick Menu apply Dark style differently
*** This bug is a duplicate of bug 1989477 *** https://bugs.launchpad.net/bugs/1989477 The issue re-appeared on my laptop as well after an update. Update history below. "Start-Date: 2023-03-22 07:38:25 Commandline: /usr/bin/unattended-upgrade Upgrade: printer-driver-foo2zjs-common:amd64 (20200505dfsg0-2ubuntu2, 20200505dfsg0-2ubuntu2.22.10.1), printer-driver-foo2zjs:amd64 (20200505dfsg0-2ubuntu2, 20200505dfsg0-2ubuntu2.22.10.1) End-Date: 2023-03-22 07:38:30 Start-Date: 2023-03-22 07:38:33 Commandline: /usr/bin/unattended-upgrade Upgrade: libgraphicsmagick++-q16-12:amd64 (1.4+really1.3.38+hg16739-1, 1.4+really1.3.38+hg16739-1ubuntu0.1), libgraphicsmagick-q16-3:amd64 (1.4+really1.3.38+hg16739-1, 1.4+really1.3.38+hg16739-1ubuntu0.1) End-Date: 2023-03-22 07:38:34 Start-Date: 2023-03-22 08:00:48 Commandline: aptdaemon role='role-commit-packages' sender=':1.1579' Upgrade: libsnmp-base:amd64 (5.9.3+dfsg-1ubuntu1.3, 5.9.3+dfsg-1ubuntu1.4), libsnmp40:amd64 (5.9.3+dfsg-1ubuntu1.3, 5.9.3+dfsg-1ubuntu1.4), google-chrome-stable:amd64 (111.0.5563.64-1, 111.0.5563.110-1) End-Date: 2023-03-22 08:00:56 " -- 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/1993874 Title: Settings and Quick Menu apply Dark style differently Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I just upgraded to Ubuntu 22.10 and noticed that some of my apps were no longer in Dark mode including gedit/chrome. When setting the style through the quick menu however, these apps go to Dark mode (presumably due to gtk theme being applied). Likewise for the quick menu itself, setting the style to Dark in gnome-control-settings doesn't change it to dark, it remains light. see screenshot attached, you will see that when setting the style to Dark in Settings, gedit and the quick menu remain light. I tried to logout in case it was an issue with how the settings are applied but it didn't help. it's also clear that the toggle in the quick menu works as intended so there seems to be an issue with the way gnome- control-center applies the Dark style. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 10:21:40 2022 InstallationDate: Installed on 2022-04-06 (198 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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
** Tags added: 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 [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 2012388] Re: Unable to focus Windows below system tray (wayland session)
Thank you for your help. I have been running some tests: - Disabled all extensions and re-logged the sessionSame result. However, when hovering over the previously mentioned rectangle, I noticed that a popup was appearing, repoting "Anydesk", an application that was set to autostart and had an icon on the taskbar. - Presto I went to prevent this application from auto starting on login, and I cannot reproduce the issue any more. - I re-enabled all gnome extensions, left Anydesk with autostart disabled, and re-logged. I cannot reproduce the issue. - I have other applications that are set to auto start and have a taskbar icon, such as ProtonMail Bridge, Nextcloud client, and Polychromatic. However I cannot reproduce the issue with those applications. Note. I have been using Anydesk for a long time and on Gnome and this is the first time I saw this problem. Do you believe it is worth exploring more about this issue or consider this resolved? I am happy to help if needed. -- 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
(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
