[Touch-packages] [Bug 2023301] Re: Please merge dbus 1.14.6-1 (main) from debian unstable (main)
This bug was fixed in the package dbus - 1.14.6-1ubuntu1
---
dbus (1.14.6-1ubuntu1) mantic; urgency=medium
* Merge with Debian unstable (LP: #2023301). Remaining changes:
- Add aa-get-connection-apparmor-security-context.patch: This is not
intended for upstream inclusion. It implements a bus method
(GetConnectionAppArmorSecurityContext) to get a connection's AppArmor
security context but upstream D-Bus has recently added a generic way of
getting a connection's security credentials (GetConnectionCredentials).
Ubuntu should carry this patch until packages in the archive are moved
over to the new, generic method of getting a connection's credentials.
- Add dont-stop-dbus.patch: Don't stop D-Bus in the service unit.
- Rework ubuntu/dont-stop-dbus.patch to actually make dbus.service _and_
dbus.socket to not be part of the shutdown transaction. And yet make
it possible to still stop/kill/restart dbus.service if one really
wants to, because it is stuck and stopped responding to any
commands. This allows allows to restart dbus.service with
needrestart. However a finalrd hook might still be needed, to kill
dbus-daemon for good, once we pivot off rootfs.
- Rework d/p/ubuntu/dont-stop-dbus.patch to avoid a deadlock during boot
(LP #1936948)
- debian/dbus.postinst, debian/rules: Don't start D-Bus on package
installation, as that doesn't work any more with dont-stop-dbus.patch.
Instead, start dbus.socket in postinst, which will then start D-Bus
on demand after package installation.
- Prevent dbus from being restarted on upgrade (LP #1962036)
- git configuration changes for Ubuntu (d/gbp.conf, d/.gitignore)
* Removed obsoleted patches:
- d/p/u/concrete-dbus-socket.patch: Add the "real" path used by the apparmor
autopkgtest to the apparmor profile in the test
[merged upstream in 1.14.6]
- d/control: Add M-A: foreign to the new dbus-{session,system}-bus-common
packages to permit the resolver to use them to satisfy i386 dependencies
[merged in debian in 1.14.6-1]
dbus (1.14.6-1) unstable; urgency=medium
* New upstream stable release
- Fixes a denial of service issue that is not relevant for the way
we compile dbus in Debian
* d/copyright: Update
* Standards-Version: 4.6.2 (no changes required)
* d/control: Mark dbus-*-bus-common as Multi-Arch: foreign.
Thanks to Dave Jones / Ubuntu
* d/upstream/metadata: Update Gitlab URLs to preferred format
* Drop migration path from very old debug symbol packages
* Avoid explicitly specifying -Wl,--as-needed linker flag,
which is the default with Debian 12 toolchains
* Remove version constraints unnecessary since Debian 10
-- Olivier Gayot Thu, 08 Jun 2023
17:46:03 +0200
** Changed in: dbus (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/2023301
Title:
Please merge dbus 1.14.6-1 (main) from debian unstable (main)
Status in dbus package in Ubuntu:
Fix Released
Bug description:
Debian has dbus 1.14.6-1 in unstable
Ubuntu has dbus 1.14.4-1ubuntu1 in mantic
Two changes from @waveform have been merged upstream and the relevant
delta can be dropped in Ubuntu.
- d/p/u/concrete-dbus-socket.patch: Add the "real" path used by the apparmor
autopkgtest to the apparmor profile in the test
[merged upstream in 1.14.6]
- d/control: Add M-A: foreign to the new dbus-{session,system}-bus-common
packages to permit the resolver to use them to satisfy i386 dependencies
[merged in debian in 1.14.6-1]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2023301/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2024406] Re: sudo systemctl edit snapd.service fails to save changes
Sorry, I can not reproduce this bug. When I try again after a reboot it works. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2024406 Title: sudo systemctl edit snapd.service fails to save changes Status in systemd package in Ubuntu: Invalid Bug description: IN 22.04 this command sudo systemctl edit snapd.service opens the default editor. Upon exiting, changes are saved In 23.04, exiting gives this error: Editing "/etc/systemd/system/snapd.service.d/override.conf" canceled: temporary file is empty. and changes are not saved. This happens with nano as the default editor, and vim.tiny as the default editor. Explicitly saving changes makes no difference to the problem. I can't find any help resources about this problem. by using systemctl show -p FragmentPath snapd.service I can find the file and edit it manually, as a workaround. ' tim@vm1:/etc/systemd/system$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 tim@vm1:/etc/systemd/system$ apt-cache policy systemd systemd: Installed: 252.5-2ubuntu3 Candidate: 252.5-2ubuntu3 Version table: *** 252.5-2ubuntu3 500 500 http://au.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: systemd 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 20 08:10:15 2023 InstallationDate: Installed on 2023-05-17 (33 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-23-generic root=UUID=c274e419-27dd-47f1-96e5-6fdb35f886ad ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-6.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-6.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2024406/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017169] Re: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2017169 Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Expired Bug description: updating to new release of ubuntu took issue with a modified /etc/systemd/resolved.conf ProblemType: Package DistroRelease: Ubuntu 23.04 Package: systemd-resolved 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 20 20:18:17 2023 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-12 (67 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: systemd Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-20 (0 days ago) modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2023-03-05T13:57:42.686749 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2024403] Re: Accessibility Zoom - display jumping
** Tags added: a11y zoom ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2024403 Title: Accessibility Zoom - display jumping Status in gnome-shell package in Ubuntu: New Bug description: When Accessibility Zoom option is enabled, display is jumping after click. Check video in attachment. I observed this issue also in Ubuntu 22.04 LTS. The problem is very common. The problem is not observed only on websites. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 19 22:12:28 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell GeminiLake [UHD Graphics 605] [1028:080c] InstallationDate: Installed on 2023-05-29 (21 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dell Inc. Wyse 5070 Thin Client ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=93c13196-10b6-4fcd-bcd0-2b6d9fa507e5 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 0K6VXP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd03/06/2023:br1.22:efr1.1:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn0K6VXP:rvrA00:cvnDellInc.:ct3:cvr:sku080C: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2024403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1985057] Re: Camera output freeze when using pipewiresrc
The attachment "pipewire_0.3.48-1ubuntu2.debdiff" 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 Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1985057 Title: Camera output freeze when using pipewiresrc Status in OEM Priority Project: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Triaged Bug description: [Impact] On Dell platform with Microdia Integrated webcam, the Cheese preview is stuck on jammy. The gst-launch-1.0 command suggested by gst-device-monitor-1.0 can reproduce it too. [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is in upstream from 0.3.52 to 0.3.56, and there is no regression found, so the risk is low. [Other Info] Upstream commits: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2024406] [NEW] sudo systemctl edit snapd.service fails to save changes
Public bug reported: IN 22.04 this command sudo systemctl edit snapd.service opens the default editor. Upon exiting, changes are saved In 23.04, exiting gives this error: Editing "/etc/systemd/system/snapd.service.d/override.conf" canceled: temporary file is empty. and changes are not saved. This happens with nano as the default editor, and vim.tiny as the default editor. Explicitly saving changes makes no difference to the problem. I can't find any help resources about this problem. by using systemctl show -p FragmentPath snapd.service I can find the file and edit it manually, as a workaround. ' tim@vm1:/etc/systemd/system$ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 tim@vm1:/etc/systemd/system$ apt-cache policy systemd systemd: Installed: 252.5-2ubuntu3 Candidate: 252.5-2ubuntu3 Version table: *** 252.5-2ubuntu3 500 500 http://au.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: systemd 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 20 08:10:15 2023 InstallationDate: Installed on 2023-05-17 (33 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-23-generic root=UUID=c274e419-27dd-47f1-96e5-6fdb35f886ad ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-6.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-6.2 dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2024406 Title: sudo systemctl edit snapd.service fails to save changes Status in systemd package in Ubuntu: New Bug description: IN 22.04 this command sudo systemctl edit snapd.service opens the default editor. Upon exiting, changes are saved In 23.04, exiting gives this error: Editing "/etc/systemd/system/snapd.service.d/override.conf" canceled: temporary file is empty. and changes are not saved. This happens with nano as the default editor, and vim.tiny as the default editor. Explicitly saving changes makes no difference to the problem. I can't find any help resources about this problem. by using systemctl show -p FragmentPath snapd.service I can find the file and edit it manually, as a workaround. ' tim@vm1:/etc/systemd/system$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 tim@vm1:/etc/systemd/system$ apt-cache policy systemd systemd: Installed: 252.5-2ubuntu3 Candidate: 252.5-2ubuntu3 Version table: *** 252.5-2ubuntu3 500 500 http://au.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: systemd 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 20 08:10:15 2023 InstallationDate: Installed on 2023-05-17 (33 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /:
[Touch-packages] [Bug 2019501] Re: Matebook D15 AMD Ryzen 5500U - Can't find Headphones/Speakers and not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2019501 Title: Matebook D15 AMD Ryzen 5500U - Can't find Headphones/Speakers and not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: My speakers and headphones jack don't work properly: Ubuntu can't find these audio output and can't of course reproduce a sound. Using USB audio card [to connect headphones jack/mic] works, and also I can use the HDMI video and audio output perfectly. I've tested the speakers and headphones with Windows and there's no problem. Found ,I think, the exact same issue online: https://github.com/codepayne/linux-sound-huawei/issues/5 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bleffjack 1726 F pipewire-media- bleffjack 1727 F pulseaudio /dev/snd/pcmC0D3p: bleffjack 1727 F...m pulseaudio /dev/snd/seq:bleffjack 1724 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 14 15:57:05 2023 InstallationDate: Installed on 2022-10-12 (213 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: acp - acp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bleffjack 1726 F pipewire-media- bleffjack 1727 F pulseaudio /dev/snd/pcmC0D3p: bleffjack 1727 F...m pulseaudio /dev/snd/seq:bleffjack 1724 F pipewire Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2022 dmi.bios.release: 2.9 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BOM-WXX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.9 dmi.modalias: dmi:bvnHUAWEI:bvr2.09:bd03/23/2022:br2.9:efr2.9:svnHUAWEI:pnBOM-WXX9:pvrM1010:rvnHUAWEI:rnBOM-WXX9-PCB-B2:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook D dmi.product.name: BOM-WXX9 dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-03-07T11:57:40.023335 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2019501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020560] Re: ssh.service and ssh.socket both running.
I adjusted our documentation for the next Debian upload (which will get merged into Ubuntu at some point and will close this bug then): https://salsa.debian.org/ssh- team/openssh/-/commit/a183f4934873b0dd663177e1772090d1d7a6a631 ** Changed in: openssh (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Colin Watson (cjwatson) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2020560 Title: ssh.service and ssh.socket both running. Status in openssh package in Ubuntu: Fix Committed Bug description: I am running Ubuntu 23.04. The out-of-the-box configuration allows SSH access on port 22. I wish to have ssh listen on both ports 22 and 7022. The ssh_config file contains a comment that Ubuntu now uses socket activated connections and thus ignores the Port and ListenAddress entries. I looked up the ssh socket activation and found that I needed a /etc/systemd/system/ssh.socket.d directory that contains a listen.conf file. I created the directory and the listen.conf file that contains this. [Socket] # Uncomment the following line to turn of listening on port 22. #ListenStream= ListenStream=7022 I then ran these two commands: sudo systemctl daemon-reload sudo systemctl restart ssh I then checked for port listeners: root# lsof -i -P -n | grep LISTEN systemd 1root 454u IPv625979 0t0 TCP *:22 (LISTEN) systemd-r 638 systemd-resolve 14u IPv435332 0t0 TCP 127.0.0.53:53 (LISTEN) systemd-r 638 systemd-resolve 16u IPv435334 0t0 TCP 127.0.0.54:53 (LISTEN) Xtigervnc 941 moose9u IPv422485 0t0 TCP 127.0.0.1:5902 (LISTEN) Xtigervnc 941 moose 10u IPv622486 0t0 TCP [::1]:5902 (LISTEN) cupsd 2258639root6u IPv6 33526334 0t0 TCP [::1]:631 (LISTEN) cupsd 2258639root7u IPv4 33526335 0t0 TCP 127.0.0.1:631 (LISTEN) sshd 3698765root3u IPv625979 0t0 TCP *:22 (LISTEN) I then discovered that both ssh.service and ssh.socket are running: root@/etc/netplan# systemctl status ssh.service ? ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d ??00-socket.conf Active: active (running) since Tue 2023-05-23 11:17:29 EDT; 36min ago TriggeredBy: ? ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 3698763 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Main PID: 3698765 (sshd) Tasks: 3 (limit: 38046) Memory: 3.6M CPU: 206ms CGroup: /system.slice/ssh.service ??3698765 "sshd: /usr/sbin/sshd -D [listener] 1 of 10-100 startups" ??3777496 "sshd: root [priv]" ??3777497 "sshd: root [net]" May 23 11:51:44 alces sshd[3771657]: ... Hint: Some lines were ellipsized, use -l to show in full. root@/etc/netplan# systemctl status ssh.socket ? ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d ??listen.conf Active: active (running) since Mon 2023-05-15 09:23:44 EDT; 1 week 1 day ago Until: Mon 2023-05-15 09:23:44 EDT; 1 week 1 day ago Triggers: ? ssh.service Listen: [::]:22 (Stream) [::]:7022 (Stream) Tasks: 0 (limit: 38046) Memory: 8.0K CPU: 569us CGroup: /system.slice/ssh.socket May 15 09:23:44 alces systemd[1]: ... Hint: Some lines were ellipsized, use -l to show in full. Finally, I found that /lib/systemd/system contains both ssh.service and ssh.socket configurations. ssh.service: [Unit] Description=OpenBSD Secure Shell server Documentation=man:sshd(8) man:sshd_config(5) After=network.target auditd.service ConditionPathExists=!/etc/ssh/sshd_not_to_be_run [Service] EnvironmentFile=-/etc/default/ssh ExecStartPre=/usr/sbin/sshd -t ExecStart=/usr/sbin/sshd -D $SSHD_OPTS ExecReload=/usr/sbin/sshd -t ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartPreventExitStatus=255 Type=notify [Install] WantedBy=multi-user.target Alias=sshd.service ssh.socket: [Unit] Description=OpenBSD Secure Shell server socket Before=sockets.target ConditionPathExists=!/etc/ssh/sshd_not_to_be_run [Socket] ListenStream=22 Accept=no [Install] WantedBy=sockets.target Finally, in /etc/systemd/system there is an ssh.service.d directory that contains the 00-socket.conf file that contains: [Unit] After=ssh.socket
[Touch-packages] [Bug 2024403] Re: Accessibility Zoom - display jumping
One more video. Sorry I am not able to capture image in better way, i have too slow machine. ** Attachment added: "display jumping" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2024403/+attachment/5680833/+files/vid-20230530-195108_iGct36RN.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2024403 Title: Accessibility Zoom - display jumping Status in xorg package in Ubuntu: New Bug description: When Accessibility Zoom option is enabled, display is jumping after click. Check video in attachment. I observed this issue also in Ubuntu 22.04 LTS. The problem is very common. The problem is not observed only on websites. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 19 22:12:28 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell GeminiLake [UHD Graphics 605] [1028:080c] InstallationDate: Installed on 2023-05-29 (21 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dell Inc. Wyse 5070 Thin Client ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=93c13196-10b6-4fcd-bcd0-2b6d9fa507e5 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 0K6VXP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd03/06/2023:br1.22:efr1.1:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn0K6VXP:rvrA00:cvnDellInc.:ct3:cvr:sku080C: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2024403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2024403] [NEW] Accessibility Zoom - display jumping
Public bug reported: When Accessibility Zoom option is enabled, display is jumping after click. Check video in attachment. I observed this issue also in Ubuntu 22.04 LTS. The problem is very common. The problem is not observed only on websites. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 19 22:12:28 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell GeminiLake [UHD Graphics 605] [1028:080c] InstallationDate: Installed on 2023-05-29 (21 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dell Inc. Wyse 5070 Thin Client ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=93c13196-10b6-4fcd-bcd0-2b6d9fa507e5 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 0K6VXP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd03/06/2023:br1.22:efr1.1:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn0K6VXP:rvrA00:cvnDellInc.:ct3:cvr:sku080C: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu wayland-session ** Attachment added: "display jumping" https://bugs.launchpad.net/bugs/2024403/+attachment/5680815/+files/vid-20230530-184842_s6P2qNt1.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2024403 Title: Accessibility Zoom - display jumping Status in xorg package in Ubuntu: New Bug description: When Accessibility Zoom option is enabled, display is jumping after click. Check video in attachment. I observed this issue also in Ubuntu 22.04 LTS. The problem is very common. The problem is not observed only on websites. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 19 22:12:28 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell GeminiLake [UHD Graphics 605] [1028:080c] InstallationDate: Installed on 2023-05-29 (21 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dell Inc. Wyse 5070 Thin Client ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=93c13196-10b6-4fcd-bcd0-2b6d9fa507e5 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 0K6VXP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.1
[Touch-packages] [Bug 1985057] Re: Camera output freeze when using pipewiresrc
Could you provide details on how we ensure the components updates would land in order? What would be the consequence of having the pipewire update landing before gstreamer or the other way around? Do we have confidence it would not impact other components? It sounds a risky changeset to fix cheese which is a known to be buggy component anyway, could we consider an alternative option to deprecate or replace cheese perhaps? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1985057 Title: Camera output freeze when using pipewiresrc Status in OEM Priority Project: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Triaged Bug description: [Impact] On Dell platform with Microdia Integrated webcam, the Cheese preview is stuck on jammy. The gst-launch-1.0 command suggested by gst-device-monitor-1.0 can reproduce it too. [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is in upstream from 0.3.52 to 0.3.56, and there is no regression found, so the risk is low. [Other Info] Upstream commits: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2023455] Re: Pulse audio does not remember output device
I'm reading the module-switch-on-connect blacklist will resolve the issue, but to get pulseaudio 14 I will either need to update to ubuntu 22.04 or manage to install it on ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2023455 Title: Pulse audio does not remember output device Status in pulseaudio package in Ubuntu: New Bug description: My output device keeps switching from "built in analog stereo audio" (my headphones), to HDMI output 2 (one of my monitors), which has no sound. I have to keep switching it back through pavucontrol. I read through a similar issue, but it was reported as fixed by my version. I wonder if there was a regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.4.0-150.167-generic 5.4.233 Uname: Linux 5.4.0-150-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: harry 3113 F pulseaudio /dev/snd/controlC0: harry 3113 F pulseaudio /dev/snd/pcmC0D0p: harry 3113 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 10 16:40:24 2023 InstallationDate: Installed on 2019-01-19 (1603 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-06-23 (1082 days ago) dmi.bios.date: 09/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2023455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2024398] [NEW] wipefs not working as documented
Public bug reported: Working on a new app to do full-disk backup and recovery, I'm having trouble with clearing existing partitions on a target drive. The man page for wipefs says that wipefs -a should wipe all partitions on the drive, but I have a situation where it has a strange result: lsblk reports one partition still remains. Steps to reproduce: - zero the first and last megabytes on the target drive - partition the drive with 'sfdisk /dev/drive is the name of the file attached to this report - wipefs -a - lsblk What I see at this point is a drive with one partition -- oddly 1,3,4,5 and 6 have disappeared, but partition 2 remains. This persists even after doing 'partprobe'. The problem seems to be that something in the label looks like an atari disk label(!!!), and 'wipefs -a' is not clearing it. I can get around the problem by using the --force parameter so: 'wipefs -f -a', and it reports an "atari" signature that was hiding in my DOS MBR somehow. Since I had zeroed the entire disk label area, this has to be a kind of mirage created by a specific configuration of bits. This behavior is a sneaky trap. It took me a very long time to stumble upon the cause and the fix I've just described. It seems best to me if wipefs can detect this issue and clear any odd artifacts like this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: util-linux 2.34-0.1ubuntu9.3 Uname: Linux 5.18.10-76051810-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 19 11:19:03 2023 SourcePackage: util-linux UpgradeStatus: Upgraded to focal on 2022-05-13 (402 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-05-02T14:12:29.908000 ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "sfdisk --dump output" https://bugs.launchpad.net/bugs/2024398/+attachment/5680804/+files/camelot-20210218-sda-dump.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2024398 Title: wipefs not working as documented Status in util-linux package in Ubuntu: New Bug description: Working on a new app to do full-disk backup and recovery, I'm having trouble with clearing existing partitions on a target drive. The man page for wipefs says that wipefs -a should wipe all partitions on the drive, but I have a situation where it has a strange result: lsblk reports one partition still remains. Steps to reproduce: - zero the first and last megabytes on the target drive - partition the drive with 'sfdisk /dev/drive is the name of the file attached to this report - wipefs -a - lsblk What I see at this point is a drive with one partition -- oddly 1,3,4,5 and 6 have disappeared, but partition 2 remains. This persists even after doing 'partprobe'. The problem seems to be that something in the label looks like an atari disk label(!!!), and 'wipefs -a' is not clearing it. I can get around the problem by using the --force parameter so: 'wipefs -f -a', and it reports an "atari" signature that was hiding in my DOS MBR somehow. Since I had zeroed the entire disk label area, this has to be a kind of mirage created by a specific configuration of bits. This behavior is a sneaky trap. It took me a very long time to stumble upon the cause and the fix I've just described. It seems best to me if wipefs can detect this issue and clear any odd artifacts like this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: util-linux 2.34-0.1ubuntu9.3 Uname: Linux 5.18.10-76051810-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 19 11:19:03 2023 SourcePackage: util-linux UpgradeStatus: Upgraded to focal on 2022-05-13 (402 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-05-02T14:12:29.908000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2024398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2019424] Re: Heimdal can be synced
Hi @Steve/@Vorlon Could you help me identify where I might make a mistake in my investigation in Heimdal? I am writing that comment after a month again, because I would love to gain more knowledge and know where I was wrong. Thank you in advance -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2019424 Title: Heimdal can be synced Status in heimdal package in Ubuntu: Confirmed Bug description: After heimdal merge process, I was trying to figure out if the delta that is still not dropped is required or not. So, to test it, I have created 2 PPAs, one in which lto is disabled, and the second one, where the lto is enabled. I have built them and downloaded the debs for i386 and amd64. Then I have compared amd64 deb from PPA1 with amd64 deb from PPA2. The same story with i386. The binary dependencies were identical. There is no difference between the files. So in that case, the delta can possibly be dropped. The package has already been merged again, with the change: heimdal (7.8.git20221117.28daf24+dfsg-2ubuntu1) mantic; urgency=low * Merge from Debian unstable. Remaining changes: - d/rules: Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different than i386 resulting in different files on amd64 and i386. -- Steve Langasek Tue, 02 May 2023 09:56:10 +0200 heimdal (7.8.git20221117.28daf24+dfsg-1ubuntu1) lunar; urgency=low * Merge from Debian unstable. Remaining changes: - d/rules: Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different than i386 resulting in different files on amd64 and i386. (LP #1934936) -- Steve Langasek Tue, 24 Jan 2023 19:14:54 -0800 Due to this, syncpackage doesn't run. The package can be sync'd next time it comes up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2019424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2022927] Re: Busybox mount fails to mount Snaps
Thanks @paelzer I'll try to follow it up on the BB mailing list -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2022927 Title: Busybox mount fails to mount Snaps Status in busybox package in Ubuntu: New Bug description: Snapd tries to mount squashfs Snaps with non-standard mount flags like "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to userspace programs that a given mount should not be shown in a list of mounted partitions/filesystems. Busybox does not support these flags, and so fails with "Invalid argument". $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test mount: mounting test on /tmp/test failed: Invalid argument These flags can likely be be safely ignored, as they don't actually affect the functionality of the mount. This goes for all mount options starting with "x-", as these generally denote non-standard mount option "extensions". I've created a patch against Busybox which adds an optional configuration item to ignore all mount options beginning with "x-". An additional verbose option has also been added to enable the ability to report that the mount flags have been ignored, rather than silently ignoring them. This is a requirement for a customer project, where we are limited to using Busybox (due to coreutils' GPL-3.0 licence) but would also require using Snaps like checkbox for testing and verification. This was posted on the Busybox mailing list a few months ago (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html) but patch acceptance there seems to take quite a long time, and we need this for the customer. A PPA containing the patched Busybox version is available on the project's Launchpad team: https://launchpad.net/~nemos- team/+archive/ubuntu/ppa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2022927] Re: Busybox mount fails to mount Snaps
This is somewhat opinion, so I'm happy to be convinced, but without either - upstream progress to merge it there or - a good explanation why you think that wouldn't lock us in into hard to maintain delta and issues to users => This won't be uploaded IMHO. When that upstream response or explanation is ready please post it and subscribe ubuntu-sponsors again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2022927 Title: Busybox mount fails to mount Snaps Status in busybox package in Ubuntu: New Bug description: Snapd tries to mount squashfs Snaps with non-standard mount flags like "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to userspace programs that a given mount should not be shown in a list of mounted partitions/filesystems. Busybox does not support these flags, and so fails with "Invalid argument". $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test mount: mounting test on /tmp/test failed: Invalid argument These flags can likely be be safely ignored, as they don't actually affect the functionality of the mount. This goes for all mount options starting with "x-", as these generally denote non-standard mount option "extensions". I've created a patch against Busybox which adds an optional configuration item to ignore all mount options beginning with "x-". An additional verbose option has also been added to enable the ability to report that the mount flags have been ignored, rather than silently ignoring them. This is a requirement for a customer project, where we are limited to using Busybox (due to coreutils' GPL-3.0 licence) but would also require using Snaps like checkbox for testing and verification. This was posted on the Busybox mailing list a few months ago (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html) but patch acceptance there seems to take quite a long time, and we need this for the customer. A PPA containing the patched Busybox version is available on the project's Launchpad team: https://launchpad.net/~nemos- team/+archive/ubuntu/ppa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created
Thanks Simon, those are two good catches! The "file" package/command is seeded in the Ubuntu desktop flavours: $ seeded-in-ubuntu file file (from file) is seeded in: edubuntu: daily-live kubuntu: daily-live lubuntu: daily-live ubuntu-budgie: daily-legacy, daily-live ubuntu-mate: daily-live ubuntu-server: daily-live, daily-preinstalled ubuntu-unity: daily-live ubuntu: daily-canary, daily-legacy, daily-live, daily-preinstalled ubuntucinnamon: daily-live ubuntukylin: daily-live ubuntustudio: dvd xubuntu: daily-live, daily-minimal The subshell issue should be fixed with this commit: https://git.launchpad.net/network-manager/commit/?id=781778e6b7dd6677ef308ad0a3f8f5dfed1e1c63 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2010561 Title: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created Status in netplan: Invalid Status in network-manager package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a WiFi adapter. (I used Lubuntu Lunar.) 2. Connect to WiFi and install all updates. 3. Enable the Netplan Everywhere PPA and install the updated NetworkManager from it (further details at https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420?u=arraybolt3) 4. When the installation finishes, run "sudo netplan get". Expected result: Networking information related to the WiFi connection should appear in the "sudo netplan get" output. Actual result: "sudo netplan get" returns the following: ** (process:4088): WARNING **: 12:41:41.394; Permissions for /etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration should NOT be accessible by others. network: version: 2 renderer: NetworkManager End of output. Additionally, the /etc/netplan folder does not contain files that I would expect to be there that would contain the networking info. Additional information: If I disconnect from WiFi, then delete my WiFi connection entirely in nmtui, and *then* reconnect to the same WiFi network, "sudo netplan get" returns the expected networking information. /etc/netplan is also properly populated after doing this. This bug seems like it will probably cause unintended behavior after an upgrade from 23.04 (which uses normal NetworkManager) to 23.10 (which is supposed to be using the Netplan Everywhere NetworkManager). People probably won't know to entirely delete the WiFi and other connections and then reconnect them in order for the netplan output to be usable. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2010561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2022927] Re: Busybox mount fails to mount Snaps
Debian is at 1.36 already, but without your change landing upstream that doesn't help us :-/ (This was released before on January 2023 anyway) The upstream contribubution was nice, but stalled with http://lists.busybox.net/pipermail/busybox/2023-March/090211.html It didn't come up again in April-June :-/ Was there any follow up to avoid this being Ubuntu delta forever? Especially with something that changes behavior so that e.g. guides and howtos would behave differently between linux variants you'd usually want upstreams buy-in to avoid maintenance nightmare. Would you mind following up with them and summarizing here about that progress to get it upstream? P.S. by now you might want to set "mantic" in your debdiff changelog stanza as that is what someone will eventually sponsor it to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2022927 Title: Busybox mount fails to mount Snaps Status in busybox package in Ubuntu: New Bug description: Snapd tries to mount squashfs Snaps with non-standard mount flags like "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to userspace programs that a given mount should not be shown in a list of mounted partitions/filesystems. Busybox does not support these flags, and so fails with "Invalid argument". $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test mount: mounting test on /tmp/test failed: Invalid argument These flags can likely be be safely ignored, as they don't actually affect the functionality of the mount. This goes for all mount options starting with "x-", as these generally denote non-standard mount option "extensions". I've created a patch against Busybox which adds an optional configuration item to ignore all mount options beginning with "x-". An additional verbose option has also been added to enable the ability to report that the mount flags have been ignored, rather than silently ignoring them. This is a requirement for a customer project, where we are limited to using Busybox (due to coreutils' GPL-3.0 licence) but would also require using Snaps like checkbox for testing and verification. This was posted on the Busybox mailing list a few months ago (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html) but patch acceptance there seems to take quite a long time, and we need this for the customer. A PPA containing the patched Busybox version is available on the project's Launchpad team: https://launchpad.net/~nemos- team/+archive/ubuntu/ppa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2019212] Re: Backport packages for 22.04.3 HWE stack
** Description changed: - WIP - [Impact] The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3 mesa - - new major release (23.0.x) - - new HW support... + - new major release (23.0.4) [Test case] - Install the new mesa on various hw, see that everything still works like before or better. + Install the new mesa on various hw configs, check that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 23.0.x in order to minimize the chance for those. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2019212 Title: Backport packages for 22.04.3 HWE stack Status in mesa package in Ubuntu: Invalid Status in mesa source package in Jammy: In Progress Bug description: [Impact] The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3 mesa - new major release (23.0.4) [Test case] Install the new mesa on various hw configs, check that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 23.0.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2019212/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020604] Update Released
The verification of the Stable Release Update for mesa 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 Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: Invalid Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics
This bug was fixed in the package mesa - 22.2.5-0ubuntu0.1~22.04.3 --- mesa (22.2.5-0ubuntu0.1~22.04.3) jammy; urgency=medium * rules: Set VERSION so that it also includes the packaging revision. (LP: #2020604) -- Timo Aaltonen Wed, 31 May 2023 11:21:54 +0300 ** Changed in: mesa (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: Invalid Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color
** Description changed:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers are
affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-PDF_Printer-
PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
- editor. Chcke whether it contains a line
+ editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints about
color printing. So the regression potential is very low.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Committed
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When
[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color
Fixed in Mantic via cups 2.4.5-0ubuntu1:
cups (2.4.5-0ubuntu1) mantic; urgency=medium
* Update to new upstream version 2.4.5.
- Fixes color printing on printers with "CMYK" choice instead of "RGB"
in "ColorModel" option of their PPD (Upstream issues #451 and #500,
LP: 1971242).
* Merge from Debian unstable. Remaining changes:
- Added "--enable-snapped-clients" to the "./configure" options to use
the correct Snap mediation mode for an unsnapped cupsd, like provided
by this package.
- In the AppArmor profile allow CUPS to access (/var)/run/snapd.socket
to allow cupsd to determine which interfaces a snapped client
is plugging.
- Build-depend on libapparmor-dev, libsnapd-glib-dev, needed for
Snap mediation.
- Added fully automatic generation of PPD option setting presets to
be applied depending on the settings of the job IPP attributes
"print-color-mode", "print-quality", and "print-content-optimize".
This allows easy control of any printer with only standard IPP
attributes, as for example from a phone (functionality overtaken
from cups-filters, mot (yet) upstream in CUPS).
- In debian/rules updated ./configure arguments from --enable-gnutls to
--with-tls=gnutls. Now libcups has support for all hash types again,
especially can provide sha2-256 to PAPPL.
- When polling capabilities of a driverless printer via
get-printer-attributes IPP request, do a separate poll of the
media-col-database attribute in case it did not get obtained by the
first polls.
- In libcupsimage2 recommend libcupsfilters2 instead of libcupsfilters1.
* Manually refreshed patch 9100-ppd-cache-add-auto-presets.patch.
* Removed patches included upstream:
- 9110-create-local-printer-localhost-fix.patch
- CVE-2022-26691-2.patch
- snapd-glib-2.patch
- poll-media-col-database-separately.patch
- CVE-2023-32324.patch
cups (2.4.2-4) unstable; urgency=medium
* CVE-2023-32324
A heap buffer overflow vulnerability would allow a remote attacker to
lauch a dos attack.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-26691
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32324
** Changed in: cups (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Committed
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[
