[Desktop-packages] [Bug 2056331] Re: [SRU] fix suspend/resume when there are no input devices
Hello Talha, or anyone else affected, Accepted xorg-server into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:21.1.7-3ubuntu2.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xorg-server (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: xorg-server (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2056331 Title: [SRU] fix suspend/resume when there are no input devices Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Mantic: Fix Committed Status in xorg-server source package in Noble: Fix Released Bug description: [Impact] Bug is impacting the suspend/resume flow when there is no input device connected to machine. xorg hangs in this case. [Where problems could occur] The problem could occur in places where there is no input device connected to the system but a suspend/resume is triggered. [Test Case] * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed) * Update xorg-server to the version in -proposed: sudo apt install -t jammy-proposed xorg-server * Unplug all USB devices such as USB drive, keyboard, mouse, etc. * Set RTC timer and suspend the system via UART console $ echo 8 > /proc/sys/kernel/printk $ sudo rtcwake -v -m no -s 240 $ sudo systemctl suspend [Regression Potential] The patch defines a default behavior in systemd_logind_drop_master function so there is a possibility that there might be a regression that may affect all the systems that utilizes systemd_logind_drop_master Upstream Bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2056331/+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 2056331] Please test proposed package
Hello Talha, or anyone else affected, Accepted xorg-server into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:21.1.4-2ubuntu1.7~22.04.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2056331 Title: [SRU] fix suspend/resume when there are no input devices Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Mantic: Fix Committed Status in xorg-server source package in Noble: Fix Released Bug description: [Impact] Bug is impacting the suspend/resume flow when there is no input device connected to machine. xorg hangs in this case. [Where problems could occur] The problem could occur in places where there is no input device connected to the system but a suspend/resume is triggered. [Test Case] * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed) * Update xorg-server to the version in -proposed: sudo apt install -t jammy-proposed xorg-server * Unplug all USB devices such as USB drive, keyboard, mouse, etc. * Set RTC timer and suspend the system via UART console $ echo 8 > /proc/sys/kernel/printk $ sudo rtcwake -v -m no -s 240 $ sudo systemctl suspend [Regression Potential] The patch defines a default behavior in systemd_logind_drop_master function so there is a possibility that there might be a regression that may affect all the systems that utilizes systemd_logind_drop_master Upstream Bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2056331/+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 2063556] [NEW] '${outputPath}' appear instead of the real reference
Public bug reported: '${outputPath}' appear in the window while unzipping tar archive, then in the notification center it appears as '${fullPathFile}', in addiction the minimize button doesn't work ## release No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 # package version (gjs) gjs: Installato: 1.80.2-1build2 Candidato: 1.80.2-1build2 Tabella versione: *** 1.80.2-1build2 500 500 http://it.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gjs 1.80.2-1build2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 09:20:47 2024 InstallationDate: Installed on 2024-04-25 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "Schermata del 2024-04-26 09-04-22.png" https://bugs.launchpad.net/bugs/2063556/+attachment/5770832/+files/Schermata%20del%202024-04-26%2009-04-22.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2063556 Title: '${outputPath}' appear instead of the real reference Status in gjs package in Ubuntu: New Bug description: '${outputPath}' appear in the window while unzipping tar archive, then in the notification center it appears as '${fullPathFile}', in addiction the minimize button doesn't work ## release No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 # package version (gjs) gjs: Installato: 1.80.2-1build2 Candidato: 1.80.2-1build2 Tabella versione: *** 1.80.2-1build2 500 500 http://it.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gjs 1.80.2-1build2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 09:20:47 2024 InstallationDate: Installed on 2024-04-25 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2063556/+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 2062967] Re: ubuntu-drivers no longer offers nvidia 550 drivers
Thank you for the report, bug #2061830 might provider some context there > Since 550 wasn't included in the beta we should limit the potential impact on > 24.04 stability by limiting > the driver to be loaded only on the new hw supported by this driver. This > will be temporary until we are > ready to migrate 535 to 550. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2062967 Title: ubuntu-drivers no longer offers nvidia 550 drivers Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: While I am unclear which package update impacted the video drivers detected by ubuntu-drivers, the nvidia 545 and nvidia 550 video drivers are no longer shown as an option on NVIDIA GeForce GTX 1050 video card. I can understand the removal of the nvidia 545 drivers as the current kernel's linux-signatures-nvidia-6.8.0-28-generic package lacks signatures for the nvidia 545 kernel modules for secure boot but the nvidia 550 kernel modules signatures are available. So while it would be acceptable to downgrade the 'tested' default nvidia driver to 535, ubuntu-drivers and Additional Drivers should be offering the nvidia 550 drivers as an untested option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2062967/+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 2061708] Re: Yubikey stopped working after noble upgrade
https://blog.apdu.fr/posts/2024/04/gnupg-and-pcsc-conflicts-episode-2/ I do not use GnuPG with a smartcard. So I don't know which configuration is more stable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/2061708 Title: Yubikey stopped working after noble upgrade Status in Arch Linux on Launchpad: Fix Released Status in gnupg2 package in Ubuntu: Triaged Status in pcsc-lite package in Ubuntu: Invalid Bug description: In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but since upgrading to Noble I get the following trying to access it. $ gpg --card-status gpg: selecting card failed: No such device gpg: OpenPGP card not available: No such device If I run this as root it works: $ sudo gpg --card-status Reader ...: 1050:0407:X:0 Application ID ...: D27600012401000609082616 Application type .: OpenPGP Version ..: 2.1 Manufacturer .: Yubico Serial number : Name of cardholder: [not set] Language prefs ...: [not set] Salutation ...: URL of public key : [not set] Login data ...: [not set] Signature PIN : not forced Key attributes ...: rsa4096 rsa4096 rsa2048 Max. PIN lengths .: 127 127 127 PIN retry counter : 10 0 10 Signature counter : 1172 UIF setting ..: Sign=off Decrypt=off Auth=off Signature key : created : Encryption key: created : Authentication key: [none] General key info..: [none] If I manually run pcscd.service then it stops working both as root and a user. $ sudo pkill -9 scdaemon $ sudo systemctl start pcscd.service $ gpg --card-status gpg: selecting card failed: No such device gpg: OpenPGP card not available: No such device $ sudo gpg --card-status gpg: selecting card failed: No such device gpg: OpenPGP card not available: No such device It might be worth mentioning I'm accessing the machine over SSH, so I also did experiment with a polkit rule like this: polkit.addRule(function(action, subject) { if (action.id == "org.debian.pcsc-lite.access_card" && subject.isInGroup("sudo")) { return polkit.Result.YES; } }); polkit.addRule(function(action, subject) { if (action.id == "org.debian.pcsc-lite.access_pcsc" && subject.isInGroup("sudo")) { return polkit.Result.YES; } }); Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading polkit.service in case this was a polkit issue, but this didn't do anything. Versions in noble: pcscd: 2.0.3-1build1 libpcslite1: 2.0.3-1build1 gnupg: 2.4.4-2ubuntu17 scdaemon: 2.4.4-2ubuntu17 To manage notifications about this bug go to: https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+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 2063397] Re: extracting rar archives sometime incomplete
Thanks, confirming that extracting that archive leads to described issues. You mentioned data loss in the original description so I guess the 'directory with empty files' might not be the only trigger but at least we have a base to work on I've reported the file-roller segfault upstream now https://gitlab.gnome.org/GNOME/file-roller/-/issues/243 Nautilus crashing when trying to compress is a known upstream issue fixes in 46.1 which we will SRU https://gitlab.gnome.org/GNOME/nautilus/-/commit/6ea1f9ad ** Bug watch added: gitlab.gnome.org/GNOME/file-roller/-/issues #243 https://gitlab.gnome.org/GNOME/file-roller/-/issues/243 ** Changed in: nautilus (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2063397 Title: extracting rar archives sometime incomplete Status in nautilus package in Ubuntu: Triaged Bug description: Extraction of rar files (v5) from the context menu ("Extract") occasionally results in one or more subfolders silently being skipped. This behavior is not systematic. Some rar archives extract properly, other ones do not. There is not any warning or error message when the problem manifests, which make it likely that the problem goes overlooked. I have effectively sustained data loss until I discovered that one of my extracted folders was much smaller than it should have been. I have unrar (non-free) and 7z installed. Applications like file-roller and arqiver appear to function properly. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 05:26:17 2024 InstallationDate: Installed on 2022-03-27 (759 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: eiciel0.10.0-1build2 file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 python3-nautilus 4.0-1build4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063397/+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 2063476] Re: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2
** Tags added: xilinx ** Summary changed: - libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 + Xilinx: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2063476 Title: Xilinx: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 Status in gnome-control-center package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Cannot run gnome-control-center due to missing symbol lookup. Please see the output of the console: ``` ubuntu@kria:~$ gnome-control-center -h gnome-control-center: symbol lookup error: /lib/aarch64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.8 ProcVersionSignature: Ubuntu 5.15.0-1027.31-xilinx-zynqmp 5.15.136 Uname: Linux 5.15.0-1027-xilinx-zynqmp aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk1p1) Date: Thu Apr 25 16:57:26 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063476/+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 2063153] Re: Incorrect display Graphics Card in System -> system details
** Tags added: noble -- 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/2063153 Title: Incorrect display Graphics Card in System -> system details Status in gnome-control-center package in Ubuntu: New Bug description: NVIDIA GeForce RTX 3050 Ti Mobile should be displayed here To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012371] Re: [FFe] ubuntu-proxy-manager and adsys
this still does not have the SRU information as requested ~11 months ago... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2012371 Title: [FFe] ubuntu-proxy-manager and adsys Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Jammy: Incomplete Status in adsys source package in Lunar: Won't Fix Bug description: Ubuntu Proxy Manager is a D-Bus mediated service that allows for managing system proxy settings via multiple backends (APT, environment variables and GSettings). We request a FFe for this new source package (ubuntu-proxy-manager). As it's a new source package the risk of it breaking existing setups is non-existent as it must be explicitly opted into by users. The package is written in Go and benefits from an extensive test suite covering over 90% of the codebase. Additionally, we would like to request a FFe for adsys where we added a Suggests dependency on ubuntu-proxy-manager. We have taken great care on the adsys part to maintain backwards compatibility and not affect users who do not install the ubuntu-proxy-manager package. Installing the ubuntu-proxy-manager package on its own has no impact to the system. To benefit from its functionality adsys has to be upgraded and correctly configured. - Relevant URLs: 1. ubuntu-proxy-manager homepage: https://github.com/ubuntu/ubuntu-proxy-manager 2. ubuntu-proxy-manager implementation in ADSys: https://github.com/ubuntu/adsys/pull/637 3. LP build of ubuntu-proxy-manager: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562796/+listing-archive-extra 4. LP build of adsys: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/14562807/+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2012371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063397] Re: extracting rar archives sometime incomplete
The gnome-autoar test-extract utility has the same issue, I've reported that upstream now, https://gitlab.gnome.org/GNOME/gnome- autoar/-/issues/48 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-autoar/-/issues #48 https://gitlab.gnome.org/GNOME/gnome-autoar/-/issues/48 ** Package changed: nautilus (Ubuntu) => gnome-autoar (Ubuntu) ** Also affects: gnome-autoar via https://gitlab.gnome.org/GNOME/gnome-autoar/-/issues/48 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-autoar in Ubuntu. https://bugs.launchpad.net/bugs/2063397 Title: extracting rar archives sometime incomplete Status in GNOME Autoar: Unknown Status in gnome-autoar package in Ubuntu: Triaged Bug description: Extraction of rar files (v5) from the context menu ("Extract") occasionally results in one or more subfolders silently being skipped. This behavior is not systematic. Some rar archives extract properly, other ones do not. There is not any warning or error message when the problem manifests, which make it likely that the problem goes overlooked. I have effectively sustained data loss until I discovered that one of my extracted folders was much smaller than it should have been. I have unrar (non-free) and 7z installed. Applications like file-roller and arqiver appear to function properly. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 05:26:17 2024 InstallationDate: Installed on 2022-03-27 (759 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: eiciel0.10.0-1build2 file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 python3-nautilus 4.0-1build4 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-autoar/+bug/2063397/+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 2056331] Re: [SRU] fix suspend/resume when there are no input devices
Hello Timo, On jammy, ``` No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy ``` I was able to reproduce the issue using old version of the xorg-server package(2:21.1.4-2ubuntu1.7~22.04.10), for the ones who are curious about the bug, first you need to boot the board with keyboard/mouse connected to usb and display attached and then login as usual. Then remove all usb device and follow the steps in bug description through tty console. After enabling -proposed and updating xorg-server packages to 2:21.1.4-2ubuntu1.7~22.04.11, I followed the same steps to reproduce the bug. I can confirm that the bug has been fixed with 2:21.1.4-2ubuntu1.7~22.04.11 Thank you all! ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2056331 Title: [SRU] fix suspend/resume when there are no input devices Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Mantic: Fix Committed Status in xorg-server source package in Noble: Fix Released Bug description: [Impact] Bug is impacting the suspend/resume flow when there is no input device connected to machine. xorg hangs in this case. [Where problems could occur] The problem could occur in places where there is no input device connected to the system but a suspend/resume is triggered. [Test Case] * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed) * Update xorg-server to the version in -proposed: sudo apt install -t jammy-proposed xorg-server * Unplug all USB devices such as USB drive, keyboard, mouse, etc. * Set RTC timer and suspend the system via UART console $ echo 8 > /proc/sys/kernel/printk $ sudo rtcwake -v -m no -s 240 $ sudo systemctl suspend [Regression Potential] The patch defines a default behavior in systemd_logind_drop_master function so there is a possibility that there might be a regression that may affect all the systems that utilizes systemd_logind_drop_master Upstream Bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2056331/+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 2024377] Re: Adsys can't fetch GPOs
SRU information missing from the description -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2024377 Title: Adsys can't fetch GPOs Status in adsys package in Ubuntu: Fix Released Bug description: Bad, maybe no understandable english ahead. Can't find anything related to this on Github, Canonical Forums, Reddit or StackOverflow. On Ubuntu 22.04, I've followed the Wiki tutorial and verified all steps on Integration Ubuntu Desktop whitepaper. Currently using SSSD backend, I can log with Active Directory users however when adsys is installed I can't fetch GPOs. In this version the error is: ERROR Error from server: error while updating policy: can't get policies for "ubuntu": can't download all gpos and assets: one or more error while fetching GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot open smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI: invalid argument It happens when using "adsysctl update -m" or "adsysctl update usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just "adsysctl update" too. I've upgrade the machine to 22.10 and the error changed to: ERROR Error from server: error while updating policy: can't get policies for "ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1 Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP client internal error: NT_STATUS_INVALID_PARAMETER Failed to open session: (1, 'LDAP client internal error: NT_STATUS_INVALID_PARAMETER'). After upgrade to 23.04 the error persist same as the above. Full info 22.04 (- verbose): INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates /root /etc /usr/sbin]". We will only use the defaults, env variables or flags. DEBUG Connecting as [[2504:109556]] DEBUG New request /service/UpdatePolicy DEBUG Requesting with parameters: IsComputer: true, All: false, Target: ubuntu, Krb5Cc: DEBUG NormalizeTargetName for "ubuntu", type "computer" DEBUG Check if grpc request peer is authorized DEBUG Authorized as being administrator DEBUG GetPolicies for "ubuntu", type "computer" DEBUG Getting gpo list with arguments: "--objectclass computer ldap://addc01.domain.com.br ubuntu" DEBUG GPO "ubuntuRoot" for "ubuntu" available at "smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}" DEBUG Analyzing "assets" DEBUG Analyzing "ubuntuRoot" INFO No assets directory with GPT.INI file found on AD, skipping assets download ERROR Error from server: error while updating policy: can't get policies for "ubuntu": can't download all gpos and assets: one or more error while fetching GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot open smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI: invalid argument Full info 23.04 (- verbose): INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates /root /etc /usr/sbin]". DEBUG Connecting as [[58811:006019]] DEBUG New request /service/UpdatePolicy DEBUG Requesting with parameters: IsComputer: true, All: false, Target: ubuntu, Krb5Cc: DEBUG NormalizeTargetName for "ubuntu", type "computer" DEBUG Check if grpc request peer is authorized DEBUG Authorized as being administrator DEBUG GetPolicies for "ubuntu", type "computer" DEBUG Getting gpo list with arguments: "--objectclass computer ldap://addc01.domain.com.br ubuntu" ERROR Error from server: error while updating policy: can't get policies for "ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1 Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP client internal error: NT_STATUS_INVALID_PARAMETER Failed to open session: (1, 'LDAP client internal error: NT_STATUS_INVALID_PARAMETER') Additional info: Domain Controller and machine are on the same subnet without firewall on any level; Domain Controller is a Windows Server 2019 updated to the last security version; Both machine and user are on the same OU with "no heritage" enabled and just one policy added to permit usern...@domain.com.br to become root; The info header directory is "/home/jzprates" on both logs because I've collected them using the local account using "sudo adsysctl update -m -"; If I disable Adsys login on pam-auth-update, Ubuntu creates a homedir and enter correctly with domain users. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: adsys 0.11.0 ProcVe
[Desktop-packages] [Bug 2051363] Re: Cannot perform certificate auto-enroll without NDES installed
SRU information missing from the description -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2051363 Title: Cannot perform certificate auto-enroll without NDES installed Status in adsys package in Ubuntu: Fix Released Bug description: NDES role should not be mandatory in order to perform certificate auto-enrollment with adsys. Samba/ADSys is able to take advantage of the NDES endpoint to install the root certificate chain, but is also able to infer the certificate information from LDAP. Due to a bug in the Samba implementation of cert-autoenroll, the root cert is not parsed properly if the NDES component is not installed -- so in the current state attempting auto-enrollment without NDES installed will result in an error like the following: 2024-01-08 16:11:07.809|[W26775]| Failed to fetch the root certificate chain. | {} 2024-01-08 16:11:07.809|[W05621]| The Network Device Enrollment Service is either not installed or not configured. | {} 2024-01-08 16:11:07.809|[W11946]| Installing the server certificate only. | {} Traceback (most recent call last): File "", line 142, in File "", line 89, in main File "", line 20, in enroll File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", line 502, in __enroll self.apply(guid, ca, cert_enroll, ca, ldb, trust_dir, File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", line 369, in apply data = applier_func(*args, **kwargs) ^ File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", line 274, in cert_enroll root_certs = getca(ca, url, trust_dir) ^ File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", line 221, in getca cert = load_der_x509_certificate(ca['cACertificate'], ^^ File "/usr/lib/python3/dist-packages/cryptography/x509/base.py", line 528, in load_der_x509_certificate return rust_x509.load_der_x509_certificate(data) ^ TypeError: argument 'data': 'str' object cannot be converted to 'PyBytes' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2051363/+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 2054445] Re: Regresion in sssd backend configuration
SRU information missing from the description -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2054445 Title: Regresion in sssd backend configuration Status in adsys package in Ubuntu: Fix Released Bug description: This is a regression from when we added support for multiple AD backends (see https://github.com/ubuntu/adsys/pull/467) Previously adsys would use the first domain from `sssd.conf` and potentially override it if `ad_domain` is explicitly set for the domain, see: https://github.com/ubuntu/adsys/blob/32a830f2a8204cc8b896094bad512ed619fbf6b7/internal/adsysservice/adsysservice.go#L279-L280 The current implementation raises an error if we are not able to find an `ad_domain` setting in the domain section, even if we already have a domain (`sssdDomain`): https://github.com/ubuntu/adsys/blob/c68d2cc999d25b1cb408a9e31775a76d2af4c8c7/internal/ad/backends/sss/sss.go#L62-L65 Ideally we should set `domain` to `sssdDomain` if we cannot find a value for `ad_domain`, which will mimic the behavior previous to the refactor. While by default joining a domain with `realm join` will set the appropriate configuration values in `sssd.conf` so this doesn't happen, this is a regression we should aim to fix. ### Steps to reproduce it 1. Join an AD domain with sssd (e.g. using `realm join`) 2. Install the latest version of adsys, run `adsysctl update -m -vv`, everything should work 3. Comment out the `ad_domain` line from `/etc/sssd/sssd.conf` 4. `adsysctl update -m -vv` now fails, and the adsysd service does not start anymore 5. (Optional) To confirm the functionality prior to the regression, re-attempt the steps above on Ubuntu 22.04 using the adsys version currently in the archive (0.9.2) -- adsys is able to correctly determine the domain even without the `ad_domain` setting. GitHub issue: https://github.com/ubuntu/adsys/issues/910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2054445/+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 2037271] Re: No pot file extraction when using multiple lines
SRU information missing from the description -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2037271 Title: No pot file extraction when using multiple lines Status in adsys package in Ubuntu: Fix Released Bug description: Upstream C gettext does not extract successfully the strings mark up for translation when they are on multiple lines. Switch to our go-i18n module to achieve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2037271/+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 2037270] Re: No PAM module is shipped in mantic
SRU information missing from the description -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2037270 Title: No PAM module is shipped in mantic Status in adsys package in Ubuntu: Fix Released Bug description: Due to an issue in using multiple tags introduced in 0.12, the PAM module was not generated, and thus, shipped by the debian package anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2037270/+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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
I'm upstream. I saw the removal first in the release notes. Yet I'm not surprised by removal. The contributions to pptp and pptpd have declined, so the release cadence has slowed as well (1.4.0 in 2013, but a few commits in git since). Number of people asking for help has also declined. Some countries or corporations still require it, presumably because it is so easily monitored. Using pptpd on Ubuntu will be more difficult because of removal from Ubuntu, but that's just a security by obscurity; very easily bypassed by installing the software yourself. Thanks for holding on so long. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Fix Released Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. Current Windows versions natively support IPSec and L2TP as much better alternatives. https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- configuration#how-to-use-wfp-to-configure-ipsec-policies https://learn.microsoft.com/en-US/troubleshoot/windows- server/networking/configure-l2tp-ipsec-server-behind-nat-t-device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2041751/+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 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly
Hello Philipp, or anyone else affected, Accepted poppler into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/poppler/22.02.0-2ubuntu0.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: poppler (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1980836 Title: Regression in Ubuntu 22.04: Content of form field stored invisibly Status in Poppler: Fix Released Status in evince package in Ubuntu: Invalid Status in poppler package in Ubuntu: Triaged Status in evince source package in Jammy: Invalid Status in poppler source package in Jammy: Fix Committed Bug description: [ Impact ] The bug causes text entered in certain PDF form fields to be stored but both displayed and printed white (on white background). [ Test Plan ] 1. Download the attached 230-muster-01.pdf. 2. Try to input to any of the main content fields starting with 06-09 ("Anrede des Zahlungspflichtigen etc"). 3. Observe that it does not work. 4. Install the updated poppler package versions 5. Try the same fields and see they're functoning properly now with visible text. 6. Test also that the fields like "Aktenzeichen", "TL-Nr." or "Buchungsstelle" that weren't broken, continue to work. [ Where problems could occur ] It is a merged upstream fix to Annot.cc file that fixed two upstream bugs https://gitlab.freedesktop.org/poppler/poppler/-/issues/1189 and https://gitlab.freedesktop.org/poppler/poppler/-/issues/1267. There are no indications of upstream regressions caused by this fix, and it was released in upstream stable release 22.08.0 (Ubuntu 22.04 LTS has version based on 22.02.0). However, since it's an individual cherry-pick there could always be a PDF somewhere having issues with this, so it's useful to let it be tested with various files in addition to the problematic ones. --- original report --- Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04. The symptom is that one can edit the form content and also save it, but that the entered text is only visible when the form field is focused and in edit mode. Otherwise the text it is invisible, also on printouts. Such bugs have been reported against Evince for a long time (e.g., https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I am reporting this as a new bug because for the current form with which I am experiencing this it is a regression. I have attached the problematic form with two form fields filled out, one in the upper left corner and the big one in the lower half. I have produced this by taking the original, empty form (produced by somebody else) and first opened it in Evince 41.4, which I have installed from the snap package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field and saved the form. Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and entered text in the big field and saved the form. Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince 41.4. When I open the PDF again, only the text in the first field is visible. The text in the second field is visible only if I click into the field. The visibility of the field contents is the same for Evince 41.4 (snap), Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems that the problem is with Evince 42.3 incorrectly saving the field content, not with displaying it. Firefox shows and prints the content of both fields, though. Note that I cannot switch back to Evince 41 because for some other forms that I have the exact same problem happens only with
[Desktop-packages] [Bug 2044112] Re: Add dependency on nfs-common
SRU information missing from the description -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2044112 Title: Add dependency on nfs-common Status in adsys package in Ubuntu: Fix Released Bug description: The nfs-common package is required if NFS shares are to be mounted on the client. Unlike cifs-utils, this package is not installed by default on Ubuntu Desktop. Given that we declare the former as a dependency we should do the same with nfs-common. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2044112/+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 2063815] [NEW] No microphone available
Public bug reported: The system Ubuntu 24.04 does not detect any microphone. The system is Lenovo ThinkPad T14 Gen4. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:frybort2330 F pipewire /dev/snd/controlC0: frybort2334 F wireplumber /dev/snd/controlC1: frybort2334 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 11:37:02 2024 InstallationDate: Installed on 2024-04-19 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) MachineType: LENOVO 21K3003RCK PackageArchitecture: all ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2024 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET55W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3003RCK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR2FET55W(1.35):bd02/20/2024:br1.35:efr1.28:svnLENOVO:pn21K3003RCK:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3003RCK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3003RCK dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2063815 Title: No microphone available Status in alsa-driver package in Ubuntu: New Bug description: The system Ubuntu 24.04 does not detect any microphone. The system is Lenovo ThinkPad T14 Gen4. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:frybort2330 F pipewire /dev/snd/controlC0: frybort2334 F wireplumber /dev/snd/controlC1: frybort2334 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 11:37:02 2024 InstallationDate: Installed on 2024-04-19 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) MachineType: LENOVO 21K3003RCK PackageArchitecture: all ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2024 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET55W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3003RCK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR2FET55W(1.35):bd02/20/2024:br1.35:efr1.28:svnLENOVO:pn21K3003RCK:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3003RCK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3003RCK dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2063815/+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 2049061] Re: adsysctl update with a domain user fails if KRB5CCNAME is not set
SRU information missing from the description -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2049061 Title: adsysctl update with a domain user fails if KRB5CCNAME is not set Status in adsys package in Ubuntu: Fix Released Bug description: In an environment where /etc/krb5.conf sets "default_ccache_name = FILE:/tmp/krb5cc_%{uid}" and you don't have the KRB5CCNAME variable set, running "adsysctl update" with a AD domain user will fail. If you either export the variable with the path to the kerberos ticket OR run the command "adsysctl update " it works. The adsysctl command should fallback to the default location when KRB5CCNAME is not defined or have a mechanism to query klist and find the Kerberos tickets location. Given that adsys can't find Kerberos tickets when `klist` does. It seems like a feature parity issue, granted, an edge case. Here is an example of a reproducer: https://pastebin.ubuntu.com/p/FjyTWQChjM/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: adsys 0.9.2~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1014-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) CurrentDesktop: ubuntu:GNOME Date: Thu Jan 11 11:39:06 2024 Ec2AMI: ami-00094f7041bb1b79d Ec2AMIManifest: (unknown) Ec2Architecture: x86_64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-00094f7041bb1b79d Ec2InstanceType: t3.large Ec2Instancetype: t3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: sssd 2.6.3-1ubuntu3.2 python3-samba 2:4.15.13+dfsg-0ubuntu1.5 SourcePackage: adsys UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.polkit-1.localauthority.conf.d.99-adsys-privilege-enforcement.conf: [deleted] modified.conffile..etc.sudoers.d.99-adsys-privilege-enforcement: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2049061/+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 2063501] Re: Sometimes gnome-shell crash upon unlocking session from suspension
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2063501/+attachment/5770842/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: Sometimes gnome-shell crash upon unlocking session from suspension Status in gnome-shell package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+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 2063501] Re: Sometimes gnome-shell crash upon unlocking session from suspension
** Attachment added: "prevjournal-1.txt" https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2063501/+attachment/5770843/+files/prevjournal-1.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: Sometimes gnome-shell crash upon unlocking session from suspension Status in gnome-shell package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+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 2063501] Re: Sometimes gnome-shell crash upon unlocking session from suspension
** Attachment added: "prevjournal-2.txt" https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2063501/+attachment/5770844/+files/prevjournal-2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: Sometimes gnome-shell crash upon unlocking session from suspension Status in gnome-shell package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+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 2063397] Re: extracting rar archives sometime incomplete
** Changed in: gnome-autoar Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-autoar in Ubuntu. https://bugs.launchpad.net/bugs/2063397 Title: extracting rar archives sometime incomplete Status in GNOME Autoar: New Status in gnome-autoar package in Ubuntu: Triaged Bug description: Extraction of rar files (v5) from the context menu ("Extract") occasionally results in one or more subfolders silently being skipped. This behavior is not systematic. Some rar archives extract properly, other ones do not. There is not any warning or error message when the problem manifests, which make it likely that the problem goes overlooked. I have effectively sustained data loss until I discovered that one of my extracted folders was much smaller than it should have been. I have unrar (non-free) and 7z installed. Applications like file-roller and arqiver appear to function properly. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 05:26:17 2024 InstallationDate: Installed on 2022-03-27 (759 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: eiciel0.10.0-1build2 file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 python3-nautilus 4.0-1build4 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-autoar/+bug/2063397/+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 2063501] Re: Sometimes gnome-shell crash upon unlocking session from suspension
https://errors.ubuntu.com/user/2b93ad219b48c9b97a7a077caec6d69c0c1775edbb7ed9adc197eb0f82ef67bad56000432096446e2a08ce86802994b7d7974a33972dece2b7b97ff663da8f05 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: Sometimes gnome-shell crash upon unlocking session from suspension Status in gnome-shell package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+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 2063828] Re: v4l-utils failed to flip upside down webcam.
The out put of "v4l2-ctl -d /dev/video0 -l" User Controls brightness 0x00980900 (int): min=-64 max=64 step=1 default=0 value=0 contrast 0x00980901 (int): min=0 max=64 step=1 default=32 value=32 saturation 0x00980902 (int): min=0 max=128 step=1 default=67 value=67 hue 0x00980903 (int): min=-40 max=40 step=1 default=0 value=0 white_balance_automatic 0x0098090c (bool) : default=1 value=1 gamma 0x00980910 (int): min=72 max=150 step=1 default=110 value=110 gain 0x00980913 (int): min=0 max=80 step=1 default=0 value=0 power_line_frequency 0x00980918 (menu) : min=0 max=2 default=2 value=2 (60 Hz) white_balance_temperature 0x0098091a (int): min=2800 max=6500 step=1 default=4600 value=4600 flags=inactive sharpness 0x0098091b (int): min=0 max=6 step=1 default=3 value=3 backlight_compensation 0x0098091c (int): min=0 max=2 step=1 default=1 value=1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/2063828 Title: v4l-utils failed to flip upside down webcam. Status in v4l-utils package in Ubuntu: New Bug description: About a year ago (June 2023) I can flip my upside down webcam using LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4lconvert.so.0 . But now, It's no longer works. When I launch webcam app (e.g cheese or snapshot), it's always upside down, whether I use LD_PRELOAD or not. My machine is an Asus laptop (Asus PRO36S / U36SD) and my webcam is Asus Integrated Webcam from Chicony Electronics Co. This is the output of "lsusb | grep Webcam" : Bus 002 Device 004: ID 04f2:b1b9 Chicony Electronics Co., Ltd Asus Integrated Webcam. - I'm using Ubuntu Noble / 24.04. - The version of v4l-utils package is 1.26.1-4build3. - I expect the library from v4l-utils will flip my upside down webcam using LD_PRELOAD. - What I get is the library from v4l-utils won't flip my upside down webcam. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: v4l-utils 1.26.1-4build3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 26 18:16:57 2024 SourcePackage: v4l-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/2063828/+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 2063827] [NEW] Gnome Control Center fails to open on Wayland
Public bug reported: Hello, I just installed Ubuntu 24.04 LTS and I realized that Gnome Control Center does not open on Wayland, but does on Xorg, attempting to open it will simply open the crash dialog after some time. When running from the terminal: $ gnome-control-center libEGL warning: egl: failed to create dri2 screen Segmentation fault (core dumped) Version installed: gnome-control-center: Installed: 1:46.0.1-1ubuntu7 Candidate: 1:46.0.1-1ubuntu7 My current installation is very lightweight, and I haven't removed any packages or changed any system files. This occurs on a Nvidia GPU, specifically the NVIDA GeForce 1060 3GB with the driver version being 535.171.04 If more information is needed, please let me know, however I might be slow to respond. Thank you. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Incomplete -- 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/2063827 Title: Gnome Control Center fails to open on Wayland Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Hello, I just installed Ubuntu 24.04 LTS and I realized that Gnome Control Center does not open on Wayland, but does on Xorg, attempting to open it will simply open the crash dialog after some time. When running from the terminal: $ gnome-control-center libEGL warning: egl: failed to create dri2 screen Segmentation fault (core dumped) Version installed: gnome-control-center: Installed: 1:46.0.1-1ubuntu7 Candidate: 1:46.0.1-1ubuntu7 My current installation is very lightweight, and I haven't removed any packages or changed any system files. This occurs on a Nvidia GPU, specifically the NVIDA GeForce 1060 3GB with the driver version being 535.171.04 If more information is needed, please let me know, however I might be slow to respond. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063827/+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 2019906] Re: 24.04 : condensed, bold and black fonts can't be used for interface and title bar
Sorry for commenting again, maybe best workaround is installing older Ubuntu fonts ( taken from 20.04 ) as listed below where ubuntu_initial are now default in 24.04 and ubuntu are the older ones. django@ASGARD:~$ ls -la /usr/share/fonts/truetype/ubuntu* /usr/share/fonts/truetype/ubuntu: total 4084 drwxr-xr-x 2 root root 4096 avril 26 04:27 . drwxr-xr-x 22 root root 4096 avril 26 04:43 .. -rw-r--r-- 1 root root 356980 avril 26 04:27 Ubuntu-BI.ttf -rw-r--r-- 1 root root 333612 avril 26 04:27 Ubuntu-B.ttf -rw-r--r-- 1 root root 350444 avril 26 04:27 Ubuntu-C.ttf -rw-r--r-- 1 root root 409608 avril 26 04:27 Ubuntu-LI.ttf -rw-r--r-- 1 root root 415552 avril 26 04:27 Ubuntu-L.ttf -rw-r--r-- 1 root root 366992 avril 26 04:27 Ubuntu-MI.ttf -rw-r--r-- 1 root root 216208 avril 26 04:27 UbuntuMono-BI.ttf -rw-r--r-- 1 root root 191400 avril 26 04:27 UbuntuMono-B.ttf -rw-r--r-- 1 root root 210216 avril 26 04:27 UbuntuMono-RI.ttf -rw-r--r-- 1 root root 205748 avril 26 04:27 UbuntuMono-R.ttf -rw-r--r-- 1 root root 341324 avril 26 04:27 Ubuntu-M.ttf -rw-r--r-- 1 root root 386440 avril 26 04:27 Ubuntu-RI.ttf -rw-r--r-- 1 root root 353824 avril 26 04:27 Ubuntu-R.ttf -rw-r--r-- 1 root root 36 avril 26 04:27 .uuid /usr/share/fonts/truetype/ubuntu_initial: total 4256 drwxr-xr-x 2 root root4096 avril 24 12:48 . drwxr-xr-x 22 root root4096 avril 26 04:43 .. lrwxrwxrwx 1 root root 28 mars 21 21:03 Ubuntu-BI.ttf -> 'Ubuntu-Italic[wdth,wght].ttf' lrwxrwxrwx 1 root root 21 mars 21 21:03 Ubuntu-B.ttf -> 'Ubuntu[wdth,wght].ttf' lrwxrwxrwx 1 root root 21 mars 21 21:03 Ubuntu-C.ttf -> 'Ubuntu[wdth,wght].ttf' -rw-r--r-- 1 root root 679224 mars 21 21:03 'Ubuntu-Italic[wdth,wght].ttf' lrwxrwxrwx 1 root root 28 mars 21 21:03 Ubuntu-LI.ttf -> 'Ubuntu-Italic[wdth,wght].ttf' lrwxrwxrwx 1 root root 21 mars 21 21:03 Ubuntu-L.ttf -> 'Ubuntu[wdth,wght].ttf' lrwxrwxrwx 1 root root 28 mars 21 21:03 Ubuntu-MI.ttf -> 'Ubuntu-Italic[wdth,wght].ttf' lrwxrwxrwx 1 root root 27 mars 21 21:03 UbuntuMono-BI.ttf -> 'UbuntuMono-Italic[wght].ttf' lrwxrwxrwx 1 root root 20 mars 21 21:03 UbuntuMono-B.ttf -> 'UbuntuMono[wght].ttf' -rw-r--r-- 1 root root 172196 mars 21 21:03 'UbuntuMono-Italic[wght].ttf' lrwxrwxrwx 1 root root 27 mars 21 21:03 UbuntuMono-RI.ttf -> 'UbuntuMono-Italic[wght].ttf' lrwxrwxrwx 1 root root 20 mars 21 21:03 UbuntuMono-R.ttf -> 'UbuntuMono[wght].ttf' -rw-r--r-- 1 root root 172232 mars 21 21:03 'UbuntuMono[wght].ttf' lrwxrwxrwx 1 root root 21 mars 21 21:03 Ubuntu-M.ttf -> 'Ubuntu[wdth,wght].ttf' lrwxrwxrwx 1 root root 28 mars 21 21:03 Ubuntu-RI.ttf -> 'Ubuntu-Italic[wdth,wght].ttf' lrwxrwxrwx 1 root root 21 mars 21 21:03 Ubuntu-R.ttf -> 'Ubuntu[wdth,wght].ttf' -rw-r--r-- 1 root root 738444 mars 21 20:56 'UbuntuSans-Italic[wdth,wght].ttf' -rw-r--r-- 1 root root 186356 mars 21 20:56 'UbuntuSansMono-Italic[wght].ttf' -rw-r--r-- 1 root root 230324 mars 21 20:56 'UbuntuSansMono[wght].ttf' -rw-r--r-- 1 root root 1080900 mars 21 20:56 'UbuntuSans[wdth,wght].ttf' lrwxrwxrwx 1 root root 21 mars 21 21:03 Ubuntu-Th.ttf -> 'Ubuntu[wdth,wght].ttf' -rw-r--r-- 1 root root 1072960 mars 21 21:03 'Ubuntu[wdth,wght].ttf' django@ASGARD:~$ The big difference here is the linked variants which suggest a variable font type and maybe those are the culprits. Older fonts were one file per variant. Now if I set [ Ubuntu Condensed, Regular 13 ] as font-name in /org/gnome/desktop/interface/font-name everything seems to work fine. -- 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/2019906 Title: 24.04 : condensed, bold and black fonts can't be used for interface and title bar Status in budgie-desktop package in Ubuntu: Confirmed Status in fonts-ubuntu package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Hi, fresh lunar lobster installation here, from legacy iso image ( ubiquity installer. ) As I usually do, I tried to change the font for interface, as I much prefer « condensed » fonts rather than large, round, regular ones. In 20.04 or 22.04 or 22.10 gnome-tweaks allowed to do that. Today in 23.04, it only changes font in gnome-shell ( top panel, activities and app's views ) but not in other app's, not in the whole interface as it used to do. In dconf-editor I did not find entries regarding « global » interface font. Is this intended behavior ? Ability to change font type and size is also a matter of accessibility. For references : ⋅ https://askubuntu.com/questions/1468338/23-04-how-change-font-in-interface-gnome-shell-window-title-bar ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2079313 This affects many users. To manag
[Desktop-packages] [Bug 2063828] [NEW] v4l-utils failed to flip upside down webcam.
Public bug reported: About a year ago (June 2023) I can flip my upside down webcam using LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4lconvert.so.0 . But now, It's no longer works. When I launch webcam app (e.g cheese or snapshot), it's always upside down, whether I use LD_PRELOAD or not. My machine is an Asus laptop (Asus PRO36S / U36SD) and my webcam is Asus Integrated Webcam from Chicony Electronics Co. This is the output of "lsusb | grep Webcam" : Bus 002 Device 004: ID 04f2:b1b9 Chicony Electronics Co., Ltd Asus Integrated Webcam. - I'm using Ubuntu Noble / 24.04. - The version of v4l-utils package is 1.26.1-4build3. - I expect the library from v4l-utils will flip my upside down webcam using LD_PRELOAD. - What I get is the library from v4l-utils won't flip my upside down webcam. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: v4l-utils 1.26.1-4build3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 26 18:16:57 2024 SourcePackage: v4l-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: v4l-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/2063828 Title: v4l-utils failed to flip upside down webcam. Status in v4l-utils package in Ubuntu: New Bug description: About a year ago (June 2023) I can flip my upside down webcam using LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4lconvert.so.0 . But now, It's no longer works. When I launch webcam app (e.g cheese or snapshot), it's always upside down, whether I use LD_PRELOAD or not. My machine is an Asus laptop (Asus PRO36S / U36SD) and my webcam is Asus Integrated Webcam from Chicony Electronics Co. This is the output of "lsusb | grep Webcam" : Bus 002 Device 004: ID 04f2:b1b9 Chicony Electronics Co., Ltd Asus Integrated Webcam. - I'm using Ubuntu Noble / 24.04. - The version of v4l-utils package is 1.26.1-4build3. - I expect the library from v4l-utils will flip my upside down webcam using LD_PRELOAD. - What I get is the library from v4l-utils won't flip my upside down webcam. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: v4l-utils 1.26.1-4build3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 26 18:16:57 2024 SourcePackage: v4l-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/2063828/+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 2049061] Re: adsysctl update with a domain user fails if KRB5CCNAME is not set
Hi Timo, We plan to do a release of ADSys from 24.04 to 22.04 which contains much more than this bug and we'll cover the testing of the entirety of the package. Master SRU bug https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756 We'll send the exception request in the coming days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2049061 Title: adsysctl update with a domain user fails if KRB5CCNAME is not set Status in adsys package in Ubuntu: Fix Released Bug description: In an environment where /etc/krb5.conf sets "default_ccache_name = FILE:/tmp/krb5cc_%{uid}" and you don't have the KRB5CCNAME variable set, running "adsysctl update" with a AD domain user will fail. If you either export the variable with the path to the kerberos ticket OR run the command "adsysctl update " it works. The adsysctl command should fallback to the default location when KRB5CCNAME is not defined or have a mechanism to query klist and find the Kerberos tickets location. Given that adsys can't find Kerberos tickets when `klist` does. It seems like a feature parity issue, granted, an edge case. Here is an example of a reproducer: https://pastebin.ubuntu.com/p/FjyTWQChjM/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: adsys 0.9.2~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1014-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) CurrentDesktop: ubuntu:GNOME Date: Thu Jan 11 11:39:06 2024 Ec2AMI: ami-00094f7041bb1b79d Ec2AMIManifest: (unknown) Ec2Architecture: x86_64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-00094f7041bb1b79d Ec2InstanceType: t3.large Ec2Instancetype: t3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: sssd 2.6.3-1ubuntu3.2 python3-samba 2:4.15.13+dfsg-0ubuntu1.5 SourcePackage: adsys UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.polkit-1.localauthority.conf.d.99-adsys-privilege-enforcement.conf: [deleted] modified.conffile..etc.sudoers.d.99-adsys-privilege-enforcement: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2049061/+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 2063827] Re: Gnome Control Center fails to open on Wayland
Interesting, after getting the backtrace on Wayland I tried to attach the file, however this bug also seems to affect Nautilus as well, the browser will try to open Nautilus and fail. I had to switch back to Xorg to attach the report. Trying to open Nautilus from the terminal gives exactly the same error as trying to open Gnome Control Center. I assume that the backtrace for Gnome Control Center is enough, but if it's necessary I will also provide the backtrace for Nautilus if requested. Thank you for your time. ** Attachment added: "gdb-gnome-control-center.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063827/+attachment/5770915/+files/gdb-gnome-control-center.txt -- 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/2063827 Title: Gnome Control Center fails to open on Wayland Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Hello, I just installed Ubuntu 24.04 LTS and I realized that Gnome Control Center does not open on Wayland, but does on Xorg, attempting to open it will simply open the crash dialog after some time. When running from the terminal: $ gnome-control-center libEGL warning: egl: failed to create dri2 screen Segmentation fault (core dumped) Version installed: gnome-control-center: Installed: 1:46.0.1-1ubuntu7 Candidate: 1:46.0.1-1ubuntu7 My current installation is very lightweight, and I haven't removed any packages or changed any system files. This occurs on a Nvidia GPU, specifically the NVIDA GeForce 1060 3GB with the driver version being 535.171.04 If more information is needed, please let me know, however I might be slow to respond. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063827/+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 2062177] Re: Remmina crashes after RDP connection
** Changed in: remmina (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: remmina (Ubuntu) Status: In Progress => Fix Committed ** Description changed: - When connecting with RDP Remmina crashes. Syslog show the following: + * Impact + + When connecting with RDP Remmina crashes. It's due to an invalid API use + in remmina and stricter checking in the most recent freerdp3 version + which makes it error out now. + + * Test case + + Try to connect to a RDP server using remmina, it shouldn't crash + + * Regression potential + + The change is fixing an incorrect API use in the RDP plugin around color + check, if there is an issue it will be in the RDP support, probably + around colors handling + + -- + + Syslog show the following: 2024-04-18T13:49:02.969819+02:00 localhost dbus-daemon[3214]: [session uid=1001 pid=3214] Successfully activated service 'org.gnome.seahorse.Application' 2024-04-18T13:49:03.655883+02:00 localhost systemd[3176]: Started app-gnome-org.remmina.Remmina-53436.scope - Application launched by gnome-shell. 2024-04-18T13:49:03.656884+02:00 localhost remmina[53441]: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable.#012More info available on the Remmina wiki at:#012https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging 2024-04-18T13:49:03.766401+02:00 localhost remmina[53441]: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem 2024-04-18T13:49:13.851397+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] 2024-04-18T13:49:13.851716+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:637] 2024-04-18T13:49:13.851760+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_backtrace [0x70e694e97660] 2024-04-18T13:49:13.851791+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_log_backtrace_ex [0x70e694e9f150] 2024-04-18T13:49:13.851803+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851815+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=freerdp_settings_get_bool [0x70e6942658a0] 2024-04-18T13:49:13.851827+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851839+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851851+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851873+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851885+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) 2024-04-18T13:49:14.938231+02:00 localhost org.remmina.Remmina.desktop[53436]: /usr/bin/remmina-file-wrapper: line 37: 53441 Aborted (core dumped) "$REMMINA" "${@}" ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64
[Desktop-packages] [Bug 2063827] Re: Gnome Control Center fails to open on Wayland
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/2063827 Title: Gnome Control Center fails to open on Wayland Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Hello, I just installed Ubuntu 24.04 LTS and I realized that Gnome Control Center does not open on Wayland, but does on Xorg, attempting to open it will simply open the crash dialog after some time. When running from the terminal: $ gnome-control-center libEGL warning: egl: failed to create dri2 screen Segmentation fault (core dumped) Version installed: gnome-control-center: Installed: 1:46.0.1-1ubuntu7 Candidate: 1:46.0.1-1ubuntu7 My current installation is very lightweight, and I haven't removed any packages or changed any system files. This occurs on a Nvidia GPU, specifically the NVIDA GeForce 1060 3GB with the driver version being 535.171.04 If more information is needed, please let me know, however I might be slow to respond. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063827/+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 2063815] Re: No microphone available
*** This bug is a duplicate of bug 2061254 *** https://bugs.launchpad.net/bugs/2061254 Please refer to #2061254 ** This bug has been marked a duplicate of bug 2061254 No mic detected - Ubuntu 24.04 Beta -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2063815 Title: No microphone available Status in alsa-driver package in Ubuntu: New Bug description: The system Ubuntu 24.04 does not detect any microphone. The system is Lenovo ThinkPad T14 Gen4. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:frybort2330 F pipewire /dev/snd/controlC0: frybort2334 F wireplumber /dev/snd/controlC1: frybort2334 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 11:37:02 2024 InstallationDate: Installed on 2024-04-19 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) MachineType: LENOVO 21K3003RCK PackageArchitecture: all ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2024 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET55W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3003RCK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR2FET55W(1.35):bd02/20/2024:br1.35:efr1.28:svnLENOVO:pn21K3003RCK:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3003RCK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3003RCK dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2063815/+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 2037004] Re: warnings in terminal with software-properties-gtk
confirmed ubuntu 24.02 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2037004 Title: warnings in terminal with software-properties-gtk Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: When running software-properties-gtk and switching to the "Additional Drivers" tab I saw the following warnings in my terminal: $ software-properties-gtk udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. ... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-gtk 0.99.39 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 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 11:49:24 2023 InstallationDate: Installed on 2018-08-10 (1868 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: software-properties UpgradeStatus: Upgraded to mantic on 2023-09-06 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2037004/+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 2029480] Re: SyntaxWarnings with Python3.12
I'm sorry but the related fix seem to be not complete: during upgrade from 23.10.1 mantic to 24.04 noble it updates hplip-data 3.23.12+dfsg0-0ubuntu5 from previous 3.22.10+dfsg0-2ubuntu1 and it doesn't generate SyntaxWarnings... but a few moments later, then during python3 (3.12.3-0ubuntu1) configuration: Configurando python3 (3.12.3-0ubuntu1) ... running python rtupdate hooks for python3.12... ... /usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence '\#' re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize), /usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence '\/' re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize), /usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence '\*' re.compile('^II\*\x00'): ('image/tiff', tiffsize), /usr/share/hplip/fax/ledmfax.py:46: SyntaxWarning: invalid escape sequence '\d' http_result_pat = re.compile(b"""HTTP/\d.\d\s(\d+)""", re.I) ... running python post-rtupdate hooks for python3.12... You can also reinstall hplip-data using apt and ending in the same problem: # apt install --reinstall hplip-data Leyendo lista de paquetes... Hecho Creando árbol de dependencias... Hecho Leyendo la información de estado... Hecho 0 actualizados, 0 nuevos se instalarán, 1 reinstalados, 0 para eliminar y 0 no actualizados. Se necesita descargar 6.467 kB de archivos. Se utilizarán 0 B de espacio de disco adicional después de esta operación. Des:1 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 hplip-data all 3.23.12+dfsg0-0ubuntu5 [6.467 kB] Descargados 6.467 kB en 1s (8.035 kB/s) (Leyendo la base de datos ... 221724 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../hplip-data_3.23.12+dfsg0-0ubuntu5_all.deb ... Desempaquetando hplip-data (3.23.12+dfsg0-0ubuntu5) sobre (3.23.12+dfsg0-0ubuntu5) ... Configurando hplip-data (3.23.12+dfsg0-0ubuntu5) ... /usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence '\#' re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize), /usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence '\/' re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize), /usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence '\*' re.compile('^II\*\x00'): ('image/tiff', tiffsize), /usr/share/hplip/fax/ledmfax.py:46: SyntaxWarning: invalid escape sequence '\d' http_result_pat = re.compile(b"""HTTP/\d.\d\s(\d+)""", re.I) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2029480 Title: SyntaxWarnings with Python3.12 Status in HPLIP: Confirmed Status in hplip package in Ubuntu: Fix Released Bug description: Fedora 39 uses Python 3.12 by default, which generates many SyntaxWarnings when running hplip scripts. Most warnings are due regular expressions in strings, so making them raw fixes the issue. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/2029480/+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 2061211] Re: Invalid escape sequences in regexes when installing gedit
It can also be reproduced reinstalling gedit (in this example in aarch64 architecture): # apt install --reinstall gedit Leyendo lista de paquetes... Hecho Creando árbol de dependencias... Hecho Leyendo la información de estado... Hecho 0 actualizados, 0 nuevos se instalarán, 1 reinstalados, 0 para eliminar y 0 no actualizados. Se necesita descargar 353 kB de archivos. Se utilizarán 0 B de espacio de disco adicional después de esta operación. Des:1 http://ports.ubuntu.com/ubuntu-ports noble/universe arm64 gedit arm64 46.2-2 [353 kB] Descargados 353 kB en 0s (1.178 kB/s) (Leyendo la base de datos ... 221724 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../gedit_46.2-2_arm64.deb ... Desempaquetando gedit (46.2-2) sobre (46.2-2) ... Configurando gedit (46.2-2) ... /usr/lib/aarch64-linux-gnu/gedit/plugins/externaltools/library.py:212: SyntaxWarning: invalid escape sequence '\-' RE_KEY = re.compile('^([a-zA-Z_][a-zA-Z0-9_.\-]*)(\[([a-zA-Z_@]+)\])?$') /usr/lib/aarch64-linux-gnu/gedit/plugins/snippets/substitutionparser.py:162: SyntaxWarning: invalid escape sequence '\s' match = re.match('?%s\s*' % self.REG_GROUP, tokens) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/2061211 Title: Invalid escape sequences in regexes when installing gedit Status in gedit package in Ubuntu: Confirmed Bug description: On a clean install of the 24.04 beta, if you do a "sudo apt install gedit", you get the following messages at the end of the install: /usr/lib/x86_64-linux-gnu/gedit/plugins/externaltools/library.py:212: SyntaxWarning: invalid escape sequence '\-' RE_KEY = re.compile('^([a-zA-Z_][a-zA-Z0-9_.\-]*)(\[([a-zA-Z_@]+)\])?$') /usr/lib/x86_64-linux-gnu/gedit/plugins/snippets/substitutionparser.py:162: SyntaxWarning: invalid escape sequence '\s' match = re.match('?%s\s*' % self.REG_GROUP, tokens) So there are 2 issues with regexes. Bug #2055010 reports the first of these, but not the second, and it also reports a different issue as "the huger problem" (one that I can't reproduce). I hope I'm making the right call in opening a new bug report specifically for these regex issues. Some more details: - on the clean install, I did apply all available updates before trying to install gedit - you can also reproduce this issue from the live ("try ubuntu") environment ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gedit 46.2-1build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.496 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 08:41:26 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2061211/+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 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
Also tried virtualbox this morning on a different win 11 machine with an nvidia laptop gpu and same thing. No 3D acceleration is not stable on vmware (crashes after a while) With 3D acceleration black screens really fast on vmware and virtualbox (which uses the vmware driver by default) -- 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/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2063827] Re: Gnome Control Center fails to open on Wayland
Thanks, the backtrace indicates a bug in the nvidia driver #5 0x7fffcc201e0d in ProducerCleanup () from /lib/x86_64-linux-gnu/libnvidia-vulkan-producer.so No symbol table info available. #6 0x7fffcc2020db in ProducerInit () from /lib/x86_64-linux-gnu/libnvidia-vulkan-producer.so No symbol table info available. #7 0x7fffb5e1a0e2 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.535.171.04 No symbol table info available. #8 0x7fffb5e4442f in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.535.171.04 No symbol table info available. #9 0x7fffb5e6844d in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.535.171.04 No symbol table info available. #10 0x7fffec4a9b50 in ?? () from /lib/x86_64-linux-gnu/libGLX_nvidia.so.0 ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New ** Package changed: gnome-control-center (Ubuntu) => nvidia-graphics- drivers-535 (Ubuntu) -- 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/2063827 Title: Gnome Control Center fails to open on Wayland Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: Hello, I just installed Ubuntu 24.04 LTS and I realized that Gnome Control Center does not open on Wayland, but does on Xorg, attempting to open it will simply open the crash dialog after some time. When running from the terminal: $ gnome-control-center libEGL warning: egl: failed to create dri2 screen Segmentation fault (core dumped) Version installed: gnome-control-center: Installed: 1:46.0.1-1ubuntu7 Candidate: 1:46.0.1-1ubuntu7 My current installation is very lightweight, and I haven't removed any packages or changed any system files. This occurs on a Nvidia GPU, specifically the NVIDA GeForce 1060 3GB with the driver version being 535.171.04 If more information is needed, please let me know, however I might be slow to respond. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2063827/+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 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure
Seems like a racecondition of some sort. I tried a few days ago with no issue. This seems to be a long running bug, not something new since its been reported in other places. https://ubuntuforums.org/archive/index.php/t-2391820.html https://forums.freebsd.org/threads/linuxulator-switching-to-non-root-user-in-the-chroot-to-run-davinci-resolve.92234/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aspell in Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure Status in aspell package in Ubuntu: New Status in dictionaries-common package in Ubuntu: New Bug description: this is running with LC_ALL=C the following are output in terminal when configuring dictionaries- common Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine &main::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dictionaries-common this worked without issues when I last built images of ubuntu-noble in late February 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+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 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
Upstream MR in gnome-shell to partially fix this https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3283 ** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues #515 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/515 ** Also affects: gnome-shell-extension-appindicator via https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/515 Importance: Unknown Status: Unknown ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen Status in Ubuntu AppIndicators: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: In ubuntu jammy and previous releases, right clicking on appindicator icons brings up the menu below the appindicator with appropriate gnome theming. In ubuntu noble, right clicking on some appindicator icons (example: barrier) results in the menu appearing on the left side of the screen without proper theming. See attached image. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
Upstream QT bugtracker url (can't add to launchpad because it doesn't recognize the format) https://bugreports.qt.io/browse/QTBUG-94871 ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed -- 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/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen Status in Ubuntu AppIndicators: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: In ubuntu jammy and previous releases, right clicking on appindicator icons brings up the menu below the appindicator with appropriate gnome theming. In ubuntu noble, right clicking on some appindicator icons (example: barrier) results in the menu appearing on the left side of the screen without proper theming. See attached image. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)
Ubuntu 24.04 still has a bug. -- 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/1986451 Title: Can't click context menu items when they cover the dock (in a Xorg session) Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: ubuntu dock in bottom position won't let me click on button (convert java file to Kotlin file) in android studio, but in the left position everything works correctly. That is, if the menu android studio overlaps the ubuntu dock, then the menu buttons will not be pressed. https://youtu.be/KsOVG7Uucow ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sun Aug 14 10:52:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2022-07-13 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 106.121 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0603 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.3 dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1986451/+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 2056331] Re: [SRU] fix suspend/resume when there are no input devices
On Mantic, I installed the package from mantic-proposed and applied the same steps as I did in jammy (mentioned in comment #19). ``` ubuntu@kria:~$ apt policy xserver-xorg-core xserver-xorg-core: Installed: 2:21.1.7-3ubuntu2.10 Candidate: 2:21.1.7-3ubuntu2.10 Version table: *** 2:21.1.7-3ubuntu2.10 100 100 http://ports.ubuntu.com/ubuntu-ports mantic-proposed/main arm64 Packages 100 /var/lib/dpkg/status ``` After removing all connected usb devices from the board did a suspend/resume test and everything is working fine in mantic version of the package as well. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2056331 Title: [SRU] fix suspend/resume when there are no input devices Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Mantic: Fix Committed Status in xorg-server source package in Noble: Fix Released Bug description: [Impact] Bug is impacting the suspend/resume flow when there is no input device connected to machine. xorg hangs in this case. [Where problems could occur] The problem could occur in places where there is no input device connected to the system but a suspend/resume is triggered. [Test Case] * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed) * Update xorg-server to the version in -proposed: sudo apt install -t jammy-proposed xorg-server * Unplug all USB devices such as USB drive, keyboard, mouse, etc. * Set RTC timer and suspend the system via UART console $ echo 8 > /proc/sys/kernel/printk $ sudo rtcwake -v -m no -s 240 $ sudo systemctl suspend [Regression Potential] The patch defines a default behavior in systemd_logind_drop_master function so there is a possibility that there might be a regression that may affect all the systems that utilizes systemd_logind_drop_master Upstream Bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2056331/+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 2060400] Re: Remmina crashes instantly when trying to open a remote session
bluppfisk (bluppfisk) i was be able to import all my conections of remmina in the snap version. I copy the conection files to the snap configuration folder: ~/snap/remmina/current/.local/share/remmina/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2060400 Title: Remmina crashes instantly when trying to open a remote session Status in remmina package in Ubuntu: Confirmed Bug description: I've been testing Noble for a couple of weeks and Remmina has not been working. Fully upto date with regards to updates now and it's still crashing. The initial windows comes up allowing you to select a session. The various preference dialogues seem to work but as soon as you try to initiate a remote session it crashes instantly. No crash is shown on the command line. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 20:17:02 2024 InstallationDate: Installed on 2024-03-25 (13 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2060400/+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 2036315] Re: sol takes a long time to start
** Changed in: aisleriot (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/2036315 Title: sol takes a long time to start Status in aisleriot package in Ubuntu: Fix Released Bug description: sol takes a long time to start I see a msg: corrado@corrado-n12-mm-0915:~$ sol ;;; note: source file /usr/share/guile/3.0/ice-9/eval.scm ;;; newer than compiled /usr/lib/x86_64-linux-gnu/guile/3.0/ccache/ice-9/eval.go ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: aisleriot 1:3.22.23-1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 17:01:29 2023 InstallationDate: Installed on 2023-09-15 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230915) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: aisleriot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/2036315/+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 2062177] Re: Remmina crashes after RDP connection
I was able to make remnina works using the snap version. If anyone wants to import all of its conections can do it moving the files here: ~/snap/remmina/current/.local/share/remmina/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2062177 Title: Remmina crashes after RDP connection Status in remmina package in Ubuntu: Fix Committed Bug description: * Impact When connecting with RDP Remmina crashes. It's due to an invalid API use in remmina and stricter checking in the most recent freerdp3 version which makes it error out now. * Test case Try to connect to a RDP server using remmina, it shouldn't crash * Regression potential The change is fixing an incorrect API use in the RDP plugin around color check, if there is an issue it will be in the RDP support, probably around colors handling -- Syslog show the following: 2024-04-18T13:49:02.969819+02:00 localhost dbus-daemon[3214]: [session uid=1001 pid=3214] Successfully activated service 'org.gnome.seahorse.Application' 2024-04-18T13:49:03.655883+02:00 localhost systemd[3176]: Started app-gnome-org.remmina.Remmina-53436.scope - Application launched by gnome-shell. 2024-04-18T13:49:03.656884+02:00 localhost remmina[53441]: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable.#012More info available on the Remmina wiki at:#012https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging 2024-04-18T13:49:03.766401+02:00 localhost remmina[53441]: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem 2024-04-18T13:49:13.851397+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] 2024-04-18T13:49:13.851716+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:637] 2024-04-18T13:49:13.851760+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_backtrace [0x70e694e97660] 2024-04-18T13:49:13.851791+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_log_backtrace_ex [0x70e694e9f150] 2024-04-18T13:49:13.851803+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851815+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=freerdp_settings_get_bool [0x70e6942658a0] 2024-04-18T13:49:13.851827+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851839+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851851+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851873+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851885+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) 2024-04-18T13:49:14.938231+02:00 localhost org.remmina.Remmina.desktop[53436]: /usr/bin/remmina-file-wrapper: line 37: 53441 Aborted (core dumped) "$REMMINA" "${
[Desktop-packages] [Bug 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
** Changed in: gnome-shell-extension-appindicator Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen Status in Ubuntu AppIndicators: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: In ubuntu jammy and previous releases, right clicking on appindicator icons brings up the menu below the appindicator with appropriate gnome theming. In ubuntu noble, right clicking on some appindicator icons (example: barrier) results in the menu appearing on the left side of the screen without proper theming. See attached image. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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 2062177] Re: Remmina crashes after RDP connection
In addition, a version of Remmina with the fix applied can be installed using the project's remmina-next PPA, found here: https://launchpad.net/~remmina-ppa-team/+archive/ubuntu/remmina-next A flatpak version exists as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2062177 Title: Remmina crashes after RDP connection Status in remmina package in Ubuntu: Fix Committed Bug description: * Impact When connecting with RDP Remmina crashes. It's due to an invalid API use in remmina and stricter checking in the most recent freerdp3 version which makes it error out now. * Test case Try to connect to a RDP server using remmina, it shouldn't crash * Regression potential The change is fixing an incorrect API use in the RDP plugin around color check, if there is an issue it will be in the RDP support, probably around colors handling -- Syslog show the following: 2024-04-18T13:49:02.969819+02:00 localhost dbus-daemon[3214]: [session uid=1001 pid=3214] Successfully activated service 'org.gnome.seahorse.Application' 2024-04-18T13:49:03.655883+02:00 localhost systemd[3176]: Started app-gnome-org.remmina.Remmina-53436.scope - Application launched by gnome-shell. 2024-04-18T13:49:03.656884+02:00 localhost remmina[53441]: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable.#012More info available on the Remmina wiki at:#012https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging 2024-04-18T13:49:03.766401+02:00 localhost remmina[53441]: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem 2024-04-18T13:49:13.851397+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] 2024-04-18T13:49:13.851716+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:637] 2024-04-18T13:49:13.851760+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_backtrace [0x70e694e97660] 2024-04-18T13:49:13.851791+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_log_backtrace_ex [0x70e694e9f150] 2024-04-18T13:49:13.851803+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851815+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=freerdp_settings_get_bool [0x70e6942658a0] 2024-04-18T13:49:13.851827+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851839+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851851+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851873+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851885+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) 2024-04-18T13:49:14.938231+02:00 localhost org.remmina.Remmina.desktop[53436]: /usr/bin/remmina-file-wrapper: line 37: 53441 Aborted
[Desktop-packages] [Bug 2063851] [NEW] libgstamrnb.so missing from gstreamer-plugins-good
Public bug reported: This file used to come from the -ugly gstreamer plugins package: /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so This plugin has been moved to the -good set in version 1.22 (upstream gstreamer commit 83026f62890b97904f3da0138456680eac3e0cef). Unfortunately the plugin appears to be missing from the Ubuntu "noble" package... presumably missing a buildtime option to have it built. ** Affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063851 Title: libgstamrnb.so missing from gstreamer-plugins-good Status in gst-plugins-good1.0 package in Ubuntu: New Bug description: This file used to come from the -ugly gstreamer plugins package: /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so This plugin has been moved to the -good set in version 1.22 (upstream gstreamer commit 83026f62890b97904f3da0138456680eac3e0cef). Unfortunately the plugin appears to be missing from the Ubuntu "noble" package... presumably missing a buildtime option to have it built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/2063851/+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 2062177] Re: Remmina crashes after RDP connection
I just rebuilt and installed fresh packages on Noble using the supplied patch above and all good now! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2062177 Title: Remmina crashes after RDP connection Status in remmina package in Ubuntu: Fix Committed Bug description: * Impact When connecting with RDP Remmina crashes. It's due to an invalid API use in remmina and stricter checking in the most recent freerdp3 version which makes it error out now. * Test case Try to connect to a RDP server using remmina, it shouldn't crash * Regression potential The change is fixing an incorrect API use in the RDP plugin around color check, if there is an issue it will be in the RDP support, probably around colors handling -- Syslog show the following: 2024-04-18T13:49:02.969819+02:00 localhost dbus-daemon[3214]: [session uid=1001 pid=3214] Successfully activated service 'org.gnome.seahorse.Application' 2024-04-18T13:49:03.655883+02:00 localhost systemd[3176]: Started app-gnome-org.remmina.Remmina-53436.scope - Application launched by gnome-shell. 2024-04-18T13:49:03.656884+02:00 localhost remmina[53441]: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable.#012More info available on the Remmina wiki at:#012https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging 2024-04-18T13:49:03.766401+02:00 localhost remmina[53441]: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem 2024-04-18T13:49:13.851397+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] 2024-04-18T13:49:13.851716+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:637] 2024-04-18T13:49:13.851760+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_backtrace [0x70e694e97660] 2024-04-18T13:49:13.851791+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_log_backtrace_ex [0x70e694e9f150] 2024-04-18T13:49:13.851803+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851815+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=freerdp_settings_get_bool [0x70e6942658a0] 2024-04-18T13:49:13.851827+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851839+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851851+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851873+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851885+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) 2024-04-18T13:49:14.938231+02:00 localhost org.remmina.Remmina.desktop[53436]: /usr/bin/remmina-file-wrapper: line 37: 53441 Aborted (core dumped) "$REMMINA" "${@}" ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+d
[Desktop-packages] [Bug 2063831] [NEW] Clicking on bottom half of applications switches to background application
You have been subscribed to a public bug: Basicly having more that 1 GUI application running in full screen and clicking bottom half of the currently opened GUI application will make the other application come to the foreground Eg: Google Chrome & Eclipse IDE are both in fullscreen, - Clicking On Eclipse IDE bottom half of the app window will get chrome to display infront of Eclipse, Eg2: Terminal and DBeaver are both in fullscreen, - Clicking On DBeaver bottom half of the app window will get Termial to display infront of Eclipse, ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:07:41 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-P GT2 [Iris Xe Graphics] [1462:1331] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Ti Mobile] [1462:135d] InstallationDate: Installed on 2024-04-25 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Micro-Star International Co., Ltd. Katana GF66 12UD ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=7c59c657-2812-4b59-8441-927f4302e8fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1584IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-1584 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.:bvrE1584IMS.10C:bd05/05/2022:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF6612UD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1584:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku1584.1: dmi.product.family: GF dmi.product.name: Katana GF66 12UD dmi.product.sku: 1584.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 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 noble ubuntu -- Clicking on bottom half of applications switches to background application https://bugs.launchpad.net/bugs/2063831 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063831] Re: Clicking on bottom half of applications switches to background application
** Package changed: ubuntu => xorg (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/2063831 Title: Clicking on bottom half of applications switches to background application Status in xorg package in Ubuntu: New Bug description: Basicly having more that 1 GUI application running in full screen and clicking bottom half of the currently opened GUI application will make the other application come to the foreground Eg: Google Chrome & Eclipse IDE are both in fullscreen, - Clicking On Eclipse IDE bottom half of the app window will get chrome to display infront of Eclipse, Eg2: Terminal and DBeaver are both in fullscreen, - Clicking On DBeaver bottom half of the app window will get Termial to display infront of Eclipse, ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:07:41 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-P GT2 [Iris Xe Graphics] [1462:1331] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Ti Mobile] [1462:135d] InstallationDate: Installed on 2024-04-25 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Micro-Star International Co., Ltd. Katana GF66 12UD ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=7c59c657-2812-4b59-8441-927f4302e8fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1584IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-1584 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.:bvrE1584IMS.10C:bd05/05/2022:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF6612UD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1584:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku1584.1: dmi.product.family: GF dmi.product.name: Katana GF66 12UD dmi.product.sku: 1584.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063831/+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 2063855] [NEW] desktop-file-utils lists snap-store as a default handler for Debian packages but it doesn't handle them
Public bug reported: Currently, desktop-file-utils lists the snap store as the default handler for Debian packages: $ grep debian /usr/share/applications/defaults.list application/vnd.debian.binary-package=snap-store_ubuntu-software-local-file.desktop application/x-debian-package=snap-store_ubuntu-software-local-file.desktop $ However, as discussed at https://github.com/ubuntu/app- center/issues/1407 it does not, in fact, have support for handling these packages. We should correct this so that handling of the packages falls through to something that actually does. ** Affects: desktop-file-utils (Ubuntu) Importance: High Status: Triaged ** Affects: desktop-file-utils (Ubuntu Noble) Importance: High Status: Triaged ** Changed in: desktop-file-utils (Ubuntu) Status: New => Triaged ** Changed in: desktop-file-utils (Ubuntu) Importance: Undecided => High ** Also affects: desktop-file-utils (Ubuntu Noble) Importance: High Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2063855 Title: desktop-file-utils lists snap-store as a default handler for Debian packages but it doesn't handle them Status in desktop-file-utils package in Ubuntu: Triaged Status in desktop-file-utils source package in Noble: Triaged Bug description: Currently, desktop-file-utils lists the snap store as the default handler for Debian packages: $ grep debian /usr/share/applications/defaults.list application/vnd.debian.binary-package=snap-store_ubuntu-software-local-file.desktop application/x-debian-package=snap-store_ubuntu-software-local-file.desktop $ However, as discussed at https://github.com/ubuntu/app- center/issues/1407 it does not, in fact, have support for handling these packages. We should correct this so that handling of the packages falls through to something that actually does. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2063855/+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 2063855] Re: desktop-file-utils lists snap-store as a default handler for Debian packages but it doesn't handle them
Thanks. We should remove those entries but they shouldn't create any visible issue because the referenced .desktop isn't provided by the current snap-store which make those entries just ignored. Marking as Wontfix for Noble, that's not worth a SRU upload ** Changed in: desktop-file-utils (Ubuntu Noble) Status: Triaged => Won't Fix ** Changed in: desktop-file-utils (Ubuntu) Importance: High => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2063855 Title: desktop-file-utils lists snap-store as a default handler for Debian packages but it doesn't handle them Status in desktop-file-utils package in Ubuntu: Triaged Status in desktop-file-utils source package in Noble: Won't Fix Bug description: Currently, desktop-file-utils lists the snap store as the default handler for Debian packages: $ grep debian /usr/share/applications/defaults.list application/vnd.debian.binary-package=snap-store_ubuntu-software-local-file.desktop application/x-debian-package=snap-store_ubuntu-software-local-file.desktop $ However, as discussed at https://github.com/ubuntu/app- center/issues/1407 it does not, in fact, have support for handling these packages. We should correct this so that handling of the packages falls through to something that actually does. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2063855/+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 2063869] [NEW] Missing default cursor
Public bug reported: After upgrading from Ubuntu 23.10 to 24.04, the DMZ-White mouse pointer works correctly when the pointer is over a window, but shows a pale grey square when over the desktop or Ubuntu top bar. This appears to happen because the /usr/share/icons/DMZ-White/cursors/default file (or symlink) is missing. Doing the following appears to fix the problem: 1. cd /usr/share/icons/DMZ-White/cursors 2. ln -s left_ptr default 3. In gnome-tweaks change to some other mouse pointer. 4. In gnome-tweaks change back to DMZ-White. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: dmz-cursor-theme 0.4.5ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 18:39:40 2024 Dependencies: InstallationDate: Installed on 2020-07-14 (1382 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: dmz-cursor-theme UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) ** Affects: dmz-cursor-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dmz-cursor-theme in Ubuntu. https://bugs.launchpad.net/bugs/2063869 Title: Missing default cursor Status in dmz-cursor-theme package in Ubuntu: New Bug description: After upgrading from Ubuntu 23.10 to 24.04, the DMZ-White mouse pointer works correctly when the pointer is over a window, but shows a pale grey square when over the desktop or Ubuntu top bar. This appears to happen because the /usr/share/icons/DMZ-White/cursors/default file (or symlink) is missing. Doing the following appears to fix the problem: 1. cd /usr/share/icons/DMZ-White/cursors 2. ln -s left_ptr default 3. In gnome-tweaks change to some other mouse pointer. 4. In gnome-tweaks change back to DMZ-White. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: dmz-cursor-theme 0.4.5ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 18:39:40 2024 Dependencies: InstallationDate: Installed on 2020-07-14 (1382 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: dmz-cursor-theme UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmz-cursor-theme/+bug/2063869/+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 2061298] Re: Screen corruption in Firefox and Thunderbird when using Wayland
This appears to only happen if Firefox and Thunderbird are set to use the "System theme - auto" theme. Manually selecting either the light or dark theme seems to work around this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2061298 Title: Screen corruption in Firefox and Thunderbird when using Wayland Status in xwayland package in Ubuntu: New Bug description: After upgrading from Ubuntu 23.10 to 24.04, Firefox and Thunderbird both suffer from screen corruption when running with Wayland and virtual desktops. The main windows are fine, but their tab bars show old data from other apps in other virtual desktops. Attached are screenshots of this. The screenshots don't really show the corruption, but they do show the areas that are corrupted as a grey "chessboard" pattern. Apologies if this is filed against the wrong package. If so, please re-assign it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.4-1build3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 10:53:11 2024 InstallationDate: Installed on 2020-07-14 (1370 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2061298/+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 1285444] Re: Login Successful, Desktop Never Loads
Same issue with Secure boot enable and file system encrypted. The only workaround i find was at the login screen toggle to shell Crtl Alt F3, then login and manually launch the gnome (startx) to see what was wrong.The error was xf86enableio failed to enable io ports -03ff operation. Something wrong in the configuration file perhaps linked with the use of a dual screen configuration. So sudo apt install ubuntu- desktop will allow to run gnome ( without tweaks from canonical). The only problem is that in the x.conf there is a leak of definition for the second screen but i think it's a know bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads Status in at-spi2-core package in Ubuntu: Triaged Bug description: Here is what I encounter 1. Boot computer, boot proceeds normally 2. Reach standard Ubuntu login screen, nothing seems to be amiss 3. Enter user name and password 4. Login disappears, just see the pink "Ubuntu 14.04" background The desktop never loads, not even after ~30 minutes. The launcher never appears, and the Desktop background never changes to the user- configured background. Other features: * Cursor works fine, it can be moved around the screen * No error messages pop up * ALT+F1 etc. can be used to switch to different TTYs; all files on the system appear to be intact * Print screen button works (I will upload a screen shot when I get a chance to copy it onto a USB drive) * Hitting power button pops up a window prompting the user to decide whether to shut down * CTRL+ALT+DELETE prompts the user to log out * Desktop does not load on any user accounts, including the guest account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+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 2062177] Re: Remmina crashes after RDP connection
I've uploaded the fix for SRU, it's waiting in the review queue now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2062177 Title: Remmina crashes after RDP connection Status in remmina package in Ubuntu: Fix Committed Bug description: * Impact When connecting with RDP Remmina crashes. It's due to an invalid API use in remmina and stricter checking in the most recent freerdp3 version which makes it error out now. * Test case Try to connect to a RDP server using remmina, it shouldn't crash * Regression potential The change is fixing an incorrect API use in the RDP plugin around color check, if there is an issue it will be in the RDP support, probably around colors handling -- Syslog show the following: 2024-04-18T13:49:02.969819+02:00 localhost dbus-daemon[3214]: [session uid=1001 pid=3214] Successfully activated service 'org.gnome.seahorse.Application' 2024-04-18T13:49:03.655883+02:00 localhost systemd[3176]: Started app-gnome-org.remmina.Remmina-53436.scope - Application launched by gnome-shell. 2024-04-18T13:49:03.656884+02:00 localhost remmina[53441]: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable.#012More info available on the Remmina wiki at:#012https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging 2024-04-18T13:49:03.766401+02:00 localhost remmina[53441]: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem 2024-04-18T13:49:13.851397+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] 2024-04-18T13:49:13.851716+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:637] 2024-04-18T13:49:13.851760+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_backtrace [0x70e694e97660] 2024-04-18T13:49:13.851791+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_log_backtrace_ex [0x70e694e9f150] 2024-04-18T13:49:13.851803+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851815+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=freerdp_settings_get_bool [0x70e6942658a0] 2024-04-18T13:49:13.851827+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851839+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851851+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851873+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851885+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) 2024-04-18T13:49:14.938231+02:00 localhost org.remmina.Remmina.desktop[53436]: /usr/bin/remmina-file-wrapper: line 37: 53441 Aborted (core dumped) "$REMMINA" "${@}" ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu4 ProcVersionSignatur
[Desktop-packages] [Bug 2063851] Re: libgstamrnb.so missing from gstreamer-plugins-good
Thank you for your bug report. They are currently disabled because the required libraries are currently in universe https://salsa.debian.org/gstreamer-team/gst-plugins- good1.0/-/commit/748c622e Could you tell us what's the impact for you? ** Changed in: gst-plugins-good1.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063851 Title: libgstamrnb.so missing from gstreamer-plugins-good Status in gst-plugins-good1.0 package in Ubuntu: Triaged Bug description: This file used to come from the -ugly gstreamer plugins package: /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so This plugin has been moved to the -good set in version 1.22 (upstream gstreamer commit 83026f62890b97904f3da0138456680eac3e0cef). Unfortunately the plugin appears to be missing from the Ubuntu "noble" package... presumably missing a buildtime option to have it built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/2063851/+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 2060400] Re: Remmina crashes instantly when trying to open a remote session
is that trying to connect to a RDP server? in which case that's probably a duplicate of bug #2062177 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2060400 Title: Remmina crashes instantly when trying to open a remote session Status in remmina package in Ubuntu: Confirmed Bug description: I've been testing Noble for a couple of weeks and Remmina has not been working. Fully upto date with regards to updates now and it's still crashing. The initial windows comes up allowing you to select a session. The various preference dialogues seem to work but as soon as you try to initiate a remote session it crashes instantly. No crash is shown on the command line. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 20:17:02 2024 InstallationDate: Installed on 2024-03-25 (13 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2060400/+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 2061993] Re: RDP Remmina on Noble Numbat Ubuntu closes when trying to connect to a remote desktop - the same configuration works fine on other Ubuntu editions.
I experience this same issue on a fresh Noble installation. FWIW, this is only with the Debian repository version - the Snap version of Remmina is able to connect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2061993 Title: RDP Remmina on Noble Numbat Ubuntu closes when trying to connect to a remote desktop - the same configuration works fine on other Ubuntu editions. Status in remmina package in Ubuntu: Confirmed Bug description: blox_land@blox-land-numbat:~$ remmina remmina-Message: 13:25:34.158: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging (org.remmina.Remmina:11727): Gtk-WARNING **: 13:25:35.117: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem [13:25:41:43] [11727:2e1c] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:634] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x766d98ccc000], dli_sname=winpr_backtrace [0x766d98d38540] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x766d98ccc000], dli_sname=winpr_log_backtrace_ex [0x766d98d3ffe0] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x766d93c0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x766d93c0], dli_sname=freerdp_settings_get_bool [0x766d93c648a0] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x766d9a047000], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x766d9a047000], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x766d9da0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x766d9da0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) Aborted (core dumped) blox_land@blox-land-numbat:~$ remmina --version remmina-Message: 13:26:03.550: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging org.remmina.Remmina - 1.4.35 (git n/a) blox_land@blox-land-numbat:~$ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 13:22:37 2024 InstallationDate: Installed on 2024-04-14 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) blox_land@blox-land-numbat:~$ G_MESSAGES_DEBUG=remmina remmina (process:12618): remmina-DEBUG: 14:26:56.726: (remmina_file_manager_init) - Initialized the "/home/blox_land/.local/share/remmina" data folder (process:12618): remmina-DEBUG: 14:26:56.919: (remmina_plugin_manager_register_plugin) - Remmina plugin glibsecret (type=Secret) has been registered, but is not yet initialized/activated. The initialization order is 2000. (process:12618): remmina-DEBUG: 14:26:57.711: (remmina_plugin_entry) - gfx_h264_available: 0 (process:12618): remmina-DEBUG: 14:26:57.727: (remm
[Desktop-packages] [Bug 2063143] Re: Frequent boot to black display
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #32509 https://github.com/systemd/systemd/issues/32509 ** Also affects: systemd via https://github.com/systemd/systemd/issues/32509 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display Status in Linux: New Status in Plymouth: New Status in SDDM: New Status in systemd: Unknown Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Incomplete Status in sddm package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2063143/+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 2063143] Re: Frequent boot to black display
** Changed in: systemd Status: Unknown => New ** Changed in: linux Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display Status in Linux: Fix Released Status in Plymouth: New Status in SDDM: New Status in systemd: New Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Incomplete Status in sddm package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2063143/+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 2063143] Re: Frequent boot to black display
** No longer affects: linux ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display Status in Plymouth: New Status in SDDM: New Status in systemd: New Status in plymouth package in Ubuntu: Incomplete Status in sddm package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2063143/+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 2063882] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
*** This bug is a duplicate of bug 1813171 *** https://bugs.launchpad.net/bugs/1813171 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1813171, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2063882/+attachment/5771046/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2063882/+attachment/5771048/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2063882/+attachment/5771053/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2063882/+attachment/5771054/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2063882/+attachment/5771055/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2063882/+attachment/5771056/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2063882/+attachment/5771057/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1813171 nautilus crashed with SIGSEGV in nautilus_files_view_set_selection when working with large directory tree ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2063882 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in nautilus package in Ubuntu: New Bug description: Crash when changing to sub-directory in top bar. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 21:20:40 2024 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2023-06-06 (325 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x72cfd94bec39 : mov(%rdi),%rax PC (0x72cfd94bec39) ok source "(%rdi)" (0x5b7d0001) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: g_type_check_instance_is_fundamentally_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: Upgraded to mantic on 2023-10-14 (195 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo users mtime.conffile..etc.apport.crashdb.conf: 2024-03-06T17:35:57.237100 separator: usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063882/+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 2062394] Proposed package upload rejected
An upload of xdg-desktop-portal to noble-proposed has been rejected from the upload queue for the following reason: "merge changelog includes references to long-fixed bugs, needs cleanup". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/2062394 Title: Update xdg-desktop-portal to 1.18.4 Status in xdg-desktop-portal package in Ubuntu: In Progress Bug description: This includes part of a CVE security fix; the more important part of the CVE is in flatpak but there is some hardening on the xdg-desktop- portal side. https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.18.4 https://github.com/flatpak/xdg-desktop-portal/compare/1.18.3...1.18.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/2062394/+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 1968215] Proposed package upload rejected
An upload of xdg-desktop-portal to noble-proposed has been rejected from the upload queue for the following reason: "merge changelog includes references to long-fixed bugs, needs cleanup". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1968215 Title: [FFe] include a new webextensions portal to be used by firefox and other confined browsers Status in xdg-desktop-portal package in Ubuntu: Fix Released Bug description: The request is to add the new webextensions portal which is up for review upstream on https://github.com/flatpak/xdg-desktop- portal/pull/705 The patch to add to the package would be https://patch- diff.githubusercontent.com/raw/flatpak/xdg-desktop- portal/pull/705.patch The code has been written by James from the Desktop Team and reviewed by Olivier from Desktop and got a security review from Alex. The regression potential is null since that's a new feature The code is needed for the firefox messaging protocol to keep working which is seen as an important feature that would regress in the deb to snap transition otherwise. The feature has been discussed on https://forum.snapcraft.io/t/native- messaging-support-in-strictly-confined-browser-snaps Olivier is working on getting the firefox side of the changes ready but those aren't part of this FFe since they will be integrated as the firefox snap gets updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1968215/+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 1958019]
> Kindly follow Comment 872 to force tas2781 to work I had been using 6.7.9 for the last week with no issues. I upgrade to 6.8.7, and within 3 minutes audio broken. I save your script and run it -- su root -- ./tas2781-2dev-on.sh Sound works again, however: - sound is notably louder compared to 6.7.9 - right inside / right speaker? (not sure if there's 1 or 2) is louder than on 6.8.7 with your script. After a few minutes, once again audio will break again, until I re-run your script. Interestingly, after second run of script the audio balance is fixed. Both left/right speakers sound correct instead of being right-side balanced. Unfortunately, breaks soon after. For me audio never lasts more than ~3min. I also notice that the audio levels will oscillate occasionally on 6.8.x kernels, where this does not occur on 6.7.9. If there is anything more I can do to help, please advise. I can try any combination of kernel/patches if needed. I just want to resolve this issue without beings stuck on 6.7.9 kernel. Again for my posts, model is: Lenovo Legion Pro 7i (Gen 8, 2023) - and alsamixer shows ALC287 under system info. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
Created attachment 306214 attachment-10825-0.html I am currently out of the office on holiday I will be returning on Tuesday April 30th, I will not be checking email. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2063892] [NEW] How to « star » an item in Nautilus 46 / Ubuntu 24.04 ?
Public bug reported: Hi ! For few months I'm getting used to « starred x items in Nautilus / Ubuntu 22.04. To my surprise I can't find how to do the same in 24.04, looks like the option for « starring » an element is missing in context menu. It's a default install of 24.04 hence « minimal » so maybe I'm missing a package ? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 00:45:55 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1040, 667)' InstallationDate: Installed on 2024-04-25 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "context menu on an item in Nautilus 46 / Ubuntu 24.04" https://bugs.launchpad.net/bugs/2063892/+attachment/5771154/+files/nautilus_favoris_starred.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2063892 Title: How to « star » an item in Nautilus 46 / Ubuntu 24.04 ? Status in nautilus package in Ubuntu: New Bug description: Hi ! For few months I'm getting used to « starred x items in Nautilus / Ubuntu 22.04. To my surprise I can't find how to do the same in 24.04, looks like the option for « starring » an element is missing in context menu. It's a default install of 24.04 hence « minimal » so maybe I'm missing a package ? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 00:45:55 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1040, 667)' InstallationDate: Installed on 2024-04-25 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063892/+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 2019906] Re: 24.04 : condensed, bold and black fonts can't be used for interface and title bar
** Description changed: Hi, fresh lunar lobster installation here, from legacy iso image ( ubiquity installer. ) As I usually do, I tried to change the font for interface, as I much prefer « condensed » fonts rather than large, round, regular ones. In 20.04 or 22.04 or 22.10 gnome-tweaks allowed to do that. - Today in 23.04, it only changes font in gnome-shell ( top panel, - activities and app's views ) but not in other app's, not in the whole - interface as it used to do. + Today in 24.04 ( and since 23.04 ) it only changes font in gnome-shell ( + top panel, activities and app's views ) but not in other app's, not in + the whole interface as it used to do. In dconf-editor I did not find entries regarding « global » interface font. Is this intended behavior ? Ability to change font type and size is also a matter of accessibility. For references : ⋅ https://askubuntu.com/questions/1468338/23-04-how-change-font-in-interface-gnome-shell-window-title-bar ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2079313 This affects many users. -- 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/2019906 Title: 24.04 : condensed, bold and black fonts can't be used for interface and title bar Status in budgie-desktop package in Ubuntu: Confirmed Status in fonts-ubuntu package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Hi, fresh lunar lobster installation here, from legacy iso image ( ubiquity installer. ) As I usually do, I tried to change the font for interface, as I much prefer « condensed » fonts rather than large, round, regular ones. In 20.04 or 22.04 or 22.10 gnome-tweaks allowed to do that. Today in 24.04 ( and since 23.04 ) it only changes font in gnome-shell ( top panel, activities and app's views ) but not in other app's, not in the whole interface as it used to do. In dconf-editor I did not find entries regarding « global » interface font. Is this intended behavior ? Ability to change font type and size is also a matter of accessibility. For references : ⋅ https://askubuntu.com/questions/1468338/23-04-how-change-font-in-interface-gnome-shell-window-title-bar ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2079313 This affects many users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2019906/+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 2020009] Re: F9 no longer hides side pane
*** This bug is a duplicate of bug 2059871 *** https://bugs.launchpad.net/bugs/2059871 ** This bug has been marked a duplicate of bug 2059871 F9 still mentionned as a way to hide side pane but no longer works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2020009 Title: F9 no longer hides side pane Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: Hi, 23.04 Ubuntu freshly installed. In Nautilus F9 key no longer hides side pane as it used to do. This keyboard shortcut is mentioned though in [ Ctrl ] + [ ? ] Expected : ability to hide side pane Use-case : easier on eyes and mouse moves when moving elements between two opened windows of Nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2020009/+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 2059871] Re: F9 still mentionned as a way to hide side pane but no longer works
** Description changed: Hi, ubuntu 24.04 + nautilus 46 in Nautilus « main menu » the keyboard-shortcuts list [ ctrl + ? ] reads F9 as a way to hide / unhide side panel. I wish it were true, but it's no longer since 23.04 where F9 was disabled upstream ( https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2020009 ) Though there was a button~icon at the bottom of window for hiding / unhiding side panel. Now this also seems gone. So now only way to hide side pane is to adjust width of Nautilus window. + But how now to achieve this → https://launchpadlibrarian.net/666797838/nautilus_side_by_side.png ? Hiding side pane is very convenient when needing to drag and drop elements between two ( or more ) open windows of nautilus. It can ease task for visually impaired people and people with unsure or slow hand moves. Could F9 shortcut or dedicated button-icon ( or both ) make a comeback in Ubuntu ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2059871 Title: F9 still mentionned as a way to hide side pane but no longer works Status in nautilus package in Ubuntu: New Bug description: Hi, ubuntu 24.04 + nautilus 46 in Nautilus « main menu » the keyboard-shortcuts list [ ctrl + ? ] reads F9 as a way to hide / unhide side panel. I wish it were true, but it's no longer since 23.04 where F9 was disabled upstream ( https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2020009 ) Though there was a button~icon at the bottom of window for hiding / unhiding side panel. Now this also seems gone. So now only way to hide side pane is to adjust width of Nautilus window. But how now to achieve this → https://launchpadlibrarian.net/666797838/nautilus_side_by_side.png ? Hiding side pane is very convenient when needing to drag and drop elements between two ( or more ) open windows of nautilus. It can ease task for visually impaired people and people with unsure or slow hand moves. Could F9 shortcut or dedicated button-icon ( or both ) make a comeback in Ubuntu ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2059871/+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 2063143] Re: Frequent boot to black display
** Changed in: plymouth Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display Status in Plymouth: Fix Released Status in SDDM: New Status in systemd: New Status in plymouth package in Ubuntu: Incomplete Status in sddm package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2063143/+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 2062967] Re: ubuntu-drivers no longer offers nvidia 550 drivers
Thanks for the feedback, Sebastien. Question, I read that Nvidia has a new driver V555 in the works, which together with Gnome 46.1 will fix explicit sync issues under Wayland, resolving a number of outstanding glitches and bugs when gaming via Steam under wayland. When the time has come, will Ubuntu be offering that new version as well via the driver selection tool or will we stick to V550? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2062967 Title: ubuntu-drivers no longer offers nvidia 550 drivers Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: While I am unclear which package update impacted the video drivers detected by ubuntu-drivers, the nvidia 545 and nvidia 550 video drivers are no longer shown as an option on NVIDIA GeForce GTX 1050 video card. I can understand the removal of the nvidia 545 drivers as the current kernel's linux-signatures-nvidia-6.8.0-28-generic package lacks signatures for the nvidia 545 kernel modules for secure boot but the nvidia 550 kernel modules signatures are available. So while it would be acceptable to downgrade the 'tested' default nvidia driver to 535, ubuntu-drivers and Additional Drivers should be offering the nvidia 550 drivers as an untested option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2062967/+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 2056331] Autopkgtest regression report (xorg-server/2:21.1.4-2ubuntu1.7~22.04.11)
All autopkgtests for the newly accepted xorg-server (2:21.1.4-2ubuntu1.7~22.04.11) for jammy have finished running. The following regressions have been reported in tests triggered by the package: airport-utils/2-8 (armhf) apport/2.20.11-0ubuntu82.5 (armhf) at-spi2-atk/2.38.0-3 (i386) auto-multiple-choice/unknown (armhf) libsoup3/3.0.7-0ubuntu1 (s390x) mutter/42.9-0ubuntu7 (arm64) nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf) pytest-qt/4.0.2-1 (armhf) python-qtpy/2.0.0-3 (amd64, arm64, armhf, ppc64el, s390x) sasview/5.0.4-1 (armhf) sphinx/4.3.2-1 (s390x) update-manager/1:22.04.20 (amd64, arm64, armhf, i386, ppc64el, s390x) xlbiff/4.6.3-1 (arm64) xpra/3.1-1build5 (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/jammy/update_excuses.html#xorg-server [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 xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2056331 Title: [SRU] fix suspend/resume when there are no input devices Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Mantic: Fix Committed Status in xorg-server source package in Noble: Fix Released Bug description: [Impact] Bug is impacting the suspend/resume flow when there is no input device connected to machine. xorg hangs in this case. [Where problems could occur] The problem could occur in places where there is no input device connected to the system but a suspend/resume is triggered. [Test Case] * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed) * Update xorg-server to the version in -proposed: sudo apt install -t jammy-proposed xorg-server * Unplug all USB devices such as USB drive, keyboard, mouse, etc. * Set RTC timer and suspend the system via UART console $ echo 8 > /proc/sys/kernel/printk $ sudo rtcwake -v -m no -s 240 $ sudo systemctl suspend [Regression Potential] The patch defines a default behavior in systemd_logind_drop_master function so there is a possibility that there might be a regression that may affect all the systems that utilizes systemd_logind_drop_master Upstream Bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2056331/+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 235101]
Can confirm this as Verified. Tested on OS WIN(64): Version 61.0a1 Build: 0180501100117 Version 62.0a1 Build: 20180606101752 OS MAC Sonoma 14 Version : 126.0b1 Build: 20240422190155 -- 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/235101 Title: Can't select/copy/paste address block from Address Book in Thunderbird Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Bug description: Binary package hint: mozilla-thunderbird Very often in my day to day work, I need to send someone an address. It seems that Thunderbird won't allow me to select the address from the "Card Summary Pane" in the Address Book. I must go in the card and copy/paste each field manually. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/235101/+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 2063536] Re: flickering screen
** Information type changed from Private Security to Public -- 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/2063536 Title: flickering screen Status in xorg package in Ubuntu: New Bug description: automatically refresh and hang ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 08:44:25 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtbth/3.9.8, 6.5.0-27-generic, x86_64: installed rtbth/3.9.8, 6.5.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-S GT2 [UHD Graphics 630] [1462:7d82] InstallationDate: Installed on 2024-04-16 (9 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 2M/x2 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Micro-Star International Co., Ltd. MS-7D82 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=5d5b2975-ec40-4c41-919c-f0c2ecc1a822 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.22 dmi.board.asset.tag: Default string dmi.board.name: PRO H410M-B(MS-7D82) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.22:bd03/24/2022:br5.19:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D82:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROH410M-B(MS-7D82):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D82 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063536/+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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
Hey James, thanks for maintaining pptpd for so many years. I know I'm cranky when old software I use is removed just because it's no longer in fashion. But we do try to move people to safer protocols and safer programs over time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Fix Released Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. Current Windows versions natively support IPSec and L2TP as much better alternatives. https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- configuration#how-to-use-wfp-to-configure-ipsec-policies https://learn.microsoft.com/en-US/troubleshoot/windows- server/networking/configure-l2tp-ipsec-server-behind-nat-t-device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2041751/+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 2063831] Re: Clicking on bottom half of applications switches to background application
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: focus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2063831 Title: Clicking on bottom half of applications switches to background application Status in mutter package in Ubuntu: New Bug description: Basicly having more that 1 GUI application running in full screen and clicking bottom half of the currently opened GUI application will make the other application come to the foreground Eg: Google Chrome & Eclipse IDE are both in fullscreen, - Clicking On Eclipse IDE bottom half of the app window will get chrome to display infront of Eclipse, Eg2: Terminal and DBeaver are both in fullscreen, - Clicking On DBeaver bottom half of the app window will get Termial to display infront of Eclipse, ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:07:41 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-P GT2 [Iris Xe Graphics] [1462:1331] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Ti Mobile] [1462:135d] InstallationDate: Installed on 2024-04-25 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Micro-Star International Co., Ltd. Katana GF66 12UD ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=7c59c657-2812-4b59-8441-927f4302e8fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1584IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-1584 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.:bvrE1584IMS.10C:bd05/05/2022:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF6612UD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1584:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku1584.1: dmi.product.family: GF dmi.product.name: Katana GF66 12UD dmi.product.sku: 1584.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063831/+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 2063536] Re: flickering screen
I can see 'gjs' crashing constantly so please try: gnome-extensions disable d...@rastersoft.com If that doesn't fix it then please provide a video of the problem. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2063536 Title: flickering screen Status in Ubuntu: Incomplete Bug description: automatically refresh and hang ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 08:44:25 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtbth/3.9.8, 6.5.0-27-generic, x86_64: installed rtbth/3.9.8, 6.5.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-S GT2 [UHD Graphics 630] [1462:7d82] InstallationDate: Installed on 2024-04-16 (9 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 2M/x2 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Micro-Star International Co., Ltd. MS-7D82 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=5d5b2975-ec40-4c41-919c-f0c2ecc1a822 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.22 dmi.board.asset.tag: Default string dmi.board.name: PRO H410M-B(MS-7D82) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.22:bd03/24/2022:br5.19:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D82:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROH410M-B(MS-7D82):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D82 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2063536/+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 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF
** Changed in: openvswitch (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/2040472 Title: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF Status in dpdk package in Ubuntu: New Status in edk2 package in Ubuntu: New Status in libslirp package in Ubuntu: New Status in libvirt package in Ubuntu: New Status in libvirt-python package in Ubuntu: New Status in meson package in Ubuntu: New Status in openvswitch package in Ubuntu: New Status in qemu package in Ubuntu: New Status in rdma-core package in Ubuntu: New Status in seabios package in Ubuntu: New Status in spice package in Ubuntu: New Status in spice-protocol package in Ubuntu: New Status in spice-vdagent package in Ubuntu: New Status in virglrenderer package in Ubuntu: New Status in virt-manager package in Ubuntu: New Status in dpdk source package in Focal: Fix Committed Status in edk2 source package in Focal: Fix Committed Status in libslirp source package in Focal: Fix Committed Status in libvirt source package in Focal: New Status in libvirt-python source package in Focal: Fix Committed Status in meson source package in Focal: New Status in openvswitch source package in Focal: Fix Committed Status in qemu source package in Focal: New Status in rdma-core source package in Focal: New Status in seabios source package in Focal: Fix Committed Status in spice source package in Focal: Fix Committed Status in spice-protocol source package in Focal: Fix Committed Status in spice-vdagent source package in Focal: New Status in virglrenderer source package in Focal: New Status in virt-manager source package in Focal: New Status in dpdk source package in Jammy: Fix Committed Status in edk2 source package in Jammy: Fix Committed Status in libslirp source package in Jammy: Fix Committed Status in libvirt source package in Jammy: Fix Committed Status in libvirt-python source package in Jammy: Fix Committed Status in meson source package in Jammy: Won't Fix Status in openvswitch source package in Jammy: Fix Committed Status in qemu source package in Jammy: Fix Committed Status in rdma-core source package in Jammy: Fix Committed Status in seabios source package in Jammy: Fix Committed Status in spice source package in Jammy: Fix Committed Status in spice-protocol source package in Jammy: Fix Committed Status in spice-vdagent source package in Jammy: Fix Committed Status in virglrenderer source package in Jammy: Fix Committed Status in virt-manager source package in Jammy: Fix Committed Bug description: Backport the following packages to the server-backports PPA for noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt- python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice', 'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+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 2063904] Re: gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_
*** This bug is a duplicate of bug 2063341 *** https://bugs.launchpad.net/bugs/2063341 ** Summary changed: - /usr/bin/gnome-shell:11:wl_closure_invoke:wl_client_connection_data:wl_event_loop_dispatch:wayland_event_source_dispatch:g_main_dispatch + gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() ** This bug has been marked a duplicate of bug 2063341 gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() -- 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/2063904 Title: gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() 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 42.9-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60 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/2063904/+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 2063904] [NEW] gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from
*** This bug is a duplicate of bug 2063341 *** https://bugs.launchpad.net/bugs/2063341 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 42.9-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60 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: jammy -- 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/2063904 Title: gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() 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 42.9-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60 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/2063904/+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 2063341] Re: gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_
Tracking in: https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60 ** Summary changed: - gnome-shell crashed with SIGSEGV + gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() ** Description changed: + https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60 + I've been using Ubuntu for almost 2 years and it's been working fine. I use a KVM switch (built in Benq monitor) all the time. Since last month Ubuntu randomly crashes when I switch back to it. Or it could be wake up/suspend, I can't see when it exactly happens, it's just logging screen after crash. I am running: openVPN, firefox (dozen tabs), chrome (ms teams), slack, postman, 3x Intellij IDEA, VS Code System logs don't show anything meaningful to me or Google and I don't know how to get a clue as to what's going on. I suspect a new version of MS Teams that was introduced a few weeks ago. - Please help me + Please help me I cannot reproduce the crash or find anything on the web about it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:59:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (601 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2063341 Title: gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() Status in gnome-shell package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60 I've been using Ubuntu for almost 2 years and it's been working fine. I use a KVM switch (built in Benq monitor) all the time. Since last month Ubuntu randomly crashes when I switch back to it. Or it could be wake up/suspend, I can't see when it exactly happens, it's just logging screen after crash. I am running: openVPN, firefox (dozen tabs), chrome (ms teams), slack, postman, 3x Intellij IDEA, VS Code System logs don't show anything meaningful to me or Google and I don't know how to get a clue as to what's going on. I suspect a new version of MS Teams that was introduced a few weeks ago. Please help me I cannot reproduce the crash or find anything on the web about it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:59:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (601 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063341/+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 2063501] Re: gnome-shell crashed with assertion failure "meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l>"
** Summary changed: - Sometimes gnome-shell crash upon unlocking session from suspension + gnome-shell crashed with assertion failure "meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l>" ** No longer affects: xwayland (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/2063501 Title: gnome-shell crashed with assertion failure "meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l>" Status in gnome-shell package in Ubuntu: New Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https:/
[Desktop-packages] [Bug 2023647] Re: [amdgpu] Screens go into flicker cycle after going blank with external monitor(s)
Thank you for reporting this bug to Ubuntu. Ubuntu 23.04 (lunar) reached end-of-life on January 25, 2024. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023647 Title: [amdgpu] Screens go into flicker cycle after going blank with external monitor(s) Status in Mutter: New Status in linux package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: This happens whenever screen goes blank after inactivity with external monitors. When there is only one external monitor after few cycles the system recovers from the bug. When there are more than one monitors the system almost never recovers until unplugging extra monitor, as shown in video: https://photos.app.goo.gl/td6coEKFQd3DKe9C7 Happens on desktop and login screen. The same result with Wayland and X11. Does not depend on size of the monitor, cable (HDMI or USB-C) or is it connected via USB-C hub or directly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 13 12:36:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-13 (60 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 44.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (52 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (131 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: mutter ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 Tags: lunar Uname: Linux 6.2.0-27-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (122 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2023647/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
** Summary changed: - GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) + GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2063501] Re: gnome-shell crashed with assertion failure "meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l>"
*** This bug is a duplicate of bug 2050865 *** https://bugs.launchpad.net/bugs/2050865 I am seeing three different gnome-shell crashes here: * Signal 6: Assertion in meta_window_get_work_area_for_logical_monitor * Signal 11: Reason unknown. No crash report. * Shutdown due to Xwayland crashing. Also the only reason for Xwayland crashing I can see is related to nouveau. So please use the 'Additional Drivers' app to install an official Nvidia driver. Though that will force you to use Xorg instead of Wayland. ** Summary changed: - gnome-shell crashed with assertion failure "meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l>" + gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)" -- 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/2063501 Title: gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)" Status in gnome-shell package in Ubuntu: New Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOM
[Desktop-packages] [Bug 2063501] Re: gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_mon
*** This bug is a duplicate of bug 2050865 *** https://bugs.launchpad.net/bugs/2050865 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2050865, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 2050865 GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) -- 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/2063501 Title: gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)" Status in gnome-shell package in Ubuntu: New Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03
[Desktop-packages] [Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
This might actually be https://gitlab.gnome.org/GNOME/mutter/-/issues/3402 which is fixed in mutter 46.1 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3402 https://gitlab.gnome.org/GNOME/mutter/-/issues/3402 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2063501] Re: gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_mon
*** This bug is a duplicate of bug 2050865 *** https://bugs.launchpad.net/bugs/2050865 If you can find any crash files from Xwayland in /var/crash then please open a new bug for that. -- 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/2063501 Title: gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)" Status in gnome-shell package in Ubuntu: New Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+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 2063869] Re: Missing default cursor
Tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/3184 the proposed fix is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3718 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3184 https://gitlab.gnome.org/GNOME/mutter/-/issues/3184 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3184 Importance: Unknown Status: Unknown ** Changed in: dmz-cursor-theme (Ubuntu) Status: New => Won't Fix ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Milestone: None => noble-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2063869 Title: Missing default cursor Status in Mutter: Unknown Status in dmz-cursor-theme package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: After upgrading from Ubuntu 23.10 to 24.04, the DMZ-White mouse pointer works correctly when the pointer is over a window, but shows a pale grey square when over the desktop or Ubuntu top bar. This appears to happen because the /usr/share/icons/DMZ-White/cursors/default file (or symlink) is missing. Doing the following appears to fix the problem: 1. cd /usr/share/icons/DMZ-White/cursors 2. ln -s left_ptr default 3. In gnome-tweaks change to some other mouse pointer. 4. In gnome-tweaks change back to DMZ-White. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: dmz-cursor-theme 0.4.5ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 18:39:40 2024 Dependencies: InstallationDate: Installed on 2020-07-14 (1382 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: dmz-cursor-theme UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063869/+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 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected
** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3454 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2062377 Title: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected Status in Mutter: Unknown Status in mutter package in Ubuntu: In Progress Bug description: 1)Go to xorg 2)Download Gnome Tweak Tool 3)Select DMZ-white 4)crash from the system ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:38:02 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524] Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524] InstallationDate: Installed on 2024-04-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) MachineType: Acer Aspire A715-42G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_CAS dmi.board.vendor: LN dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-42G dmi.product.sku: dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2062377/+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 2037004] Re: warnings in terminal with software-properties-gtk
Booting the just released ISO of Ubuntu 22.04 Desktop, ubuntu-drivers list and the Software & Updates/Additional Drivers tab are missing the Nvidia drivers 545 and 550, but the above warning(error?) is repeated 6 times. The apt pkgnmames will list the 545 and 550 drivers. sudo apt install nvidia-driver-550 will have the lsmod show nvidia in the modules list, but nvidia-settings does not show the expected output for an nvidia driver. Software & updates/Additional will show nouveau running, and all the nvidia drivers greyed out. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2037004 Title: warnings in terminal with software-properties-gtk Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: When running software-properties-gtk and switching to the "Additional Drivers" tab I saw the following warnings in my terminal: $ software-properties-gtk udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. ... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-gtk 0.99.39 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 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 11:49:24 2023 InstallationDate: Installed on 2018-08-10 (1868 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: software-properties UpgradeStatus: Upgraded to mantic on 2023-09-06 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2037004/+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