[Desktop-packages] [Bug 1995349] Re: [goodix] The enrolled finger is unknown to device
** Also affects: libfprint (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1995349 Title: [goodix] The enrolled finger is unknown to device Status in libfprint: New Status in OEM Priority Project: Triaged Status in libfprint package in Ubuntu: New Status in libfprint source package in Jammy: New Status in libfprint source package in Kinetic: New Status in libfprint source package in Lunar: New Bug description: [Impact] * The enrolled finger is unknown to device [Test Plan] * Find a machine with Goodix fingerprint device * Clean up the storage of fp device by `manage-prints` * Launch `settings` and enable `Fingerprint Login` * Enroll left index finger and right index finger * Login with right index finger [Where problems could occur] * This is only affected goodix fingerprint device To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1995349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006586] [NEW] Ubuntu Pro: Segmentation faults when quit gnome-initial-setup
Public bug reported: Click 'Quit' from applications menu directly after the gnome-initial-setup show, then this issue will be reproduced. ubuntu: 22.04.1 gnome-initial-setup: 42.0.1-1ubuntu2.1 ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Description changed: - Click 'Quit' from applications menu directly after the gnome-initial- - setup show, then this issue will be reproduced. + Click 'Quit' from applications menu directly after the gnome-initial-setup show, then this issue will be reproduced. + ubuntu: 22.04.1 + gnome-initial-setup: 42.0.1-1ubuntu2.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2006586 Title: Ubuntu Pro: Segmentation faults when quit gnome-initial-setup Status in gnome-initial-setup package in Ubuntu: New Bug description: Click 'Quit' from applications menu directly after the gnome-initial-setup show, then this issue will be reproduced. ubuntu: 22.04.1 gnome-initial-setup: 42.0.1-1ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2006586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907121] Re: simple-scan unable to connect scanner HP 2630
both sane-airscan and ipp-usb are installed on my Lunar and simple-scan works fine with my HP 2630 corrado@corrado-n4-lunar:~$ apt policy sane-airscan sane-airscan: Installed: 0.99.27-1build1 Candidate: 0.99.27-1build1 Version table: *** 0.99.27-1build1 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n4-lunar:~$ apt policy ipp-usb ipp-usb: Installed: 0.9.23-1 Candidate: 0.9.23-1 Version table: *** 0.9.23-1 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n4-lunar:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1907121 Title: simple-scan unable to connect scanner HP 2630 Status in simple-scan package in Ubuntu: New Bug description: simple-scan says: "Ready to scan" but when i click on "scan" it fails to scan with a message "unable to connect to scanner" corrado@corrado-x4-focal:~$ scanimage -L device `hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS' is a Hewlett-Packard DeskJet_2600_series all-in-one corrado@corrado-x4-focal:~$ apt policy simple-scan simple-scan: Installed: 3.36.3-0ubuntu0.20.04.0 Candidate: 3.36.3-0ubuntu0.20.04.0 Version table: *** 3.36.3-0ubuntu0.20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages corrado@corrado-x4-focal:~$ inxi -Fx System:Host: corrado-x4-focal Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 Sound Server: ALSA v: k5.4.0-56-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 19.43 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 19.42 GiB (62.2%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 31.0 C Fan Speeds (RPM): fan-1: 0 fan-2: 2276 fan-3: 0 fan-4: 2216 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.42 vbat: 3.15 Info: Processes: 227 Uptime: 36m Memory: 7.48 GiB used: 1.59 GiB (21.2%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 corrado@corrado-x4-focal:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 17:16:02 2020 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2020-04-29 (222 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=8a3753b1-5036-49b8-98d8-8b5c3eb01c74 ro quiet splash SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/
[Desktop-packages] [Bug 2006590] [NEW] Xorg freeze
You have been subscribed to a public bug: Suddenly this week, my GUI (ubuntu 22.10) does not open, stuck on the console text. I tried to free some space (by uninstall a app), then to check/update the paquets (dkpg). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.86.01 Wed Oct 26 09:12:38 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Feb 8 12:13:40 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 950M] [1025:1094] InstallationDate: Installed on 2022-05-03 (280 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 25a7:fa23 Areson Technology Corp 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.32 dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.4 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze kinetic ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/2006590 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006590] Re: Xorg freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2006590 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Suddenly this week, my GUI (ubuntu 22.10) does not open, stuck on the console text. I tried to free some space (by uninstall a app), then to check/update the paquets (dkpg). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.86.01 Wed Oct 26 09:12:38 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Feb 8 12:13:40 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 950M] [1025:1094] InstallationDate: Installed on 2022-05-03 (280 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 25a7:fa23 Areson Technology Corp 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.32 dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2006590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979412] Re: [snap] Chromium crashes when downloading
Of the latest crash, I attached the last 10 seconds in the log. The URL I visited last was https://mails.bronger.org/xx/4?tokenFull=13t4Q4g2C_ (sorry, due to confidential content I had to replace parts of it with “x”es). It is a docx file. ** Attachment added: "chromium.log" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1979412/+attachment/5645540/+files/chromium.log -- 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/1979412 Title: [snap] Chromium crashes when downloading Status in chromium-browser package in Ubuntu: Incomplete Bug description: For a couple of weeks, I observe random crashes of Chromium when you click on a link that starts a non-HTML download (e.g. PDF or an MS Excel file). After restarting Chromium and restoring the tabs, a second click on the link starts the download without problems, probably because this issue is not 100% reproducible in the first place. Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit) on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1979412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2005124] Re: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubu
Is there any way to work around this until a fix is released? It appears I cannot use apt to upgrade/remove other things while this is broken. -- 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/2005124 Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 Status in fontconfig package in Ubuntu: Fix Committed Status in kubuntu-settings package in Ubuntu: Fix Released Status in fontconfig package in Debian: Unknown Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 23.04 Package: fontconfig-config 2.13.1-4.4ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Feb 4 05:59:53 2023 DuplicateSignature: package:fontconfig-config:2.13.1-4.4ubuntu1 Unpacking fontconfig-config (2.14.1-3ubuntu1) over (2.13.1-4.4ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-xn7IM4/015-fontconfig-config_2.14.1-3ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 ErrorMessage: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 InstallationDate: Installed on 2023-01-31 (3 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230130) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.19ubuntu3 apt 2.5.5 SourcePackage: fontconfig Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790608] Re: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp)
In fact, it's worse under KDE, because you pick '/tmp/' in the side bar of the file save dialogue, it looks right, you can press save, the download feedback happens OK, and then the files don't appear in the host system at all. -- 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/1790608 Title: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp) Status in snapd: New Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I received a document via e-mail in Thunderbird. I have the Libreoffice snap package installed. When I want to open the document from Thunderbird, I see the Libreoffice splash screen, and then a dialog stating "/tmp/mozilla_0/.docx does not exist." The same dialog appears when I navigate to the folder in Files and want to open it. When I copy the file to my desktop, however, I can open it without problems. I guess the source of the issue is confinement, that the Libreoffice snap can only access files from $HOME. But this breaks the case where thunderbird creates a temporary copy in /tmp. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1790608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2005124] Re: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubu
yes in a terminal app.. sudo dpkg -r kubuntu-desktop sudo dpkg -r kubuntu-settings-desktop sudo apt --fix-broken install sudo apt reinstall kubuntu-desktop will get around the blockage (as kubuntu-settings-desktop gets pulled in by kubuntu-desktop both need to be temporarily removed) -- 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/2005124 Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 Status in fontconfig package in Ubuntu: Fix Committed Status in kubuntu-settings package in Ubuntu: Fix Released Status in fontconfig package in Debian: Unknown Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 23.04 Package: fontconfig-config 2.13.1-4.4ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Feb 4 05:59:53 2023 DuplicateSignature: package:fontconfig-config:2.13.1-4.4ubuntu1 Unpacking fontconfig-config (2.14.1-3ubuntu1) over (2.13.1-4.4ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-xn7IM4/015-fontconfig-config_2.14.1-3ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 ErrorMessage: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 InstallationDate: Installed on 2023-01-31 (3 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230130) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.19ubuntu3 apt 2.5.5 SourcePackage: fontconfig Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006590] Re: Xorg freeze after rebooting
** Summary changed: - Xorg freeze + Xorg freeze after rebooting -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2006590 Title: Xorg freeze after rebooting Status in xorg package in Ubuntu: New Bug description: Suddenly this week, my GUI (ubuntu 22.10) does not open, stuck on the console text. I tried to free some space (by uninstall a app), then to check/update the paquets (dkpg). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.86.01 Wed Oct 26 09:12:38 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Feb 8 12:13:40 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 950M] [1025:1094] InstallationDate: Installed on 2022-05-03 (280 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 25a7:fa23 Areson Technology Corp 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.32 dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2006590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2005124] Re: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubu
Very cool, thanks for that! -- 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/2005124 Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 Status in fontconfig package in Ubuntu: Fix Committed Status in kubuntu-settings package in Ubuntu: Fix Released Status in fontconfig package in Debian: Unknown Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 23.04 Package: fontconfig-config 2.13.1-4.4ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Feb 4 05:59:53 2023 DuplicateSignature: package:fontconfig-config:2.13.1-4.4ubuntu1 Unpacking fontconfig-config (2.14.1-3ubuntu1) over (2.13.1-4.4ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-xn7IM4/015-fontconfig-config_2.14.1-3ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 ErrorMessage: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 InstallationDate: Installed on 2023-01-31 (3 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230130) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.19ubuntu3 apt 2.5.5 SourcePackage: fontconfig Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006625] [NEW] Merge modemmanager 1.20.4-1 (main) from Debian unstable (main)
Public bug reported: Please merge modemmanager 1.20.4-1 (main) from Debian unstable (main) Changelog entries since current lunar version 1.20.0-1ubuntu1: modemmanager (1.20.4-1) unstable; urgency=medium * New upstream version 1.20.4 * d/control: bump Standards-Version, no change required -- Arnaud Ferraris Tue, 03 Jan 2023 13:34:49 +0100 modemmanager (1.20.2-1) unstable; urgency=medium * d/watch: only watch for stable releases. ModemManager has a x.y.z version numbering scheme where y is even for stable releases and odd for development ones. Stable release candidates have x.y-rcz version numbers with y being an even number. This change ensures we only watch for stable releases, including RCs. * New upstream version 1.20.2 * d/patches: drop upstreamed patch -- Arnaud Ferraris Mon, 19 Dec 2022 13:59:08 +0100 Remaining differences with modemmanager from Debian unstable: * Build without libqrtr for now, the MIR is blocked since we don't have hardware available to do the required testing of the feature, include some workarounds to fix the build ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Patch added: "debdiff to 1.20.4-1 in unstable" https://bugs.launchpad.net/bugs/2006625/+attachment/5645626/+files/modemmanager_1.20.4-1ubuntu1-from-1.20.4-1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2006625 Title: Merge modemmanager 1.20.4-1 (main) from Debian unstable (main) Status in modemmanager package in Ubuntu: New Bug description: Please merge modemmanager 1.20.4-1 (main) from Debian unstable (main) Changelog entries since current lunar version 1.20.0-1ubuntu1: modemmanager (1.20.4-1) unstable; urgency=medium * New upstream version 1.20.4 * d/control: bump Standards-Version, no change required -- Arnaud Ferraris Tue, 03 Jan 2023 13:34:49 +0100 modemmanager (1.20.2-1) unstable; urgency=medium * d/watch: only watch for stable releases. ModemManager has a x.y.z version numbering scheme where y is even for stable releases and odd for development ones. Stable release candidates have x.y-rcz version numbers with y being an even number. This change ensures we only watch for stable releases, including RCs. * New upstream version 1.20.2 * d/patches: drop upstreamed patch -- Arnaud Ferraris Mon, 19 Dec 2022 13:59:08 +0100 Remaining differences with modemmanager from Debian unstable: * Build without libqrtr for now, the MIR is blocked since we don't have hardware available to do the required testing of the feature, include some workarounds to fix the build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2006625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Changed in: aide (Ubuntu) Status: Incomplete => Fix Released ** Changed in: anope (Ubuntu) Status: Incomplete => Fix Released ** Changed in: apache2 (Ubuntu) Status: Triaged => Fix Released ** Changed in: exim4 (Ubuntu) Status: In Progress => Fix Released ** Changed in: glib2.0 (Ubuntu) Status: Incomplete => Fix Released ** Changed in: postfix (Ubuntu) Status: Incomplete => Fix Released ** Changed in: grep (Ubuntu) Status: Incomplete => Fix Released ** Changed in: python-pyscss (Ubuntu) Status: Incomplete => Fix Released ** Changed in: tilix (Ubuntu) Status: New => Fix Released ** No longer affects: ubuntu-core-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Fix Released Status in anope package in Ubuntu: Fix Released Status in apache2 package in Ubuntu: Fix Released Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Fix Released Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in grep package in Ubuntu: Fix Released Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Fix Released Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Fix Released Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Fix Released Status in python-pyscss package in Ubuntu: Fix Released Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in tilix package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Status in postfix package in Debian: Fix Released Status in zsh package in Debian: Confirmed Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
Thanks for testing. So, your first log contains this error, though: ``` /build/chromium/parts/chromium/build ERROR at //build/config/linux/dri/BUILD.gn:11:20: Script returned non-zero exit code. dri_driver_dir = exec_script(pkg_config_script, ^-- Current dir: /build/chromium/parts/chromium/build/out/Release/ Command: python3 /build/chromium/parts/chromium/build/build/config/linux/pkg-config.py -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config --dridriverdir dri Returned 1 and printed out: Error from pkg-config. stderr: ``` -- 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/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: In Progress Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006628] [NEW] Merge libqmi 1.32.2-1 (main) from Debian unstable (main)
Public bug reported: Please merge libqmi 1.32.2-1 (main) from Debian unstable (main) Changelog entries since current lunar version 1.32.0-1ubuntu2: libqmi (1.32.2-1) unstable; urgency=medium * d/watch: only watch for stable releases `libqmi` has a x.y.z version numbering scheme where y is even for stable releases and odd for development ones. Stable release candidates have x.y-rcz version numbers with y being an even number. This change ensures we only watch for stable releases, including RCs. * New upstream version 1.32.2 -- Arnaud Ferraris Mon, 19 Dec 2022 11:51:57 +0100 Remaining differences with modemmanager from Debian unstable: * Build without libqrtr for now, the MIR is blocked since we don't have hardware available to do the required testing of the feature, include some workarounds to fix the build ** Affects: libqmi (Ubuntu) Importance: Undecided Status: New ** Patch added: "debdiff to 1.32.2-1 in unstable" https://bugs.launchpad.net/bugs/2006628/+attachment/5645629/+files/libqmi_1.32.2-1ubuntu1-from-1.32.2-1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/2006628 Title: Merge libqmi 1.32.2-1 (main) from Debian unstable (main) Status in libqmi package in Ubuntu: New Bug description: Please merge libqmi 1.32.2-1 (main) from Debian unstable (main) Changelog entries since current lunar version 1.32.0-1ubuntu2: libqmi (1.32.2-1) unstable; urgency=medium * d/watch: only watch for stable releases `libqmi` has a x.y.z version numbering scheme where y is even for stable releases and odd for development ones. Stable release candidates have x.y-rcz version numbers with y being an even number. This change ensures we only watch for stable releases, including RCs. * New upstream version 1.32.2 -- Arnaud Ferraris Mon, 19 Dec 2022 11:51:57 +0100 Remaining differences with modemmanager from Debian unstable: * Build without libqrtr for now, the MIR is blocked since we don't have hardware available to do the required testing of the feature, include some workarounds to fix the build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/2006628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006628] Re: Merge libqmi 1.32.2-1 (main) from Debian unstable (main)
** Description changed: Please merge libqmi 1.32.2-1 (main) from Debian unstable (main) Changelog entries since current lunar version 1.32.0-1ubuntu2: libqmi (1.32.2-1) unstable; urgency=medium - * d/watch: only watch for stable releases - `libqmi` has a x.y.z version numbering scheme where y is even for - stable releases and odd for development ones. Stable release candidates - have x.y-rcz version numbers with y being an even number. This change - ensures we only watch for stable releases, including RCs. - * New upstream version 1.32.2 + * d/watch: only watch for stable releases + `libqmi` has a x.y.z version numbering scheme where y is even for + stable releases and odd for development ones. Stable release candidates + have x.y-rcz version numbers with y being an even number. This change + ensures we only watch for stable releases, including RCs. + * New upstream version 1.32.2 - -- Arnaud Ferraris Mon, 19 Dec 2022 11:51:57 + -- Arnaud Ferraris Mon, 19 Dec 2022 11:51:57 +0100 - Remaining differences with modemmanager from Debian unstable: + Remaining differences with libqmi from Debian unstable: - * Build without libqrtr for now, the MIR is blocked since we don't have - hardware available to do the required testing of the feature, - include some workarounds to fix the build + * Build without libqrtr for now, the MIR is blocked since we don't have + hardware available to do the required testing of the feature, + include some workarounds to fix the build -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/2006628 Title: Merge libqmi 1.32.2-1 (main) from Debian unstable (main) Status in libqmi package in Ubuntu: New Bug description: Please merge libqmi 1.32.2-1 (main) from Debian unstable (main) Changelog entries since current lunar version 1.32.0-1ubuntu2: libqmi (1.32.2-1) unstable; urgency=medium * d/watch: only watch for stable releases `libqmi` has a x.y.z version numbering scheme where y is even for stable releases and odd for development ones. Stable release candidates have x.y-rcz version numbers with y being an even number. This change ensures we only watch for stable releases, including RCs. * New upstream version 1.32.2 -- Arnaud Ferraris Mon, 19 Dec 2022 11:51:57 +0100 Remaining differences with libqmi from Debian unstable: * Build without libqrtr for now, the MIR is blocked since we don't have hardware available to do the required testing of the feature, include some workarounds to fix the build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/2006628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04
*** This bug is a duplicate of bug 1949340 *** https://bugs.launchpad.net/bugs/1949340 **Just waiting for it to fixed calmly** -- 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/1968887 Title: Save As Dialog Box does not get focus in Ubuntu 22.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: When using a browser to right click a file and save as, the save as window does not get focus, which means you can't just type the name of the file you want, you have to force focus onto the window to use it by clicking it. This defeats the entire purpose of 2 built in features, 1 being the pre-selected original file name (since you can't rename until you re- aquire focus for that window, thereby undoing the pre-selection programmed in) and 2, the ability to quickly save the file with a keystroke. A side note to this, ubuntu-bug should have an option to report bugs with other WITHOUT having to specify a package. This is a bug in ubuntu-bug. Not a feature. Because we don't always know what package(s) are involved. This needs to be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 13 07:55:24 2022 InstallationDate: Installed on 2022-03-31 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade 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/1968887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995743] Re: webdav error trying to connect to nextcloud
It has been fixed upstream now in https://gitlab.gnome.org/GNOME/libsoup/-/merge_requests/356 ** Package changed: gvfs (Ubuntu) => libsoup2.4 (Ubuntu) ** Changed in: libsoup2.4 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1995743 Title: webdav error trying to connect to nextcloud Status in libsoup2.4 package in Ubuntu: Fix Committed Bug description: upgraded to ubuntu 22.10 from 22.04 and webdav fails to connect to nextcloud. Reimaged back to 22.04 and it worked. Error message is "Message recipient disconnected from message bus without replying Please select another viewer and try again." I have tried webdav from mate 22.10 and gnome 22.10 with same failure. Crash report fails as well but I was able to get a copy before deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1995743/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006630] [NEW] CD not found in MusicBrainz, but I can see it in musicbrainz.org
Public bug reported: rhythmbox version 3.4.4, Ubuntu Ubuntu 22.04.1 LTS When I try to extract a legit copy of "Never born to follow" by the Men They Couldn't Hang, rhythmbox says "can't find, please add". I go to musicbrainz.org and can see it listed, but there is a 1 second discrepancy in the final track length, and I assume that is stopping the match. Presumably the existing data works for other people so I am hesitant to report it as a MusicBrainz data error. Rather than a bug therefore, this may be an enhancement request either to loosen the match criteria, or perhaps allow the user to manually enter a MusicBrainz url or other ID to force the match? ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/2006630 Title: CD not found in MusicBrainz, but I can see it in musicbrainz.org Status in rhythmbox package in Ubuntu: New Bug description: rhythmbox version 3.4.4, Ubuntu Ubuntu 22.04.1 LTS When I try to extract a legit copy of "Never born to follow" by the Men They Couldn't Hang, rhythmbox says "can't find, please add". I go to musicbrainz.org and can see it listed, but there is a 1 second discrepancy in the final track length, and I assume that is stopping the match. Presumably the existing data works for other people so I am hesitant to report it as a MusicBrainz data error. Rather than a bug therefore, this may be an enhancement request either to loosen the match criteria, or perhaps allow the user to manually enter a MusicBrainz url or other ID to force the match? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2006630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006628] Re: Merge libqmi 1.32.2-1 (main) from Debian unstable (main)
The attachment "debdiff to 1.32.2-1 in unstable" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/2006628 Title: Merge libqmi 1.32.2-1 (main) from Debian unstable (main) Status in libqmi package in Ubuntu: New Bug description: Please merge libqmi 1.32.2-1 (main) from Debian unstable (main) Changelog entries since current lunar version 1.32.0-1ubuntu2: libqmi (1.32.2-1) unstable; urgency=medium * d/watch: only watch for stable releases `libqmi` has a x.y.z version numbering scheme where y is even for stable releases and odd for development ones. Stable release candidates have x.y-rcz version numbers with y being an even number. This change ensures we only watch for stable releases, including RCs. * New upstream version 1.32.2 -- Arnaud Ferraris Mon, 19 Dec 2022 11:51:57 +0100 Remaining differences with libqmi from Debian unstable: * Build without libqrtr for now, the MIR is blocked since we don't have hardware available to do the required testing of the feature, include some workarounds to fix the build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/2006628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006625] Re: Merge modemmanager 1.20.4-1 (main) from Debian unstable (main)
The attachment "debdiff to 1.20.4-1 in unstable" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2006625 Title: Merge modemmanager 1.20.4-1 (main) from Debian unstable (main) Status in modemmanager package in Ubuntu: New Bug description: Please merge modemmanager 1.20.4-1 (main) from Debian unstable (main) Changelog entries since current lunar version 1.20.0-1ubuntu1: modemmanager (1.20.4-1) unstable; urgency=medium * New upstream version 1.20.4 * d/control: bump Standards-Version, no change required -- Arnaud Ferraris Tue, 03 Jan 2023 13:34:49 +0100 modemmanager (1.20.2-1) unstable; urgency=medium * d/watch: only watch for stable releases. ModemManager has a x.y.z version numbering scheme where y is even for stable releases and odd for development ones. Stable release candidates have x.y-rcz version numbers with y being an even number. This change ensures we only watch for stable releases, including RCs. * New upstream version 1.20.2 * d/patches: drop upstreamed patch -- Arnaud Ferraris Mon, 19 Dec 2022 13:59:08 +0100 Remaining differences with modemmanager from Debian unstable: * Build without libqrtr for now, the MIR is blocked since we don't have hardware available to do the required testing of the feature, include some workarounds to fix the build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2006625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)
Public bug reported: 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 ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New ** Patch added: "debdiff to 2.54.5+dfsg-1 in unstable" https://bugs.launchpad.net/bugs/2006633/+attachment/5645634/+files/librsvg_2.54.5+dfsg-1ubuntu1-from-2.54.5+dfsg-1.debdiff -- 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 2006060] Re: bbswitch-dkms 0.8-10ubuntu2: bbswitch kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bbswitch (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/2006060 Title: bbswitch-dkms 0.8-10ubuntu2: bbswitch kernel module failed to build Status in bbswitch package in Ubuntu: Confirmed Bug description: error with building bbswitch module 1) lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) apt-cache policy bbswitch-dkms bbswitch-dkms: 0.8-10ubuntu2 3) What you expected to happen error during linux-headers-5.19.0-28-generic installation 4) What happened instead smooth installation of linux-headers and bbswitch module built ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bbswitch-dkms 0.8-10ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass DKMSKernelVersion: 5.19.0-28-generic Date: Sun Feb 5 23:01:49 2023 DuplicateSignature: dkms:bbswitch-dkms:0.8-10ubuntu2:/var/lib/dkms/bbswitch/0.8/build/bbswitch.c:272:13: error: implicit declaration of function ‘acpi_bus_get_device’; did you mean ‘acpi_is_pnp_device’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2023-01-26 (9 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageVersion: 0.8-10ubuntu2 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: bbswitch Title: bbswitch-dkms 0.8-10ubuntu2: bbswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/2006060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
I confirmed that DRI_DRIVER_DIR never makes it to the compiler flags. I added an error pragma to catch an empty definition and no definition in attached patch. The result when building w that patch (on 107 chromium): FAILED: obj/third_party/minigbm/minigbm/amdgpu.o ../../third_party/llvm-build/Release+Asserts/bin/clang -MMD -MF obj/third_party/minigbm/minigbm/amdgpu.o.d -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -D_GNU_SOURCE -DCR_CLANG_REVISION=\"llvmorg-16-init-4609-g025a5b22-2\" -D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS -D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -DCR_LIBCXX_REVISION=e2f63a1a48a3cdcacbfc212236050ca5deeacc30 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DDRV_AMDGPU -DDRV_I915 -I../.. -Igen -I../../buildtools/third_party/libc++ -I../../third_party/minigbm/src -fno-delete-null-pointer-checks -fno-ident -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -fcrash-diagnostics-dir=../../tools/clang/crashreports -mllvm -instcombine-lower-dbg-declare=0 -ffp-contract=off -flto=thin -fsplit-lto-unit -fw hole-program-vtables -fcomplete-member-pointers -m64 -msse3 -ffile-compilation-dir=. -no-canonical-prefixes -ftrivial-auto-var-init=pattern -O2 -fdata-sections -ffunction-sections -fno-unique-section-names -fno-omit-frame-pointer -g0 -fprofile-use=../../chrome/build/pgo_profiles/chrome-linux-5304-1666369430-50bfc04797db1acc0805fe1425e83d1bbe3b92f6.profdata -Wno-profile-instr-unprofiled -Wno-profile-instr-out-of-date -Wno-backend-plugin -fvisibility=hidden -Xclang -add-plugin -Xclang find-bad-constructs -Xclang -plugin-arg-find-bad-constructs -Xclang raw-ref-template-as-trivial-member -Xclang -plugin-arg-find-bad-constructs -Xclang check-ipc -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall -Wno-unused-variable -Wno-c++11-narrowing -Wno-unused-but-set-variable -Wno-misleading-indentation -Wno-missing-field-initializers -Wno-unused-parameter -Wloop-analysis -Wno-unneeded-internal-declaration -Wenum-compare-conditional -Wno-psabi -Wno-ignored-pragma-optimize -Wn o-deprecated-builtins -Wno-bitfield-constant-conversion -I/usr/include/libdrm -std=c11 -c ../../third_party/minigbm/src/amdgpu.c -o obj/third_party/minigbm/minigbm/amdgpu.o ../../third_party/minigbm/src/amdgpu.c:27:3: error: "DRI_DRIVER_DIR is not defined." # error "DRI_DRIVER_DIR is not defined." ^ 1 error generated. [1511/54251] CXX obj/third_party/protobuf/protoc_lib/csharp_message.o ninja: build stopped: subcommand failed. Failed to run 'override-build': Exit code was 1. If will probably make sense to add a default path for that if the symbol has not been defined. I'll work on that. ** Patch added: "amdtest:check-for-empty-define.patch" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+attachment/5645635/+files/amdtest%3Acheck-for-empty-define.patch -- 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/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: In Progress Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Lin
[Desktop-packages] [Bug 2006636] [NEW] Many Cyan Lines Cover Computer Screen
Public bug reported: bunch of cyan lines appearing on my screen rapidly, pretty sure its a hardware issue but want to make sure the graphics drivers are up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 13:34:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2023-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K08H3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.sku: xxx123x#ABA dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2006636 Title: Many Cyan Lines Cover Computer Screen Status in xorg package in Ubuntu: New Bug description: bunch of cyan lines appearing on my screen rapidly, pretty sure its a hardware issue but want to make sure the graphics drivers are up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 13:34:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2023-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K08H3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.sku: xxx123x#ABA dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 vers
[Desktop-packages] [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup
Change for gdm3 was pushed to git repo: https://salsa.debian.org/gnome-team/gdm/-/commit/03d610a4 lightdm has been uploaded with the change. ** Changed in: gdm3 (Ubuntu) Status: In Progress => Fix Committed ** Changed in: lightdm (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1887252 Title: config-error-dialog.sh should pass --no-markup Status in gdm3 package in Ubuntu: Fix Committed Status in lightdm package in Ubuntu: Fix Committed Bug description: I modified my ~/.profile to call "logger". This resulted in in producing some output on stderr like ``` <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... ``` This showed an empty zenity prompt. Logs suggest zenity was failing because it was treating `<13>` as pango markup. ``` from markup due to error parsing markup: Error on line 3 char 6: “13” is not a valid ``` We should not assume the error message strings contain valid markup, since their source is unknown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998263] Re: JPEG ( backing store not supported ) : many pictures won't open.
This bug was fixed in the package gdk-pixbuf - 2.42.9+dfsg-1ubuntu1 --- gdk-pixbuf (2.42.9+dfsg-1ubuntu1) kinetic; urgency=medium * debian/patches/git_jpg_memlimit.patch: - increase the new jpg loader memory limitation to 1GB, the 100MB value previously used isn't enough for highres images (lp: #1998263) -- Sebastien Bacher Fri, 13 Jan 2023 12:20:08 +0100 ** Changed in: gdk-pixbuf (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1998263 Title: JPEG ( backing store not supported ) : many pictures won't open. Status in Eye of GNOME: Fix Released Status in gdk-pixbuf: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in gdk-pixbuf source package in Jammy: Invalid Status in gdk-pixbuf source package in Kinetic: Fix Released Status in gdk-pixbuf source package in Lunar: Fix Released Bug description: * Impact Eog can't open high resolution jpg files * Test Case - download https://gitlab.gnome.org/GNOME/gdk-pixbuf/uploads/fcda5bc359fbf55a1b9755ba92c3303d/kwiatek.jpg - try to open the image in eog * Regression potential The change increase the memory usage limit for loading jpg, it could lead to put the system under memory pressure. The limit has been added in 22.10 though so it isn't a regression compared to the previous version of Ubuntu - Hi, 22.10. Just try to open some .jpg files from my usual storage. Error interpreting jpeg file ( Backing store not supported. ) Those same pictures open in other OSes ( 22.04, 20.04 and else. ) Can't use those pictures as backgrounds. But able to open them in Gimp or Shotwell. Maybe related to : https://gitlab.gnome.org/GNOME/gdk- pixbuf/-/issues/216 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: eog 43.0-1 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: Tue Nov 29 23:31:36 2022 InstallationDate: Installed on 2022-10-27 (33 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1998263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998263] Update Released
The verification of the Stable Release Update for gdk-pixbuf has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1998263 Title: JPEG ( backing store not supported ) : many pictures won't open. Status in Eye of GNOME: Fix Released Status in gdk-pixbuf: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in gdk-pixbuf source package in Jammy: Invalid Status in gdk-pixbuf source package in Kinetic: Fix Released Status in gdk-pixbuf source package in Lunar: Fix Released Bug description: * Impact Eog can't open high resolution jpg files * Test Case - download https://gitlab.gnome.org/GNOME/gdk-pixbuf/uploads/fcda5bc359fbf55a1b9755ba92c3303d/kwiatek.jpg - try to open the image in eog * Regression potential The change increase the memory usage limit for loading jpg, it could lead to put the system under memory pressure. The limit has been added in 22.10 though so it isn't a regression compared to the previous version of Ubuntu - Hi, 22.10. Just try to open some .jpg files from my usual storage. Error interpreting jpeg file ( Backing store not supported. ) Those same pictures open in other OSes ( 22.04, 20.04 and else. ) Can't use those pictures as backgrounds. But able to open them in Gimp or Shotwell. Maybe related to : https://gitlab.gnome.org/GNOME/gdk- pixbuf/-/issues/216 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: eog 43.0-1 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: Tue Nov 29 23:31:36 2022 InstallationDate: Installed on 2022-10-27 (33 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1998263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
This bug was fixed in the package ubiquity - 22.04.19 --- ubiquity (22.04.19) jammy; urgency=medium * zsys-setup: generate correct zfs-list.cache for target (LP: #1993318) -- Dimitri John Ledkov Tue, 10 Jan 2023 16:26:48 + ** Changed in: ubiquity (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Status in ubiquity source package in Jammy: Fix Released Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] [NEW] hwacc branches fail to build
Public bug reported: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: kivu -- 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/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: New Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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)
The attachment "debdiff to 2.54.5+dfsg-1 in unstable" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to 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 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
The attachment "amdtest:check-for-empty-define.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: In Progress Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Bram Stolk (b-stolk) -- 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/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: New Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] [NEW] hwacc branch builds with minigbm switch to software compositor on amd.
Public bug reported: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Attachment added: "comparision between minigbm and systemgbm" https://bugs.launchpad.net/bugs/2006646/+attachment/5645686/+files/chrome-gpu-comparision-minigbm-vs-systemgbm.png -- 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/2006646 Title: hwacc branch builds with minigbm switch to software compositor on amd. Status in chromium-browser package in Ubuntu: New Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006645] [NEW] Death Stranding(Video Game) crashes consistenly when moving right control stick with map open
Public bug reported: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7735#note_1674704 99% sure it's this bug on Mesa's gitlab. Installing the kisak-mesa PPA fixed the issue for me. Any chance of a backport for the fix? ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/2006645 Title: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open Status in mesa package in Ubuntu: New Bug description: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7735#note_1674704 99% sure it's this bug on Mesa's gitlab. Installing the kisak-mesa PPA fixed the issue for me. Any chance of a backport for the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds with minigbm switch to software compositor on amd.
The previous test was on a chromium 107 build. I re-tested it on a chromium 110 build with minigbm, and it shows the same result on rx580 gpu: software compositing. -- 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/2006646 Title: hwacc branch builds with minigbm switch to software compositor on amd. Status in chromium-browser package in Ubuntu: New Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006517] [NEW] Bluetooth works on desktop but not on ubuntu core
You have been subscribed to a public bug: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 ** Affects: bluez (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: jammy -- Bluetooth works on desktop but not on ubuntu core https://bugs.launchpad.net/bugs/2006517 You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
The locality to this apparmor denial suggests to me it's just the bluez snap that needs to request some extra privileges. Feb 07 23:50:34 ubuntu audit[1562]: AVC apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1562 comm="bluetoothd" family="alg" sock_type="seqpacket" protocol=0 requested_mask="create" denied_mask="create" Feb 07 23:50:34 ubuntu bluetoothd[1562]: src/advertising.c:read_adv_features_callback() Failed to read advertising features: Not Supported (0x0c) ** Package changed: linux (Ubuntu) => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1211700] Re: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very f
Closing this ticket where I can as there's no update for 5 years. Plus mir has been supplanted by wayland. ** Changed in: mesa (Ubuntu) Status: New => Won't Fix ** Changed in: mir (Ubuntu) Status: Triaged => Won't Fix ** Changed in: mir Status: Triaged => 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/1211700 Title: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very few frames Status in Mir: Fix Released Status in mesa package in Ubuntu: Won't Fix Status in mir package in Ubuntu: Won't Fix Bug description: GPU-heavy clients on Mesa gallium drivers (e.g. radeon, nouveau and freedreno) cause the Mir server to slow, sometimes to a halt. This is seen as a frozen screen, unable to move surfaces, or unable to switch VTs (for a while). For example: mir_demo_client_egltriangle -n mir_demo_client_eglplasma -n The -n flag (swapinterval = 0) seems to cause the client to overload the mir server to the point where it cannot render physical frames very often. $ es2_info EGL_VERSION = 1.4 (Gallium) EGL_VENDOR = Mesa Project EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel GL_RENDERER: Gallium 0.4 on AMD CEDAR ... $ es2_info EGL_VERSION = 1.4 (Gallium) EGL_VENDOR = Mesa Project EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel GL_RENDERER: Gallium 0.4 on NVA8 ... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1211700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006669] [NEW] Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])
Public bug reported: GUI hard lock during zoom session and gnome-terminal kern.log shows a mix of errors __ kernel: [ 3627.948545] Asynchronous wait on fence :00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready [i915]) kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in chrome [5521] kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset due to GPU hang kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled ___ I suspect this issue to be upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755 upstream commit: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217 Reproducer: Although I don't have my own reproducer, the upstream mesa reproducer does trigger a hang on my machine. Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it loads, you will see pikachu. Press "S", he will go back. My whole system freezes from this in Wayland, regardless of the browser. Kernel: 6.0.0-1008-oem Mesa: 22.2.5-0ubuntu0.1~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9 Uname: Linux 6.0.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 21:40:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b1a] Subsystem: Dell Device [1028:0b1a] InstallationDate: Installed on 2022-07-13 (211 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: Dell Inc. Precision 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 03M8N5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mesa (Ubuntu) Importance: Undecided Assignee: Dave Chiluk (chiluk) Status: New ** Tags: amd64 apport-bug jammy ubuntu uec-images wayland-session -- 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/2006669 Title: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915]) Status in mesa package in Ubuntu: New Bug description: GUI hard lock during zoom session and gnome-terminal kern.log shows a mix of errors __ kernel: [ 3627.948545] Asynchronous wait on fence :00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready [i915]) kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in chrome [5521] kernel: [ 3631.064218] i915
[Desktop-packages] [Bug 1211700] Re: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very f
Mir actually uses Wayland these days :) Also this bug is probably either still valid or might have been fixed. I don't have the time or interest to figure out which so "Won't Fix" is fine, unless RAOF wants to investigate. ** Changed in: mir Status: Fix Released => Won't Fix -- 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/1211700 Title: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very few frames Status in Mir: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in mir package in Ubuntu: Won't Fix Bug description: GPU-heavy clients on Mesa gallium drivers (e.g. radeon, nouveau and freedreno) cause the Mir server to slow, sometimes to a halt. This is seen as a frozen screen, unable to move surfaces, or unable to switch VTs (for a while). For example: mir_demo_client_egltriangle -n mir_demo_client_eglplasma -n The -n flag (swapinterval = 0) seems to cause the client to overload the mir server to the point where it cannot render physical frames very often. $ es2_info EGL_VERSION = 1.4 (Gallium) EGL_VENDOR = Mesa Project EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel GL_RENDERER: Gallium 0.4 on AMD CEDAR ... $ es2_info EGL_VERSION = 1.4 (Gallium) EGL_VENDOR = Mesa Project EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel GL_RENDERER: Gallium 0.4 on NVA8 ... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1211700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])
** Tags added: indeed -- 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/2006669 Title: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915]) Status in mesa package in Ubuntu: New Bug description: GUI hard lock during zoom session and gnome-terminal kern.log shows a mix of errors __ kernel: [ 3627.948545] Asynchronous wait on fence :00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready [i915]) kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in chrome [5521] kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset due to GPU hang kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled ___ I suspect this issue to be upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755 upstream commit: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217 Reproducer: Although I don't have my own reproducer, the upstream mesa reproducer does trigger a hang on my machine. Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it loads, you will see pikachu. Press "S", he will go back. My whole system freezes from this in Wayland, regardless of the browser. Kernel: 6.0.0-1008-oem Mesa: 22.2.5-0ubuntu0.1~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9 Uname: Linux 6.0.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 21:40:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b1a] Subsystem: Dell Device [1028:0b1a] InstallationDate: Installed on 2022-07-13 (211 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: Dell Inc. Precision 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 03M8N5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])
The above referenced commits are committed into mesa 23.0.0. I see references to backports of this onto stable, but I'm not familiar enough with mesa as a project just yet. ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Assignee: Dave Chiluk (chiluk) Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu Jammy) Assignee: (unassigned) => Dave Chiluk (chiluk) ** Changed in: mesa (Ubuntu Lunar) Assignee: Dave Chiluk (chiluk) => (unassigned) -- 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/2006669 Title: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915]) Status in mesa package in Ubuntu: New Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Status in mesa source package in Lunar: New Bug description: GUI hard lock during zoom session and gnome-terminal kern.log shows a mix of errors __ kernel: [ 3627.948545] Asynchronous wait on fence :00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready [i915]) kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in chrome [5521] kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset due to GPU hang kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled ___ I suspect this issue to be upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755 upstream commit: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217 Reproducer: Although I don't have my own reproducer, the upstream mesa reproducer does trigger a hang on my machine. Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it loads, you will see pikachu. Press "S", he will go back. My whole system freezes from this in Wayland, regardless of the browser. Kernel: 6.0.0-1008-oem Mesa: 22.2.5-0ubuntu0.1~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9 Uname: Linux 6.0.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 21:40:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b1a] Subsystem: Dell Device [1028:0b1a] InstallationDate: Installed on 2022-07-13 (211 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: Dell Inc. Precision 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 03M8N5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 versio
[Desktop-packages] [Bug 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])
Looking at mesa git staging/23.0 it looks like 78a75e0d2 and 4c986c58b may also be required. -- 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/2006669 Title: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915]) Status in mesa package in Ubuntu: New Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Status in mesa source package in Lunar: New Bug description: GUI hard lock during zoom session and gnome-terminal kern.log shows a mix of errors __ kernel: [ 3627.948545] Asynchronous wait on fence :00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready [i915]) kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in chrome [5521] kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset due to GPU hang kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled ___ I suspect this issue to be upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755 upstream commit: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217 Reproducer: Although I don't have my own reproducer, the upstream mesa reproducer does trigger a hang on my machine. Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it loads, you will see pikachu. Press "S", he will go back. My whole system freezes from this in Wayland, regardless of the browser. Kernel: 6.0.0-1008-oem Mesa: 22.2.5-0ubuntu0.1~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9 Uname: Linux 6.0.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 21:40:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b1a] Subsystem: Dell Device [1028:0b1a] InstallationDate: Installed on 2022-07-13 (211 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: Dell Inc. Precision 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 03M8N5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubsc
[Desktop-packages] [Bug 2006675] [NEW] Memory leak when hdmi switcher is not sending data/not outputting
Public bug reported: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Main problem: - Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. - - Additional Info: - Ubuntu Version: Ubuntu 20.04 - GNOME Version: GNOME Shell 3.36.9-0ubuntu0.20.04.2 + Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2006675 Title: Memory leak when hdmi switcher is not sending data/not outputting Status in gnome-shell package in Ubuntu: New Bug description: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2006675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.laun
[Desktop-packages] [Bug 2006590] Re: Xorg freeze after rebooting
Thanks for the bug report. Your system is stuck in recovery mode so you will need to access the grub menu (tap escape before Ubuntu starts just after the BIOS) and select the regular kernel to fix it. When done, your /proc/cmdline should not mention either "nomodeset" or "recovery". ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2006590 Title: Xorg freeze after rebooting Status in Ubuntu: Incomplete Bug description: Suddenly this week, my GUI (ubuntu 22.10) does not open, stuck on the console text. I tried to free some space (by uninstall a app), then to check/update the paquets (dkpg). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.86.01 Wed Oct 26 09:12:38 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Feb 8 12:13:40 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 950M] [1025:1094] InstallationDate: Installed on 2022-05-03 (280 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 25a7:fa23 Areson Technology Corp 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.32 dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2006590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006636] Re: Many Cyan Lines Cover Computer Screen
Thanks for the bug report. Please try adding a kernel parameter: i915.enable_psr=0 Please also attach a photo of the problem. ** Summary changed: - Many Cyan Lines Cover Computer Screen + [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2006636 Title: [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen Status in linux package in Ubuntu: Incomplete Bug description: bunch of cyan lines appearing on my screen rapidly, pretty sure its a hardware issue but want to make sure the graphics drivers are up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 13:34:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2023-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K08H3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.sku: xxx123x#ABA dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006636/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006675] Re: Memory leak when hdmi switcher is not sending data/not outputting
Thanks for the bug report. Judging by your system log I am guessing that the Desktop Icons extension is the problem here. Please try disabling the desktop icons extension in the Extensions app and then log in again. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- desktop-icons (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Incomplete ** Tags added: gnome-shell-leak nvidia -- 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/2006675 Title: Memory leak when hdmi switcher is not sending data/not outputting Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006675] Re: Memory leak when hdmi switcher is not sending data/not outputting
Please also consider installing Ubuntu 22.04 as it has a newer desktop icons extension and will perform better in general. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/2006675 Title: Memory leak when hdmi switcher is not sending data/not outputting Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006675] Re: Memory leak when hdmi switcher is not sending data/not outputting
I let it run for a bit, but it appears it isn't just the desktop icons. I will sleep with my set up in the state where the leak happens to fully confirm since it only has gone from 120 to 240 MB. Let me know how I can collect and post data after letting it leak for a while and I will do so when I wake up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/2006675 Title: Memory leak when hdmi switcher is not sending data/not outputting Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006675] Re: Memory leak when hdmi switcher is not sending data/not outputting
You're probably the best judge of whether the problem is fixed, given the conditions you describe are very specific. But an increase of 120 to 240MB is normal and wouldn't be considered a leak. Also remember to only look at the RSS value of the gnome-shell process. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/2006675 Title: Memory leak when hdmi switcher is not sending data/not outputting Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1994027 Title: Can't move window by drag and drop by using touch screen Status in OEM Priority Project: Fix Released Status in XServer: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Released Bug description: [Impact] Users using touch screen could not move windows with 'Drag-n-drop'. This SRU fixes the issue. [Test Plan] 1. Install the 22.04 2. Boot and login 3. Open a folder or terminal 4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch 5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom Pen Expected: Both finger touch and wacom pen work normally. Actual: Wacom Pen works normally, finger touch can not move the windows. [Where problems could occur] It's a regression of upstream packages, https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866 It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e. [Version] xserver-xorg-core 2:21.1.3-2ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp