[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Tagging onto my previous post (https://bugs.launchpad.net/ubuntu- cdimage/+bug/1871268/comments/167) I am on a Nvidia GTX 2060 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion:
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Just hit this bug on Ubuntu MATE 20.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed
[Touch-packages] [Bug 465433]
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/465433 Title: dolphin crashed in [PolygonRegion, QRegion, QX11PaintEngine::updateState] (assert failure) Status in Qt: Invalid Status in qt4-x11 package in Ubuntu: Triaged Bug description: Binary package hint: kdebase Release: Kubuntu 9.10, i386 Dolphin package version: 4:4.3.2-0ubuntu3 Dolphin crashed when I tried to move one picture from one folder to another folder (each opened in separate Dolphin windows). Expected result: - picture gets moved - both windows stay opened Actual result: - picture got moved - Dolphin crashed (all opened windows disappeared) ProblemType: Crash Architecture: i386 AssertionMessage: *** glibc detected *** dolphin: corrupted double-linked list: 0x09c774f0 *** Date: Fri Oct 30 20:39:43 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/dolphin Package: dolphin 4:4.3.2-0ubuntu3 ProcCmdline: dolphin -session 10d2dc656600012567575210229620045_1256913310_108428 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic Signal: 6 SourcePackage: kdebase StacktraceTop: __kernel_vsyscall () *__GI_raise (sig=6) *__GI_abort () at abort.c:92 __libc_message (do_abort=2, malloc_printerr (action=, Title: dolphin assert failure: *** glibc detected *** dolphin: corrupted double-linked list: 0x09c774f0 *** Uname: Linux 2.6.31-14-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (polkit-gnome-authentication-agent-1:2444): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/465433/+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 465433] Re: dolphin crashed in [PolygonRegion, QRegion, QX11PaintEngine::updateState] (assert failure)
** Changed in: qt Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/465433 Title: dolphin crashed in [PolygonRegion, QRegion, QX11PaintEngine::updateState] (assert failure) Status in Qt: Invalid Status in qt4-x11 package in Ubuntu: Triaged Bug description: Binary package hint: kdebase Release: Kubuntu 9.10, i386 Dolphin package version: 4:4.3.2-0ubuntu3 Dolphin crashed when I tried to move one picture from one folder to another folder (each opened in separate Dolphin windows). Expected result: - picture gets moved - both windows stay opened Actual result: - picture got moved - Dolphin crashed (all opened windows disappeared) ProblemType: Crash Architecture: i386 AssertionMessage: *** glibc detected *** dolphin: corrupted double-linked list: 0x09c774f0 *** Date: Fri Oct 30 20:39:43 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/dolphin Package: dolphin 4:4.3.2-0ubuntu3 ProcCmdline: dolphin -session 10d2dc656600012567575210229620045_1256913310_108428 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic Signal: 6 SourcePackage: kdebase StacktraceTop: __kernel_vsyscall () *__GI_raise (sig=6) *__GI_abort () at abort.c:92 __libc_message (do_abort=2, malloc_printerr (action=, Title: dolphin assert failure: *** glibc detected *** dolphin: corrupted double-linked list: 0x09c774f0 *** Uname: Linux 2.6.31-14-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (polkit-gnome-authentication-agent-1:2444): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/465433/+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 1900481] Re: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1900481 Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Expired Bug description: Following upgrade to 20.04, I have no audio. My output device is "Dummy Output". I chose one audio device to report against: none are detected. All this may be obvious from the auto-detected diagnostics. It was working in 18.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Oct 19 19:43:52 2020 InstallationDate: Installed on 2018-05-05 (897 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180505) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel MID Symptom_Jack: Mic, Top Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 030DMJ dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn030DMJ:rvrA10:cvnDellInc.:ct8:cvrA10: dmi.product.name: Vostro 3300 dmi.product.sku: To be filled by O.E.M. dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1900481/+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 1910480] Re: no audio on fresh install kubuntu groovy
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1910480 Title: no audio on fresh install kubuntu groovy Status in alsa-driver package in Ubuntu: New Bug description: on installing Kubuntu Groovy 'no output or input devices found' sound appears to be disabled running ubuntu-debug -s audio does produce sound in both headphone channels in first part of test but no sound in second part sound is recognised and working okay if Kubuntu Focal is installed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1071 F pulseaudio bob1074 F pipewire-media- /dev/snd/controlC1: bob1074 F pipewire-media- /dev/snd/seq:bob1070 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 03:19:48 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [MBB-895908, Realtek ALC892, SPDIF Out, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: 7354844-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:br4.6:svnNOVATECHLTD:pnMBB-895908:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnNOVATECHLTD:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-895908 dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1910480/+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 1910480] [NEW] no audio on fresh install kubuntu groovy
You have been subscribed to a public bug: on installing Kubuntu Groovy 'no output or input devices found' sound appears to be disabled running ubuntu-debug -s audio does produce sound in both headphone channels in first part of test but no sound in second part sound is recognised and working okay if Kubuntu Focal is installed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1071 F pulseaudio bob1074 F pipewire-media- /dev/snd/controlC1: bob1074 F pipewire-media- /dev/snd/seq:bob1070 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 03:19:48 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [MBB-895908, Realtek ALC892, SPDIF Out, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: 7354844-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:br4.6:svnNOVATECHLTD:pnMBB-895908:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnNOVATECHLTD:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-895908 dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- no audio on fresh install kubuntu groovy https://bugs.launchpad.net/bugs/1910480 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1910405] Re: bluetoothd hangs and cannot be killed
A process that cannot be killed usually means it's blocked in a kernel call. So this sounds like a bug in the kernel Bluetooth code... Please: 1. Run this command to gather more system info: apport-collect 1910405 2. Try a newer Ubuntu release or just a newer kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D ** Tags added: bionic ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1910405 Title: bluetoothd hangs and cannot be killed Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hi, When having a bluetooth headphone (JBL Live) connected using the A2DP pulseaudio sink, the output sound suddenly stops during a music streaming of videocall session. Sometimes just disconnecting and reconnecting the headphone works, but some times reconnection is not possible anymore due to the hanging of bluetoothd. Bluetoothd still appears in the processes list, but cannot be killed, neither with "sudo service bluetooth stop" or "kill -9": $ ps afx | grep blue 9597 tty2 Sl+0:01 | \_ gnome-control-center bluetooth 5405 ?Ss 0:00 \_ /usr/lib/bluetooth/obexd 10694 pts/0S+ 0:00 \_ grep blue 20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd All programs keep working normally, only bluetooth is affected as well as the bluetooth settings page. The only solution is a hard reboot. A soft reboot doesn't even work: the systems keeps trying to end the bluetoothd process so one needs to press the power button for a few seconds to terminate the process. $ bluetoothd --version 5.48 $ uname -a Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working nice for over one year now just like previous versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910435] Re: display texts are gone noting will show
Thanks for the bug report. Please attach a screenshot or photo of the problem. Also, do you find the problem only occurs after suspend/hibernate? ** Tags added: nvidia ** Summary changed: - display texts are gone noting will show + [nvidia] display texts are gone noting will show ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910435 Title: [nvidia] display texts are gone noting will show Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-450 package in Ubuntu: Incomplete Bug description: no text showing even restart and shutdown button's text ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 02:17:02 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-42-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 450.80.02, 5.4.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:8627] InstallationDate: Installed on 2020-12-24 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A) Bus 001 Device 003: ID 1038:170a SteelSeries ApS SteelSeries Rival 100 Dell China Bus 001 Device 002: ID 0c45:672e Microdia USB DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=15221e3c-7bd7-41a8-b8bc-27f5c93ca2a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: H110M-F 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.:bvr3806:bd05/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-F: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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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:
[Touch-packages] [Bug 1910471] [NEW] [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all
Public bug reported: Running Ubuntu Mate 20.04 on Raspberry Pi 4 with Dual Monitor Set-up Description:Ubuntu 20.04.1 LTS Release:20.04 Packages involved: Unknown Issue: I can choose either 2 HDMI monitors or sound but not both Expected: Sound works with both monitors plugged in (1) No sound from headphone jack or HDMI in two monitor configuration (2) If I unplug 2nd monitor and reboot, sound works fine in HDMI or headphone jack (3) If I plug in second monitor while Pi is running, no picture in second monitor but sound still works (4) Sound works normally in Raspbian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-1025.28-raspi 5.4.73 Uname: Linux 5.4.0-1025-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio /dev/snd/pcmC2D0p: loreleiandmike 1211 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jan 6 19:45:47 2021 ImageMediaBuild: 20200812 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US 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:b1 failed Symptom_Card: Built-in Audio - bcm2835 Headphones Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio Symptom_Type: No sound at all Title: [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 focal uec-images -- 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/1910471 Title: [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Running Ubuntu Mate 20.04 on Raspberry Pi 4 with Dual Monitor Set-up Description: Ubuntu 20.04.1 LTS Release: 20.04 Packages involved: Unknown Issue: I can choose either 2 HDMI monitors or sound but not both Expected: Sound works with both monitors plugged in (1) No sound from headphone jack or HDMI in two monitor configuration (2) If I unplug 2nd monitor and reboot, sound works fine in HDMI or headphone jack (3) If I plug in second monitor while Pi is running, no picture in second monitor but sound still works (4) Sound works normally in Raspbian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-1025.28-raspi 5.4.73 Uname: Linux 5.4.0-1025-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio /dev/snd/pcmC2D0p: loreleiandmike 1211 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jan 6 19:45:47 2021 ImageMediaBuild: 20200812 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US 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:b1 failed Symptom_Card: Built-in Audio - bcm2835 Headphones Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio Symptom_Type: No sound at all Title: [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1910471/+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 1909698] Autopkgtest regression report (tzdata/2020f-0ubuntu0.20.04)
All autopkgtests for the newly accepted tzdata (2020f-0ubuntu0.20.04) for focal have finished running. The following regressions have been reported in tests triggered by the package: gnustep-base/1.26.0-7 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#tzdata [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
Verified on xenial: (xenial-amd64)root@impulse:~# apt-cache policy tzdata tzdata: Installed: 2020f-0ubuntu0.16.04 Candidate: 2020f-0ubuntu0.16.04 Version table: *** 2020f-0ubuntu0.16.04 500 500 http://archive.ubuntu.com//ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2020d-0ubuntu0.16.04 500 500 http://ubuntu.osuosl.org/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2016d-0ubuntu0.16.04 500 500 http://ubuntu.osuosl.org/ubuntu xenial/main amd64 Packages (xenial-amd64)root@impulse:~# zdump -v Europe/Volgograd | tail -n6 Europe/Volgograd Sat Oct 27 22:59:59 2018 UT = Sun Oct 28 01:59:59 2018 +03 isdst=0 gmtoff=10800 Europe/Volgograd Sat Oct 27 23:00:00 2018 UT = Sun Oct 28 03:00:00 2018 +04 isdst=0 gmtoff=14400 Europe/Volgograd Sat Dec 26 21:59:59 2020 UT = Sun Dec 27 01:59:59 2020 +04 isdst=0 gmtoff=14400 Europe/Volgograd Sat Dec 26 22:00:00 2020 UT = Sun Dec 27 01:00:00 2020 +03 isdst=0 gmtoff=10800 Europe/Volgograd 9223372036854689407 = NULL Europe/Volgograd 9223372036854775807 = NULL (xenial-amd64)root@impulse:~# diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) ** Tags removed: verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-xenial ** 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 tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
There is also updated information in Focal for Volgograd. (focal-amd64)root@impulse:~# zdump -v Europe/Volgograd | tail -n 6 Europe/Volgograd Sat Oct 27 22:59:59 2018 UT = Sun Oct 28 01:59:59 2018 +03 isdst=0 gmtoff=10800 Europe/Volgograd Sat Oct 27 23:00:00 2018 UT = Sun Oct 28 03:00:00 2018 +04 isdst=0 gmtoff=14400 Europe/Volgograd Sat Dec 26 21:59:59 2020 UT = Sun Dec 27 01:59:59 2020 +04 isdst=0 gmtoff=14400 Europe/Volgograd Sat Dec 26 22:00:00 2020 UT = Sun Dec 27 01:00:00 2020 +03 isdst=0 gmtoff=10800 Europe/Volgograd 9223372036854689407 = NULL Europe/Volgograd 9223372036854775807 = NULL (focal-amd64)root@impulse:~# apt-cache policy tzdata tzdata: Installed: 2020f-0ubuntu0.20.04 Candidate: 2020f-0ubuntu0.20.04 Version table: *** 2020f-0ubuntu0.20.04 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2020d-0ubuntu0.20.04 500 500 http://192.168.10.7/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 2019c-3ubuntu1 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages And the SystemV timezones are still available. focal-amd64)root@impulse:~# diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) nothing to see here ** Tags removed: verification-needed-focal verification-needed-groovy ** Tags added: verification-done-focal verification-done-groovy -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
Verified on bionic: (bionic-amd64)root@impulse:~# apt-cache policy tzdata tzdata: Installed: 2020f-0ubuntu0.18.04 Candidate: 2020f-0ubuntu0.18.04 Version table: *** 2020f-0ubuntu0.18.04 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2020d-0ubuntu0.18.04 500 500 http://ubuntu.osuosl.org/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2018d-1 500 500 http://ubuntu.osuosl.org/ubuntu bionic/main amd64 Packages (bionic-amd64)root@impulse:~# zdump -v Europe/Volgograd | tail -n 6 Europe/Volgograd Sat Oct 27 22:59:59 2018 UT = Sun Oct 28 01:59:59 2018 +03 isdst=0 gmtoff=10800 Europe/Volgograd Sat Oct 27 23:00:00 2018 UT = Sun Oct 28 03:00:00 2018 +04 isdst=0 gmtoff=14400 Europe/Volgograd Sat Dec 26 21:59:59 2020 UT = Sun Dec 27 01:59:59 2020 +04 isdst=0 gmtoff=14400 Europe/Volgograd Sat Dec 26 22:00:00 2020 UT = Sun Dec 27 01:00:00 2020 +03 isdst=0 gmtoff=10800 Europe/Volgograd 9223372036854689407 = NULL Europe/Volgograd 9223372036854775807 = NULL (bionic-amd64)root@impulse:~# diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) (bionic-amd64)root@impulse:~# -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
We can see that there is updated information for Volgograd, so setting to v-done for groovy. (groovy-amd64)root@impulse:~# apt-cache policy tzdata tzdata: Installed: 2020f-0ubuntu0.20.10 Candidate: 2020f-0ubuntu0.20.10 Version table: *** 2020f-0ubuntu0.20.10 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2020d-1ubuntu1 500 500 http://192.168.10.7/ubuntu groovy-updates/main amd64 Packages 500 http://192.168.10.7/ubuntu groovy-security/main amd64 Packages 2020b-1ubuntu1 500 500 http://192.168.10.7/ubuntu groovy/main amd64 Packages (groovy-amd64)root@impulse:~# zdump -v Europe/Volgograd | tail -n 6 Europe/Volgograd Sat Oct 27 22:59:59 2018 UT = Sun Oct 28 01:59:59 2018 +03 isdst=0 gmtoff=10800 Europe/Volgograd Sat Oct 27 23:00:00 2018 UT = Sun Oct 28 03:00:00 2018 +04 isdst=0 gmtoff=14400 Europe/Volgograd Sat Dec 26 21:59:59 2020 UT = Sun Dec 27 01:59:59 2020 +04 isdst=0 gmtoff=14400 Europe/Volgograd Sat Dec 26 22:00:00 2020 UT = Sun Dec 27 01:00:00 2020 +03 isdst=0 gmtoff=10800 Europe/Volgograd 9223372036854689407 = NULL Europe/Volgograd 9223372036854775807 = NULL -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1907744] Re: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess was killed by signal (A
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1907744 Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess was killed by signal (Aborted) Status in unattended-upgrades package in Ubuntu: New Bug description: I have problems, it has disappeared programs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: unattended-upgrades 2.3ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 10 19:18:08 2020 ErrorMessage: installed unattended-upgrades package post-installation script subprocess was killed by signal (Aborted) InstallationDate: Installed on 2014-04-19 (2427 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: unattended-upgrades Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess was killed by signal (Aborted) UpgradeStatus: Upgraded to focal on 2020-12-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1907744/+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 1907744] Re: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess was killed by signal (A
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1907744 Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess was killed by signal (Aborted) Status in unattended-upgrades package in Ubuntu: New Bug description: I have problems, it has disappeared programs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: unattended-upgrades 2.3ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 10 19:18:08 2020 ErrorMessage: installed unattended-upgrades package post-installation script subprocess was killed by signal (Aborted) InstallationDate: Installed on 2014-04-19 (2427 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: unattended-upgrades Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess was killed by signal (Aborted) UpgradeStatus: Upgraded to focal on 2020-12-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1907744/+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 1881947] Re: Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting.
** Also affects: systemd (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Hirsute) Status: New => In Progress ** Changed in: systemd (Ubuntu Hirsute) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Hirsute) Importance: Undecided => Low -- 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/1881947 Title: Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting. Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: In Progress Bug description: Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz [...] PASS: test-journal-enum == test-journal-flush === Root directory /var/log/journal removed. Directory /var/log/journal/3286b2469d224077b1026d239d625b0d removed. mmap cache statistics: 739 hit, 5 miss journal_file_copy_entry failed: Bad message Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting. FAIL: test-journal-flush (code: 134) Aborted (core dumped) == test-journal-importer === [...] autopkgtest [07:17:29]: summary timedatedPASS hostnamedPASS localed-locale PASS localed-x11-keymap PASS logind PASS unit-config PASS storage PASS networkd-test.py PASS build-login PASS boot-and-servicesPASS udev PASS root-unittests FAIL non-zero exit status 134 upstream PASS boot-smoke PASS systemd-fsckdPASS Exit request sent. [...] To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1881947/+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 1750051] Re: cron doesn't support MAILFROM
I also just ran into a case where this would make my life much easier. Any idea on when we can expect this? -- 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/1750051 Title: cron doesn't support MAILFROM Status in cron package in Ubuntu: Triaged Status in cron package in Debian: New Bug description: Ubuntu's cron version doesn't support setting MAILFROM to set the "From:" header of cron generated emails. This feature would be nice to have and bring parity with RHEL/CentOS which has it since RHEL 6: $ cat /etc/redhat-release CentOS release 6.6 (Final) $ man 5 crontab | grep -1 FROM doesn´t do aliasing, and UUCP usually doesn´t read its mail. If MAIL- FROM is defined (and non-empty), it will be used as the envelope sender address, otherwise, ‘‘root’’ will be used. $ apt-cache policy cron cron: Installed: 3.0pl1-128ubuntu2 Candidate: 3.0pl1-128ubuntu2 Version table: *** 3.0pl1-128ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 16 15:52:54 2018 InstallationDate: Installed on 2016-12-06 (436 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161206) 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/1750051/+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 1909698] Please test proposed package
Hello Tw1ce, or anyone else affected, Accepted tzdata into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2020f- 0ubuntu0.16.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
Hello Tw1ce, or anyone else affected, Accepted tzdata into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2020f- 0ubuntu0.18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tzdata (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic ** Changed in: tzdata (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Please test proposed package
Hello Tw1ce, or anyone else affected, Accepted tzdata into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2020f- 0ubuntu0.20.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
Hello Tw1ce, or anyone else affected, Accepted tzdata into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2020f- 0ubuntu0.20.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tzdata (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: tzdata (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1910435] Re: display texts are gone noting will show
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910435 Title: display texts are gone noting will show Status in xorg package in Ubuntu: New Bug description: no text showing even restart and shutdown button's text ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 02:17:02 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-42-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 450.80.02, 5.4.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:8627] InstallationDate: Installed on 2020-12-24 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A) Bus 001 Device 003: ID 1038:170a SteelSeries ApS SteelSeries Rival 100 Dell China Bus 001 Device 002: ID 0c45:672e Microdia USB DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=15221e3c-7bd7-41a8-b8bc-27f5c93ca2a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: H110M-F 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.:bvr3806:bd05/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-F: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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/1910435/+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 1910435] [NEW] display texts are gone noting will show
You have been subscribed to a public bug: no text showing even restart and shutdown button's text ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 02:17:02 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-42-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia, 450.80.02, 5.4.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:8627] InstallationDate: Installed on 2020-12-24 (12 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A) Bus 001 Device 003: ID 1038:170a SteelSeries ApS SteelSeries Rival 100 Dell China Bus 001 Device 002: ID 0c45:672e Microdia USB DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=15221e3c-7bd7-41a8-b8bc-27f5c93ca2a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: H110M-F 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.:bvr3806:bd05/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-F: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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- display texts are gone noting will show https://bugs.launchpad.net/bugs/1910435 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted
Has gnulib upstream been notified about the fix for this bug? ... or about the original treat-devtmpfs-and-squashfs-as-dummy- filesystems.patch that the fix was applied to? https://launchpadlibrarian.net/510003931/coreutils_8.32-4ubuntu1_8.32-4ubuntu2.diff.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in coreutils package in Ubuntu: Fix Released Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1881947] Re: Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting.
** Merge proposal linked: https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/395861 -- 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/1881947 Title: Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting. Status in systemd: New Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Bug description: Observed in an focal/arm64 autopkgtest failure of systemd 245.4-4ubuntu3.1: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20200603_071743_738b2@/log.gz [...] PASS: test-journal-enum == test-journal-flush === Root directory /var/log/journal removed. Directory /var/log/journal/3286b2469d224077b1026d239d625b0d removed. mmap cache statistics: 739 hit, 5 miss journal_file_copy_entry failed: Bad message Assertion 'r >= 0' failed at src/journal/test-journal-flush.c:52, function main(). Aborting. FAIL: test-journal-flush (code: 134) Aborted (core dumped) == test-journal-importer === [...] autopkgtest [07:17:29]: summary timedatedPASS hostnamedPASS localed-locale PASS localed-x11-keymap PASS logind PASS unit-config PASS storage PASS networkd-test.py PASS build-login PASS boot-and-servicesPASS udev PASS root-unittests FAIL non-zero exit status 134 upstream PASS boot-smoke PASS systemd-fsckdPASS Exit request sent. [...] To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1881947/+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 1909698] Re: new upstream release 2020f
** Changed in: tzdata (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Groovy) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Groovy: New Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
Here's a debdiff for Precise. ** Patch added: "precise.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+attachment/5449825/+files/precise.debdiff -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Groovy: New Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
And here's a trusty debdiff with a bug reference. ** Patch added: "trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+attachment/5449803/+files/trusty.debdiff ** Patch removed: "trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+attachment/5449801/+files/trusty.debdiff -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Groovy: New Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
Attached is a debdiff for Trusty. ** Patch added: "trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+attachment/5449801/+files/trusty.debdiff -- 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/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Xenial: New Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Groovy: New Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909390] Re: package libudev1 245.4-4ubuntu3.3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libudev1/changelog.Debian.gz', which is different from other
> So there should not have been any 32/64-bit conflict; something appears to > have > happened on your system to corrupt the changelog.Debian.gz file, or maybe > mismatched versions of your 32 and 64 libudev1 packages were installed. Apt should be enforcing that the versions of the i386 and amd64 multiarch packages are in sync; so if a different version of libudev1:i386 is installed, this would be a bug in apt. But if the libudev1:i386 comes from a different source than the Ubuntu archive, it could have the same package version but not have the correct contents (in particular, the Ubuntu-specific changelog filtering which is done in Launchpad). To fix up the system once in this state, you may need to do a `sudo rm /usr/share/doc/libudev1/changelog.Debian.gz` and then reinstall libudev1:amd64. But this doesn't guarantee that libudev1:i386 is in a correct state or that it will continue to work correctly on future upgrades; for that you need to figure out the root cause of libudev1:i386's changelog not being in sync. -- 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/1909390 Title: package libudev1 245.4-4ubuntu3.3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libudev1/changelog.Debian.gz', which is different from other instances of package libudev1:amd64 Status in systemd package in Ubuntu: New Bug description: Can't overwrite shared directory ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libudev1 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Dec 26 22:19:09 2020 DpkgTerminalLog: Preparing to unpack .../libudev1_245.4-4ubuntu3.3_amd64.deb ... Unpacking libudev1:amd64 (245.4-4ubuntu3.3) over (245.4-4ubuntu3.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libudev1_245.4-4ubuntu3.3_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libudev1/changelog.Debian.gz', which is different from other instances of package libudev1:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libudev1/changelog.Debian.gz', which is different from other instances of package libudev1:amd64 InstallationDate: Installed on 2020-12-11 (15 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: systemd Title: package libudev1 245.4-4ubuntu3.3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libudev1/changelog.Debian.gz', which is different from other instances of package libudev1:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1909390/+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 1891407] Re: [journalctl --follow] Wi-Fi auto disconnect randomly, unable to fix (updated: including PCIe Bus Error)
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
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/1891407
Title:
[journalctl --follow] Wi-Fi auto disconnect randomly, unable to fix
(updated: including PCIe Bus Error)
Status in network-manager package in Ubuntu:
Invalid
Bug description:
Ubuntu 20.04.01 LTS (newly installed)
(Moved that device from windows 10, didnt had issue in it)
HP 15T-au000 device.
[lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
PCIe Wireless Network Adapter
[lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI
Express Fast Ethernet controller (rev 0a)
DeviceName: Realtek PCIe FE Family Controller
Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet
controller
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe
Wireless Network Adapter
DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be
Wi-Fi key is correct (i can use internet to visit sites, watch videos in
youtube etc) however randomly disconnect and appear window to re-connect
(sometimes constantly disconnect)
No network related change has made (IPv6 disabled through settings)
Only one SSID is in use: Dialog 4G
I ran `journalctl --follow` and below is the log. let me know if
required to provide further details
~Updated~
There also `PCIe Bus Error: severity=Corrected, type=Physical Layer` occur
due that wifi card - RTL8723BE
It usually appear when boot the device (before login screen) and currently i
suppressed that issue by adding `pci=noaer` to grub (alternative pci=nomsi)
I found https://github.com/rtlwifi-linux/rtlwifi_new and
https://github.com/silenoth/rtlwifi_new-extended it contain
'RTL8723BE' however most people had used them due wifi card does not
display or unable connect but i dont have such issue and users have
reported installation issues then didnt consider to put to my machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+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 1910405] [NEW] bluetoothd hangs and cannot be killed
Public bug reported: Hi, When having a bluetooth headphone (JBL Live) connected using the A2DP pulseaudio sink, the output sound suddenly stops during a music streaming of videocall session. Sometimes just disconnecting and reconnecting the headphone works, but some times reconnection is not possible anymore due to the hanging of bluetoothd. Bluetoothd still appears in the processes list, but cannot be killed, neither with "sudo service bluetooth stop" or "kill -9": $ ps afx | grep blue 9597 tty2 Sl+0:01 | \_ gnome-control-center bluetooth 5405 ?Ss 0:00 \_ /usr/lib/bluetooth/obexd 10694 pts/0S+ 0:00 \_ grep blue 20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd All programs keep working normally, only bluetooth is affected as well as the bluetooth settings page. The only solution is a hard reboot. A soft reboot doesn't even work: the systems keeps trying to end the bluetoothd process so one needs to press the power button for a few seconds to terminate the process. $ bluetoothd --version 5.48 $ uname -a Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working nice for over one year now just like previous versions. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1910405 Title: bluetoothd hangs and cannot be killed Status in bluez package in Ubuntu: New Bug description: Hi, When having a bluetooth headphone (JBL Live) connected using the A2DP pulseaudio sink, the output sound suddenly stops during a music streaming of videocall session. Sometimes just disconnecting and reconnecting the headphone works, but some times reconnection is not possible anymore due to the hanging of bluetoothd. Bluetoothd still appears in the processes list, but cannot be killed, neither with "sudo service bluetooth stop" or "kill -9": $ ps afx | grep blue 9597 tty2 Sl+0:01 | \_ gnome-control-center bluetooth 5405 ?Ss 0:00 \_ /usr/lib/bluetooth/obexd 10694 pts/0S+ 0:00 \_ grep blue 20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd All programs keep working normally, only bluetooth is affected as well as the bluetooth settings page. The only solution is a hard reboot. A soft reboot doesn't even work: the systems keeps trying to end the bluetoothd process so one needs to press the power button for a few seconds to terminate the process. $ bluetoothd --version 5.48 $ uname -a Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been working nice for over one year now just like previous versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910405/+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 1910391] [NEW] Lightdm is not working on minimal DE install without recommends
Public bug reported: I tried to install Focal with minimal DE without install recommends and installing lightdm. On debian works "out of the box" on ubuntu not, lightdm fails to start. I saw that issue is because missing a greeter, on debian is correctly as dependencies, on ubuntu packages is instead as recommends, moving from recommends to dependens will solve this. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1910391 Title: Lightdm is not working on minimal DE install without recommends Status in lightdm package in Ubuntu: New Bug description: I tried to install Focal with minimal DE without install recommends and installing lightdm. On debian works "out of the box" on ubuntu not, lightdm fails to start. I saw that issue is because missing a greeter, on debian is correctly as dependencies, on ubuntu packages is instead as recommends, moving from recommends to dependens will solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1910391/+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 1170353] Re: Host names intermittently resolve to 0.0.0.0
It's happened to me a few times on 20.04.1: $ host support.coinjar.com support.coinjar.com has address 0.0.0.0 support.coinjar.com has IPv6 address :: support.coinjar.com is an alias for coinjar.zendesk.com. coinjar.zendesk.com mail is handled by 10 mail-pod-25.int.zendesk.com. $ sudo resolvectl flush-caches $ host support.coinjar.com support.coinjar.com has address 0.0.0.0 support.coinjar.com has IPv6 address :: support.coinjar.com is an alias for coinjar.zendesk.com. coinjar.zendesk.com mail is handled by 10 mail-pod-25.int.zendesk.com. $ dig support.coinjar.com ; <<>> DiG 9.16.1-Ubuntu <<>> support.coinjar.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12759 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;support.coinjar.com. IN A ;; ANSWER SECTION: support.coinjar.com.34 IN A 0.0.0.0 ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Jan 06 20:23:28 AEDT 2021 ;; MSG SIZE rcvd: 64 Then 2 minutes later the problem resolves itself: $ dig support.coinjar.com ; <<>> DiG 9.16.1-Ubuntu <<>> support.coinjar.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64605 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;support.coinjar.com. IN A ;; ANSWER SECTION: support.coinjar.com.151 IN CNAME coinjar.zendesk.com. coinjar.zendesk.com.900 IN A 104.16.51.111 coinjar.zendesk.com.900 IN A 104.16.53.111 ;; Query time: 68 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Jan 06 20:25:31 AEDT 2021 ;; MSG SIZE rcvd: 110 Nothing in /var/log/syslog or systemd-resolved's systemd log. -- 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/1170353 Title: Host names intermittently resolve to 0.0.0.0 Status in network-manager package in Ubuntu: Invalid Bug description: About 5% of DNS queries resolve to 0.0.0.0. A couple of times an hour during normal browsing, Firefox resolves a domain to 0.0.0.0. Opening the same site in Chrome has a 50% chance of it working, then it normally works after a few reloads. Thunderbird has also occasionally resolved googlemail.com to 0.0.0.0. Domains include google.com, wikipedia.org, harvestapp.com and many more. I couldn't reproduce this with dig/nslookup for a while, but after 5 minutes of (re)trying random domains) did: $ dig mail.google.com ; <<>> DiG 9.8.1-P1 <<>> mail.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22905 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;mail.google.com. IN A ;; ANSWER SECTION: mail.google.com. 60 IN A 0.0.0.0 ;; Query time: 0 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Thu Apr 18 13:57:04 2013 ;; MSG SIZE rcvd: 49 Note the "0 msec", so I'm pretty sure this is dnsmasq's local cache. Using Xubuntu 12.10, NetworkManager 0.9.6.0, Dnsmasq 2.63rc6. NetworkManager has DNS servers set to "8.8.8.8, 8.8.4.4" (also tried setting it to my router's DNS server, with no effect). /etc/resolve.conf just has "nameserver 127.0.1.1" dnsmasq is currently running: /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind- interfaces --pid-file=/var/run/sendsigs.omit.d/network- manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run /nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec --enable- dbus=org.freedesktop.NetworkManager.dnsmasq --conf- dir=/etc/NetworkManager/dnsmasq.d ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Apr 18 14:27:33 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-11 (97 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IpRoute: default via 10.0.0.1 dev eth0 proto static 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.10 metric 1 169.254.0.0/16 dev eth0 scope
[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak
The attachment "Debdiff for librelp on Groovy" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
leads to file descriptor leak
Status in librelp package in Ubuntu:
In Progress
Status in rsyslog package in Ubuntu:
Fix Released
Status in librelp source package in Focal:
In Progress
Status in rsyslog source package in Focal:
Won't Fix
Status in librelp source package in Groovy:
In Progress
Status in rsyslog source package in Groovy:
Fix Released
Status in librelp source package in Hirsute:
In Progress
Status in rsyslog source package in Hirsute:
Fix Released
Bug description:
[Impact]
In recent versions of rsyslog and librelp, the imrelp module leaks
file descriptors due to a bug where it does not correctly close
sockets, and instead, leaves them in the CLOSE_WAIT state.
This causes rsyslogd on busy servers to eventually hit the limit of
maximum open files allowed, which locks rsyslogd up until it is
restarted.
A workaround is to restart rsyslogd every month or so to manually
close all of the open sockets.
Only users of the imrelp module are affected, and not rsyslog users in
general.
[Testcase]
Install the rsyslog-relp module like so:
$ sudo apt install rsyslog rsyslog-relp
Next, generate a working directory, and make a config file that loads
the relp module.
$ sudo mkdir /workdir
$ cat << EOF >> ./spool.conf
\$LocalHostName spool
\$AbortOnUncleanConfig on
\$PreserveFQDN on
global(
workDirectory="/workdir"
maxMessageSize="256k"
)
main_queue(queue.type="Direct")
module(load="imrelp")
input(
type="imrelp"
name="imrelp"
port="601"
ruleset="spool"
MaxDataSize="256k"
)
ruleset(name="spool" queue.type="direct") {
}
# Just so rsyslog doesn't whine that we do not have outputs
ruleset(name="noop" queue.type="direct") {
action(
type="omfile"
name="omfile"
file="/workdir/spool.log"
)
}
EOF
Verify that the config is valid, then start a rsyslog server.
$ sudo rsyslogd -f ./spool.conf -N9
$ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid
Fetch the rsyslogd PID and check for open files.
$ RLOGPID=$(cat /workdir/rsyslogd.pid)
$ sudo ls -l /proc/$RLOGPID/fd
total 0
lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'
We have 3 sockets open by default. Next, use netcat to open 100
connections:
$ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done
Now check for open file descriptors, and there will be an extra 100 sockets
in the list:
$ sudo ls -l /proc/$RLOGPID/fd
https://paste.ubuntu.com/p/f6NQVNbZcR/
We can check the state of these sockets with:
$ ss -t
https://paste.ubuntu.com/p/7Ts2FbxJrg/
The listening sockets will be in CLOSE-WAIT, and the netcat sockets
will be in FIN-WAIT-2.
$ ss -t | grep CLOSE-WAIT | wc -l
100
If you install the test package available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf299578-test
When you open connections with netcat, these will be closed properly,
and the file descriptor leak will be fixed.
[Where problems could occur]
If a regression were to occur, it would be limited to users of the
imrelp module, which is a part of the rsyslogd-relp package, and
depends on librelp.
rsyslog-relp is not part of a default installation of rsyslog, and is
opt in by changing a configuration file to enable imrelp.
The changes to rsyslog implement a testcase which exercises the
problematic code to ensure things are working as expected, and should
run during autopkgtest time.
[Other]
Upstream bug list:
https://github.com/rsyslog/rsyslog/issues/4350
https://github.com/rsyslog/rsyslog/issues/4005
https://github.com/rsyslog/librelp/issues/188
https://github.com/rsyslog/librelp/pull/193
The following commits fix the problem:
rsyslogd
commit baee0bd5420649329793746f0daf87c4f59fe6a6
Author: Andre lorbach
Date: Thu Apr 9 13:00:35 2020 +0200
Subject:
[Touch-packages] [Bug 1905467] Re: [USB-Audio - Logitech Wireless Headset, playback] volume slider - sound audible only from 50% to 100% of the slider position
I see the same behavior. -- 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/1905467 Title: [USB-Audio - Logitech Wireless Headset, playback] volume slider - sound audible only from 50% to 100% of the slider position Status in alsa-driver package in Ubuntu: New Bug description: After establishing connection with Logitech H800 Wireless Headset via USB Dongle, the system sound has to be set at the minimum of 50% of the slider for the sound in the headphones to be audible. Below the 50% volume slider position the sound is completely muted. Expected behaviour: Volume slider properly changing the sound level from 0% to 100% with the sound being muted at 0% and at maximum level at 100%. System: Ubuntu 20.04.1 LTS alsa-driver: k5.4.0-54-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: maciej 6716 F pulseaudio /dev/snd/pcmC3D0p: maciej 6716 F...m pulseaudio /dev/snd/controlC0: maciej 6716 F pulseaudio /dev/snd/controlC1: maciej 6716 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 21:29:56 2020 InstallationDate: Installed on 2020-06-22 (154 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: H600 [Wireless Headset] - Logitech Wireless Headset Symptom_PulseAudioLog: lis 22 12:33:32 y510p-ubuntu dbus-daemon[1500]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=125 pid=1940 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") lis 22 12:33:34 y510p-ubuntu pulseaudio[1940]: Failed to find a working profile. lis 22 12:33:34 y510p-ubuntu pulseaudio[1940]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. lis 24 09:41:02 y510p-ubuntu pulseaudio[1940]: Failed to create sink input: sink is suspended. lis 24 10:30:54 y510p-ubuntu pulseaudio[1940]: Failed to create sink input: sink is suspended. Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - Logitech Wireless Headset, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 1/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN47WW(V3.08) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 3193STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN47WW(V3.08):bd1/30/2015:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr3193STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1905467/+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 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak
The test package fixes the issue for me.
--
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/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
leads to file descriptor leak
Status in librelp package in Ubuntu:
In Progress
Status in rsyslog package in Ubuntu:
Fix Released
Status in librelp source package in Focal:
In Progress
Status in rsyslog source package in Focal:
Won't Fix
Status in librelp source package in Groovy:
In Progress
Status in rsyslog source package in Groovy:
Fix Released
Status in librelp source package in Hirsute:
In Progress
Status in rsyslog source package in Hirsute:
Fix Released
Bug description:
[Impact]
In recent versions of rsyslog and librelp, the imrelp module leaks
file descriptors due to a bug where it does not correctly close
sockets, and instead, leaves them in the CLOSE_WAIT state.
This causes rsyslogd on busy servers to eventually hit the limit of
maximum open files allowed, which locks rsyslogd up until it is
restarted.
A workaround is to restart rsyslogd every month or so to manually
close all of the open sockets.
Only users of the imrelp module are affected, and not rsyslog users in
general.
[Testcase]
Install the rsyslog-relp module like so:
$ sudo apt install rsyslog rsyslog-relp
Next, generate a working directory, and make a config file that loads
the relp module.
$ sudo mkdir /workdir
$ cat << EOF >> ./spool.conf
\$LocalHostName spool
\$AbortOnUncleanConfig on
\$PreserveFQDN on
global(
workDirectory="/workdir"
maxMessageSize="256k"
)
main_queue(queue.type="Direct")
module(load="imrelp")
input(
type="imrelp"
name="imrelp"
port="601"
ruleset="spool"
MaxDataSize="256k"
)
ruleset(name="spool" queue.type="direct") {
}
# Just so rsyslog doesn't whine that we do not have outputs
ruleset(name="noop" queue.type="direct") {
action(
type="omfile"
name="omfile"
file="/workdir/spool.log"
)
}
EOF
Verify that the config is valid, then start a rsyslog server.
$ sudo rsyslogd -f ./spool.conf -N9
$ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid
Fetch the rsyslogd PID and check for open files.
$ RLOGPID=$(cat /workdir/rsyslogd.pid)
$ sudo ls -l /proc/$RLOGPID/fd
total 0
lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'
We have 3 sockets open by default. Next, use netcat to open 100
connections:
$ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done
Now check for open file descriptors, and there will be an extra 100 sockets
in the list:
$ sudo ls -l /proc/$RLOGPID/fd
https://paste.ubuntu.com/p/f6NQVNbZcR/
We can check the state of these sockets with:
$ ss -t
https://paste.ubuntu.com/p/7Ts2FbxJrg/
The listening sockets will be in CLOSE-WAIT, and the netcat sockets
will be in FIN-WAIT-2.
$ ss -t | grep CLOSE-WAIT | wc -l
100
If you install the test package available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf299578-test
When you open connections with netcat, these will be closed properly,
and the file descriptor leak will be fixed.
[Where problems could occur]
If a regression were to occur, it would be limited to users of the
imrelp module, which is a part of the rsyslogd-relp package, and
depends on librelp.
rsyslog-relp is not part of a default installation of rsyslog, and is
opt in by changing a configuration file to enable imrelp.
The changes to rsyslog implement a testcase which exercises the
problematic code to ensure things are working as expected, and should
run during autopkgtest time.
[Other]
Upstream bug list:
https://github.com/rsyslog/rsyslog/issues/4350
https://github.com/rsyslog/rsyslog/issues/4005
https://github.com/rsyslog/librelp/issues/188
https://github.com/rsyslog/librelp/pull/193
The following commits fix the problem:
rsyslogd
commit baee0bd5420649329793746f0daf87c4f59fe6a6
Author: Andre lorbach
Date: Thu Apr 9 13:00:35 2020 +0200
Subject: testbench: Add test for imrelp to check broken session handling.
Link:
https://github.com/rsyslog/rsyslog/commit/baee0bd5420649329793746f0daf87c4f59fe6a6
librelp
===
commit 7907c9c57f6ed94c8ce5a4e63c3c4e019f71cff0
Author: Andre lorbach
Date: Mon May 11 14:59:55 2020 +0200
Subject: fix memory leak on session break.
Link:
https://github.com/rsyslog/librelp/commit/7907c9c57f6ed94c8ce5a4e63c3c4e019f71cff0
commit
