[Touch-packages] [Bug 1871154] Re: Error message displayed during boot (mountroot hook, premount)
** Description changed: + [Impact] + * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path + + [Test Case] + * Install lvm2 on Ubuntu 20.04 + + [Regression Potential] + * Low, the fix is already part of groovy + + [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: lvm2 (Ubuntu Focal) Status: Confirmed => In Progress -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: In Progress Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
*** This bug is a duplicate of bug 1871154 ***
https://bugs.launchpad.net/bugs/1871154
** This bug has been marked a duplicate of bug 1871154
Error message displayed during boot (mountroot hook, premount)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Status in initramfs-tools:
New
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Package lvm2 contains a init-premount script named /usr/share
/initramfs-tools/scripts/init-premount/lvm2
In this script there is the function call:
add_mountroot_fail_hook "20-lvm2"
Which is defined in /usr/share/initramfs-tools/scripts/functions
In focal's 0.136ubuntu6 , this is defined as:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
}
The final line of the function will execute as
ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"
And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
not exist.
It is clear from lvm2's invocation that it expects the symlink to be
named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
the case:
add_mountroot_fail_hook()
{
mkdir -p /tmp/mountroot-fail-hooks.d
ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
}
focal's version needs to be updated to either support the "$1"
argument or strip the directory from "$0".
To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1873614/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu Focal) Status: New => Confirmed -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: In Progress Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
** Also affects: lvm2 (Ubuntu Focal) Importance: Undecided Status: New -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: In Progress Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
Laurent, I uploaded the package in queue for review, and in my ppa https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa please have a look and report back -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: In Progress Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1866604] Re: gdbtui source window does't display Unicode text
yes,i have this problem too.
--
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/1866604
Title:
gdbtui source window does't display Unicode text
Status in gdb package in Ubuntu:
New
Bug description:
In Ubuntu 20.04, I discovered that the gdb 9 TUI source code window
doesn't display properly the UTF-8 characters (Chinese, Cyrillic,
etc.) but displays correctly only the ASCII ones. For example, the
following source code
printf("Здравей, свят!\n");
appears in the source code window as
printf("^^P^ ^P^ ^Q^┗↑@^^P^ ^P^ ^P^ ^P^ ^^Q^┗↑╝^^P^ ^Q^ ^Q^ \n");
The command windows is not affected (when I type non-ASCII characters
into it, they appear OK).
Additionally, I found out the following:
(1) This bug was introduced in version 8.3;
(2) It affects only some CPU architectures.
In more detail, I tested version "Debian 8.3.1-1" on two 64-bit
machines with the same version of Debian (bullseye/sid), one with
PowerPC, and the other with SPARC. The bug shows up only on the SPARC
machine, not the PowerPC one. I then built the generic version 8.3.1
on a 64-bit ARM machine. The bug didn't show up there. And then, I
built it on a 64-bit MIPS (big endian) machine, where the bug did show
up. Repeated this with version 8.3. The bug showed up again. When I
built the generic version 8.2.1 on the same MIPS machine, the bug
didn't show up. A "diff -u gdb-8.2.1/gdb/tui gdb-8.3/gdb/tui" shows a
lot of changes made in the TUI code of version 8.3 to add some
colourisation to the TUI, and the bug was probably introduced during
this process. Sorry that I can't help more to isolate the bug. But
it's quite strange that it manifests itself only on x86-64 (as I had
found out previously using Ubuntu 20-04), SPARC and MIPS, but not on
ARM and PowerPC. I suppose that because of this, it will be rather
hard to pinpoint.
This bug is similar to the already fixed bug 1275210 where I also
described it but then realised that it has a different origin and is
therefore a different bug, so I report it as a new one now. Someone
already reported this bug as bug 25296 in the gdb Bugzilla which I
confirmed there.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1866604/+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 1877987] Re: apt search coredumping
how can i update my apt package on my focal desktop to get the latest version ? -- 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/1877987 Title: apt search coredumping Status in apt package in Ubuntu: Fix Committed Status in apt source package in Focal: Triaged Bug description: root@citoyx:/var/crash# apt search jdk Sorting... Done Segmentation fault (core dumped) May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in libapt-pkg.so.6.0.0[7f6309bb5000+147000] May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 8d 04 c2 0f root@citoyx:/var/crash# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" apt search is coredumping While apt install/upgrade/update is running fine crash file in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
** Tags added: id-5ed147b927281a2fc1132624 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Released Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. Test Case - 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Regression Potential None, as we are just adding a symlink from linux-firmware to the linux source package hook. Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1872118] Re: DHCP Cluster crashes after a few hours
MM , Thanks I install the isc-dhcp-server from the Bionic-Security repository, and it appears to work. For anyone else here is how to install an older version of the server,and then block updates to the focal version PLEASE USE AT YOUR OWN RISK #Backup your old config sudo mkdir /etc/dhcp.20.04 sudo cp -r /etc/dhcp /etc/dhcp.20.04 #Remove your old isc-dhcp server sudo apt remove isc-dhcp-server #Add the old Bionic repository add-apt-repository 'deb http://security.ubuntu.com/ubuntu bionic-security main' sudo apt update #Install isc-dhcp-server from the bionic-security repository sudo apt-get install -t bionic-security/main isc-dhcp-server sudo systemctl restart isc-dhcp-server #Block upgrades of the package from the Focal Repository edit /etc/apt/preferences.d/repo and add the following lines Package: isc-dhcp-server Pin: release a=bionic-security Pin-Priority: 900 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872118 Title: DHCP Cluster crashes after a few hours Status in isc-dhcp package in Ubuntu: Confirmed Bug description: I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked perfectly until recently, when they started stopping with code=killed, status=6/ABRT. This is being fixed by https://bugs.launchpad.net/bugs/1870729 However now one stops after a few hours with the following errors. One can stay on line but not both. Syslog shows Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ?? nothing in kern.log apport.log shows ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid with dump mode of 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf") ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report /var/crash/_usr_sbin_dhcpd.0.crash /var/crash/_usr_sbin_dhcpd.0.crash shows ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Fri Apr 10 17:20:15 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/sbin/dhcpd ExecutableTimestamp: 1586210315 ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' ProcStatus: Name: dhcpd Umask: 0022 State: D (disk sleep) Tgid: 6828 Ngid: 0 Pid: 6828 PPid: 1 TracerPid: 0 Uid: 113 113 113 113 Gid: 118 118 118 118 FDSize:128 Groups: NStgid:6828 NSpid: 6828 NSpgid:6828 NSsid: 6828 VmPeak: 236244 kB VmSize: 170764 kB VmLck:0 kB VmPin:0 kB VmHWM:12064 kB VmRSS:12064 kB RssAnon: 5940 kB RssFile: 6124 kB RssShmem: 0 kB VmData: 30792 kB VmStk: 132 kB VmExe: 592 kB VmLib: 5424 kB VmPTE: 76 kB VmSwap: 0 kB HugetlbPages: 0 kB CoreDumping: 1 THP_enabled: 1 Threads: 4 SigQ: 0/7609 SigPnd: ShdPnd: SigBlk: SigIgn:1000 SigCgt:00018000 CapInh: CapPrm: CapEff: CapBnd:003f CapAmb: NoNewPrivs:0 Seccomp: 0 Speculation_Store_Bypass: thread vulnerable Cpus_allowed: 3 Cpus_allowed_list: 0-1 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,0001 Mems_allowed_list: 0 voluntary_ctxt_switches: 111 nonvoluntary_ctxt_switches:144 Signal: 6 Uname: Linux 5.4.0-21-generic x86_64 UserGroups: To manage notifications about this bug go to:
[Touch-packages] [Bug 1881314] Re: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04
ddebs.ubuntu.com has caught up now. Thanks for letting us know. ** Changed in: openssl (Ubuntu) Status: In Progress => Fix Released -- 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/1881314 Title: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04 Status in openssl package in Ubuntu: Fix Released Bug description: After a recent update: $ apt-get install libssl1.1-dbgsym The following packages have unmet dependencies: libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.5) but 1.1.1-1ubuntu2.1~18.04.6 is to be installed E: Unable to correct problems, you have held broken packages. The following debug repositories are enabled: $ cat /etc/apt/sources.list.d/ddebs.list deb http://ddebs.ubuntu.com bionic main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse When manually inspecting the apt repository for `bionic-updates`[1], the timestamp is 5/19/2020 (prior to the libssl update on ~5/27), and the only libssl1.1-dbgsym entry is: Package: libssl1.1-dbgsym Package-Type: ddeb Architecture: amd64 Version: 1.1.1-1ubuntu2.1~18.04.5 Meanwhile, I'm unable to find any policy information online about how frequently the ddebs repositories get updated. [1] http://ddebs.ubuntu.com/dists/bionic-updates/main/binary- amd64/Packages.gz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libssl1.1 1.1.1-1ubuntu2.1~18.04.6 Uname: Linux 5.5.17-1rodete4-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Fri May 29 08:47:51 2020 ProcEnviron: LD_LIBRARY_PATH= TERM=xterm PATH=(custom, user) SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1881314/+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 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again
If there is no log from pulseaudio, it means the pulseaudio does not join the connection process yet. The pulseaudio needs to receive a Dbus message (connection request) from bluez first, then it starts to processing bluetooth connection. So in your case, the connection failed in the bluez. Could you connect other bluetooth heapdhones to your laptop? Let's see if it is the problem on your laptop (bluetooth hci controller). If it is, it is highly possible that it is bluetooth driver or firmware's problem. Could you connect your redmi headphone to other laptops? If yes, you could capture bt packages during the reconnection and compare them: close gnome bluetooth applet, $sudo btmon -w good.cap $btmon -r good.cap on the machine with problem: $sudo btmon -w bad.cap $btmon -r bad.cap -- 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/1879582 Title: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again Status in alsa-driver package in Ubuntu: New Bug description: I can connect to my bluetooth phone only the first time after pair the device. It works until disconnecting, (whether by turning off the phone, or putting into the case, or disconnecting in ubuntu settings), and then i turn on the phone again (or remove from the case), i cannot connect until I manually remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. If the Ubuntu/Gnome Settings is opened, i can see the status "connected" blinks, and fastly change to "disconnected". My bluetooth phone works fine with another devices. Ubuntu 20.04 LTS Laptop Acer Aspire Nitro 5 (AN515-52-5771). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: felipe 2149 F pulseaudio /dev/snd/controlC0: felipe 2149 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 19:10:35 2020 InstallationDate: Installed on 2020-04-29 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redmi AirDots_R Symptom_Type: None of the above Title: [Redmi AirDots_R, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+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 1881207] Re: systemd-networkd brings eno1 up and down repeatedly
Thanks for the workaround. I've reinstated the DHCP MTU option, and updated netplan's config. I can confirm that this behaves for me too. -- 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/1881207 Title: systemd-networkd brings eno1 up and down repeatedly Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Bug description: Running on a NUC (BOXNUC8i7BEH3). After updating the `systemd` package past `237-3ubuntu10.32`, I see the onboard NIC link being taken down / up repeatedly, as shown below (dates are from my original notes, but the issue remains the same today). The NIC fails to remain up, and all networking is out of action. Running `systemctl stop systemd-netword` stops this and leaves the NIC in an unknown state. Subsequently running `ifconfig eno1 up && dhclient eno1` allows networking to continue basic operation, albeit without systemd's oversight. My original solution was to downgrade both the `libsystemd0` and `systemd` packages to `237-3ubuntu10.28`. After attempting an `apt update && apt upgrade` again today, exactly the same thing is happening with `237-3ubuntu10.41`. Good versions: - 237-3ubuntu10.28 - 237-3ubuntu10.32 (currently in use, and held) Bad versions: - 237-3ubuntu10.33 - 237-3ubuntu10.38 - 237-3ubuntu10.41 dmesg: [ 360.711367] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 360.714370] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000 [ 360.726189] e1000e :00:1f.6: Interrupt Throttle Rate off [ 361.733073] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500 [ 361.744146] e1000e :00:1f.6: Interrupt Throttle Rate on [ 366.760198] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 366.763375] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000 [ 366.776060] e1000e :00:1f.6: Interrupt Throttle Rate off [ 367.781718] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500 [ 367.792796] e1000e :00:1f.6: Interrupt Throttle Rate on [ 372.808660] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 372.811537] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000 [ 372.823648] e1000e :00:1f.6: Interrupt Throttle Rate off [ 373.830436] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500 [ 373.841512] e1000e :00:1f.6: Interrupt Throttle Rate on journalctl -u systemd-networkd: Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Gained carrier Jan 06 18:04:05 patch systemd-networkd[755]: eno1: DHCPv4 address 10.42.0.5/24 via 10.42.0.3 Jan 06 18:04:05 patch systemd-networkd[755]: eno1: IPv6 successfully enabled Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Configured Jan 06 18:04:06 patch systemd-networkd[755]: eno1: Lost carrier Jan 06 18:04:06 patch systemd-networkd[755]: eno1: DHCP lease lost Jan 06 18:04:06 patch systemd-networkd[755]: eno1: IPv6 successfully enabled Jan 06 18:04:11 patch systemd-networkd[755]: eno1: Gained carrier Jan 06 18:04:11 patch systemd-networkd[755]: eno1: DHCPv4 address 10.42.0.5/24 via 10.42.0.3 Jan 06 18:04:11 patch systemd-networkd[755]: eno1: IPv6 successfully enabled Jan 06 18:04:11 patch systemd-networkd[755]: eno1: Configured Jan 06 18:04:12 patch systemd-networkd[755]: eno1: Lost carrier Jan 06 18:04:12 patch systemd-networkd[755]: eno1: DHCP lease lost Jan 06 18:04:12 patch systemd-networkd[755]: eno1: IPv6 successfully enabled Jan 06 18:04:17 patch systemd-networkd[755]: eno1: Gained carrier Jan 06 18:04:17 patch systemd-networkd[755]: eno1: DHCPv4 address 10.42.0.5/24 via 10.42.0.3 Jan 06 18:04:17 patch systemd-networkd[755]: eno1: IPv6 successfully enabled Jan 06 18:04:17 patch systemd-networkd[755]: eno1: Configured Jan 06 18:04:18 patch systemd-networkd[755]: eno1: Lost carrier Jan 06 18:04:18 patch systemd-networkd[755]: eno1: DHCP lease lost Jan 06 18:04:18 patch systemd-networkd[755]: eno1: IPv6 successfully enabled ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.32 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Thu May 28 23:19:27 2020 InstallationDate: Installed on 2019-06-20 (343 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0dc6:3401 Precision Squared Technology Corp. Bus 001 Device 002: ID 0403:6014 Future Technology
[Touch-packages] [Bug 1881314] Re: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04
** Tags added: id-5e7bc26b5d28f20e31726c8a -- 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/1881314 Title: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04 Status in openssl package in Ubuntu: In Progress Bug description: After a recent update: $ apt-get install libssl1.1-dbgsym The following packages have unmet dependencies: libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.5) but 1.1.1-1ubuntu2.1~18.04.6 is to be installed E: Unable to correct problems, you have held broken packages. The following debug repositories are enabled: $ cat /etc/apt/sources.list.d/ddebs.list deb http://ddebs.ubuntu.com bionic main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse When manually inspecting the apt repository for `bionic-updates`[1], the timestamp is 5/19/2020 (prior to the libssl update on ~5/27), and the only libssl1.1-dbgsym entry is: Package: libssl1.1-dbgsym Package-Type: ddeb Architecture: amd64 Version: 1.1.1-1ubuntu2.1~18.04.5 Meanwhile, I'm unable to find any policy information online about how frequently the ddebs repositories get updated. [1] http://ddebs.ubuntu.com/dists/bionic-updates/main/binary- amd64/Packages.gz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libssl1.1 1.1.1-1ubuntu2.1~18.04.6 Uname: Linux 5.5.17-1rodete4-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Fri May 29 08:47:51 2020 ProcEnviron: LD_LIBRARY_PATH= TERM=xterm PATH=(custom, user) SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1881314/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
I installed the updated packages, and rebooted my system. Unfortunately the error message is still displayed. -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Focal: In Progress Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
Ok, so lvm2 was not broken, but initramfs was! ./initramfs-tools-0.103ubuntu4.11/scripts/functions:ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1" ./initramfs-tools-0.122ubuntu8.16/scripts/functions:ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1" ./initramfs-tools-0.125ubuntu12.2/scripts/functions:ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1" ./initramfs-tools-0.130ubuntu3.9/scripts/functions: ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1" ./initramfs-tools-0.131ubuntu15.2/scripts/functions:ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1" ./initramfs-tools-0.131ubuntu19.2/scripts/functions:ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1" ./initramfs-tools-0.133ubuntu10/scripts/functions: ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1" ./initramfs-tools-0.136ubuntu6/scripts/functions: ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0" ./initramfs-tools-0.137ubuntu7/scripts/functions: ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0" ./initramfs-tools-0.99ubuntu13.5/scripts/functions: ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1" -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in initramfs-tools package in Ubuntu: New Status in lvm2 package in Ubuntu: Triaged Status in initramfs-tools source package in Focal: New Status in lvm2 source package in Focal: In Progress Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+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 1822416] Re: resolve: do not hit CNAME or DNAME entry in NODATA cache
I have the same problem in 237-3ubuntu10.41 amd64 May 30 12:55:59 cerberus systemd-resolved[1595]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. -- 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/1822416 Title: resolve: do not hit CNAME or DNAME entry in NODATA cache Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: The question: DNS A record lookups fail to resolve due to cached CNAME NODATA lookups ... https://askubuntu.com/questions/1063462/18-04-server-systemd-resolve- returns-cached-cname-nodata-for-a-lookup Upstream at Github: Systemd issue 998 - Cached cname NODATA returned for A lookup ... https://github.com/systemd/systemd/issues/9833 Please patch ... https://github.com/systemd/systemd/commit/3740146a4cbd99883af79e375ee4836206dcea4e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1822416/+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 1849399] Re: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key
I submitted a patch to the upstream repository that fixes the invalid parsing in ibus: https://github.com/ibus/ibus/pull/2227 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1849399 Title: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key Status in ibus package in Ubuntu: Triaged Bug description: After upgrade to 19.10, I found that my Delete key was not working as a Delete key, but that instead if I hit Delete twice it would print the character ☭. Since others were not reporting this issue, I had a look around at my input config and remembered that I had ibus configured from a long time ago in order to support Chinese input. If I disable ibus (either by unsetting the environment variables; or by killing ibus-daemon), then the Delete key works again as expected. This is a regression in behavior since Ubuntu 19.04, where I had the same input setup on my desktop but the Delete key worked without problems. I'm also not sure how to disable ibus, now that I am in this situation; or if ibus is expected to always be running. The problem persists if I run ibus-setup and remove Chinese SunPinyin from the list of input methods, leaving only "English - English (US)". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1849399/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
It seems to me that /tmp/mountroot-fail-hooks.d/ never worked correctly. Thus i wonder if it should be dropped altogether. ** Changed in: lvm2 (Ubuntu) Status: Fix Released => Triaged ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in initramfs-tools package in Ubuntu: New Status in lvm2 package in Ubuntu: Triaged Status in initramfs-tools source package in Focal: New Status in lvm2 source package in Focal: In Progress Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+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 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects
I still see this in 20.04 -- 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/1717995 Title: extra domains not removed from resolv.conf when VPN disconnects Status in systemd package in Ubuntu: Fix Released Bug description: I use a VPN (network manager "vpnc" config) to connect to my work network. The gateway is "webvpn.purestorage.com". When I connect, I get "purestorage.com" added to the "search" line in my /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) - which makes perfect sense, the VPN passes this info to me and then I can connect to systems within the work network without having to use a FQDN. The bug (which is a regression from older versions of Ubuntu) is that when I lose my connection to the VPN (either because I disconnect explicitly, or because the network goes down or I suspend my laptop), the "purestorage.com" domain is not removed from those "search" lines. And for some reason this prevents me from resolving webvpn.purestorage.com (which prevents me from reconnecting to the VPN). In particular, if I connect and disconnect my VPN, I get: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: resolve call failed: No appropriate name servers or networks for name found If I then edit /etc/resolv.conf by hand to remove all the purestorage.com entries from the search line - in other words, change $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org purestorage.com dev.purestorage.com to $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org and change nothing else, then: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: 192.30.189.1 (vpn.purestorage.com) -- Information acquired via protocol DNS in 25.9ms. -- Data is authenticated: no I'm not sure if the bug is in systemd, network manager, or some other package, but I'm happy to try any debugging that is helpful to resolve this (no pun intended). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 11:20:17 2017 InstallationDate: Installed on 2016-09-01 (381 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901) MachineType: LENOVO 20FRS2FK00 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET53W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2FK00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2FK00 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717995/+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 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
I have this issue. kbd_mode -s fixes it but then gnome session restarts when I hit enter anywhere. Ubuntu 20.04 LTS Linux 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: Won't Fix Status in xorg-server source package in Xenial: Confirmed Status in console-setup source package in Bionic: Fix Released Status in kbd source package in Bionic: Won't Fix Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Released Status in kbd source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Released Status in kbd source package in Disco: Won't Fix Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: Fix Released Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (kbd) [Impact] * kbd_mode -u is documented to break keyboards in modes other than xlate and unicode, while it is still called by some scripts. Those scripts are called transitively by maintainer scripts such as the one already fixed in console-setup. * To avoid accidentally breaking keyboards a -f option is added to force such breaking mode changes. Without -f only the safe mode changes are performed and an error is printed when the requested mode change is not safe. Next upstream version will also exit with error, but the cherry-picked fix makes kbd_mode return success even when the mode switch is not performed to avoid regressions of scripts. [Test case] * Verify that safe mode switches work and dangerous ones are skipped without -f. Please note that the test will temporarily break the system's keyboard and it is recommended to run the test in a VM. rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $? The keyboard is in Unicode (UTF-8) mode 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in xlate (8-bit) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in some unknown mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in raw (scancode) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in raw (scancode) mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 [Regression Potential] * kbd_mode stops performing breaking mode switches and this may make scripts ineffective when trying to perform a breaking change. This is the intention of the change and the emitter error helps in finding the offending script. The following packages found to call kbd_mode directly: console-setup xinit console-cyrillic initramfs-tools dracut console-tools xview ubiquity's embedded console-setup copy console-data vnc4 The console related packages are expected to execute only safe mode changes because they should operate on consoles only and the rest seem to be safe, too. (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode
[Touch-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
I had time today to test 20.0.4-2ubuntu1~18.04.2 proposed bionic It's working , wow what a long stuff.. Happy end -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: Fix Released Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1881314] Re: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04
Great! Thanks! -- 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/1881314 Title: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04 Status in openssl package in Ubuntu: Fix Released Bug description: After a recent update: $ apt-get install libssl1.1-dbgsym The following packages have unmet dependencies: libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.5) but 1.1.1-1ubuntu2.1~18.04.6 is to be installed E: Unable to correct problems, you have held broken packages. The following debug repositories are enabled: $ cat /etc/apt/sources.list.d/ddebs.list deb http://ddebs.ubuntu.com bionic main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse When manually inspecting the apt repository for `bionic-updates`[1], the timestamp is 5/19/2020 (prior to the libssl update on ~5/27), and the only libssl1.1-dbgsym entry is: Package: libssl1.1-dbgsym Package-Type: ddeb Architecture: amd64 Version: 1.1.1-1ubuntu2.1~18.04.5 Meanwhile, I'm unable to find any policy information online about how frequently the ddebs repositories get updated. [1] http://ddebs.ubuntu.com/dists/bionic-updates/main/binary- amd64/Packages.gz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libssl1.1 1.1.1-1ubuntu2.1~18.04.6 Uname: Linux 5.5.17-1rodete4-amd64 x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Fri May 29 08:47:51 2020 ProcEnviron: LD_LIBRARY_PATH= TERM=xterm PATH=(custom, user) SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1881314/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
** Changed in: lvm2 (Ubuntu) Status: Triaged => Invalid ** Changed in: initramfs-tools (Ubuntu Focal) Status: New => In Progress -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in initramfs-tools package in Ubuntu: Fix Committed Status in lvm2 package in Ubuntu: Invalid Status in initramfs-tools source package in Focal: In Progress Status in lvm2 source package in Focal: Invalid Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
Ok regression introduced in https://launchpad.net/ubuntu/+source/initramfs-tools/0.133ubuntu12 http://launchpadlibrarian.net/453615482/initramfs- tools_0.133ubuntu11_0.133ubuntu12.diff.gz ** Changed in: lvm2 (Ubuntu Focal) Status: In Progress => Invalid ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Committed -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in initramfs-tools package in Ubuntu: Fix Committed Status in lvm2 package in Ubuntu: Triaged Status in initramfs-tools source package in Focal: New Status in lvm2 source package in Focal: Invalid Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
Uploaded initramfs-tools_0.136ubuntu6.20.04.1_source.changes in focal queue, after getting a good feedback from another user being hit from this bug. (my ppa has the fix uploaded) -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in initramfs-tools package in Ubuntu: Fix Committed Status in lvm2 package in Ubuntu: Invalid Status in initramfs-tools source package in Focal: In Progress Status in lvm2 source package in Focal: Invalid Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+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 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+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 1877269] Re: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large)
*** This bug is a duplicate of bug 1881432 *** https://bugs.launchpad.net/bugs/1881432 ** This bug has been marked a duplicate of bug 1881432 System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" -- 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/1877269 Title: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installé : 1:11.1-1ubuntu7.5 Candidat : 1:11.1-1ubuntu7.5 Table de version : *** 1:11.1-1ubuntu7.5 500 500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The OS freezes when using in normal conditions, usually VS Code, Discord app and Spotify in browser. When it does, I need to hard reboot by holding power button. I checked journalctl to confirm it was due to pulseaudio. alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large The above line is always the last to prompt in the boot journal. It does not freeze instantly, it progressively freezes down, but sometime Mozilla Firefox crashes and it freezes no more. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 Uname: Linux 5.1.15-surface-linux-surface x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saravanane 2071 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 7 11:00:37 2020 InstallationDate: Installed on 2019-10-01 (218 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 108.2706.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr108.2706.768:bd04/18/2019:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B09F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.sku: Surface_Pro_4 dmi.product.version: D:0B:09F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877269/+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 1817912] Re: alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily large: 370196 bytes (2098 мс).
*** This bug is a duplicate of bug 1881432 *** https://bugs.launchpad.net/bugs/1881432 ** This bug has been marked a duplicate of bug 1881432 System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1817912 Title: alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily large: 370196 bytes (2098 мс). Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-utils package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: An old issue with ALSA is still present in Ubuntu 16.04.6. The system became extraordinarily slow and hangs at total in around a minute while playing a music (around a few hours in my case). [15:38:51] [root@ThinkPad/var/log]#grep "alsa-sink-CX20751/2 Analog" syslog Feb 27 14:58:50 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily large: 370196 bytes (2098 мс). Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Most likely this is a bug in the ALSA driver «snd_hda_intel». Please report this issue to the ALSA developers. Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: snd_pcm_dump(): Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Soft volume PCM Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Control: PCM Playback Volume Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: min_dB: -51 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: max_dB: 0 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: resolution: 256 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Its setup is: Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: stream : PLAYBACK Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: access : MMAP_INTERLEAVED Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: format : S16_LE Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: subformat: STD Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: channels : 2 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: rate : 44100 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: exact rate : 44100 (44100/1) Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: msbits : 16 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: buffer_size : 16384 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: period_size : 8192 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: period_time : 185759 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: tstamp_mode : ENABLE Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: tstamp_type : MONOTONIC Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: period_step : 1 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: avail_min: 15680 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: period_event : 0 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: start_threshold : -1 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: stop_threshold : 4611686018427387904 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: silence_threshold: 0 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: silence_size : 0 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: boundary : 4611686018427387904 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Slave: Hardware PCM card 1 'HDA Intel PCH' device 0 subdevice 0 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Its setup is: Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: stream : PLAYBACK Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2
[Touch-packages] [Bug 1881432] [NEW] System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
Public bug reported: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "See @ timestamp 13:52:49 for beginning of system hang event" https://bugs.launchpad.net/bugs/1881432/+attachment/5378818/+files/syslog -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: New Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+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 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
** Attachment added: "System hang event @ timestamp 01:45:23 while playing video game" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+attachment/5378819/+files/syslog.5 -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: New Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+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 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
** Description changed: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. + + --- + + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-01 (59 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + ProcCpuinfoMinimal: + processor: 3 + vendor_id: AuthenticAMD + cpu family : 23 + model: 24 + model name : AMD Ryzen 3 3200G with Radeon Vega Graphics + stepping : 1 + microcode: 0x8108109 + cpu MHz : 1782.484 + cache size : 512 KB + physical id : 0 + siblings : 4 + core id : 3 + cpu cores: 4 + apicid : 3 + initial apicid : 3 + fpu : yes + fpu_exception: yes + cpuid level : 13 + wp : yes + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + SourcePackage: pulseaudio + Tags: focal + Uname: Linux 5.4.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + _MarkForUpload: True + dmi.bios.date: 11/14/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P3.70 + dmi.board.name: B450M-HDV R4.0 + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ProcCpuinfoMinimal: processor: 3 vendor_id: AuthenticAMD cpu family : 23 model: 24 model name : AMD Ryzen 3 3200G with Radeon Vega Graphics stepping : 1 microcode: 0x8108109 cpu MHz : 1782.484 cache size : 512 KB physical id : 0 siblings : 4 core id : 3 cpu cores: 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception: yes cpuid level : 13 wp : yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
I can replicate this issue on Ubuntu 18.04 with kernel
4.15.0-101-generic x86_64 and rsync 3.1.2 protocol version 31.
As a workaround for rsync verbose logging with the -vvv flag, you can
instead pass rsync to strace for tracing the system calls and signals
made by rsnc by running "sudo strace rsync". You can still see the
commands and params that are being used by rsync much like -vvv except
strace does not cause it to get stuck syncing plus if you have some
other sort of timeout, strace will also show that.
I hope this is helpful to at least one person reading this looking for a
workaround.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync package in Ubuntu:
Confirmed
Bug description:
In the last few months my home directory backup stopped completing.
I've been able to reproduce the problem on a single subdirectory
although I had to add the --debug=all flag to reproduce it on that
smaller directory. Specifically, this command never completes:
rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
The html2 directory is a copy of
gnuradio-3.7.8.1/build/docs/doxygen/html .
When I strace the command, I see this:
write(1, "sender finished /tmp/html2/atsc_"..., 58sender finished
/tmp/html2/atsc__interleaver_8h__incl.md5
) = 58
write(1, "send_files(338, /tmp/html2/atsc_"..., 59send_files(338,
/tmp/html2/atsc__interleaver_8h__incl.png)
) = 59
open("html2/atsc__interleaver_8h__incl.png", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=264657, ...}) = 0
write(1, "html2/atsc__interleaver_8h__incl"...,
37html2/atsc__interleaver_8h__incl.png
) = 37
read(3,
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\n\253\0\0\2\233\10\6\0\0\0h\242\""...,
262144) = 262144
select(6, [5], [4], [5], {60, 0}) = 2 (in [5], out [4], left {59,
96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95)
= 95
write(4,
"r\311\0\7\177\377\232\237\264\272e\300\300\240\316\264&\314\301\252*\37\256y\225g\373^\315j\370\350"...,
51574) = 51574
select(5, [], [4], [], {60, 0}) = 1 (out [4], left {59, 97})
write(4,
"\7\320\0\7\177\377\234|\7X\223Y\273\255c\27\25f\306\212\202\214#E\272\212t\1\225A\fU"...,
53259) = 53259
select(5, [], [4], [], {60, 0}
The select command times out over and over. I get the same behavior
when trying to back up my entire home directory but I don't need the
--debug=all flag in that case.
lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
apt-cache policy rsync
rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
*** 3.1.0-2ubuntu0.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386
Packages
100 /var/lib/dpkg/status
3.1.0-2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rsync 3.1.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CurrentDesktop: KDE
Date: Wed Dec 23 09:44:17 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-09-18 (1922 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
SourcePackage: rsync
UpgradeStatus: Upgraded to trusty on 2014-12-27 (361 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+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 1881453] Re: Screen corruption on resize (Android Studio start screen)
** Attachment added: "Captura de pantalla de 2020-05-31 04-40-56.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881453/+attachment/5378936/+files/Captura%20de%20pantalla%20de%202020-05-31%2004-40-56.png -- 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/1881453 Title: Screen corruption on resize (Android Studio start screen) Status in xorg package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) (not installed from software center) Android Studio 4.0 Build #AI-193.6911.18.40.6514223, built on May 20, 2020 Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Linux 5.4.0-33-generic GC: ParNew, ConcurrentMarkSweep Memory: 1981M Cores: 8 Registry: ide.new.welcome.screen.force=true Non-Bundled Plugins: 3) It should resize without problems 4) Resizing the window corrupts the image ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 04:41:37 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:380a] Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b] InstallationDate: Installed on 2020-04-23 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 5986:0670 Acer, Inc Lenovo EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=5b998715-8d22-4261-a707-c6958e6eeb81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN63WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN63WW:bd06/14/2018:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 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/1881453/+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 1881453] [NEW] Screen corruption on resize (Android Studio start screen)
Public bug reported: 1) Description:Ubuntu 20.04 LTS Release:20.04 2) (not installed from software center) Android Studio 4.0 Build #AI-193.6911.18.40.6514223, built on May 20, 2020 Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Linux 5.4.0-33-generic GC: ParNew, ConcurrentMarkSweep Memory: 1981M Cores: 8 Registry: ide.new.welcome.screen.force=true Non-Bundled Plugins: 3) It should resize without problems 4) Resizing the window corrupts the image ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 04:41:37 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:380a] Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b] InstallationDate: Installed on 2020-04-23 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 5986:0670 Acer, Inc Lenovo EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=5b998715-8d22-4261-a707-c6958e6eeb81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN63WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN63WW:bd06/14/2018:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 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 -- 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/1881453 Title: Screen corruption on resize (Android Studio start screen) Status in xorg package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) (not installed from software center) Android Studio 4.0 Build #AI-193.6911.18.40.6514223, built on May 20, 2020 Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Linux 5.4.0-33-generic GC: ParNew, ConcurrentMarkSweep Memory: 1981M Cores: 8 Registry: ide.new.welcome.screen.force=true Non-Bundled Plugins: 3) It should resize without problems 4) Resizing the window corrupts the image ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate
[Touch-packages] [Bug 1881432] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378822/+files/CurrentDmesg.txt -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+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 1881432] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378825/+files/PulseList.txt ** Description changed: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- - - DistroRelease: Ubuntu 20.04 - InstallationDate: Installed on 2020-04-01 (59 days ago) - InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) - ApportVersion: 2.20.11-0ubuntu27.2 - Architecture: amd64 - ProcCpuinfoMinimal: - processor: 3 - vendor_id: AuthenticAMD - cpu family : 23 - model: 24 - model name : AMD Ryzen 3 3200G with Radeon Vega Graphics - stepping : 1 - microcode: 0x8108109 - cpu MHz : 1782.484 - cache size : 512 KB - physical id : 0 - siblings : 4 - core id : 3 - cpu cores: 4 - apicid : 3 - initial apicid : 3 - fpu : yes - fpu_exception: yes - cpuid level : 13 - wp : yes - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: pulseaudio - Tags: focal - Uname: Linux 5.4.0-33-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - _MarkForUpload: True - dmi.bios.date: 11/14/2019 - dmi.bios.vendor: American Megatrends Inc. - dmi.bios.version: P3.70 - dmi.board.name: B450M-HDV R4.0 - dmi.board.vendor: ASRock - dmi.chassis.asset.tag: To Be Filled By O.E.M. - dmi.chassis.type: 3 - dmi.chassis.vendor: To Be Filled By O.E.M. - dmi.chassis.version: To Be Filled By O.E.M. - dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: - dmi.product.family: To Be Filled By O.E.M. - dmi.product.name: To Be Filled By O.E.M. - dmi.product.sku: To Be Filled By O.E.M. - dmi.product.version: To Be Filled By O.E.M. - dmi.sys.vendor: To Be Filled By O.E.M. - --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2.
[Touch-packages] [Bug 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
apport information ** Tags added: apport-collected focal ** Description changed: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ProcCpuinfoMinimal: processor: 3 vendor_id: AuthenticAMD cpu family : 23 model: 24 model name : AMD Ryzen 3 3200G with Radeon Vega Graphics stepping : 1 microcode: 0x8108109 cpu MHz : 1782.484 cache size : 512 KB physical id : 0 siblings : 4 core id : 3 cpu cores: 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception: yes cpuid level : 13 wp : yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-01 (59 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + NonfreeKernelModules: wl + Package: pulseaudio 1:13.99.1-1ubuntu3.2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 + Tags: focal + Uname: Linux 5.4.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/14/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P3.70 + dmi.board.name: B450M-HDV R4.0 + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378820/+files/AlsaInfo.txt -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error
[Touch-packages] [Bug 1881447] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
Public bug reported: Upgrading from 16.04 LTS to 18.04 LTS. This is a WEB server with a Let's Encrypt certificate. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Sat May 30 20:00:50 2020 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-09-16 (987 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-05-31 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1881447 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: Upgrading from 16.04 LTS to 18.04 LTS. This is a WEB server with a Let's Encrypt certificate. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Sat May 30 20:00:50 2020 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-09-16 (987 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-05-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1881447/+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 1693900] Re: apt-get update should return exit code != 0 on error
@Julian Andres Klode Is this something you'd be willing to reassess? I saw your old message [1] on the Debian list that says: > The question what a successful update is is complicated and depends on the expections of the person using APT. With that in mind, I'd say there are situations where it's reasonable for the expectation to be that `apt-get update` fails on any error. I completely understand the reasoning for the default behavior and don't expect that to change, but a `--strict` switch (or similar) like the one suggested in the mailing list would be extremely useful to some of us. Even an advanced option like (note this is not real) `-o=APT::Get ::Strict-Mode=1` would be useful if that's easier than a full blown command line switch. I'm not sure I got the syntax right, but I'm sure you get the idea. With containerization gaining popularity, I think there could be a lot of people who have automated build systems set up where they pull a container, (try to) apply security updates, and so on... In those cases, the warnings are really hard to notice since the build system claims everything is OK. Automated build systems that use Docker tend to surface the problem a bit more because of the way they handle DNS [2][3]. The TLDR of those issues is that Docker tries to be smart and sometimes falls back to Google DNS: > level=info msg="No non-localhost DNS nameservers are left in resolv.conf. Using default external servers: [nameserver 8.8.8.8 nameserver 8.8.4.4]" For anyone using an internal APT mirror, a bunch of assumptions get broken, but nothing throws an error to surface the break down. I bet there's a subset of developers that don't realize their automated builds could be failing to apply updates. I spent several hours today trying to find a reasonable workaround, but all I could find were people trying to parse apt-get's output in a variety of creative ways. AFAIK, there aren't any good workarounds. I even tried fumbling my way through the source code to see if there were any existing options to control the behavior, but didn't have much luck (I don't know C++ though). So, I guess I have two questions. First, is there _any_ way to make `apt-get update` fail on any error? Second, if the answer to my first question is no, would you consider adding an option that lets us control it? 1) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776152#15 2) https://github.com/moby/moby/issues/23910 3) https://github.com/moby/libnetwork/issues/1654 ** Bug watch added: Debian Bug tracker #776152 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776152 ** Bug watch added: github.com/moby/moby/issues #23910 https://github.com/moby/moby/issues/23910 ** Bug watch added: github.com/moby/libnetwork/issues #1654 https://github.com/moby/libnetwork/issues/1654 -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Triaged Bug description: When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1881434] [NEW] PCI/internal sound card not detected
Public bug reported: In my PC is a Intel Corporation Device 2284 (rev 35). When I open the sound preferences, I only see a dummy output. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat May 30 22:38:22 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2019-02-13 (471 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 0M08DC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1881434 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: In my PC is a Intel Corporation Device 2284 (rev 35). When I open the sound preferences, I only see a dummy output. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat May 30 22:38:22 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2019-02-13 (471 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 0M08DC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1881434/+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 1881437] [NEW] IBus right click on system tray shows in top left corner hindering screen edges on KDE desktop
Public bug reported: Right-clicking IBus on system tray shows options on the top left corner of the desktop taking up space and hindering screen edges to be executed on KDE desktop. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: kde -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1881437 Title: IBus right click on system tray shows in top left corner hindering screen edges on KDE desktop Status in ibus package in Ubuntu: New Bug description: Right-clicking IBus on system tray shows options on the top left corner of the desktop taking up space and hindering screen edges to be executed on KDE desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1881437/+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 1881435] [NEW] Xorg freeze
You have been subscribed to a public bug: Screen freezes randomly. Keyboard and mouse do not work at that time. I am not able to ssh to the computer or access tty. I am able to do only a hard reset. I tried some troubleshooting myself, but with my novice expertise with ubuntu. The freeze is more or less random. But it is possibly more frequent when running a video, like a youtube video in a browser. Freeze is more frequenty when going full screen with a video, a VM machine or a remote desktop through vnc4server. 1. Tried removing some software like chrome, dropbox, virtualbox, etc. That did not help. 2. Tried reverting back to an older version of Ubuntu, like 16.04 with a 4.15 kernel. That did not help either. 3. Tried other distros like Mint and Fedora. Still had problem. 4. Tried running with NVidia driver and xserver-xorg. The problem occured with both. 5. Tried NVidia as well as Integrated Intel graphics cards. Problem occured in both. 6. Tried all the suggestions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 that were applicable. None of the suggestions helped. 7. Finally tried Windows 7 and there was no problem. Tested for 12 hours and experienced no crash/freeze with youtube running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 12:36:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2651] InstallationDate: Installed on 2020-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4b614f0e-95f5-4cc7-8157-bf617c9b1571 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 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 N/A 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 freeze ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/1881435 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 1881447] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
I Found that there was a symbolic link in /etc/ssl/certs to a non- existent file. So how do I recover after removing the symbolic link? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1881447 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: Upgrading from 16.04 LTS to 18.04 LTS. This is a WEB server with a Let's Encrypt certificate. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Sat May 30 20:00:50 2020 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-09-16 (987 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-05-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1881447/+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 1866923] Re: Wifi connection says it's connected but this is not true after the computer goes into a sleep status
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1866923 Title: Wifi connection says it's connected but this is not true after the computer goes into a sleep status Status in network-manager package in Ubuntu: Expired Bug description: The wifi is connected and working correctly when powered on, however when I close the laptop lid, which I think puts it to sleep, and then reopen it, it says it's connected according to the icon but this is not true. A workaround is turning on Airplane mode and then switching it back on again. It then reconnects and is then fine again. Unless I close the lid and then the process repeats again. I guess this is to do with the wifi driver but I don't know what package it is so I just picked network-manager, sorry - I'm trying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 19:29:03 2020 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.68.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.68.0/24 dev wlp1s0 proto kernel scope link src 192.168.68.18 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1866923/+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 1881432] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378824/+files/ProcCpuinfoMinimal.txt -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+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 1881432] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378823/+files/Dependencies.txt -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+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 1413232] Re: [systemd] dhclient causes apparmor warnings against /run/systemd/journal/dev-log
Potential regression? I think I'm seeing this on Ubuntu 20.04:
May 31 04:35:10 HOSTNAME audit[2997513]: AVC apparmor="DENIED"
operation="sendmsg" profile="/{,usr/}sbin/dhclient" name="/log"
pid=2997513 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0
ouid=0
dpkg --list | grep apparmor
ii apparmor 2.13.3-7ubuntu5
amd64user-space parser utility for AppArmor
ii libapparmor1:amd64 2.13.3-7ubuntu5
amd64changehat AppArmor library
--
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/1413232
Title:
[systemd] dhclient causes apparmor warnings against
/run/systemd/journal/dev-log
Status in AppArmor:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
When running a system with systemd, the logs get filled with dhclient
getting denied access to the below.
Example dmesg output:
[ 28.037120] audit: type=1400 audit(1421846274.704:51): apparmor="DENIED"
operation="sendmsg" profile="/sbin/dhclient"
name="/run/systemd/journal/dev-log" pid=1678 comm="dhclient" requested_mask="w"
denied_mask="w" fsuid=0 ouid=0
[ 45.367871] audit: type=1400 audit(1421846292.048:52): apparmor="DENIED"
operation="sendmsg" profile="/sbin/dhclient"
name="/run/systemd/journal/dev-log" pid=1678 comm="dhclient" requested_mask="w"
denied_mask="w" fsuid=0 ouid=0
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: isc-dhcp-client 4.3.1-5ubuntu2
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
Date: Wed Jan 21 09:26:16 2015
DhclientLeases:
InstallationDate: Installed on 2015-01-08 (12 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150108)
ProcEnviron:
LANGUAGE=en_US
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1413232/+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 1881432] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378821/+files/AudioDevicesInUse.txt -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+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 1881435] Re: Xorg freeze
** 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/1881435 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Screen freezes randomly. Keyboard and mouse do not work at that time. I am not able to ssh to the computer or access tty. I am able to do only a hard reset. I tried some troubleshooting myself, but with my novice expertise with ubuntu. The freeze is more or less random. But it is possibly more frequent when running a video, like a youtube video in a browser. Freeze is more frequenty when going full screen with a video, a VM machine or a remote desktop through vnc4server. 1. Tried removing some software like chrome, dropbox, virtualbox, etc. That did not help. 2. Tried reverting back to an older version of Ubuntu, like 16.04 with a 4.15 kernel. That did not help either. 3. Tried other distros like Mint and Fedora. Still had problem. 4. Tried running with NVidia driver and xserver-xorg. The problem occured with both. 5. Tried NVidia as well as Integrated Intel graphics cards. Problem occured in both. 6. Tried all the suggestions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 that were applicable. None of the suggestions helped. 7. Finally tried Windows 7 and there was no problem. Tested for 12 hours and experienced no crash/freeze with youtube running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01: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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 12:36:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2651] InstallationDate: Installed on 2020-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4b614f0e-95f5-4cc7-8157-bf617c9b1571 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 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 N/A 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/1881435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
Let us see if the HDMI sound card or analogue sound card introduced this problem, please edit /etc/modprobe.d/alsa-base.conf, add "options snd- hda-intel enable=0,1", reboot, this will disable the hdmi audio sound card (please check if the hdmi sound card is disabled successfully by pacmd list-cards). If the hdmi audio is disabled, please see if the problem still happens or not. If the problem still happens, please change enable=0,1 to enable=1,0, this will disable analog sound card, and let us see if the problem happens or not. -- 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/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+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
