[Desktop-packages] [Bug 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
If the OBS issue is related to this then it will be in some common component like a library or the shell. We don't need to add a task for each app. This problem is too low level for apps to have any control over it. ** No longer affects: obs-studio (Ubuntu) -- 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/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel
And I knew there is a plan to upgrade MM to 1.18.6[1], and it's proposed channel, but it has been hold more than one month because of some risks. Is it possible that we merge this fix[2] into 1.16.6 first. [1] https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1965901 [2] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1978057 Title: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel Status in modemmanager package in Ubuntu: New Bug description: [Impact] On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly. With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like set 'AT' to wwan0mbim. [Where problems could occur] It's just a udev rules, no harm to the system. [Fix] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 udev: Match WWAN "type" attribute instead of device name Recent changes in the WWAN framework in the kernel changed the WWAN port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and "wwan0qmi0" [1, 2]. This means that the udev rules no longer match since AT/QMI are now lower-case and no longer at the end of the name. However, recently additionally a "type" sysfs attribute was added for all WWAN ports [3], which makes it much more reliable to match the WWAN port names without relying on their exact device name. Add some additional udev rules to apply the port hints based on the "type" sysfs attributes. This fixes the port enumeration on newer Linux kernels that include the aforementioned commits. Note that we still need to keep the old udev rules for now since Linux 5.13 does not have the "type" attribute yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f [2]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde [3]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c (cherry picked from commit 4282c8d8) [Test] With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 'Mobile Broadband' item in the top-right menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+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 1978053] Re: lubuntu kinetic live - firefox can't open libreoffice help file
** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1978053 Title: lubuntu kinetic live - firefox can't open libreoffice help file Status in libreoffice package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Lubuntu kinetic jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) To re-create - boot live media (Lubuntu kinetic) - open libreoffice (any, but I used the base app here) - seek help in menu or press F1 ** Expected Results Firefox opens with some helpful text ** Actual Results Firefox opens at URL : file:///usr/share/libreoffice/help/index.html?Target=swriter/.uno%3AHelpIndex=en- US=UNIX=7.3 with message --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- ** Background Notes This issue was reported before in jammy; but was marked RESOLVED. The directory though is different so something has changed.. I believe I'm thinking of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210 I'm unsure if this is a firefox issue, Lubuntu config issue, or Libreoffice issue, but snap'd apps have issues due to confinement thus firefox issue is I fear suspected. Reported also at https://bugzilla.mozilla.org/show_bug.cgi?id=1773414 though i suspect issue may not actually be with firefox snap. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.472 CurrentDesktop: LXQt Date: Thu Jun 9 04:41:26 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220608) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1978053/+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 1977748] [NEW] No cairo GL support for wayland, 22.04
You have been subscribed to a public bug: Instructed by "ask a question" I tried to file a wayland-targeted bug, but apport-bug thinks I'm running Xorg. See https://answers.launchpad.net/ubuntu/+question/702075 PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy $ ps -ef | grep Xwayland xx 24931685 0 Jun04 ?00:05:36 /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1001/.mutter-Xwaylandauth.5ZZYM1 -listen 4 -listen 5 -displayfd 6 -initfd 7 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 06:40:48 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0991] InstallationDate: Installed on 2021-10-02 (246 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic root=UUID=c737013a-1cc7-494f-a1b7-a6efce6f09f7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2022 dmi.bios.release: 3.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.6.0 dmi.board.name: 0MK6WC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.6.0:bd03/17/2022:br3.6:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MK6WC:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: cairo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- No cairo GL support for wayland, 22.04 https://bugs.launchpad.net/bugs/1977748 You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo 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 1978057] [NEW] [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel
Public bug reported: [Impact] On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly. With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like set 'AT' to wwan0mbim. [Where problems could occur] It's just a udev rules, no harm to the system. [Fix] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 udev: Match WWAN "type" attribute instead of device name Recent changes in the WWAN framework in the kernel changed the WWAN port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and "wwan0qmi0" [1, 2]. This means that the udev rules no longer match since AT/QMI are now lower-case and no longer at the end of the name. However, recently additionally a "type" sysfs attribute was added for all WWAN ports [3], which makes it much more reliable to match the WWAN port names without relying on their exact device name. Add some additional udev rules to apply the port hints based on the "type" sysfs attributes. This fixes the port enumeration on newer Linux kernels that include the aforementioned commits. Note that we still need to keep the old udev rules for now since Linux 5.13 does not have the "type" attribute yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f [2]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde [3]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c (cherry picked from commit 4282c8d8) [Test] With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 'Mobile Broadband' item in the top-right menu. ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1978057 Title: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel Status in modemmanager package in Ubuntu: New Bug description: [Impact] On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly. With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like set 'AT' to wwan0mbim. [Where problems could occur] It's just a udev rules, no harm to the system. [Fix] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 udev: Match WWAN "type" attribute instead of device name Recent changes in the WWAN framework in the kernel changed the WWAN port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and "wwan0qmi0" [1, 2]. This means that the udev rules no longer match since AT/QMI are now lower-case and no longer at the end of the name. However, recently additionally a "type" sysfs attribute was added for all WWAN ports [3], which makes it much more reliable to match the WWAN port names without relying on their exact device name. Add some additional udev rules to apply the port hints based on the "type" sysfs attributes. This fixes the port enumeration on newer Linux kernels that include the aforementioned commits. Note that we still need to keep the old udev rules for now since Linux 5.13 does not have the "type" attribute yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f [2]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde [3]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c (cherry picked from commit 4282c8d8) [Test] With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 'Mobile Broadband' item in the top-right menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+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 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
** Also affects: obs-studio (Ubuntu) Importance: Undecided Status: 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/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in obs-studio package in Ubuntu: New Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
OBS is also affected. Log: $ obs ... qt.qpa.wayland: Wayland does not support QWindow::requestActivate() ... info: [pipewire] screencast session created The Wayland connection experienced a fatal error: Protocol error Aborted (core dumped) $ -- 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/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1978053] Re: lubuntu kinetic live - firefox can't open libreoffice help file
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1978053 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1978053 Title: lubuntu kinetic live - firefox can't open libreoffice help file Status in libreoffice package in Ubuntu: New Bug description: Lubuntu kinetic jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) To re-create - boot live media (Lubuntu kinetic) - open libreoffice (any, but I used the base app here) - seek help in menu or press F1 ** Expected Results Firefox opens with some helpful text ** Actual Results Firefox opens at URL : file:///usr/share/libreoffice/help/index.html?Target=swriter/.uno%3AHelpIndex=en- US=UNIX=7.3 with message --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- ** Background Notes This issue was reported before in jammy; but was marked RESOLVED. The directory though is different so something has changed.. I believe I'm thinking of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210 I'm unsure if this is a firefox issue, Lubuntu config issue, or Libreoffice issue, but snap'd apps have issues due to confinement thus firefox issue is I fear suspected. Reported also at https://bugzilla.mozilla.org/show_bug.cgi?id=1773414 though i suspect issue may not actually be with firefox snap. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.472 CurrentDesktop: LXQt Date: Thu Jun 9 04:41:26 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220608) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1978053/+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 1978053] [NEW] lubuntu kinetic live - firefox can't open libreoffice help file
Public bug reported: Lubuntu kinetic jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) To re-create - boot live media (Lubuntu kinetic) - open libreoffice (any, but I used the base app here) - seek help in menu or press F1 ** Expected Results Firefox opens with some helpful text ** Actual Results Firefox opens at URL : file:///usr/share/libreoffice/help/index.html?Target=swriter/.uno%3AHelpIndex=en- US=UNIX=7.3 with message --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- ** Background Notes This issue was reported before in jammy; but was marked RESOLVED. The directory though is different so something has changed.. I believe I'm thinking of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210 I'm unsure if this is a firefox issue, Lubuntu config issue, or Libreoffice issue, but snap'd apps have issues due to confinement thus firefox issue is I fear suspected. Reported also at https://bugzilla.mozilla.org/show_bug.cgi?id=1773414 though i suspect issue may not actually be with firefox snap. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.472 CurrentDesktop: LXQt Date: Thu Jun 9 04:41:26 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220608) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1978053 Title: lubuntu kinetic live - firefox can't open libreoffice help file Status in libreoffice package in Ubuntu: New Bug description: Lubuntu kinetic jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) To re-create - boot live media (Lubuntu kinetic) - open libreoffice (any, but I used the base app here) - seek help in menu or press F1 ** Expected Results Firefox opens with some helpful text ** Actual Results Firefox opens at URL : file:///usr/share/libreoffice/help/index.html?Target=swriter/.uno%3AHelpIndex=en- US=UNIX=7.3 with message --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- ** Background Notes This issue was reported before in jammy; but was marked RESOLVED. The directory though is different so something has changed.. I believe I'm thinking of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210 I'm unsure if this is a firefox issue, Lubuntu config issue, or Libreoffice issue, but snap'd apps have issues due to confinement thus firefox issue is I fear suspected. Reported also at https://bugzilla.mozilla.org/show_bug.cgi?id=1773414 though i suspect issue may not actually be with firefox snap. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.472 CurrentDesktop: LXQt Date: Thu Jun 9 04:41:26 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220608) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1978053/+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 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
I second nmaxx's thanks. Nouveau is very slow and my old laptop also has the GeForce 8400GS GPU so I was very glad to see the update. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Released Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1978044] [NEW] In Activities Overview search, only the first item can be selected
Public bug reported: Description:Ubuntu 22.04 LTS Release:22.04 gnome-shell: Installed: 42.1-0ubuntu0.1 Candidate: 42.1-0ubuntu0.1 Version table: *** 42.1-0ubuntu0.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 1. Press the GUI key or "Activities" in the top left of the screen 2. Search for an app. For example, type "calc". 3. Depending on the installed apps, you might see Calculator and LibreOffice Calc icons in some order. 4. Try clicking on an icon -- expected: the app launches, actual: nothing 5. Press an arrow key or tab to try to select a different app -- expected: switches focus to a different icon, actual: nothing is focused, cannot regain focus without mouse ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 22:51:31 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-13 (238 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-08 (1 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1978044 Title: In Activities Overview search, only the first item can be selected Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 gnome-shell: Installed: 42.1-0ubuntu0.1 Candidate: 42.1-0ubuntu0.1 Version table: *** 42.1-0ubuntu0.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 1. Press the GUI key or "Activities" in the top left of the screen 2. Search for an app. For example, type "calc". 3. Depending on the installed apps, you might see Calculator and LibreOffice Calc icons in some order. 4. Try clicking on an icon -- expected: the app launches, actual: nothing 5. Press an arrow key or tab to try to select a different app -- expected: switches focus to a different icon, actual: nothing is focused, cannot regain focus without mouse ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 22:51:31 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-13 (238 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-08 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978044/+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 1969512] Re: Totem unable to play video: "The specified movie could not be found"
I wonder if https://gitlab.gnome.org/GNOME/gtk/-/issues/4950 is related to that (trying to use GLES version 2). ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4950 https://gitlab.gnome.org/GNOME/gtk/-/issues/4950 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Fix Released Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
If MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 doesn't work for you then you are commenting on the wrong bug. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+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 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
** Tags added: oem-priority originate-from-1975803 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1977986 Title: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad Status in OEM Priority Project: New Status in upower package in Ubuntu: New Bug description: We found this issue on several ThinkPad. The upower will change 'pending-charge' to 'charging' after 2 minutes later, but the /sys/class/power_supply/BAT0/status changes to 'Charging' immediately when connecting the power cable. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Sunwoda model:5B10W13975 serial: 34226 power supply: yes updated: Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 55.94 Wh energy-empty:0 Wh energy-full: 57 Wh energy-full-design: 57 Wh energy-rate: 5.79 W voltage: 16.688 V percentage: 98% capacity:100% technology: lithium-polymer icon-name: 'battery-full-charging-symbolic' History (charge): 1654702882 98.000 pending-charge 1654702863 97.000 pending-charge History (rate): 1654702863 5.790 pending-charge 1654702863 6.171 pending-charge $ cat /sys/class/power_supply/BAT0/status Charging To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1977986/+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 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing
The attachment "0001-Remove-pipewire-media-session.service-when-the- packa.patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1977564 Title: wireplumber conflicts with pipewire-media-session & needs fixing Status in pipewire-media-session package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Triaged Status in wireplumber package in Ubuntu: Triaged Status in pipewire-media-session package in Debian: Confirmed Bug description: This issue was reported on IRC and we should probably fix it before installing wireplumber by default so I'm setting the block-proposed tag. https://i.imgur.com/L5VFZO8.png wireplumber is apparently too forceful in how it enables PipeWire. Both Arch Linux and Debian had to https://archlinux.org/news/undone-replacement-of-pipewire-media- session-with-wireplumber/ Is it necessary for wireplumber to conflict with pipewire-media- session? Should we add Replaces? What files does pipewire-media-session need to clean up when it is removed? See https://salsa.debian.org/gnome-team/gnome-remote- desktop/-/commit/52799cfd for an example of how files that aren't technically conffiles can be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1977564/+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 1965951] Re: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()
*** This bug is a duplicate of bug 1965897 *** https://bugs.launchpad.net/bugs/1965897 Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1965951 Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type() Status in gnome-shell package in Ubuntu: Confirmed Bug description: Its fresh installation and I tried install some "dock" extension from extensions.gnome.org ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 22 15:12:43 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_get_window_type () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 meta_display_close () from /lib/x86_64-linux-gnu/libmutter-10.so.0 shell_global_reexec_self () from /usr/lib/gnome-shell/libgnome-shell.so Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965951/+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 1978016] [NEW] package libfprint-2-tod1:amd64 1:1.90.2+tod1-0ubuntu1~20.04.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it be
Public bug reported: nyou@nyou:~$ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libfprint-2-tod1 libfwupdplugin1 shim Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded. 1 not fully installed or removed. Need to get 0 B/44,5 kB of archives. After this operation, 0 B of additional disk space will be used. dpkg: error processing package libfprint-2-tod1:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Errors were encountered while processing: libfprint-2-tod1:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libfprint-2-tod1:amd64 1:1.90.2+tod1-0ubuntu1~20.04.8 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 8 18:09:39 2022 DuplicateSignature: package:libfprint-2-tod1:amd64:1:1.90.2+tod1-0ubuntu1~20.04.8 Preparing to unpack .../38-libavutil56_7%3a4.2.7-0ubuntu0.1_amd64.deb ... Log started: 2022-06-08 18:09:39 dpkg: error processing package libfprint-2-tod1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-04-07 (62 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: libfprint Title: package libfprint-2-tod1:amd64 1:1.90.2+tod1-0ubuntu1~20.04.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1978016 Title: package libfprint-2-tod1:amd64 1:1.90.2+tod1-0ubuntu1~20.04.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libfprint package in Ubuntu: New Bug description: nyou@nyou:~$ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libfprint-2-tod1 libfwupdplugin1 shim Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded. 1 not fully installed or removed. Need to get 0 B/44,5 kB of archives. After this operation, 0 B of additional disk space will be used. dpkg: error processing package libfprint-2-tod1:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Errors were encountered while processing: libfprint-2-tod1:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libfprint-2-tod1:amd64 1:1.90.2+tod1-0ubuntu1~20.04.8 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 8 18:09:39 2022 DuplicateSignature: package:libfprint-2-tod1:amd64:1:1.90.2+tod1-0ubuntu1~20.04.8 Preparing to unpack .../38-libavutil56_7%3a4.2.7-0ubuntu0.1_amd64.deb ... Log started: 2022-06-08 18:09:39 dpkg: error processing package libfprint-2-tod1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-04-07 (62 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: libfprint Title: package libfprint-2-tod1:amd64 1:1.90.2+tod1-0ubuntu1~20.04.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus:
[Desktop-packages] [Bug 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing
Basically, pipewire-pulse.service wants pipewire-session-manager.service. pipewire-session-manager.service is an alias from both wireplumber.service and pipewire-media-session.service. To avoid this conflict, we need to remove pipewire-media-session.service during the remove step of the package, not only at the purge step. I am thinking about applying this fix. And a similar patch for wireplumber, just in case a user wants to move from wireplumber to pipewire-media-session for whatever reason. ** Patch added: "0001-Remove-pipewire-media-session.service-when-the-packa.patch" https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/1977564/+attachment/5595684/+files/0001-Remove-pipewire-media-session.service-when-the-packa.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1977564 Title: wireplumber conflicts with pipewire-media-session & needs fixing Status in pipewire-media-session package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Triaged Status in wireplumber package in Ubuntu: Triaged Status in pipewire-media-session package in Debian: Confirmed Bug description: This issue was reported on IRC and we should probably fix it before installing wireplumber by default so I'm setting the block-proposed tag. https://i.imgur.com/L5VFZO8.png wireplumber is apparently too forceful in how it enables PipeWire. Both Arch Linux and Debian had to https://archlinux.org/news/undone-replacement-of-pipewire-media- session-with-wireplumber/ Is it necessary for wireplumber to conflict with pipewire-media- session? Should we add Replaces? What files does pipewire-media-session need to clean up when it is removed? See https://salsa.debian.org/gnome-team/gnome-remote- desktop/-/commit/52799cfd for an example of how files that aren't technically conffiles can be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1977564/+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 1977660] Re: Power settings have no effect and offer nonexisting options
Could you give details on the model you are using? There are some upstream issue on thinkpad as https://gitlab.freedesktop.org/hadess/power-profiles-daemon/-/issues/78 ** Bug watch added: gitlab.freedesktop.org/hadess/power-profiles-daemon/-/issues #78 https://gitlab.freedesktop.org/hadess/power-profiles-daemon/-/issues/78 -- 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/1977660 Title: Power settings have no effect and offer nonexisting options Status in gnome-control-center package in Ubuntu: Incomplete Bug description: The "power" area of the settings offer three options: powersave, balanced, and performance. As per cpufreq-info "balanced" is not a valid option. Also changing to any of the two really existing options does not change cpu frequency in a visible way. Maybe there is a connection between this and the bug i reported about the matching indicator: https://bugs.launchpad.net/ubuntu/+source/indicator- cpufreq/+bug/1977659 I *can* actually switch between the values using the studio-controls application. changing values there leads to visible changes in cpufreq-info output and /proc/cpuinfo data shown. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-35.36-lowlatency 5.15.35 Uname: Linux 5.15.0-35-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 20:36:14 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-12 (782 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-28 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1977660/+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 1978007] [NEW] Please merge network-manager-applet 1.28.0-1 from Debian unstable
Public bug reported: This is a proposed merge for network-manager-applet 1.28.0-1. I verified that Ubuntu patches were applied and reached Debian, so they were dropped, but some older modifications remain. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium * Merge from Debian unstable. Remaining changes: - Drop all Ubuntu patches. - d/control: + Drop , since the packages are now also available in s390x. + Drop >= 1.8 version requirement for network-manager since all supported releases satisfy it. - d/control, d/rules: + Run dh_translations. -- Nathan Pratta Teodosio Wed, 08 Jun 2022 16:26:11 -0300 ==>END<== I tested it with Pbuilder. ** Affects: network-manager-applet (Ubuntu) Importance: Wishlist Status: Confirmed ** Patch added: "1.28.0-1--1.28.0-1ubuntu1.diff" https://bugs.launchpad.net/bugs/1978007/+attachment/5595678/+files/1.28.0-1--1.28.0-1ubuntu1.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1978007 Title: Please merge network-manager-applet 1.28.0-1 from Debian unstable Status in network-manager-applet package in Ubuntu: Confirmed Bug description: This is a proposed merge for network-manager-applet 1.28.0-1. I verified that Ubuntu patches were applied and reached Debian, so they were dropped, but some older modifications remain. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium * Merge from Debian unstable. Remaining changes: - Drop all Ubuntu patches. - d/control: + Drop , since the packages are now also available in s390x. + Drop >= 1.8 version requirement for network-manager since all supported releases satisfy it. - d/control, d/rules: + Run dh_translations. -- Nathan Pratta Teodosio Wed, 08 Jun 2022 16:26:11 -0300 ==>END<== I tested it with Pbuilder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978007/+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 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
@seb128 I am also affected by this bug and privacy-wise every other Ubuntu 22.04 user as well, but I didn´t respond, trusting the process that this bug would be fixed. So I am supporting your efforts getting an upstream fix shortly or alternatively reverting the change that created the regression. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1977619 Title: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC Status in NetworkManager: New Status in network-manager package in Ubuntu: Triaged Bug description: Situation: My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy perspective, for readability reasons and for network management policies, DHCPv6 should *always* be preferred over SLAAC addresses when available. And according to RFC 6724, the smaller /128 scope of the DHCPv6 address should be chosen over the larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection (in nm-connection-editor *not* selecting "Prefer temporary address" for IPv6 privacy extensions). Then it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Regression: Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Constantly removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's on the router are now the only ways to stop NetworkManager from preferring SLAAC over DHCPv6. None of the local options in NetworkManager 1.36.6 are able to restore the previous, desired and correct way of working: the SLAAC address should never be used as the preferred address if a DHCPv6 lease is given. Looking at the changelog of NetworkManager 1.36.6, multiple things regarding IP address order and temporary addresses have been changed in that release, any of them (or a combination) introducing this bug: * Fix a bug in synchronization of IP addresses with kernel that could lead to a wrong address order. * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag is set. * Ensure temporary IPv6 addresses are removed on disconnect and reapply. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS Steps to reproduce: 1. Connect to a network where the router sends "A" and "M" bits in the RA's and has a DHCPv6 server running (e.g. any OpenWrt router). 2. When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not the case. (The Linux kernel uses the address highest in the list as preferred.) 3. When running something like `curl ifconfig.co`, the SLAAC address is being returned, which makes sense as that is now preferred by the kernel. (But it shouldn't be.) Desired behaviour: NetworkManager should always sort DHCPv6 addresses above SLAAC addresses, as is the case for all versions prior to 1.36.6 and also corrected again in 1.38.0. In case static addresses are manually set, those should take first priority, with DHCPv6 second and SLAAC/autoconf last. Implications: This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on and cannot centrally configure), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. Note that "just disabling SLAAC RA's on the router" is not something everybody can do, as it requires root access to the device. Moreover, it would break IPv6 connectivity entirely for devices that don't support DHCPv6 (read: Android). Conclusion: So this update introduces a very breaking change in IPv6 source address selection to an LTS release, while LTS releases should be stable. I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it should. As that version is also used in Ubuntu kinetic, most likely this bug is not present there. Looking at the changelog of 1.38.0: * Fix bug setting priority for IP addresses. * Static IPv6 addresses from "ipv6.addresses" are now preferred over addresses from DHCPv6, which are preferred over addresses from autoconf. This
[Desktop-packages] [Bug 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
Unfortunately I was not tracking jammy-proposed, so I only found out about this bug when it entered jammy-updates. I don't think my configuration is that exotic to be honest. Many companies use DHCPv6 servers giving out static leases, and many companies use firewalls to restrict incoming (SSH) connections to their servers. And not many network administrators disable SLAAC as that would break IPv6 for all Android users. So corporate and home networks with DHCPv6 and SLAAC enabled are quite common. How viable would it be to create something like 1.36.7~really1.36.4 or something like that, which would be the previous version with only commit 6a82dd18 cherry picked to fix the hotspot issue and not introduce the source address selection bug? I suppose upstream would at some point release 1.36.9, which will hopefully have this bug fixed, and also have commit 6a82dd18 included, so Ubuntu can go back to the upstream version then. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1977619 Title: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC Status in NetworkManager: New Status in network-manager package in Ubuntu: Triaged Bug description: Situation: My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy perspective, for readability reasons and for network management policies, DHCPv6 should *always* be preferred over SLAAC addresses when available. And according to RFC 6724, the smaller /128 scope of the DHCPv6 address should be chosen over the larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection (in nm-connection-editor *not* selecting "Prefer temporary address" for IPv6 privacy extensions). Then it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Regression: Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Constantly removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's on the router are now the only ways to stop NetworkManager from preferring SLAAC over DHCPv6. None of the local options in NetworkManager 1.36.6 are able to restore the previous, desired and correct way of working: the SLAAC address should never be used as the preferred address if a DHCPv6 lease is given. Looking at the changelog of NetworkManager 1.36.6, multiple things regarding IP address order and temporary addresses have been changed in that release, any of them (or a combination) introducing this bug: * Fix a bug in synchronization of IP addresses with kernel that could lead to a wrong address order. * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag is set. * Ensure temporary IPv6 addresses are removed on disconnect and reapply. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS Steps to reproduce: 1. Connect to a network where the router sends "A" and "M" bits in the RA's and has a DHCPv6 server running (e.g. any OpenWrt router). 2. When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not the case. (The Linux kernel uses the address highest in the list as preferred.) 3. When running something like `curl ifconfig.co`, the SLAAC address is being returned, which makes sense as that is now preferred by the kernel. (But it shouldn't be.) Desired behaviour: NetworkManager should always sort DHCPv6 addresses above SLAAC addresses, as is the case for all versions prior to 1.36.6 and also corrected again in 1.38.0. In case static addresses are manually set, those should take first priority, with DHCPv6 second and SLAAC/autoconf last. Implications: This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on and cannot centrally configure), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. Note that "just disabling SLAAC RA's on the router" is not something everybody can do, as it requires root access to the device. Moreover, it would break IPv6 connectivity entirely for devices that don't support DHCPv6 (read: Android).
[Desktop-packages] [Bug 1964601] Re: I have no processor!
Thanks, that explain, and I think we have an understanding of each of the disks/graphics/cpu causes now! ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Triaged ** Summary changed: - I have no processor! + incorrect cpu/graphics/disks information on raspi -- 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/1964601 Title: incorrect cpu/graphics/disks information on raspi Status in gnome-control-center package in Ubuntu: Triaged Bug description: At least according to gnome-control-center anyway. Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi 4B), selecting Settings, then the "About" page shows that gnome- control-center thinks the processor is "", the graphics are "unknown", and apparently so is the disk capacity! I admit it's a trivial thing, but it's been this way since at least hirsute, and it'd be nice to see something vaguely sane in there at some point :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+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 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
@Kevin. Thanks, it's a bit of an annoying situation. The current update is not only in proposed but was moving to updates before you reported the regression, which means we can't simply delete it from proposed, we need a fix or revert. I was hoping upstream would figure out a fix quickly enough that we could do another bugfix upload. If that doesn't play out this way we need to figure out what to do. The initial reason for SRUing the update, out of keeping up with upstream fixes, was that it fixes some hotspot issues which is a topic we are getting complain about (https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6a82dd18) We could revert back the version, including other fixes. Or revert the change that created the regression you reported. Note that while it seems an annoying issue to you that's the only report we got so far which suggest it's not a common configuration for our users, which is also a reason why I decided to wait a bit to see if upstream was reacting before reverting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1977619 Title: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC Status in NetworkManager: New Status in network-manager package in Ubuntu: Triaged Bug description: Situation: My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy perspective, for readability reasons and for network management policies, DHCPv6 should *always* be preferred over SLAAC addresses when available. And according to RFC 6724, the smaller /128 scope of the DHCPv6 address should be chosen over the larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection (in nm-connection-editor *not* selecting "Prefer temporary address" for IPv6 privacy extensions). Then it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Regression: Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Constantly removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's on the router are now the only ways to stop NetworkManager from preferring SLAAC over DHCPv6. None of the local options in NetworkManager 1.36.6 are able to restore the previous, desired and correct way of working: the SLAAC address should never be used as the preferred address if a DHCPv6 lease is given. Looking at the changelog of NetworkManager 1.36.6, multiple things regarding IP address order and temporary addresses have been changed in that release, any of them (or a combination) introducing this bug: * Fix a bug in synchronization of IP addresses with kernel that could lead to a wrong address order. * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag is set. * Ensure temporary IPv6 addresses are removed on disconnect and reapply. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS Steps to reproduce: 1. Connect to a network where the router sends "A" and "M" bits in the RA's and has a DHCPv6 server running (e.g. any OpenWrt router). 2. When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not the case. (The Linux kernel uses the address highest in the list as preferred.) 3. When running something like `curl ifconfig.co`, the SLAAC address is being returned, which makes sense as that is now preferred by the kernel. (But it shouldn't be.) Desired behaviour: NetworkManager should always sort DHCPv6 addresses above SLAAC addresses, as is the case for all versions prior to 1.36.6 and also corrected again in 1.38.0. In case static addresses are manually set, those should take first priority, with DHCPv6 second and SLAAC/autoconf last. Implications: This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on and cannot centrally configure), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. Note that "just disabling SLAAC RA's on the router" is not something everybody can do, as it requires root access to the device. Moreover, it would break IPv6
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Many thanks to Butterfly (kelebek333) for the PPA. :) I can finally use the HWE kernel on Linux Mint 20 with my old GeForce 8400GS. I tried nouveau, but on that card it is essentially software-rendering speed we're talking about (10-20 fps in dxx-rebirth vs. ~200 fps with the 340 drivers). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Released Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
@seb128 What is the plan for the network-manager package in Ubuntu jammy-updates? Is it to be left broken until upstream fixes this bug? Because I think that the problem this last version introduces is a lot bigger than the problem(s) it solves. Therefore I would say that it can be defended to upload a new version that restores 1.36.4-2ubuntu1 for the time being, and then re-sync with upstream when (or if) this bug is fixed. As far as I'm aware, the update from 1.36.4 to 1.36.6 did not close any outstanding Launchpad bugs, so it didn't fix anything from Ubuntu's perspective. It just introduced this regression. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1977619 Title: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC Status in NetworkManager: New Status in network-manager package in Ubuntu: Triaged Bug description: Situation: My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy perspective, for readability reasons and for network management policies, DHCPv6 should *always* be preferred over SLAAC addresses when available. And according to RFC 6724, the smaller /128 scope of the DHCPv6 address should be chosen over the larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection (in nm-connection-editor *not* selecting "Prefer temporary address" for IPv6 privacy extensions). Then it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Regression: Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Constantly removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's on the router are now the only ways to stop NetworkManager from preferring SLAAC over DHCPv6. None of the local options in NetworkManager 1.36.6 are able to restore the previous, desired and correct way of working: the SLAAC address should never be used as the preferred address if a DHCPv6 lease is given. Looking at the changelog of NetworkManager 1.36.6, multiple things regarding IP address order and temporary addresses have been changed in that release, any of them (or a combination) introducing this bug: * Fix a bug in synchronization of IP addresses with kernel that could lead to a wrong address order. * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag is set. * Ensure temporary IPv6 addresses are removed on disconnect and reapply. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS Steps to reproduce: 1. Connect to a network where the router sends "A" and "M" bits in the RA's and has a DHCPv6 server running (e.g. any OpenWrt router). 2. When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not the case. (The Linux kernel uses the address highest in the list as preferred.) 3. When running something like `curl ifconfig.co`, the SLAAC address is being returned, which makes sense as that is now preferred by the kernel. (But it shouldn't be.) Desired behaviour: NetworkManager should always sort DHCPv6 addresses above SLAAC addresses, as is the case for all versions prior to 1.36.6 and also corrected again in 1.38.0. In case static addresses are manually set, those should take first priority, with DHCPv6 second and SLAAC/autoconf last. Implications: This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on and cannot centrally configure), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. Note that "just disabling SLAAC RA's on the router" is not something everybody can do, as it requires root access to the device. Moreover, it would break IPv6 connectivity entirely for devices that don't support DHCPv6 (read: Android). Conclusion: So this update introduces a very breaking change in IPv6 source address selection to an LTS release, while LTS releases should be stable. I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it should. As that
[Desktop-packages] [Bug 1964601] Re: I have no processor!
Sorry, hadn't refreshed this page and didn't notice your comment 9 before posting mine! With the override in place it looks like things work properly: $ MESA_GL_VERSION_OVERRIDE=3.3 /usr/libexec/gnome-control-center-print-renderer V3D 4.2 And looking at the upstream ticket you linked makes a lot of sense: the Pi's GL driver only goes up to 2.1: $ glxinfo | grep "GL version string" OpenGL version string: 2.1 Mesa 22.0.1 -- 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/1964601 Title: I have no processor! Status in gnome-control-center package in Ubuntu: Confirmed Bug description: At least according to gnome-control-center anyway. Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi 4B), selecting Settings, then the "About" page shows that gnome- control-center thinks the processor is "", the graphics are "unknown", and apparently so is the disk capacity! I admit it's a trivial thing, but it's been this way since at least hirsute, and it'd be nice to see something vaguely sane in there at some point :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+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 1884299] Re: Chromium snap won't run with nfs home drive
I get the same error "cannot open path of the current working directory: Permission denied" when trying to open a file located on a filesystem which is mounted with sshfs. This is the case for firefox and chromium-browser (both snaps), but not for google-chrome (not snap). This is on 22.04. It used to work fine for firefox in 21.10, when firefox was not a snap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1884299 Title: Chromium snap won't run with nfs home drive Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: My physical computer lab uses AutoFS home drives (per https://help.ubuntu.com/community/Autofs#Wildcard_characters). If any user tries to run chromium browser, it fails. I assume it is related to these: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 But that says a fix was released, but seems toi only work for NFS home drives https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873 That ones is reported as a dupe but it's not, AutoFS home drives still don't work. $ chromium -v cannot create user data directory: /home/test.student2/snap/chromium/1193: Stale file handle $ tail -f /var/log/syslog Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" $ lsb_release -rd Description: Ubuntu 20.04 LTS $ apt policy chromium-browser chromium-browser: Installed: 81.0.4044.129-0ubuntu0.20.04.1 Candidate: 81.0.4044.129-0ubuntu0.20.04.1 Version table: *** 81.0.4044.129-0ubuntu0.20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 80.0.3987.163-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+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 1859033] Re: guile-2.2 installed but not guild-2.2
FYI, the upstream debian package for guile has been updated (by rlb) to fix this. I have no objection to closing this item. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to guile-2.2 in Ubuntu. https://bugs.launchpad.net/bugs/1859033 Title: guile-2.2 installed but not guild-2.2 Status in guile-2.2 package in Ubuntu: New Bug description: guile-2.2 package apparently installs guile, guile-2.2 and guild in /usr/bin, but not guild-2.2. This causes packages using configure w/ guile.m4 macros to fail: GUILE is defined but not GUILD. So builds which use commands (in the Makefiles) of the form "$(GUILD) compile ..." will fail. Suggest adding guild-2.2 to the install process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: guile-2.2 2.2.3+1-3ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 9 06:30:37 2020 InstallationDate: Installed on 2019-02-03 (339 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: guile-2.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1859033/+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 1951586] Re: Need option to specify wifi regulatory domain
** Changed in: netplan Status: New => In Progress ** Changed in: netplan Assignee: (unassigned) => Lukas Märdian (slyon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: In Progress Status in NetworkManager: New Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Triaged Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 1977660] Re: Power settings have no effect and offer nonexisting options
yes, here it is: $ powerprofilesctl performance: Driver: platform_profile Degraded: no balanced: Driver: platform_profile * power-saver: Driver: platform_profile The other command gives me this - but note that I did an update in between and a reboot to another kernel, while the effect reported keeps the same: $ cpupower frequency-info WARNING: cpupower not found for kernel 5.15.0-37 You may need to install the following packages for this specific kernel: linux-tools-5.15.0-37-generic linux-cloud-tools-5.15.0-37-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic After inbstalling the tools package for the runinng kernel, i get this output, but still no change from changing the governor in the settings or the matchjing indicator, and both keep telling me the current state is "balanced" which does not exist as governor as far as I understand: $ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 4.80 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 2.30 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 2.28 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes And againgf, when I run the "studio-controls" application, this can change the setting. -- 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/1977660 Title: Power settings have no effect and offer nonexisting options Status in gnome-control-center package in Ubuntu: Incomplete Bug description: The "power" area of the settings offer three options: powersave, balanced, and performance. As per cpufreq-info "balanced" is not a valid option. Also changing to any of the two really existing options does not change cpu frequency in a visible way. Maybe there is a connection between this and the bug i reported about the matching indicator: https://bugs.launchpad.net/ubuntu/+source/indicator- cpufreq/+bug/1977659 I *can* actually switch between the values using the studio-controls application. changing values there leads to visible changes in cpufreq-info output and /proc/cpuinfo data shown. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-35.36-lowlatency 5.15.35 Uname: Linux 5.15.0-35-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 20:36:14 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-12 (782 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-28 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1977660/+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 1977986] [NEW] UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad
Public bug reported: We found this issue on several ThinkPad. The upower will change 'pending-charge' to 'charging' after 2 minutes later, but the /sys/class/power_supply/BAT0/status changes to 'Charging' immediately when connecting the power cable. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Sunwoda model:5B10W13975 serial: 34226 power supply: yes updated: Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 55.94 Wh energy-empty:0 Wh energy-full: 57 Wh energy-full-design: 57 Wh energy-rate: 5.79 W voltage: 16.688 V percentage: 98% capacity:100% technology: lithium-polymer icon-name: 'battery-full-charging-symbolic' History (charge): 1654702882 98.000 pending-charge 1654702863 97.000 pending-charge History (rate): 1654702863 5.790 pending-charge 1654702863 6.171 pending-charge $ cat /sys/class/power_supply/BAT0/status Charging ** Affects: upower (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1977986 Title: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad Status in upower package in Ubuntu: New Bug description: We found this issue on several ThinkPad. The upower will change 'pending-charge' to 'charging' after 2 minutes later, but the /sys/class/power_supply/BAT0/status changes to 'Charging' immediately when connecting the power cable. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Sunwoda model:5B10W13975 serial: 34226 power supply: yes updated: Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 55.94 Wh energy-empty:0 Wh energy-full: 57 Wh energy-full-design: 57 Wh energy-rate: 5.79 W voltage: 16.688 V percentage: 98% capacity:100% technology: lithium-polymer icon-name: 'battery-full-charging-symbolic' History (charge): 1654702882 98.000 pending-charge 1654702863 97.000 pending-charge History (rate): 1654702863 5.790 pending-charge 1654702863 6.171 pending-charge $ cat /sys/class/power_supply/BAT0/status Charging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1977986/+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 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
I'm going to Mark it wontfix, it seems not something important enough to justify a stable update. If you want to work on it and update the bug to be SRU compliant and do the verification I'm fine sponsoring the update for you though ** Changed in: hwdata (Ubuntu Focal) Importance: Undecided => Wishlist ** Changed in: hwdata (Ubuntu Jammy) Importance: Undecided => Wishlist ** Changed in: hwdata (Ubuntu Focal) Status: New => Won't Fix ** Changed in: hwdata (Ubuntu Jammy) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: Fix Released Status in hwdata source package in Focal: Won't Fix Status in hwdata source package in Jammy: Won't Fix Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 1975890] Re: mp4 video gets stuck in a frame, like it's paused
Most of them were .mp4 videos downloaded from Tik Tok with yt-dlp (https://github.com/yt-dlp/yt-dlp) or by right-clicking and using the 'Save as' dialog. Here's one example: https://v16-webapp.tiktok.com/150af96e4903dde52283b7197631cd1e/62a10462/video/tos/useast2a/tos- useast2a-pve-0068/861748d6c58c4c4a8b0808e153c5d1f6/?a=1988=0=0=0=tiktok_m=0%7C0%7C1%7C0=1=1602=801=8=0=3=eXd.6HAzMyq8ZACuawe2N5Uoyl7Gb_type=video_mp4=0=NmdmO2RkM2U2NzM4NDQ2OkBpamQ3cjY6ZjZrZDMzNzczM0BeMGBfNDYyX2IxMl8tX2BgYSNsZmgxcjRfLWJgLS1kMTZzcw%3D%3D=202206081419310102230981511D31941C -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1975890 Title: mp4 video gets stuck in a frame, like it's paused Status in totem package in Ubuntu: Incomplete Bug description: The video stops playing at a certain random frame, like it's been paused. You can drag the range control and move forwards and backwards and the frame will change as expected, but toggling play/pause does nothing. I can only reproduce this on Ubuntu 22.04. On Debian 11 it works as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 23:13:19 2022 InstallationDate: Installed on 2022-05-23 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1975890/+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 1969274] Re: openvpn client no longer connects in 22.04 until certificate update
no, only the cipher was needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969274 Title: openvpn client no longer connects in 22.04 until certificate update Status in network-manager-openvpn package in Ubuntu: New Bug description: Client no longer connects. previous version had no problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 15:09:56 2022 InstallationDate: Installed on 2022-04-15 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+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 1962170] Re: DEP8 failure with samba 4.15.5
** Description changed: + [Impact] + Tests are failing with the samba version in jammy. We want people using focal be able to upgrade to newer samba and still be compatible with adsys. + + [Test Plan] + 1. Ensure that DEP8 tests are passing once uploaded to proposed and ready to be migrated + + [Where problems could occur] + The functionalities failing are only on tests running (DEP8 or tests during package builds), but we want to be able to run our tests with newer versions of samba on focal too without regressing existing testsuite. + + + -- + The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server - ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 - you just need to run go test . in internal/ad/ the failure is as the pre-test setup - - 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz + 1. https://autopkgtest.ubuntu.com/results/autopkgtest- + jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz -- 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/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Bug description: [Impact] Tests are failing with the samba version in jammy. We want people using focal be able to upgrade to newer samba and still be compatible with adsys. [Test Plan] 1. Ensure that DEP8 tests are passing once uploaded to proposed and ready to be migrated [Where problems could occur] The functionalities failing are only on tests running (DEP8 or tests during package builds), but we want to be able to run our tests with newer versions of samba on focal too without regressing existing testsuite. -- The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+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 1962510] Re: failing tests with new sssd, blocks python3-defaults
** Description changed: + [Impact] + Fix some flaky tests to ensure that future SRUs are easier to release + + [Test Plan] + 1. Have the package build (tests are running) and that DEP8 tests are passing. + + [Where problems could occur] + The fix is only impacting some tests that were flaky and asking for a rerun. Fixes are only located in this test code to make them more reliable and less racy, even in VM environments. + + - + adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. -- 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/1962510 Title: failing tests with new sssd, blocks python3-defaults Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Bug description: [Impact] Fix some flaky tests to ensure that future SRUs are easier to release [Test Plan] 1. Have the package build (tests are running) and that DEP8 tests are passing. [Where problems could occur] The fix is only impacting some tests that were flaky and asking for a rerun. Fixes are only located in this test code to make them more reliable and less racy, even in VM environments. - adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962510/+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 1961459] Re: adsys pam issues
** Description changed: + [Impact] + Memory leaks in adsys pam modules. + + [Test Plan] + 1. Install SRU version of adsys + 2. Login as an user + 3. Ensure that you can still login successfully. + + [Where problems could occur] + Login can be disabled due to the PAM module crashing. There is only one code path leading to that, so easy to detect. + + -- + These may not be security issues but it's possible I overlooked something; since they live in a security boundary I thought it worth reporting with a bit of hassle. If you'd rather work on this in the open, feel free to open this. pam_adsys.c update_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() -- status != 0 looks like it ought to work but I don't think that's how that API is supposed to be used pam_adsys.c pam_sm_open_session() -- gethostname() indentation is funny Thanks -- 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/1961459 Title: adsys pam issues Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Bug description: [Impact] Memory leaks in adsys pam modules. [Test Plan] 1. Install SRU version of adsys 2. Login as an user 3. Ensure that you can still login successfully. [Where problems could occur] Login can be disabled due to the PAM module crashing. There is only one code path leading to that, so easy to detect. -- These may not be security issues but it's possible I overlooked something; since they live in a security boundary I thought it worth reporting with a bit of hassle. If you'd rather work on this in the open, feel free to open this. pam_adsys.c update_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() -- status != 0 looks like it ought to work but I don't think that's how that API is supposed to be used pam_adsys.c pam_sm_open_session() -- gethostname() indentation is funny Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1961459/+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 1973816] Re: Deja Dup's Google support will break in September 2022 for versions < 43.3
https://launchpad.net/ubuntu/+source/deja-dup/43.3-1ubuntu1 ** Changed in: deja-dup (Ubuntu Focal) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: deja-dup (Ubuntu Focal) Importance: Undecided => High ** Changed in: deja-dup (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: deja-dup (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1973816 Title: Deja Dup's Google support will break in September 2022 for versions < 43.3 Status in deja-dup package in Ubuntu: Fix Released Status in deja-dup source package in Focal: Fix Committed Status in deja-dup source package in Jammy: Fix Released Status in deja-dup package in Debian: New Bug description: * Impact The method Deja-Dup is using to authentificate to google account will stop working in september. * Test case Configure deja-dup to do backups on a google drive account. After confirming the authorization through the web browser it should be possible to start the backup. Check on the webview that the files are correctly added. Restore some data and unsure that's working. * Regression potential The codepath is used for oauth authentification and integration with the system mimetype. Check that the webbrowser auth workflow works as expected, testing deb and snap based browsers -- Hello! I'm the maintainer of Deja Dup. I was recently made aware that Google is removing an oauth workflow that Deja Dup uses, in September. Here's their blog post about it: https://developers.googleblog.com/2022/02/making-oauth-flows- safer.html Here's the upstream bug about switching to a new oauth flow: https://gitlab.gnome.org/World/deja-dup/-/issues/222 I've released version 43.3 with a new oauth workflow. This basically switches us from redirecting the oauth page to a local http://localhost:/ page being served by deja-dup and instead has the browser launch a custom URI like 'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches deja-dup and gives it the correct oauth token. The key differences for packagers is just to note that now deja-dup will register itself as a handler for those weird URI schemes (they are specific to deja-dup, as they include its client ids for the service). I think this deserves a backport to all supported releases. I can whip up a patch for you in a bit, just wanted to get this registered as an issue. To be a bit more specific about what will break: - Existing users that have already granted deja-dup access to Google will continue to work without any issue. - In August, users will see a warning on the oauth screen. - And then in September, any new attempt to connect deja-dup to Google will not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1973816/+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 1977948] Re: Unable to display Chinese name on desktop
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Package changed: update-manager (Ubuntu) => gnome-shell-extension- desktop-icons-ng (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1977948 Title: Unable to display Chinese name on desktop Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Incomplete Bug description: I set the current environment language to Chinese, but when I add a shortcut to the desktop it shows English, I think I need to add the Name[zh_CN] field to the desktop file of this application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1977948/+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 1977977] [NEW] Blanked screen doesn't wake up after locking
Public bug reported: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1977977 Title: Blanked screen doesn't wake up after locking Status in gdm3 package in Ubuntu: New Bug description: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1977977/+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 1977948] [NEW] Unable to display Chinese name on desktop
You have been subscribed to a public bug: I set the current environment language to Chinese, but when I add a shortcut to the desktop it shows English, I think I need to add the Name[zh_CN] field to the desktop file of this application ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: Incomplete -- Unable to display Chinese name on desktop https://bugs.launchpad.net/bugs/1977948 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969274] Re: openvpn client no longer connects in 22.04 until certificate update
did you also change to tls-cipher=DEFAULT:@SECLEVEL=0 ? the error on the askubuntu is > CA signature digest algorithm too weak: which is another case of higher security standards being enforced by openssl3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969274 Title: openvpn client no longer connects in 22.04 until certificate update Status in network-manager-openvpn package in Ubuntu: New Bug description: Client no longer connects. previous version had no problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 15:09:56 2022 InstallationDate: Installed on 2022-04-15 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+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 1969274] Re: openvpn client no longer connects in 22.04 until certificate update
FYI
In the `/var/log/syslog` there was a message about inconsistent cipher between
client and server ("Failed to negociate cipher with server.")
I fixed the problem by:
- editing the file
`/etc/NetworkManager/system-connections/(connectionname).nmconnection`
- adding in the vpn section the line
`cipher=BF-CBC`
Thanks to https://askubuntu.com/questions/1407774/cant-connect-to-vpn-
after-upgrading-to-ubuntu-22-04 that helped me finding the file and
knowing the available options.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1969274
Title:
openvpn client no longer connects in 22.04 until certificate update
Status in network-manager-openvpn package in Ubuntu:
New
Bug description:
Client no longer connects. previous version had no problem
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager-openvpn 1.8.18-1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 16 15:09:56 2022
InstallationDate: Installed on 2022-04-15 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
The "Unblank lock screen" extenions (https://extensions.gnome.org/extension/1414/unblank/) works for me as a workaround until this issue gets fixed. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+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 1964601] Re: I have no processor!
I've done a bit of debugging on this; wound up tweaking the code
mentioned in comment 8 above to return g_strdup("NULL context") instead
of return NULL and with this in place, gnome-control-center-print-
renderer (and indeed the "Graphics" field of the control center) both
return "NULL context" so at least we know that's what's going on.
I also hacked up an openGL demo to print the result of
glGetString(GL_RENDERER) and apparently we should be getting "V3D 4.2"
when everything's working correctly. Unfortunately I've no idea why
gdk_window_create_gl_context isn't working on the pi desktop.
--
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/1964601
Title:
I have no processor!
Status in gnome-control-center package in Ubuntu:
Confirmed
Bug description:
At least according to gnome-control-center anyway.
Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi
4B), selecting Settings, then the "About" page shows that gnome-
control-center thinks the processor is "", the graphics are "unknown",
and apparently so is the disk capacity!
I admit it's a trivial thing, but it's been this way since at least
hirsute, and it'd be nice to see something vaguely sane in there at
some point :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+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 1973816] Re: Deja Dup's Google support will break in September 2022 for versions < 43.3
Here is the SRU for Focal. I have built it successfully with Pbuilder. I installed the resulting deb and confirmed the program still works as intended: I set up Dejadup with my Google account, made a back-up there, and restored it. ** Patch added: "40.7-0ubuntu1--40.7-0ubuntu2.diff" https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1973816/+attachment/5595610/+files/40.7-0ubuntu1--40.7-0ubuntu2.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1973816 Title: Deja Dup's Google support will break in September 2022 for versions < 43.3 Status in deja-dup package in Ubuntu: Fix Committed Status in deja-dup source package in Focal: In Progress Status in deja-dup source package in Jammy: Fix Released Status in deja-dup package in Debian: New Bug description: * Impact The method Deja-Dup is using to authentificate to google account will stop working in september. * Test case Configure deja-dup to do backups on a google drive account. After confirming the authorization through the web browser it should be possible to start the backup. Check on the webview that the files are correctly added. Restore some data and unsure that's working. * Regression potential The codepath is used for oauth authentification and integration with the system mimetype. Check that the webbrowser auth workflow works as expected, testing deb and snap based browsers -- Hello! I'm the maintainer of Deja Dup. I was recently made aware that Google is removing an oauth workflow that Deja Dup uses, in September. Here's their blog post about it: https://developers.googleblog.com/2022/02/making-oauth-flows- safer.html Here's the upstream bug about switching to a new oauth flow: https://gitlab.gnome.org/World/deja-dup/-/issues/222 I've released version 43.3 with a new oauth workflow. This basically switches us from redirecting the oauth page to a local http://localhost:/ page being served by deja-dup and instead has the browser launch a custom URI like 'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches deja-dup and gives it the correct oauth token. The key differences for packagers is just to note that now deja-dup will register itself as a handler for those weird URI schemes (they are specific to deja-dup, as they include its client ids for the service). I think this deserves a backport to all supported releases. I can whip up a patch for you in a bit, just wanted to get this registered as an issue. To be a bit more specific about what will break: - Existing users that have already granted deja-dup access to Google will continue to work without any issue. - In August, users will see a warning on the oauth screen. - And then in September, any new attempt to connect deja-dup to Google will not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1973816/+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 1977968] [NEW] Security update tracking bug
*** This bug is a security vulnerability *** Public security bug reported: This bug is to track the security update that will contain these possibly security-relevant commits: https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=e2b0f0d8d63e1223bb714a9efb37e2257818268b https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=7a80d2096f1b7125085e21448112aa02f49f5e9a ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1977968 Title: Security update tracking bug Status in bluez package in Ubuntu: New Bug description: This bug is to track the security update that will contain these possibly security-relevant commits: https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=e2b0f0d8d63e1223bb714a9efb37e2257818268b https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=7a80d2096f1b7125085e21448112aa02f49f5e9a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1977968/+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 1973751] Re: Machines or Users scripts are not executed
I successfully verified that this is fixed in Jammy and didn't introduce any regression with adsys 0.8.5~22.04. Marking as verification-done ** 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973751 Title: Machines or Users scripts are not executed Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Machine and user scripts are not executed on startup/shutdown/login/logoff. /run has been recently changed to be noexec on jammy. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mecanism has been reviewed by the security team, so we can reset them as executable. [Test case] * Setup some scripts under AD to be executed, one for machine scripts (on startup), one for user scripts (on login). Those scripts can create some temporary files under /tmp for instance. * Reboot and login on the Ubuntu laptop connected with AD by adsys, with ua attached * Check that the scripts were executed by testing that the created file under /tmp are present. [Where problems could occur] This is technically a new .mount systemd unit service which takes the same mount option than /run, but don’t set noexec. The setup is similar than qemu .mount unit for instance. Worst impact could be that the script policy manager can’t run the scripts as it is already the case today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973751/+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 1973748] Re: Updating any gsettings key makes user dconf database unreadable
I successfully verified that this is fixed in Jammy and didn't introduce any regression with adsys 0.8.5~22.04. Marking as verification-done ** 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973748 Title: Updating any gsettings key makes user dconf database unreadable Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Changing any gsettings key in AD resulted in user databases under /etc/dconf, owned by root, with 0600 as permissions. This change was done late in the cycle after passing some permissions checkers to harden the binaries. However, in that case, the user databases needs to be readable by the users so that they can apply those values, so we need to align with ibus profile and makes them 644. [Test case] * Change a gsettings key under AD, like picture-uri one. * Login on the Ubuntu laptop connected with AD by adsys * The background should now be changed to the set value. [Where problems could occur] This code is located in the dconf policy application manager and restricted to it. The negative impact in case of a new bug will be seen by gsettings key not being applied as it is already nowdays. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973748/+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 1973745] Re: adsys windows admx/adml lts only does not include 22.04
I successfully verified that this is fixed in Jammy and didn't introduce any regression with adsys 0.8.5~22.04. Marking as verification-done ** 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973745 Title: adsys windows admx/adml lts only does not include 22.04 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Due to some misunterpretation in how the launchpad API works when listing lts only, 22.04 was not included there by the admx/adml files generated by CI. Consequently, when those files are deployed on Windows AD server with LTS only templates, this one is not listed. [Test Plan] * Deploy the admx/adml generated for "LTS Only" use cases on an AD server * Open any GPO rule like changing the background * Ensure there is an "Override for 22.04" entry. [Where problems could occur] Those files are statically generated and then shipped as thus. There is no runtime exercising this. The consequence of those generated files to be invalid is that Windows AD server will not show up "Ubuntu" in its GPO template. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973745/+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 1973752] Re: Fix privilege permission which can not be set to disabled
I successfully verified that this is fixed in Jammy and didn't introduce any regression with adsys 0.8.5~22.04. Marking as verification-done ** 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973752 Title: Fix privilege permission which can not be set to disabled Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Disallowing local administrator does not work as excepted: - on some AD server, setting in the UI this key (and some other similars) to disabled, go to next GPO rule, then back to this one, AD will display the key as enabled. - on the client machine, we can see that the key has no state and nothing is forcibly allowed or disallowed. [Test case] * Install the new admx/adml with this version on the AD server. * On AD, go to disallow local administator, set it to disabled * Go to next GPO rules and then go back * The rule should still be disabled. * On an Ubuntu machine connected with AD by adsys, with ua attached, force a machine refresh with adsysctl policy update -m. * Check in adsysctl policy applied --all that the key is displayed as disabled * Confirm that no local administrator (part of the sudo group) can run "sudo". [Where problems could occur] The privilege manager and other policies impacts both Windows and client: - on Windows, this is in the admx/adml are statically generated and then shipped as thus. There is no runtime exercising this. The consequence of those generated files to be invalid is that Windows AD server will not show up "Ubuntu" in its GPO template. - on the client, the privilege manager is the main consumer of those disabled key types. The other kinds of keys are not impacted. [Additional informations] * New test cases have been added for the client part. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973752/+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 1977966] [NEW] Huawei MateStation S [AMD HD-Audio + Realtek ALC256] Rear analog output not detected
Public bug reported: Hello, unfortunately I am not familiar with Ubuntu anymore since a decade so hopefully I'm filing this bug correctly (I am using ubuntu-bug which reportbug recommended to me); that said, my problem is... The name-brand computer in the topic is almost perfectly Linux* compatible, except for the fact the conventional green audio socket on the back is not detected; however, the rear inputs (mic & line) as well as the front jack (combo headphone+mic, only tested the former) do in fact work fine! * The problem also manifests in Devuan Chimaera (5.10 and 5.18) and Fedora I am willing to cooperate in testing if you need to! Thanks in advance lspci (relevant device only): 08:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] /proc/asound/cards (alsamixer): 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd05c8000 irq 92 1 [Generic_1 ]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd05c irq 93 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: riki 1576 F pulseaudio /dev/snd/controlC0: riki 1576 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 12:07:54 2022 InstallationDate: Installed on 2022-04-26 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HD-Audio Generic, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2021 dmi.bios.release: 1.13 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.13 dmi.board.asset.tag: N/A dmi.board.name: PUM-WDX9-PCB-B1 dmi.board.vendor: HUAWEI dmi.board.version: M1020 dmi.chassis.asset.tag: 3430210522028242 dmi.chassis.type: 3 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1020 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnHUAWEI:bvr1.13:bd04/30/2021:br1.13:efr1.13:svnHUAWEI:pnPUM-WDX9:pvrM1020:rvnHUAWEI:rnPUM-WDX9-PCB-B1:rvrM1020:cvnHUAWEI:ct3:cvrM1020:skuC100: dmi.product.family: MateStation S dmi.product.name: PUM-WDX9 dmi.product.sku: C100 dmi.product.version: M1020 dmi.sys.vendor: HUAWEI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/1977966 Title: Huawei MateStation S [AMD HD-Audio + Realtek ALC256] Rear analog output not detected Status in alsa-driver package in Ubuntu: New Bug description: Hello, unfortunately I am not familiar with Ubuntu anymore since a decade so hopefully I'm filing this bug correctly (I am using ubuntu- bug which reportbug recommended to me); that said, my problem is... The name-brand computer in the topic is almost perfectly Linux* compatible, except for the fact the conventional green audio socket on the back is not detected; however, the rear inputs (mic & line) as well as the front jack (combo headphone+mic, only tested the former) do in fact work fine! * The problem also manifests in Devuan Chimaera (5.10 and 5.18) and Fedora I am willing to cooperate in testing if you need to! Thanks in advance lspci (relevant device only): 08:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] /proc/asound/cards (alsamixer): 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd05c8000 irq 92 1 [Generic_1 ]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd05c irq 93 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: riki 1576 F pulseaudio /dev/snd/controlC0: riki 1576 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 12:07:54 2022 InstallationDate: Installed on 2022-04-26 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all
[Desktop-packages] [Bug 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
Those changes are in https://bugs.launchpad.net/ubuntu/+source/hwdata/0.359-1 now. Could you describe why you would like the changes backported to older series and provide a testcase? Which software are relying on those information and to for what purpose? ** Changed in: hwdata (Ubuntu) Importance: Undecided => Low ** Changed in: hwdata (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: Fix Released Status in hwdata source package in Focal: New Status in hwdata source package in Jammy: Incomplete Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET 1b4b: 2241: 1028: 2196 ROR-N100 Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental
More discussion here: https://salsa.debian.org/utopia- team/polkit/-/merge_requests/6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 0.120-6 (main) from Debian experimental Changelog entries since current kinetic version 0.105-33: https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6 In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. It appears the Debian maintainer is considering switching Debian to the updated version in time for the next Debian Stable release (so uploading to unstable later this year). My requested deadline is August 25, Ubuntu 22.10 Feature Freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1965490] Re: Create multiple profiles per verb for conflicting devices
** Changed in: pulseaudio (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1965490 Title: Create multiple profiles per verb for conflicting devices Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: Please include the following MR to make UCM's ConflictingDevice work properly under PulseAudio. Systems like Lenovo P520c requires the change to make audio port selection logic really work. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/596 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1965490/+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 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental
> There was a proposal to use duktape instead of mozjs for the JavaScript > interpreter but I don't think that's been merged yet. This was merged upstream, but unfortunately there has not yet been a release that contains this change. I don't really want to use an arbitrary git snapshot for security- sensitive software; but then again, all releases of polkit have security vulnerabilities (CVE-2021-4115 and CVE-2021-4034 were both fixed since 0.120) so in some ways an arbitrary git snapshot would be safer. I was surprised to see that Fedora is currently patching polkit to use mozjs91 (also merged upstream but not released), rather than patching it to use duktape. > My understanding is the Debian experimental version doesn't support both at > the same > time, it's one or the other depending on which binary package you install. That is correct. You can have the old PKLA policies with no runtime dependency on mozjs by installing polkitd-pkla, or you can have the JS policies with a runtime dependency on mozjs (which will switch to duktape in future) by installing polkitd-javascript, but you can't have both simultaneously. There is a separate package in e.g. Fedora that extends the JS backend to also read PKLA policies, but that's not currently in Debian or Ubuntu, and it isn't clear to me that it should be. I have also been very tempted to modify 0.120 so it only builds polkitd- pkla (dropping the JS dependency) and upload that to unstable, versioned 0.105+really0.120 or something, as a way to get a PKLA backend that isn't in a codebase from the distant past (look at the debian/patches of 0.105 and despair). ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4034 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4115 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 0.120-6 (main) from Debian experimental Changelog entries since current kinetic version 0.105-33: https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6 In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. It appears the Debian maintainer is considering switching Debian to the updated version in time for the next Debian Stable release (so uploading to unstable later this year). My requested deadline is August 25, Ubuntu 22.10 Feature Freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1977964] Re: /usr/bin/gnome-control-center:11:reset_all_shortcuts_cb:gtk_list_box_forall:reset_all_clicked_cb:_g_closure_invoke_va:g_signal_emit_valist
The issue is fixed by https://gitlab.gnome.org/GNOME/gnome-control- center/-/merge_requests/1244 which is available in https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/1:41.7-0ubuntu1 ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released -- 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/1977964 Title: /usr/bin/gnome-control- center:11:reset_all_shortcuts_cb:gtk_list_box_forall:reset_all_clicked_cb:_g_closure_invoke_va:g_signal_emit_valist Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:41.4-1ubuntu13.2, the problem page at https://errors.ubuntu.com/problem/a8df2c456ed6a6ef3cfd937f57f479e8c586d861 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1977964/+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 1977964] [NEW] /usr/bin/gnome-control-center:11:reset_all_shortcuts_cb:gtk_list_box_forall:reset_all_clicked_cb:_g_closure_invoke_va:g_signal_emit_valist
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:41.4-1ubuntu13.2, the problem page at https://errors.ubuntu.com/problem/a8df2c456ed6a6ef3cfd937f57f479e8c586d861 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-control-center (Ubuntu) Importance: Low Status: Fix Released ** Tags: 20 impish jammy kylin-22.04 -- 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/1977964 Title: /usr/bin/gnome-control- center:11:reset_all_shortcuts_cb:gtk_list_box_forall:reset_all_clicked_cb:_g_closure_invoke_va:g_signal_emit_valist Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:41.4-1ubuntu13.2, the problem page at https://errors.ubuntu.com/problem/a8df2c456ed6a6ef3cfd937f57f479e8c586d861 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1977964/+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 1964601] Re: I have no processor!
Is the renderer result different if MESA_GL_VERSION_OVERRIDE=3.3 is exported? It could be similar to https://gitlab.gnome.org/GNOME/gtk/-/issues/2619 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #2619 https://gitlab.gnome.org/GNOME/gtk/-/issues/2619 -- 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/1964601 Title: I have no processor! Status in gnome-control-center package in Ubuntu: Confirmed Bug description: At least according to gnome-control-center anyway. Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi 4B), selecting Settings, then the "About" page shows that gnome- control-center thinks the processor is "", the graphics are "unknown", and apparently so is the disk capacity! I admit it's a trivial thing, but it's been this way since at least hirsute, and it'd be nice to see something vaguely sane in there at some point :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+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 1969512] Re: Totem unable to play video: "The specified movie could not be found"
New upstream report, https://gitlab.gnome.org/GNOME/totem/-/issues/523 which also has to do with https://gitlab.gnome.org/GNOME/gtk/-/issues/2619 GTK doesn't handle opengl < 3.0 correctly, which seems to be the same on the raspi? Does setting MESA_GL_VERSION_OVERRIDE=3.3 workaround the issue? ** Bug watch added: gitlab.gnome.org/GNOME/totem/-/issues #523 https://gitlab.gnome.org/GNOME/totem/-/issues/523 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #2619 https://gitlab.gnome.org/GNOME/gtk/-/issues/2619 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Fix Released Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+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 1977666] Re: gnome-shell crash when a monitor is connected
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: amdgpu ** Summary changed: - gnome-shell crash when a monitor is connected + [amdgpu] gnome-shell crash when a monitor is connected ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: multimonitor -- 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/1977666 Title: [amdgpu] gnome-shell crash when a monitor is connected Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I have just installed Ubuntu 22.04, and I have found a bug when I connect an external monitor to my laptop. Gnome-shell crash, and it seems to be linked with Wayland, the problem doesn't appear with Xorg. Here is my syslog when the crash occurs : Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: GNOME Shell crashed with signal 11 Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: == Stack trace for context 0x562d4c9ca4b0 == Jun 4 23:23:04 Ubuntu-Principal psensor[31395]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal xdg-desktop-por[29992]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal evolution-alarm[29692]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal xdg-desktop-por[30039]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-media-keys[29633]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-wacom[29665]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-keyboard[29631]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-power[29638]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal nautilus[29574]: Error reading events from display: Connexion ré-initialisée par le correspondant Jun 4 23:23:04 Ubuntu-Principal xpad[29711]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal update-notifier[31948]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal gnome-shell[29781]: (EE) failed to write to Xwayland fd: Broken pipe Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.Shell@wayland.service: Main process exited, code=dumped, status=11/SEGV Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Power.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]:
[Desktop-packages] [Bug 1977695] Re: Black Screen on Boot with X11
Please also check for evidence of crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- 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/1977695 Title: Black Screen on Boot with X11 Status in xorg-server package in Ubuntu: Incomplete Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 1. Uncomment WaylandEnable=false in /etc/gdm3/custom.conf 2. Reboot. 3. See black screen after selecting Ubuntu at GRUB prompt. Login screen never loads. Unplugging any external monitors appears to have no effect on the bug. I am aware that most users of Ubuntu 22.04 see an option at the login screen to change the display manager. I have never seen such an option. My machine always uses Wayland unless I modify /etc/gdm3/custom.conf directly. Using Wayland is detrimental to my health, because the Night Light feature does nothing. I have nvidia- driver-510 installed. I am happy to provide further debugging information upon request. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-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 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:47:31 2022 DistUpgraded: 2022-05-07 18:27:00,043 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8259] Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8259] InstallationDate: Installed on 2020-12-09 (543 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP OMEN by HP Laptop ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-35-generic root=UUID=13d7b775-7783-44fc-8e24-164127457fd4 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-05-08 (28 days ago) dmi.bios.date: 12/22/2020 dmi.bios.release: 15.56 dmi.bios.vendor: Insyde dmi.bios.version: F.56 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.72 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 83.72 dmi.modalias: dmi:bvnInsyde:bvrF.56:bd12/22/2020:br15.56:efr83.72:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.72:cvnHP:ct10:cvrChassisVersion:skuW2N35UAR#ABA: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: W2N35UAR#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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-server/+bug/1977695/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1977695] Re: Black Screen on Boot with X11
Thanks for the bug report. Please: 1. Reproduce the black screen problem again. 2. Reboot in a mode that avoids the problem. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Tags added: hybrid i915 nvidia ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1977695 Title: Black Screen on Boot with X11 Status in xorg-server package in Ubuntu: Incomplete Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 1. Uncomment WaylandEnable=false in /etc/gdm3/custom.conf 2. Reboot. 3. See black screen after selecting Ubuntu at GRUB prompt. Login screen never loads. Unplugging any external monitors appears to have no effect on the bug. I am aware that most users of Ubuntu 22.04 see an option at the login screen to change the display manager. I have never seen such an option. My machine always uses Wayland unless I modify /etc/gdm3/custom.conf directly. Using Wayland is detrimental to my health, because the Night Light feature does nothing. I have nvidia- driver-510 installed. I am happy to provide further debugging information upon request. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-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 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:47:31 2022 DistUpgraded: 2022-05-07 18:27:00,043 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8259] Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8259] InstallationDate: Installed on 2020-12-09 (543 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP OMEN by HP Laptop ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-35-generic root=UUID=13d7b775-7783-44fc-8e24-164127457fd4 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-05-08 (28 days ago) dmi.bios.date: 12/22/2020 dmi.bios.release: 15.56 dmi.bios.vendor: Insyde dmi.bios.version: F.56 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.72 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 83.72 dmi.modalias: dmi:bvnInsyde:bvrF.56:bd12/22/2020:br15.56:efr83.72:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.72:cvnHP:ct10:cvrChassisVersion:skuW2N35UAR#ABA: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: W2N35UAR#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
fprietog, that's a driver issue. Nothing what g-r-d can do about (nor even knows about). It should be reported against the RPi gpu driver here. This is something, that Ubuntus Raspberry Pi team should actually test, before advertising RPi support. Possible related issues: https://github.com/raspberrypi/linux/issues/3416 https://github.com/raspberrypi/linux/issues/3411 ** Bug watch added: github.com/raspberrypi/linux/issues #3416 https://github.com/raspberrypi/linux/issues/3416 ** Bug watch added: github.com/raspberrypi/linux/issues #3411 https://github.com/raspberrypi/linux/issues/3411 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 19. abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop. abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop... abr 25 00:12:18 fpgrpi systemd[2859]: Started GNOME Remote Desktop. abr 25 00:12:19 fpgrpi
[Desktop-packages] [Bug 1977748] Re: apport-bug thinks it's running on Xorg
The statement "apport-bug thinks it's running on Xorg" appears to be false. Apport created this bug and correctly identified that you are using Wayland (see the Tags section). While all graphics bugs do get assigned to the 'xorg' source package by default, that's a minor annoyance and I suspect isn't the main problem you want to solve... So what's the real issue we should discuss here? Is it the Cairo problem from https://answers.launchpad.net/ubuntu/+question/702075 ? ** 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/1977748 Title: apport-bug thinks it's running on Xorg Status in Ubuntu: Incomplete Bug description: Instructed by "ask a question" I tried to file a wayland-targeted bug, but apport-bug thinks I'm running Xorg. See https://answers.launchpad.net/ubuntu/+question/702075 PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy $ ps -ef | grep Xwayland xx 24931685 0 Jun04 ?00:05:36 /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1001/.mutter-Xwaylandauth.5ZZYM1 -listen 4 -listen 5 -displayfd 6 -initfd 7 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 06:40:48 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0991] InstallationDate: Installed on 2021-10-02 (246 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic root=UUID=c737013a-1cc7-494f-a1b7-a6efce6f09f7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2022 dmi.bios.release: 3.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.6.0 dmi.board.name: 0MK6WC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.6.0:bd03/17/2022:br3.6:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MK6WC:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/1977748/+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 1969274] Re: openvpn client no longer connects in 22.04 until certificate update
if you have AX88U and Merlin firmware, raise a new OpenVPN server that will be have a new certificate and then slowly migrate all your fleet from server 1 to server 2, switching the server 1 at the end of the journey, IMHO... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969274 Title: openvpn client no longer connects in 22.04 until certificate update Status in network-manager-openvpn package in Ubuntu: New Bug description: Client no longer connects. previous version had no problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 15:09:56 2022 InstallationDate: Installed on 2022-04-15 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+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 1977912] Re: Ubuntu 22.04 desktop shortcut not executable
I can't yet find where those error messages are coming from, but they're not mentioned in the gnome-shell source code. ** Tags added: jammy ** Package changed: gnome-shell (Ubuntu) => ubuntu -- 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/1977912 Title: Ubuntu 22.04 desktop shortcut not executable Status in Ubuntu: New Bug description: Ubuntu 22.04 desktop shortcut created from /usr/share/applications cannot be executed! right-click does not show allow launching in the drop down menu! so it cannot be launched and show the message: Untrusted Desktop File This .desktop is not trusted. It can not be launched. To enable launching, right-click then: Enable "Allow Launching" but guess what there is no "Allow Launching" in the drop down menu. It is working in Ubuntu 20.04 and the "Allow Launching" is available. Making the shortcut executable and making desktop owns by user and not root does not help. 1) release: Ubuntu 22.04 LTS Jammy 5.15.0-37-generic 2) package: not relevant. 3) what you expect: execution of the .desktop shortcut 4) what happened instead: message: Untrusted Desktop File This .desktop is not trusted. It can not be launched. To enable launching, right-click then: Enable "Allow Launching" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1977912/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I can confirm #14 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1977935] Re: Right clicking the app status bar changes right click menu for complete window and doesn't reset to file context actions.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1977935 Title: Right clicking the app status bar changes right click menu for complete window and doesn't reset to file context actions. Status in nautilus package in Ubuntu: Incomplete Bug description: Clicking the top status bar affects the whole window's right click context menu with "Take Screenshot", "Hide", "Restore", "Move", etc even when right clicking on files or folders. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 12:52:57 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.window-state' b'sidebar-width' b'195' RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-05-30 (8 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1977935/+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 1969274] Re: openvpn client no longer connects in 22.04 until certificate update
jorge, I don't understand what do you mean by "update the certificate". We have one openvpn server at the company with all users connected to it. We have just bought a new machine that runs Ubuntu 22.04 for a new comer. This new comer can't connect to the vpn. We haven't touch the server, but we don't want to update the certificate of all our 50 users every time a new one is added ! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969274 Title: openvpn client no longer connects in 22.04 until certificate update Status in network-manager-openvpn package in Ubuntu: New Bug description: Client no longer connects. previous version had no problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 15:09:56 2022 InstallationDate: Installed on 2022-04-15 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+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 1976554] Re: [Lenovo X1 Yoga 5th Gen] Screen auto rotates randomly after suspend
Maybe related: bug 1960747 and bug 1973402 ** Summary changed: - Screen auto rotates randomly after suspend + [Lenovo X1 Yoga 5th Gen] Screen auto rotates randomly after suspend ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/1976554 Title: [Lenovo X1 Yoga 5th Gen] Screen auto rotates randomly after suspend Status in mutter package in Ubuntu: New Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-30 (707 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mutter 42.0-3ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-22 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+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 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
This is a very important issue because there are some GLX apps doesn't work with PRIME offload so they need Nvidia to be the default. -- 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/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+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 1975872] Re: [ASUS GL552VW] Loss of signal (black screen) on external monitor
Please also try this in a Xorg session: xrandr --output HDMI-2 --set "max bpc" 8 If that fixes the problem then you should subscribe to https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2412 -- 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/1975872 Title: [ASUS GL552VW] Loss of signal (black screen) on external monitor Status in mutter package in Ubuntu: Incomplete Bug description: External screen flickers on and off (image is present and then signal is lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh installation. Details: - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make that HDMI work with NVIDIA GTX 960M in my laptop). - Nothing was installed after installing the OS - i connected to the Internet while installing the system and marked the option to download the updates. - I had that issue on Windows 10 - I fixed it by installing a latest Intel GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers installed by Windows - they were the latest Intel drivers. - Internal screen works fine. - If I mirror external and internal monitor, external isn't flickering, but internal monitor's resolution is lower that external's one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 26 22:34:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d] InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. GL552VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mutter/+bug/1975872/+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 1976554] Re: Screen auto rotates randomly after suspend
I detected the screen is also rotating after suspend if you *lock* screen rotation. This is even more annoying, cause the screen rotations does not revert into its current position. Machine is a X1 Yoga 5th Gen -- 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/1976554 Title: [Lenovo X1 Yoga 5th Gen] Screen auto rotates randomly after suspend Status in mutter package in Ubuntu: New Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-30 (707 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mutter 42.0-3ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-22 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+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 1976554] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1976554/+attachment/5595558/+files/ProcCpuinfoMinimal.txt -- 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/1976554 Title: Screen auto rotates randomly after suspend Status in mutter package in Ubuntu: Incomplete Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-30 (707 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mutter 42.0-3ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-22 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+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 1976554] Re: Screen auto rotates randomly after suspend
apport information ** Tags added: apport-collected ** Description changed: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2020-06-30 (707 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: mutter 42.0-3ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/usr/bin/zsh + ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 + Tags: jammy + Uname: Linux 5.15.0-33-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-22 (46 days ago) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1976554/+attachment/5595557/+files/Dependencies.txt -- 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/1976554 Title: Screen auto rotates randomly after suspend Status in mutter package in Ubuntu: Incomplete Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-30 (707 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mutter 42.0-3ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-22 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+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 1977649] Re: [i915] Analog VGA defaults to 1024x768 instead of 1080p
Please try booting the newer Ubuntu 22.04 release from USB: https://ubuntu.com/download/desktop If that fixes the problem then I would recommend installing 22.04 instead. ** Summary changed: - my system is not showing me 1080p resolution + [i915] Analog VGA defaults to 1024x768 instead of 1080p ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Tags added: i915 -- 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/1977649 Title: [i915] Analog VGA defaults to 1024x768 instead of 1080p Status in linux-hwe-5.13 package in Ubuntu: New Bug description: After ubuntu 20 install I am not able to increase my screen resolution. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 19:16:39 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4th Generation Core Processor Family Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2022-06-04 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Gigabyte Technology Co., Ltd. H81M-S1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-44-generic root=UUID=fc58eb01-ce48-4d0e-ac05-443d37948ed0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-S1 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/17/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S1:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-S1 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1977649/+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 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xwayland (Ubuntu) Status: New => Confirmed -- 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/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+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 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed -- 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/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+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 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
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 xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+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 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags added: jammy wayland-session -- 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/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+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 1974029] Re: [nvidia] vram memory leak under Wayland
** Tags added: gnome-shell-leak -- 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/1974029 Title: [nvidia] vram memory leak under Wayland Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: I use 3 monitors. When I turn two of then off and on, the "memory usage" shown by nvidia-smi grows by approximately 400 MB each cycle. When used video memory reaches maximum my card has (it ix GTX 970 with 4GB) the graphical system sort of crashes (desktop is not shown, one of the monitor does not show image at all). This occurs only under Wayland. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp 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..0c.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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 18 14:50:11 2022 DistUpgraded: 2022-03-19 09:03:59,252 INFO cache.commit() DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed nvidia/510.60.02, 5.15.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:367a] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=UUID=ca73c670-cd82-4bb7-9d49-1e036cf94a1a ro usbcore.autosuspend=-1 libata.force=1.00:noncq acpi_enforce_resources=lax libata.noacpi=1 amd_iommu=on iommu=pt SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-03-19 (60 days ago) dmi.bios.date: 08/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5861 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5861:bd08/10/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/mutter/+bug/1974029/+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 1977648] Re: GLX is rendered by Intel GPU only in Wayland
*** This bug is a duplicate of bug 1969130 *** https://bugs.launchpad.net/bugs/1969130 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 1969130, 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. ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Package changed: wayland (Ubuntu) => xwayland (Ubuntu) ** Summary changed: - GLX is rendered by Intel GPU only in Wayland + [nvidia] GLX is rendered by Intel GPU only in Wayland ** Tags added: nvidia nvidia-wayland ** This bug has been marked a duplicate of bug 1969130 [Feature requrest] nvidia offloading doesn't work on Wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1977648 Title: [nvidia] GLX is rendered by Intel GPU only in Wayland Status in mutter package in Ubuntu: New Status in xwayland package in Ubuntu: New Bug description: I'm using Nvidia driver and PRIME profile is set to performance, however in Wayland only, GLX is rendered by Intel GPU and can't have Nvidia as default renderer. This is a problem because not all OpenGL applications can work with XWayland or by setting the ENV variables to use Nvidia. In Xorg Nvidia can be the default renderer with the same configuration. $ prime-select query nvidia $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) Xe Graphics (TGL GT2) (0x9a49) Version: 22.0.1 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.0.1 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.0.1 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 4 15:15:50 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1977648/+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 1977545] Re: xrandr: Failed to get size of gamma for output default
Ubuntu 14.04 (trusty) reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- 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/1977545 Title: xrandr: Failed to get size of gamma for output default Status in Ubuntu: Won't Fix Bug description: spectrum@04397701017:/opt/swSpectrum/bin$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.0* Display setup GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jun 3 17:50:08 2022 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9bc8] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09b4] InstallationDate: Installed on 2022-05-27 (7 days ago) InstallationMedia: VMI 14.04 - Release amd64 MachineType: Dell Inc. Vostro 3681 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic.efi.signed root=UUID=27e11871-0570-4fe3-91a8-53cd0df8d538 ro splash quiet i915.alpha_support=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2022 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.2 dmi.board.name: 0X9X1W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.8.2:bd01/13/2022:svnDellInc.:pnVostro3681:pvr:rvnDellInc.:rn0X9X1W:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 3681 dmi.sys.vendor: Dell Inc. drirc: version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Jun 3 17:29:43 2022 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1977545/+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 1977486] Re: every time i set ubuntu to sleep, everything crashes
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Package changed: gnome-shell (Ubuntu) => ubuntu -- 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/1977486 Title: every time i set ubuntu to sleep, everything crashes Status in Ubuntu: Incomplete Bug description: i set ubuntu to sleep and i find everything crashing when i wake up the laptop as if i didnot go to suspend mood and i just restarted the labtop. chrome tells me that it crahsed . i donot know what to do or where is the problem is ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 3 08:41:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-05 (28 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1977486/+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 1977643] Re: gdm crash when unlocking screen if using Nouveau driver
gdm3 is not involved in screen locking so this is likely to be a crash in either Xorg or gnome-shell. Please follow the instructions in comment #3. ** Package changed: gdm3 (Ubuntu) => ubuntu ** Summary changed: - gdm crash when unlocking screen if using Nouveau driver + Crash when unlocking screen if using Nouveau driver -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1977643 Title: Crash when unlocking screen if using Nouveau driver Status in Ubuntu: Incomplete Bug description: Randomly but frequently when trying to unlock screen, it either becomes very slow (like when typing the password, characters are reflected very slowly) or it totally freeze and crash. Also switching TTY's doesn't work and have to hard reset. This was happening for me before while using Nvidia's driver but it has been working fine, now when I switched to the Nouveau driver, it constantly happens. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 4 13:06:05 2022 InstallationDate: Installed on 2022-02-03 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago) mtime.conffile..etc.pam.d.gdm-password: 2022-02-19T02:26:10.814729 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1977643/+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 1977650] Re: gjs is running always on my system. but it has a icon at the bar. cannot exit from that
A 'gjs' process is usually caused by the Desktop Icons NG extension, although it may also be caused by other extensions. It is not necessarily a bug in the extension that owns the gjs process but more likely a bug in the dock/panel extension that is displaying the icon. Please start by removing all unsupported extensions: cd ~/.local/share/gnome-shell rm -rf extensions and then log in again. Does the problem still occur? ** Package changed: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1977650 Title: gjs is running always on my system. but it has a icon at the bar. cannot exit from that Status in Ubuntu: Incomplete Bug description: gjs is running always on my system. but it has a icon at the bar. cannot exit from that ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 17:52:11 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-09-05 (272 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-07 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1977650/+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 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
Well, as I stated above the fix is working and now VNC and RDP connections are working again. But I've tested gnome-remote-desktop under X11 and Wayland and there is a real performance problem in Wayland compared to X11 (key presseds are shown with a lag of seconds because refresh takes too much time). While you are connected to a gnome-remote-desktop session (using VNC or RDP) and only under Wayland the system log is populated several times per second with these messages that may be related to the performance problem: ... jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 14 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 106 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1933312 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 14 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 106 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:13 fpgrpi kernel: swiotlb_tbl_map_single: 82 callbacks suppressed ... These messages stops when you disconnect to gnome-remote-desktop. Please, tell me if it's necessary to open another bug for this problem or can be followed here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'.
[Desktop-packages] [Bug 1977466] Re: Memory leak
I am going to make this bug private to avoid irrelevant me-too comments from other users. ** Information type changed from Public to Private ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: gnome-shell-leak -- 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/1977466 Title: Memory leak Status in Ubuntu: Incomplete Bug description: /usr/bin/gnome-shell -> using 30% of RAM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 2 22:31:50 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-28 (339 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1977466/+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 1976567] Re: Desktop resolution was set incorrectly until I booted up the PC AFTER turning on the monitor
I suspect when this bug is occurring you are seeing a Xorg session, despite the fact this bug was created from a Wayland session. The reason being bug 1919400... Please reproduce the problem again and log in with the problem still happening. While the problem is happening, please run: journalctl -b0 > journal.txt xrandr --verbose > xrandrv.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1976567 Title: Desktop resolution was set incorrectly until I booted up the PC AFTER turning on the monitor Status in xorg-server package in Ubuntu: Incomplete Bug description: Whenever I boot up my PC, I turn on the monitor as well. When this happens, the Intel Mesa graphics loads, and my screen ends up being small with large pixelated icons. The resolution was capped at 1024x768. Only after I reboot my PC multiple times without changing the display settings did the resolution increase to 1680x1050, the correct resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 21:07:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0589] InstallationDate: Installed on 2022-05-22 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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-server/+bug/1976567/+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 1977466] Re: Memory leak
Thanks for the bug report. Please start by removing unsupported extensions: cd ~/.local/share/gnome-shell rm -rf extensions and then log in again. If the leak still occurs after that then please run: ps auxw > ps.txt and attach the resulting text file here. -- 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/1977466 Title: Memory leak Status in Ubuntu: Incomplete Bug description: /usr/bin/gnome-shell -> using 30% of RAM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 2 22:31:50 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-28 (339 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1977466/+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 1962170] Re: DEP8 failure with samba 4.15.5
** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Bug description: The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+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 1961459] Re: adsys pam issues
** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1961459 Title: adsys pam issues Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Bug description: These may not be security issues but it's possible I overlooked something; since they live in a security boundary I thought it worth reporting with a bit of hassle. If you'd rather work on this in the open, feel free to open this. pam_adsys.c update_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() -- status != 0 looks like it ought to work but I don't think that's how that API is supposed to be used pam_adsys.c pam_sm_open_session() -- gethostname() indentation is funny Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1961459/+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 1962510] Re: failing tests with new sssd, blocks python3-defaults
** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962510 Title: failing tests with new sssd, blocks python3-defaults Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Bug description: adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962510/+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 1973745] Re: adsys windows admx/adml lts only does not include 22.04
** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973745 Title: adsys windows admx/adml lts only does not include 22.04 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Due to some misunterpretation in how the launchpad API works when listing lts only, 22.04 was not included there by the admx/adml files generated by CI. Consequently, when those files are deployed on Windows AD server with LTS only templates, this one is not listed. [Test Plan] * Deploy the admx/adml generated for "LTS Only" use cases on an AD server * Open any GPO rule like changing the background * Ensure there is an "Override for 22.04" entry. [Where problems could occur] Those files are statically generated and then shipped as thus. There is no runtime exercising this. The consequence of those generated files to be invalid is that Windows AD server will not show up "Ubuntu" in its GPO template. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973745/+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 1973748] Re: Updating any gsettings key makes user dconf database unreadable
** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973748 Title: Updating any gsettings key makes user dconf database unreadable Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Changing any gsettings key in AD resulted in user databases under /etc/dconf, owned by root, with 0600 as permissions. This change was done late in the cycle after passing some permissions checkers to harden the binaries. However, in that case, the user databases needs to be readable by the users so that they can apply those values, so we need to align with ibus profile and makes them 644. [Test case] * Change a gsettings key under AD, like picture-uri one. * Login on the Ubuntu laptop connected with AD by adsys * The background should now be changed to the set value. [Where problems could occur] This code is located in the dconf policy application manager and restricted to it. The negative impact in case of a new bug will be seen by gsettings key not being applied as it is already nowdays. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973748/+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 1973751] Re: Machines or Users scripts are not executed
** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973751 Title: Machines or Users scripts are not executed Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Machine and user scripts are not executed on startup/shutdown/login/logoff. /run has been recently changed to be noexec on jammy. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mecanism has been reviewed by the security team, so we can reset them as executable. [Test case] * Setup some scripts under AD to be executed, one for machine scripts (on startup), one for user scripts (on login). Those scripts can create some temporary files under /tmp for instance. * Reboot and login on the Ubuntu laptop connected with AD by adsys, with ua attached * Check that the scripts were executed by testing that the created file under /tmp are present. [Where problems could occur] This is technically a new .mount systemd unit service which takes the same mount option than /run, but don’t set noexec. The setup is similar than qemu .mount unit for instance. Worst impact could be that the script policy manager can’t run the scripts as it is already the case today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973751/+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 1973752] Re: Fix privilege permission which can not be set to disabled
** Also affects: adsys (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973752 Title: Fix privilege permission which can not be set to disabled Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Disallowing local administrator does not work as excepted: - on some AD server, setting in the UI this key (and some other similars) to disabled, go to next GPO rule, then back to this one, AD will display the key as enabled. - on the client machine, we can see that the key has no state and nothing is forcibly allowed or disallowed. [Test case] * Install the new admx/adml with this version on the AD server. * On AD, go to disallow local administator, set it to disabled * Go to next GPO rules and then go back * The rule should still be disabled. * On an Ubuntu machine connected with AD by adsys, with ua attached, force a machine refresh with adsysctl policy update -m. * Check in adsysctl policy applied --all that the key is displayed as disabled * Confirm that no local administrator (part of the sudo group) can run "sudo". [Where problems could occur] The privilege manager and other policies impacts both Windows and client: - on Windows, this is in the admx/adml are statically generated and then shipped as thus. There is no runtime exercising this. The consequence of those generated files to be invalid is that Windows AD server will not show up "Ubuntu" in its GPO template. - on the client, the privilege manager is the main consumer of those disabled key types. The other kinds of keys are not impacted. [Additional informations] * New test cases have been added for the client part. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973752/+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 1976563] Re: All text and images in Gnome Shell are corrupted
*** This bug is a duplicate of bug 1876632 *** https://bugs.launchpad.net/bugs/1876632 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 1876632, 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. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-510 (Ubuntu) ** This bug has been marked a duplicate of bug 1876632 [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend -- 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/1976563 Title: All text and images in Gnome Shell are corrupted Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: See attached screenshot. The corrupted text and images are only appearing in the Ubuntu desktop environment (like the login screen, dock, and the bar at top of the screen). Applications like Nautilus, the Terminal app, and Chrome are not affected. Maybe an Nvidia issue? I'm going to restart my PC which will probably fix the issue. I'll edit this if the issue persists after the restart. Edit: To anyone investigating this issue, I recommend looking at some of the other issues I've reported recently. It seems like they could all be connected somehow, with Nvidia as the common thread. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-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..06.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 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 18:58:22 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.73.05, 5.15.0-33-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (39 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
