[Desktop-packages] [Bug 2038977] Re: Update to 118.0.2
References: https://ubuntu.com/security/notices/USN-6404-2 Package Information: https://launchpad.net/ubuntu/+source/firefox/118.0.2+build2-0ubuntu0.20.04.1 ** Changed in: firefox (Ubuntu) Status: New => Fix Released ** Changed in: firefox (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2038977 Title: Update to 118.0.2 Status in firefox package in Ubuntu: Fix Released Status in firefox source package in Focal: Fix Released Bug description: https://www.mozilla.org/en-US/firefox/118.0.2/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2038977/+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 2038977] [NEW] Update to 118.0.2
Public bug reported: https://www.mozilla.org/en-US/firefox/118.0.2/releasenotes/ ** Affects: firefox (Ubuntu) Importance: Undecided Assignee: Nishit Majithia (0xnishit) Status: New ** Affects: firefox (Ubuntu Focal) Importance: Undecided Assignee: Nishit Majithia (0xnishit) Status: New ** Also affects: firefox (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Nishit Majithia (0xnishit) ** Changed in: firefox (Ubuntu Focal) Assignee: (unassigned) => Nishit Majithia (0xnishit) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2038977 Title: Update to 118.0.2 Status in firefox package in Ubuntu: New Status in firefox source package in Focal: New Bug description: https://www.mozilla.org/en-US/firefox/118.0.2/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2038977/+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 2003192]
err: that broken thunderbird snap beta revision is 391 (119.0b3-1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2003192 Title: thunderbird snap does not work without x11 interface connected Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: New Bug description: When I disconnect the thunderbird from the x11 interface thunderbird crashes saying it can not find the wayland socket. If I add a link to the wayland socket inside the container thunderbird works fine. That is on kubuntu 22.04 in a plasma/wayland session, MOZ_ENABLE_WAYLAND=1 is set on the host and in the container as well. This also probably means that the thunderbird snap actually never uses native wayland and falls back to xwayland (because the wayland socket can not be found). This unintended use of xwayland could be construed as a security issue, but someone who mistrusts snaps using x11 (like me) will remove the permission which leads to failure instead of a security issue. $ snap run thunderbird ## BROKEN ... [GFX1-]: glxtest: libpci missing [GFX1-]: glxtest: Could not connect to wayland socket [GFX1-]: No GPUs detected via PCI (thunderbird:103861): Gtk-WARNING **: 12:37:14.162: cannot open display: :1 ExceptionHandler::GenerateDump cloned child 103976 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... $ snap run --shell thunderbird ## FIXING IT To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. user@user-mycomputer:/$ ln -s /run/user/1000/wayland-0 $XDG_RUNTIME_DIR/ ; exit $ snap run thunderbird ## NOW IT WORKS $ lsb_release -rd ## UBUNTU VERSION Description:Ubuntu 22.04.1 LTS Release:22.04 $ snap interfaces thunderbird ## SNAP CONFIGURATION Slot Plug gnome-3-38-2004:gnome-3-38-2004 thunderbird gtk-common-themes:gtk-3-themes thunderbird gtk-common-themes:icon-themesthunderbird gtk-common-themes:sound-themes thunderbird :audio-playback thunderbird :browser-support thunderbird:browser-sandbox :cups-controlthunderbird :desktop thunderbird :desktop-legacy thunderbird :gsettings thunderbird :homethunderbird :network thunderbird :opengl thunderbird :system-filesthunderbird:etc-thunderbird-policies :wayland thunderbird thunderbird:dbus-daemon - -thunderbird:avahi-observe -thunderbird:camera -thunderbird:gpg-keys -thunderbird:network-control -thunderbird:removable-media -thunderbird:u2f-devices -thunderbird:x11 $ snap info thunderbird ## THUNDERBIRD SNAP VERSION ... installed: 102.7.0-1(288) 106MB - $ snap --version ## SNAPD etc VERSION snap2.58 snapd 2.58 series 16 ubuntu 22.04 kernel 5.15.0-57-generic To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/2003192/+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 2003192]
still a problem with snap stable revisision 389 (115.3.1-1) and snap beta revision 389 (119.0b3-1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2003192 Title: thunderbird snap does not work without x11 interface connected Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: New Bug description: When I disconnect the thunderbird from the x11 interface thunderbird crashes saying it can not find the wayland socket. If I add a link to the wayland socket inside the container thunderbird works fine. That is on kubuntu 22.04 in a plasma/wayland session, MOZ_ENABLE_WAYLAND=1 is set on the host and in the container as well. This also probably means that the thunderbird snap actually never uses native wayland and falls back to xwayland (because the wayland socket can not be found). This unintended use of xwayland could be construed as a security issue, but someone who mistrusts snaps using x11 (like me) will remove the permission which leads to failure instead of a security issue. $ snap run thunderbird ## BROKEN ... [GFX1-]: glxtest: libpci missing [GFX1-]: glxtest: Could not connect to wayland socket [GFX1-]: No GPUs detected via PCI (thunderbird:103861): Gtk-WARNING **: 12:37:14.162: cannot open display: :1 ExceptionHandler::GenerateDump cloned child 103976 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... $ snap run --shell thunderbird ## FIXING IT To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. user@user-mycomputer:/$ ln -s /run/user/1000/wayland-0 $XDG_RUNTIME_DIR/ ; exit $ snap run thunderbird ## NOW IT WORKS $ lsb_release -rd ## UBUNTU VERSION Description:Ubuntu 22.04.1 LTS Release:22.04 $ snap interfaces thunderbird ## SNAP CONFIGURATION Slot Plug gnome-3-38-2004:gnome-3-38-2004 thunderbird gtk-common-themes:gtk-3-themes thunderbird gtk-common-themes:icon-themesthunderbird gtk-common-themes:sound-themes thunderbird :audio-playback thunderbird :browser-support thunderbird:browser-sandbox :cups-controlthunderbird :desktop thunderbird :desktop-legacy thunderbird :gsettings thunderbird :homethunderbird :network thunderbird :opengl thunderbird :system-filesthunderbird:etc-thunderbird-policies :wayland thunderbird thunderbird:dbus-daemon - -thunderbird:avahi-observe -thunderbird:camera -thunderbird:gpg-keys -thunderbird:network-control -thunderbird:removable-media -thunderbird:u2f-devices -thunderbird:x11 $ snap info thunderbird ## THUNDERBIRD SNAP VERSION ... installed: 102.7.0-1(288) 106MB - $ snap --version ## SNAPD etc VERSION snap2.58 snapd 2.58 series 16 ubuntu 22.04 kernel 5.15.0-57-generic To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/2003192/+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 2034996] Re: Mantic amd64 daily ISO also installs i386 packages
Yes? $ apt-cache show gamemode | grep Recommends Recommends: libgamemode0:i386, libgamemodeauto0:i386 $ So what's the bug? ** Changed in: ubuntu-meta (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034996 Title: Mantic amd64 daily ISO also installs i386 packages Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: Mantic amd64 daily ISO installed these i386 packages libgcc-s1:i386 gcc-13-base:i386 libc6:i386 libcap2:i386 libcom- err2:i386 libdbus-1-3:i386 libgamemode0:i386 libgamemodeauto0:i386 libgcrypt20:i386 libgpg-error0:i386 libgssapi-krb5-2:i386 libidn2-0:i386 libk5crypto3:i386 libkeyutils1:i386 libkrb5-3:i386 libkrb5support0:i386 liblz4-1:i386 liblzma5:i386 libnsl2:i386 libnss- nis:i386 libnss-nisplus:i386 libssl3:i386 libsystemd0:i386 libtirpc3:i386 libunistring2:i386 libzstd1:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034996/+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 2034986] Re: some text became unreadable during a distribution upgrade
Besides the very minor Firefox issue, I didn't see any font issues when I tested 23.04 -> 23.10 basic upgrades today of - Ubuntu Desktop - Ubuntu Budgie - Kubuntu - Lubuntu - Xubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade
Sorry for the noise about Lubuntu. There is a very minor issue seen during the upgrade if Firefox is running (regardless of whether the desktop is Lubuntu). It's recommended to not run other apps during the upgrade. In this case, restarting Firefox is usually enough to fix the issue. If not, restarting after the upgrade completes does fix the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034967] Re: cloud-init & cloud-guest-utils are installed on non-cloud installations
** Changed in: cloud-utils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034967 Title: cloud-init & cloud-guest-utils are installed on non-cloud installations Status in cloud-init package in Ubuntu: Invalid Status in cloud-utils package in Ubuntu: Invalid Status in subiquity package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: New Bug description: ~$ apt-cache rdepends --installed cloud-init cloud-init Reverse Depends: cloud-guest-utils ~$ apt-cache rdepends --installed cloud-guest-utils cloud-guest-utils Reverse Depends: |cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2034967/+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 2038964] Re: raspi ethernet rename is racy
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038964 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: New Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy
** Attachment added: "kern.log from unaffected 2B (rev 1.2)" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708342/+files/unaffected.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: New Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy
** Attachment added: "kern.log from affected 3B+" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708341/+files/affected.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: New Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] [NEW] raspi ethernet rename is racy
Public bug reported: The renaming of the ethernet interface (controlled by 10-raspi-eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: raspi-image ** Tags added: raspi-image -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: New Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2037497] Re: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
** Changed in: mesa (Fedora) Status: Fix Committed => Fix Released -- 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/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Fix Released Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037497]
FEDORA-2023-86e10b6cae has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. -- 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/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Fix Released Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 1863103] Re: apparmor messages for libreoffice-oopslash about /tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a...
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1863103 Title: apparmor messages for libreoffice-oopslash about /tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a... Status in libreoffice package in Ubuntu: Confirmed Bug description: i opened libreoffice writer, then, after some time, clicked a document, to open it in libreoffice, and i see these messages in syslog: Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979570] audit: type=1400 audit(1581600289.824:108): apparmor="ALLOWED" operation="connect" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979578] audit: type=1400 audit(1581600289.824:109): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979581] audit: type=1400 audit(1581600289.824:110): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979781] audit: type=1400 audit(1581600289.828:111): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979786] audit: type=1400 audit(1581600289.828:112): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 also there was Feb 13 16:24:50 dinar-Lenovo-G580 kernel: [17789.649828] audit: type=1400 audit(1581600290.496:117): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/dinar/.mozilla/firefox/sge95l3o.default/cert8.db" pid=8829 comm="soffice.bin" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 i reported about that type of message: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862331 . (but this time there is no request for key3.db). also there are messages about the opened document file itself, i am going to write a separate bug about that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863103/+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 2034986] Re: some text became unreadable during a distribution upgrade
I just ran an errand, and thought about that font workaround. The MATE
issue makes me doubt about running the code for all the flavors.
We know that the root cause is changes to the Ubuntu font. That font is
explicitly used for desktop in standard Ubuntu and MATE. But is it used
for desktop by any other flavor?
I fear that we for other flavors mess with their settings unnecessarily.
If the reset succeeds, it doesn't matter much, but maybe more flavors
have not enabled the required systemd integration, and then our
'temporary' change gets persistent. Which may or may not matter in
practice.
So maybe it would be better to only run the code for flavors where we
know that it makes a difference. Something like:
is_mate = False
desktops = os.getenv('XDG_CURRENT_DESKTOP', '').split(':')
if 'MATE' in desktops:
schema = 'org.mate.interface'
is_mate = True
else if 'GNOME' in desktops:
schema = 'org.gnome.desktop.interface'
else if 'xxx' in desktops:
schema = 'yyy'
else:
return
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986
Title:
some text became unreadable during a distribution upgrade
Status in Ubuntu MATE:
New
Status in ubuntu-meta package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
In Progress
Status in ubuntu-meta source package in Mantic:
Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
In Progress
Bug description:
I was upgrading from Lunar to Mantic the other day and left a couple
of applications open during the upgrade process. During the upgrade
the text in audacious became unreadable (I'll attach a screenshot) and
I seem to recall the title bar of Firefox being unreadable but the
contents of web pages still being readable.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-release-upgrader-core 1:23.10.5
ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
Uname: Linux 6.5.0-4-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 8 15:39:27 2023
InstallationDate: Installed on 2018-08-10 (1855 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat',
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code
126: Error executing command as another user: Request dismissed
VarLogDistupgradeTermlog:
mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade
I filed the Lubuntu equivalent of this bug as https://launchpad.net/bugs/2038946 Minor issue, didn't affect the upgrade itself or most apps. Easy workaround for Firefox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
I'm pointing that when I add chromium on a fresh Ubuntu install it does not do configure itself to use the libsecret keyring. When I add chromium on a fresh Debian/Gnome Desktop install it does. This difference is in packaging, and presumably came when chromium was migrated to use snap. But I would think what should happen is the prior behavior, if you're on a gnome with libsecret, it by default should use the OS key ring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: New Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+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 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
** Tags added: password-storage -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: New Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+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
Re: [Desktop-packages] [Bug 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
If password-manager-service is connected with snap connect chromium:password-manager-service then it uses the operating system's key ring. So are you pointing out that Chromium ought to use gnome-libcrypt instead of basic when no key ring is detected? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: New Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+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 2038761] Re: gnome-disk-utility does not give size of nvme disk
** Changed in: udisks Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2038761 Title: gnome-disk-utility does not give size of nvme disk Status in udisks: New Status in udisks2 package in Ubuntu: Triaged Bug description: Mantic gnome-disk-utility: 45.0-1ubuntu1 Size of nvme disk is blank while in Jammy 42.0-1ubuntu1 gives correct size. see attached image ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-disk-utility 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 17:16:12 2023 InstallationDate: Installed on 2023-10-07 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231005) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/2038761/+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 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
The Chrome password manager does not mean it uses the Operating System's key ring. If the key ring is not available or the configuration doesn't detect it (as in the case of the snap) it will use key "peanuts" with salt "saltysalt". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: New Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+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 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Released Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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 1399945] Re: Settings, Preferences, ect. - All keyboard input is added twice
** Changed in: winff (Ubuntu) Status: Fix Committed => Fix Released -- 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/1399945 Title: Settings, Preferences, ect. - All keyboard input is added twice Status in Winff: Unknown Status in ibus package in Ubuntu: New Status in winff package in Ubuntu: Fix Released Bug description: Test Case: Open winff Try to edit or add something using keyboard. All characters are doubled Screen shows attempt to add /Videos to Output Folder box ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: winff 1.5.3-4ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 6 10:32:03 2014 InstallationDate: Installed on 2014-11-16 (20 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) PackageArchitecture: all SourcePackage: winff UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/winff/+bug/1399945/+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 2038922] [NEW] Sudden screen crash
Public bug reported: All of the sudden screen started flickering and showing artifacts and after a few seconds got frozen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Tue Oct 10 15:46:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (172 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2038922 Title: Sudden screen crash Status in xorg package in Ubuntu: New Bug description: All of the sudden screen started flickering and showing artifacts and after a few seconds got frozen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Tue Oct 10 15:46:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (172 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias:
[Desktop-packages] [Bug 2037017] Re: Sharing tab hangs gnome-control-center
the backtrace suggests it's blocked trying to access the keyring to read/write a rdp password -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+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 2038727] Re: Chromium snap theme parsing error
** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+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 2037642] Re: [FFe] Raspberry Pi 5 support
Added text to the release notes [1] detailing Pi 5 support, including the planned SRU of libcamera support. Can others double-check the raspberry pi sections look reasonable, and let me know if we want to mention anything else specific? I've also updated the "known issues" section, removing a couple of bits (totem now works and the audio output selection is now sane out of the box), and adding others (slide corruption on the pi4 during installation). Again, if there's anything missing that should be mentioned please either let me know or feel free to add it yourself! [1]: https://discourse.ubuntu.com/t/mantic-minotaur-release-notes/35534 ** Changed in: ubuntu-release-notes Status: New => In Progress -- 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/2037642 Title: [FFe] Raspberry Pi 5 support Status in Release Notes for Ubuntu: In Progress Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+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 2037017] Re: Sharing tab hangs gnome-control-center
Additional observation: I re-tested this on the Pi 4 and 5. The hang only occurs on the Pi 4 and 400, but does *not* occur on the 5 -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+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 2037017] Re: Sharing tab hangs gnome-control-center
Attaching backtrace from gdb with debug symbols ** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+attachment/5708243/+files/gdb.txt ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+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 1993316] Re: Non-existent audio output selected on Pi 400
No longer occurs on the Mantic final images; HDMI is selected by default. Marking fix released. ** Changed in: pipewire (Ubuntu) Status: Confirmed => Fix Released -- 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/1993316 Title: Non-existent audio output selected on Pi 400 Status in PipeWire: New Status in pipewire package in Ubuntu: Fix Released Bug description: When testing the Ubuntu 22.10 (kinetic) Desktop for Raspberry Pi on a Raspberry Pi 400 (the keyboard-based model), the new pipewire stack selects a non-existent audio output by default. Specifically, the output device listed in the gnome control center is "Analogue Output - Built-in Audio". On the Raspberry Pi 4 this refers to the auxiliary output (the 3.5mm headphone jack on the board), however the Pi 400 has no such output. Under the older pulseaudio stack, this was correct (no analogue output was listed) and the HDMI output was correctly selected on the Pi 400 (though, notably, the older stack got the default output wrong on the Pi 4; see LP: #1877194). This is a low priority since the default selection is easily changed from the gnome control center, and the new selection persists across boots (in contrast to the aforementioned pulseaudio bug). To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1993316/+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 1993347] Re: Wrong audio output selected by default on Pi 4
No longer occurs on the Mantic final images; HDMI is selected by default, with analog output still available as a secondary option. Marking fix released. ** Changed in: pipewire (Ubuntu) Status: Confirmed => Fix Released -- 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/1993347 Title: Wrong audio output selected by default on Pi 4 Status in PipeWire: New Status in pipewire package in Ubuntu: Fix Released Bug description: When testing the Ubuntu 22.10 (kinetic) Desktop for Raspberry Pi on a Raspberry Pi 4, the new pipewire stack selects the "Analogue Output - Built-in Audio" by default when the system is first installed, when the HDMI output probably ought to be selected by default (the analogue output is notably lower quality due to the low resolution DAC used, and tends to only be used when there is no alternative, e.g. on DPI/DSI displays with no audio channel). This is a low priority since the default is easily changed in the gnome control center, and the new selection persists across boots (in contrast to the same issue in the older pulseaudio stack; LP: #1877194). However, it is a minor annoyance that a non-technical user may struggle to figure out initially (it also means the first-time setup sound isn't audible on first boot). To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1993347/+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 1998782] Re: Totem unable to play video on Raspberry Pi: "could not initialize OpenGL support"
With the correct video codecs installed (for the particular test video I was using, I needed gstreamer1.0-plugins-bad which pulls in libav), this now works on the mantic final images, under both the Pi 4 and 5. ** Changed in: totem (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1998782 Title: Totem unable to play video on Raspberry Pi: "could not initialize OpenGL support" Status in totem package in Ubuntu: Fix Released Bug description: Testing Ubuntu Lunar Daily RaspPI 4 image dated 2022-12-05 I received this error trying to play the video "big_buck_bunny" in Totem as per the testcase: This maybe a duplicate of the old bug 1969512 but as the error message is not the same a new bug is filed. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1004.10-raspi 5.19.7 Uname: Linux 5.19.0-1004-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 11:24:38 2022 ImageMediaBuild: 20221205 LogAlsaMixer: Simple mixer control 'PCM',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -1988 [78%] [-19.88dB] [on] SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1998782/+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: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks
Temporary solution: 1. jack@jack:~$ xwininfo 2. Click on the invisible square in right top corner 3. Get the square ID (Window id): " > xwininfo: Please select the window about which you > would like information by clicking the > mouse in that window. > > xwininfo: Window id: 0xc02f07 (has no name) " 4. jack@jack:~$ xdotool windowclose 0xc02f07 I need to do this every time i use AnyDesk -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks Status in gnome-shell-extension-appindicator package in Ubuntu: Triaged 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-extension-appindicator/+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 2016217] Re: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer()
Also tracking in
https://errors.ubuntu.com/problem/b3b9287ceddb6c240bd1503530c0cbe8b4448cab
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/2016217
Title:
gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from
st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer()
from GjsAutoPointer()
Status in GNOME Shell:
Fix Released
Status in gnome-shell package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Won't Fix
Status in gnome-shell package in Fedora:
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.0-2ubuntu3, the problem page at
https://errors.ubuntu.com/problem/677a794c2788cd0244c8fc6d7d34780a85127bc9
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/.
#0 0x7f3aa429dd82 in clutter_actor_remove_effect
(self=self@entry=0x55d60fa59e90, effect=0x55d6101c48a0) at
../clutter/clutter/clutter-actor.c:14830
__inst = 0x55d6101c48a0
__t = 94377826055744
__r =
_g_boolean_var_274 =
__func__ = "clutter_actor_remove_effect"
#1 0x7f3aa3f9d27f in st_scroll_view_dispose (object=0x55d60fa59e90) at
../src/st/st-scroll-view.c:246
priv = 0x55d60fa59a00
#2 0x7f3aa4aeada0 in g_object_unref (_object=0x55d60fa59e90) at
../../../gobject/gobject.c:3891
_pp =
gaig_temp =
gaig_temp =
weak_locations =
nqueue = 0x55d60fa6da60
_ptr =
object = 0x55d60fa59e90
old_ref =
retry_atomic_decrement1 =
__func__ = "g_object_unref"
#3 0x7f3aa43b4b2c in GjsAutoPointer<_GObject, void, _object_unref,
_object_ref>::reset (ptr=0x0, this=) at ../gjs/jsapi-util.h:229
old_ptr =
#4 GjsAutoPointer<_GObject, void, _object_unref,
_object_ref>::~GjsAutoPointer (this=, this=) at
../gjs/jsapi-util.h:172
No locals.
#5 GjsSmartPointer<_GObject>::~GjsSmartPointer (this=,
this=) at ../gjs/jsapi-util.h:349
No locals.
#6 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1524
No locals.
#7 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1500
No locals.
#8 0x7f3aa43c9ec0 in ObjectInstance::~ObjectInstance (this=, this=) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1945
was_using_toggle_refs = false
had_toggle_up = false
had_toggle_down =
had_toggle_up =
had_toggle_down =
was_using_toggle_refs =
#9 GIWrapperInstance::finalize_impl (this=0x55d60fa0ce80) at ../gi/wrapperutils.h:1113
No locals.
#10 ObjectInstance::finalize_impl (gcx=, obj=0x35b1abd24820,
this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1912
query = {type = 94377830362416, type_name = 0x7f3aa3fdcda6
"StScrollView", class_size = 664, instance_size = 48}
query =
_g_boolean_var_74 =
#11 GIWrapperBase::finalize
(gcx=, obj=0x35b1abd24820) at ../gi/wrapperutils.h:411
priv = 0x55d60fa0ce80
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2016217/+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 2035096] Re: gnome-shell crashed with SIGSEGV in clutter_stage_emit_event()
** Description changed: https://errors.ubuntu.com/problem/ed14da5028cf683dd899169fc0c092c27703e62e + https://errors.ubuntu.com/problem/13864618e249d119c794022eb8467fb70d7565cb --- This occurred on startup - fresh system Chromebook HP G6 with Mr.Chromebook BIOS/UEFI. Installed from CD Image 23.10 release date - 9/8/2023. No apparent issues after error. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 08:11:14 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-11 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: clutter_stage_process_event () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0 _clutter_stage_process_queued_events () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_stage_process_event() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: -- 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/2035096 Title: gnome-shell crashed with SIGSEGV in clutter_stage_emit_event() Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/ed14da5028cf683dd899169fc0c092c27703e62e https://errors.ubuntu.com/problem/13864618e249d119c794022eb8467fb70d7565cb --- This occurred on startup - fresh system Chromebook HP G6 with Mr.Chromebook BIOS/UEFI. Installed from CD Image 23.10 release date - 9/8/2023. No apparent issues after error. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 08:11:14 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-11 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: clutter_stage_process_event () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0 _clutter_stage_process_queued_events () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_stage_process_event() 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/2035096/+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 2038908] Re: /usr/bin/gnome-shell:11:clutter_actor_remove_effect:clutter_actor_remove_effect:st_scroll_view_dispose:g_object_unref:g_object_unref
*** This bug is a duplicate of bug 2016217 *** https://bugs.launchpad.net/bugs/2016217 ** This bug has been marked a duplicate of bug 2016217 gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer() -- 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/2038908 Title: /usr/bin/gnome- shell:11:clutter_actor_remove_effect:clutter_actor_remove_effect:st_scroll_view_dispose:g_object_unref:g_object_unref Status in gnome-shell package in Ubuntu: New 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 45.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/b3b9287ceddb6c240bd1503530c0cbe8b4448cab contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2038908/+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 2038908] [NEW] /usr/bin/gnome-shell:11:clutter_actor_remove_effect:clutter_actor_remove_effect:st_scroll_view_dispose:g_object_unref:g_object_unref
*** This bug is a duplicate of bug 2016217 *** https://bugs.launchpad.net/bugs/2016217 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 45.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/b3b9287ceddb6c240bd1503530c0cbe8b4448cab 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: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: mantic -- 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/2038908 Title: /usr/bin/gnome- shell:11:clutter_actor_remove_effect:clutter_actor_remove_effect:st_scroll_view_dispose:g_object_unref:g_object_unref Status in gnome-shell package in Ubuntu: New 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 45.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/b3b9287ceddb6c240bd1503530c0cbe8b4448cab contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2038908/+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 2038910] Re: /usr/bin/gnome-shell:11:__GI_getenv:guess_category_value:__dcigettext:__GI___dcgettext:g_dgettext
*** This bug is a duplicate of bug 2036651 ***
https://bugs.launchpad.net/bugs/2036651
** This bug has been marked a duplicate of bug 2036651
gnome-shell crashed with SIGSEGV in __GI_getenv("LANGUAGE") from
guess_category_value() from __dcigettext()
--
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/2038910
Title:
/usr/bin/gnome-
shell:11:__GI_getenv:guess_category_value:__dcigettext:__GI___dcgettext:g_dgettext
Status in gnome-shell package in Ubuntu:
New
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
45.0-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/c594694003aced06b5eff8df461b4ab6fb89646b
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2038910/+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 2038910] [NEW] /usr/bin/gnome-shell:11:__GI_getenv:guess_category_value:__dcigettext:__GI___dcgettext:g_dgettext
*** This bug is a duplicate of bug 2036651 *** https://bugs.launchpad.net/bugs/2036651 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 45.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c594694003aced06b5eff8df461b4ab6fb89646b 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: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: mantic xenial -- 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/2038910 Title: /usr/bin/gnome- shell:11:__GI_getenv:guess_category_value:__dcigettext:__GI___dcgettext:g_dgettext Status in gnome-shell package in Ubuntu: New 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 45.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c594694003aced06b5eff8df461b4ab6fb89646b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2038910/+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 2038911] [NEW] /usr/bin/gnome-shell:11:clutter_stage_emit_event:emit_event:_clutter_process_event_details:clutter_stage_process_event:0x0000ffffaf05af9c
*** This bug is a duplicate of bug 2035096 *** https://bugs.launchpad.net/bugs/2035096 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 45.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/13864618e249d119c794022eb8467fb70d7565cb 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: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: mantic -- 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/2038911 Title: /usr/bin/gnome- shell:11:clutter_stage_emit_event:emit_event:_clutter_process_event_details:clutter_stage_process_event:0xaf05af9c Status in gnome-shell package in Ubuntu: New 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 45.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/13864618e249d119c794022eb8467fb70d7565cb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2038911/+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 2038911] Re: /usr/bin/gnome-shell:11:clutter_stage_emit_event:emit_event:_clutter_process_event_details:clutter_stage_process_event:0x0000ffffaf05af9c
*** This bug is a duplicate of bug 2035096 *** https://bugs.launchpad.net/bugs/2035096 ** This bug has been marked a duplicate of bug 2035096 gnome-shell crashed with SIGSEGV in clutter_stage_emit_event() -- 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/2038911 Title: /usr/bin/gnome- shell:11:clutter_stage_emit_event:emit_event:_clutter_process_event_details:clutter_stage_process_event:0xaf05af9c Status in gnome-shell package in Ubuntu: New 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 45.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/13864618e249d119c794022eb8467fb70d7565cb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2038911/+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 2038907] [NEW] Ubuntu patch incorrect disable the thunderbolt and security panels
Public bug reported: * Impact After an upstream reorganisation the patch to disable the microcophone/camera panels incorrectly disable also the rest of the device section, including thunderbolt and security which should be displayed * Testcase $ gnome-control-center privacy The right page should have a devices section listing thunderbolt (if the corresponding hardware is available) and security * Regression potential The change is a simple tweak to the .ui of the privacy panel, any bug would show in that panel. Also the thunderbolt and security panel haven't got recent testing due to this issue so they could be buggy (but it wouldn't be a regression over having the functionality not available) ** Affects: gnome-control-center (Ubuntu) Importance: High Assignee: Sebastien Bacher (seb128) Status: In Progress ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => In Progress -- 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/2038907 Title: Ubuntu patch incorrect disable the thunderbolt and security panels Status in gnome-control-center package in Ubuntu: In Progress Bug description: * Impact After an upstream reorganisation the patch to disable the microcophone/camera panels incorrectly disable also the rest of the device section, including thunderbolt and security which should be displayed * Testcase $ gnome-control-center privacy The right page should have a devices section listing thunderbolt (if the corresponding hardware is available) and security * Regression potential The change is a simple tweak to the .ui of the privacy panel, any bug would show in that panel. Also the thunderbolt and security panel haven't got recent testing due to this issue so they could be buggy (but it wouldn't be a regression over having the functionality not available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038907/+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 2038901] [NEW] Ubuntu default/minimal installation should be smaller
Public bug reported: Ubuntu default/minimal installation should be made smaller in future. It's a little too close to the full install size right now. As of mantic 2023-10-10, the default/minimal install ends up 8.4 GB whereas the full install is 9.4 GB. https://docs.google.com/spreadsheets/d/e/2PACX-1vSmQLXuDO0E-tKnWcgjL3Ua2bWDeUg4ICZIfuMrrZndBrYjbVLKAWlKuiZLZ9EOrj4N1WV37DRg8GyW/pubchart?oid=2040836911=interactive ** Affects: ubuntu-meta (Ubuntu) Importance: Wishlist Status: New ** Tags: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2038901 Title: Ubuntu default/minimal installation should be smaller Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu default/minimal installation should be made smaller in future. It's a little too close to the full install size right now. As of mantic 2023-10-10, the default/minimal install ends up 8.4 GB whereas the full install is 9.4 GB. https://docs.google.com/spreadsheets/d/e/2PACX-1vSmQLXuDO0E-tKnWcgjL3Ua2bWDeUg4ICZIfuMrrZndBrYjbVLKAWlKuiZLZ9EOrj4N1WV37DRg8GyW/pubchart?oid=2040836911=interactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2038901/+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 2038727] Re: Chromium snap theme parsing error
I'll take a good guess that you cannot actually notice the visual difference between Adwaita and Adwaita-modified in Chromium — please confirm or deny this. That is correct. No visual difference between Adwaita and Adwaita_modified. My modifications are only to the GTK-2.0 portion of the theme (scrollbar slider width and some minor text/background color changes). For GTK-3.0 related changes I use /home/aej/.config/gtk-3.0/gtk.css which snap/chromium seems to have no problem accessing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Triaged Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+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 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes error on login/live session
** Summary changed:
- df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
+ df: /sys/firmware/efi/efivars: Invalid argument causes error on login/live
session
** Description changed:
df: /sys/firmware/efi/efivars: Invalid argument appears on first display
of the live session - I note subsequently that at the end of the
installation curtin fails due to an efivars error - looking at syslog I
saw various efivars errors so I'm filing this with the kernel since this
is the first instance.
+
+ Note - raised separate issue for the installation crash which has now
+ been duplicated against
+ https://bugs.launchpad.net/subiquity/+bug/2003222
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/2038765
Title:
df: /sys/firmware/efi/efivars: Invalid argument causes error on
login/live session
Status in lightdm package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
df: /sys/firmware/efi/efivars: Invalid argument appears on first
display of the live session - I note subsequently that at the end of
the installation curtin fails due to an efivars error - looking at
syslog I saw various efivars errors so I'm filing this with the kernel
since this is the first instance.
Note - raised separate issue for the installation crash which has now
been duplicated against
https://bugs.launchpad.net/subiquity/+bug/2003222
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple
[Desktop-packages] [Bug 2038789] Re: Password for VPN not saved
alright, let's close then but feel free to reopen if you get the issue again, it could have been the bug fixed in https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/1:45.0-1ubuntu2 ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- 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/2038789 Title: Password for VPN not saved Status in gnome-control-center package in Ubuntu: Invalid Bug description: Cannot change password of a VPN connection. It doesn't get saved when you click "Apply". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038789/+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 2037274] Autopkgtest regression report (libreoffice/4:7.5.7-0ubuntu0.23.04.1)
All autopkgtests for the newly accepted libreoffice (4:7.5.7-0ubuntu0.23.04.1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: libreoffice/4:7.5.7-0ubuntu0.23.04.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#libreoffice [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2037274 Title: [SRU] libreoffice 7.5.7 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Committed Bug description: [Impact] * LibreOffice 7.5.7 is in its seventh bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.7_release * Version 7.5.6 is currently released in lunar. For a list of fixed bugs compared to 7.5.6 see the list of bugs fixed in the release candidates of 7.5.7 (that's a total of 14 bugs): https://wiki.documentfoundation.org/Releases/7.5.7/RC1#List_of_fixed_bugs 7.5.7 RC1 is identical to the 7.5.7 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [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_75/1697/ * 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. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15171690/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20230925_122613_dc43d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20230925_154920_2e924@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20230926_164913_a0855@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20230925_123824_567d4@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20230925_131148_33d08@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 14 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2037274/+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 2038727] Re: Chromium snap theme parsing error
OK, I managed to reproduce the issue. > Proposition < Chromium loads a dark theme when it finds a theme but cannot read it. Chromium loads a light theme when it doesn't find a theme. I'll take a good guess that you cannot actually notice the visual difference between Adwaita and Adwaita-modified in Chromium — please confirm or deny this. Before, Chromium wouldn't even find Adwaita-modified and thus give you no error message, and would load a default, light theme, that you identify as "matching your system theme", as you can still observe by giving GTK_THEME=random-string in the command line. Now, due to changes in XDG_DATA_HOME, Chromium finds your Adwaita- modified, but cannot nonetheless read it due to snap confinement, and decides to load instead a dark theme regardless of your system settings. As to the why there is this behavior mismatch of loading a light theme in one case and a dark one in other, I don't know yet. ** Changed in: chromium-browser (Ubuntu) Status: New => Triaged ** Tags added: regression ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2038727 Title: Chromium snap theme parsing error Status in chromium-browser package in Ubuntu: Triaged Bug description: Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not following my GTK theme. Starting the Chromium snap from the terminal yields a theme parsing error: (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error: gtk.css:1:0: Failed to import: Error opening file /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css: Permission denied Previous versions of the Chromium snap have not had this problem. Debian 11 + XFCE. I have been running the chromium snap for about two years without an issue like this on this system. I have reverted to the previous version of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+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 2038892] Re: How To Contact +1(202-960-2084) McAfee Customer Service Number?
** Package changed: cups (Ubuntu) => null-and-void ** Information type changed from Public to Private ** Changed in: null-and-void Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2038892 Title: How To Contact +1(202-960-2084) McAfee Customer Service Number? Status in NULL Project: Invalid Bug description: o contact McAfee Customer Service Phone Number, you can follow these steps: Visit the McAfee Website: Start by going to the official McAfee website. Navigate to Support: Look for a “Support” or “Contact Us” link on the website. This is typically found at the top or bottom of the homepage. Choose Your Product: Select the McAfee product you need assistance with. They offer various security solutions, so make sure to pick the right one. Access the Help Center: Many common issues can be resolved by searching the McAfee Help Center. Try entering your problem or question in the search bar. Contact Options: If you can’t find a solution in the Help Center, look for contact options. This may include phone numbers, live chat, or email support. Click on the option that suits you best. Provide Information: When contacting McAfee, be prepared to provide information like your product key, account details, and a clear description of your issue. Follow Instructions: Follow the instructions provided by McAfee’s customer support team. They may guide you through troubleshooting steps or offer a solution tailored to your problem. Record Reference Numbers: If you speak to a customer service representative or open a support ticket, make sure to record any reference numbers or case IDs for future reference. Remember that McAfee’s contact options may vary depending on your location and the specific product you’re using. Always verify the contact details on their official website to ensure you’re reaching out to legitimate customer support. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/2038892/+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 2038892] [NEW] How To Contact +1(202-960-2084) McAfee Customer Service Number?
Private bug reported: o contact McAfee Customer Service Phone Number, you can follow these steps: Visit the McAfee Website: Start by going to the official McAfee website. Navigate to Support: Look for a “Support” or “Contact Us” link on the website. This is typically found at the top or bottom of the homepage. Choose Your Product: Select the McAfee product you need assistance with. They offer various security solutions, so make sure to pick the right one. Access the Help Center: Many common issues can be resolved by searching the McAfee Help Center. Try entering your problem or question in the search bar. Contact Options: If you can’t find a solution in the Help Center, look for contact options. This may include phone numbers, live chat, or email support. Click on the option that suits you best. Provide Information: When contacting McAfee, be prepared to provide information like your product key, account details, and a clear description of your issue. Follow Instructions: Follow the instructions provided by McAfee’s customer support team. They may guide you through troubleshooting steps or offer a solution tailored to your problem. Record Reference Numbers: If you speak to a customer service representative or open a support ticket, make sure to record any reference numbers or case IDs for future reference. Remember that McAfee’s contact options may vary depending on your location and the specific product you’re using. Always verify the contact details on their official website to ensure you’re reaching out to legitimate customer support. ** Affects: null-and-void Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2038892 Title: How To Contact +1(202-960-2084) McAfee Customer Service Number? Status in NULL Project: Invalid Bug description: o contact McAfee Customer Service Phone Number, you can follow these steps: Visit the McAfee Website: Start by going to the official McAfee website. Navigate to Support: Look for a “Support” or “Contact Us” link on the website. This is typically found at the top or bottom of the homepage. Choose Your Product: Select the McAfee product you need assistance with. They offer various security solutions, so make sure to pick the right one. Access the Help Center: Many common issues can be resolved by searching the McAfee Help Center. Try entering your problem or question in the search bar. Contact Options: If you can’t find a solution in the Help Center, look for contact options. This may include phone numbers, live chat, or email support. Click on the option that suits you best. Provide Information: When contacting McAfee, be prepared to provide information like your product key, account details, and a clear description of your issue. Follow Instructions: Follow the instructions provided by McAfee’s customer support team. They may guide you through troubleshooting steps or offer a solution tailored to your problem. Record Reference Numbers: If you speak to a customer service representative or open a support ticket, make sure to record any reference numbers or case IDs for future reference. Remember that McAfee’s contact options may vary depending on your location and the specific product you’re using. Always verify the contact details on their official website to ensure you’re reaching out to legitimate customer support. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/2038892/+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
Re: [Desktop-packages] [Bug 2038875] Re: Snap uses hardcoded key and salt for password and cookie encryption
Hi Evan, thank you for the thorough report. Are you aware of Chromium having the password-manager-interface? Then it will use the keyring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2038875 Title: Snap uses hardcoded key and salt for password and cookie encryption Status in chromium-browser package in Ubuntu: New Bug description: A working Ubuntu install includes Gnome which includes the gnome- keyring. The snap version of Ubuntu does not make use of it. On an install of Debian with Gnome, the key ring is used. However, with Ubuntu everything is encrypted with the static key of peanuts and the salt of saltysalt, and openly accessible as sqlite databases in ~/snap/chromium/common/chromium, including passwords from the browser and the cookies. This should probably be fixed. If a laptop is physically compromised it's trivial to decrypt this with a tool like xbrowser. You can verify that gnome-libcrypt isn't chosen by default with --enable-logging=stderr --v=1 redirect stderr to a log and look for Crypt. You can see /why/ gnome-libcrypt isn't chosen with chromium --password-store=gnome-libcrypt --enable-logging=stderr --v=1 and again looking for messages with Crypt. I don't think this is a vulnerability per se, Chrome ships in Debian with the ability to use a basic store too. But it's an undesirable configuration and a regression from Debian when it's run on a platform with gnome and libsecret, and only doesn't work because of snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038875/+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 2038741] Re: Disk capacity shows as uknown on NVME SSD
yes it is the same issue i'm pretty sure
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/2038741
Title:
Disk capacity shows as uknown on NVME SSD
Status in udisks2 package in Ubuntu:
Incomplete
Bug description:
see picture added
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: udisks2 2.10.1-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.eog.rules 70-snap.gnome-logs.rules
70-snap.discord.rules 70-snap.snap-store.rules 70-snap.steam.rules
70-snap.element-desktop.rules 70-snap.0ad.rules 70-snap.cups.rules
70-snap.gnome-calculator.rules 70-snap.gnome-characters.rules
70-snap.snapd-desktop-integration.rules 70-snap.thunderbird.rules
70-snap.gedit.rules 70-snap.gimp.rules 70-snap.onlyoffice-desktopeditors.rules
ubuntu--vg-ubuntu--lv.rules 70-snap.kdenlive.rules 70-snap.firefox.rules
70-snap.snapd.rules
Date: Sun Oct 8 09:23:26 2023
InstallationDate: Installed on 2023-09-27 (11 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-7-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: udisks2
UpgradeStatus: Upgraded to mantic on 2023-10-03 (4 days ago)
dmi.bios.date: 09/04/2023
dmi.bios.release: 1.14
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: E15K1IMS.10E
dmi.board.asset.tag: Default string
dmi.board.name: MS-15K1
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15K1IMS.10E:bd09/04/2023:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnCyborg15A13VE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15K1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku15K1.1:
dmi.product.family: GF
dmi.product.name: Cyborg 15 A13VE
dmi.product.sku: 15K1.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2038741/+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 2028082] Autopkgtest regression report (glib2.0/2.76.4-0ubuntu1)
All autopkgtests for the newly accepted glib2.0 (2.76.4-0ubuntu1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: adsys/0.11.0 (arm64) balsa/2.6.4-2 (arm64) cmake-extras/1.6-1 (armhf) firewalld/1.3.0-1 (arm64) libsoup3/3.4.0-1 (amd64) slurm-wlm/22.05.8-3 (armhf) surf/2.1+git20221016-4build1 (armhf) udisks2/2.9.4-4 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2028082 Title: Update glib to 2.76.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+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
