[Touch-packages] [Bug 2022836] [NEW] package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de er
Public bug reported: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2023c-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 3 13:13:18 2023 ErrorMessage: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-09-28 (247 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: tzdata Title: package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2022836 Title: package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 Status in tzdata package in Ubuntu: New Bug description: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2023c-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 3 13:13:18 2023 ErrorMessage: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-09-28 (247 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: tzdata Title: package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2022836/+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 2022835] [NEW] package cups 2.4.1op1-1ubuntu4.2 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: W [01/Jun/2023:00:00:26 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:09:56 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:13:20 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 Date: Sat Jun 3 13:13:20 2023 ErrorMessage: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-09-28 (247 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for HP_Color_LaserJet_E55040_5A6F72: implicitclass://HP_Color_LaserJet_E55040_5A6F72/ device for HP_LaserJet_P4014_319155: implicitclass://HP_LaserJet_P4014_319155/ device for HP_LaserJet_P4014_319155@NPI319155.local: implicitclass://HP_LaserJet_P4014_319155%40NPI319155.local/ device for L5190: dnssd://EPSON%20L5190%20Series._ipp._tcp.local/?uuid=cfe92100-67c4-11d4-a45f-e0bb9e531389 MachineType: Dell Inc. Latitude 5430 Papersize: letter PpdFiles: HP_Color_LaserJet_E55040_5A6F72: HP Color LaserJet E55040, driverless, cups-filters 1.28.15 L5190: EPSON L5190 Series, driverless, cups-filters 1.28.15 HP_LaserJet_P4014_319155@NPI319155.local: HP LaserJet P4014, driverless, cups-filters 1.28.15 HP_LaserJet_P4014_319155: HP LaserJet P4014, driverless, cups-filters 1.28.15 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=2efb7e3e-d9e5-4dda-a70f-e5c6425f913c ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=2efb7e3e-d9e5-4dda-a70f-e5c6425f913c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: cups Title: package cups 2.4.1op1-1ubuntu4.2 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2022 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 03G0RF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd06/20/2022:br1.4:svnDellInc.:pnLatitude5430:pvr:rvnDellInc.:rn03G0RF:rvrA00:cvnDellInc.:ct10:cvr:sku0B04: dmi.product.family: Latitude dmi.product.name: Latitude 5430 dmi.product.sku: 0B04 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2022835 Title: package cups 2.4.1op1-1ubuntu4.2 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 Status in cups package in Ubuntu: New Bug description: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: W [01/Jun/2023:00:00:26 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:09:56 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:13:20 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 Date: Sat Jun 3 13:13:20 2023 ErrorMessage: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-09-28 (247 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for HP_Color_LaserJet_E55040_5A6F72: implicitclass://HP_Color_LaserJet_E55040_5A6F72/ device for HP_LaserJet_P4014_319155: implicitclass://HP_LaserJ
[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried
I restored the verification-done-focal tag because I already verified this bug on focal (see comment #24). I think the linux-bluefield kernel patch is not appropriate for this bug. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1856871 Title: i/o error if next unused loop device is queried Status in linux package in Ubuntu: Fix Released Status in parted package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] * There's an I/O error on fsync() in a detached loop device if it has been previously attached. The issue is that write cache is enabled in the attach path in loop_configure() but it isn't disabled in the detach path; thus it remains enabled in the block device regardless of whether it is attached or not. * fsync() on detached loop devices can be called by partition tools and commands run by sosreport, so the unexpected kernel error message might surprise users or even distract from the actual issue being investigatedr. It might also trigger alerts in logging/monitoring/alerting stacks [Fix] * Disable write cache in the detach path [Test Plan] * Attach and detach an image to a loop device and test fsync return value aterwards # DEV=/dev/loop7 # IMG=/tmp/image # truncate --size 1M $IMG # losetup $DEV $IMG # losetup -d $DEV Before: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= -1 EIO (Input/output error) Warning: Error fsyncing/closing /dev/loop7: Input/output error [ 982.529929] blk_update_request: I/O error, dev loop7, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 After: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= 0 [Where problems could occur] * The detach path for block devices is modified. Worst case scenario would be an error when detaching loop devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+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 1856871] Re: i/o error if next unused loop device is queried
Tested with kernel 5.4.0-149.166 in focal. Test plan works Ok. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1856871 Title: i/o error if next unused loop device is queried Status in linux package in Ubuntu: Fix Released Status in parted package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] * There's an I/O error on fsync() in a detached loop device if it has been previously attached. The issue is that write cache is enabled in the attach path in loop_configure() but it isn't disabled in the detach path; thus it remains enabled in the block device regardless of whether it is attached or not. * fsync() on detached loop devices can be called by partition tools and commands run by sosreport, so the unexpected kernel error message might surprise users or even distract from the actual issue being investigatedr. It might also trigger alerts in logging/monitoring/alerting stacks [Fix] * Disable write cache in the detach path [Test Plan] * Attach and detach an image to a loop device and test fsync return value aterwards # DEV=/dev/loop7 # IMG=/tmp/image # truncate --size 1M $IMG # losetup $DEV $IMG # losetup -d $DEV Before: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= -1 EIO (Input/output error) Warning: Error fsyncing/closing /dev/loop7: Input/output error [ 982.529929] blk_update_request: I/O error, dev loop7, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 After: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= 0 [Where problems could occur] * The detach path for block devices is modified. Worst case scenario would be an error when detaching loop devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+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 1856871] Re: i/o error if next unused loop device is queried
** Also affects: parted (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: udev (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: parted (Ubuntu Bionic) ** No longer affects: snapd (Ubuntu Bionic) ** No longer affects: systemd (Ubuntu Bionic) ** No longer affects: udev (Ubuntu Bionic) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Jorge Merlino (jorge-merlino) -- 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/1856871 Title: i/o error if next unused loop device is queried Status in linux package in Ubuntu: Fix Released Status in parted package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] * There's an I/O error on fsync() in a detached loop device if it has been previously attached. The issue is that write cache is enabled in the attach path in loop_configure() but it isn't disabled in the detach path; thus it remains enabled in the block device regardless of whether it is attached or not. * fsync() on detached loop devices can be called by partition tools and commands run by sosreport, so the unexpected kernel error message might surprise users or even distract from the actual issue being investigatedr. It might also trigger alerts in logging/monitoring/alerting stacks [Fix] * Disable write cache in the detach path [Test Plan] * Attach and detach an image to a loop device and test fsync return value aterwards # DEV=/dev/loop7 # IMG=/tmp/image # truncate --size 1M $IMG # losetup $DEV $IMG # losetup -d $DEV Before: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= -1 EIO (Input/output error) Warning: Error fsyncing/closing /dev/loop7: Input/output error [ 982.529929] blk_update_request: I/O error, dev loop7, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 After: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= 0 [Where problems could occur] * The detach path for block devices is modified. Worst case scenario would be an error when detaching loop devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+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 1856871] Re: i/o error if next unused loop device is queried
** Description changed: - This is reproducible in Bionic and late. - Here's an example running 'focal': + [Impact] - $ lsb_release -cs - focal + * There's an I/O error on fsync() in a detached loop device if it has + been previously attached. The issue is that write cache is enabled in + the attach path in loop_configure() but it isn't disabled in the detach + path; thus it remains enabled in the block device regardless of whether + it is attached or not. - $ uname -r - 5.3.0-24-generic + * fsync() on detached loop devices can be called by partition tools and + commands run by sosreport, so the unexpected kernel error message might + surprise users or even distract from the actual issue being + investigatedr. It might also trigger alerts in + logging/monitoring/alerting stacks - The error is: - blk_update_request: I/O error, dev loop2, sector 0 + [Fix] - and on more recent kernel: + * Disable write cache in the detach path - kernel: [18135.185709] blk_update_request: I/O error, dev loop18, sector - 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 + [Test Plan] + * Attach and detach an image to a loop device and test fsync return + value aterwards - How to trigger it: - $ sosreport -o block + # DEV=/dev/loop7 - or more precisely the cmd causing the situation inside the block plugin: - $ parted -s $(losetup -f) unit s print + # IMG=/tmp/image + # truncate --size 1M $IMG - https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52 + # losetup $DEV $IMG + # losetup -d $DEV - but if I run it on the next next unused loop device, in this case - /dev/loop3 (which is also unused), no errors. + Before: + # strace -e fsync parted -s $DEV print 2>&1 | grep fsync + fsync(3)= -1 EIO (Input/output error) + Warning: Error fsyncing/closing /dev/loop7: Input/output error + [ 982.529929] blk_update_request: I/O error, dev loop7, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 - While I agree that sosreport shouldn't query unused loop devices, there - is definitely something going on with the next unused loop device. + After: + # strace -e fsync parted -s $DEV print 2>&1 | grep fsync + fsync(3)= 0 - What is differentiate loop2 and loop3 and any other unused ones ? + [Where problems could occur] - 3 things so far I have noticed: - * loop2 is the next unused loop device (losetup -f) - * A reboot is needed (if some loop modification (snap install, mount loop, ...) has been made at runtime - * I have also noticed that loop2 (or whatever the next unused one is) have some stat as oppose to other unused loop devices. The stat exist already right after the system boot for the next unused loop device. - - /sys/block/loop2/stat - :: - 2 0 10 0 1 0 0 0 0 0 0 - - 2 = number of read I/Os processed - 10 = number of sectors read - 1 = number of write I/Os processed - - Explanation of each column: - https://www.kernel.org/doc/html/latest/block/stat.html - - while /dev/loop3 doesn't - - /sys/block/loop3/stat - :: - 0 0 0 0 0 0 0 0 0 0 0 - - Which tells me that something during the boot process most likely - acquired (on purpose or not) the next unused loop and possibly didn't - released it well enough. - - If loop2 is generating errors, and I install a snap, the snap squashfs - will take loop2, making loop3 the next unused loop device. - - If I query loop3 with 'parted' right after, no errors. - - If I reboot, and query loop3 again, then no I'll have an error. - - To triggers the errors it need to be after a reboot and it only impact - the first unused loop device available (losetup -f). - - This was tested with focal/systemd whic his very close to latest - upstream code. - - This has been test with latest v5.5 mainline kernel as well. - - For now, I don't think it's a kernel problem, I'm more thinking of a - userspace misbehaviour dealing with loop device (or block device) at - boot. + * The detach path for block devices is modified. Worst case scenario + would be an error when detaching loop devices. ** Also affects: parted (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: udev (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: udev (Ubuntu Focal) ** No longer affects: systemd (Ubuntu Focal) ** No longer affects: snapd (Ubuntu Focal) ** No longer affects: parted (Ubuntu Focal) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jorge Merlino (jorge-merlin
[Touch-packages] [Bug 1987523] Re: Pulsaudio crashes once BT microphone is connected
This big is fixed in kinetic ** Also affects: pulseaudio (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu Jammy) Assignee: (unassigned) => Jorge Merlino (jorge-merlino) ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Jammy) Importance: Undecided => Low -- 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/1987523 Title: Pulsaudio crashes once BT microphone is connected Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Jammy: New Bug description: When I connect my BT headset with microphone and change profile to HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports: Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX (AVRCP) as /devices/virtual/input/input37 Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80% Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data descriptor : 0x1 terminating Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of process 50808 owned by '1000' RT at priority 5. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: [51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at ../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). Aborting. Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash report... Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie Aug 24 13:44:24 p14s systemd[1]: Started crash report submission. Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: /var/lock/whoopsie/lock Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully. Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk I've identified the upstream fix for this: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e I've built packages with the fix and can confirm that it does solve the problem. Packages are available at: https://launchpad.net/~ivoks/+archive/ubuntu/pulse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1987523/+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 1987523] Re: Pulsaudio crashes once BT microphone is connected
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Jorge Merlino (jorge-merlino) -- 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/1987523 Title: Pulsaudio crashes once BT microphone is connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: When I connect my BT headset with microphone and change profile to HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports: Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX (AVRCP) as /devices/virtual/input/input37 Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80% Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data descriptor : 0x1 terminating Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of process 50808 owned by '1000' RT at priority 5. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: [51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at ../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). Aborting. Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash report... Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie Aug 24 13:44:24 p14s systemd[1]: Started crash report submission. Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: /var/lock/whoopsie/lock Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully. Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk I've identified the upstream fix for this: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e I've built packages with the fix and can confirm that it does solve the problem. Packages are available at: https://launchpad.net/~ivoks/+archive/ubuntu/pulse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1987523/+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 1979126] [NEW] [22V280-L.BY31P1, Realtek ALC256, Speaker, Internal] No sound at all
Public bug reported: Som desaparece e não consigo escutar audios de youtube ou outros ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alberto1041 F pulseaudio /dev/snd/pcmC0D0c: alberto1041 F...m pulseaudio /dev/snd/pcmC0D0p: alberto1041 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 18 22:28:20 2022 InstallationDate: Installed on 2022-03-22 (89 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alberto1041 F pulseaudio /dev/snd/pcmC0D0c: alberto1041 F...m pulseaudio /dev/snd/pcmC0D0p: alberto1041 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [22V280-L.BY31P1, Realtek ALC256, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 22VC0251 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22V280 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr22VC0251X64:bd08/01/2018:br0.1:svnLGElectronics:pn22V280-L.BY31P1:pvr0.1:rvnLGElectronics:rn22V280:rvrFAB1:cvnLGElectronics:ct13:cvr0.1:sku: dmi.product.family: V Series dmi.product.name: 22V280-L.BY31P1 dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1979126 Title: [22V280-L.BY31P1, Realtek ALC256, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Som desaparece e não consigo escutar audios de youtube ou outros ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alberto1041 F pulseaudio /dev/snd/pcmC0D0c: alberto1041 F...m pulseaudio /dev/snd/pcmC0D0p: alberto1041 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 18 22:28:20 2022 InstallationDate: Installed on 2022-03-22 (89 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alberto1041 F pulseaudio /dev/snd/pcmC0D0c: alberto1041 F...m pulseaudio /dev/snd/pcmC0D0p: alberto1041 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [22V280-L.BY31P1, Realtek ALC256, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 22VC0251 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 22V280 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr22VC0251X64:bd08/01/2018:br0.1:svnLGElectronics:pn22V280-L.BY31P1:pvr0.1:rvnLGElectronics:rn22V280:rvrFAB1:cvnLGElectronics:ct13:cvr0.1:sku: dmi.product.family: V Series dmi.product.name: 22V280-L.BY31P1 dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1979126/+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 1965603] [NEW] [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound at all
Public bug reported: computer model:notebook 9 pen 15" nvidia GPU: Nvidia geforce mx150 Sound: AKG stereo speakers High definition audio no sound whats so ever, not even in bluetooth. removed and reinstalled alsa and pulse audio, then restarted, just to have no sound still. checked settings in sound menu to see if I can select proper audio device but only one selection is given. Any ideas on how to go about in fixing issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: densetsu 1521 F pulseaudio /dev/snd/pcmC0D0c: densetsu 1521 F...m pulseaudio /dev/snd/pcmC0D0p: densetsu 1521 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 19:19:42 2022 InstallationDate: Installed on 2022-03-17 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1033 F pulseaudio densetsu 1521 F pulseaudio /dev/snd/pcmC0D0c: densetsu 1521 F...m pulseaudio /dev/snd/pcmC0D0p: densetsu 1521 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P07RES.076.190919.SP dmi.board.asset.tag: No Asset Tag dmi.board.name: NP950SBE-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9849A0L-C01-G001-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP07RES.076.190919.SP:bd09/19/2019:br5.13:svnSAMSUNGELECTRONICSCO.,LTD.:pn950SBE/951SBE:pvrP07RES:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP950SBE-X01US:rvrSGL9849A0L-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PRES: dmi.product.family: Notebook 9 Series dmi.product.name: 950SBE/951SBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PRES dmi.product.version: P07RES dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1965603 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: computer model:notebook 9 pen 15" nvidia GPU: Nvidia geforce mx150 Sound: AKG stereo speakers High definition audio no sound whats so ever, not even in bluetooth. removed and reinstalled alsa and pulse audio, then restarted, just to have no sound still. checked settings in sound menu to see if I can select proper audio device but only one selection is given. Any ideas on how to go about in fixing issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: densetsu 1521 F pulseaudio /dev/snd/pcmC0D0c: densetsu 1521 F...m pulseaudio /dev/snd/pcmC0D0p: densetsu 1521 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 19:19:42 2022 InstallationDate: Installed on 2022-03-17 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1033 F pulseaudio densetsu 1521 F pulseaudio /dev/snd/pcmC0D0c: densetsu 1521 F...m pulseaudio /dev/snd/pcmC0D0p:
[Touch-packages] [Bug 1883534] Re: Screen flickering
*** This bug is a duplicate of bug 1853094 *** https://bugs.launchpad.net/bugs/1853094 I have de same problem, I change to star ubuntu wayland, but in different moments, ubuntu again present the same problem, this occurs when update the ubuntu because never see this problem the last year in my laptop. Where is the Answer to resolve this problem, I have intel graphic.. -- 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/1883534 Title: Screen flickering Status in xorg package in Ubuntu: Confirmed Bug description: To whom it may concern, As stated I have screen flickerings (see lightning like flickering on photo attached for portrait screen, for horizontal screen I also have screen flickering on the upper part but hard to catch in a photo) on freshly installed Ubuntu 20.04 LTS. I have tried this: https://askubuntu.com/questions/1231441/ubuntu-screen-flickering and this: https://learnubuntumate.weebly.com/screen-tearing-on-intel- graphics.html without success. I have also seen some other people mentioning screen flickering on ubuntu 20.04 here: https://www.reddit.com/r/Ubuntu/comments/fvk536/anyone_else_noticing_window_flickering_on_ubuntu/ without solution. I also know that it is very unlikely hardware problem because my screens were displaying well on archlinux. I think my graphic card info are already included in the report but just in case: Intel Corporation UHD Graphics 630. Might be intel driver problems ? Could you help me on this please ? Best regards, Jeremy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 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: Mon Jun 15 15:05:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] InstallationDate: Installed on 2020-06-12 (2 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 002: ID 046a:0023 Cherry GmbH Keyboard Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 9: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=81cee77a-b529-4dac-9834-dc6d5ab2dc16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0615 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0615:bd04/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1917350] [NEW] cron not honoring pam_group.so groups
Public bug reported: When a job is invoked from cron and the pam_group.so is configured to add supplementary groups it DOES NOT work as expected. pam_group should provide membership based /etc/security/group.conf and it is working fine if you test with login or sudo. After some tests I've compiled pam_group.so in DEBUG and I can confirm that pam_setcred in being called by cron and the module is adding the expected groups membership. Then, checking do_command.c of cron I found there is need to call pam_setcred(pamh, PAM_REINITIALIZE_CRED | PAM_SILENT) after fork() the final patch should be something like #if defined(USE_PAM) if (pamh != NULL) { pam_setcred(pamh, PAM_REINITIALIZE_CRED | PAM_SILENT); } #endif ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cron 3.0pl1-136ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 1 15:49:42 2021 InstallationDate: Installed on 2021-01-21 (39 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1917350 Title: cron not honoring pam_group.so groups Status in cron package in Ubuntu: New Bug description: When a job is invoked from cron and the pam_group.so is configured to add supplementary groups it DOES NOT work as expected. pam_group should provide membership based /etc/security/group.conf and it is working fine if you test with login or sudo. After some tests I've compiled pam_group.so in DEBUG and I can confirm that pam_setcred in being called by cron and the module is adding the expected groups membership. Then, checking do_command.c of cron I found there is need to call pam_setcred(pamh, PAM_REINITIALIZE_CRED | PAM_SILENT) after fork() the final patch should be something like #if defined(USE_PAM) if (pamh != NULL) { pam_setcred(pamh, PAM_REINITIALIZE_CRED | PAM_SILENT); } #endif ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cron 3.0pl1-136ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Mar 1 15:49:42 2021 InstallationDate: Installed on 2021-01-21 (39 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1917350/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
** Changed in: hud (Ubuntu Xenial) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in Unity HUD: Confirmed Status in Application Menu Indicator: Confirmed Status in Unity: Won't Fix Status in firefox package in Ubuntu: Incomplete Status in hud package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Status in firefox source package in Xenial: Incomplete Status in hud source package in Xenial: In Progress Status in unity source package in Xenial: Invalid Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/987060/+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 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]
Hello Karsten, Can you check comments https://bugs.launchpad.net/dhcp/+bug/1872118/comments/62 and https://bugs.launchpad.net/dhcp/+bug/1872118/comments/63 and validate the versions? * Also, could be possible to upload the crash report here? and the output of dpkg -l Thanks, Jorge -- 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/1872106 Title: isc-dhcp-server crashing constantly [Ubuntu 20.04] Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Focal: Confirmed Bug description: isc-dhcp-server crashing constantly (sometimes within seconds or minutes, sometimes within hours) with the following error messages: Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service. Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ?? Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ?? Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ?? Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ?? Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ?? Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+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: [SRU] DHCP Cluster crashes after a few hours
** No longer affects: isc-dhcp (Ubuntu) ** No longer affects: isc-dhcp (Ubuntu Focal) ** No longer affects: isc-dhcp (Ubuntu Groovy) ** Changed in: bind9-libs (Ubuntu Groovy) Importance: Undecided => High -- 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: [SRU] DHCP Cluster crashes after a few hours Status in DHCP: New Status in bind9-libs package in Ubuntu: Fix Released Status in bind9-libs source package in Focal: Fix Committed Status in bind9-libs source package in Groovy: Fix Released Bug description: [Description] isc-dhcp-server uses libisc-export (coming from bind9-libs package) for handling the socket event(s) when configured in peer mode (master/secondary). It's possible that a sequence of messages dispatched by the master that requires acknowledgment from its peers holds a socket in a pending to send state, a timer or a subsequent write request can be scheduled into this socket and the !sock->pending_send assertion will be raised when trying to write again at the time data hasn't been flushed entirely and the pending_send flag hasn't been reset to 0 state. If this race condition happens, the following stacktrace will be hit: (gdb) info threads Id Target Id Frame * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait (futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52 3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, processes_to_wake=1, futex_word=) at ../sysdeps/nptl/futex-internal.h:364 4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable (private=, expected=0, futex_word=0x7fb4de6cd0d0) at ../sysdeps/nptl/futex-internal.h:183 (gdb) frame 2 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 (gdb) bt #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 #4 process_fd (writeable=, readable=, fd=11, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054 #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211 #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397 #7 0x7fb4dea68609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb4deba4103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) frame 3 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 4041 in ../../../../lib/isc/unix/socket.c (gdb) p sock->pending_send $2 = 1 [TEST CASE] 1) Install isc-dhcp-server in 2 focal machine(s). 2) Configure peer/cluster mode as follows: Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/ Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/ 2) Run dhcpd as follows in both machine(s) # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4 3) Leave the cluster running for a long (2h) period until the crash/race condition is reproduced. [REGRESSION POTENTIAL] * The fix will prevent the assertion to happen in the dispatch_send path, later versions of isch-dhcp upstream lack this logic and entirely removed the existence of this flag. Therefore, removing the need for this assertion at process_fd shouldn't be problematic. To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1872118/+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: [SRU] DHCP Cluster crashes after a few hours
** Patch added: "lp-1872118-focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+attachment/5400761/+files/lp-1872118-focal.debdiff -- 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: [SRU] DHCP Cluster crashes after a few hours Status in DHCP: New Status in bind9-libs package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in bind9-libs source package in Focal: In Progress Status in isc-dhcp source package in Focal: In Progress Status in bind9-libs source package in Groovy: In Progress Status in isc-dhcp source package in Groovy: In Progress Bug description: [Description] isc-dhcp-server uses libisc-export (coming from bind9-libs package) for handling the socket event(s) when configured in peer mode (master/secondary). It's possible that a sequence of messages dispatched by the master that requires acknowledgment from its peers holds a socket in a pending to send state, a timer or a subsequent write request can be scheduled into this socket and the !sock->pending_send assertion will be raised when trying to write again at the time data hasn't been flushed entirely and the pending_send flag hasn't been reset to 0 state. If this race condition happens, the following stacktrace will be hit: (gdb) info threads Id Target Id Frame * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait (futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52 3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, processes_to_wake=1, futex_word=) at ../sysdeps/nptl/futex-internal.h:364 4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable (private=, expected=0, futex_word=0x7fb4de6cd0d0) at ../sysdeps/nptl/futex-internal.h:183 (gdb) frame 2 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 (gdb) bt #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 #4 process_fd (writeable=, readable=, fd=11, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054 #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211 #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397 #7 0x7fb4dea68609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb4deba4103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) frame 3 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 4041 in ../../../../lib/isc/unix/socket.c (gdb) p sock->pending_send $2 = 1 [TEST CASE] 1) Install isc-dhcp-server in 2 focal machine(s). 2) Configure peer/cluster mode as follows: Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/ Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/ 2) Run dhcpd as follows in both machine(s) # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4 3) Leave the cluster running for a long (2h) period until the crash/race condition is reproduced. [REGRESSION POTENTIAL] * The fix will prevent the assertion to happen in the dispatch_send path, later versions of isch-dhcp upstream lack this logic and entirely removed the existence of this flag. Therefore, removing the need for this assertion at process_fd shouldn't be problematic. To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1872118/+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: [SRU] DHCP Cluster crashes after a few hours
** Patch added: "lp-1872118-groovy.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+attachment/5400760/+files/lp-1872118-groovy.debdiff -- 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: [SRU] DHCP Cluster crashes after a few hours Status in DHCP: New Status in bind9-libs package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in bind9-libs source package in Focal: In Progress Status in isc-dhcp source package in Focal: In Progress Status in bind9-libs source package in Groovy: In Progress Status in isc-dhcp source package in Groovy: In Progress Bug description: [Description] isc-dhcp-server uses libisc-export (coming from bind9-libs package) for handling the socket event(s) when configured in peer mode (master/secondary). It's possible that a sequence of messages dispatched by the master that requires acknowledgment from its peers holds a socket in a pending to send state, a timer or a subsequent write request can be scheduled into this socket and the !sock->pending_send assertion will be raised when trying to write again at the time data hasn't been flushed entirely and the pending_send flag hasn't been reset to 0 state. If this race condition happens, the following stacktrace will be hit: (gdb) info threads Id Target Id Frame * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait (futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52 3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, processes_to_wake=1, futex_word=) at ../sysdeps/nptl/futex-internal.h:364 4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable (private=, expected=0, futex_word=0x7fb4de6cd0d0) at ../sysdeps/nptl/futex-internal.h:183 (gdb) frame 2 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 (gdb) bt #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 #4 process_fd (writeable=, readable=, fd=11, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054 #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211 #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397 #7 0x7fb4dea68609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb4deba4103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) frame 3 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 4041 in ../../../../lib/isc/unix/socket.c (gdb) p sock->pending_send $2 = 1 [TEST CASE] 1) Install isc-dhcp-server in 2 focal machine(s). 2) Configure peer/cluster mode as follows: Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/ Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/ 2) Run dhcpd as follows in both machine(s) # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4 3) Leave the cluster running for a long (2h) period until the crash/race condition is reproduced. [REGRESSION POTENTIAL] * The fix will prevent the assertion to happen in the dispatch_send path, later versions of isch-dhcp upstream lack this logic and entirely removed the existence of this flag. Therefore, removing the need for this assertion at process_fd shouldn't be problematic. To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1872118/+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: [SRU] DHCP Cluster crashes after a few hours
Uploaded debdiff(s) for groovy and focal. This will require a follow up rebuild change for isc-dhcp, once the library change lands. -- 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: [SRU] DHCP Cluster crashes after a few hours Status in DHCP: New Status in bind9-libs package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in bind9-libs source package in Focal: In Progress Status in isc-dhcp source package in Focal: In Progress Status in bind9-libs source package in Groovy: In Progress Status in isc-dhcp source package in Groovy: In Progress Bug description: [Description] isc-dhcp-server uses libisc-export (coming from bind9-libs package) for handling the socket event(s) when configured in peer mode (master/secondary). It's possible that a sequence of messages dispatched by the master that requires acknowledgment from its peers holds a socket in a pending to send state, a timer or a subsequent write request can be scheduled into this socket and the !sock->pending_send assertion will be raised when trying to write again at the time data hasn't been flushed entirely and the pending_send flag hasn't been reset to 0 state. If this race condition happens, the following stacktrace will be hit: (gdb) info threads Id Target Id Frame * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait (futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52 3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, processes_to_wake=1, futex_word=) at ../sysdeps/nptl/futex-internal.h:364 4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable (private=, expected=0, futex_word=0x7fb4de6cd0d0) at ../sysdeps/nptl/futex-internal.h:183 (gdb) frame 2 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 (gdb) bt #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 #4 process_fd (writeable=, readable=, fd=11, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054 #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211 #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397 #7 0x7fb4dea68609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb4deba4103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) frame 3 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 4041 in ../../../../lib/isc/unix/socket.c (gdb) p sock->pending_send $2 = 1 [TEST CASE] 1) Install isc-dhcp-server in 2 focal machine(s). 2) Configure peer/cluster mode as follows: Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/ Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/ 2) Run dhcpd as follows in both machine(s) # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4 3) Leave the cluster running for a long (2h) period until the crash/race condition is reproduced. [REGRESSION POTENTIAL] * The fix will prevent the assertion to happen in the dispatch_send path, later versions of isch-dhcp upstream lack this logic and entirely removed the existence of this flag. Therefore, removing the need for this assertion at process_fd shouldn't be problematic. To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1872118/+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: [SRU] DHCP Cluster crashes after a few hours
** Description changed: + [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 + isc-dhcp-server uses libisc-export (coming from bin9-libs package) for handling the socket event(s) when configured in peer mode (master/secondary). It's possible that a sequence of messages dispatched by the master that requires acknowledgment from its peers holds a socket + in a pending to send state, a timer or a subsequent write request can be scheduled into this socket and the !sock->pending_send assertion + will be raised when trying to write again at the time data hasn't been flushed entirely and the pending_send flag hasn't been reset to 0 state. - https://bugs.launchpad.net/bugs/1870729 + If this race condition happens, the following stacktrace will be + hit: - However now one stops after a few hours with the following errors. One - can stay on line but not both. + (gdb) info threads + Id Target Id Frame + * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 + 2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait (futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52 + 3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, processes_to_wake=1, futex_word=) at ../sysdeps/nptl/futex-internal.h:364 + 4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable (private=, expected=0, futex_word=0x7fb4de6cd0d0) at ../sysdeps/nptl/futex-internal.h:183 + + (gdb) frame 2 + #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, + cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 + (gdb) bt + #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79 + #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, + cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 + #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 + #4 process_fd (writeable=, readable=, fd=11, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054 + #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211 + #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397 + #7 0x7fb4dea68609 in start_thread (arg=) at pthread_create.c:477 + #8 0x7fb4deba4103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 + + (gdb) frame 3 + #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 + 4041 in ../../../../lib/isc/unix/socket.c + (gdb) p sock->pending_send + $2 = 1 + + [TEST CASE] + + 1) Install isc-dhcp-server in 2 focal machine(s). + 2) Configure peer/cluster mode as follows: +Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/ +Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/ + 2) Run dhcpd as follows in both machine(s) + + # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4 + + 3) Leave the cluster running for a long (2h) period until the crash/race + condition is reproduced. + [REGRESSION POTENTIAL] - 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/dhc
[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours
** Summary changed: - DHCP Cluster crashes after a few hours + [SRU] DHCP Cluster crashes after a few hours -- 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: [SRU] DHCP Cluster crashes after a few hours Status in DHCP: New Status in bind9-libs package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in bind9-libs source package in Focal: In Progress Status in isc-dhcp source package in Focal: In Progress Status in bind9-libs source package in Groovy: In Progress Status in isc-dhcp source package in Groovy: In Progress 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: https://bugs.launchpad.net/dhcp/+bug/1872118/+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
** Changed in: bind9-libs (Ubuntu Focal) Status: New => In Progress ** Changed in: bind9-libs (Ubuntu Groovy) Status: New => In Progress ** Changed in: isc-dhcp (Ubuntu Focal) Status: New => In Progress ** Changed in: isc-dhcp (Ubuntu Groovy) Status: Confirmed => In Progress ** Changed in: bind9-libs (Ubuntu Focal) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) ** Changed in: bind9-libs (Ubuntu Groovy) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) ** Changed in: isc-dhcp (Ubuntu Focal) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) ** Changed in: isc-dhcp (Ubuntu Groovy) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) -- 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 DHCP: New Status in bind9-libs package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in bind9-libs source package in Focal: In Progress Status in isc-dhcp source package in Focal: In Progress Status in bind9-libs source package in Groovy: In Progress Status in isc-dhcp source package in Groovy: In Progress 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_
[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours
Hello @Andrew, @rlaager, Any crashes to report before I propose this patch? my env is running this patch for close to 3 days without any failures. Thanks, -- 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 DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: 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: https://bugs.launchpad.net/dhcp/+bug/1872118/+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
Hello Andrew, I just reviewed the core file that you provided. Thread 1 is the thread that panics on assertion because sock.pending_send is already set. This is the condition I prevented in the PPA, so *shouldn't* be hitting the frame 3 In my test systems I don't hit this condition, dispatch_send isn't called if pending_send is set. (gdb) thread 1 [Switching to thread 1 (Thread 0x7f39a41f5700 (LWP 18780))] #1 0x7f39a4dd1859 in __GI_abort () at abort.c:79 79 in abort.c (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7f39a4dd1859 in __GI_abort () at abort.c:79 #2 0x7f39a4faf985 in isc_assertion_failed (file=, line=, type=, cond=) at ../../../lib/isc/assertions.c:52 #3 0x7f39a4feb7e1 in dispatch_send (sock=0x7f39a4a03730) at ../../../../lib/isc/unix/socket.c:3380 #4 process_fd (writeable=, readable=, fd=0, manager=0x7f39a49fa010) at ../../../../lib/isc/unix/socket.c:4054 #5 process_fds (writefds=, readfds=0x16, maxfd=-1533038191, manager=0x7f39a49fa010) at ../../../../lib/isc/unix/socket.c:4211 #6 watcher (uap=0x7f39a49fa010) at ../../../../lib/isc/unix/socket.c:4397 [...] (gdb) frame 3 #3 0x7f39a4feb7e1 in dispatch_send (sock=0x7f39a4a03730) at ../../../../lib/isc/unix/socket.c:3380 3380../../../../lib/isc/unix/socket.c: No such file or directory. (gdb) info locals iev = 0x0 ev = sender = 0x2 iev = ev = sender = (gdb) p sock $1 = (isc__socket_t *) 0x7f39a4a03730 (gdb) p sock.pending_send $2 = 1 Can you check your library links, etc? ubuntu@dhcpd1:~$ ldd /usr/sbin/dhcpd | grep export libirs-export.so.161 => /lib/x86_64-linux-gnu/libirs-export.so.161 (0x7f5cb62e5000) libdns-export.so.1109 => /lib/x86_64-linux-gnu/libdns-export.so.1109 (0x7f5cb60b) libisc-export.so.1105 => /lib/x86_64-linux-gnu/libisc-export.so.1105 (0x7f5cb6039000) libisccfg-export.so.163 => /lib/x86_64-linux-gnu/libisccfg-export.so.163 (0x7f5cb5df5000) ubuntu@dhcpd1:~$ dpkg -S /lib/x86_64-linux-gnu/libisc-export.so.1105 libisc-export1105:amd64: /lib/x86_64-linux-gnu/libisc-export.so.1105 ubuntu@dhcpd1:~$ apt-cache policy libisc-export1105 | grep -i ppa Installed: 1:9.11.16+dfsg-3~ppa1 Candidate: 1:9.11.16+dfsg-3~ppa1 *** 1:9.11.16+dfsg-3~ppa1 500 500 http://ppa.launchpad.net/niedbalski/1872188-dbg/ubuntu focal/main amd64 Packages -- 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 DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: 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
[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours
OK, I have no crashes to report for the last 24 hours with the PPA included here. ● isc-dhcp-server.service - ISC DHCP IPv4 server Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-08-04 14:58:11 UTC; 1 day 1h ago Docs: man:dhcpd(8) Main PID: 1202 (dhcpd) Tasks: 5 (limit: 5882) Memory: 6.3M CGroup: /system.slice/isc-dhcp-server.service └─592 dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf root@dhcpd1:/home/ubuntu# dpkg -l | grep ppa1 ii isc-dhcp-server 4.4.1-2.1ubuntu6~ppa1 amd64 ISC DHCP server for automatic IP address assignment ii libirs-export161 1:9.11.16+dfsg-3~ppa1 amd64 Exported IRS Shared Library ii libisc-export1105:amd64 1:9.11.16+dfsg-3~ppa1 amd64 Exported ISC Shared Library ii libisccfg-export163 1:9.11.16+dfsg-3~ppa1 amd64 Exported ISC CFG Shared Library Andrew, what's the current version of libisc-export1105:amd64 installed in your system? can you provide a dpkg -l output and a systemctl status for the dhcpd service? Did you restarted/killed the dhcpd processes after upgrading that library? Thanks in advance. -- 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 DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: 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
[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours
Andrew, Thank you for your input. ** Do you have any logs or a crash report to take a look after you upgraded these systems? On my test lab , I am counting for 3+ hours without a crash. root@dhcpd1:/home/ubuntu# dpkg -l | grep ppa1 ii isc-dhcp-server4.4.1-2.1ubuntu6~ppa1 amd64 ISC DHCP server for automatic IP address assignment ii libirs-export161 1:9.11.16+dfsg-3~ppa1 amd64 Exported IRS Shared Library ii libisc-export1105:amd641:9.11.16+dfsg-3~ppa1 amd64 Exported ISC Shared Library ii libisccfg-export1631:9.11.16+dfsg-3~ppa1 amd64 Exported ISC CFG Shared Library --- DHCPACK on 10.19.101.120 to 52:54:00:d1:eb:66 (sleek-kodiak) via ens4 balancing pool 555643e55f40 12 total 221 free 111 backup 110 lts 0 max-own (+/-)22 balanced pool 555643e55f40 12 total 221 free 111 backup 110 lts 0 max-misbal 33 balancing pool 555643e55f40 12 total 221 free 111 backup 110 lts 0 max-own (+/-)22 balanced pool 555643e55f40 12 total 221 free 111 backup 110 lts 0 max-misbal 33 --- balancing pool 5595dff0df10 12 total 221 free 111 backup 110 lts 0 max-own (+/-)22 balanced pool 5595dff0df10 12 total 221 free 111 backup 110 lts 0 max-misbal 33 balancing pool 5595dff0df10 12 total 221 free 111 backup 110 lts 0 max-own (+/-)22 balanced pool 5595dff0df10 12 total 221 free 111 backup 110 lts 0 max-misbal 33 --- -- 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 DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: 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:
[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours
Hello Andrew, Correct me if I am wrong but it seems your system isn't running with libisc-export1105:amd64 1:9.11.16+dfsg-3~ppa1 (?) I am running the following packages from the PPA, please note that libisc-export1105 is required (that's where the fix is located). root@dhcpd1:/home/ubuntu# dpkg -l | grep ppa1 ii isc-dhcp-server 4.4.1-2.1ubuntu6~ppa1 amd64 ISC DHCP server for automatic IP address assignment ii libirs-export161 1:9.11.16+dfsg-3~ppa1 amd64 Exported IRS Shared Library ii libisc-export1105:amd64 1:9.11.16+dfsg-3~ppa1 amd64 Exported ISC Shared Library ii libisccfg-export163 1:9.11.16+dfsg-3~ppa1 amd64 Exported ISC CFG Shared Library --- Sent update done message to failover-partner failover peer failover-partner: peer moves from recover to recover-done failover peer failover-partner: peer update completed. failover peer failover-partner: I move from recover to recover-done failover peer failover-partner: peer moves from recover-done to normal failover peer failover-partner: I move from recover-done to normal failover peer failover-partner: Both servers normal balancing pool 55d0a88a4f10 12 total 221 free 221 backup 0 lts -110 max-own (+/-)22 balanced pool 55d0a88a4f10 12 total 221 free 221 backup 0 lts -110 max-misbal 33 --- balanced pool 55eb2fe58f40 12 total 221 free 111 backup 110 lts 0 max-misbal 33 Sending updates to failover-partner. failover peer failover-partner: peer moves from recover-done to normal failover peer failover-partner: Both servers normal --- DHCPDISCOVER from 52:54:00:d1:eb:66 via ens4: load balance to peer failover-partner DHCPREQUEST for 10.19.101.120 (10.19.101.233) from 52:54:00:d1:eb:66 via ens4: lease owned by peer On failover: peer failover-partner: disconnected failover peer failover-partner: I move from normal to communications-interrupted DHCPDISCOVER from 52:54:00:e8:14:0a via ens4 DHCPOFFER on 10.19.101.10 to 52:54:00:e8:14:0a (shapely-peccary) via ens4 DHCPREQUEST for 10.19.101.10 (10.19.101.127) from 52:54:00:e8:14:0a (shapely-peccary) via ens4 DHCPACK on 10.19.101.10 to 52:54:00:e8:14:0a (shapely-peccary) via ens4 I'll leave this running until I can reproduce the crash or assume that the fix works. Please let me know if you can reproduce with those packages. Thanks, Jorge Niedbalski -- 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 DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: 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: 68
[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours
Hello Andrew, The fix is on the libisc-export1105 library (check dependencies on: https://launchpad.net/~niedbalski/+archive/ubuntu/fix-1872118/+packages), just replacing the dhcpd binary won't be enough. If you can install isc-dhcp-server and its dependencies from the PPA and test, would be great. Thanks for any feedback. -- 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 DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: 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: https://bugs.launchpad.net/dhcp/+bug/1872118/+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
** Follow up from my previous comment, I've built a PPA with a fix similar to the one pointed in 430065. https://launchpad.net/~niedbalski/+archive/ubuntu/fix-1872118 * I'd appreciate if anyone can test that PPA with focal and report back if the problem keeps reproducible with that version. In case it does, please upload the crash file / coredump and the configuration file used. Thank you. -- 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 DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: 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: https://bugs.launchpad.net/dhcp/+bug/1872118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages M
[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours
Hello, I checked the backtrace of a crashed dhcpd running on 4.4.1-2.1ubuntu5. (gdb) info threads Id Target Id Frame * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait (futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52 3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, processes_to_wake=1, futex_word=) at ../sysdeps/nptl/futex-internal.h:364 4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable (private=, expected=0, futex_word=0x7fb4de6cd0d0) at ../sysdeps/nptl/futex-internal.h:183 (gdb) frame 2 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 (gdb) bt #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 #4 process_fd (writeable=, readable=, fd=11, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054 #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211 #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397 #7 0x7fb4dea68609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb4deba4103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) frame 3 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 4041 in ../../../../lib/isc/unix/socket.c (gdb) p sock->pending_send $2 = 1 The code is crashing on this assertion: https://gitlab.isc.org/isc-projects/bind9/-/blob/v9_11_3/lib/isc/unix/socket.c#L3364 This was already reported and marked as fixed in debian (?) via [0] ""Now if a wakeup event occurres the socket would be dispatched for processing regardless which kind of event (timer?) triggered the wakeup. At least I did not find any sanity checks in process_fds() except SOCK_DEAD(sock). This leads to the following situation: The sock is not dead yet but it is still pending when it is dispatched again. I would now check sock->pending_send before calling dispatch_send().This would at least prevent the assertion failure - well knowing that the situation described above ( not dead but still pending and alerting ) is not a very pleasant one - until someone comes up with a better solution. """ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430065#20 ** Follow up questions: 0) The reproducer doesn't seems consistent and seems to be related to a race condition associated with a internal timer/futex. 1) Can anyone confirm that a pristine upstream 4.4.1 doesn't reproduces the issue? ** Bug watch added: Debian Bug tracker #430065 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430065 -- 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 DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: 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: /u
[Touch-packages] [Bug 1888926] Re: tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0
Hello, I checked the backtrace of a crashed dhcpd running on 4.4.1-2.1ubuntu5. (gdb) info threads Id Target IdFrame * 1Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 2Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait (futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52 3Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, processes_to_wake=1, futex_word=) at ../sysdeps/nptl/futex-internal.h:364 4Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable (private=, expected=0, futex_word=0x7fb4de6cd0d0) at ../sysdeps/nptl/futex-internal.h:183 (gdb) frame 2 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 (gdb) bt #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 #4 process_fd (writeable=, readable=, fd=11, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054 #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211 #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397 #7 0x7fb4dea68609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb4deba4103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) frame 3 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 4041in ../../../../lib/isc/unix/socket.c (gdb) p sock->pending_send $2 = 1 The code is crashing on this assertion: https://gitlab.isc.org/isc-projects/bind9/-/blob/v9_11_3/lib/isc/unix/socket.c#L3364 This was already reported and marked as fixed in debian (?) via [0] ""Now if a wakeup event occurres the socket would be dispatched for processing regardless which kind of event (timer?) triggered the wakeup. At least I did not find any sanity checks in process_fds() except SOCK_DEAD(sock). This leads to the following situation: The sock is not dead yet but it is still pending when it is dispatched again. I would now check sock->pending_send before calling dispatch_send().This would at least prevent the assertion failure - well knowing that the situation described above ( not dead but still pending and alerting ) is not a very pleasant one - until someone comes up with a better solution. """ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430065#20 ** Follow up questions: 0) The reproducer doesn't seems consistent and seems to be related to a race condition associated with a internal timer/futex. 1) Can anyone confirm that a pristine upstream 4.4.1 doesn't reproduces the issue? ** Bug watch added: Debian Bug tracker #430065 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430065 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1888926 Title: tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0 Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Focal: In Progress Status in rsyslog source package in Groovy: Fix Released Bug description: [Description] Problem is according to https://launchpad.net/ubuntu/+source/librelp/+publishinghistory, librelp-dev 1.5.0 was published into focal at 2020-04-21, but reverse dependencies (such as rsyslog) weren't rebuilt after this new version was published # dpkg -l | grep librelp ii librelp-dev:amd64 1.5.0-1ubuntu2 amd64 Reliable Event Logging Protocol (RELP) library - development files ii librelp0:amd64 1.5.0-1ubuntu2 amd64 Reliable Event Logging Protocol (RELP) library rsyslogd: error during parsing file /etc/rsyslog.d/FILENAME.conf, on or before line 22: imrelp: librelp does not support input parameter 'tls.tlscfgcmd'; it probably is too old (1.5.0 or higher should be fine); ignoring setting now. [v8.2001.0 try https://www.rsyslog.com/e/2207 ] [Reproducer] Setup a focal machine with rsyslog, using the following configuration: module(load="imrelp" tls.tlslib="openssl") input( type="imrelp" port="2515" tls="on" # This should work in rsyslog 8.2006.0: #tls.mycert="/etc/rsyslog.tls/fullchain.pem" # for now we use the work-around discussed in: # https://github.com/rsyslog/rsyslog/issues/4360 tls.cacert="/etc/rsyslog.
[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours
** Also affects: isc-dhcp (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Also affects: isc-dhcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: bind9-libs (Ubuntu) Importance: Undecided Status: New -- 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 DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: 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: https://bugs.launchpad.net/dhcp/+bug/1872118/+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
Hello, I am trying to setup a reproducer for the mentioned issue. I have 2 machines acting as peers with the following versions: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal # dpkg -l |grep -i isc-dh ii isc-dhcp-client4.4.1-2.1ubuntu5 amd64 DHCP client for automatically obtaining an IP address ii isc-dhcp-common4.4.1-2.1ubuntu5 amd64 common manpages relevant to all of the isc-dhcp packages ii isc-dhcp-server4.4.1-2.1ubuntu5 amd64 ISC DHCP server for automatic IP address assignment = Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/ Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/ Started with: # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4 ---> Raised some DHCP requests to these servers. balanced pool 560b8c263f40 12 total 221 free 111 backup 110 lts 0 max-misbal 33 Sending updates to failover-partner. failover peer failover-partner: peer moves from recover-done to normal failover peer failover-partner: Both servers normal DHCPDISCOVER from 52:54:00:2d:53:93 via ens4 DHCPOFFER on 10.19.101.120 to 52:54:00:2d:53:93 (glistening-elephant) via ens4 DHCPREQUEST for 10.19.101.120 (10.19.101.236) from 52:54:00:2d:53:93 (glistening-elephant) via ens4 DHCPACK on 10.19.101.120 to 52:54:00:2d:53:93 (glistening-elephant) via ens4 DHCPREQUEST for 10.19.101.120 from 52:54:00:2d:53:93 (glistening-elephant) via ens4 DHCPACK on 10.19.101.120 to 52:54:00:2d:53:93 (glistening-elephant) via ens4 DHCPREQUEST for 10.19.101.121 from 52:54:00:53:a3:d8 (valiant-motmot) via ens4 DHCPACK on 10.19.101.121 to 52:54:00:53:a3:d8 (valiant-motmot) via ens4 --- failover peer failover-partner: Both servers normal balancing pool 5606b2c95f10 12 total 221 free 221 backup 0 lts -110 max-own (+/-)22 balanced pool 5606b2c95f10 12 total 221 free 221 backup 0 lts -110 max-misbal 33 balancing pool 5606b2c95f10 12 total 221 free 111 backup 110 lts 0 max-own (+/-)22 balanced pool 5606b2c95f10 12 total 221 free 111 backup 110 lts 0 max-misbal 33 DHCPDISCOVER from 52:54:00:2d:53:93 via ens4: load balance to peer failover-partner DHCPREQUEST for 10.19.101.120 (10.19.101.236) from 52:54:00:2d:53:93 via ens4: lease owned by peer So far (after 1.5h) no crash has been reported in any of the servers. Questions: 1) Anything missed from the provided configuration? 2) Is this load or concurrency related? meaning a specific amount of leases needs to be allocated for this crash to happen? I will take a look to an existing crash/coredump. -- 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 DHCP: New 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'
[Touch-packages] [Bug 1888926] Re: tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0
** Patch added: "lp1888926-focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1888926/+attachment/5398376/+files/lp1888926-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1888926 Title: tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0 Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Focal: In Progress Status in rsyslog source package in Groovy: Fix Released Bug description: [Description] Problem is according to https://launchpad.net/ubuntu/+source/librelp/+publishinghistory, librelp-dev 1.5.0 was published into focal at 2020-04-21, but reverse dependencies (such as rsyslog) weren't rebuilt after this new version was published # dpkg -l | grep librelp ii librelp-dev:amd64 1.5.0-1ubuntu2 amd64 Reliable Event Logging Protocol (RELP) library - development files ii librelp0:amd64 1.5.0-1ubuntu2 amd64 Reliable Event Logging Protocol (RELP) library rsyslogd: error during parsing file /etc/rsyslog.d/FILENAME.conf, on or before line 22: imrelp: librelp does not support input parameter 'tls.tlscfgcmd'; it probably is too old (1.5.0 or higher should be fine); ignoring setting now. [v8.2001.0 try https://www.rsyslog.com/e/2207 ] [Reproducer] Setup a focal machine with rsyslog, using the following configuration: module(load="imrelp" tls.tlslib="openssl") input( type="imrelp" port="2515" tls="on" # This should work in rsyslog 8.2006.0: #tls.mycert="/etc/rsyslog.tls/fullchain.pem" # for now we use the work-around discussed in: # https://github.com/rsyslog/rsyslog/issues/4360 tls.cacert="/etc/rsyslog.tls/chain.pem" tls.mycert="/etc/rsyslog.tls/cert.pem" tls.myprivkey="/etc/rsyslog.tls/privkey.pem" tls.tlscfgcmd="ServerPreference CipherString=ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 Ciphersuites=TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384 MinProtocol=TLSv1.2" ) This error comes from this code in plugins/imrelp/imrelp.c: #if defined(HAVE_RELPENGINESETTLSCFGCMD) inst->tlscfgcmd = (uchar*)es_str2cstr(pvals[i].val.d.estr, NULL); #else parser_errmsg("imrelp: librelp does not support input parameter 'tls.tlscfgcmd'; " "it probably is too old (1.5.0 or higher should be fine); ignoring setting now."); #endif The build log for focal: https://launchpadlibrarian.net/464665610/buildlog_ubuntu-focal-arm64.rsyslog_8.2001.0-1ubuntu1_BUILDING.txt.gz says: checking for relpSrvSetTlsConfigCmd... no checking for relpSrvSetTlsConfigCmd... (cached) no The build log for groovy: https://launchpadlibrarian.net/486409321/buildlog_ubuntu-groovy-arm64.rsyslog_8.2006.0-2ubuntu1_BUILDING.txt.gz says: checking for relpSrvSetTlsConfigCmd... yes checking for relpSrvSetTlsConfigCmd... (cached) yes If I rebuild the rsyslog package, I get: checking for relpSrvSetTlsConfigCmd... yes checking for relpSrvSetTlsConfigCmd... (cached) yes I suspect that the rsyslog package was built against and older librelp version. A simple rebuild of rsyslog should fix this, though a more complete fix would be to raise the Build-Depends from librelp-dev (>= 1.4.0) to librelp-dev (>= 1.5.0). [Risk potential] * No identified as this is a rebuild that should have been done on all reverse dependencies of librelp-dev when upgraded from 1.4.0 to 1.5.0 [Fix] Provide a rebuild SRU for focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1888926/+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 1888926] Re: tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0
** Tags added: sts-sru-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1888926 Title: tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0 Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Focal: In Progress Status in rsyslog source package in Groovy: Fix Released Bug description: [Description] Problem is according to https://launchpad.net/ubuntu/+source/librelp/+publishinghistory, librelp-dev 1.5.0 was published into focal at 2020-04-21, but reverse dependencies (such as rsyslog) weren't rebuilt after this new version was published # dpkg -l | grep librelp ii librelp-dev:amd64 1.5.0-1ubuntu2 amd64 Reliable Event Logging Protocol (RELP) library - development files ii librelp0:amd64 1.5.0-1ubuntu2 amd64 Reliable Event Logging Protocol (RELP) library rsyslogd: error during parsing file /etc/rsyslog.d/FILENAME.conf, on or before line 22: imrelp: librelp does not support input parameter 'tls.tlscfgcmd'; it probably is too old (1.5.0 or higher should be fine); ignoring setting now. [v8.2001.0 try https://www.rsyslog.com/e/2207 ] [Reproducer] Setup a focal machine with rsyslog, using the following configuration: module(load="imrelp" tls.tlslib="openssl") input( type="imrelp" port="2515" tls="on" # This should work in rsyslog 8.2006.0: #tls.mycert="/etc/rsyslog.tls/fullchain.pem" # for now we use the work-around discussed in: # https://github.com/rsyslog/rsyslog/issues/4360 tls.cacert="/etc/rsyslog.tls/chain.pem" tls.mycert="/etc/rsyslog.tls/cert.pem" tls.myprivkey="/etc/rsyslog.tls/privkey.pem" tls.tlscfgcmd="ServerPreference CipherString=ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 Ciphersuites=TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384 MinProtocol=TLSv1.2" ) This error comes from this code in plugins/imrelp/imrelp.c: #if defined(HAVE_RELPENGINESETTLSCFGCMD) inst->tlscfgcmd = (uchar*)es_str2cstr(pvals[i].val.d.estr, NULL); #else parser_errmsg("imrelp: librelp does not support input parameter 'tls.tlscfgcmd'; " "it probably is too old (1.5.0 or higher should be fine); ignoring setting now."); #endif The build log for focal: https://launchpadlibrarian.net/464665610/buildlog_ubuntu-focal-arm64.rsyslog_8.2001.0-1ubuntu1_BUILDING.txt.gz says: checking for relpSrvSetTlsConfigCmd... no checking for relpSrvSetTlsConfigCmd... (cached) no The build log for groovy: https://launchpadlibrarian.net/486409321/buildlog_ubuntu-groovy-arm64.rsyslog_8.2006.0-2ubuntu1_BUILDING.txt.gz says: checking for relpSrvSetTlsConfigCmd... yes checking for relpSrvSetTlsConfigCmd... (cached) yes If I rebuild the rsyslog package, I get: checking for relpSrvSetTlsConfigCmd... yes checking for relpSrvSetTlsConfigCmd... (cached) yes I suspect that the rsyslog package was built against and older librelp version. A simple rebuild of rsyslog should fix this, though a more complete fix would be to raise the Build-Depends from librelp-dev (>= 1.4.0) to librelp-dev (>= 1.5.0). [Risk potential] * No identified as this is a rebuild that should have been done on all reverse dependencies of librelp-dev when upgraded from 1.4.0 to 1.5.0 [Fix] Provide a rebuild SRU for focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1888926/+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 1888926] Re: tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0
mple rebuild of rsyslog should fix this, though a more complete fix would be to raise the Build-Depends from librelp-dev (>= 1.4.0) to librelp-dev (>= 1.5.0). + + [Risk potential] + + * No identified as this is a rebuild that should have been done on all + reverse dependencies of librelp-dev when upgraded from 1.4.0 to 1.5.0 + + + [Fix] + + Provide a rebuild SRU for focal. ** Changed in: rsyslog (Ubuntu Groovy) Status: New => Fix Released ** Changed in: rsyslog (Ubuntu Focal) Status: New => In Progress ** Changed in: rsyslog (Ubuntu Focal) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) ** Changed in: rsyslog (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1888926 Title: tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0 Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Focal: In Progress Status in rsyslog source package in Groovy: Fix Released Bug description: [Description] Problem is according to https://launchpad.net/ubuntu/+source/librelp/+publishinghistory, librelp-dev 1.5.0 was published into focal at 2020-04-21, but reverse dependencies (such as rsyslog) weren't rebuilt after this new version was published # dpkg -l | grep librelp ii librelp-dev:amd64 1.5.0-1ubuntu2 amd64 Reliable Event Logging Protocol (RELP) library - development files ii librelp0:amd64 1.5.0-1ubuntu2 amd64 Reliable Event Logging Protocol (RELP) library rsyslogd: error during parsing file /etc/rsyslog.d/FILENAME.conf, on or before line 22: imrelp: librelp does not support input parameter 'tls.tlscfgcmd'; it probably is too old (1.5.0 or higher should be fine); ignoring setting now. [v8.2001.0 try https://www.rsyslog.com/e/2207 ] [Reproducer] Setup a focal machine with rsyslog, using the following configuration: module(load="imrelp" tls.tlslib="openssl") input( type="imrelp" port="2515" tls="on" # This should work in rsyslog 8.2006.0: #tls.mycert="/etc/rsyslog.tls/fullchain.pem" # for now we use the work-around discussed in: # https://github.com/rsyslog/rsyslog/issues/4360 tls.cacert="/etc/rsyslog.tls/chain.pem" tls.mycert="/etc/rsyslog.tls/cert.pem" tls.myprivkey="/etc/rsyslog.tls/privkey.pem" tls.tlscfgcmd="ServerPreference CipherString=ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 Ciphersuites=TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384 MinProtocol=TLSv1.2" ) This error comes from this code in plugins/imrelp/imrelp.c: #if defined(HAVE_RELPENGINESETTLSCFGCMD) inst->tlscfgcmd = (uchar*)es_str2cstr(pvals[i].val.d.estr, NULL); #else parser_errmsg("imrelp: librelp does not support input parameter 'tls.tlscfgcmd'; " "it probably is too old (1.5.0 or higher should be fine); ignoring setting now."); #endif The build log for focal: https://launchpadlibrarian.net/464665610/buildlog_ubuntu-focal-arm64.rsyslog_8.2001.0-1ubuntu1_BUILDING.txt.gz says: checking for relpSrvSetTlsConfigCmd... no checking for relpSrvSetTlsConfigCmd... (cached) no The build log for groovy: https://launchpadlibrarian.net/486409321/buildlog_ubuntu-groovy-arm64.rsyslog_8.2006.0-2ubuntu1_BUILDING.txt.gz says: checking for relpSrvSetTlsConfigCmd... yes checking for relpSrvSetTlsConfigCmd... (cached) yes If I rebuild the rsyslog package, I get: checking for relpSrvSetTlsConfigCmd... yes checking for relpSrvSetTlsConfigCmd... (cached) yes I suspect that the rsyslog package was built against and older librelp version. A simple rebuild of rsyslog should fix this, though a more complete fix would be to raise the Build-Depends from librelp-dev (>= 1.4.0) to librelp-dev (>= 1.5.0). [Risk potential] * No identified as this is a rebuild that should have been done on all reverse dependencies of librelp-dev when upgraded from 1.4.0 to 1.5.0 [Fix] Provide a rebuild SRU for focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1888926/+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 1888926] Re: tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0
** Also affects: rsyslog (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: rsyslog (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 rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1888926 Title: tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0 Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Focal: New Status in rsyslog source package in Groovy: New Bug description: rsyslogd: error during parsing file /etc/rsyslog.d/FILENAME.conf, on or before line 22: imrelp: librelp does not support input parameter 'tls.tlscfgcmd'; it probably is too old (1.5.0 or higher should be fine); ignoring setting now. [v8.2001.0 try https://www.rsyslog.com/e/2207 ] Here is the config: module(load="imrelp" tls.tlslib="openssl") input( type="imrelp" port="2515" tls="on" # This should work in rsyslog 8.2006.0: #tls.mycert="/etc/rsyslog.tls/fullchain.pem" # for now we use the work-around discussed in: # https://github.com/rsyslog/rsyslog/issues/4360 tls.cacert="/etc/rsyslog.tls/chain.pem" tls.mycert="/etc/rsyslog.tls/cert.pem" tls.myprivkey="/etc/rsyslog.tls/privkey.pem" tls.tlscfgcmd="ServerPreference CipherString=ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 Ciphersuites=TLS_AES_128_GCM_SHA256:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384 MinProtocol=TLSv1.2" ) This error comes from this code in plugins/imrelp/imrelp.c: #if defined(HAVE_RELPENGINESETTLSCFGCMD) inst->tlscfgcmd = (uchar*)es_str2cstr(pvals[i].val.d.estr, NULL); #else parser_errmsg("imrelp: librelp does not support input parameter 'tls.tlscfgcmd'; " "it probably is too old (1.5.0 or higher should be fine); ignoring setting now."); #endif The build log for focal: https://launchpadlibrarian.net/464665610/buildlog_ubuntu-focal-arm64.rsyslog_8.2001.0-1ubuntu1_BUILDING.txt.gz says: checking for relpSrvSetTlsConfigCmd... no checking for relpSrvSetTlsConfigCmd... (cached) no The build log for groovy: https://launchpadlibrarian.net/486409321/buildlog_ubuntu-groovy-arm64.rsyslog_8.2006.0-2ubuntu1_BUILDING.txt.gz says: checking for relpSrvSetTlsConfigCmd... yes checking for relpSrvSetTlsConfigCmd... (cached) yes If I rebuild the rsyslog package, I get: checking for relpSrvSetTlsConfigCmd... yes checking for relpSrvSetTlsConfigCmd... (cached) yes I suspect that the rsyslog package was built against and older librelp version. A simple rebuild of rsyslog should fix this, though a more complete fix would be to raise the Build-Depends from librelp-dev (>= 1.4.0) to librelp-dev (>= 1.5.0). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1888926/+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 1886835] Re: crashes to login screen, uvc related stuff blinks on console
After a new reboot I can no longer reproduce this. ** Changed in: lightdm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1886835 Title: crashes to login screen, uvc related stuff blinks on console Status in lightdm package in Ubuntu: Invalid Bug description: I started getting random crashes to login screen, about twice a day. When crashes I briefly see some logging output to screen mentioning "UVC Control" or uvcview. I'm not using the webcam when the system crashes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-61-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jul 8 11:55:34 2020 InstallationDate: Installed on 2020-02-12 (146 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1886835/+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 1886835] Re: crashes to login screen, uvc related stuff blinks on console
I caught the console message on camera: uvcvideo: Failed to query (GET_INFO) UVC control 15 on unit 1: -32 (exp. 1). Googling around it seems this is a pretty spammy message, perhaps it is unrelated to what is actually happening. I can reproduce this crash putting my system under stress, opening a lot of programs and making it swap. At some point it starts stuttering, then crashes. It happens before the swap space is depleted, about 30% of a 2GB swap partition. It's a ThinkPad X1 laptop with SSD. ** Attachment added: "Screenshot_20200710-153131.png" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1886835/+attachment/5391439/+files/Screenshot_20200710-153131.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1886835 Title: crashes to login screen, uvc related stuff blinks on console Status in lightdm package in Ubuntu: New Bug description: I started getting random crashes to login screen, about twice a day. When crashes I briefly see some logging output to screen mentioning "UVC Control" or uvcview. I'm not using the webcam when the system crashes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-61-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jul 8 11:55:34 2020 InstallationDate: Installed on 2020-02-12 (146 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1886835/+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 1886835] Re: crashes to login screen, uvc related stuff blinks on console
Also, this is the very last thing I see on dmesg just after relogging: ``` [469698.684830] Bluetooth: hci0: Hardware error 0x0a [469698.694845] Bluetooth: hci0: Retrieving Intel exception info failed (-16) [469698.795777] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [469698.795781] debugfs: File 'le_max_key_size' in directory 'hci0' already present! ``` (might be unrelated? I have a bluetooth mouse and nothing else) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1886835 Title: crashes to login screen, uvc related stuff blinks on console Status in lightdm package in Ubuntu: New Bug description: I started getting random crashes to login screen, about twice a day. When crashes I briefly see some logging output to screen mentioning "UVC Control" or uvcview. I'm not using the webcam when the system crashes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-61-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jul 8 11:55:34 2020 InstallationDate: Installed on 2020-02-12 (146 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1886835/+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 1886835] [NEW] crashes to login screen, uvc related stuff blinks on console
Public bug reported: I started getting random crashes to login screen, about twice a day. When crashes I briefly see some logging output to screen mentioning "UVC Control" or uvcview. I'm not using the webcam when the system crashes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-61-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jul 8 11:55:34 2020 InstallationDate: Installed on 2020-02-12 (146 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1886835 Title: crashes to login screen, uvc related stuff blinks on console Status in lightdm package in Ubuntu: New Bug description: I started getting random crashes to login screen, about twice a day. When crashes I briefly see some logging output to screen mentioning "UVC Control" or uvcview. I'm not using the webcam when the system crashes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-61-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jul 8 11:55:34 2020 InstallationDate: Installed on 2020-02-12 (146 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1886835/+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 1855350] Re: Will not logout or shutdown from guest-session
** Summary changed: - Will not logout or shutdown form guest-session + Will not logout or shutdown from guest-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1855350 Title: Will not logout or shutdown from guest-session Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: This is in Xubuntu 19.10, a regression from 18.04. xfce4-session 4.14.0-0ubuntu1. I enabled guest-session and logged in that. But there I can not log out or even shut down using the graphical way at least unless put Action Buttons on the panel and choose Switch User. If I run "xfce4-session-logout -l" I get error dialog saying: Received error while trying to log out GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs:Type of message, "(yb)", does not match expected type"(b)" And in standard output there is: "Received error while trying to log out, error was GDBus.Error:org.xfce.SessionManager.Error.Failed: Session manager must be in idle state when requesting a shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1855350/+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 1882849] [NEW] Doesn't send dhcpv6 request
Public bug reported: I'm using network-manager 1.22.10-1ubuntu2.1 in Ubuntu Focal 20.04. After a connection the internal dhcp doesn't send request to dhcpv6 server. All options in NM are default. IPv4 is ok. Using tcpdump I can see the packages: 17:47:38.428145 IP6 fe80::426e:5cc5:ab6b:e126.546 > ff02::1:2.547: dhcp6 solicit 17:47:38.428902 IP6 fe80::20e:1eff:fe7a:9ed0.547 > fe80::426e:5cc5:ab6b:e126.546: dhcp6 advertise After dhcp6 advertise the NM doesn't send any request. After some seconds I can see a timeout on logs. NetworkManager[3803]: [1591735670.9313] dhcp6 (eno1): request timed out NetworkManager[3803]: [1591735670.9314] dhcp6 (eno1): state changed unknown -> timeout As man says, we can change the dhcp client. If I change /etc/NetworkManager/NetworkManager.conf adding [main] dhcp=dhclient so everything works nice. I think there is some problem with the internal dhcp client of NetworkManager. Tks ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1882849 Title: Doesn't send dhcpv6 request Status in network-manager package in Ubuntu: New Bug description: I'm using network-manager 1.22.10-1ubuntu2.1 in Ubuntu Focal 20.04. After a connection the internal dhcp doesn't send request to dhcpv6 server. All options in NM are default. IPv4 is ok. Using tcpdump I can see the packages: 17:47:38.428145 IP6 fe80::426e:5cc5:ab6b:e126.546 > ff02::1:2.547: dhcp6 solicit 17:47:38.428902 IP6 fe80::20e:1eff:fe7a:9ed0.547 > fe80::426e:5cc5:ab6b:e126.546: dhcp6 advertise After dhcp6 advertise the NM doesn't send any request. After some seconds I can see a timeout on logs. NetworkManager[3803]: [1591735670.9313] dhcp6 (eno1): request timed out NetworkManager[3803]: [1591735670.9314] dhcp6 (eno1): state changed unknown -> timeout As man says, we can change the dhcp client. If I change /etc/NetworkManager/NetworkManager.conf adding [main] dhcp=dhclient so everything works nice. I think there is some problem with the internal dhcp client of NetworkManager. Tks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1882849/+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 280533] Re: procps failed to install/upgrade :unable to make backup link of `./bin/ps' before installing new version: Operation not permitted
The command that allowed it for me was: chattr -sia /bin/ps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/280533 Title: procps failed to install/upgrade :unable to make backup link of `./bin/ps' before installing new version: Operation not permitted Status in procps package in Ubuntu: Invalid Bug description: Binary package hint: procps When I install new packages, I get the following error message: E: /var/cache/apt/archives/procps_1%3a3.2.7-5ubuntu3_amd64.deb: unable to make backup link of `./bin/ps' before installing new version ProblemType: Package Architecture: amd64 Date: Wed Oct 8 22:35:55 2008 DistroRelease: Ubuntu 8.04 ErrorMessage: unable to make backup link of `./bin/ps' before installing new version Package: procps 1:3.2.7-5ubuntu3 [modified: bin/ps usr/bin/top] PackageArchitecture: amd64 SourcePackage: procps Title: package procps 1:3.2.7-5ubuntu3 [modified: bin/ps usr/bin/top] failed to install/upgrade: unable to make backup link of `./bin/ps' before installing new version Uname: Linux 2.6.24-20-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/280533/+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 1385245] Re: Beats Studio wireless bluetooth headphones wont pair w/ ubuntu 14.04
Hello, I would like to confirm that this issue is also present on the lastest ubuntu release. I try to connect Beats Studio 3 in different ways and it doesn't connect. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1385245 Title: Beats Studio wireless bluetooth headphones wont pair w/ ubuntu 14.04 Status in blueman package in Ubuntu: Won't Fix Status in bluez package in Ubuntu: Won't Fix Bug description: I have Beats Studio wireless bluetooth headphones and when adding device (pair bluetooth device) it wont pair w/ ubuntu 14.04 system. Closest thing I've found is this: https://code.google.com/p/chromium/issues/detail?id=379126 It looks like it's working on ChromeOS so I'm hoping it's possible it will work w/ ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1385245/+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
** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** This bug is no longer a duplicate of bug 1818527 Stub resolver cache is corrupted -- 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: Confirmed Status in systemd source package in Bionic: New Status in systemd source package in Disco: New Status in systemd source package in Eoan: New Status in systemd source package in Focal: Confirmed 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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived clusters
For reference: https://github.com/systemd/systemd/pull/12511 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815101 Title: [master] Restarting systemd-networkd breaks keepalived clusters Status in netplan: Invalid Status in keepalived package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Bug description: Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses obfuscated) global_defs # Block id { notification_email { sysadm...@blah.com } notification_email_from keepali...@system3.hq.blah.com smtp_server 10.22.11.7 # IP smtp_connect_timeout 30 # integer, seconds router_id system3 # string identifying the machine, # (doesn't have to be hostname). vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18 vrrp_mcast_group6 ff02::12 # optional, default ff02::12 enable_traps # enable SNMP traps } vrrp_sync_group collection { group { wan lan phone } vrrp_instance wan { state MASTER interface eth2 virtual_router_id 77 priority 150 advert_int 1 smtp_alert authentication { auth_type PASS auth_pass BlahBlah } virtual_ipaddress { 12.13.14.20 } } vrrp_instance lan { state MASTER interface eth3 virtual_router_id 78 priority 150 advert_int 1 smtp_alert authentication { auth_type PASS auth_pass MoreBlah } virtual_ipaddress { 10.22.11.13/24 } } vrrp_instance phone { state MASTER interface eth4 virtual_router_id 79 priority 150 advert_int 1 smtp_alert authentication { auth_type PASS auth_pass MostBlah } virtual_ipaddress { 10.22.14.3/24 } } At boot the affected interfaces have: 5: eth4: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ab:cd:ef:90:c0:e3 brd ff:ff:ff:ff:ff:ff inet 10.22.14.6/24 brd 10.22.14.255 scope global eth4 valid_lft forever preferred_lft forever inet 10.22.14.3/24 scope global secondary eth4 valid_lft forever preferred_lft forever inet6 fe80::ae1f:6bff:fe90:c0e3/64 scope link valid_lft forever preferred_lft forever 7: eth3: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ab:cd:ef:b0:26:29 brd ff:ff:ff:ff:ff:ff inet 10.22.11.6/24 brd 10.22.11.255 scope global eth3 valid_lft forever preferred_lft forever inet 10.22.11.13/24 scope global secondary eth3 valid_lft forever preferred_lft forever inet6 fe80::ae1f:6bff:feb0:2629/64 scope link valid_lft forever preferred_lft forever 9: eth2: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ab:cd:ef:b0:26:2b brd ff:ff:ff:ff:ff:ff inet 12.13.14.18/29 brd 12.13.14.23 scope global eth2 valid_lft forever preferred_lft forever inet 12.13.14.20/32 scope
[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
I've also verified that bionic-updates fixes the described issue root@bionic-test:/home/ubuntu# ip route default via 172.16.0.1 dev ens3 proto dhcp metric 1024 172.16.0.0/24 dev ens3 proto kernel scope link src 172.16.0.50 root@bionic-test:/home/ubuntu# ip r default via 172.16.0.1 dev ens3 proto dhcp metric 1024 172.16.0.0/24 dev ens3 proto kernel scope link src 172.16.0.50 root@bionic-test:/home/ubuntu# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:db:d8:6a brd ff:ff:ff:ff:ff:ff inet 172.16.0.50/24 brd 172.16.0.255 scope global ens3 valid_lft forever preferred_lft forever inet 172.16.0.24/24 brd 172.16.0.255 scope global secondary dynamic ens3 valid_lft 3468sec preferred_lft 3468sec inet6 fe80::5054:ff:fedb:d86a/64 scope link valid_lft forever preferred_lft forever root@bionic-test:/home/ubuntu# ip r default via 172.16.0.1 dev ens3 proto dhcp metric 1024 172.16.0.0/24 dev ens3 proto kernel scope link src 172.16.0.50 root@bionic-test:/home/ubuntu# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:db:d8:6a brd ff:ff:ff:ff:ff:ff inet 172.16.0.50/24 brd 172.16.0.255 scope global ens3 valid_lft forever preferred_lft forever inet 172.16.0.24/24 brd 172.16.0.255 scope global secondary dynamic ens3 valid_lft 3435sec preferred_lft 3435sec inet6 fe80::5054:ff:fedb:d86a/64 scope link valid_lft forever preferred_lft forever 3: ens7: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:11:c6:5b brd ff:ff:ff:ff:ff:ff root@bionic-test:/home/ubuntu# ip r default via 172.16.0.1 dev ens3 proto dhcp src 172.16.0.24 metric 1024 172.16.0.0/24 dev ens3 proto kernel scope link src 172.16.0.50 root@bionic-test:/home/ubuntu# ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco ** Tags added: verification-done verification-done-bionic verification-done-disco -- 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/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h On the dhcp client system, use networkd config such as: $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3580sec preferred_lft 3580sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 10.10.0.1 dev
[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
Hello, I've verified this with disco-updates. /etc/systemd/network/80-ens3.network :: [Match] Name=ens3 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=172.16.0.5/24 root@disco-test:/home/ubuntu# ip -4 a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 172.16.0.5/24 brd 172.16.0.255 scope global ens3 valid_lft forever preferred_lft forever inet 172.16.0.21/24 brd 172.16.0.255 scope global secondary dynamic ens3 valid_lft 3485sec preferred_lft 3485sec root@disco-test:/home/ubuntu# ip route default via 172.16.0.1 dev ens3 proto dhcp src 172.16.0.21 metric 1024 172.16.0.0/24 dev ens3 proto kernel scope link src 172.16.0.5 172.16.0.1 dev ens3 proto dhcp scope link src 172.16.0.21 metric 1024 root@disco-test:/home/ubuntu# ip r get 1.1.1.1 1.1.1.1 via 172.16.0.1 dev ens3 src 172.16.0.21 uid 0 cache -> setting classless option ubuntu@disco-test:~$ sudo su root@disco-test:/home/ubuntu# ip -4 a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 172.16.0.5/24 brd 172.16.0.255 scope global ens3 valid_lft forever preferred_lft forever inet 172.16.0.21/24 brd 172.16.0.255 scope global secondary dynamic ens3 valid_lft 3575sec preferred_lft 3575sec root@disco-test:/home/ubuntu# ip r default via 172.16.0.1 dev ens3 proto dhcp metric 1024 172.16.0.0/24 dev ens3 proto kernel scope link src 172.16.0.5 root@disco-test:/home/ubuntu# ip r get 1.1.1.1 1.1.1.1 via 172.16.0.1 dev ens3 src 172.16.0.5 uid 0 cache -> With the proposed package ubuntu@disco-test:~$ sudo su root@disco-test:/home/ubuntu# ip -4 a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 172.16.0.5/24 brd 172.16.0.255 scope global ens3 valid_lft forever preferred_lft forever inet 172.16.0.21/24 brd 172.16.0.255 scope global secondary dynamic ens3 valid_lft 3589sec preferred_lft 3589sec root@disco-test:/home/ubuntu# ip r get 1.1.1.1 1.1.1.1 via 172.16.0.1 dev ens3 src 172.16.0.21 uid 0 cache root@disco-test:/home/ubuntu# ip r default via 172.16.0.1 dev ens3 proto dhcp src 172.16.0.21 metric 1024 172.16.0.0/24 dev ens3 proto kernel scope link src 172.16.0.5 -- 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/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h On the dhcp client system, use networkd config such as: $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3580sec preferred_lft 3580sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 Note that, because networkd completes the static ip configuration before the dhcp reply is returned and processed, the static address is used for the subnet-local routing. But for global routing through the gateway, the dhcp-provided address is used: $ ip r get
[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
Without the patch for LP: #1668771 resolved caches the SERVFAIL answer on disco. oot@disco:/home/multipass# host www.montemar.cl Host www.montemar.cl not found: 2(SERVFAIL) (reverse-i-search)`': ^C root@disco:/home/multipass# journalctl -u systemd-resolved -f -- Logs begin at Fri 2019-07-26 13:15:35 -04. -- Jul 26 13:17:56 disco systemd-resolved[3872]: Transaction 43091 for scope dns on ens3/*. Jul 26 13:17:56 disco systemd-resolved[3872]: Using feature level UDP for transaction 43091. Jul 26 13:17:56 disco systemd-resolved[3872]: Sending query packet with id 43091. Jul 26 13:17:56 disco systemd-resolved[3872]: Processing incoming packet on transaction 43091 (rcode=SERVFAIL). Jul 26 13:17:56 disco systemd-resolved[3872]: Server returned error: SERVFAIL Jul 26 13:17:56 disco systemd-resolved[3872]: Verified we get a response at feature level UDP from DNS server 10.91.4.1. Jul 26 13:17:56 disco systemd-resolved[3872]: Added SERVFAIL cache entry for www.montemar.cl IN A 30s Jul 26 13:17:56 disco systemd-resolved[3872]: Transaction 43091 for on scope dns on ens3/* now complete with from network (unsigned). Jul 26 13:17:56 disco systemd-resolved[3872]: Sending response packet with id 40433 on interface 1/AF_INET. Jul 26 13:17:56 disco systemd-resolved[3872]: Freeing transaction 43091. With the patch for LP: #1668771 resolved + setting Cache: 'no-negative' doesn't caches the SERVFAIL option on disco. Logs begin at Fri 2019-07-26 13:15:35 -04. -- Jul 26 13:18:21 disco systemd-resolved[3893]: Transaction 22380 for scope dns on ens3/*. Jul 26 13:18:21 disco systemd-resolved[3893]: Using feature level UDP for transaction 22380. Jul 26 13:18:21 disco systemd-resolved[3893]: Sending query packet with id 22380. Jul 26 13:18:21 disco systemd-resolved[3893]: Processing incoming packet on transaction 22380 (rcode=SERVFAIL). Jul 26 13:18:21 disco systemd-resolved[3893]: Server returned error: SERVFAIL Jul 26 13:18:21 disco systemd-resolved[3893]: Verified we get a response at feature level UDP from DNS server 10.91.4.1. Jul 26 13:18:21 disco systemd-resolved[3893]: Not caching negative entry for: www.montemar.cl IN A, cache mode set to no-negative Jul 26 13:18:21 disco systemd-resolved[3893]: Transaction 22380 for on scope dns on ens3/* now complete with from network (unsigned). Jul 26 13:18:21 disco systemd-resolved[3893]: Sending response packet with id 30418 on interface 1/AF_INET. Jul 26 13:18:21 disco systemd-resolved[3893]: Freeing transaction 22380. ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco ** Tags added: verification-done verification-done-bionic verification-done-disco -- 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/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco syste
[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
Without the patch for LP: #1668771 resolved caches the SERVFAIL answer. root@bionic:/home/multipass# host www.montemar.cl Host www.montemar.cl not found: 2(SERVFAIL) root@bionic:/home/multipass# journalctl -u systemd-resolved -f -- Logs begin at Fri 2019-07-26 13:10:01 -04. -- Jul 26 13:13:12 bionic systemd-resolved[3167]: Transaction 25942 for scope dns on ens3/*. Jul 26 13:13:12 bionic systemd-resolved[3167]: Using feature level UDP for transaction 25942. Jul 26 13:13:12 bionic systemd-resolved[3167]: Sending query packet with id 25942. Jul 26 13:13:12 bionic systemd-resolved[3167]: Processing incoming packet on transaction 25942. (rcode=SERVFAIL) Jul 26 13:13:12 bionic systemd-resolved[3167]: Server returned error: SERVFAIL Jul 26 13:13:12 bionic systemd-resolved[3167]: Verified we get a response at feature level UDP from DNS server 10.91.4.1. Jul 26 13:13:12 bionic systemd-resolved[3167]: Added SERVFAIL cache entry for www.montemar.cl IN A 30s Jul 26 13:13:12 bionic systemd-resolved[3167]: Transaction 25942 for on scope dns on ens3/* now complete with from network (unsigned). Jul 26 13:13:12 bionic systemd-resolved[3167]: Sending response packet with id 26821 on interface 1/AF_INET. Jul 26 13:13:12 bionic systemd-resolved[3167]: Freeing transaction 25942. With the patch for LP: #1668771 resolved + setting Cache: 'no-negative' doesn't caches the SERVFAIL option root@bionic:/home/multipass# host www.montemar.cl Host www.montemar.cl not found: 2(SERVFAIL) root@bionic:/home/multipass# journalctl -u systemd-resolved -f -- Logs begin at Fri 2019-07-26 13:10:01 -04. -- Jul 26 13:13:40 bionic systemd-resolved[3199]: Transaction 48671 for scope dns on ens3/*. Jul 26 13:13:40 bionic systemd-resolved[3199]: Using feature level UDP for transaction 48671. Jul 26 13:13:40 bionic systemd-resolved[3199]: Sending query packet with id 48671. Jul 26 13:13:40 bionic systemd-resolved[3199]: Processing incoming packet on transaction 48671. (rcode=SERVFAIL) Jul 26 13:13:40 bionic systemd-resolved[3199]: Server returned error: SERVFAIL Jul 26 13:13:40 bionic systemd-resolved[3199]: Verified we get a response at feature level UDP from DNS server 10.91.4.1. Jul 26 13:13:40 bionic systemd-resolved[3199]: Not caching negative entry for: www.montemar.cl IN A, cache mode set to no-negative Jul 26 13:13:40 bionic systemd-resolved[3199]: Transaction 48671 for on scope dns on ens3/* now complete with from network (unsigned). Jul 26 13:13:40 bionic systemd-resolved[3199]: Sending response packet with id 25454 on interface 1/AF_INET. Jul 26 13:13:40 bionic systemd-resolved[3199]: Freeing transaction 48671. Marking this as verified and working. -- 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/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco sy
[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
** No longer affects: systemd (Ubuntu Xenial) -- 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/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. [Other Info] Note that systemd in Eoan is being upgraded to upstream 242, so I am not adding this to Eoan now, as I don't want to disturb the merge. If needed after the merge, I'll add to Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
** Patch added: "lp1668771-disco.debdiff" https://bugs.launchpad.net/systemd/+bug/1668771/+attachment/5278759/+files/lp1668771-disco.debdiff -- 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/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1668771] Re: systemd-resolved negative caching for extended period of time
** Patch added: "lp1668771-bionic.debdiff" https://bugs.launchpad.net/systemd/+bug/1668771/+attachment/5278752/+files/lp1668771-bionic.debdiff ** Summary changed: - systemd-resolved negative caching for extended period of time + [SRU] systemd-resolved negative caching for extended period of time -- 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/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1668771] Re: systemd-resolved negative caching for extended period of time
** Description changed: - 231-9ubuntu3 + [Impact] - If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the + * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. - After SERVFAIL DNS server issue has been resolved, chromium/firefox + * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. + + [Test Case] + + * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), + however, there are several use cases on which this condition is not acceptable (See #5552 comments) + and the only workaround would be to disable cache entirely or flush it , which isn't optimal. + + * Configure /etc/systemd/resolved.conf as follows: + + Cache=yes (default) + + * Restart systemd-resolved (systemctl restart systemd-resolved.service) + + * Run a host/getent command against a entry that will return SERVFAIL + and check the journalctl output to see that the reply gets served from + cache. + + root@systemd-disco:/home/ubuntu# host www.no-record.cl + Host www.montemar.cl not found: 2(SERVFAIL) + root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n + -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- + Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with + Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. + Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. + Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 + Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. + Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A + Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. + + The following patch https://github.com/systemd/systemd/pull/13047 + implements the required changes. -- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: T
[Touch-packages] [Bug 1668771] Re: systemd-resolved negative caching for extended period of time
** Tags added: sts sts-sru-needed -- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: 231-9ubuntu3 If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1668771] Re: systemd-resolved negative caching for extended period of time
-- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: 231-9ubuntu3 If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1668771] Re: systemd-resolved negative caching for extended period of time
** Patch added: "lp1668771-eoan.debdiff" https://bugs.launchpad.net/systemd/+bug/1668771/+attachment/5278115/+files/lp1668771-eoan.debdiff -- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: 231-9ubuntu3 If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1668771] Re: systemd-resolved negative caching for extended period of time
** Changed in: systemd (Ubuntu Disco) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => High -- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: 231-9ubuntu3 If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1668771] Re: systemd-resolved negative caching for extended period of time
** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Disco) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Disco) Status: New => In Progress -- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: 231-9ubuntu3 If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1668771] Re: systemd-resolved negative caching for extended period of time
The proposal to extend the 'cache' option with 'no-negative' has been merged upstream. I will proceed with the backports to Ubuntu on the affected LTS releases. [0] https://github.com/systemd/systemd/pull/13047 -- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Bug description: 231-9ubuntu3 If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1668771] Re: systemd-resolved negative caching for extended period of time
I've made a proposal to change the resolved.conf Cache option to a tri- state "no, no-negative, yes" values. [0] If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. This change adds the 'no-negative' option when set it avoids putting in cache negative answers but still works the same heuristics for positive answers. [0] https://github.com/systemd/systemd/pull/13047 ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: Confirmed => In Progress -- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Bug description: 231-9ubuntu3 If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1668771] Re: systemd-resolved negative caching for extended period of time
** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) -- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: 231-9ubuntu3 If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+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 1818100] [NEW] sistema roto
Public bug reported: cuando quiero actualizar, me dice que el sistema esta roto. cada vez que abro office, primero tiene que restaurar. esto es nuevo, hasta hace 2 dias no hacia nada de esto. gracias ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 28 12:53:00 2019 DistUpgraded: 2018-10-26 19:46:47,556 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: ath9k-msi, 1.1: added radeon-si, 1a, 4.4.0-38-generic, x86_64: built GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0789] InstallationDate: Installed on 2017-07-14 (594 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 14-3467 ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=4da0aff2-5e0c-4124-950f-922794c92879 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-10-26 (124 days ago) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0PCXP1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0PCXP1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 14-3467 dmi.product.sku: 0789 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Sun Mar 25 21:08:16 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1319 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1818100 Title: sistema roto Status in xorg package in Ubuntu: New Bug description: cuando quiero actualizar, me dice que el sistema esta roto. cada vez que abro office, primero tiene que restaurar. esto es nuevo, hasta hace 2 dias no hacia nada de esto. gracias ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 28 12:53:00 2019 DistUpgraded: 2018-10-26 19:46:47,556 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: ath9k-msi, 1.1: added radeon-si, 1a, 4.4.0-38-generic, x86_64: built GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0789] InstallationDate: Installed on 2017-07-14 (594 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspir
[Touch-packages] [Bug 1803579] [NEW] package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade: installed x11-common package post-installation script subprocess returned error exit status 1
Public bug reported: sudo dpkg --configure -a update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Thu Nov 15 12:16:54 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: installed x11-common package post-installation script subprocess returned error exit status 1 ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2018-11-15 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=8c500269-234e-4a72-82b7-7ad3b0172dc9 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: xorg Title: package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade: installed x11-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1616 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1616:bd10/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1803579 Title: package x11-common 1:7.7+19ubuntu7.1 failed to install/upgrade: installed x11-common package post-installation script subprocess returned error exit status 1 Status in xorg package in Ubuntu: New Bug description: sudo dpkg --configure -a update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Thu Nov 15 12:16:54 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: installed x11-common package post-installation script subprocess returned error exit status 1 ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2018-11-15 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=8c500269-
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
This is still happening on Ubuntu 18.04 and kernel 4.15 :( (Dell XPS 9550) -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1781804] [NEW] package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
*** This bug is a duplicate of bug 1779237 *** https://bugs.launchpad.net/bugs/1779237 Public bug reported: el sistema me pidio que lo informara, lo siento, no soy informatico ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jul 15 10:50:41 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-06-23 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3-defaults (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 python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1781804 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: New Bug description: el sistema me pidio que lo informara, lo siento, no soy informatico ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jul 15 10:50:41 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-06-23 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1781804/+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 1775700] [NEW] development package calls for .la in Libs but not provided
Public bug reported: The package config info files for libgstreamer-plugins-bad1.0-dev v1.8.x gstreamer-bad-audio-1.0.pc gstreamer-bad-base-1.0.pc gstreamer-bad-video-1.0.pc Calls for these libraries: ... Libs: -L${libdir} ${libdir}/libgstbadaudio-1.0.la ... However, the package does not include the .la files listed. Removing the .la files from the .pc file allows for successful compilation of some projects, but if they are required for some reason, they should be included in the package. ** Affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1775700 Title: development package calls for .la in Libs but not provided Status in gst-plugins-bad1.0 package in Ubuntu: New Bug description: The package config info files for libgstreamer-plugins-bad1.0-dev v1.8.x gstreamer-bad-audio-1.0.pc gstreamer-bad-base-1.0.pc gstreamer-bad-video-1.0.pc Calls for these libraries: ... Libs: -L${libdir} ${libdir}/libgstbadaudio-1.0.la ... However, the package does not include the .la files listed. Removing the .la files from the .pc file allows for successful compilation of some projects, but if they are required for some reason, they should be included in the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1775700/+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
Re: [Touch-packages] [Bug 1774979] Re: no input and output devices detected in sound definitions
I wanna thank you for the time you spent with this. What I did was a fresh install of the Ubuntu because I needed the laptop urgently. Everything went back to normal. Thank you once again for your support. I want to say that I' m very pleased with Ubuntu. A Ter, 5/06/2018, 03:11, Daniel van Vugt escreveu: > When experiencing the problem please also run: > > ps auxw | grep pulse > > and send us the output. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1774979 > > Title: > no input and output devices detected in sound definitions > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > After installing pulse audio equalizer, it worked good. everything was > detected in Sound Definitions and there was sound in the headphone > out. > > In the day after, every input and output devices were gone in Sound > Definition. I uninstalled pulse audio equalizer but nothing happened > in Sound Definitions, everything was gone. > > I rebooted the system and nothing. No sound. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: pulseaudio 1:8.0-0ubuntu3.10 > ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 > Uname: Linux 4.13.0-43-generic i686 > ApportVersion: 2.20.1-0ubuntu2.18 > Architecture: i386 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', > '/dev/snd/pcmC0D6p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', > '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > Date: Mon Jun 4 12:35:32 2018 > InstallationDate: Installed on 2018-01-04 (150 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 > (20170801) > ProcEnviron: >LANGUAGE=pt:pt_BR:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=pt_PT.UTF-8 >SHELL=/bin/bash > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > SourcePackage: pulseaudio > Symptom: audio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/15/2006 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: A6FAS.212 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: A6F > dmi.board.vendor: ASUSTeK Computer Inc. > dmi.board.version: 1.0 > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK Computer Inc. > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrA6FAS.212:bd05/15/2006:svnASUSTeKComputerInc.:pnA6F:pvr1.0:rvnASUSTeKComputerInc.:rnA6F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: > dmi.product.family: To Be Filled By O.E.M. > dmi.product.name: A6F > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK Computer Inc. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1774979/+subscriptions > -- 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/1774979 Title: no input and output devices detected in sound definitions Status in pulseaudio package in Ubuntu: Incomplete Bug description: After installing pulse audio equalizer, it worked good. everything was detected in Sound Definitions and there was sound in the headphone out. In the day after, every input and output devices were gone in Sound Definition. I uninstalled pulse audio equalizer but nothing happened in Sound Definitions, everything was gone. I rebooted the system and nothing. No sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jun 4 12:35:32 2018 InstallationDate: Installed on 2018-01-04 (150 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A6FAS.212 dmi.board.
[Touch-packages] [Bug 1774979] [NEW] no input and output devices detected in sound definitions
Public bug reported: After installing pulse audio equalizer, it worked good. everything was detected in Sound Definitions and there was sound in the headphone out. In the day after, every input and output devices were gone in Sound Definition. I uninstalled pulse audio equalizer but nothing happened in Sound Definitions, everything was gone. I rebooted the system and nothing. No sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jun 4 12:35:32 2018 InstallationDate: Installed on 2018-01-04 (150 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A6FAS.212 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A6F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA6FAS.212:bd05/15/2006:svnASUSTeKComputerInc.:pnA6F:pvr1.0:rvnASUSTeKComputerInc.:rnA6F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A6F dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial -- 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/1774979 Title: no input and output devices detected in sound definitions Status in pulseaudio package in Ubuntu: New Bug description: After installing pulse audio equalizer, it worked good. everything was detected in Sound Definitions and there was sound in the headphone out. In the day after, every input and output devices were gone in Sound Definition. I uninstalled pulse audio equalizer but nothing happened in Sound Definitions, everything was gone. I rebooted the system and nothing. No sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jun 4 12:35:32 2018 InstallationDate: Installed on 2018-01-04 (150 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A6FAS.212 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A6F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA6FAS.212:bd05/15/2006:svnASUSTeKComputerInc.:pnA6F:pvr1.0:rvnASUSTeKComputerInc.:rnA6F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A6F dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1774979/+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 1772130] [NEW] [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all
Public bug reported: Headphones worked for a while. After restart no sound at all ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jmachuca 7895 F pulseaudio CurrentDesktop: Unity Date: Fri May 18 21:20:36 2018 InstallationDate: Installed on 2018-03-22 (57 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jmachuca 7895 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.44 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.71 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.44:bd12/13/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.71:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1772130 Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Headphones worked for a while. After restart no sound at all ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jmachuca 7895 F pulseaudio CurrentDesktop: Unity Date: Fri May 18 21:20:36 2018 InstallationDate: Installed on 2018-03-22 (57 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jmachuca 7895 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.44 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.71 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.44:bd12/13/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.71:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1772130/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
Hello César Bento Freire, I've wrote a small tutorial about installing Portuguese Citizen Smartcard Software, at https://blog.geomaster.pt/cartao-de-cidadao-no-ubuntu-18-04/ You can install manually libxerces-c3.1 as Evgeny Brazgin explained. It also depends on libcurl3. To install Evgeny Brazgin packages, please do: sudo add-apt-repository ppa:xapienz/curl34 sudo apt policy curl sudo apt remove curl libcurl4 sudo apt install curl=7.58.0-2ubuntu3ppa2 libcurl4=7.58.0-2ubuntu3ppa2 Evgeny Brazgin: thank you for providing the packages! Well done! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1747238] [NEW] package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: See summary above ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Sat Jan 27 06:26:12 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2017-07-06 (212 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: qtbase-opensource-src Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1747238 Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in qtbase-opensource-src package in Ubuntu: New Bug description: See summary above ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Sat Jan 27 06:26:12 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2017-07-06 (212 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: qtbase-opensource-src Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1747238/+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 1743697] [NEW] package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: Ok That is ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Wed Jan 17 06:58:36 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2017-07-06 (194 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: qtbase-opensource-src Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1743697 Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in qtbase-opensource-src package in Ubuntu: New Bug description: Ok That is ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Wed Jan 17 06:58:36 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2017-07-06 (194 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: qtbase-opensource-src Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1743697/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade
Proposed fixed this bug on my Dell Vostro 1015 description: Portable Computer product: Vostro 1015 vendor: Dell Inc. serial: 9KKDQQ1 width: 64 bits capabilities: smbios-2.4 dmi-2.4 vsyscall32 configuration: boot=normal chassis=portable uuid=44454C4C-4B00-104B-8044-B9C04F515131 *-cpu description: CPU product: Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz vendor: Intel Corp. physical id: 400 bus info: cpu@0 slot: Microprocessor size: 918MHz capacity: 2201MHz width: 64 bits *-display:0 description: VGA compatible controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 07 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:16 memory:f6c0-f6ff memory:e000-efff ioport:efe8(size=8) memory:c-d *-display:1 UNCLAIMED description: Display controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2.1 bus info: pci@:00:02.1 version: 07 width: 64 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: latency=0 resources: memory:f6b0-f6bf libgl1-mesa-dri: Installed: 17.2.4-0ubuntu1~16.04.4 Candidate: 17.2.4-0ubuntu1~16.04.4 Version table: *** 17.2.4-0ubuntu1~16.04.4 100 100 /var/lib/dpkg/status 17.2.4-0ubuntu1~16.04.2 500 500 http://do.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 11.2.0-1ubuntu2 500 500 http://do.archive.ubuntu.com/ubuntu xenial/main amd64 Packages clock: 200MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm pti tpr_shadow vnmi flexpriority dtherm ida cpufreq configuration: cores=2 enabledcores=2 threads=2 *-pci description: Host bridge product: Mobile 4 Series Chipset Memory Controller Hub vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 07 width: 32 bits clock: 33MHz -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1737983] [NEW] after boot login box is not showed
Public bug reported: It is only visible on screen: "/dev/sda6: clean, 310791/3080192 files, 4546374/12317447 blocks" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.1: ApportVersion: 2.20.7-0ubuntu3.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Dec 13 11:52:41 2017 DistUpgraded: 2017-11-30 14:37:36,148 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-17-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-19-generic, i686: installed GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 945GSE Express Integrated Graphics Controller [103c:308f] Subsystem: Hewlett-Packard Company Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [103c:308f] InstallationDate: Installed on 2013-10-26 (1508 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=be4cca24-adab-48e0-963f-fc3129e79d9b ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2017-11-30 (12 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 308F0 Ver. F.18 dmi.board.name: 308F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 02.10 dmi.chassis.type: 10 dmi.chassis.vendor: Inventec dmi.modalias: dmi:bvnHewlett-Packard:bvr308F0Ver.F.18:bd10/06/2009:svnHewlett-Packard:pn:pvr03000:rvnHewlett-Packard:rn308F:rvrKBCVersion02.10:cvnInventec:ct10:cvr: dmi.product.family: 103C_5335KV dmi.product.version: 03000 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Dec 13 11:05:28 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful i386 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/1737983 Title: after boot login box is not showed Status in xorg package in Ubuntu: New Bug description: It is only visible on screen: "/dev/sda6: clean, 310791/3080192 files, 4546374/12317447 blocks" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.1: ApportVersion: 2.20.7-0ubuntu3.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Dec 13 11:52:41 2017 DistUpgraded: 2017-11-30 14:37:36,148 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-17-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-19-generic, i686: installed GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 945GSE Express Integrated Graphics Controller [103c:308f] Subsystem: Hewlett-Packard Company Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [103c:308f] InstallationDate: Installed on 2013-10-26 (1508 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0
[Touch-packages] [Bug 1733062] [NEW] package libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti
Public bug reported: A message issued while updating system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic i686 ApportVersion: 2.20.1-0ubuntu2.12 Architecture: i386 Date: Mon Nov 13 21:34:31 2017 DuplicateSignature: package:libqt5network5:i386:5.5.1+dfsg-16ubuntu7.5 Setting up perl-base (5.22.1-9ubuntu0.2) ... dpkg: error processing package libqt5network5:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-07-06 (134 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: qtbase-opensource-src Title: package libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1733062 Title: package libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in qtbase-opensource-src package in Ubuntu: New Bug description: A message issued while updating system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic i686 ApportVersion: 2.20.1-0ubuntu2.12 Architecture: i386 Date: Mon Nov 13 21:34:31 2017 DuplicateSignature: package:libqt5network5:i386:5.5.1+dfsg-16ubuntu7.5 Setting up perl-base (5.22.1-9ubuntu0.2) ... dpkg: error processing package libqt5network5:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-07-06 (134 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: qtbase-opensource-src Title: package libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1733062/+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 508522] Re: Mic is not available with A2DP Bluetooth profile
I'm on kubuntu 17.04 with pulseaudio 10.0, I'm still having this issue. -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in pulseaudio package in Ubuntu: Fix Released Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+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 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.
I dont know what happend -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1719004 Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Status in CUPS: Fix Released Status in cups package in Ubuntu: Invalid Status in glibc package in Ubuntu: Confirmed Bug description: 1. Error: Package/cups-daemon2.2.4-7 (mutilated) 2. compiz-core/tmp/apport_core_q_vnqis (corrupted) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-daemon 2.2.4-7 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Date: Fri Sep 22 22:16:18 2017 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2017-05-27 (118 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Papersize: a4 ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcEnviron: LANG=el_GR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: H110M-K D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1719004/+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 1723049] [NEW] package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: An error after operating system update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Oct 11 17:35:12 2017 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2017-07-06 (97 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: qtbase-opensource-src Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1723049 Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in qtbase-opensource-src package in Ubuntu: New Bug description: An error after operating system update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Oct 11 17:35:12 2017 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2017-07-06 (97 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: qtbase-opensource-src Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1723049/+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 1641272] Re: Debug symbols package doesnt exist
** Description changed: - On Yakkery with ddebs repos enabled there is no debug packages for + On Yakkety with ddebs repos enabled there is no debug packages for dnsmasq -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1641272 Title: Debug symbols package doesnt exist Status in dnsmasq package in Ubuntu: New Bug description: On Yakkety with ddebs repos enabled there is no debug packages for dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1641272/+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 1703796] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: I have received an error message indicating an error on this package (and many other messages) when running the upgrade from 14.04 LTS to 16.04 LTS. My apologies, I'm not a developer, I can not provide more details. I really apologise for that. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic i686 ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 Date: Wed Jul 12 08:21:15 2017 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-01-03 (920 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-07-12 (0 days ago) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1703796 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: I have received an error message indicating an error on this package (and many other messages) when running the upgrade from 14.04 LTS to 16.04 LTS. My apologies, I'm not a developer, I can not provide more details. I really apologise for that. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic i686 ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 Date: Wed Jul 12 08:21:15 2017 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-01-03 (920 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-07-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1703796/+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 1686036] Re: mountpoint remains in use after restore snapshot
** Summary changed: - strange behavior after restore snapshot + mountpoint remains in use after restore snapshot ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New ** No longer affects: lxc (Ubuntu) ** Changed in: lxd (Ubuntu) Status: New => Fix Committed ** Changed in: lxd (Ubuntu) Importance: Undecided => High ** Changed in: lxd (Ubuntu) Assignee: (unassigned) => Christian Brauner (cbrauner) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1686036 Title: mountpoint remains in use after restore snapshot Status in lxd package in Ubuntu: Fix Committed Status in lxd source package in Xenial: New Status in lxd source package in Yakkety: New Status in lxd source package in Zesty: New Status in lxd source package in Artful: Fix Committed Bug description: uname -a Linux lxd2-chel1 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux lxd: 2.12-0ubuntu3~ubuntu16.04.1~ppa1 zfsutils-linux: 0.6.5.6-0ubuntu16 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial after restore container from shapshot cannot add new snapshot or restore again until restart container example: # lxc image list +---+--++--++-+--+ | ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE | +---+--++--++-+--+ | debian/jessie | ba43812c4cb9 | no | Debian jessie amd64 (20170423_22:42) | x86_64 | 94.14MB | Apr 24, 2017 at 9:07am (UTC) | +---+--++--++-+--+ # lxc launch debian/jessie Creating popular-kitten The container you are starting doesn't have any network attached to it. To create a new network, use: lxc network create To attach a network to a container, use: lxc network attach Starting popular-kitten # lxc info popular-kitten Name: popular-kitten Remote: unix:/var/lib/lxd/unix.socket Architecture: x86_64 Created: 2017/04/25 07:17 UTC Status: Running Type: persistent Profiles: default Pid: 6965 Ips: lo: inet127.0.0.1 lo: inet6 ::1 Resources: Processes: 7 Disk usage: root: 1.48MB CPU usage: CPU usage (in seconds): 25 Memory usage: Memory (current): 16.22MB Memory (peak): 23.01MB Network usage: lo: Bytes received: 0B Bytes sent: 0B Packets received: 0 Packets sent: 0 # lxc profile show default config: {} description: Default LXD profile devices: root: path: / pool: main-pool type: disk name: default used_by: - /1.0/containers/popular-kitten # lxc snapshot popular-kitten # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted yes - # zfs get mounted main-pool/snapshots/popular-kitten NAMEPROPERTY VALUESOURCE main-pool/snapshots/popular-kitten mounted yes - # lxc restore popular-kitten snap0 # zfs get mounted main-pool/snapshots/popular-kitten NAMEPROPERTY VALUESOURCE main-pool/snapshots/popular-kitten mounted yes - # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted no - # lxc snapshot popular-kitten error: Failed to mount ZFS filesystem: filesystem 'main-pool/containers/popular-kitten' is already mounted cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is busy # lxc restore popular-kitten snap0 error: Failed to mount ZFS filesystem: filesystem 'main-pool/containers/popular-kitten' is already mounted cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is busy but container still work: # lxc info popular-kitten Name: popular-kitten Remote: unix:/var/lib/lxd/unix.socket Architecture: x86_64 Created: 2017/04/25 07:17 UTC Status: Running ... # lxc exec popular-kitten bash root@popular-kitten:~# uptime 07:34:06 up 8 min, 0 users, load average: 0.00, 0.02, 0.03 after restart container: # lxc restart popular-kitten # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popula
[Touch-packages] [Bug 1605813] Re: lock screen freezes while trying to wake from suspend
I too was affected by this bug. I run a fully updated 16.04 installation (currently 16.04.2) of Ubuntu. I used nouveau. When I pressed the power button on my work desktop to wake it from suspend, *sometimes* (here I differ from the original reporter) the login screen would appear and freeze. The system would not completely lock up. I could use ctrl + alt + f2 to switch to TTY2 and then restart the computer, like the original reporter. If I tried restarting lightdm via sudo service lightdm restart, the computer would completely lock up and I had to perform a hard restart. I successfully worked around the issue by installing the proprietary nvidia driver (nvidia-340). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1605813 Title: lock screen freezes while trying to wake from suspend Status in lightdm package in Ubuntu: Confirmed Bug description: Background: I am running a fully updated 16.04.1 installation of Ubuntu using open source nVidia drivers. When I press the power button on my PC to wake the computer from suspend, the login screen appears and freezes. The box around my username becomes somewhat opaque and no text box that would allow me to enter my password appears. I have tried this many times, and it always locks up in the same way. Steps taken after issue occurs: I have found, however, that the system is not completely locked up. I can use CTL + ALT + F2 to switch to TTY2. From there I can login and restart the computer without issue. I also tried restarting lightdm via sudo service lightdm restart. When I tried this and switched back to the GUI, the login screen was loaded, and I could type my password. Once the login screen disappeared, one of my monitors (dual-monitor setup) switched to my user account's wallpaper, and then the system locked up. I had to perform a hard restart. Workaround: I have found that using the proprietary 361.42 drivers provides a work around for this issue. When using the proprietary drivers, the computer resumes from suspend without issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 22 20:53:10 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-08 (14 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1605813/+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 1641272] Re: Debug symbols package doesnt exist
** Changed in: dnsmasq (Ubuntu) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1641272 Title: Debug symbols package doesnt exist Status in dnsmasq package in Ubuntu: New Bug description: On Yakkery with ddebs repos enabled there is no debug packages for dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1641272/+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 1677146] [NEW] package linux-image-4.8.0-44-generic 4.8.0-44.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: error updating the kernel? ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-44-generic 4.8.0-44.47 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jorge 6605 F pulseaudio Date: Wed Mar 29 04:40:58 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=69138c51-dcc0-4652-ba4b-d9064a368afb InstallationDate: Installed on 2016-11-21 (127 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: LENOVO 80FY ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic.efi.signed root=UUID=d2845ca9-eec8-4371-a8b0-ac313cebc9b4 ro intel_idle.max_cstate=1 quiet splash quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.8.0-44-generic 4.8.0-44.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 4A6 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN45WW:bd01/22/2015:svnLENOVO:pn80FY:pvrLenovoG40-30:rvnLENOVO:rnLancer4A6:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoG40-30: dmi.product.name: 80FY dmi.product.version: Lenovo G40-30 dmi.sys.vendor: LENOVO ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- 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/1677146 Title: package linux-image-4.8.0-44-generic 4.8.0-44.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: error updating the kernel? ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-44-generic 4.8.0-44.47 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jorge 6605 F pulseaudio Date: Wed Mar 29 04:40:58 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=69138c51-dcc0-4652-ba4b-d9064a368afb InstallationDate: Installed on 2016-11-21 (127 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: LENOVO 80FY ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic.efi.signed root=UUID=d2845ca9-eec8-4371-a8b0-ac313cebc9b4 ro intel_idle.max_cstate=1 quiet splash quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.8.0-44-generic 4.8.0-44.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 4A6 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN45WW:bd01/22/2015:svnLENOVO:pn80FY:pvrLenovoG40-30:rvnLENOVO:rnLancer4A6:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoG40-30: dmi.product.name: 80FY dmi.product.version: Lenovo G40-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1677146/+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 1672113] [NEW] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2
Public bug reported: i cant install software brackets because i can problem in gconf2 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Mar 12 00:05:26 2017 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 2 InstallationDate: Installed on 2016-05-06 (310 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1672113 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2 Status in gconf package in Ubuntu: New Bug description: i cant install software brackets because i can problem in gconf2 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Mar 12 00:05:26 2017 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 2 InstallationDate: Installed on 2016-05-06 (310 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1672113/+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 1662008] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: If you are using third party repositories then disable them, since they are a common source of problems. Now run the following command in a terminal: apt-get install -f If you are using third party repositories then disable them, since they are a common source of problems. Now run the following command in a terminal: apt-get install -f ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: cups-daemon: Install cups-daemon: Configure cups-core-drivers: Configure cups: Configure NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Sun Feb 5 20:08:13 2017 DpkgHistoryLog: Start-Date: 2017-02-05 20:08:11 Commandline: apt-get install -f Requested-By: jorge (1000) Upgrade: cups-daemon:amd64 (2.1.3-4, 2.1.3-4ubuntu0.1) ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-02-22 (1444 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer Aspire V5-431 Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=b8a734d9-9a19-4310-9464-ab3b143fb195 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=b8a734d9-9a19-4310-9464-ab3b143fb195 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-06-25 (225 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.03 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-431 dmi.board.vendor: Acer dmi.board.version: V2.03 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.03 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.03:bd08/31/2012:svnAcer:pnAspireV5-431:pvrV2.03:rvnAcer:rnAspireV5-431:rvrV2.03:cvnAcer:ct9:cvrV2.03: dmi.product.name: Aspire V5-431 dmi.product.version: V2.03 dmi.sys.vendor: Acer modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.default.cups: 2014-06-07T20:30:22.151186 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1662008 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: If you are using third party repositories then disable them, since they are a common source of problems. Now run the following command in a terminal: apt-get install -f If you are using third party repositories then disable them, since they are a common source of problems. Now run the following command in a terminal: apt-get install -f ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: cups-daemon: Install cups-daemon: Configure cups-core-drivers: Configure cups: Configure NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Sun Feb 5 20:08:13 2017 DpkgHistoryLog: Start-Date: 2017-02-05 20:08:11 Commandline: apt-get install -f Requested-By: jorge (1000) Upgrade: cups-daemon:amd64 (2.1.3-4, 2.1.3-4ubuntu0.1) ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-02-22 (1444 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer Aspire V5-431 Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=b8a734d9-9a19-4310-9464-ab3b143fb195 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=b8a734d9-9a19-4310-9464-ab3b143fb195 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-06-25 (225 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: Phoenix Technologies Lt
[Touch-packages] [Bug 1660822] [NEW] I need install samsung ML-2010 on ubuntu mate
Public bug reported: Hi friends .. I have a joybook lite u101c with ubuntu mate as operating system. The problem is that I need to install and configure my samsung ML-2010 printer and there are no suitable drivers .. try the system \ admin \ printers option but at the time of sending the print test comes the following ML-2010 printer message << PAUSED >> .. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: MATE Date: Tue Jan 31 16:23:18 2017 InstallationDate: Installed on 2016-09-05 (148 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) Lpstat: device for ML-2010: usb://Samsung/ML-2010?serial=4461BKAQ137842T. device for MP250-series: usb://Canon/MP250%20series?serial=B03193&interface=1 MachineType: BenQ Joybook Lite U101 Series Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MP250-series.ppd', '/etc/cups/ppd/ML-2010.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MP250-series.ppd: Permission denied grep: /etc/cups/ppd/ML-2010.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=4aa8affa-55eb-4e39-817b-0d22285a84ec ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 2.07 dmi.board.name: Joybook Lite U101 Series dmi.board.vendor: BenQ dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.07:bd04/23/2009:svnBenQ:pnJoybookLiteU101Series:pvr:rvnBenQ:rnJoybookLiteU101Series:rvr:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Joybook Lite U101 Series dmi.sys.vendor: BenQ ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1660822 Title: I need install samsung ML-2010 on ubuntu mate Status in cups package in Ubuntu: New Bug description: Hi friends .. I have a joybook lite u101c with ubuntu mate as operating system. The problem is that I need to install and configure my samsung ML-2010 printer and there are no suitable drivers .. try the system \ admin \ printers option but at the time of sending the print test comes the following ML-2010 printer message << PAUSED >> .. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: MATE Date: Tue Jan 31 16:23:18 2017 InstallationDate: Installed on 2016-09-05 (148 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) Lpstat: device for ML-2010: usb://Samsung/ML-2010?serial=4461BKAQ137842T. device for MP250-series: usb://Canon/MP250%20series?serial=B03193&interface=1 MachineType: BenQ Joybook Lite U101 Series Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MP250-series.ppd', '/etc/cups/ppd/ML-2010.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MP250-series.ppd: Permission denied grep: /etc/cups/ppd/ML-2010.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=4aa8affa-55eb-4e39-817b-0d22285a84ec ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 2.07 dmi.board.name: Joybook Lite U101 Series dmi.board.vendor: BenQ dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.07:bd04/23/2009:svnBenQ:pnJoybookLiteU101Series:pvr:rvnBenQ:rnJoybookLiteU101Series:rvr:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Joybook Lite U101 Series dmi.sys.vendor: BenQ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1660822/+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 1638695] Re: Python 2.7.12 performance regression
Hello, I have been working to track down the origin of the performance penalty exposed by this bug. All the tests that I am performing are made on top of a locally compiled version of python 2.7.12 (from upstream sources, not applying any ubuntu patch on it) built with different versions of GCC, 5.3.1 (current) and 4.8.0 both coming from the Ubuntu archives. I can see important performance differences as I mentioned on my previous comments (check the full comparisons stats) just by switching the GCC version. I decided to focus my investigation on the pickle module, since it seems to be the most affected one being approximately 1.17x slower between the different gcc versions. Due to the amount of changes introduced between 4.8.0 and 5.3.1 I decided to not persue the approach of doing a bisection of the changes for identifying an offending commit yet, until we can identify which optimization or change at compile time is causing the regression and focus our investigation on that specific area. My understanding is that the performance penalty caused by the compiler might be related to 2 factors, a important change on the linked libc or a optimization made by the compiler in the resulting object. Since the resulting objects are linked against the same glibc version 2.23, I will not consider that factor as part of the analysis, instead I will focus on analyzing the performance of the resulting objects generated by the compiler. For following this approach I ran the pyperformance suite and used a valgrind session excluding all the modules with the exception of the pickle module, using the default supressions to avoid missing any reference in the python runtime with the following arguments: valgrind --tool=callgrind --instr-atstart=no --trace-children=yes venv/cpython2.7-6ed9b6df9cd4/bin/python -m performance run --python /usr/local/bin/python2.7 -b pickle --inside-venv I did run this process multiple times with both GCC 4.8.0 and 5.3.1 to produce a large set of callgrind files to analyze , those callgrind files contains the full tree of execution including all the relocations, jumps, calls to the libc and the python runtime itself and of course time spent per function and the amount of calls made to it. I cleaned out all the resulting callgrind files removing the files smaller than 100k and the ones that were not loading the cPickle extension (https://pastebin.canonical.com/175951/). Over that set of files I executed callgrind_annotate to generate the stats per function ordered by the exclusive cost of function, Then with this script (http://paste.ubuntu.com/23795048/ ) I added all the costs per function per GCC version (4.8 and 5.3.1) and then I calculated the variance in cost between them. The resulting file contains a tuple with the following format: function name - gcc 4.8 cost - gcc 5.3.1 cost - variance in percent As an example: /home/ubuntu/python/cpython/Objects/tupleobject.c:tupleiter_dealloc 258068.00 445009.00 (variance: 0.724387) /home/ubuntu/python/cpython/Objects/object.c:try_3way_compare 984860.00 1676351.00 (variance: 0.702121) /home/ubuntu/python/cpython/Python/marshal.c:r_object 183524.00 27742.00 (variance: -0.848837) The full results can be located here sorted by variance in descending order http://paste.ubuntu.com/23795023/ Now that we have these results we can move forward comparing the generated code for the functions with bigger variance and track which optimization done by GCC might be altering the resulting objects. I will update this case after further investigation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression Status in python2.7 package in Ubuntu: Confirmed Bug description: I work on the OpenStack-Ansible project and we've noticed that testing jobs on 16.04 take quite a bit longer to complete than on 14.04. They complete within an hour on 14.04 but they normally take 90 minutes or more on 16.04. We use the same version of Ansible with both versions of Ubuntu. After more digging, I tested python performance (using the 'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There is a significant performance difference between each version of python. That is detailed in a spreadsheet[0]. I began using perf to dig into the differences when running the python performance module and when using Ansible playbooks. CPU migrations (as measured by perf) are doubled in Ubuntu 16.04 when running the same python workloads. I tried changing some of the kerne.sched sysctl configurables but they had very little effect on the results. I compiled python 2.7.12 from source on 14.04 and found the performance to be unchanged there. I'm not entirely sure where the problem might be now. We also h
[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression
** Changed in: python2.7 (Ubuntu) Importance: Undecided => High ** Changed in: python2.7 (Ubuntu) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression Status in python2.7 package in Ubuntu: Confirmed Bug description: I work on the OpenStack-Ansible project and we've noticed that testing jobs on 16.04 take quite a bit longer to complete than on 14.04. They complete within an hour on 14.04 but they normally take 90 minutes or more on 16.04. We use the same version of Ansible with both versions of Ubuntu. After more digging, I tested python performance (using the 'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There is a significant performance difference between each version of python. That is detailed in a spreadsheet[0]. I began using perf to dig into the differences when running the python performance module and when using Ansible playbooks. CPU migrations (as measured by perf) are doubled in Ubuntu 16.04 when running the same python workloads. I tried changing some of the kerne.sched sysctl configurables but they had very little effect on the results. I compiled python 2.7.12 from source on 14.04 and found the performance to be unchanged there. I'm not entirely sure where the problem might be now. We also have a bug open in OpenStack-Ansible[1] that provides additional detail. Thanks in advance for any help you can provide! [0] https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+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 1638695] Re: Python 2.7.12 performance regression
Hello, I am in the process of verifying this performance regression on a 16.04 Xenial machine using the kernel Linux-4.4.0-38. I ran a locally compiled python 2.7.12 version built with different versions of GCC, 5.3.1 (current) and 4.8.0 both coming from the Ubuntu archives. The benchmark suite I am using is the pyperformance suite (https://github.com/python/performance), I am running the full test suite, using the following command: $ pyperformance run --python=python2 -o xxx.json According to the latest test run i did using Python 2.7.12/GCC 4.8 (using GCC 5.3.1 as the baseline), 50% of the tests (32/64) have a significant variance in performance from which 19/32 are slower (in times ranging from 5-15%). Just for information, I am comparing results using the following command: $ pyperformance compare python-2.7.12-gcc-5.3.1.json python-2.7.12-gcc-4.8.0.json I am attaching here the current comparison results for analysis. ** Attachment added: "comparison-gcc-5.3.1-gcc-4.8.json" https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+attachment/4778622/+files/comparison-gcc-5.3.1-gcc-4.8.json -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression Status in python2.7 package in Ubuntu: Confirmed Bug description: I work on the OpenStack-Ansible project and we've noticed that testing jobs on 16.04 take quite a bit longer to complete than on 14.04. They complete within an hour on 14.04 but they normally take 90 minutes or more on 16.04. We use the same version of Ansible with both versions of Ubuntu. After more digging, I tested python performance (using the 'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There is a significant performance difference between each version of python. That is detailed in a spreadsheet[0]. I began using perf to dig into the differences when running the python performance module and when using Ansible playbooks. CPU migrations (as measured by perf) are doubled in Ubuntu 16.04 when running the same python workloads. I tried changing some of the kerne.sched sysctl configurables but they had very little effect on the results. I compiled python 2.7.12 from source on 14.04 and found the performance to be unchanged there. I'm not entirely sure where the problem might be now. We also have a bug open in OpenStack-Ansible[1] that provides additional detail. Thanks in advance for any help you can provide! [0] https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+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 1641324] [NEW] package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
Public bug reported: Restoring Xubuntu Xenial to manifest list of contents ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-shim 9-1bzr4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Nov 12 11:19:26 2016 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2014-03-19 (969 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd-shim Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-11-11 (0 days ago) mtime.conffile..etc.dbus-1.system.d.org.freedesktop.systemd1.conf: 2016-10-26T09:04:44 ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1641324 Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in systemd-shim package in Ubuntu: New Bug description: Restoring Xubuntu Xenial to manifest list of contents ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-shim 9-1bzr4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Nov 12 11:19:26 2016 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2014-03-19 (969 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd-shim Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-11-11 (0 days ago) mtime.conffile..etc.dbus-1.system.d.org.freedesktop.systemd1.conf: 2016-10-26T09:04:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1641324/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF
** No longer affects: libnl3 (Ubuntu Precise) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1567578 Title: libnl should be updated to support up to 63 VFs per single PF Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: Fix Released Bug description: [Impact] libnl can only enable up to 30 VFs even if the PF supports up to 63 VFs in an Openstack SRIOV configuration. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4. When trying to enable a guest with more than 30 VFs attached, the following error is returned: error: Failed to start domain guest1 error: internal error: missing IFLA_VF_INFO in netlink response [Test Case] 1) Edit /etc/default/grub. GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63" 2) Update grub and reboot the machine. $ sudo update-grub 3) Check that the virtual functions are available. $ sudo lspci|grep -i eth | grep -i virtual | wc -l 126 4) Create a KVM guest. $ sudo uvt-kvm create guest1 release=trusty 5) List the VF devices. $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed 's/\:/\_/g' | sed 's/\./\_/g' > devices.txt 6) Get the libvirt node device. $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list | grep $device; done > pci_devices.txt 7) Generate the XML config for each device. $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh nodedev-dumpxml $d > devices/$d.xml; done 8) Save and Run the following script. (http://pastebin.ubuntu.com/23374186/) $ sudo python generate-interfaces.py |grep address | wc -l 9) Finally attach the devices to the guest. $ sudo for i in $(seq 0 63); do virsh attach-device guest1 ./interfaces/$i.xml --config; done Device attached successfully [...] Device attached successfully Device attached successfully 10) Then destroy/start the guest again, at this point the error is reproduced. $ sudo virsh destroy guest1 Domain guest1 destroyed $ sudo virsh start guest1 error: Failed to start domain guest1 error: internal error: missing IFLA_VF_INFO in netlink response [Regression Potential] * None identified. [Other Info] * Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626 * A workaround is to install a newer library release. $ wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb $ wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb $ wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb $ dpkg -i libnl-3-200_3.2.24-2_amd64.deb $ dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb $ dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF
Hello Bryan, After installing the -proposed version the error presented on this bug is not reproducible anymore and the guest starts correctly. You can follow the reproduction steps that I added to the bug's description. Without -proposed: $ sudo virsh destroy guest1 Domain guest1 destroyed $ sudo virsh start guest1 error: Failed to start domain guest1 error: internal error: missing IFLA_VF_INFO in netlink response With proposed: root@bronzor:/home/ubuntu# start libvirt-bin libvirt-bin start/running, process 31492 root@bronzor:/home/ubuntu# virsh start guest1 Domain guest1 started ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1567578 Title: libnl should be updated to support up to 63 VFs per single PF Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Precise: New Status in libnl3 source package in Trusty: Fix Committed Bug description: [Impact] libnl can only enable up to 30 VFs even if the PF supports up to 63 VFs in an Openstack SRIOV configuration. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4. When trying to enable a guest with more than 30 VFs attached, the following error is returned: error: Failed to start domain guest1 error: internal error: missing IFLA_VF_INFO in netlink response [Test Case] 1) Edit /etc/default/grub. GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63" 2) Update grub and reboot the machine. $ sudo update-grub 3) Check that the virtual functions are available. $ sudo lspci|grep -i eth | grep -i virtual | wc -l 126 4) Create a KVM guest. $ sudo uvt-kvm create guest1 release=trusty 5) List the VF devices. $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed 's/\:/\_/g' | sed 's/\./\_/g' > devices.txt 6) Get the libvirt node device. $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list | grep $device; done > pci_devices.txt 7) Generate the XML config for each device. $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh nodedev-dumpxml $d > devices/$d.xml; done 8) Save and Run the following script. (http://pastebin.ubuntu.com/23374186/) $ sudo python generate-interfaces.py |grep address | wc -l 9) Finally attach the devices to the guest. $ sudo for i in $(seq 0 63); do virsh attach-device guest1 ./interfaces/$i.xml --config; done Device attached successfully [...] Device attached successfully Device attached successfully 10) Then destroy/start the guest again, at this point the error is reproduced. $ sudo virsh destroy guest1 Domain guest1 destroyed $ sudo virsh start guest1 error: Failed to start domain guest1 error: internal error: missing IFLA_VF_INFO in netlink response [Regression Potential] * None identified. [Other Info] * Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626 * A workaround is to install a newer library release. $ wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb $ wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb $ wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb $ dpkg -i libnl-3-200_3.2.24-2_amd64.deb $ dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb $ dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF
** Patch added: "fix-1567578-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+attachment/4766476/+files/fix-1567578-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1567578 Title: libnl should be updated to support up to 63 VFs per single PF Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Precise: New Status in libnl3 source package in Trusty: In Progress Bug description: [Description] Ubuntu 14.04.4 and SRIOV settings. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4 When trying to enable a guest with more than 30 VFs attached, the following error is returned: error: Failed to start domain guest1 error: internal error: missing IFLA_VF_INFO in netlink response [Impact] The library release is the 3.2.21-1 the bug is impacting on the maximum VFs number that can be enabled (up to 30) even if the PF supports up to 63 VFs in an Openstack SRIOV configuration [Test Case] The sequence to reproduce this bug is: 1) Edit /etc/default/grub GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63" 2) $ sudo update-grub ### Reboot the machine. 3) Check that the virtual functions are available: $ sudo lspci|grep -i eth | grep -i virtual | wc -l 126 4) Create a KVM guest $ sudo uvt-kvm create guest1 release=trusty 5) List the VF devices : $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed 's/\:/\_/g' | sed 's/\./\_/g' > devices.txt 6) Get the libvirt node device: $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list | grep $device; done > pci_devices.txt 7) Generate the XML config for each device: $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh nodedev-dumpxml $d > devices/$d.xml; done 8) Save and Run the following script (http://pastebin.ubuntu.com/23374186/) $ sudo python generate-interfaces.py |grep address | wc -l 9) Finally attach the devices to the guest. $ sudo for i in $(seq 0 63); do virsh attach-device guest1 ./interfaces/$i.xml --config; done Device attached successfully [...] Device attached successfully Device attached successfully 10) Then destroy/start the guest again, at this point the error is reproduced. $ sudo virsh destroy guest1 Domain guest1 destroyed $ sudo virsh start guest1 error: Failed to start domain guest1 error: internal error: missing IFLA_VF_INFO in netlink response * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. [Regression Potential] ** None identified. [Other Info] - Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626 [Workaround] The workaround is to install a newer library release, the 3.2.24-2: wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb dpkg -i libnl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF
Hello, After running a bisect between tags libnl3_2_21 and libnl3_2_22 I identified the fixer commit to be 807fddc nl: Increase receive buffer size to 4 pages commit 807fddc4cd9ecb12ba64e1b7fa26d86b6c2f19b0 Author: Thomas Graf Date: Wed May 8 13:52:27 2013 +0200 nl: Increase receive buffer size to 4 pages Assuming that the kernel does not send more than a page is no longer valid, and enabling MSG_PEEK'ing by default to figure out the exact message buffer requirements can have a negative influence on the performance of existing applications. Bumping the default receive buffer space to 4 pages seems a sane default. Signed-off-by: Thomas Graf --- After applying this patch on top of the current trusty-updates this problem is not longer exhibited and I can attach the full 128 VFs to the guest. I am proposing this patch for SRU, and I already updated the description with the reproduction steps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1567578 Title: libnl should be updated to support up to 63 VFs per single PF Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Precise: New Status in libnl3 source package in Trusty: In Progress Bug description: [Description] Ubuntu 14.04.4 and SRIOV settings. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4 When trying to enable a guest with more than 30 VFs attached, the following error is returned: error: Failed to start domain guest1 error: internal error: missing IFLA_VF_INFO in netlink response [Impact] The library release is the 3.2.21-1 the bug is impacting on the maximum VFs number that can be enabled (up to 30) even if the PF supports up to 63 VFs in an Openstack SRIOV configuration [Test Case] The sequence to reproduce this bug is: 1) Edit /etc/default/grub GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63" 2) $ sudo update-grub ### Reboot the machine. 3) Check that the virtual functions are available: $ sudo lspci|grep -i eth | grep -i virtual | wc -l 126 4) Create a KVM guest $ sudo uvt-kvm create guest1 release=trusty 5) List the VF devices : $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed 's/\:/\_/g' | sed 's/\./\_/g' > devices.txt 6) Get the libvirt node device: $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list | grep $device; done > pci_devices.txt 7) Generate the XML config for each device: $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh nodedev-dumpxml $d > devices/$d.xml; done 8) Save and Run the following script (http://pastebin.ubuntu.com/23374186/) $ sudo python generate-interfaces.py |grep address | wc -l 9) Finally attach the devices to the guest. $ sudo for i in $(seq 0 63); do virsh attach-device guest1 ./interfaces/$i.xml --config; done Device attached successfully [...] Device attached successfully Device attached successfully 10) Then destroy/start the guest again, at this point the error is reproduced. $ sudo virsh destroy guest1 Domain guest1 destroyed $ sudo virsh start guest1 error: Failed to start domain guest1 error: internal error: missing IFLA_VF_INFO in netlink response * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. [Regression Potential] ** None identified. [Other Info] - Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626 [Workaround] The workaround is to install a newer library release, the 3.2.24-2: wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb dpkg -i libnl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF
Hello, I am able to reproduce this bug consistently on a Trusty (3.19.0-73-generic) machine equipped with 2 ixgbe 10GbE cards: 04:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01) 04:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01) The sequence to reproduce this bug is: 1) Edit /etc/default/grub GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63" 2) $ sudo update-grub ### Reboot the machine. 3) Check that the virtual functions are available: $ sudo lspci|grep -i eth | grep -i virtual | wc -l 126 4) Create a KVM guest $ sudo uvt-kvm create guest1 release=trusty 5) List the VF devices : $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed 's/\:/\_/g' | sed 's/\./\_/g' > devices.txt 6) Get the libvirt node device: $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list | grep $device; done > pci_devices.txt 7) Generate the XML config for each device: $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh nodedev-dumpxml $d > devices/$d.xml; done 8) Save and Run the following script (http://pastebin.ubuntu.com/23374186/) $ sudo python generate-interfaces.py |grep address | wc -l 9) Finally attach the devices to the guest. $ sudo for i in $(seq 0 63); do virsh attach-device guest1 ./interfaces/$i.xml --config; done Device attached successfully [...] Device attached successfully Device attached successfully 10) Then destroy/start the guest again, at this point the error is reproduced. $ sudo virsh destroy guest1 Domain guest1 destroyed $ sudo virsh start guest1 error: Failed to start domain guest1 error: internal error: missing IFLA_VF_INFO in netlink response Please note that this error is not reproducible using libnl3_2_22. I am currently working to bisect and identify the offending commit and propose a backport to Ubuntu Trusty. ** Description changed: + [Description] + Ubuntu 14.04.4 and SRIOV settings. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4 - The library release is the 3.2.21-1 and the bug is impacting on the - maximum VFs number that can be enabled (up to 30) even if the PF - supports up to 63 VFs in an Openstack SRIOV configuration + When trying to enable a guest with more than 30 VFs attached, the + following error is returned: + + error: Failed to start domain guest1 + error: internal error: missing IFLA_VF_INFO in netlink response + + [Impact] + + The library release is the 3.2.21-1 the bug is impacting on the maximum + VFs number that can be enabled (up to 30) even if the PF supports up to + 63 VFs in an Openstack SRIOV configuration + + [Test Case] + + The sequence to reproduce this bug is: + + 1) Edit /etc/default/grub + + GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63" + + 2) $ sudo update-grub + + ### Reboot the machine. + + 3) Check that the virtual functions are available: + + $ sudo lspci|grep -i eth | grep -i virtual | wc -l + 126 + + 4) Create a KVM guest + + $ sudo uvt-kvm create guest1 release=trusty + + 5) List the VF devices : + + $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed + 's/\:/\_/g' | sed 's/\./\_/g' > devices.txt + + 6) Get the libvirt node device: + + $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list | grep + $device; done > pci_devices.txt + + 7) Generate the XML config for each device: + + $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh + nodedev-dumpxml $d > devices/$d.xml; done + + 8) Save and Run the following script + (http://pastebin.ubuntu.com/23374186/) + + $ sudo python generate-interfaces.py |grep address | wc -l + + 9) Finally attach the devices to the guest. + + $ sudo for i in $(seq 0 63); do virsh attach-device guest1 ./interfaces/$i.xml --config; done + Device attached successfully + [...] + + Device attached successfully + Device attached successfully + + 10) Then destroy/start the guest again, at this point the error is + reproduced. + + $ sudo virsh destroy guest1 + Domain guest1 destroyed + + $ sudo virsh start guest1 + + error: Failed to start domain guest1 + error: internal error: missing IFLA_VF_INFO in netlink response + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + + [Regression Potential] + + ** None identified. + + [Other Info] + + - Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626 + + [Workaround] The workaround is to install a newer library release, the 3.2.24-2: wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/u
[Touch-packages] [Bug 1567578] Re: libnl should be updated to support up to 63 VFs per single PF
** Changed in: libnl3 (Ubuntu Trusty) Status: New => In Progress ** Changed in: libnl3 (Ubuntu Trusty) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1567578 Title: libnl should be updated to support up to 63 VFs per single PF Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Precise: New Status in libnl3 source package in Trusty: In Progress Bug description: Ubuntu 14.04.4 and SRIOV settings. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4 The library release is the 3.2.21-1 and the bug is impacting on the maximum VFs number that can be enabled (up to 30) even if the PF supports up to 63 VFs in an Openstack SRIOV configuration The workaround is to install a newer library release, the 3.2.24-2: wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb dpkg -i libnl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF
** Changed in: libnl3 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libnl3 (Ubuntu) Assignee: Jorge Niedbalski (niedbalski) => (unassigned) ** Changed in: libnl3 (Ubuntu Trusty) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) ** Changed in: libnl3 (Ubuntu Precise) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1567578 Title: libnl should be updated to support up to 63 VFs per single PF Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Precise: New Status in libnl3 source package in Trusty: New Bug description: Ubuntu 14.04.4 and SRIOV settings. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4 The library release is the 3.2.21-1 and the bug is impacting on the maximum VFs number that can be enabled (up to 30) even if the PF supports up to 63 VFs in an Openstack SRIOV configuration The workaround is to install a newer library release, the 3.2.24-2: wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb dpkg -i libnl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF
** Changed in: libnl3 (Ubuntu) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) ** Changed in: libnl3 (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1567578 Title: libnl should be updated to support up to 63 VFs per single PF Status in libnl3 package in Ubuntu: Confirmed Bug description: Ubuntu 14.04.4 and SRIOV settings. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4 The library release is the 3.2.21-1 and the bug is impacting on the maximum VFs number that can be enabled (up to 30) even if the PF supports up to 63 VFs in an Openstack SRIOV configuration The workaround is to install a newer library release, the 3.2.24-2: wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb dpkg -i libnl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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