[Desktop-packages] [Bug 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio
I'm not sure what the intended configuration of these two packages is. On one (older) lunar system I find neither installed. On a fresh lunar install however I find pipewire-alsa but no pulseaudio. Neither package is seeded so it seems either of those configurations is valid. They do definitely conflict though so I recommend manually removing 'pulseaudio' and then reattempting the upgrade. ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2017196 Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire- alsa conflicts with pulseaudio] Status in pipewire package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required software appeared to have downloaded. Committing Changes operated to about 84% at which point the system crashed. It was necessary to re- initiate the upgrade procedure. This time, the upgrade proceeded to about 95% when an error notification appeared on the screen. Further upgrades were not attempted. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: pipewire-alsa (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 21 04:46:04 2023 ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64 InstallationDate: Installed on 2020-02-04 (1171 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: pipewire Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2017196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017196] [NEW] package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64
Public bug reported: Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required software appeared to have downloaded. Committing Changes operated to about 84% at which point the system crashed. It was necessary to re- initiate the upgrade procedure. This time, the upgrade proceeded to about 95% when an error notification appeared on the screen. Further upgrades were not attempted. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: pipewire-alsa (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 21 04:46:04 2023 ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64 InstallationDate: Installed on 2020-02-04 (1171 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: pipewire Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2017196 Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 Status in pipewire package in Ubuntu: New Bug description: Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required software appeared to have downloaded. Committing Changes operated to about 84% at which point the system crashed. It was necessary to re- initiate the upgrade procedure. This time, the upgrade proceeded to about 95% when an error notification appeared on the screen. Further upgrades were not attempted. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: pipewire-alsa (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 21 04:46:04 2023 ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64 InstallationDate: Installed on 2020-02-04 (1171 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: pipewire Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2017196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015873] Re: Firefox does not open when clicked -- first time
This sounds very similar to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806 -- 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/2015873 Title: Firefox does not open when clicked -- first time Status in firefox package in Ubuntu: Incomplete Bug description: When clicking Firefox starter in the side bar, the browser does not load. The cursor changes into a running action but nothing happens. Close with the drop down menu and click the starter again does open the Firefox browser. First attempt to open the browser is failing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2015873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017186] Re: No ubuntu dock after 23.04 upgrade
Please also run: dconf dump /org/gnome/shell/ > settings.txt and attach the resulting text file here. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2017186 Title: No ubuntu dock after 23.04 upgrade Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Extensions app wont activate or deactivate any extension. Only from the web pannel https://extensions.gnome.org/local/ works when enabling "Disable version validation" ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-ubuntu-dock 79ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 22:06:41 2023 InstallationDate: Installed on 2021-06-07 (682 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANG=es_DO.UTF-8 LANGUAGE=es_DO:es PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to lunar on 2023-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2017186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017186] Re: No ubuntu dock after 23.04 upgrade
Thanks for the bug report. Please try removing any local (unsupported) extensions you might have: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. Please also note that extensions not provided by Ubuntu are unlikely to support GNOME 44 yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2017186 Title: No ubuntu dock after 23.04 upgrade Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Extensions app wont activate or deactivate any extension. Only from the web pannel https://extensions.gnome.org/local/ works when enabling "Disable version validation" ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-ubuntu-dock 79ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 22:06:41 2023 InstallationDate: Installed on 2021-06-07 (682 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANG=es_DO.UTF-8 LANGUAGE=es_DO:es PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to lunar on 2023-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2017186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981163]
It's been 6 months since this bug was assigned. Perhaps it could be reassigned to someone who has the time to look at the bug and fix it? Much appreciated. (This was not a problem until T-bird > 63, I believe). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1981163 Title: [upstream] In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince Status in Mozilla Thunderbird: In Progress Status in thunderbird package in Ubuntu: Confirmed Bug description: In Thunderbird on Ubuntu Gnome, I set Evince as default program to open pdf files from Thunderbird. In received messages, and those saved on "Sent" folder, it works perfectly. But in the "Compose" window: if I add a pdf file to the message, and double-click on it to open and verify it, Thunderbird always uses Firefox to show it. In case Firefox is not installed (has been removed), I have an error message telling there is not associated application for pdf files and to go to Preferences - where Evince is already and still defined as default. It happens since many months and bug is still present in Thunderbird 102 / Ubuntu 22.10 beta. It's not the same as bug 234349 as here, it's not an URL file but directly a pdf joined in a mail. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1981163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017153] Re: cryptsetup messages overlap with the distribution logo in the plymouth splash screen
** Also affects: kubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2017153 Title: cryptsetup messages overlap with the distribution logo in the plymouth splash screen Status in kubuntu-settings package in Ubuntu: New Status in plymouth package in Ubuntu: New Bug description: I use Kubuntu and have enabled full-disk encryption using LUKS, grub cryptodisk etc. During the boot process, the plymouth splash screen is displayed and in that the cryptsetup message is rendered in such a way that it slightly overlaps with the Kubuntu logo. Please see the attached screenshot illustrating this issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth 22.02.122-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 20 21:08:15 2023 DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationDate: Installed on 2021-12-02 (504 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5530 ProcCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-20-generic root=UUID=a69dbf54-f211-4f43-9882-ee5e80fbd158 ro rootflags=subvol=@ quiet splash loglevel=3 systemd.unified_cgroup_hierarchy=0 vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-20-generic root=UUID=a69dbf54-f211-4f43-9882-ee5e80fbd158 ro rootflags=subvol=@ quiet splash loglevel=3 systemd.unified_cgroup_hierarchy=0 vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: Upgraded to lunar on 2023-04-20 (0 days ago) dmi.bios.date: 03/13/2023 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd03/13/2023:br1.31:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr:sku087D: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2017153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989477] Re: Switching to dark mode in settings does not change shell theme.
This bug is about shell elements whereas comment #12 is about app elements so please open a new bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1989477 Title: Switching to dark mode in settings does not change shell theme. Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: Changing the "Style" in the "Appearance" section of "Settings" (gnome- control-center), does not update the shell theme. When I select dark mode from settings, Libadwaita apps respond to the changes, but the shell theme and GTK3 applications do not. This has been observed on both Wayland and X11. Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10 Package Version: 1:43~rc-1ubuntu2 What I Expected: Changing the style in settings will affect all the apps that support changing light/dark mode. The shell theme will also respond to the change. What happened instead: Only libadwaita apps are affected by changing the style in Settings. GTK3 apps and the shell theme do not change. When changing to dark mode via the quick settings menu, all the apps change their color scheme appropriately. However, there is not a smooth transition when switching the style from quick settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016007] Re: gnome-shell crashed with SIGSEGV in shell_global_get_display() from update_focus_app() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_val
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-gnome-shell-44.1 fixed-upstream -- 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/2016007 Title: gnome-shell crashed with SIGSEGV in shell_global_get_display() from update_focus_app() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/746bcf4f26f269a08ef5a7b5748fcf8e16bb7a51 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2016007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017186] [NEW] No ubuntu dock after 23.04 upgrade
Public bug reported: Extensions app wont activate or deactivate any extension. Only from the web pannel https://extensions.gnome.org/local/ works when enabling "Disable version validation" ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-ubuntu-dock 79ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 22:06:41 2023 InstallationDate: Installed on 2021-06-07 (682 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANG=es_DO.UTF-8 LANGUAGE=es_DO:es PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to lunar on 2023-04-20 (0 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2017186 Title: No ubuntu dock after 23.04 upgrade Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Extensions app wont activate or deactivate any extension. Only from the web pannel https://extensions.gnome.org/local/ works when enabling "Disable version validation" ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-ubuntu-dock 79ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 22:06:41 2023 InstallationDate: Installed on 2021-06-07 (682 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANG=es_DO.UTF-8 LANGUAGE=es_DO:es PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to lunar on 2023-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2017186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989477] Re: Switching to dark mode in settings does not change shell theme.
Seems like it might only have been partially fixed. Is anyone else getting the issue where when opening a “save as” window from a browser (firefox/chrome) in dark mode, the window opens in light mode? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1989477 Title: Switching to dark mode in settings does not change shell theme. Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: Changing the "Style" in the "Appearance" section of "Settings" (gnome- control-center), does not update the shell theme. When I select dark mode from settings, Libadwaita apps respond to the changes, but the shell theme and GTK3 applications do not. This has been observed on both Wayland and X11. Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10 Package Version: 1:43~rc-1ubuntu2 What I Expected: Changing the style in settings will affect all the apps that support changing light/dark mode. The shell theme will also respond to the change. What happened instead: Only libadwaita apps are affected by changing the style in Settings. GTK3 apps and the shell theme do not change. When changing to dark mode via the quick settings menu, all the apps change their color scheme appropriately. However, there is not a smooth transition when switching the style from quick settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016435] Re: amdgpu driver randomly resets
This just happened while I was watching Twitch, had Amazon open, and just opened Disney+ And it happened multiple times in multiple minutes ** Attachment added: "journal_230420.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2016435/+attachment/5665959/+files/journal_230420.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2016435 Title: amdgpu driver randomly resets Status in mesa package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: amdgpu tends to randomly reset. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xserver-xorg-video-amdgpu 23.0.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sun Apr 16 18:04:34 2023 DistUpgraded: 2023-04-01 18:21:47,742 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 6.2.0-19-generic, x86_64: installed openrazer-driver/3.4.0, 6.2.0-20-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-19-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1849:5212] NVIDIA Corporation GA104 [GeForce RTX 3060 Ti] [10de:2486] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GA104 [GeForce RTX 3060 Ti] [3842:3663] InstallationDate: Installed on 2022-01-14 (457 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to lunar on 2023-04-01 (14 days ago) dmi.bios.date: 10/01/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F3c dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF3c:bd10/01/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE DistUpgraded: 2023-04-01 18:21:47,742 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroRelease: Ubuntu 23.04 DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 6.2.0-19-generic, x86_64: installed openrazer-driver/3.4.0, 6.2.0-20-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-19-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, I
[Desktop-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_obje
@Andreas Replying about the accountsservice part, we got some issues resolved there before the release but the bug here is a different problem then the one addressed in accountsservice 22.08.8-1ubuntu7. The issue is in the indicator codebase and the right fix is what has been uploaded for (ayatana-)indicator-messages recently but Marco also worked on making accountsservice more robust to such coding errors. The fix has been commited upstream now but not uploaded to Ubuntu yet (we tend to use 'fix commited' on desktop component for things which have a fix available in the upstream vcs which can be slightly confusing) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in ayatana-indicator-messages package in Ubuntu: Triaged Status in indicator-messages package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016708] Re: Characters search through GNOME Shell is broken 😿
This is in lunar-proposed at the moment. Please proceed with SRU verification. I don't think the tooling treats lunar as a stable release just yet, that's why there is no automated comment here. I'll add the tags. ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2016708 Title: Characters search through GNOME Shell is broken 😿 Status in gnome-characters package in Ubuntu: Fix Committed Bug description: [ Impact ] Searching for characters in gnome shell does not bring any result [ Test Case ] - Having gnome-characters installed - Open the overview (hit super), search for "pizza" - The "pizza slice" character should show in the search results: 🍕 [ Regression potential ] The shell search provider is never stopped once done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/2016708/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017173] Re: Ubuntu desktop settings unavailable
Some more details: $ gnome-extensions show ubuntu-d...@ubuntu.com ubuntu-d...@ubuntu.com Name: Ubuntu Dock Description: A dock for the Gnome Shell, default Ubuntu experience. This extension is a modified version of Dash To Dock with different defaults. Dash To Dock can be installed to replace it and give more (but unsupported) configuration options. Path: /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com URL: https://micheleg.github.io/dash-to-dock/ Original author: mic...@gmail.com Version: 79 State: UNKNOWN whereas: $ gnome-extensions show tiling-assist...@ubuntu.com Extension “tiling-assist...@ubuntu.com” doesn’t exist -- 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/2017173 Title: Ubuntu desktop settings unavailable Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I have just upgraded from 22.10 to 23.04. Now, in "Settings", the "Ubuntu Desktop" option shows: "No ubuntu settings found. Oops, something has gone wrong. Please report a bug in Launchpad." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2017173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017173] Re: Ubuntu desktop settings unavailable
When starting `gnome-control-center` from terminal I see: ``` 21:54:25.3724 cc-ubuntu-panel[14629]: WARNING: Extension d...@rastersoft.com is not available or invalid (state 99) 21:54:25.3726 cc-ubuntu-panel[14629]: WARNING: Extension ubuntu-d...@ubuntu.com is not available or invalid (state 99) 21:54:25.3726 cc-ubuntu-panel[14629]: WARNING: Extension tiling-assist...@ubuntu.com is not available or invalid (state 99) ``` When I open GNOME Extensions app I see that those are disabled. Could it be that those did not upgrade for some reason? How can I trigger manual re-installation of these three extensions? Could the error message in `Ubuntu Desktop` panel be more informative? -- 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/2017173 Title: Ubuntu desktop settings unavailable Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I have just upgraded from 22.10 to 23.04. Now, in "Settings", the "Ubuntu Desktop" option shows: "No ubuntu settings found. Oops, something has gone wrong. Please report a bug in Launchpad." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2017173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_obje
Summarizing this bug from an SRU POV We need https://launchpad.net/ubuntu/+source/indicator- messages/13.10.1+18.10.20180918-0ubuntu5 in lunar. Previous upload of 0ubuntu4 failed to migrate/build (see comment #24), and I guess 0ubuntu5 arrived too late for the release. We also have https://launchpad.net/ubuntu/lunar/+upload/31007427/+files/ayatana- indicator-messages_22.9.0-1ubuntu1_source.changes in lunar-unapproved I'm sensing both need to land in lunar-proposed at the same time for this bug to be fixed in lunar? And what about accountsservice 22.08.8-1ubuntu7, which is in lunar already, but its task in this bug is "fix committed"? I saw there was some back and forth with it, and it sounded it would have the fix for this bug, but then didn't. Is it still related to this bug, or can we remove/delete its task? Or move it to "fix released"? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in ayatana-indicator-messages package in Ubuntu: Triaged Status in indicator-messages package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017173] Re: Ubuntu desktop settings unavailable
** Tags added: lunar ** Package changed: ubuntu => gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2017173 Title: Ubuntu desktop settings unavailable Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I have just upgraded from 22.10 to 23.04. Now, in "Settings", the "Ubuntu Desktop" option shows: "No ubuntu settings found. Oops, something has gone wrong. Please report a bug in Launchpad." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2017173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016007] Re: gnome-shell crashed with SIGSEGV in shell_global_get_display() from update_focus_app() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_val
** Changed in: gnome-shell Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2016007 Title: gnome-shell crashed with SIGSEGV in shell_global_get_display() from update_focus_app() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/746bcf4f26f269a08ef5a7b5748fcf8e16bb7a51 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2016007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976] Re: firefox black window on wayland
@Andreas: I just wrote this on #ubuntu-desktop: https://irclogs.ubuntu.com/2023/04/20/%23ubuntu-desktop.html#t17:57 -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Confirmed Status in Mutter: New Status in Release Notes for Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976] Re: firefox black window on wayland
Hi Gunnar and others, with Lunar just released, I'm going over the lunar unapproved queue to pick out packages that should now become SRUs for lunar. Could someone please add the SRU template to this bug's description, and fill it out? Since the package is in unapproved, and not proposed, I'm switching the bug task back to "in progress". Regarding the patch, I see there is still a bit of back and forth in the upstream merge request[1]. Can we get that stabilized, hopefully even merged, before committing to an SRU? 1. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 ** Changed in: mutter (Ubuntu) Status: Fix Committed => In Progress -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Confirmed Status in Mutter: New Status in Release Notes for Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
Adding the language-selector package, since many fontconfig files affecting Chinese rendering are provided by language-selector-common. ** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: New Status in fontconfig package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
One thought is to ask why we still install the fonts-arphic-uming package when installing Chinese (Simplified as well as Traditional). Probably it is of historical reasons from the time before Noto existed. But let's consider that to be a matter of its own. Even if AR PL UMing is available, Noto Sans CJK should have higher precedence. With a Chinese locale, it's not possible to have fontconfig give Noto Sans CJK higher precedence that it currently has: $ LC_CTYPE=zh_CN.UTF-8 fc-match NotoSansCJK-Regular.ttc: "Noto Sans CJK SC" "Regular" But also with non-Chinese locales, Noto Sans CJK ought to be preferred over AR PL UMing: $ LC_CTYPE=en_US.UTF-8 fc-match -a | grep -iE 'uming|cjk' | head -38 NotoSansCJK-Regular.ttc: "Noto Sans CJK JP" "Regular" NotoSansCJK-Medium.ttc: "Noto Sans CJK JP" "Medium" NotoSansCJK-DemiLight.ttc: "Noto Sans CJK JP" "DemiLight" NotoSansCJK-Light.ttc: "Noto Sans CJK JP" "Light" NotoSansCJK-Thin.ttc: "Noto Sans CJK JP" "Thin" NotoSansCJK-Bold.ttc: "Noto Sans CJK JP" "Bold" NotoSansCJK-Black.ttc: "Noto Sans CJK JP" "Black" NotoSansCJK-Regular.ttc: "Noto Sans CJK KR" "Regular" NotoSansCJK-Medium.ttc: "Noto Sans CJK KR" "Medium" NotoSansCJK-DemiLight.ttc: "Noto Sans CJK KR" "DemiLight" NotoSansCJK-Light.ttc: "Noto Sans CJK KR" "Light" NotoSansCJK-Thin.ttc: "Noto Sans CJK KR" "Thin" NotoSansCJK-Bold.ttc: "Noto Sans CJK KR" "Bold" NotoSansCJK-Black.ttc: "Noto Sans CJK KR" "Black" NotoSansCJK-Regular.ttc: "Noto Sans CJK SC" "Regular" NotoSansCJK-Medium.ttc: "Noto Sans CJK SC" "Medium" NotoSansCJK-DemiLight.ttc: "Noto Sans CJK SC" "DemiLight" NotoSansCJK-Light.ttc: "Noto Sans CJK SC" "Light" NotoSansCJK-Thin.ttc: "Noto Sans CJK SC" "Thin" NotoSansCJK-Bold.ttc: "Noto Sans CJK SC" "Bold" NotoSansCJK-Black.ttc: "Noto Sans CJK SC" "Black" NotoSansCJK-Regular.ttc: "Noto Sans CJK TC" "Regular" NotoSansCJK-Medium.ttc: "Noto Sans CJK TC" "Medium" NotoSansCJK-DemiLight.ttc: "Noto Sans CJK TC" "DemiLight" NotoSansCJK-Light.ttc: "Noto Sans CJK TC" "Light" NotoSansCJK-Thin.ttc: "Noto Sans CJK TC" "Thin" NotoSansCJK-Bold.ttc: "Noto Sans CJK TC" "Bold" NotoSansCJK-Black.ttc: "Noto Sans CJK TC" "Black" NotoSansCJK-Regular.ttc: "Noto Sans CJK HK" "Regular" NotoSansCJK-Medium.ttc: "Noto Sans CJK HK" "Medium" NotoSansCJK-DemiLight.ttc: "Noto Sans CJK HK" "DemiLight" NotoSansCJK-Light.ttc: "Noto Sans CJK HK" "Light" NotoSansCJK-Thin.ttc: "Noto Sans CJK HK" "Thin" NotoSansCJK-Bold.ttc: "Noto Sans CJK HK" "Bold" NotoSansCJK-Black.ttc: "Noto Sans CJK HK" "Black" uming.ttc: "AR PL UMing CN" "Light" uming.ttc: "AR PL UMing HK" "Light" uming.ttc: "AR PL UMing TW" "Light" But apparently the snap applications don't query fontconfig dynamically about the default font. Instead a default font seems to be established during installation, based on to me unknown criteria, and that default font does not change. We need help from the snap folks to sort this out, I think. Another thought is that many available fontconfig files were moved from /etc/fonts/conf.avail to /usr/share/fontconfig/conf.avail during the lunar development cycle. Can this possibly have created a dissonance between the snaps and the system in this respect? If I understand it correctly, the snaps honor the symlinks in /etc/fonts/conf.d: $ cat ~/snap/firefox/current/.config/fontconfig/fonts.conf /snap/firefox/2517/gnome-platform/usr/share/fonts /usr/local/share//fonts /usr/share//fonts /etc/fonts/conf.d conf.d fontconfig /var/snap/firefox/common/fontconfig But many of those symlinks on the system now point to /usr instead of /etc. One reason why I suspect that this has something to do with it is that /etc/fonts/conf.avail/65-fonts-arphic-uming.conf — which prefers AR PL UMing —is one of the files which was *not* moved to /usr. ** Changed in: fontconfig (Ubuntu) Importance: Undecided => High ** Changed in: fontconfig (Ubuntu) Status: Incomplete => New ** Also affects: snappy Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: New Status in fontconfig package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubunt
[Desktop-packages] [Bug 2017153] [NEW] cryptsetup messages overlap with the distribution logo in the plymouth splash screen
Public bug reported: I use Kubuntu and have enabled full-disk encryption using LUKS, grub cryptodisk etc. During the boot process, the plymouth splash screen is displayed and in that the cryptsetup message is rendered in such a way that it slightly overlaps with the Kubuntu logo. Please see the attached screenshot illustrating this issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth 22.02.122-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 20 21:08:15 2023 DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationDate: Installed on 2021-12-02 (504 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5530 ProcCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-20-generic root=UUID=a69dbf54-f211-4f43-9882-ee5e80fbd158 ro rootflags=subvol=@ quiet splash loglevel=3 systemd.unified_cgroup_hierarchy=0 vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-20-generic root=UUID=a69dbf54-f211-4f43-9882-ee5e80fbd158 ro rootflags=subvol=@ quiet splash loglevel=3 systemd.unified_cgroup_hierarchy=0 vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: Upgraded to lunar on 2023-04-20 (0 days ago) dmi.bios.date: 03/13/2023 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd03/13/2023:br1.31:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr:sku087D: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "plymouth.jpeg" https://bugs.launchpad.net/bugs/2017153/+attachment/5665724/+files/plymouth.jpeg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2017153 Title: cryptsetup messages overlap with the distribution logo in the plymouth splash screen Status in plymouth package in Ubuntu: New Bug description: I use Kubuntu and have enabled full-disk encryption using LUKS, grub cryptodisk etc. During the boot process, the plymouth splash screen is displayed and in that the cryptsetup message is rendered in such a way that it slightly overlaps with the Kubuntu logo. Please see the attached screenshot illustrating this issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth 22.02.122-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 20 21:08:15 2023 DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationDate: Installed on 2021-12-02 (504 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5530 ProcCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-20-generic root=UUID=a69dbf54-f211-4f43-9882-ee5e80fbd158 ro rootflags=subvol=@ quiet splash loglevel=3 systemd.unified_cgroup_hierarchy=0 vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-20-generic root=UUID=a69dbf54-f211-4f43-9882-ee5e80fbd158 ro rootflags=subvol=@ quiet splash loglevel=3 systemd.unified_cgroup_hierarchy=0 vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: Upgraded to lunar on 2023-04-2
Re: [Desktop-packages] [Bug 1943752] Re: cheese does not work with laptop webcam in Ubuntu 21.10+
Fred, Have you looked at this? https://askubuntu.com/questions/348838/how-to-check-available-webcams-from-the-command-line On Thu, Apr 20, 2023 at 10:18 AM Keith Clemmons wrote: > Fred, > I noticed that there is a BIOS update for you computer > https://support.hp.com/sg-en/drivers/selfservice/hp-elite-dragonfly-13.5-inch-g3-notebook-pc/2101012761/model/2101012775 > have you updated the BIOS? > Have you looked at the following links? > https://wiki.archlinux.org/title/Webcam_setup > https://en.opensuse.org/HCL:Web_cameras > https://www.osradar.com/activate-the-webcam-using-the-terminal-linux/ > This Ubuntu documentation is rather old. > https://help.ubuntu.com/community/Webcam > https://help.ubuntu.com/community/Webcam/Troubleshooting > > > On Thu, Apr 20, 2023 at 4:55 AM Fred J <1943...@bugs.launchpad.net> wrote: > >> Hi, >> Didn't work for me, elite dragonfly g3 4J044AV >> Tried other distro and cam didn't work either. >> Stuck with pc without webcam. >> --F >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1943752 >> >> Title: >> cheese does not work with laptop webcam in Ubuntu 21.10+ >> >> Status in cheese package in Ubuntu: >> Confirmed >> >> Bug description: >> Ubuntu 21.10 from live usb on a HP 840 G3 laptop >> 1.Ubuntu Impish Indri (development branch) >> 2.cheese version installed: 3.38.0-4, candidate: 3.38.0-4 >> version table:***3.38.0-4 500 >> 3.cheese should display an image from laptop camera after being opened. >> 4.The error has reproduced by me on this hardware at least 4 times. >> When opening the cheese app no image is displayed until closing and >> reopening the app at least 3 times. The cheese app works as expected in >> both Ubuntu 18.04 and Ubuntu 20.04. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 21.10 >> Package: cheese 3.38.0-4 >> ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 >> Uname: Linux 5.13.0-14-generic x86_64 >> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair >> ApportVersion: 2.20.11-0ubuntu68 >> Architecture: amd64 >> CasperMD5CheckResult: pass >> CasperVersion: 1.465 >> CurrentDesktop: ubuntu:GNOME >> Date: Wed Sep 15 17:10:23 2021 >> LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915) >> MachineType: HP HP EliteBook 840 G3 >> ProcEnviron: >>TERM=xterm-256color >>PATH=(custom, no user) >>XDG_RUNTIME_DIR= >>LANG=en_US.UTF-8 >>SHELL=/bin/bash >> RelatedPackageVersions: >>cheese3.38.0-4 >>cheese-common 3.38.0-4 >> SourcePackage: linux >> UpgradeStatus: No upgrade log present (probably fresh install) >> dmi.bios.date: 04/20/2021 >> dmi.bios.release: 1.52 >> dmi.bios.vendor: HP >> dmi.bios.version: N75 Ver. 01.52 >> dmi.board.name: 8079 >> dmi.board.vendor: HP >> dmi.board.version: KBC Version 85.79 >> dmi.chassis.type: 10 >> dmi.chassis.vendor: HP >> dmi.ec.firmware.release: 133.121 >> dmi.modalias: >> dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr: >> dmi.product.family: 103C_5336AN HP EliteBook >> dmi.product.name: HP EliteBook 840 G3 >> dmi.product.sku: 2FZ00UP#ABA >> dmi.sys.vendor: HP >> lsusb: >>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >>Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD >> Camera >>Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 >> Fingerprint Reader >>Bus 001 Device 002: ID 154b:0054 PNY USB 2.0 FD >>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> --- >> ProblemType: Bug >> ApportVersion: 2.20.11-0ubuntu68 >> Architecture: amd64 >> AudioDevicesInUse: >>USERPID ACCESS COMMAND >>/dev/snd/controlC0: ubuntu 5074 F pulseaudio >> CasperMD5CheckResult: pass >> CasperVersion: 1.465 >> CurrentDesktop: ubuntu:GNOME >> DistroRelease: Ubuntu 21.10 >> LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915) >> Lsusb: >>Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra >>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >>Bus 001 Device 003: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD >> Camera >>Bus 001 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 >> Fingerprint Reader >>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >> MachineType: HP HP EliteBook 840 G3 >> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair >> Package: linux (not installed) >> ProcEnviron: >>TERM=xterm-256color >>PATH=(custom, no user) >>XDG_RUNTIME_DIR= >>LANG=en_US.UTF-8 >>SHELL=/bin/bash >> ProcFB: 0 i915drmfb >> ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz >> file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- >> ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 >> Re
Re: [Desktop-packages] [Bug 1943752] Re: cheese does not work with laptop webcam in Ubuntu 21.10+
Fred, I noticed that there is a BIOS update for you computer https://support.hp.com/sg-en/drivers/selfservice/hp-elite-dragonfly-13.5-inch-g3-notebook-pc/2101012761/model/2101012775 have you updated the BIOS? Have you looked at the following links? https://wiki.archlinux.org/title/Webcam_setup https://en.opensuse.org/HCL:Web_cameras https://www.osradar.com/activate-the-webcam-using-the-terminal-linux/ This Ubuntu documentation is rather old. https://help.ubuntu.com/community/Webcam https://help.ubuntu.com/community/Webcam/Troubleshooting On Thu, Apr 20, 2023 at 4:55 AM Fred J <1943...@bugs.launchpad.net> wrote: > Hi, > Didn't work for me, elite dragonfly g3 4J044AV > Tried other distro and cam didn't work either. > Stuck with pc without webcam. > --F > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1943752 > > Title: > cheese does not work with laptop webcam in Ubuntu 21.10+ > > Status in cheese package in Ubuntu: > Confirmed > > Bug description: > Ubuntu 21.10 from live usb on a HP 840 G3 laptop > 1.Ubuntu Impish Indri (development branch) > 2.cheese version installed: 3.38.0-4, candidate: 3.38.0-4 > version table:***3.38.0-4 500 > 3.cheese should display an image from laptop camera after being opened. > 4.The error has reproduced by me on this hardware at least 4 times. > When opening the cheese app no image is displayed until closing and > reopening the app at least 3 times. The cheese app works as expected in > both Ubuntu 18.04 and Ubuntu 20.04. > > ProblemType: Bug > DistroRelease: Ubuntu 21.10 > Package: cheese 3.38.0-4 > ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 > Uname: Linux 5.13.0-14-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu68 > Architecture: amd64 > CasperMD5CheckResult: pass > CasperVersion: 1.465 > CurrentDesktop: ubuntu:GNOME > Date: Wed Sep 15 17:10:23 2021 > LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915) > MachineType: HP HP EliteBook 840 G3 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > RelatedPackageVersions: >cheese3.38.0-4 >cheese-common 3.38.0-4 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/20/2021 > dmi.bios.release: 1.52 > dmi.bios.vendor: HP > dmi.bios.version: N75 Ver. 01.52 > dmi.board.name: 8079 > dmi.board.vendor: HP > dmi.board.version: KBC Version 85.79 > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.ec.firmware.release: 133.121 > dmi.modalias: > dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr: > dmi.product.family: 103C_5336AN HP EliteBook > dmi.product.name: HP EliteBook 840 G3 > dmi.product.sku: 2FZ00UP#ABA > dmi.sys.vendor: HP > lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD > Camera >Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 > Fingerprint Reader >Bus 001 Device 002: ID 154b:0054 PNY USB 2.0 FD >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu68 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: ubuntu 5074 F pulseaudio > CasperMD5CheckResult: pass > CasperVersion: 1.465 > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 21.10 > LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915) > Lsusb: >Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD > Camera >Bus 001 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 > Fingerprint Reader >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: HP HP EliteBook 840 G3 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > Package: linux (not installed) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz > file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- > ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 > RelatedPackageVersions: >linux-restricted-modules-5.13.0-14-generic N/A >linux-backports-modules-5.13.0-14-generic N/A >linux-firmware 1.199 > RfKill: >0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > Tags: impish > Uname: Linux 5.13.0-14-generic x8
[Desktop-packages] [Bug 2017076] Re: default Chinese font is ugly
@Gunnar Hjalmarsson: I have attached the screenshot at https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/comments/2 + Both Firefox and snap-store are displayed with UMing + The webpage in Firefox is displayed with UMing + Non-snap applications uses Noto ** Summary changed: - default Chinese font is ugly + default Chinese font in snap apps is ugly -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in fontconfig package in Ubuntu: Incomplete Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font is ugly
@Shengjing Zhu: Can you confirm that it's only in snap applications you see UMing instead of Noto? Btw, is it limited to Snap Store, or is the FF snap affected as well? Also: Is Noto used as expected - when browsing web sites with Chinese contents - in the desktop itself, e.g. Settings ** Changed in: fontconfig (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font is ugly Status in fontconfig package in Ubuntu: Incomplete Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016708] Re: Characters search through GNOME Shell is broken 😿
I reviewed this SRU and it's ok to be accepted into lunar-proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2016708 Title: Characters search through GNOME Shell is broken 😿 Status in gnome-characters package in Ubuntu: Fix Committed Bug description: [ Impact ] Searching for characters in gnome shell does not bring any result [ Test Case ] - Having gnome-characters installed - Open the overview (hit super), search for "pizza" - The "pizza slice" character should show in the search results: 🍕 [ Regression potential ] The shell search provider is never stopped once done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/2016708/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017142] [NEW] [jammy] VA-API doesn't work on DCN 3.1.4
Public bug reported: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: originate-from-2016915 ** Tags added: originate-from-2016915 ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Bug description: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Description changed: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel + + Workaround + -- + You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Summary changed: - Failed to install bcmwl wireless driver during the install + b43 driver conflicts with bcmwl driver for some Broadcom devices -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016972] Re: Chromium snap does not support Intel Raptor Lake (13th gen)
** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- 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/2016972 Title: Chromium snap does not support Intel Raptor Lake (13th gen) Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The Chromium snap does not support Intel Raptor Lake (13th gen). RPL support was added in Mesa version 22.2.0 and our snaps contain: • /snap/gnome-3-38-2004: Mesa version 21.2.6 • /snap/gnome-42-2204: Mesa version 22.2.5 So the way forward is to get the chromium snap to use gnome-42-2204 (right now Chromium uses 3-38-2004). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2016972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016987] Re: login screen not translated from English when doing no network Non-english install
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/2016987 Title: login screen not translated from English when doing no network Non- english install Status in ubuntu-desktop-installer: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Installing a non-english version of ubuntu with no network results in the login screen displaying words like 'password' in english, and the error message when inputting wrong password in english, and the 'users' button also in english. The clock however, is in the desired language, as is everything after logging in. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-desktop-installer (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 11:44:12 2023 InstallationDate: Installed on 2023-04-19 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=sv_SE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: ubuntu-desktop-installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2016987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016987] Re: login screen not translated from English when doing no network Non-english install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (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/2016987 Title: login screen not translated from English when doing no network Non- english install Status in ubuntu-desktop-installer: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Installing a non-english version of ubuntu with no network results in the login screen displaying words like 'password' in english, and the error message when inputting wrong password in english, and the 'users' button also in english. The clock however, is in the desired language, as is everything after logging in. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-desktop-installer (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 11:44:12 2023 InstallationDate: Installed on 2023-04-19 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=sv_SE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: ubuntu-desktop-installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2016987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font is ugly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font is ugly Status in fontconfig package in Ubuntu: Confirmed Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Thanks for testing, that's good news. CBCM is disabled since the build is not Chrome branded; That diagnostic message is expected. -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119 (772095164c7d5d4e73160f858ef
[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed
See also bug 2017137 -- 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/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed Status in mutter package in Ubuntu: Triaged Bug description: On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017137] Re: Xorg sessions on Intel GPUs stutter noticeably in 23.04
Probably related to bug 2017097 -- 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/2017137 Title: Xorg sessions on Intel GPUs stutter noticeably in 23.04 Status in mutter package in Ubuntu: In Progress Bug description: Xorg sessions on Intel GPUs stutter noticeably in 23.04 Seems like a combination of: * over-aggressive latency optimizations in the latest version of triple buffering; and * gnome-shell 44 being slightly less efficient at some operations like scrolling the app grid. Workaround: Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017137] [NEW] Xorg sessions on Intel GPUs stutter noticeably in 23.04
Public bug reported: Xorg sessions on Intel GPUs stutter noticeably in 23.04 Seems like a combination of: * over-aggressive latency optimizations in the latest version of triple buffering; and * gnome-shell 44 being slightly less efficient at some operations like scrolling the app grid. Workaround: Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always ** Affects: mutter (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: lunar performance regression-release triple-buffering -- 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/2017137 Title: Xorg sessions on Intel GPUs stutter noticeably in 23.04 Status in mutter package in Ubuntu: In Progress Bug description: Xorg sessions on Intel GPUs stutter noticeably in 23.04 Seems like a combination of: * over-aggressive latency optimizations in the latest version of triple buffering; and * gnome-shell 44 being slightly less efficient at some operations like scrolling the app grid. Workaround: Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed
Think I found it. The new version of triple buffering in mutter 44.0 is too aggressive at scaling back to double buffering. So that's why 22.04 and 22.10 felt faster on Pi than 23.04 does right now. The workaround is to add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always ** Tags added: triple-buffering ** Tags added: regression-release ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** No longer affects: linux-raspi (Ubuntu) ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => Triaged -- 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/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed Status in mutter package in Ubuntu: Triaged Bug description: On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004021] Re: Moving video position /scrubbing in Totem (Videos) causes video to freeze (but not audio)
Issue is pseudo-sporadic. On the desktop, it usually freezes the moment I pick a different time in the video. On my laptop I at first had thought it didn't suffer from it, but after selecting 10 or so video positions, it locked the video. -- 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/2004021 Title: Moving video position /scrubbing in Totem (Videos) causes video to freeze (but not audio) Status in GStreamer: New Status in Totem: Fix Released Status in gstreamer package in Ubuntu: Confirmed Status in pitivi package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: When playing videos in 22.04, moving the position will often cause the video to stop. The audio will work as expected. I found mention of this behavior here as well: https://gitlab.gnome.org/GNOME/totem/-/issues/526 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/2004021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004021] Re: Moving video position /scrubbing in Totem (Videos) causes video to freeze (but not audio)
I'm experiencing this so far on a Ryzen 5600X with a Geforce RTX 2060, and a laptop running Intel integrated graphics on an i7-7600U. Issue persists regardless of whether 'gstreamer1.0-vaapi' is installed or not. I removed it and performed a full reboot to ensure the library wasn't loaded or locked in use. -- 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/2004021 Title: Moving video position /scrubbing in Totem (Videos) causes video to freeze (but not audio) Status in GStreamer: New Status in Totem: Fix Released Status in gstreamer package in Ubuntu: Confirmed Status in pitivi package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: When playing videos in 22.04, moving the position will often cause the video to stop. The audio will work as expected. I found mention of this behavior here as well: https://gitlab.gnome.org/GNOME/totem/-/issues/526 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/2004021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
I tried with the edge version and the rendering looks ok now, still some error messages: ~$ chromium-browser & [1] 634220 Gtk-Message: 13:45:31.618: Failed to load module "appmenu-gtk-module" [634220:634220:0420/134531.890979:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled. /usr/share/libdrm/amdgpu.ids: No such file or directory amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description. If they do, bad things may happen! [634220:634497:0420/134535.783796:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration. -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago)
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Any change the edge channel (in which we have now more up to date libraries) works for you? sudo snap refresh --edge chromium -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119 (772095164c7d5d4e73160f858efed3b
[Desktop-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
I think we all understand the direction here, Jeremy. You don't care about non-paying users. I'm not sure what being an Ubuntu Member means any more but what the point if part of that isn't speaking out when there's a problem, and I have to say that removing freedoms from users is about as big a problem as it gets for FOSS, especially when the leverage is commercial gain. What situation or mechanism are we imagining where somebody on an ubuntu-minimal base can't apt install ubuntu-advantage-tools if they want ubuntu-advantage-tools? I've no problem with it being bundled in, an installer question, but as soon as you say "oh you can't get rid of that", you're not compliant to me. You're telling me what I can and can't do with my installation, and for no good reason. I'm writing this now because I've had pushback from client netadmins demanding to know why these installations are individually phoning home on a regular basis. Yes I have sensitive clients, they do sensitive work. So now I have a choice, I either have to hack around your work to botch it and hope that an update doesn't fix it, or we can't use Ubuntu. -- 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/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu Lunar) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: Confirmed Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Confirmed Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Confirmed Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Confirmed Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Confirmed Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Confirmed Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 Focal requires four additional patches to solve
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu Kinetic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: Confirmed Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Confirmed Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Confirmed Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Confirmed Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Confirmed Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Confirmed Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 Focal requires four additional patches to sol
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: Confirmed Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Confirmed Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Confirmed Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Confirmed Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Confirmed Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Confirmed Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 Focal requires four additional patches to solve
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: Confirmed Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Confirmed Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Confirmed Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Confirmed Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Confirmed Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Confirmed Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 Focal requires four additional patches to solve
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: Confirmed Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Confirmed Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Confirmed Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Confirmed Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Confirmed Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Confirmed Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 Focal requires four additional patches to solv
[Desktop-packages] [Bug 1943752] Re: cheese does not work with laptop webcam in Ubuntu 21.10+
Hi, Didn't work for me, elite dragonfly g3 4J044AV Tried other distro and cam didn't work either. Stuck with pc without webcam. --F -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1943752 Title: cheese does not work with laptop webcam in Ubuntu 21.10+ Status in cheese package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 from live usb on a HP 840 G3 laptop 1.Ubuntu Impish Indri (development branch) 2.cheese version installed: 3.38.0-4, candidate: 3.38.0-4 version table:***3.38.0-4 500 3.cheese should display an image from laptop camera after being opened. 4.The error has reproduced by me on this hardware at least 4 times. When opening the cheese app no image is displayed until closing and reopening the app at least 3 times. The cheese app works as expected in both Ubuntu 18.04 and Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: cheese 3.38.0-4 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 15 17:10:23 2021 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915) MachineType: HP HP EliteBook 840 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.52 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.52 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.79 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.121 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: 2FZ00UP#ABA dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 002: ID 154b:0054 PNY USB 2.0 FD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 5074 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 840 G3 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 RelatedPackageVersions: linux-restricted-modules-5.13.0-14-generic N/A linux-backports-modules-5.13.0-14-generic N/A linux-firmware 1.199 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.52 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.52 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.79 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.121 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: 2FZ00UP#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad
[Desktop-packages] [Bug 2017120] [NEW] Sound/audio related problems option fails
Public bug reported: 1. ubuntu-bug 2. Sound/audio related problems Then you get a dialog: "PulseAudio seems to have crashed. Do you with to report a bug?" ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bdrung 1233 F wireplumber /dev/snd/seq:bdrung 1230 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 11:35:05 2023 InstallationDate: Installed on 2023-04-06 (13 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.0-debian-1.16.0-4 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-4:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.0 dmi.sys.vendor: QEMU ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Description changed: + I tried to reproduce bug #2016712. + 1. ubuntu-bug 2. Sound/audio related problems ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: bdrung 1233 F wireplumber - /dev/snd/seq:bdrung 1230 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC0: bdrung 1233 F wireplumber + /dev/snd/seq:bdrung 1230 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 11:35:05 2023 InstallationDate: Installed on 2023-04-06 (13 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.0-debian-1.16.0-4 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-4:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.0 dmi.sys.vendor: QEMU ** Description changed: - I tried to reproduce bug #2016712. - 1. ubuntu-bug 2. Sound/audio related problems + + Then you get a dialog: "PulseAudio seems to have crashed. Do you with to + report a bug?" ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bdrung 1233 F wireplumber /dev/snd/seq:bdrung 1230 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 11:35:05 2023 InstallationDate: Installed on 2023-04-06 (13 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.0-debian-1.16.0-4 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-4:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.0 dmi.sys.vendor: QEMU -- 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/2017120 Title: Sound/audio related problems option fails Status in pulse
[Desktop-packages] [Bug 2017090] Re: [raspi] glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS
The problem has gone away and direct scanout is working. Now I get 60 FPS fullscreen. I can only imagine direct scanout wasn't being used for some reason because if I disable that then I can synthesise this bug again. But under those circumstances it's really bug 2017097. ** Changed in: glmark2 (Ubuntu) Status: New => Incomplete ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017090 Title: [raspi] glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS Status in glmark2 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS in the terminal. Doesn't seem to happen in windowed mode. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: glmark2-wayland 2021.02-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:10:16 2023 ImageMediaBuild: 20230417 SourcePackage: glmark2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glmark2/+bug/2017090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed
To get FPS in the system journal set environment: CLUTTER_SHOW_FPS=1 which will give you accurate FPS but not accurate render times because OpenGL is asynchronous. To get accurate render times too you will need to slow it down a little by adding: COGL_DEBUG=sync-frame -- 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/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed Status in linux-raspi package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed
How do you determine shell fps? -- 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/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed Status in linux-raspi package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016990] Re: [Lunar] Irregular FPS with Path of Exile
I tested MUTTER_DEBUG_TRIPLE_BUFFERING=never first and it made no difference. -- 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/2016990 Title: [Lunar] Irregular FPS with Path of Exile Status in mutter package in Ubuntu: Triaged Bug description: I'm having a strange issue with the game Path of Exile (free). With Ubuntu Wayland session, vsync on, I get very irregular frame rates, it jumps around 40 fps. If I switch to Plasma Wayland the game is very smooth 60 fps. I'm running the game from Steam with Proton. I've tried Proton Experimental and Proton 8.0 so far, no difference. The game uses Vulkan so I guess it's being allowed to set up all the swap and presentation stuff pretty much itself... ? MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 doesn't help Mutter so it's not strictly related to triple buffering, which makes sense since it's a full screen game anyway. Kernel: 6.2.0-1003-lowlatency GPU: Radeon 6800 XT CPU: Ryzen 9 5900X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2016990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017090] Re: [raspi] glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2017090 ** Tags added: iso-testing -- 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/2017090 Title: [raspi] glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS Status in glmark2 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS in the terminal. Doesn't seem to happen in windowed mode. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: glmark2-wayland 2021.02-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:10:16 2023 ImageMediaBuild: 20230417 SourcePackage: glmark2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glmark2/+bug/2017090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2017097 ** Tags added: iso-testing -- 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/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed Status in linux-raspi package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016990] Re: [Lunar] Irregular FPS with Path of Exile
Please report the bug upstream at https://gitlab.gnome.org/GNOME/mutter/-/issues and mention: * GPU model * graphics driver in use (lspci -k) * The version of libmutter installed (should be 44.0) * That CLUTTER_PAINT=disable-dynamic-max-render-time fixes it ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: Incomplete => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2334 https://gitlab.gnome.org/GNOME/mutter/-/issues/2334 -- 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/2016990 Title: [Lunar] Irregular FPS with Path of Exile Status in mutter package in Ubuntu: Triaged Bug description: I'm having a strange issue with the game Path of Exile (free). With Ubuntu Wayland session, vsync on, I get very irregular frame rates, it jumps around 40 fps. If I switch to Plasma Wayland the game is very smooth 60 fps. I'm running the game from Steam with Proton. I've tried Proton Experimental and Proton 8.0 so far, no difference. The game uses Vulkan so I guess it's being allowed to set up all the swap and presentation stuff pretty much itself... ? MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 doesn't help Mutter so it's not strictly related to triple buffering, which makes sense since it's a full screen game anyway. Kernel: 6.2.0-1003-lowlatency GPU: Radeon 6800 XT CPU: Ryzen 9 5900X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2016990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016990] Re: [Lunar] Irregular FPS with Path of Exile
The other upstream issue currently open that requires CLUTTER_PAINT=disable-dynamic-max-render-time is https://gitlab.gnome.org/GNOME/mutter/-/issues/2334 but that seems to be different enough that you should log a new bug. ** Tags added: dynamic-max-render-time -- 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/2016990 Title: [Lunar] Irregular FPS with Path of Exile Status in mutter package in Ubuntu: Triaged Bug description: I'm having a strange issue with the game Path of Exile (free). With Ubuntu Wayland session, vsync on, I get very irregular frame rates, it jumps around 40 fps. If I switch to Plasma Wayland the game is very smooth 60 fps. I'm running the game from Steam with Proton. I've tried Proton Experimental and Proton 8.0 so far, no difference. The game uses Vulkan so I guess it's being allowed to set up all the swap and presentation stuff pretty much itself... ? MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 doesn't help Mutter so it's not strictly related to triple buffering, which makes sense since it's a full screen game anyway. Kernel: 6.2.0-1003-lowlatency GPU: Radeon 6800 XT CPU: Ryzen 9 5900X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2016990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016990] Re: [Lunar] Irregular FPS with Path of Exile
Thanks. Does that mean MUTTER_DEBUG_TRIPLE_BUFFERING=never made no difference? -- 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/2016990 Title: [Lunar] Irregular FPS with Path of Exile Status in mutter package in Ubuntu: Triaged Bug description: I'm having a strange issue with the game Path of Exile (free). With Ubuntu Wayland session, vsync on, I get very irregular frame rates, it jumps around 40 fps. If I switch to Plasma Wayland the game is very smooth 60 fps. I'm running the game from Steam with Proton. I've tried Proton Experimental and Proton 8.0 so far, no difference. The game uses Vulkan so I guess it's being allowed to set up all the swap and presentation stuff pretty much itself... ? MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 doesn't help Mutter so it's not strictly related to triple buffering, which makes sense since it's a full screen game anyway. Kernel: 6.2.0-1003-lowlatency GPU: Radeon 6800 XT CPU: Ryzen 9 5900X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2016990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font is ugly
Hi, indeed I forget the store is also snap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font is ugly Status in fontconfig package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017090] Re: glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS
** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Summary changed: - glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS + [raspi] glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS -- 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/2017090 Title: [raspi] glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS Status in glmark2 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS in the terminal. Doesn't seem to happen in windowed mode. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: glmark2-wayland 2021.02-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:10:16 2023 ImageMediaBuild: 20230417 SourcePackage: glmark2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glmark2/+bug/2017090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] [NEW] [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed
Public bug reported: On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image lunar performance raspi raspi-gfx raspi-image ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed Status in linux-raspi package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font is ugly
It looks like this issue mostly affects Snap apps. Please see the font config debug output attached. ** Attachment added: "font config debug output" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5665442/+files/fc-debug.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font is ugly Status in fontconfig package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017090] [NEW] glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS
Public bug reported: glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS in the terminal. Doesn't seem to happen in windowed mode. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: glmark2-wayland 2021.02-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:10:16 2023 ImageMediaBuild: 20230417 SourcePackage: glmark2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glmark2 (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image lunar performance raspi raspi-gfx raspi-image ** Also affects: mutter (Ubuntu) Importance: Undecided Status: 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/2017090 Title: glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS Status in glmark2 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: glmark2-wayland --fullscreen stutters visually while reporting hundreds of FPS in the terminal. Doesn't seem to happen in windowed mode. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: glmark2-wayland 2021.02-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:10:16 2023 ImageMediaBuild: 20230417 SourcePackage: glmark2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glmark2/+bug/2017090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016990] Re: [Lunar] Irregular FPS with Path of Exile
If I set CLUTTER_PAINT=disable-dynamic-max-render-time it fixes the issue! I only had that variable set during the test. -- 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/2016990 Title: [Lunar] Irregular FPS with Path of Exile Status in mutter package in Ubuntu: Incomplete Bug description: I'm having a strange issue with the game Path of Exile (free). With Ubuntu Wayland session, vsync on, I get very irregular frame rates, it jumps around 40 fps. If I switch to Plasma Wayland the game is very smooth 60 fps. I'm running the game from Steam with Proton. I've tried Proton Experimental and Proton 8.0 so far, no difference. The game uses Vulkan so I guess it's being allowed to set up all the swap and presentation stuff pretty much itself... ? MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 doesn't help Mutter so it's not strictly related to triple buffering, which makes sense since it's a full screen game anyway. Kernel: 6.2.0-1003-lowlatency GPU: Radeon 6800 XT CPU: Ryzen 9 5900X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2016990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
Success, no bug: https://www.edid.tv/edid/2366/ -- 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/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor Status in linux-raspi package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Confirmed Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font is ugly
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2017076 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font is ugly Status in fontconfig package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
