[Touch-packages] [Bug 1961460] Re: My laptop shuts off randomly after displaying a black screen
Thanks for the bug report. It's the 'nouveau' kernel driver crashing here. To avoid that please use the 'Additional Drivers' app to install the proprietary Nvidia driver instead. ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Summary changed: - My laptop shuts off randomly after displaying a black screen + My laptop shuts off randomly after displaying a black screen (nouveau crashes in nvkm_pmu_reset) ** Tags added: nouveau -- 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/1961460 Title: My laptop shuts off randomly after displaying a black screen (nouveau crashes in nvkm_pmu_reset) Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Ubuntu 20.04.4 LTS N: Unable to locate package pkgname My latop screen turns black randomly and it has to do something with graphics driver. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 19 07:06:41 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 (Whiskey Lake) [1025:129a] Subsystem: Acer Incorporated [ALI] GP108BM [GeForce MX250] [1025:129a] InstallationDate: Installed on 2022-02-18 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Acer Swift SF314-55G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=8e45e071-d3dc-4ff9-9a0b-b18cd73b8609 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2018 dmi.bios.release: 1.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.07 dmi.board.asset.tag: Default string dmi.board.name: MILLER_WL dmi.board.vendor: WL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.07:bd12/24/2018:br1.7:efr1.8:svnAcer:pnSwiftSF314-55G:pvrV1.07:rvnWL:rnMILLER_WL:rvrV1.07:cvnAcer:ct10:cvrV1.07:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-55G dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961460/+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 1961488] Re: radeon module unloaded with 20.04 after upgrade from 18.04
Xorg's radeon module unloaded because you have disabled the radeon hardware with the 'nomodeset' kernel parameter. You need to remove that. Make sure you're not accidentally booting in recovery mode. ** Tags added: radeon ** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu) ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Invalid -- 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/1961488 Title: radeon module unloaded with 20.04 after upgrade from 18.04 Status in xserver-xorg-video-ati package in Ubuntu: Invalid Bug description: I upgraded a computer running Ubuntu 18.04 with AMD ATI RS482/RS485 Radeon Xpress 1100/1150 without problem. After upgrade to 20.04, resolution is virtual size of 1400x1050 which doesn't fit in screen. With 18.04 I had in xorg.o.log [ 6647.940] (II) RADEON(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 6647.940] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 [ 6647.940] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [ 6647.940] (==) RADEON(0): Default visual is TrueColor [ 6647.940] (==) RADEON(0): RGB weight 888 [ 6647.940] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) [ 6647.940] (--) RADEON(0): Chipset: "ATI Radeon 3100 Graphics" (ChipID = 0x9611) [ 6647.940] (II) Loading sub module "fb" [ 6647.940] (II) LoadModule: "fb" [ 6647.960] (II) Loading /usr/lib/xorg/modules/libfb.so [ 6647.971] (II) Module fb: vendor="X.Org Foundation" [ 6647.971]compiled for 1.18.4, module version = 1.0.0 [ 6647.971]ABI class: X.Org ANSI C Emulation, version 0.4 [ 6647.971] (II) Loading sub module "dri2" [ 6647.971] (II) LoadModule: "dri2" [ 6647.971] (II) Module "dri2" already built-in [ 6647.971] (II) Loading sub module "exa" [ 6647.971] (II) LoadModule: "exa" [ 6647.972] (II) Loading /usr/lib/xorg/modules/libexa.so [ 6647.976] (II) Module exa: vendor="X.Org Foundation" [ 6647.976]compiled for 1.18.4, module version = 2.6.0 [ 6647.976]ABI class: X.Org Video Driver, version 20.0 [ 6647.976] (II) RADEON(0): KMS Color Tiling: enabled [ 6647.976] (II) RADEON(0): KMS Color Tiling 2D: enabled [ 6647.976] (II) RADEON(0): KMS Pageflipping: enabled [ 6647.976] (II) RADEON(0): SwapBuffers wait for vsync: enabled [ 6648.008] (II) RADEON(0): Output VGA-0 has no monitor section [...] and now [ 789.949] (II) FBDEV(0): using default device [ 789.949] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32 [ 789.949] (==) FBDEV(0): RGB weight 888 [ 789.949] (==) FBDEV(0): Default visual is TrueColor [ 789.949] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) [ 789.949] (II) FBDEV(0): hardware: VESA VGA (video memory: 5760kB) [ 789.949] (DB) xf86MergeOutputClassOptions unsupported bus type 0 [ 789.949] (II) FBDEV(0): checking modes against framebuffer device... [ 789.949] (II) FBDEV(0): checking modes against monitor... [ 789.949] (II) FBDEV(0): Virtual size is 1400x1050 (pitch 1400) [ 789.949] (**) FBDEV(0): Built-in mode "current": 147.0 MHz, 83.2 kHz, 77.4 Hz [ 789.949] (II) FBDEV(0): Modeline "current"x0.0 147.04 1400 1432 1600 1768 1050 1054 1058 1074 -hsync -vsync -csync (83.2 kHz b) [ 789.949] (==) FBDEV(0): DPI set to (96, 96) [ 789.949] (II) Loading sub module "fb" [ 789.949] (II) LoadModule: "fb" [ 789.949] (II) Loading /usr/lib/xorg/modules/libfb.so [ 789.950] (II) Module fb: vendor="X.Org Foundation" [ 789.950]compiled for 1.20.13, module version = 1.0.0 [ 789.950]ABI class: X.Org ANSI C Emulation, version 0.4 [ 789.950] (**) FBDEV(0): using shadow framebuffer [ 789.950] (II) Loading sub module "shadow" [ 789.950] (II) LoadModule: "shadow" [ 789.962] (II) Loading /usr/lib/xorg/modules/libshadow.so [ 789.962] (II) Module shadow: vendor="X.Org Foundation" [ 789.962]compiled for 1.20.13, module version = 1.1.0 [ 789.962]ABI class: X.Org ANSI C Emulation, version 0.4 [ 789.962] (II) UnloadModule: "radeon" [ 789.962] (II) Unloading radeon [ 789.963] (II) UnloadModule: "modesetting" [ 789.963] (II) Unloading modesetting [...] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Feb 19 18:29:21 2022 DistUpgraded: 2021-03-08 13:38:14,332 DEBUG package
[Touch-packages] [Bug 1947920] Re: tracker-miner-f 100% CPU and slows system down
*** This bug is a duplicate of bug 1961540 *** https://bugs.launchpad.net/bugs/1961540 ** This bug has been marked a duplicate of bug 1961540 tracker-miner-fs-3 massive CPU usage and system slowdown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1947920 Title: tracker-miner-f 100% CPU and slows system down Status in tracker package in Ubuntu: New Bug description: tracker-miner-f has been using 100% CPU and my system making it almost unresponsive. This happens around once a month or so when I boot up. It sometimes lasts for a number of days (or a number of resets) until the system becomes responsive again. The command "tracker status" always shows the same thing: "Estimated less than one second left" although it appears that everything is already indexed because the file and folder counts do not increase. Even so tracker-miner-f is still showing 100% CPU inspiron@Inspiron-7348:~$ tracker status Currently indexed: 101154 files, 16046 folders Remaining space on database partition: 160.5 GB (64.11%) Data is still being indexed: Estimated less than one second left inspiron@Inspiron-7348:~$ tracker status Currently indexed: 101155 files, 16045 folders Remaining space on database partition: 161.1 GB (64.31%) Data is still being indexed: Estimated 01h 19m 03s left ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: tracker 2.3.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 08:25:58 2021 InstallationDate: Installed on 2021-06-28 (114 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) UPDATE I have now reset the tracker and it seems to be going through and indexing everything again. tracker reset --hard Now tracker-miner-f has re-indexed everything and tracker-extract and tracker-store are running. UPDATE 2 The tracker reset completed indexing everything and the went into idle state. However when rebooting, tracker-miner-f went to 100% CPU once again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1947920/+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 1953052] Re: In Jammy sound level reset after reboot
> TL;DR: pipewire-pulse and PulseAudio should *not* be installed at the same time as they serve the same function and applications don't know the difference. This is not the case at least for the default Ubuntu flavor (w/ GNOME). $ curl -s https://cdimages.ubuntu.com/daily-live/current/jammy-desktop-amd64.manifest | egrep 'pipewire|pulseaudio' gstreamer1.0-pipewire:amd64 0.3.44-1 gstreamer1.0-pulseaudio:amd64 1.18.5-1ubuntu3 libpipewire-0.3-0:amd64 0.3.44-1 libpipewire-0.3-common 0.3.44-1 libpipewire-0.3-modules:amd64 0.3.44-1 pipewire:amd64 0.3.44-1 pipewire-bin0.3.44-1 pipewire-media-session 0.4.1-2 pulseaudio 1:15.0+dfsg1-1ubuntu6 pulseaudio-module-bluetooth 1:15.0+dfsg1-1ubuntu6 pulseaudio-utils1:15.0+dfsg1-1ubuntu6 -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5
[Touch-packages] [Bug 1961542] Re: libsmartcols: Revert back to previous behaviour of non-shell parsable column output (lsblk -P)
The attachment "debdiff for util-linux on Jammy" 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 util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1961542 Title: libsmartcols: Revert back to previous behaviour of non-shell parsable column output (lsblk -P) Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Jammy: In Progress Bug description: [Impact] util-linux 2.37 in Jammy has introduced some new behaviour for lsblk and similar tools which depend on libsmartcols. This switched the -P / --pairs parameter from printing column names as normal, to changing the names to shell compatible names instead. e.g. lsblk -P now outputs LOG_SEC instead of LOG-SEC. The change broke some core tooling which rely on on the output of lsblk -P, most notably, curtin and MAAS, but I am sure there will be more applications affected. Affected MAAS users will see the following traceback when attempting to deploy 22.04: Traceback (most recent call last): File "/curtin/curtin/block/__init__.py", line 785, in get_blockdev_sector_size logical = info[parent]['LOG-SEC'] KeyError: 'LOG-SEC' 'LOG-SEC' curtin: Installation failed with exception: Unexpected error while running This is documented in MAAS bug 1956613. MAAS decided to fix it by changing from -P to -J, in the following commit: https://git.launchpad.net/maas/commit/?id=e2c01963430e6837198a54bc1eadf3efc9fdd9a2 Curtin now checks for MAJ_MIN, and changes it back to MAJ:MIN in: https://github.com/canonical/curtin/commit/ce811db127fe1ce46498b83615f8faed8c7dfeb6 The issue is that these commits are not tagged to any MAAS release, and users would be forced to upgrade MAAS to the latest stable release when available if they want to deploy 22.04. There are many users out there that don't want to upgrade MAAS, so returning to the previous column output is the most desirable solution. [Testcase] On a Jammy install, simply run lsblk with either -P or --pairs: $ sudo lsblk -P ... NAME="sda" MAJ_MIN="8:0" RM="0" SIZE="465.8G" RO="0" TYPE="disk" MOUNTPOINTS="" ... Affected installs will see MAJ_MIN. There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf326660-test If you install it, you will see MAJ:MIN, just like it is on Impish and previous. [Where problems could occur] We are changing the column output for -P and --pairs for the following applications: * lsblk * findmnt * lsipc If any application has been modified to depend on the new column output, it will break. I don't have any examples of something that will break, because MAAS and curtin were modified such that they would be compatible with both column name formats. It should be noted that the manpage documents that lsblk output can change at any time: > The default output, as well as the default output from options like --fs and --topology, is subject to change. > So whenever possible, you should avoid using default outputs in your scripts. > Always explicitly define expected columns by using --output columns-list and --list in environments where a stable output is required. If a regression should occur, we will need to fix up these affected packages also. [Other info] The change came about when a user asked upstream to make -P / --pairs shell parsable, in Issue 1201 upstream: https://github.com/util-linux/util-linux/issues/1201 Karel Zak obliged, and it was implemented in the following commit: commit 58b510e5805d8350c31bfb81a47bcd38ea9fdd7e From: Karel Zak Date: Thu, 3 Dec 2020 12:14:10 +0100 Subject: libsmartcols: sanitize variable names on export output Link: https://github.com/util-linux/util-linux/commit/58b510e5805d8350c31bfb81a47bcd38ea9fdd7e I wrote to Karel Zak with the regressions introduced by changing the format, and asked to revert back, and instead implement the shell parsable logic as a new parameter. This happened in upstream issue 1594: https://github.com/util-linux/util-linux/issues/1594 Karel Zak was happy to oblige again, and we now have the following commits: 338ad4a93 findmnt: commit missing flag 0f843ab64 lsblk: update --help output for -y eba05f308 lsipc: add -y,--shell 152c17aa4 findmnt: add -y,--shell 9c7e81ff1 lslogins: add -y,--shell 25fb0638a lsblk: add -y/--shell
[Touch-packages] [Bug 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade
This bug was fixed in the package debconf - 1.5.79ubuntu1 --- debconf (1.5.79ubuntu1) jammy; urgency=medium * dpkg-reconfigure: fix restart of services declared with --no-restart-after-upgrade (LP: #1959054) -- Dave Jones Sun, 20 Feb 2022 14:42:49 + ** Changed in: debconf (Ubuntu Jammy) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1959054 Title: debhelper restarts services marked --no-restart-on-upgrade Status in debconf package in Ubuntu: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in docker.io package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Fix Committed Status in debconf source package in Jammy: Fix Released Status in debhelper source package in Jammy: Fix Released Status in docker.io source package in Jammy: Fix Released Status in libvirt source package in Jammy: Fix Committed Status in debconf package in Debian: New Status in debhelper package in Debian: New Bug description: Debian bug #994204 (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that results in the postinst being generated in such a fashion that services marked --no-stop-on-upgrade (or its deprecated alias --no- restart-on-upgrade), restart anyway. Please note: this is nothing to do with the --no-restart-after-upgrade flag (which is, somewhat confusingly IMO, unrelated). I've confirmed that the flaw appears to be present in the jammy version of debhelper (though not impish) and that packages generated with it appear to contain the flawed postinst (I first encountered this whilst working on the open-iscsi merge), though I haven't yet managed to test that the flaw exhibits itself on upgrade (though I'd say from the presence of the flaw in the postinst, that it's a reasonable inference that it will). In dbus (the merge of which I'm currently working on), Debian has worked around this but given I've now run into two affected packages (open-iscsi and dbus), only one of which has a work-around, I'd much rather we got debhelper fixed up and rebuilt affected packages? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1959054/+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 1953052] Re: In Jammy sound level reset after reboot
I don't think the points I raised are upstream ones and I wouldn't take them upstream myself. I think it's good (in the long term) and appropriate that PipeWire upstream is a daemon, just not appropriate in Ubuntu 22.04 since we've decided to stick with PulseAudio. Hence the configuration changes I mention would be Ubuntu-specific. But if we can just not install pipewire-media-session by default then that would be better than any config changes. -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on
[Touch-packages] [Bug 1956603] Re: /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym .....
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: x11-xkb-utils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1956603 Title: /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym . Status in xlibs: Unknown Status in libx11 package in Ubuntu: Fix Committed Status in x11-xkb-utils package in Ubuntu: Confirmed Bug description: Get lot of such warnings into Jammy logged; Actual libx11 is 1.7.2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86MediaRepeat /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Images /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NotificationCenter /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86PickupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86HangupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn_Esc /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86FnRightShift /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric0 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric1 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric3 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric4 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric5 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric6 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric7 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric8 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric9 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericStar /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericPound /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericA /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericB /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericC /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericD /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraFocus /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86WPSButton /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomIn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomOut /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraLeft /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraRight /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOff /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantToggle /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86LightsToggle --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed
[Touch-packages] [Bug 1956603] Re: /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym .....
Looks like we also need an update to x11-xkb-utils to get https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/merge_requests/6 ** Also affects: x11-xkb-utils (Ubuntu) Importance: Undecided Status: New ** Description changed: - Get lot of such warnings into Jammy logged; this makes freezes and browser crashes. + Get lot of such warnings into Jammy logged; Actual libx11 is 1.7.2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86MediaRepeat /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Images /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NotificationCenter /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86PickupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86HangupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn_Esc /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86FnRightShift /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric0 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric1 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric3 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric4 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric5 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric6 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric7 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric8 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric9 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericStar /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericPound /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericA /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericB /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericC /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericD /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraFocus /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86WPSButton /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomIn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomOut /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraLeft /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraRight /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOff /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantToggle /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86LightsToggle - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu DkmsStatus: - fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed (WARNING! Diff between built and installed module!) - fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed (WARNING! Diff between built and installed module!) - fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed (WARNING! Diff between built and installed module!) + fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed (WARNING! Diff between built and installed module!) + fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic,
[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
Daniel, I disagree. PipeWire is meant to be a *drop-in replacement* for PulseAudio. Applications that recognize PulseAudio are supposed to use it instead if it's available in lieu of PulseAudio. Both options need to be available, otherwise the entire goal of PipeWire's audio capabilities of unifying Linux audio under one audio server are lost. While this might still be a bug, which is the entire reason I didn't follow through with closing it, I still believe this may be a packaging issue more than anything. The points you bring up are probably upstream ones, so I'd take it up there. https://gitlab.freedesktop.org/pipewire/pipewire/ ** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785
[Touch-packages] [Bug 1956603] Re: /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym .....
** Bug watch added: gitlab.freedesktop.org/xorg/lib/libx11/-/issues #137 https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/137 ** Also affects: xlibs via https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/137 Importance: Unknown Status: Unknown ** Tags added: fixed-in-1.7.3 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1956603 Title: /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym . Status in xlibs: Unknown Status in libx11 package in Ubuntu: New Bug description: Get lot of such warnings into Jammy logged; this makes freezes and browser crashes. Actual libx11 is 1.7.2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86MediaRepeat /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Images /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NotificationCenter /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86PickupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86HangupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn_Esc /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86FnRightShift /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric0 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric1 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric3 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric4 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric5 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric6 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric7 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric8 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric9 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericStar /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericPound /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericA /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericB /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericC /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericD /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraFocus /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86WPSButton /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomIn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomOut /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraLeft /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraRight /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOff /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantToggle /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86LightsToggle --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/21.12.00,
[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
This is definitely a bug and one we need to solve before the masses start using jammy. So just closing it wouldn't be helpful. I'm reminded a little of bug 1897965. Maybe we need either: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1897965/comments/16 or to modify pipewire-media-session.service with something like: /usr/bin/pipewire-media-session -d bluez5,alsa-seq,alsa-pcm,alsa-acp That way PulseAudio is always the only one trying to control the hardware. Alternatively; don't install pipewire-media-session by default. So long as it's not needed for Wayland screencasting/recording like at least some of Pipewire is :S -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74
[Touch-packages] [Bug 1961542] Re: libsmartcols: Revert back to previous behaviour of non-shell parsable column output (lsblk -P)
Attached is a debdiff for Jammy util-linux. ** Patch added: "debdiff for util-linux on Jammy" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1961542/+attachment/5562373/+files/lp1961542_jammy.debdiff -- 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/1961542 Title: libsmartcols: Revert back to previous behaviour of non-shell parsable column output (lsblk -P) Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Jammy: In Progress Bug description: [Impact] util-linux 2.37 in Jammy has introduced some new behaviour for lsblk and similar tools which depend on libsmartcols. This switched the -P / --pairs parameter from printing column names as normal, to changing the names to shell compatible names instead. e.g. lsblk -P now outputs LOG_SEC instead of LOG-SEC. The change broke some core tooling which rely on on the output of lsblk -P, most notably, curtin and MAAS, but I am sure there will be more applications affected. Affected MAAS users will see the following traceback when attempting to deploy 22.04: Traceback (most recent call last): File "/curtin/curtin/block/__init__.py", line 785, in get_blockdev_sector_size logical = info[parent]['LOG-SEC'] KeyError: 'LOG-SEC' 'LOG-SEC' curtin: Installation failed with exception: Unexpected error while running This is documented in MAAS bug 1956613. MAAS decided to fix it by changing from -P to -J, in the following commit: https://git.launchpad.net/maas/commit/?id=e2c01963430e6837198a54bc1eadf3efc9fdd9a2 Curtin now checks for MAJ_MIN, and changes it back to MAJ:MIN in: https://github.com/canonical/curtin/commit/ce811db127fe1ce46498b83615f8faed8c7dfeb6 The issue is that these commits are not tagged to any MAAS release, and users would be forced to upgrade MAAS to the latest stable release when available if they want to deploy 22.04. There are many users out there that don't want to upgrade MAAS, so returning to the previous column output is the most desirable solution. [Testcase] On a Jammy install, simply run lsblk with either -P or --pairs: $ sudo lsblk -P ... NAME="sda" MAJ_MIN="8:0" RM="0" SIZE="465.8G" RO="0" TYPE="disk" MOUNTPOINTS="" ... Affected installs will see MAJ_MIN. There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf326660-test If you install it, you will see MAJ:MIN, just like it is on Impish and previous. [Where problems could occur] We are changing the column output for -P and --pairs for the following applications: * lsblk * findmnt * lsipc If any application has been modified to depend on the new column output, it will break. I don't have any examples of something that will break, because MAAS and curtin were modified such that they would be compatible with both column name formats. It should be noted that the manpage documents that lsblk output can change at any time: > The default output, as well as the default output from options like --fs and --topology, is subject to change. > So whenever possible, you should avoid using default outputs in your scripts. > Always explicitly define expected columns by using --output columns-list and --list in environments where a stable output is required. If a regression should occur, we will need to fix up these affected packages also. [Other info] The change came about when a user asked upstream to make -P / --pairs shell parsable, in Issue 1201 upstream: https://github.com/util-linux/util-linux/issues/1201 Karel Zak obliged, and it was implemented in the following commit: commit 58b510e5805d8350c31bfb81a47bcd38ea9fdd7e From: Karel Zak Date: Thu, 3 Dec 2020 12:14:10 +0100 Subject: libsmartcols: sanitize variable names on export output Link: https://github.com/util-linux/util-linux/commit/58b510e5805d8350c31bfb81a47bcd38ea9fdd7e I wrote to Karel Zak with the regressions introduced by changing the format, and asked to revert back, and instead implement the shell parsable logic as a new parameter. This happened in upstream issue 1594: https://github.com/util-linux/util-linux/issues/1594 Karel Zak was happy to oblige again, and we now have the following commits: 338ad4a93 findmnt: commit missing flag 0f843ab64 lsblk: update --help output for -y eba05f308 lsipc: add -y,--shell 152c17aa4 findmnt: add -y,--shell 9c7e81ff1 lslogins: add -y,--shell 25fb0638a lsblk: add -y/--shell 39679ea0c lsfd: use new libsmartcols functions 6fd0e3590 column: use new libsmartcols functions 0b3c2e80d include/carefulputc: remove unused function 3b5db50f7 libsmartcols: change "export" behavior, add "shellvar" flag While we got the intended behaviour, these commits won't land until
[Touch-packages] [Bug 989961] Re: Provide a gmake symlink
This bug was fixed in the package make-dfsg - 4.3-4.1build1 --- make-dfsg (4.3-4.1build1) jammy; urgency=medium * No-change rebuild to hopefully address LP: #1939973 * The -4.1 upload also restores the broken gmake symlink (LP: #989961) make-dfsg (4.3-4.1) unstable; urgency=medium * Non-maintainer upload. * make-guile: fix broken symlinks /usr/bin/gmake and /usr/share/man/man1/gmake.1.gz. (Closes: #986240) -- Julian Andres Klode Tue, 15 Feb 2022 16:32:21 +0100 ** Changed in: make-dfsg (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 make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/989961 Title: Provide a gmake symlink Status in make-dfsg package in Ubuntu: Fix Released Bug description: Some, albeit older or proprietary software, expects a gmake symlink for gnu make. Can this be provided? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/989961/+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 1939973] Re: make 4.3-4.1 triggers build failures
This bug was fixed in the package make-dfsg - 4.3-4.1build1 --- make-dfsg (4.3-4.1build1) jammy; urgency=medium * No-change rebuild to hopefully address LP: #1939973 * The -4.1 upload also restores the broken gmake symlink (LP: #989961) make-dfsg (4.3-4.1) unstable; urgency=medium * Non-maintainer upload. * make-guile: fix broken symlinks /usr/bin/gmake and /usr/share/man/man1/gmake.1.gz. (Closes: #986240) -- Julian Andres Klode Tue, 15 Feb 2022 16:32:21 +0100 ** Changed in: make-dfsg (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 make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1939973 Title: make 4.3-4.1 triggers build failures Status in make-dfsg package in Ubuntu: Fix Released Bug description: trying to rebuild cross-toolchain-base from https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages triggers a build failure: [...] START stamp-dir/init-binutils tar -x -f /usr/src/binutils/binutils-2.37.tar.xz set -e; cd binutils-2.37 ; cp -a /usr/src/binutils/debian/ . ; if [ -n "$(grep -v '^\#' /<>/debian/patches/binutils/series)" ]; then QUILT_PATCHES=/<>/debian/patches/binutils quilt --quiltrc /dev/null push -a; fi; rm -rf .pc cd binutils-2.37 ; env -i CROSS_ARCHS="amd64 i386 s390x ppc64el arm64 armhf armel powerpc" debian/rules stamps/control make: dpkg-architecture: No such file or directory make: lsb_release: No such file or directory make: lsb_release: No such file or directory make: pwd: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory debian/rules:163: *** unexpected source package name: . Stop. make: *** [debian/rules:215: stamp-dir/init-binutils] Error 2 dpkg-buildpackage.pl: error: debian/rules build subprocess returned exit status 2 working around by omitting the -i option to env, or by setting PATH explicitly. Reverting to the version in the release pocket lets the c-t-b- build succeed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1939973/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
Yoga Slim 9 14ITL5 Ubuntu 20.04 kernel 5.13.0-30-generic No sound on front speakers -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1961542] [NEW] libsmartcols: Revert back to previous behaviour of non-shell parsable column output (lsblk -P)
Public bug reported: [Impact] util-linux 2.37 in Jammy has introduced some new behaviour for lsblk and similar tools which depend on libsmartcols. This switched the -P / --pairs parameter from printing column names as normal, to changing the names to shell compatible names instead. e.g. lsblk -P now outputs LOG_SEC instead of LOG-SEC. The change broke some core tooling which rely on on the output of lsblk -P, most notably, curtin and MAAS, but I am sure there will be more applications affected. Affected MAAS users will see the following traceback when attempting to deploy 22.04: Traceback (most recent call last): File "/curtin/curtin/block/__init__.py", line 785, in get_blockdev_sector_size logical = info[parent]['LOG-SEC'] KeyError: 'LOG-SEC' 'LOG-SEC' curtin: Installation failed with exception: Unexpected error while running This is documented in MAAS bug 1956613. MAAS decided to fix it by changing from -P to -J, in the following commit: https://git.launchpad.net/maas/commit/?id=e2c01963430e6837198a54bc1eadf3efc9fdd9a2 Curtin now checks for MAJ_MIN, and changes it back to MAJ:MIN in: https://github.com/canonical/curtin/commit/ce811db127fe1ce46498b83615f8faed8c7dfeb6 The issue is that these commits are not tagged to any MAAS release, and users would be forced to upgrade MAAS to the latest stable release when available if they want to deploy 22.04. There are many users out there that don't want to upgrade MAAS, so returning to the previous column output is the most desirable solution. [Testcase] On a Jammy install, simply run lsblk with either -P or --pairs: $ sudo lsblk -P ... NAME="sda" MAJ_MIN="8:0" RM="0" SIZE="465.8G" RO="0" TYPE="disk" MOUNTPOINTS="" ... Affected installs will see MAJ_MIN. There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf326660-test If you install it, you will see MAJ:MIN, just like it is on Impish and previous. [Where problems could occur] We are changing the column output for -P and --pairs for the following applications: * lsblk * findmnt * lsipc If any application has been modified to depend on the new column output, it will break. I don't have any examples of something that will break, because MAAS and curtin were modified such that they would be compatible with both column name formats. It should be noted that the manpage documents that lsblk output can change at any time: > The default output, as well as the default output from options like --fs and > --topology, is subject to change. > So whenever possible, you should avoid using default outputs in your scripts. > Always explicitly define expected columns by using --output columns-list and > --list in environments where a stable output is required. If a regression should occur, we will need to fix up these affected packages also. [Other info] The change came about when a user asked upstream to make -P / --pairs shell parsable, in Issue 1201 upstream: https://github.com/util-linux/util-linux/issues/1201 Karel Zak obliged, and it was implemented in the following commit: commit 58b510e5805d8350c31bfb81a47bcd38ea9fdd7e From: Karel Zak Date: Thu, 3 Dec 2020 12:14:10 +0100 Subject: libsmartcols: sanitize variable names on export output Link: https://github.com/util-linux/util-linux/commit/58b510e5805d8350c31bfb81a47bcd38ea9fdd7e I wrote to Karel Zak with the regressions introduced by changing the format, and asked to revert back, and instead implement the shell parsable logic as a new parameter. This happened in upstream issue 1594: https://github.com/util-linux/util-linux/issues/1594 Karel Zak was happy to oblige again, and we now have the following commits: 338ad4a93 findmnt: commit missing flag 0f843ab64 lsblk: update --help output for -y eba05f308 lsipc: add -y,--shell 152c17aa4 findmnt: add -y,--shell 9c7e81ff1 lslogins: add -y,--shell 25fb0638a lsblk: add -y/--shell 39679ea0c lsfd: use new libsmartcols functions 6fd0e3590 column: use new libsmartcols functions 0b3c2e80d include/carefulputc: remove unused function 3b5db50f7 libsmartcols: change "export" behavior, add "shellvar" flag While we got the intended behaviour, these commits won't land until util-linux 2.38, which will be after Jammy releases, and the other issue is that this changes a significant amount of code, like nearly 1k lines, and is spread over 10+ commits. I wrote to ubuntu-devel asking for advice, on either 1) not changing anything 2) backporting the 10+ new commits, or 3) simply reverting the commit which changed the behaviour. https://lists.ubuntu.com/archives/ubuntu-devel/2022-February/041870.html ubuntu-devel had strong support for option (3). Hence, we will revert the below commit to ensure Jammy can be deployed on all existing MAAS releases. 58b510e580 libsmartcols: sanitize variable names on export output ** Affects: util-linux (Ubuntu) Importance: High Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Affects:
[Touch-packages] [Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices Status in gst-plugins-bad1.0 package in Ubuntu: Confirmed Status in gstreamer1.0 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After the announcements of PulseAudio 15 and Gstreamer 1.20, which both advertised LDAC and AptX (HD) support, I expected that jammy (22.04) would support those codecs. Though in reality it seems that something is missing, gstreamer reports that those codecs are supported but "pactl [...] list-codec" only lists sbc (and variants). Checking here https://packages.ubuntu.com/jammy/pulseaudio-module- bluetooth it seems that PulseAudio is not built with gstreamer support, is that the current blocker? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1960307/+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 1961530] [NEW] CUPS driver does not send anything to printer during test print
Public bug reported: Downloaded and installed Turboprint driver for Canon iP90 but balked at the high ($55 USD) price. The 30 day free trial ended and I found that the iP90 printer would operate after installing the iP110 driver (with the iP90-Cups or the iP90-Gutenprint drivers, it would only output 25 or so blank pages with faint printing at the top of the page). Canon didn't make a Linux driver for the iP90 printer that I can find. Today, tried to uninstall Turboprint but it seems to be all over my printer config setup. As part of that, I uninstalled the 'working' iP110 driver setup. Deleted it from the printer window. Now when I install the CUPS generic iP110 driver, and try to print a test page, it does nothing. Doesn't even wink the printers activity light and doesn't show the print job in the print queue. So it seems that Turboprint insinuated itself into the system in a way that prevents it's total removal and is somehow blocking the CUPS drivers. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: cups 2.3.3op2-7ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Feb 20 10:26:57 2022 Lpstat: device for Canon-iP90: usb://Canon/iP90?serial=31A4B2 MachineType: Gigabyte Technology Co., Ltd. A520M S2H Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-iP90.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-iP90.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=c201ceca-9f5a-4845-b650-e68fc9d5230f ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to impish on 2021-10-15 (128 days ago) dmi.bios.date: 07/27/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: A520M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnA520MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA520MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: A520 MB dmi.product.name: A520M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1961530 Title: CUPS driver does not send anything to printer during test print Status in cups package in Ubuntu: New Bug description: Downloaded and installed Turboprint driver for Canon iP90 but balked at the high ($55 USD) price. The 30 day free trial ended and I found that the iP90 printer would operate after installing the iP110 driver (with the iP90-Cups or the iP90-Gutenprint drivers, it would only output 25 or so blank pages with faint printing at the top of the page). Canon didn't make a Linux driver for the iP90 printer that I can find. Today, tried to uninstall Turboprint but it seems to be all over my printer config setup. As part of that, I uninstalled the 'working' iP110 driver setup. Deleted it from the printer window. Now when I install the CUPS generic iP110 driver, and try to print a test page, it does nothing. Doesn't even wink the printers activity light and doesn't show the print job in the print queue. So it seems that Turboprint insinuated itself into the system in a way that prevents it's total removal and is somehow blocking the CUPS drivers. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: cups 2.3.3op2-7ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Feb 20 10:26:57 2022 Lpstat: device for Canon-iP90: usb://Canon/iP90?serial=31A4B2 MachineType: Gigabyte Technology Co., Ltd. A520M S2H Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-iP90.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-iP90.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Touch-packages] [Bug 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade
Excellent, happy with that. I'm attaching a debdiff for the debconf change, and will see if I can rustle up a sponsor on Monday to finally put all this to bed! ** Patch added: "1-1959054.debdiff" https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1959054/+attachment/5562301/+files/1-1959054.debdiff ** Changed in: debconf (Ubuntu Jammy) Status: New => Confirmed ** Changed in: debconf (Ubuntu Jammy) Assignee: Dave Jones (waveform) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1959054 Title: debhelper restarts services marked --no-restart-on-upgrade Status in debconf package in Ubuntu: Confirmed Status in debhelper package in Ubuntu: Fix Released Status in docker.io package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Fix Committed Status in debconf source package in Jammy: Confirmed Status in debhelper source package in Jammy: Fix Released Status in docker.io source package in Jammy: Fix Released Status in libvirt source package in Jammy: Fix Committed Status in debconf package in Debian: New Status in debhelper package in Debian: New Bug description: Debian bug #994204 (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that results in the postinst being generated in such a fashion that services marked --no-stop-on-upgrade (or its deprecated alias --no- restart-on-upgrade), restart anyway. Please note: this is nothing to do with the --no-restart-after-upgrade flag (which is, somewhat confusingly IMO, unrelated). I've confirmed that the flaw appears to be present in the jammy version of debhelper (though not impish) and that packages generated with it appear to contain the flawed postinst (I first encountered this whilst working on the open-iscsi merge), though I haven't yet managed to test that the flaw exhibits itself on upgrade (though I'd say from the presence of the flaw in the postinst, that it's a reasonable inference that it will). In dbus (the merge of which I'm currently working on), Debian has worked around this but given I've now run into two affected packages (open-iscsi and dbus), only one of which has a work-around, I'd much rather we got debhelper fixed up and rebuilt affected packages? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1959054/+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 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade
It worked ii debconf1.5.79ubuntu1 all Debian configuration management system root@j-slapd-reconfigure:~# pidof slapd 105004 root@j-slapd-reconfigure:~# dpkg-reconfigure -fnoninteractive -pcritical slapd Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.5.11+dfsg-1~exp1ubuntu3... done. Moving old database directory to /var/backups: - directory unknown... done. Creating initial configuration... done. Creating LDAP directory... done. root@j-slapd-reconfigure:~# pidof slapd 105415 root@j-slapd-reconfigure:~# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1959054 Title: debhelper restarts services marked --no-restart-on-upgrade Status in debconf package in Ubuntu: New Status in debhelper package in Ubuntu: Fix Released Status in docker.io package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Fix Committed Status in debconf source package in Jammy: New Status in debhelper source package in Jammy: Fix Released Status in docker.io source package in Jammy: Fix Released Status in libvirt source package in Jammy: Fix Committed Status in debconf package in Debian: New Status in debhelper package in Debian: New Bug description: Debian bug #994204 (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that results in the postinst being generated in such a fashion that services marked --no-stop-on-upgrade (or its deprecated alias --no- restart-on-upgrade), restart anyway. Please note: this is nothing to do with the --no-restart-after-upgrade flag (which is, somewhat confusingly IMO, unrelated). I've confirmed that the flaw appears to be present in the jammy version of debhelper (though not impish) and that packages generated with it appear to contain the flawed postinst (I first encountered this whilst working on the open-iscsi merge), though I haven't yet managed to test that the flaw exhibits itself on upgrade (though I'd say from the presence of the flaw in the postinst, that it's a reasonable inference that it will). In dbus (the merge of which I'm currently working on), Debian has worked around this but given I've now run into two affected packages (open-iscsi and dbus), only one of which has a work-around, I'd much rather we got debhelper fixed up and rebuilt affected packages? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1959054/+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 1953052] Re: In Jammy sound level reset after reboot
Ubuntu Studio lead here. We have been very closely watching the development of PipeWire as it is of interest to a large amount of our user base in the Audio Production world. Please note that PipeWire, in its current iteration, is meant to be a drop-in replacement for both PulseAudio and Jack sound servers. Having PulseAudio and PipeWire (specifically the pipewire-pulse package) installed simultaneously is asking for trouble as the PulseAudio implementation of PipeWire is feature-complete. I'm actually surprised that the pipeiwire-pulse package doesn't have a "Provides:" or "Conflicts:" line for PulseAudio as it's literally a drop-in replacement. For this reason, this is *strongly* looking like a support request more than an actual bug and I'm tempted to close it as invalid (support requests are not allowed on a bug tracker). Either that or a bug against the pipewire source package for not having the "Provides:" or "Conflicts:" lines mentioned above. TL;DR: pipewire-pulse and PulseAudio should *not* be installed at the same time as they serve the same function and applications don't know the difference. -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size:
[Touch-packages] [Bug 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade
Gladly! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1959054 Title: debhelper restarts services marked --no-restart-on-upgrade Status in debconf package in Ubuntu: New Status in debhelper package in Ubuntu: Fix Released Status in docker.io package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Fix Committed Status in debconf source package in Jammy: New Status in debhelper source package in Jammy: Fix Released Status in docker.io source package in Jammy: Fix Released Status in libvirt source package in Jammy: Fix Committed Status in debconf package in Debian: New Status in debhelper package in Debian: New Bug description: Debian bug #994204 (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that results in the postinst being generated in such a fashion that services marked --no-stop-on-upgrade (or its deprecated alias --no- restart-on-upgrade), restart anyway. Please note: this is nothing to do with the --no-restart-after-upgrade flag (which is, somewhat confusingly IMO, unrelated). I've confirmed that the flaw appears to be present in the jammy version of debhelper (though not impish) and that packages generated with it appear to contain the flawed postinst (I first encountered this whilst working on the open-iscsi merge), though I haven't yet managed to test that the flaw exhibits itself on upgrade (though I'd say from the presence of the flaw in the postinst, that it's a reasonable inference that it will). In dbus (the merge of which I'm currently working on), Debian has worked around this but given I've now run into two affected packages (open-iscsi and dbus), only one of which has a work-around, I'd much rather we got debhelper fixed up and rebuilt affected packages? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1959054/+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 1953052] Re: In Jammy sound level reset after reboot
Corrado, this is still not ideal - while it appears to work at the moment, having two audio servers with their own idea of volumes would probably cause trouble going on. -- 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/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) Package: gnome-control-center 1:41.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: wayland-session jammy Uname: Linux 5.13.0-19-generic x86_64
[Touch-packages] [Bug 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade
** Changed in: debconf (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1959054 Title: debhelper restarts services marked --no-restart-on-upgrade Status in debconf package in Ubuntu: New Status in debhelper package in Ubuntu: Fix Released Status in docker.io package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Fix Committed Status in debconf source package in Jammy: New Status in debhelper source package in Jammy: Fix Released Status in docker.io source package in Jammy: Fix Released Status in libvirt source package in Jammy: Fix Committed Status in debconf package in Debian: New Status in debhelper package in Debian: New Bug description: Debian bug #994204 (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that results in the postinst being generated in such a fashion that services marked --no-stop-on-upgrade (or its deprecated alias --no- restart-on-upgrade), restart anyway. Please note: this is nothing to do with the --no-restart-after-upgrade flag (which is, somewhat confusingly IMO, unrelated). I've confirmed that the flaw appears to be present in the jammy version of debhelper (though not impish) and that packages generated with it appear to contain the flawed postinst (I first encountered this whilst working on the open-iscsi merge), though I haven't yet managed to test that the flaw exhibits itself on upgrade (though I'd say from the presence of the flaw in the postinst, that it's a reasonable inference that it will). In dbus (the merge of which I'm currently working on), Debian has worked around this but given I've now run into two affected packages (open-iscsi and dbus), only one of which has a work-around, I'd much rather we got debhelper fixed up and rebuilt affected packages? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1959054/+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 1959211] Re: Please merge dbus 1.12.20-3 from Debian unstable
** Changed in: dbus (Ubuntu) Status: New => Confirmed -- 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/1959211 Title: Please merge dbus 1.12.20-3 from Debian unstable Status in dbus package in Ubuntu: Confirmed Bug description: Please merge dbus 1.12.20-3 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
** Also affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices Status in gst-plugins-bad1.0 package in Ubuntu: Confirmed Status in gstreamer1.0 package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: After the announcements of PulseAudio 15 and Gstreamer 1.20, which both advertised LDAC and AptX (HD) support, I expected that jammy (22.04) would support those codecs. Though in reality it seems that something is missing, gstreamer reports that those codecs are supported but "pactl [...] list-codec" only lists sbc (and variants). Checking here https://packages.ubuntu.com/jammy/pulseaudio-module- bluetooth it seems that PulseAudio is not built with gstreamer support, is that the current blocker? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1960307/+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 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade
@ahasenack Could you try the debconf version from [1]? I've patched that with the same fix that I've proposed upstream [2]. I'll add the relevant debian bug here too. I realize this is *technically* a separate issue, but it's all so interconnected and related that I'd prefer to keep it all in one place. [1]: https://launchpad.net/~waveform/+archive/ubuntu/dh-merge [2]: https://salsa.debian.org/pkg-debconf/debconf/-/merge_requests/10 ** Bug watch added: Debian Bug tracker #1006147 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006147 ** Also affects: debconf (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006147 Importance: Unknown Status: Unknown ** Changed in: docker.io (Ubuntu Jammy) Status: Confirmed => Fix Released ** Changed in: libvirt (Ubuntu Jammy) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1959054 Title: debhelper restarts services marked --no-restart-on-upgrade Status in debconf package in Ubuntu: New Status in debhelper package in Ubuntu: Fix Released Status in docker.io package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Fix Committed Status in debconf source package in Jammy: New Status in debhelper source package in Jammy: Fix Released Status in docker.io source package in Jammy: Fix Released Status in libvirt source package in Jammy: Fix Committed Status in debconf package in Debian: Unknown Status in debhelper package in Debian: New Bug description: Debian bug #994204 (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that results in the postinst being generated in such a fashion that services marked --no-stop-on-upgrade (or its deprecated alias --no- restart-on-upgrade), restart anyway. Please note: this is nothing to do with the --no-restart-after-upgrade flag (which is, somewhat confusingly IMO, unrelated). I've confirmed that the flaw appears to be present in the jammy version of debhelper (though not impish) and that packages generated with it appear to contain the flawed postinst (I first encountered this whilst working on the open-iscsi merge), though I haven't yet managed to test that the flaw exhibits itself on upgrade (though I'd say from the presence of the flaw in the postinst, that it's a reasonable inference that it will). In dbus (the merge of which I'm currently working on), Debian has worked around this but given I've now run into two affected packages (open-iscsi and dbus), only one of which has a work-around, I'd much rather we got debhelper fixed up and rebuilt affected packages? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1959054/+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 1958019]
Note to *Ubuntu users, every time I install a fresh, self compiled kernel, the computer locks up on first boot. All subsequent boots work fine. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
*Ubuntu version: 1) install kernel build tools: (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev dkms libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git 2) clone the kernel from github and checkout to v5.17 branch (Rather large, multiple GB's): * git clone https://github.com/torvalds/linux.git * cd linux * git checkout v5.17-rc4 3) get the patch and install it: get the patch form this site and save to "linux" directory: (top right corner "series" button) and use the following "git am ..." line to apply the patch: https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4-sbind...@opensource.cirrus.com/ * git am Support-Spi-in-i2c-multi-instantiate-driver.patch 4) load current kernel config and change configuration then run the following scripts/config commands: * make olddefconfig * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI * ./scripts/config --disable CONFIG_DEBUG_INFO * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" 6) build the kernel * make -j 16 7) install the kernel * sudo make module_install * sudo make install -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
Hi, Yes, you are right. You don't need to get that series patch if you use the linux-next tree or just wait for the next linux kernel release. Also, you could just: $ make olddefconfig $ ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE $ ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C $ ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI Instead of using menuconfig step. Thanks Lucas Tanure -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to henry.hormaza from comment #560) > well finally found the way to make it work in the legion 7 2021 AMD > (16achg6)... > > this is a short tutorial to build the kernel with the patch (I've done it on > fedora 35): > > 1) make sure you have all the tools to build the kernel > (https://fedoraproject.org/wiki/Building_a_custom_kernel): > > * sudo dnf install fedpkg fedora-packager rpmdevtools ncurses-devel pesign > grubby git > > 2) clone the kernel from github and checkout to v5.17 branch: > > * git clone https://github.com/torvalds/linux.git > * cd linux > * git checkout v5.17-rc4 > * git pull > > 3) get the patch and install it: > > get the patch form this site: (top rigth corner "series" button): > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > sbind...@opensource.cirrus.com/ > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > 4) load your old kernel config > > * make olddefconfig > > 5) change configuration at menuconfig as Howard Chu explained in his > previous post > > * menuconfig -> Device Drivers / X86 Platform Specific Device Drivers / I2C > and SPI multi instantiate pseudo device driver --> Enable this > > 6) build the kernel > > * make -j 16 > > 7) install the kernel > > * sudo make module_install > * sudo make install > > 8) reboot and enjoy internal speakers > > > (if anyone sees a mistake or something that I did wrong please feel free to > correct these steps) > > Thank you to everyone who worked on this patch legion 7 2021 AMD (16achg6) Can anyone do this tutorial for UBUNTU please? -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
well finally found the way to make it work in the legion 7 2021 AMD (16achg6)... this is a short tutorial to build the kernel with the patch (I've done it on fedora 35): 1) make sure you have all the tools to build the kernel (https://fedoraproject.org/wiki/Building_a_custom_kernel): * sudo dnf install fedpkg fedora-packager rpmdevtools ncurses-devel pesign grubby git 2) clone the kernel from github and checkout to v5.17 branch: * git clone https://github.com/torvalds/linux.git * cd linux * git checkout v5.17-rc4 * git pull 3) get the patch and install it: get the patch form this site: (top rigth corner "series" button): https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4-sbind...@opensource.cirrus.com/ * git am Support-Spi-in-i2c-multi-instantiate-driver.patch 4) load your old kernel config * make olddefconfig 5) change configuration at menuconfig as Howard Chu explained in his previous post * menuconfig -> Device Drivers / X86 Platform Specific Device Drivers / I2C and SPI multi instantiate pseudo device driver --> Enable this 6) build the kernel * make -j 16 7) install the kernel * sudo make module_install * sudo make install 8) reboot and enjoy internal speakers (if anyone sees a mistake or something that I did wrong please feel free to correct these steps) Thank you to everyone who worked on this patch -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1953719] Re: logrotate.service fails because it starts before winbind.service
Command: /usr/bin/smbcontrol winbindd reload-config return value 1 if there is no winbind process. I believe solution maybe to change in /etc/logrotate.d/winbind from postrotate if [ -x /usr/bin/smbcontrol ]; then /usr/bin/smbcontrol winbindd reload-config elif [ -f /run/samba/winbindd.pid ]; then kill -HUP `cat /run/samba/winbindd.pid` fi endscript to postrotate if [ -f /run/samba/winbindd.pid ]; then if [ -x /usr/bin/smbcontrol ]; then /usr/bin/smbcontrol winbindd reload-config else kill -HUP `cat /run/samba/winbindd.pid` fi fi endscript -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1953719 Title: logrotate.service fails because it starts before winbind.service Status in logrotate package in Ubuntu: Confirmed Bug description: I have started to play with Prometheus on my Ubuntu 20.04.3. You can configure Prometheus to alert you when a systemd service fails, and in this way I noticed a problem with the logrotate.service immediately after booting the system. I looked with Cockpit, and Cockpit was reporting logrotate.service as "Failed to start". This is the log for logrotate.service : 8<8<8< Dez 09 08:00:56 rdiez3 systemd[1]: Starting Rotate log files... Dez 09 08:00:58 rdiez3 logrotate[1760]: Can't find pid for destination 'winbindd' Dez 09 08:00:58 rdiez3 logrotate[1069]: error: error running non-shared postrotate script for /var/log/samba/log.winbindd of '/var/log/samba/log.winbindd ' Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Failed with result 'exit-code'. Dez 09 08:00:58 rdiez3 systemd[1]: Failed to start Rotate log files. 8<8<8< I then looked at winbind.service , which was fine: 8<8<8< Dez 09 08:01:01 rdiez3 systemd[1]: Starting Samba Winbind Daemon... Dez 09 08:01:01 rdiez3 systemd[1]: Started Samba Winbind Daemon. 8<8<8< But I noticed that winbind.service started after logrotate.service . I wonder whether this is a service dependency issue. I am using this PC only during normal working hours, and logrotate.timer is set to run at midnight, when the computer will never be turned on. The worry is that this problem could effectively cause the complete log rotation to stop working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1953719/+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 1953719] Re: logrotate.service fails because it starts before winbind.service
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: logrotate (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1953719 Title: logrotate.service fails because it starts before winbind.service Status in logrotate package in Ubuntu: Confirmed Bug description: I have started to play with Prometheus on my Ubuntu 20.04.3. You can configure Prometheus to alert you when a systemd service fails, and in this way I noticed a problem with the logrotate.service immediately after booting the system. I looked with Cockpit, and Cockpit was reporting logrotate.service as "Failed to start". This is the log for logrotate.service : 8<8<8< Dez 09 08:00:56 rdiez3 systemd[1]: Starting Rotate log files... Dez 09 08:00:58 rdiez3 logrotate[1760]: Can't find pid for destination 'winbindd' Dez 09 08:00:58 rdiez3 logrotate[1069]: error: error running non-shared postrotate script for /var/log/samba/log.winbindd of '/var/log/samba/log.winbindd ' Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Failed with result 'exit-code'. Dez 09 08:00:58 rdiez3 systemd[1]: Failed to start Rotate log files. 8<8<8< I then looked at winbind.service , which was fine: 8<8<8< Dez 09 08:01:01 rdiez3 systemd[1]: Starting Samba Winbind Daemon... Dez 09 08:01:01 rdiez3 systemd[1]: Started Samba Winbind Daemon. 8<8<8< But I noticed that winbind.service started after logrotate.service . I wonder whether this is a service dependency issue. I am using this PC only during normal working hours, and logrotate.timer is set to run at midnight, when the computer will never be turned on. The worry is that this problem could effectively cause the complete log rotation to stop working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1953719/+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 1960508] Re: glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386
Workaround for this bug is: # dpkg --configure -a # apt --fix-broken install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960508 Title: glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386 Status in glib2.0 package in Ubuntu: Confirmed Bug description: After running "sudo apt upgrade" and approving the listed packages, the following error occurred after unpacking a number of packages: dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libmount1 (>= 2.35.2-7~); however: Package libmount1:i386 is not configured yet. output from "dpkg-reconfigure libmount1:i386": /usr/sbin/dpkg-reconfigure: libmount1:i386 is broken or not fully installed output from "sudo apt install libmount1:i386": Reading package lists... Done Building dependency tree... Done Reading state information... Done libmount1:i386 is already the newest version (2.36.1-8ubuntu2.2). ... output from "sudo apt reinstall libmount1:i386": E: Internal Error, No file name for libmount1:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1960508/+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 1961517] [NEW] package base-files 11ubuntu5.5 failed to install/upgrade: end of file on stdin at conffile prompt
Public bug reported: package base-files 11ubuntu5.5 failed to install/upgrade: end of file on stdin at conffile prompt ProblemType: Package DistroRelease: Ubuntu 20.04 Package: base-files 11ubuntu5.5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: base-files:amd64: Install base-files:amd64: Configure NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Feb 20 01:05:04 2022 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2022-02-05 (14 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: base-files Title: package base-files 11ubuntu5.5 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.issue: I've read & consent to terms in IS user agreem't. \n Ubuntu 20.04.3 LTS \n \l mtime.conffile..etc.issue: 2022-02-18T21:37:57.039602 ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1961517 Title: package base-files 11ubuntu5.5 failed to install/upgrade: end of file on stdin at conffile prompt Status in base-files package in Ubuntu: New Bug description: package base-files 11ubuntu5.5 failed to install/upgrade: end of file on stdin at conffile prompt ProblemType: Package DistroRelease: Ubuntu 20.04 Package: base-files 11ubuntu5.5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: base-files:amd64: Install base-files:amd64: Configure NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Feb 20 01:05:04 2022 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2022-02-05 (14 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: base-files Title: package base-files 11ubuntu5.5 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.issue: I've read & consent to terms in IS user agreem't. \n Ubuntu 20.04.3 LTS \n \l mtime.conffile..etc.issue: 2022-02-18T21:37:57.039602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1961517/+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 1926256] Re: Pasted text in the terminal is always highlighted and selected
Still a problem for Ubuntu MATE 22.04 LTS. Please fix it on distro level. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1926256 Title: Pasted text in the terminal is always highlighted and selected Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Invalid Status in mate-terminal package in Ubuntu: Confirmed Status in readline package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+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
