[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese
Thanks handsome_feng! The Kylin discussion makes me confident that it's fine for Lubuntu as well. The Lubuntu situation is different, though, since im-config is disabled by default unless a Chinese locale is in effect. This discourse topic comes to mind: https://discourse.ubuntu.com/t/default-im-config-configuration/17136 I'm still interested in talking with some Lubuntu developer on that. But the outcome of such a discussion would affect other packages but language-selector, so I just pushed and uploaded the proposed change. ** Changed in: language-selector (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: In Progress Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: Fix Committed Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1926547] Re: Add Dell Privacy Mic Mute Key mapping
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in systemd package in Ubuntu: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1929087] Re: sfdisk refuses to write GPT table between sector 34 and 2047
A secondary bug manifests from this, whereby sfdisk chokes on its own
output and therefore cannot restore its own backup. E.g. suppose
another tool is used to put a BIOS boot partition from sector 34 to
2047, as follows:
$ sgdisk --clear -a 1 --new=1:34:2047 -c 1:"BIOS boot"
--typecode=1:$(sgdisk --list-types | sed -ne
's/.*\(\).bios.*/\1/gip') /dev/sdb
That works fine, and from that we can run "sfdisk -d /dev/sdb >
dump.txt". But when dump.txt is fed back into sfdisk, it pukes. Yet
the docs claim "It is recommended to save the layout of your devices.
sfdisk supports two ways." .. "Use the --dump option to save a
description of the device layout to a text file." .. "This can later be
restored by: sfdisk /dev/sda < sda.dump"
It's actually a security issue, because someone can make an non-
restorable backup and have the false sense of security that it is
restorable. They wouldn't necessary test restoration either because
that's a destructive process.
** Description changed:
According to https://wiki.archlinux.org/title/GRUB#BIOS_systems, it's
both legal and interesting to place the BIOS BOOT partition from sector
34 to sector 2047, as follows:
$ sudo sfdisk --no-act -f --label gpt /dev/sdb << EOF
start= 34, size=2013, name=bios, type=$(sfdisk
--label gpt -T | awk '{IGNORECASE = 1;} /bios boot/{print $1}')
start= 2048, size=12582912, name=swap, type=$(sfdisk
--label gpt -T | awk '{IGNORECASE = 1;} /linux swap/{print $1}')
EOF
The output is:
/dev/sdb1: Sector 34 already used.
Failed to add #1 partition: Numerical result out of range
Leaving.
- It's a false error. As a workaround, users must omit the BIOS BOOT
- partition then use gdisk to insert it manually. This was uncovered in
- 2015 and perhaps never reported to a bug tracker because it's still
- broken. See https://www.spinics.net/lists/util-linux-ng/msg11253.html
+ It's a false error. As a workaround, users must use parted or sgdisk
+ instead. (note fdisk & gdisk are also broken in the same way)
+
+ This bug was uncovered in 2015 and perhaps never reported to a bug
+ tracker because it's still broken. See https://www.spinics.net/lists
+ /util-linux-ng/msg11253.html
--
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/1929087
Title:
sfdisk refuses to write GPT table between sector 34 and 2047
Status in util-linux package in Ubuntu:
New
Bug description:
According to https://wiki.archlinux.org/title/GRUB#BIOS_systems, it's
both legal and interesting to place the BIOS BOOT partition from
sector 34 to sector 2047, as follows:
$ sudo sfdisk --no-act -f --label gpt /dev/sdb << EOF
start= 34, size=2013, name=bios, type=$(sfdisk
--label gpt -T | awk '{IGNORECASE = 1;} /bios boot/{print $1}')
start= 2048, size=12582912, name=swap, type=$(sfdisk
--label gpt -T | awk '{IGNORECASE = 1;} /linux swap/{print $1}')
EOF
The output is:
/dev/sdb1: Sector 34 already used.
Failed to add #1 partition: Numerical result out of range
Leaving.
It's a false error. As a workaround, users must use parted or sgdisk
instead. (note fdisk & gdisk are also broken in the same way)
This bug was uncovered in 2015 and perhaps never reported to a bug
tracker because it's still broken. See https://www.spinics.net/lists
/util-linux-ng/msg11253.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1929087/+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 1928360] Re: Switch to Fcitx 5 for Chinese
> Does this mean that the proposed changes to pkg_depends is fine from > an Ubuntu Kylin POV, and that no further changes are needed? Yes, Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: In Progress Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: In Progress Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1929114] Re: Resolução da minha tela.
Thanks for the bug report. It appears the answer is in your kernel log: [ 25.771227] NVRM: The NVIDIA NVS 3100M GPU installed in this system is NVRM: supported through the NVIDIA 340.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM: information. The 460.80 NVIDIA driver will ignore NVRM: this GPU. Continuing probe... You have installed the wrong driver. Your system needs the version 340 Nvidia driver. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Changed in: nvidia-graphics-drivers-460 (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/1929114 Title: Resolução da minha tela. Status in nvidia-graphics-drivers-460 package in Ubuntu: Invalid Bug description: Minha tela não volta para a rsolução nativa só da pra usar no 480 X 620, o que é horrível. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82~18.04.1-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 13:55:23 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.4.0-73-generic, x86_64: installed virtualbox, 5.2.42, 5.4.0-72-generic, x86_64: installed virtualbox, 5.2.42, 5.4.0-73-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T410 [17aa:2142] InstallationDate: Installed on 2020-05-06 (379 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 2537GC0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=4e34df45-65c4-4324-b2d9-8e3eb8d18fff ro quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 10/25/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET74WW (1.34 ) dmi.board.name: 2537GC0 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET74WW(1.34):bd10/25/2010:svnLENOVO:pn2537GC0:pvrThinkPadT410:rvnLENOVO:rn2537GC0:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2537GC0 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1929114/+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 1929115] Re: Video playback on all browsers lags in HD (720p and above)
Please specify which browsers are affected and we can assign the bug there. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1929115 Title: Video playback on all browsers lags in HD (720p and above) Status in Ubuntu: Incomplete Bug description: I recently installed ubuntu 20.04 GNOME and noticed that video playback lags with resolution above and equal to 720p. The video lags the audio and frame rate drops (seemingly from 30/60 fps to around 10 fps). In standard definition , there are no such frame drops. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 23:33:47 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:86fd] InstallationDate: Installed on 2021-05-20 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15s-eq0xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a41f5b2f-9502-402d-b248-2803c0503b41 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2020 dmi.bios.release: 15.22 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 99.39 dmi.modalias: dmi:bvnAMI:bvrF.22:bd07/03/2020:br15.22:efr99.39:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.39:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 9VV61PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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/+bug/1929115/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Tks @Daniel, Apparently the bug fix has been merged 2 months ago in the PulseAudio master branch: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/491 so about 5 years after the 1st bug reports. To be fair, it was not a bug in ubuntu but in PulseAudio. -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1898593] Re: Fix sphinx doc building
A fix was released in the latest impish sync (2.1.27+dfsg-2.1), where the sphinx builds were re-enabled. ** Also affects: cyrus-sasl2 (Ubuntu Impish) Importance: Medium Status: Triaged ** Also affects: cyrus-sasl2 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: cyrus-sasl2 (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: cyrus-sasl2 (Ubuntu Impish) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1898593 Title: Fix sphinx doc building Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Groovy: New Status in cyrus-sasl2 source package in Hirsute: New Status in cyrus-sasl2 source package in Impish: Fix Released Bug description: This basically the same bug as #1894907, but there I decided to disable docs rebuilding, after checking that none of the patches were against the docs source. Furthermore, we should probably fix these lintian issues: E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file usr/share/doc/cyrus-sasl2-doc/developer.html You may use the libjs-mathjax package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js) E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file usr/share/doc/cyrus-sasl2-doc/download.html You may use the libjs-mathjax package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js) E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file usr/share/doc/cyrus-sasl2-doc/genindex.html You may use the libjs-mathjax package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js) E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file usr/share/doc/cyrus-sasl2-doc/getsasl.html You may use the libjs-mathjax package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js) E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file usr/share/doc/cyrus-sasl2-doc/index.html You may use the libjs-mathjax package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js) E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file usr/share/doc/cyrus-sasl2-doc/operations.html You may use the libjs-mathjax package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js) E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file usr/share/doc/cyrus-sasl2-doc/packager.html You may use the libjs-mathjax package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js) E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file usr/share/doc/cyrus-sasl2-doc/search.html You may use the libjs-mathjax package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js) E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file usr/share/doc/cyrus-sasl2-doc/setup.html You may use the libjs-mathjax package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js) E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file usr/share/doc/cyrus-sasl2-doc/support.html You may use the libjs-mathjax package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js) E: cyrus-sasl2 source: source-is-missing doc/html/_static/jquery.js line length is 32014 characters (>512) E: cyrus-sasl2 source: source-is-missing doc/html/_static/js/modernizr.min.js E: cyrus-sasl2 source: source-is-missing doc/html/_static/underscore.js line length is 519 characters (>512) E: cyrus-sasl2 source: source-is-missing docsrc/exts/themes/cyrus/static/js/modernizr.min.js E: cyrus-sasl2 source: source-is-missing docsrc/exts/themes/sphinx_rtd_theme/static/js/modernizr.min.js To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1898593/+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 1929131] [NEW] [ZenBook UX431FAC_UX431FA, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all
Public bug reported: There is no sound on the computer even with headphones plugged in. I think the sound card is not being detected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbienvenu 1483 F pulseaudio /dev/snd/pcmC0D0p: bbienvenu 1483 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 20 22:53:05 2021 InstallationDate: Installed on 2021-04-17 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbienvenu 1483 F pulseaudio /dev/snd/pcmC0D0p: bbienvenu 1483 F...m pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [ZenBook UX431FAC_UX431FA, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431FAC.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431FAC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX431FAC.303:bd08/17/2020:br5.16:efr3.3:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FAC_UX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FAC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431FAC_UX431FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-04-18T20:03:58.714967 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1929131 Title: [ZenBook UX431FAC_UX431FA, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: There is no sound on the computer even with headphones plugged in. I think the sound card is not being detected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbienvenu 1483 F pulseaudio /dev/snd/pcmC0D0p: bbienvenu 1483 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 20 22:53:05 2021 InstallationDate: Installed on 2021-04-17 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbienvenu 1483 F pulseaudio /dev/snd/pcmC0D0p: bbienvenu 1483 F...m pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [ZenBook UX431FAC_UX431FA, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX431FAC.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX431FAC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX431FAC.303:bd08/17/2020:br5.16:efr3.3:svnASUSTeKCOMPUTERINC.:pnZenBookUX431FAC_UX431FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX431FAC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX431FAC_UX431FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modp
[Touch-packages] [Bug 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
** Patch added: "Diff from Debian" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+attachment/5499101/+files/sudo-debian-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit Status in sudo package in Ubuntu: New Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Can confirm that 3.40-1 version on flathub successfully fixes the problem. Many thanks https://flathub.org/apps/details/org.gnome.Evolution -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
** Patch added: "Diff from 1.9.5p2-2ubuntu3" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+attachment/5499102/+files/sudo-ubuntu-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit Status in sudo package in Ubuntu: New Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+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 1929125] [NEW] lib32z1 cannot be installed on ubuntu 20.04 LTS
Public bug reported: I am using Ubuntu 20.04 LTS. When trying to install lib32z1, I get the following error: The following packages have unmet dependencies: lib32z1 : Depends: libc6-i386 (>= 2.4) but it is not going to be installed E: Unable to correct problems, you have held broken packages. lib32z1 (https://packages.ubuntu.com/focal/lib32z1) depends on libc6-i386 (>= 2.4) but the latest version of libc6-i386 I can find for Ubuntu is 2.33 (https://packages.ubuntu.com/impish/libc6-i386) Is it possible Ubuntu is asking for a version of a dependency so high that it doesn't even exist? The reason I'm installing a 32-bit package is it's required for Android Studio installation process: https://developer.android.com/studio/install#linux --- apt-cache policy libc6-i386 libc6-i386: Installed: (none) Candidate: 2.31-0ubuntu9.2 Version table: 2.31-0ubuntu9.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2.31-0ubuntu9 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages apt-cache policy lib32z1 lib32z1: Installed: (none) Candidate: 1:1.2.11.dfsg-2ubuntu1.2 Version table: 1:1.2.11.dfsg-2ubuntu1.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:1.2.11.dfsg-2ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 ** Affects: zlib (Ubuntu) Importance: Undecided Status: New ** Tags: focal unmetdeps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1929125 Title: lib32z1 cannot be installed on ubuntu 20.04 LTS Status in zlib package in Ubuntu: New Bug description: I am using Ubuntu 20.04 LTS. When trying to install lib32z1, I get the following error: The following packages have unmet dependencies: lib32z1 : Depends: libc6-i386 (>= 2.4) but it is not going to be installed E: Unable to correct problems, you have held broken packages. lib32z1 (https://packages.ubuntu.com/focal/lib32z1) depends on libc6-i386 (>= 2.4) but the latest version of libc6-i386 I can find for Ubuntu is 2.33 (https://packages.ubuntu.com/impish/libc6-i386) Is it possible Ubuntu is asking for a version of a dependency so high that it doesn't even exist? The reason I'm installing a 32-bit package is it's required for Android Studio installation process: https://developer.android.com/studio/install#linux --- apt-cache policy libc6-i386 libc6-i386: Installed: (none) Candidate: 2.31-0ubuntu9.2 Version table: 2.31-0ubuntu9.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2.31-0ubuntu9 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages apt-cache policy lib32z1 lib32z1: Installed: (none) Candidate: 1:1.2.11.dfsg-2ubuntu1.2 Version table: 1:1.2.11.dfsg-2ubuntu1.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:1.2.11.dfsg-2ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1929125/+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 1929115] Re: Video playback on all browsers lags in HD (720p and above)
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1929115 Title: Video playback on all browsers lags in HD (720p and above) Status in xorg package in Ubuntu: New Bug description: I recently installed ubuntu 20.04 GNOME and noticed that video playback lags with resolution above and equal to 720p. The video lags the audio and frame rate drops (seemingly from 30/60 fps to around 10 fps). In standard definition , there are no such frame drops. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 23:33:47 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:86fd] InstallationDate: Installed on 2021-05-20 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15s-eq0xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a41f5b2f-9502-402d-b248-2803c0503b41 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2020 dmi.bios.release: 15.22 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 99.39 dmi.modalias: dmi:bvnAMI:bvrF.22:bd07/03/2020:br15.22:efr99.39:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.39:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 9VV61PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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/xorg/+bug/1929115/+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 1929115] [NEW] Video playback on all browsers lags in HD (720p and above)
You have been subscribed to a public bug: I recently installed ubuntu 20.04 GNOME and noticed that video playback lags with resolution above and equal to 720p. The video lags the audio and frame rate drops (seemingly from 30/60 fps to around 10 fps). In standard definition , there are no such frame drops. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 23:33:47 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:86fd] InstallationDate: Installed on 2021-05-20 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Laptop 15s-eq0xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a41f5b2f-9502-402d-b248-2803c0503b41 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2020 dmi.bios.release: 15.22 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 99.39 dmi.modalias: dmi:bvnAMI:bvrF.22:bd07/03/2020:br15.22:efr99.39:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.39:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 9VV61PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal performance ubuntu -- Video playback on all browsers lags in HD (720p and above) https://bugs.launchpad.net/bugs/1929115 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Sorry @~gavin.lin, by mistake marked released. Please fix it at youe end. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1929122] [NEW] networkd crashes when advertising blackhole route thru BGP
Public bug reported: lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.6 [Impact] Networkd crashes when a blackhole route (route aggregation is installed as a blackhole route) is advertised via FRR. [Fix] networkd should not crash [Test case] Bug was reported to systemd (not accepted because systemd version too old) where a test case is described: https://github.com/systemd/systemd/issues/19648 Lower in the comment you can find the full debug log from networkd. Here you can see the core dump: https://drive.google.com/file/d/1tCKiOSnGkLbx3w9du5_NNepkOQZC_hx7/view?usp=sharing For convenience I also packed the relevant parts of the prod env in a vagrant box showing the issue: vagrant init matijavizintin/networkd- debug After some more testing i noticed that immediately after the route is being advertised, networkd detects the change and crashes with "Assertion 'ifindex' failed at src/network/networkd-link.c:757, function link_get(). Aborting." Steps how it happens: 1. networkd is running 2. frr is started without advertising the aggregated address 3. add aggregated address and reload frr 4. blackhole route is installed and networkd crashes with the error above ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: systemd systemd-networkd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1929122 Title: networkd crashes when advertising blackhole route thru BGP Status in systemd package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.6 [Impact] Networkd crashes when a blackhole route (route aggregation is installed as a blackhole route) is advertised via FRR. [Fix] networkd should not crash [Test case] Bug was reported to systemd (not accepted because systemd version too old) where a test case is described: https://github.com/systemd/systemd/issues/19648 Lower in the comment you can find the full debug log from networkd. Here you can see the core dump: https://drive.google.com/file/d/1tCKiOSnGkLbx3w9du5_NNepkOQZC_hx7/view?usp=sharing For convenience I also packed the relevant parts of the prod env in a vagrant box showing the issue: vagrant init matijavizintin/networkd- debug After some more testing i noticed that immediately after the route is being advertised, networkd detects the change and crashes with "Assertion 'ifindex' failed at src/network/networkd-link.c:757, function link_get(). Aborting." Steps how it happens: 1. networkd is running 2. frr is started without advertising the aggregated address 3. add aggregated address and reload frr 4. blackhole route is installed and networkd crashes with the error above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1929122/+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 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
This bug was fixed in the package apt - 2.3.5 --- apt (2.3.5) experimental; urgency=medium * policy: Apply phasing to uninstalled packages too (LP: #1925745) -- Julian Andres Klode Mon, 17 May 2021 11:43:23 +0200 ** Changed in: apt (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in apt package in Ubuntu: Fix Released Status in apt source package in Hirsute: Confirmed Status in apt source package in Impish: Fix Released Bug description: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925745/+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 1929114] [NEW] Resolução da minha tela.
Public bug reported: Minha tela não volta para a rsolução nativa só da pra usar no 480 X 620, o que é horrível. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82~18.04.1-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 13:55:23 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.4.0-73-generic, x86_64: installed virtualbox, 5.2.42, 5.4.0-72-generic, x86_64: installed virtualbox, 5.2.42, 5.4.0-73-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T410 [17aa:2142] InstallationDate: Installed on 2020-05-06 (379 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 2537GC0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=4e34df45-65c4-4324-b2d9-8e3eb8d18fff ro quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 10/25/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET74WW (1.34 ) dmi.board.name: 2537GC0 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET74WW(1.34):bd10/25/2010:svnLENOVO:pn2537GC0:pvrThinkPadT410:rvnLENOVO:rn2537GC0:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2537GC0 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1929114 Title: Resolução da minha tela. Status in xorg package in Ubuntu: New Bug description: Minha tela não volta para a rsolução nativa só da pra usar no 480 X 620, o que é horrível. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82~18.04.1-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 13:55:23 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.4.0-73-generic, x86_64: installed virtualbox, 5.2.42, 5.4.0-72-generic, x86_64: installed virtualbox, 5.2.42, 5.4.0-73-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T410 [17aa:2142] InstallationDate: Installed on 2020-05-06 (379 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 2537GC0 ProcKernelCmdLine: B
[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
This bug was fixed in the package pam - 1.3.1-5ubuntu7 --- pam (1.3.1-5ubuntu7) impish; urgency=medium * Backport pam_faillock module from pam 1.4.0 (LP: #1927796) - debian/patches-applied/add_pam_faillock.patch: add module. - debian/patches-applied/pam_faillock_create_directory: create dir before creating file in modules/pam_faillock/faillock.c. - debian/rules: set execute permissions on pam_faillock test. - debian/libpam-modules-bin.install: install faillock binary and man page. -- Richard Maciel Costa Thu, 08 Apr 2021 07:06:27 -0400 ** Changed in: pam (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Released Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Committed Status in pam source package in Hirsute: Fix Committed Status in pam source package in Impish: Fix Released Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1886653] Re: cups-pki-expired
i am having the same issue on my HP Deskjet 3630 -- 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/1886653 Title: cups-pki-expired Status in cups package in Ubuntu: Confirmed Bug description: The printer always goes to stopped state in Ubuntu 20.04. Print properties window has status message saying: "cups-pki-expired". I have HP color laserjet m552, which Ubuntu discovers directly from the local network and configures automatically. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 14:40:00 2020 InstallationDate: Installed on 2019-11-03 (247 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: implicitclass://HP_Color_LaserJet_M552_5F80BF_/ MachineType: LENOVO 81H1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1886653/+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 1929110] [NEW] Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
Public bug reported: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. ** Affects: sudo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit Status in sudo package in Ubuntu: New Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+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 1929101] [NEW] systemd-networkd can't set ip6tnl interface mode as any
Public bug reported: systemd-networkd provides "Mode=" configuration for a virtual device of "Kind=ip6tnl". But setting mode to "any" doesn't work, tunnel mode stay as ipv6/ipv6: 20/05/21 18:08:33 darkyman@mnt-myt-focal ~ > ip -6 tun show ip6tnl0: ipv6/ipv6 remote :: local :: encaplimit 0 hoplimit inherit tclass 0x00 flowlabel 0x0 (flowinfo 0x) I'm expecting it to be in any/ipv6 mode like: ip6tnl0: any/ipv6 remote :: local :: encaplimit 0 hoplimit inherit tclass 0x00 flowlabel 0x0 (flowinfo 0x) Config file attached (00-ip6tnl0.netdev), I'm using systemd `systemd 245 (245.4-4ubuntu3.6)` on a `Ubuntu 20.04.2 LTS`. Currently I'm using systemd service as a workaround this issue, which sets mode to "any" by calling /usr/sbin/ip -6 tunnel change ip6tnl0 mode any And that's what networkctl thinks about this tunnel interface ● 7: ip6tnl0 Link File: /usr/lib/systemd/network/99-default.link Network File: /etc/systemd/network/01-ip6tnl0.network Type: tunnel6 State: degraded (configured) MTU: 9000 (min: 68, max: 65407) Queue Length (Tx/Rx): 1/1 Address: fe80::3063:1eff:febf:8aaa May 20 17:55:36 mnt-myt-focal.example.com systemd-udevd[1062]: ip6tnl0: Could not generate persistent MAC: No data available May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: netdev ready May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: netdev could not be created: Invalid argument May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: IPv6 successfully enabled May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: Link UP May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: Gained carrier May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: Gained IPv6LL ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "systemd-networkd ip6tnl configuration" https://bugs.launchpad.net/bugs/1929101/+attachment/5499022/+files/00-ip6tunl0.netdev ** Description changed: systemd-networkd provides "Mode=" configuration for a virtual device of "Kind=ip6tnl". But setting mode to "any" doesn't work, tunnel mode stay as ipv6/ipv6: 20/05/21 18:08:33 darkyman@mnt-myt-focal ~ > ip -6 tun show ip6tnl0: ipv6/ipv6 remote :: local :: encaplimit 0 hoplimit inherit tclass 0x00 flowlabel 0x0 (flowinfo 0x) I'm expecting it to be in any/ipv6 mode like: ip6tnl0: any/ipv6 remote :: local :: encaplimit 0 hoplimit inherit tclass 0x00 flowlabel 0x0 (flowinfo 0x) Config file attached (00-ip6tnl0.netdev), I'm using systemd `systemd 245 (245.4-4ubuntu3.6)` on a `Ubuntu 20.04.2 LTS`. Currently I'm using systemd service as a workaround this issue, which sets mode to "any" by calling /usr/sbin/ip -6 tunnel change ip6tnl0 mode any + + And that's what networkctl thinks about this tunnel interface + + ● 7: ip6tnl0 + Link File: /usr/lib/systemd/network/99-default.link + Network File: /etc/systemd/network/01-ip6tnl0.network + Type: tunnel6 + State: degraded (configured) +MTU: 9000 (min: 68, max: 65407) + Queue Length (Tx/Rx): 1/1 +Address: fe80::3063:1eff:febf:8aaa + + May 20 17:55:36 mnt-myt-focal.example.com systemd-udevd[1062]: ip6tnl0: Could not generate persistent MAC: No data available + May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: netdev ready + May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: netdev could not be created: Invalid argument + May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: IPv6 successfully enabled + May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: Link UP + May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: Gained carrier + May 20 17:55:36 mnt-myt-focal.example.com systemd-networkd[1008]: ip6tnl0: Gained IPv6LL -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1929101 Title: systemd-networkd can't set ip6tnl interface mode as any Status in systemd package in Ubuntu: New Bug description: systemd-networkd provides "Mode=" configuration for a virtual d
[Touch-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
@rbalint, I just tested Impish and I cannot reproduce the issue. It
doesn't prove it's not there but it's a very good sign!
I can see that our automated testing failed because of this issue on the
2021-05-10 but not after. If I'm not wrong, systemd 248 was pushed on
the 14th, this would make a nice correlation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Incomplete
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+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 1929087] [NEW] sfdisk refuses to write GPT table between sector 34 and 2047
Public bug reported:
According to https://wiki.archlinux.org/title/GRUB#BIOS_systems, it's
both legal and interesting to place the BIOS BOOT partition from sector
34 to sector 2047, as follows:
$ sudo sfdisk --no-act -f --label gpt /dev/sdb << EOF
start= 34, size=2013, name=bios, type=$(sfdisk --label
gpt -T | awk '{IGNORECASE = 1;} /bios boot/{print $1}')
start= 2048, size=12582912, name=swap, type=$(sfdisk --label
gpt -T | awk '{IGNORECASE = 1;} /linux swap/{print $1}')
EOF
The output is:
/dev/sdb1: Sector 34 already used.
Failed to add #1 partition: Numerical result out of range
Leaving.
It's a false error. As a workaround, users must omit the BIOS BOOT
partition then use gdisk to insert it manually. This was uncovered in
2015 and perhaps never reported to a bug tracker because it's still
broken. See https://www.spinics.net/lists/util-linux-ng/msg11253.html
** Affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1929087
Title:
sfdisk refuses to write GPT table between sector 34 and 2047
Status in util-linux package in Ubuntu:
New
Bug description:
According to https://wiki.archlinux.org/title/GRUB#BIOS_systems, it's
both legal and interesting to place the BIOS BOOT partition from
sector 34 to sector 2047, as follows:
$ sudo sfdisk --no-act -f --label gpt /dev/sdb << EOF
start= 34, size=2013, name=bios, type=$(sfdisk
--label gpt -T | awk '{IGNORECASE = 1;} /bios boot/{print $1}')
start= 2048, size=12582912, name=swap, type=$(sfdisk
--label gpt -T | awk '{IGNORECASE = 1;} /linux swap/{print $1}')
EOF
The output is:
/dev/sdb1: Sector 34 already used.
Failed to add #1 partition: Numerical result out of range
Leaving.
It's a false error. As a workaround, users must omit the BIOS BOOT
partition then use gdisk to insert it manually. This was uncovered in
2015 and perhaps never reported to a bug tracker because it's still
broken. See https://www.spinics.net/lists/util-linux-ng/msg11253.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1929087/+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
Another confirmation for the 9i. After set-verb.sh script my bass speaker is working. Thanks Hui Wang! You're such a helpful person. I've heard you've managed to fix a bunch of these, where people would just be frustrated for months and years without you. If you're ever in Pittsburgh, I'll buy you a beer or a dinner or whatever! Thanks again! -- 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 1928360] Re: Switch to Fcitx 5 for Chinese
On 2021-05-20 15:39, handsome_feng wrote: > With the fcitx items in the current seed, I think pkg_depends don't > need to pull in the fcitx 4 packages for Ubuntu Kylin 21.10, Ok, good. > also it's okay to pull in the fcitx 5 packages, since the im-config > will set the default input method to fcitx 4 for Ubuntu Kylin 21.10? Hmm.. Yes, AFAIK that would work. fcitx 4 and fcitx 5 can co-exist, and if both are installed im-config will pick fcitx 4 by default (can be changed by the user via Language Support). Does this mean that the proposed changes to pkg_depends is fine from an Ubuntu Kylin POV, and that no further changes are needed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: In Progress Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: In Progress Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
** Changed in: apt (Ubuntu Impish) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in apt package in Ubuntu: Fix Committed Status in apt source package in Hirsute: Confirmed Status in apt source package in Impish: Fix Committed Bug description: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925745/+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 1896632] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: »installiertes lvm2-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
** Changed in: lvm2 (Ubuntu) Assignee: (unassigned) => Christian Lampe (lampe2020) ** Changed in: lvm2 (Ubuntu) Assignee: Christian Lampe (lampe2020) => (unassigned) ** Changed in: lvm2 (Ubuntu) Assignee: (unassigned) => Christian Lampe (lampe2020) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1896632 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: »installiertes lvm2-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück Status in lvm2 package in Ubuntu: Confirmed Bug description: I ve no idea what happend or why. The system reports me a bug, I thought I would send the information. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 21 22:17:26 2020 DpkgHistoryLog: Start-Date: 2020-09-21 22:17:25 Commandline: apt-get autoremove Requested-By: pietsch (1000) ErrorMessage: »installiertes lvm2-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: »installiertes lvm2-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1896632/+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 1928360] Re: Switch to Fcitx 5 for Chinese
Hi, With the fcitx items in the current seed, I think pkg_depends don't need to pull in the fcitx 4 packages for Ubuntu Kylin 21.10, also it's okay to pull in the fcitx 5 packages, since the im-config will set the default input method to fcitx 4 for Ubuntu Kylin 21.10? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: In Progress Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: In Progress Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1928360] Re: Switch to Fcitx 5 for Chinese
@handsome_feng: Great! I have a follow-up question then: In the desktop seed of Ubuntu Kylin I see these packages: * (im-config) * (fcitx) * (fcitx-frontend-gtk2) * (fcitx-frontend-gtk3) * (fcitx-frontend-qt5) * (fcitx-ui-classic) * (fcitx-table) * (fcitx-module-cloudpinyin) * (fcitx-googlepinyin) Given that, will it work with the proposed version of pkg_depends, or is there a reason to keep letting also pkg_depends pull a bunch of fcitx 4 packages for Kylin in 21.10? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: In Progress Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: In Progress Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: New Status in gdb source package in Groovy: New Status in glibc source package in Groovy: New Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: New Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1152187] Re: [MIR] systemd
Hello, Revisiting this MIR since we (now) want to have systemd-container (from src:systemd) from Bionic/universe in Bionic/main. This package is to be included in the Google cloud images the public cloud team builds, going back to Bionic. As cloud images are to ship only packages from main, this request is to see that happen. src:systemd is in main in Bionic but bin:systemd-container isn't. Adding a task for Bionic for the same. Please let me know if there's anything else needed? TIA! ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1152187 Title: [MIR] systemd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Bug description: * The package is in universe and built on all archs: https://launchpad.net/ubuntu/+source/systemd/44-10ubuntu1 * Rationale: - in a first step we want systemd-services promoted to replace ubuntu- system-services - We will also want to move from consolekit to logind soon (https://blueprints.launchpad.net/ubuntu/+spec/foundations-1303 -consolekit-logind-migration) - udev has been merged in the systemd source upstream so we will want to build it from there at some point as well we don't plan to use the systemd init system at this point * Security: there has been some security issues in the past http://secunia.com/advisories/search/?search=systemd http://secunia.com/advisories/48220/ http://secunia.com/advisories/48208/ http://secunia.com/advisories/48331/ Those are mostly logind issue and have been fixed upstream. Our current package is outdated but we do plan to update it before starting using logind. There should be no issue with the services * Quality: - there is no RC bug in debian: http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=systemd - there is no bug open in launchpad: https://launchpad.net/ubuntu/+source/systemd/+bugs - upstream is active and responsive to issues The desktop bugs team is subscribed to the package in launchpad, foundations/desktop will maintain the package and look to the bug reports regularly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1152187/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
lincvz:
> Thank you for the patch and your investigations. In the next few days, I
> cannot install the patched package on my production machines. I'll let you
> know when I can.
Thanks.
Can you reproduce a similar issue with the modus operandi (using gdb) I
describe above?
(Note that while it renders slapd unresponsive, service is restored as
soon as you quit or detach gdb on the client).
If you do, it would be worth getting a backtrace on the slapd threads
again, so see if you get the same ones as before or some similar to
mine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
Confirmed
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1929053] [NEW] [HP EliteBook 820 G3, Conexant CX20724, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: # Description about OS and package → Description:Ubuntu 20.04.2 LTS Release:20.04 alsa-utils: Installed: 1.2.2-1ubuntu2.1 Candidate: 1.2.2-1ubuntu2.1 # What expected → Sound which plays after inserting a USB drive/any other sound made by OS while using a VM will play normally. # What happened → Actually whenever I plug my USB drive while running a VM, there is a sound of crackling/scratching when the USB drive is plugged-in and this also happens when the VM makes a sound of login or anything else, and also that the strange distortion only comes at the end of a sound. What could be the possible reason for this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-54.61~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-54-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: krrish 2259 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:14:23 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: May 20 16:00:46 720G3 dbus-daemon[1280]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.27' (uid=125 pid=1488 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") May 20 16:01:11 720G3 systemd[1482]: pulseaudio.service: Succeeded. May 20 16:01:21 720G3 systemd[1482]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP EliteBook 820 G3, Conexant CX20724, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2016 dmi.bios.release: 1.13 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.13 dmi.board.name: 807C dmi.board.vendor: HP dmi.board.version: KBC Version 85.74 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.116 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:br1.13:efr133.116:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.74:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G3 dmi.product.sku: X4A65UC#ACJ dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa-driver amd64 apport-bug focal -- 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/1929053 Title: [HP EliteBook 820 G3, Conexant CX20724, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: # Description about OS and package → Description: Ubuntu 20.04.2 LTS Release: 20.04 alsa-utils: Installed: 1.2.2-1ubuntu2.1 Candidate: 1.2.2-1ubuntu2.1 # What expected → Sound which plays after inserting a USB drive/any other sound made by OS while using a VM will play normally. # What happened → Actually whenever I plug my USB drive while running a VM, there is a sound of crackling/scratching when the USB drive is plugged-in and this also happens when the VM makes a sound of login or anything else, and also that the strange distortion only comes at the end of a sound. What could be the possible reason for this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-54.61~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-54-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: krrish 2259 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:14:23 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: May 20 16:00:46 720G3 dbus-daemon[1280]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.27' (uid=125 pid=1488 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") May 20 16:01:11 720G3 systemd[1482]: pulseaudio.service: Succeeded. May 20 16:01:21 720G3 systemd[1482]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP EliteBook 820 G3, Conexan
[Touch-packages] [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Thank you for the patch and your investigations. In the next few days,
I cannot install the patched package on my production machines. I'll let
you know when I can.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
Confirmed
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1919177] Re: Azure: issues with accelerated networking on Hirsute
@rbalint I was able to reproduce the issue with an image that was
running the following:
ii cloud-init20.4.1-79-g71564dce-0ubuntu1 all initialization
and customization tool for cloud instances
ii linux-image-azure 5.8.0.1017.19+21.04.14 amd64Linux kernel
image for Azure systems.
ii systemd 247.3-3ubuntu3 amd64system and
service manager
For reference, I took 20210219 and only upgraded systemd.
I will also try to reproduce with Impish to confirm whether or not
systemd 248 solves the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Incomplete
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
No, you would need to provide symlinks for all variants, for the real file and all the symlinks. The unstripped ld.so is 220k, the stripped one 192k. So these 28k look pretty marginal to add, and I wouldn't see this a regression in size. Attaching the diff that already is in the glibc in impish. I don't see regression potential with this patch. ** Patch added: "ld.diff" https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1927192/+attachment/5498947/+files/ld.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: New Status in gdb source package in Groovy: New Status in glibc source package in Groovy: New Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: New Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot
Tried to back-port 4 patches from #2, it didn't work for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928200 Title: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: On ubuntu 20.04, with latest kernel and systemd, it will show error on ThinkPad X1. sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy systemd 245.4-4ubuntu3.6 kernel: 5.8.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1928200/+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 1928931] Re: German strings in deja-dup.mo for en_GB
Hello Iain, or anyone else affected, Accepted language-pack-gnome-en into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /language-pack-gnome-en/1:21.10+20210415ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: language-pack-gnome-en (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en in Ubuntu. https://bugs.launchpad.net/bugs/1928931 Title: German strings in deja-dup.mo for en_GB Status in language-pack-gnome-en package in Ubuntu: In Progress Status in language-pack-gnome-en source package in Hirsute: Fix Committed Bug description: [ Description ] Some German strings were accidentally translated under en_GB. They affect the default Ubuntu install - some of them are strings which are displayed as a notification some time after first logging in, so it's quite visible. See the attached screenshot. [ Fix ] Revert the German and go back to the proper English text. The way to fix langpacks is to upload the language-pack-gnome-XX package which replaces files in language-pack-gnome-XX-base. [ Devel release ] I'd like to propose to binary copy forward, and let the normal langpack release schedule take care of eventually dominating these away in impish. [ QA ] To verify the diff, compare deja-dup.po from language-pack-gnome-en- base to the one in this upload. You'll have to do that manually. 0. Be in en_GB. 1. Install the SRU 2. In an Ubuntu Desktop session, open a terminal and run `deja-dup --prompt`. 3. Note the buttons in the notification that shows up. They should be in English. [ What could go wrong ] 1. There could be other instances of this in different packages we haven't noticed yet 2. If I break the .po file, it could either break the build or the translations at runtime (but this is English, so if we fall back to C it's not too bad) 3. If my diff is wrong then I might have dropped some en_GB translations or made them wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+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 1778073] Re: dnsmasq and resolvconf hangs on start
I run into this bug and found the cause: When starting dnsmasq, a call to resolvconf is made to update the server entries. If postfix is installed, the /etc/resolvconf/update-libc.d/postfix script is called which tries to reload it. The problem is that dnsmasq is a nss-lookup.target, while postfix requires nss-lookup.target to be active in order to restart. That will create a deadlock, the ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf script in dnsmasq times out and the service is not started. This is only triggered by having dnsmasq and postfix installed. If you also install nfs-common, the rpc-statd will also be part of nss-lookup.target and it won't be triggered. I hope somebody will find this useful, took me days to debug it :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1778073 Title: dnsmasq and resolvconf hangs on start Status in dnsmasq package in Ubuntu: Incomplete Status in dnsmasq package in Debian: New Bug description: I installed today dnsmasq and I use resolvconf in background. Problem is, that systemd takes 1 minute or so after service start and than reports: root@proxy:~# service dnsmasq status dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled) Drop-In: /run/systemd/generator/dnsmasq.service.d 50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf Active: failed (Result: timeout) since Do 2018-06-21 15:58:13 CEST; 2min 10s ago Process: 3295 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf (code=killed, signal=TERM) Process: 3865 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=killed, signal=TERM) Process: 3837 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS) Process: 3825 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS) Main PID: 3862 (code=exited, status=0/SUCCESS) Jun 21 15:56:43 proxy dnsmasq[3862]: Benutze Namensserver 192.168.23.1#53 Jun 21 15:56:43 proxy dnsmasq[3865]: * Awakening mail retriever agent: Jun 21 15:56:43 proxy dnsmasq[3865]:...done. Jun 21 15:56:43 proxy postfix[3951]: Postfix is running with backwards-compatible default settings Jun 21 15:56:43 proxy postfix[3951]: See http://www.postfix.org/COMPATIBILITY_README.html for details Jun 21 15:56:43 proxy postfix[3951]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload" Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Start-post operation timed out. Stopping. Jun 21 15:58:13 proxy systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Unit entered failed state. Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Failed with result 'timeout'. when I look into the start script /etc/init.d/dnsmasq there is a func systemd-start-resolvconf which points to start-resolvconf. There is this part: for interface in $DNSMASQ_EXCEPT do [ $interface = lo ] && return done Before I had not defined DNSMASQ_EXCEPT in /etc/defaults/dnsmasq. Problem is, that this part MUST be faulty! When I commend it out, I can start dnsmasq! It looks like it loops forever there?! Also if I define DNSMASQ_EXCEPT to my listen interface, it works - but is is really needed? I found a other user which had the same problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871958 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1ubuntu0.16.04.4 [modified: etc/default/dnsmasq] ProcVersionSignature: Ubuntu 4.15.0-23.25~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 21 16:12:14 2018 InstallationDate: Installed on 2017-02-27 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) PackageArchitecture: all ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.dnsmasq: 2018-06-21T16:07:24.818774 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1778073/+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 1928931] Re: German strings in deja-dup.mo for en_GB
hm, do we actually know *why* this happened? Does this mean there is a bug in langpack-o-matic that causes a mix-up of languages? Or was this an issue on the Launchpad translation side of things? I'd like to understand this better and, if needed, filling in a langpack-o-matic bug for this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en in Ubuntu. https://bugs.launchpad.net/bugs/1928931 Title: German strings in deja-dup.mo for en_GB Status in language-pack-gnome-en package in Ubuntu: In Progress Status in language-pack-gnome-en source package in Hirsute: In Progress Bug description: [ Description ] Some German strings were accidentally translated under en_GB. They affect the default Ubuntu install - some of them are strings which are displayed as a notification some time after first logging in, so it's quite visible. See the attached screenshot. [ Fix ] Revert the German and go back to the proper English text. The way to fix langpacks is to upload the language-pack-gnome-XX package which replaces files in language-pack-gnome-XX-base. [ Devel release ] I'd like to propose to binary copy forward, and let the normal langpack release schedule take care of eventually dominating these away in impish. [ QA ] To verify the diff, compare deja-dup.po from language-pack-gnome-en- base to the one in this upload. You'll have to do that manually. 0. Be in en_GB. 1. Install the SRU 2. In an Ubuntu Desktop session, open a terminal and run `deja-dup --prompt`. 3. Note the buttons in the notification that shows up. They should be in English. [ What could go wrong ] 1. There could be other instances of this in different packages we haven't noticed yet 2. If I break the .po file, it could either break the build or the translations at runtime (but this is English, so if we fall back to C it's not too bad) 3. If my diff is wrong then I might have dropped some en_GB translations or made them wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
@doko Would fixing the symlink as suggested in LP: #1918035 help instead of not stripping ld-*? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Committed Status in gdb source package in Focal: New Status in glibc source package in Focal: New Status in gdb source package in Groovy: New Status in glibc source package in Groovy: New Status in gdb source package in Hirsute: New Status in glibc source package in Hirsute: New Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Committed Bug description: see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1928360] Re: Switch to Fcitx 5 for Chinese
> Would that plan make sense to you? This is a good way for us, we agree with it, thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: In Progress Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: In Progress Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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
The testing kernel for yoga 9i: https://people.canonical.com/~hwang4/lp1926165/v2/, install this v2 testing kernel, don't need to run the script, check if the bass spk works or not. For c930 and c940, the testing kernel is not suitable for them, they only defines main speaker, this is different from yoga 9i, need to do more change than 9i. Let us fix the issue on 9i first, then try to fix the issue on c930 and c940. -- 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
