[Desktop-packages] [Bug 2007017] [NEW] wslview causes the font to change in WSL
Public bug reported: Version: wslu v4.1.1-1 Distro Version: Windows Version 10.0.19045.2364 x64 ``` $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ uname -a Linux csm10495-desk 5.10.16.3-microsoft-standard-WSL2 #1 SMP Fri Apr 2 22:23:49 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy wslu wslu: Installed: 4.1.1-1ubuntu1~20.04 Candidate: 4.1.1-1ubuntu1~20.04 Version table: *** 4.1.1-1ubuntu1~20.04 500 500 http://ppa.launchpad.net/wslutilities/wslu/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ``` Running wslview from the WSL inside a windows command prompt seems to resize the font/window. (This bug isn't about the warnings or errors it prints, just the weird font/window behavior). I wouldn't have expected this to change the font/window size. See attached gif to better understand what I'm describing. Thanks! ** Affects: wslu (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Gif shwoing the issue" https://bugs.launchpad.net/bugs/2007017/+attachment/5646461/+files/weird2.gif -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/2007017 Title: wslview causes the font to change in WSL Status in wslu package in Ubuntu: New Bug description: Version: wslu v4.1.1-1 Distro Version: Windows Version 10.0.19045.2364 x64 ``` $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ uname -a Linux csm10495-desk 5.10.16.3-microsoft-standard-WSL2 #1 SMP Fri Apr 2 22:23:49 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy wslu wslu: Installed: 4.1.1-1ubuntu1~20.04 Candidate: 4.1.1-1ubuntu1~20.04 Version table: *** 4.1.1-1ubuntu1~20.04 500 500 http://ppa.launchpad.net/wslutilities/wslu/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ``` Running wslview from the WSL inside a windows command prompt seems to resize the font/window. (This bug isn't about the warnings or errors it prints, just the weird font/window behavior). I wouldn't have expected this to change the font/window size. See attached gif to better understand what I'm describing. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/2007017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007011] [NEW] In the Applications search, the first letter I type is repeated so there are two.
Public bug reported: To reproduce this: Start a gnome-shell session, go to the Activities on the upper left hand corner of the screen. This opens up a "Type to search box at the top of the screen. Type any letter. It will appear twice. If you are looking for a program, for example, LTspice, the first two letters will repeat giving LLTspice, and it won't find the program until you backspace back until you have only L, then LTspice shows up. Thanks for all the fixes you provide! Rob ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 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: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 11 18:44:18 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-12-09 (65 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2007011 Title: In the Applications search, the first letter I type is repeated so there are two. Status in gnome-shell package in Ubuntu: New Bug description: To reproduce this: Start a gnome-shell session, go to the Activities on the upper left hand corner of the screen. This opens up a "Type to search box at the top of the screen. Type any letter. It will appear twice. If you are looking for a program, for example, LTspice, the first two letters will repeat giving LLTspice, and it won't find the program until you backspace back until you have only L, then LTspice shows up. Thanks for all the fixes you provide! Rob ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 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: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 11 18:44:18 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-12-09 (65 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. 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/gnome-shell/+bug/2007011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
No reproduction on Lunar for Nemo. Syslog does not show any errors ** Attachment added: "Screenshot from 2023-02-11 18-09-13.png" https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1998060/+attachment/5646439/+files/Screenshot%20from%202023-02-11%2018-09-13.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: In Progress Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 can confirm this under Gnome as well. Starting a Wayland session, all works fine. Logging in under Xorg results in this graphical issue for both Firefox and Chromium. Same GPU as the initial reporter, however I am on 22.04 and kernel 5.15.0 (stock HWE). -- 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
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- 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
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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
[Desktop-packages] [Bug 2007007] [NEW] LibreOffice Does Not Launch with KDE Integration
Public bug reported: apt-get install libreoffice-kde libreoffice-writer Launching LibreOffice Writer or the Start Center just gets stuck at the splash screen with progress bar displayed but not updated... it takes over 5 minutes to load a simple docx file. I have better luck with libreoffice-writer-nogui and no KDE integration, which loads the same docx file immediately. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libreoffice-kde 1:7.4.4-0ubuntu0.22.10.2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Feb 11 12:02:53 2023 InstallationDate: Installed on 2022-09-23 (140 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2007007 Title: LibreOffice Does Not Launch with KDE Integration Status in libreoffice package in Ubuntu: New Bug description: apt-get install libreoffice-kde libreoffice-writer Launching LibreOffice Writer or the Start Center just gets stuck at the splash screen with progress bar displayed but not updated... it takes over 5 minutes to load a simple docx file. I have better luck with libreoffice-writer-nogui and no KDE integration, which loads the same docx file immediately. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libreoffice-kde 1:7.4.4-0ubuntu0.22.10.2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Feb 11 12:02:53 2023 InstallationDate: Installed on 2022-09-23 (140 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2007007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006633] Re: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)
Please remember to mention the bug number in the changelog entry. Additionally, for stylistic purposes, I changed this: * Merge from Debian unstable. The remaining difference is the change for ignoring test results on i386 to avoir failure. To this: * Merge from Debian Unstable (LP: #2006633). Remaining changes: - Don't fail the build on tests error for i386 Otherwise, looks good to me, uploading. Please keep this in mind for a later upload. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2006633 Title: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main) Status in librsvg package in Ubuntu: New Bug description: Please merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main) Changelog entries since current lunar version 2.54.4+dfsg-1ubuntu1: librsvg (2.54.5+dfsg-1) unstable; urgency=medium * New upstream release * debian/librsvg2-2.docs: NEWS.md -> NEWS -- Jeremy Bicha Thu, 22 Sep 2022 17:00:54 -0400 Remaining differences with librsvg from Debian unstable: * Don't fail the build on tests error for i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2006633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981863] Re: gnome calendar does not sync with google calendar
Not sure about 22.04, but i am sure about 22.10, there it is no sync in any direction. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: Confirmed Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003399] Re: gnome-shell crashed with SIGSEGV in find_class_name() from remove_class_name() from st_widget_remove_style_class_name() from ffi_call_unix64() from ffi_call_int()
Blocage /usr/bin/gnome- - shell -- 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/2003399 Title: gnome-shell crashed with SIGSEGV in find_class_name() from remove_class_name() from st_widget_remove_style_class_name() from ffi_call_unix64() from ffi_call_int() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c48de759a64240e03aa3aa6f4f20143724bbd23c 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/2003399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
I have the same issue as Samuel. I can connect to the hotspot just fine, but the connected devices don't have access to internet. Strangely enough I did find one workaround that fixes the problem for me in this answer: https://askubuntu.com/a/1444778 The -999 priority doesn't seem to matter, but if I set the hotspot to start automatically and then reboot, connected devices can access the internet. Also, if the hotspot is started automatically I can stop and re-start it and things still work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007004] [NEW] Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected
Public bug reported: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. Fully updated via apt. Everything worked OK until sometime around early January 2023 (it may have started earlier, but I only noticed it the first time I moved to a location without WiFi). Since then, everything works OK as long as I am connected to WiFi. The moment I disconnect from a WiFi network, or disable WiFi altogether, the mouse begins to rapidly disconnect/connect in a loop about 3-4 times a second. If I boot up somewhere where I have no WiFi signal, same thing happens. If I boot with an older 22.04.01 live USB - no problem If I boot with a recent 22.10 live USB - same problem root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx joined with macid 0 Feb 11 20:47:19 ithaca kernel: [ 3449.943789] wlo1: associated Feb 11 20:47:19 ithaca kernel: [ 3449.995269] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready Nothing logged in dmesg After reconnecting WiFi, everything works OK again. I assume bluez is the correct package - please let me know if otherwise,
[Desktop-packages] [Bug 2006113] Re: Incomplete variable fonts export to PDF
** Bug watch added: Document Foundation Bugzilla #153048 https://bugs.documentfoundation.org/show_bug.cgi?id=153048 ** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=153048 Importance: Unknown Status: Unknown ** Tags added: ppa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2006113 Title: Incomplete variable fonts export to PDF Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: New Bug description: Ubuntu version: 22.10 (Kinetic) LO version: 7.5.0_rc3-0ubuntu0.22.10.1~lo1 Document Foundation version: 7.5.0.3 (X86_64) When exporting to PDF a document containing variable fonts, some instances (different weight or width) do not appear. There are in the font list of the PDF document, but not correctly displayed (or printed). This incomplete behaviour is observed with the Ubuntu version of LO7.5, but not with the "official" one, the .deb downloaded from the Document Foundation site. The ODT file is attached, with both PDF output (_UB: Ubuntu, _DF: Document Foundation) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2006113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006113] Re: Incomplete variable fonts export to PDF
It seems to be solved with Ubuntu version 1:7.5.1~rc1-0ubuntu0.22.10.1~lo5 (Kinetic) installed from “LibreOffice Pre-Releases” PPA. But I cannot understand why same versions downloaded from Ubuntu PPA's and form the Document Foundation site may have a different behaviour for PDF export. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2006113 Title: Incomplete variable fonts export to PDF Status in libreoffice package in Ubuntu: New Bug description: Ubuntu version: 22.10 (Kinetic) LO version: 7.5.0_rc3-0ubuntu0.22.10.1~lo1 Document Foundation version: 7.5.0.3 (X86_64) When exporting to PDF a document containing variable fonts, some instances (different weight or width) do not appear. There are in the font list of the PDF document, but not correctly displayed (or printed). This incomplete behaviour is observed with the Ubuntu version of LO7.5, but not with the "official" one, the .deb downloaded from the Document Foundation site. The ODT file is attached, with both PDF output (_UB: Ubuntu, _DF: Document Foundation) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2006113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006982] Re: Update to version 4.0
Thanks for reporting. I found a corresponding bug report in Debian, so have attached a bug watch. ** Bug watch added: Debian Bug tracker #1030857 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030857 ** Also affects: transmission (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030857 Importance: Unknown Status: Unknown ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/2006982 Title: Update to version 4.0 Status in transmission package in Ubuntu: New Status in transmission package in Debian: Unknown Bug description: Transmission recently released a new version. please update the version in the repository. thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/2006982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
