[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
Thank you Dan and Eric!
Summarizing howto with bionic for myself:
Upgrade systemd to the version with "keepconfiguration" fix.
Look at /run/systemd/network/*.network filename, in my example it is
"10-netplan-ens160.network"
Make a directory adding ".d" to this name:
/etc/systemd/network/10-netplan-ens160.network.d
Add a file "override.conf" into this directory, with content:
---
[Network]
KeepConfiguration=static
---
--
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/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in netplan:
Confirmed
Status in heartbeat package in Ubuntu:
Won't Fix
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
In Progress
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Won't Fix
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in keepalived source package in Focal:
Confirmed
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
- ALL related HA software has a small problem if interfaces are being
managed by systemd-networkd: nic restarts/reconfigs are always going
to wipe all interfaces aliases when HA software is not expecting it to
(no coordination between them.
- keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
smarter in this case because it has a service monitor that will
restart the virtual IP resource, in affected node & nic, before
considering a real failure, but other HA service might consider a real
failure when it is not.
[test case]
- comment #14 is a full test case: to have 3 node pacemaker, in that
example, and cause a networkd service restart: it will trigger a
failure for the virtual IP resource monitor.
- other example is given in the original description for keepalived.
both suffer from the same issue (and other HA softwares as well).
[regression potential]
- this backports KeepConfiguration parameter, which adds some
significant complexity to networkd's configuration and behavior, which
could lead to regressions in correctly configuring the network at
networkd start, or incorrectly maintaining configuration at networkd
restart, or losing network state at networkd stop.
- Any regressions are most likely to occur during networkd start,
restart, or stop, and most likely to involve missing or incorrect ip
address(es).
- the change is based in upstream patches adding the exact feature we
needed to fix this issue & it will be integrated with a netplan change
to add the needed stanza to systemd nic configuration file
(KeepConfiguration=)
[other info]
original description:
---
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the
[Touch-packages] [Bug 1939228] Re: screen tearing and redraw in ubuntu 20.04 LTS
*** This bug is a duplicate of bug 1937072 *** https://bugs.launchpad.net/bugs/1937072 The kernel in Ubuntu 20.04 got upgraded recently, so now it has the same bug as 21.04 :( Please keep using bug 1937072 ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** This bug has been marked a duplicate of bug 1937072 [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws -- 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/1939228 Title: screen tearing and redraw in ubuntu 20.04 LTS Status in linux-hwe-5.11 package in Ubuntu: New Bug description: I have used ubuntu 21.04 before on this device and reported a bug and it is solved by making psr value to 0. but in ubuntu 20.04LTS is not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..30.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:30:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sun Aug 8 13:57:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-08-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82A1 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=24316984-3147-43ba-aac0-f4497301192e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN32WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN32WW:bd05/27/2021:br1.32:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/linux-hwe-5.11/+bug/1939228/+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 1939202] Re: Driver no aparece ni Intel ni nvidia
According to the Nvidia web site, the Geforce 820M GPU requires driver version 430. But you have driver 460 installed which does not support the Geforce 820M GPU: [4.712300] NVRM: The NVIDIA GeForce 820M GPU installed in this system is NVRM: supported through the NVIDIA 390.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM: information. The 460.91.03 NVIDIA driver will ignore NVRM: this GPU. Continuing probe... You will need to uninstall the version 460 driver packages you have and then install 430 instead: sudo apt update sudo apt install nvidia-driver-430 If that doesn't work then try: sudo apt install nvidia-driver-390 ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1939202 Title: Driver no aparece ni Intel ni nvidia Status in Ubuntu: Invalid Bug description: Muy Buenas en información de software mas controladores, no aparece nada sin embargo nvidia x lo puse como por demanda es decir intel en segundo lugar y baje la resolución de pantalla a 1080x 748 ayuda donde estan los controladores? gracias ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 17:13:30 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:228a] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:228a] Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b40a Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550LD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=34ca3807-bd85-48be-8355-4184cd90c75e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LD.302:bd04/14/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550LD dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1939202/+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 1939211] Re: [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel
Yes please try turning off panel self refresh again by adding this kernel parameter: i915.enable_psr=0 ** Summary changed: - Screen flickering after upgrading from 5.8 kernel to 5.11 kernel + [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Incomplete ** Tags added: regression-update -- 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/1939211 Title: [Dell XPS 13 9380] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: Hello! After the upgrade to the 5.8 series kernel to the 5.11 series kernel, I have noticed some screen flickering. I had the same problem previously on Fedora after upgrading to the 5.0 series kernel, but this was not present on Ubuntu 20.04 on either the 5.4 or 5.8 series kernels. On Fedora, it was fixed by turning off panel self-refresh on my Dell XPS 13 9380. I can try that again here if you all think it would be a useful piece of information. In the Fedora bug, it was reported that this problem is fixed in the 5.13 kernel. Let me know whatever else I can do. Thanks! Ben ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 18:56:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2021-06-24 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_l80o1s@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_l80o1s ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd05/27/2021:br1.14:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939211/+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 1939173] Re: [HP 120-1100eo API] Screen flickering white vertical lines
Thanks for the bug report. You appear to be using Wayland at the moment. Can you please try logging into Xorg instead? It's the option on the login screen titled "Ubuntu" instead of "Ubuntu on Wayland". ** Summary changed: - Screen flickering white vertical lines + [HP 120-1100eo API] Screen flickering white vertical lines ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (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/1939173 Title: [HP 120-1100eo API] Screen flickering white vertical lines Status in mutter package in Ubuntu: Incomplete Bug description: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. Same thing not happening in Windows nor BIOS. Even though this looks a LOT like a hardware/wiring issue. Also the problem is visible in Ubuntu installer, but not in graphic safe one. Best regards, korho. $ lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-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: Fri Aug 6 23:04:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2021-08-06 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard 120-1100eo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=bf3dba7e-429f-455e-ac68-c016e272a4d9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 100 dmi.chassis.asset.tag: CZC2128RP3 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-1100eo:pvr:rvnQuanta:rn2AC5:rvr100:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-1100eo dmi.product.sku: H1E79EA#UUW dmi.sys.vendor: Hewlett-Packard 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/mutter/+bug/1939173/+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 1914915] Re: Sound or Audio is breaking
** Tags added: vmware ** Summary changed: - Sound or Audio is breaking + [vmware] Sound or Audio is breaking -- 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/1914915 Title: [vmware] Sound or Audio is breaking Status in pulseaudio package in Ubuntu: New Bug description: When I am watching videos sound is breaking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: hostname 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: balashanmugam 1437 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 7 15:27:47 2021 InstallationDate: Installed on 2021-02-05 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.16722896.B64.2008100651 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.16722896.B64.2008100651:bd08/10/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1914915/+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 1939255] [NEW] dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once
Public bug reported: [impact] on a system where systemd-resolved is running, if dhclient is used on more than 5 interfaces, it calls the '/etc/dhcp/dhclient-enter- hooks.d/resolved' script multiple times, which then restarts systemd- resolved multiple times, triggering the unit's start-limit throttle which results in the unit entering failed state [test case] on a system with more than 5 available interfaces to run dhclient on (where all the interfaces will get a dhcp response), run dhclient with the interfaces: $ dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 ens15 check if systemd-resolved failed: $ journalctl -b -1 -u systemd-resolved ... Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Start request repeated too quickly. Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'. Aug 09 00:38:08 sf316232-b systemd[1]: Failed to start Network Name Resolution. [regression potential] failure to start/stop/restart systemd-resolved, or problems adding dhclient-provided DNS nameservers to systemd-resolved [scope] this is needed only for b/f the dhclient 'hook' script is provided by the systemd package in focal and earlier, and needs fixing in those releases in h and later, the 'hook' script is included in the isc-dhcp-client package and notifies systemd-resolved in a more direct way without requiring restarting, and so doesn't trigger the restart limiting. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Invalid ** Affects: systemd (Ubuntu Bionic) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Focal) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) -- 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/1939255 Title: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Bug description: [impact] on a system where systemd-resolved is running, if dhclient is used on more than 5 interfaces, it calls the '/etc/dhcp/dhclient-enter- hooks.d/resolved' script multiple times, which then restarts systemd- resolved multiple times, triggering the unit's start-limit throttle which results in the unit entering failed state [test case] on a system with more than 5 available interfaces to run dhclient on (where all the interfaces will get a dhcp response), run dhclient with the interfaces: $ dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 ens15 check if systemd-resolved failed: $ journalctl -b -1 -u systemd-resolved ... Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Start request repeated too quickly. Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'. Aug 09 00:38:08 sf316232-b systemd[1]: Failed to start Network Name Resolution. [regression potential] failure to start/stop/restart systemd-resolved, or problems adding dhclient-provided DNS nameservers to systemd-resolved [scope] this is needed only for b/f the dhclient 'hook' script is provided by the systemd package in focal and earlier, and needs fixing in those releases in h and later, the 'hook' script is included in the isc-dhcp-client package and notifies systemd-resolved in a more direct way without requiring restarting, and so doesn't trigger the restart limiting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939255/+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 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
** Package changed: gnome-terminal (Ubuntu) => e2fsprogs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Status in e2fsprogs package in Ubuntu: New Bug description: Hello This problem did not occur on my computer. https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png It occurs in users who are not competent. This week, the French forum collapsed over this incident. I think changing the advice phrase might improve understanding of the action to be taken. Can these lines " ( i.e.. without -a or -p options) fsck existed with status code 4 The root file system on /dev/ requires a manual fsck" become "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root file system." ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-terminal 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 15:16:28 2021 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-08-02 (370 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939238/+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 1939243] Re: i don´t know
What kind of problem are you experiencing? ** 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/1939243 Title: i don´t know Status in Ubuntu: Incomplete Bug description: i don´t know ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Sun Aug 8 13:11:24 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS Rev. 2] [1462:1162] InstallationDate: Installed on 2016-12-02 (1710 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Itautec S.A. Infoway ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=357307e7-3637-4156-9d71-68dd5895191e ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: Itautec ST 1350 BIOS 0203-SL2, 06/27/2007 dmi.board.name: ST 1350 dmi.board.vendor: Itautec S.A. dmi.board.version: ST-1350 Padrao 02(Itautec_M) dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrItautecST1350BIOS0203-SL2,06/27/2007:bd06/27/2007:svnItautecS.A.:pnInfoway:pvrCorp:rvnItautecS.A.:rnST1350:rvrST-1350Padrao02(Itautec_M):cvnChassisManufacture:ct3:cvr: dmi.product.name: Infoway dmi.product.version: Corp dmi.sys.vendor: Itautec S.A. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Sun Aug 8 13:01:17 2021 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputSIGMACHIP Usb Mouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.11-1ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1939243/+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 1939238] [NEW] UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
You have been subscribed to a public bug: Hello This problem did not occur on my computer. https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png It occurs in users who are not competent. This week, the French forum collapsed over this incident. I think changing the advice phrase might improve understanding of the action to be taken. Can these lines " ( i.e.. without -a or -p options) fsck existed with status code 4 The root file system on /dev/ requires a manual fsck" become "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root file system." ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-terminal 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 15:16:28 2021 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-08-02 (370 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago) ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. https://bugs.launchpad.net/bugs/1939238 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs 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 1410618] Re: MacBook Air 6, 2 TRRS Headset Mic Not Working
Having the same problem with a 2017 12” Macbook (the Macbook10,2). The microphone shows up as “(unplugged)” in pavucontrol and pacmd regardless of if I have the headset plugged into the combo jack or not. Headphones are detected and work. The internal mic is still accessible and the Microphone input seems to be mirrorring it (could be to do with some chip-level switching that somehow doesn’t happen on Linux?). I’ve tried inputting all choices of model available in the CS4208 quirk list for PulseAudio (there isn’t one for my particular model) into alsa-base.conf and nothing has changed (having nothing in alsa-base.conf, which I did before attempting this fix, also makes no difference). I’m running Debian 10 with kernel 4.19.0-17-amd64. -- 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/1410618 Title: MacBook Air 6,2 TRRS Headset Mic Not Working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hello, I'm running Ubuntu Gnome 14.04 on a new MacBookAir6,2 with the Cirrus Logic CS4208 and would love to get the microphone part of the TRRS connector working. Mac OS picks up and utilizes the TRRS headset mic without issue so I know the hardware is a go. With the headset plugged in, running sudo hdajacksensetest -a results in: Pin 0x05 ( Digital Out, HDMI): present = No Pin 0x06 ( Digital Out, HDMI): present = No Pin 0x07 ( Digital Out, HDMI): present = No AlsaInfo output here: http://www.alsa-project.org/db/?f=cabc8cab44d308c8a3898c66d48d9be4fc5ccf83 I opened up hdajackretask to find four pins: Green Headphone Pin ID: 0x10 Headphone Internal Speaker Pin ID: 0x12 Internal speaker Pink Mic Pin ID: 0x18 Not connected Internal Mic Pin ID: 0x1c Internal mic Unplugging and replugging the headset changes the Output device in sound settings from Headphones to Speakers so that works, but nothing in the input tab ever changes. It always lists two devices: Internal Microphone and Microphone. Both of these seem to actually be the internal microphone in the mac - either works without the headset connected at all. So I'm not really sure how to proceed from here, but I'd be happy to run whatever diagnostic tests might prove useful and/or even contribute code toward a fix - but I just have no idea where to start. Is it as simple as just finding the right pin and telling the system to use it as a microphone? Similar bug report here: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/950494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1410618/+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 1931994] Re: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code
@Simon: You know that the packages in respective -proposed pocket need to be verified too, right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1931994 Title: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code Status in Ubuntu on IBM z Systems: Fix Committed Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Focal: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Released Bug description: Problem description: When passing a NULL key to reset AES EVC state, the state wouldn't be completely reset on s390x. https://github.com/openssl/openssl/pull/14900 Solution available here: https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8 Should be applied to all distros where openssl 1.1.1 is included for consistency reason. -> 21.10, 20.04, 18.04. I think not needed for 16.04 anymore [Test plan] $ sudo apt install libssl-dev $ gcc test.c -o evc-test -lcrypto -lssl # See https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for the test.c program $ ./evc-test && echo OK [Where problems could occur] This patch only touches s390x code paths, so there shouldn't be any regression on other architectures. However, on s390x this could reveal latent bugs by spreading a NULL key to new code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+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 1939243] [NEW] i don´t know
Public bug reported: i don´t know ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Sun Aug 8 13:11:24 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS Rev. 2] [1462:1162] InstallationDate: Installed on 2016-12-02 (1710 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Itautec S.A. Infoway ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=357307e7-3637-4156-9d71-68dd5895191e ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: Itautec ST 1350 BIOS 0203-SL2, 06/27/2007 dmi.board.name: ST 1350 dmi.board.vendor: Itautec S.A. dmi.board.version: ST-1350 Padrao 02(Itautec_M) dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrItautecST1350BIOS0203-SL2,06/27/2007:bd06/27/2007:svnItautecS.A.:pnInfoway:pvrCorp:rvnItautecS.A.:rnST1350:rvrST-1350Padrao02(Itautec_M):cvnChassisManufacture:ct3:cvr: dmi.product.name: Infoway dmi.product.version: Corp dmi.sys.vendor: Itautec S.A. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Sun Aug 8 13:01:17 2021 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputSIGMACHIP Usb Mouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.11-1ubuntu1.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1939243 Title: i don´t know Status in xorg package in Ubuntu: New Bug description: i don´t know ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Sun Aug 8 13:11:24 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS Rev. 2] [1462:1162] InstallationDate: Installed on 2016-12-02 (1710 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Itautec S.A. Infoway ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=357307e7-3637-4156-9d71-68dd5895191e ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: Itautec ST 1350 BIOS 0203-SL2, 06/27/2007 dmi.board.name: ST 1350 dmi.board.vendor: Itautec S.A. dmi.board.version: ST-1350 Padrao 02(Itautec_M) dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: dmi.modalias:
[Touch-packages] [Bug 1931104] Re: Test of dogtag-pki is failing on s390x due to LTO
** Tags removed: server-next update-excuse
** Bug watch added: Red Hat Bugzilla #1986627
https://bugzilla.redhat.com/show_bug.cgi?id=1986627
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=1986627
Importance: Unknown
Status: Unknown
** Package changed: fedora => nss (Fedora)
** Changed in: nss (Ubuntu)
Assignee: Paride Legovini (paride) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1931104
Title:
Test of dogtag-pki is failing on s390x due to LTO
Status in NSS:
Unknown
Status in nss package in Ubuntu:
Triaged
Status in nss package in Fedora:
Unknown
Bug description:
The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
Example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz
Bad:
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end
closed connection without response'))
ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote
end closed connection without response'))
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 995, in spawn
cert = deployer.setup_cert(client, tag)
File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py",
line 355, in setup_cert
return client.setupCert(request)
File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert
response = self.connection.post(
File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper
return func(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post
r = self.session.post(
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in
post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in
send
raise ConnectionError(err, request=request)
CA spawn failed:
Good:
nstalling CA into /var/lib/pki/pki-tomcat.
Notice: Trust flag u is set automatically if the private key is present.
/usr/lib/python3/dist-packages/urllib3/connection.py:455:
SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`,
falling back to check for a `commonName` for now. This feature is being removed
by major browsers and deprecated by RFC 2818. (See
https://github.com/urllib3/urllib3/issues/497 for details.)
warnings.warn(
==
INSTALLATION SUMMARY
==
...
The good test above was with:
ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security
Service libraries
ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite -
server
Worth to know, the good case test still fails later on with:
IOException: SocketException cannot write on socket: Failed to write to
socket: (-5938) Encountered end of file.
ERROR: CalledProcessError: Command '['pki', '-d',
'/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U',
'https://i-dogtag:8443', 'securitydomain-join', '--session',
'4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag',
'--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']'
returned non-zero exit status 255.
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 1038, in spawn
subsystem.join_security_domain(
File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201,
in join_security_domain
subprocess.check_call(cmd)
File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f
/etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join
--session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port
8080 --secure-port 8443 TKS i-dogtag 8443
Please check pkispawn logs in /var/log/pki/pki-tks-spawn.20210607093926.log
Well one issue at a time ... the current install issue first.
[Touch-packages] [Bug 1269456] Re: Infographic doesn’t seem to be translatable
** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1269456 Title: Infographic doesn’t seem to be translatable Status in camera-app: Fix Released Status in camera-app package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: I can't find the infographic strings (such as "photos taken today", etc.) anywhere in the template. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1269456/+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 1939228] [NEW] screen tearing and redraw in ubuntu 20.04 LTS
Public bug reported: I have used ubuntu 21.04 before on this device and reported a bug and it is solved by making psr value to 0. but in ubuntu 20.04LTS is not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..30.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:30:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sun Aug 8 13:57:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-08-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82A1 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=24316984-3147-43ba-aac0-f4497301192e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN32WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN32WW:bd05/27/2021:br1.32:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 corruption focal ubuntu ** Attachment added: "20210808_135627.jpg" https://bugs.launchpad.net/bugs/1939228/+attachment/5516599/+files/20210808_135627.jpg -- 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/1939228 Title: screen tearing and redraw in ubuntu 20.04 LTS Status in xorg package in Ubuntu: New Bug description: I have used ubuntu 21.04 before on this device and reported a bug and it is solved by making psr value to 0. but in ubuntu 20.04LTS is not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..30.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:30:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16
