[Touch-packages] [Bug 1876055] Re: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness
systemd-242-7ubuntu3.11 passes autopkgtest for eoan/i386 and resolves the FTBFS for arm64 - https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-ubuntu-security-proposed- ppa/eoan/i386/s/systemd/20200615_102850_82300@/log.gz @jdstrand can you please sponsor this to -proposed in the archive? (unless I am confused about the next steps of the process for this - if so, please let me know what should happen next to progress this). -- 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/1876055 Title: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness Status in libseccomp package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in libseccomp source package in Xenial: Fix Committed Status in libseccomp source package in Bionic: Fix Committed Status in libseccomp source package in Eoan: Fix Committed Status in systemd source package in Eoan: New Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: [Impact] The combination of snap-confine and snap-seccomp from snapd uses libseccomp to filter various system calls for confinement. The current version in eoan/bionic/xenial (2.4.1) is missing knowledge of various system calls for various architectures. As such this causes strange issues like python snaps segfaulting (https://github.com/snapcore/core20/issues/48) or the inadvertent denial of system calls which should be permitted by the base policy (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237). libseccomp in groovy is using the latest upstream base release (2.4.3) plus it includes a patch to add some missing aarch64 system calls (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633). SRUing this version back to older stable releases allows libseccomp to operate correctly on all supported architectures. Included as part of this SRU are test-suite reliability improvements - currently the xenial libseccomp package overrides test-suite failures at build time to ignore failures. This masks the fact that on ppc64el and s390x there are currently test suite failures at build time for xenial - these failures occur since libseccomp now includes knowledge of system calls for these architectures but which the linux-libc-dev package for xenial does not actually define (since this is based of the 4.4 kernel in xenial whereas libseccomp 2.4.1 in xenial has knowledge of all system calls up to 5.4). In this SRU I have instead fixed the test suite failures for xenial by including a local (test-suite specific) set of architecture specific kernel headers from the linux-libc-dev in focal for all releases. These are just the headers which define the system call numbers for each architecture *and* these are added to tests/include/$ARCH in the source package (and tests/Makefile.am is then updated to include these new headers only). As such this ensures the actual build of libseccomp or any of the tools does not reference these headers. This allows the test suite in libseccomp to then be aware of theses system calls and so all unit tests for all architectures now pass. In any future updates for libseccomp to add new system calls, we can then similarly update these local headers to ensure the unit tests continue to work as expected. [Test Case] libseccomp includes a significant unit test suite that is run during the build and as part of autopkgtests. To verify the new aarch64 system calls are resolved as expected the scmp_sys_resolver command can be used as well: $ scmp_sys_resolver -a aarch64 getrlimit 163 (whereas in the current version in focal this returns -10180 as libseccomp was not aware of this system-call at compile-time). As part of this SRU, the test suite in libseccomp has been patched to include a local copy of the architecture-specific kernel headers from the 5.4 kernel in focal *for all releases*, so that all system calls which are defined for the 5.4 kernel are known about *for the libseccomp test suite*. This allows all unit tests to pass on older releases as well and defaults the build to fail on unit test failures (whereas currently in xenial this has been overridden to ignore failures). [Regression Potential] This has a low regression potential due to significant testing with many packages that depend on libseccomp (lxc, qemu, snapd, apt, man etc) and none have shown any regression using this new version. The re-enablement of build failure on test failure at build time also ensures that we can reliably detect FTBFS issues in the future. No symbols have been removed (or
[Touch-packages] [Bug 1615685] Re: systemd-analyze stats for kernel startup time looks suspect
Has there been any progress on getting rid of initrd or adding stats in the past 2 years? Ubuntu 20.04 still uses initrd and a huge one at that, so the plan to get rid of it seemed to have failed, but without systemd so there are still no timings like with other dists. Having separate stats breakdown for firmware, loader, kernel, and initrd would be useful. -- 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/1615685 Title: systemd-analyze stats for kernel startup time looks suspect Status in systemd package in Ubuntu: New Bug description: I've instrumented a kernel so I can clearly see when processes start and exit, this allows me to see when exactly the kernel has handed off control to userspace. The time the kernel actually takes to initialize compared to the time systemd-analyze reports are different. $ systemd-analyze Startup finished in 16.878s (kernel) + 43.152s (userspace) = 1min 30ms For example: [2.286330] Freeing unused kernel memory: 1532K (b1755000 - b18d4000) [2.296300] Write protecting the kernel read-only data: 12288k [2.304356] Freeing unused kernel memory: 1872K (9d9c6e42c000 - 9d9c6e60) [2.317659] Freeing unused kernel memory: 1208K (9d9c6e8d2000 - 9d9c6ea0) [2.344896] x86/mm: Checked W+X mappings: passed, no W+X pages found. [2.368095] exec: 1 (swapper/0) -> /init [2.377284] _do_fork: 1 init [2.381933] exit 53 init [2.386444] _do_fork: 1 init [2.390741] exit 54 init [2.394899] _do_fork: 1 init and we have the initramfs initialization occurring, and then finally systemd starts: [ 16.571630] exec: 1 (run-init) -> /sbin/init [ 17.287342] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [ 17.307892] systemd[1]: Detected virtualization microsoft. [ 17.314765] systemd[1]: Detected architecture x86-64. [ 17.421589] systemd[1]: Set hostname to . So it seems that systemd is accounting initramfs time in the kernel time stats. It would be preferable to be able to report the kernel init time, the initramfs time and the userspace time rather just kernel + userspace. As it stands, the kernel passed off control to systemd at 16.571630 seconds, so I have no no idea why systemd is reporting 16.878 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
@Michael, could you tell us what option you changed back to fix the issue exactly? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879438] Re: bluetooth file transfer via bluetooth UI is too slow
Thanks! ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Changed in: bluez (Ubuntu) Status: New => Triaged ** Also affects: bluez via https://bugzilla.kernel.org/show_bug.cgi?id=208227 Importance: Unknown Status: Unknown -- 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/1879438 Title: bluetooth file transfer via bluetooth UI is too slow Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: Triaged Bug description: OS: Ubuntu 20.04 Kernel: 5.4.0-31-generic When using the UI to connect and transfer the file form one machine to another machine, BASIC mode is getting selected in the L2CAP configuration and continuous scan is not going on in both sides. the L2CAP MTU size is also in 672, which is very small. Even with the patch applied by Intel, it does not increase the TPT because the UI always selects BASIC mode. Sample File transfer duration: sending - (8MB) 5min 18s sending - (12MB) 7min36s receiving - (8MB) 4min 8s receiving - (12MB) 5min 48s **This issue was also observed in Ubuntu 18.04 OS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 14:46:11 2020 InstallationDate: Installed on 2020-05-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9SITR39 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=6716936f-20b8-4840-8a75-00f4279d9062 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR39 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR39:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR39:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR39 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: D8:3B:BF:7A:E4:22 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22494299 acl:63654 sco:0 events:77112 errors:0 TX bytes:45158198 acl:65574 sco:0 commands:7661 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1879438/+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 105101] Re: the "lock screen" thing is slow to appear after opening the lid
Present on Ubuntu 18.04.4 LTS, GNOME 3.28.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/105101 Title: the "lock screen" thing is slow to appear after opening the lid Status in GNOME Screensaver: Invalid Status in pam package in Ubuntu: Incomplete Status in gnome-screensaver package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver This is on Ubuntu Feisty, up to date, running on a Dell Latitude D620 laptop (Intel video). I have the computer set up to lock the screen when I close the lid. (This mostly works.) When I open the lid, though, there's almost always a delay before the "unlock" window appears. I can open the lid, type the password, and still have to wait three-four seconds, sometimes more, before the "enter password" window appears. It receives the already-typed password and then goes away in a second or so. Note that the screen turns on pretty much instantly (the back-light is usually on by the time the screen is up). Also, the laptop is NOT in stand-by or anything, it's running normally. The password-entry box should appear instantly (by the time the back- light turns on) and disappear the moment enter is pressed. After all, it's an extremely resource-light application. (It's OK if the desktop takes a bit to redraw after; that's a potentially slow operation. But just showing the password box on a black screen should be very quick.) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/105101/+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 1884008] Re: network manager prefers further away AP when there are multiple APs
Thank you for your bug report, could you report this upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/ ? ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- 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/1884008 Title: network manager prefers further away AP when there are multiple APs Status in network-manager package in Ubuntu: New Bug description: I'm on Ubuntu 20.04. My Wifi set-up has multiple access points throughout my home, and they all have the same SSID. It doesn't matter where I am in my home though, network manager always connects to one particular AP. If I list all the access points with `nmcli dev wifi list` I can see that it even picks that one access point if it is the farthest away one: 76:83:C2:BB:34:2A -- Infra 36405 Mbit/s 97 ▂▄▆█ WPA2 74:83:C2:BB:34:2A my_access_point Infra 36405 Mbit/s 95 ▂▄▆█ WPA2 74:83:C2:BA:34:2A my_access_point Infra 1 195 Mbit/s 94 ▂▄▆█ WPA2 76:83:C2:BA:34:2A -- Infra 1 195 Mbit/s 94 ▂▄▆█ WPA2 B6:FB:E4:45:CA:82 -- Infra 157 405 Mbit/s 44 ▂▄__ WPA2 * B4:FB:E4:45:CA:82 my_access_point Infra 157 405 Mbit/s 44 ▂▄__ WPA2 B6:FB:E4:44:CA:82 -- Infra 11195 Mbit/s 42 ▂▄__ WPA2 B4:FB:E4:44:CA:82 my_access_point Infra 11195 Mbit/s 40 ▂▄__ WPA2 It is true that if I change the BSSID field in the wifi settings I can get it to connect to a particular one, but that is not sufficient. I have a laptop, and if I move around my home I need it to connect to the closest one, and switching manually to whichever one is closest is not practical. I can't even create multiple entries for each BSSID in the list of networks, if I try many different networks appear with the same name and random numbers and I can't even label them. This is network manager version 1.22.10-1ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1884008/+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 1882042] Re: [SRU] Linux, Ubuntu, 18.4, CI, OLP15, PRTS, Audio/video is out of sync/lag when enter Suspend during playback
@Hui, thanks for the work, do you want that bionic update uploaded now or should we try to include other pending fixes still there? ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882042 Title: [SRU] Linux,Ubuntu,18.4,CI,OLP15,PRTS, Audio/video is out of sync/lag when enter Suspend during playback Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: [Impact] Users reported the audio and video is out of sync when entering suspend during playback on bionic. [Fix] The mainline pulseaudio already has the fix for this issue, and the fix is already in the eoan, focal and groovy, but it is not in the bionic. [Test Case] open a online video on the firefox, while it is playing, suspend the system, wait for 30 seconds, resume the system, the audio and video is still on the sync. [Regression Risk] Low, these 2 patches are already in the mainline pulseaudio, and already in the eoan, focal and groovy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882042/+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 1876055] Re: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness
I see this libseccomp upload has been built in the security proposed PPA - does it mean it should go into both -updates and -security? -- 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/1876055 Title: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness Status in libseccomp package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in libseccomp source package in Xenial: Fix Committed Status in libseccomp source package in Bionic: Fix Committed Status in libseccomp source package in Eoan: Fix Committed Status in systemd source package in Eoan: New Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: [Impact] The combination of snap-confine and snap-seccomp from snapd uses libseccomp to filter various system calls for confinement. The current version in eoan/bionic/xenial (2.4.1) is missing knowledge of various system calls for various architectures. As such this causes strange issues like python snaps segfaulting (https://github.com/snapcore/core20/issues/48) or the inadvertent denial of system calls which should be permitted by the base policy (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237). libseccomp in groovy is using the latest upstream base release (2.4.3) plus it includes a patch to add some missing aarch64 system calls (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633). SRUing this version back to older stable releases allows libseccomp to operate correctly on all supported architectures. Included as part of this SRU are test-suite reliability improvements - currently the xenial libseccomp package overrides test-suite failures at build time to ignore failures. This masks the fact that on ppc64el and s390x there are currently test suite failures at build time for xenial - these failures occur since libseccomp now includes knowledge of system calls for these architectures but which the linux-libc-dev package for xenial does not actually define (since this is based of the 4.4 kernel in xenial whereas libseccomp 2.4.1 in xenial has knowledge of all system calls up to 5.4). In this SRU I have instead fixed the test suite failures for xenial by including a local (test-suite specific) set of architecture specific kernel headers from the linux-libc-dev in focal for all releases. These are just the headers which define the system call numbers for each architecture *and* these are added to tests/include/$ARCH in the source package (and tests/Makefile.am is then updated to include these new headers only). As such this ensures the actual build of libseccomp or any of the tools does not reference these headers. This allows the test suite in libseccomp to then be aware of theses system calls and so all unit tests for all architectures now pass. In any future updates for libseccomp to add new system calls, we can then similarly update these local headers to ensure the unit tests continue to work as expected. [Test Case] libseccomp includes a significant unit test suite that is run during the build and as part of autopkgtests. To verify the new aarch64 system calls are resolved as expected the scmp_sys_resolver command can be used as well: $ scmp_sys_resolver -a aarch64 getrlimit 163 (whereas in the current version in focal this returns -10180 as libseccomp was not aware of this system-call at compile-time). As part of this SRU, the test suite in libseccomp has been patched to include a local copy of the architecture-specific kernel headers from the 5.4 kernel in focal *for all releases*, so that all system calls which are defined for the 5.4 kernel are known about *for the libseccomp test suite*. This allows all unit tests to pass on older releases as well and defaults the build to fail on unit test failures (whereas currently in xenial this has been overridden to ignore failures). [Regression Potential] This has a low regression potential due to significant testing with many packages that depend on libseccomp (lxc, qemu, snapd, apt, man etc) and none have shown any regression using this new version. The re-enablement of build failure on test failure at build time also ensures that we can reliably detect FTBFS issues in the future. No symbols have been removed (or added) with this update in version so there is no chance of regression due to ABI change etc. In the past, the security team has performed more significant version upgrades for libseccomp (2.2, 2.3, 2.4) -> 2.4.1 without major incident. In the case of *this* SRU, we are only doing a micro-version upgrade from 2.4.1 to 2.4.3 so this carrie
[Touch-packages] [Bug 1882042] Re: [SRU] Linux, Ubuntu, 18.4, CI, OLP15, PRTS, Audio/video is out of sync/lag when enter Suspend during playback
@Seb, No other pending fixes so far, please upload now. thx. -- 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/1882042 Title: [SRU] Linux,Ubuntu,18.4,CI,OLP15,PRTS, Audio/video is out of sync/lag when enter Suspend during playback Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: [Impact] Users reported the audio and video is out of sync when entering suspend during playback on bionic. [Fix] The mainline pulseaudio already has the fix for this issue, and the fix is already in the eoan, focal and groovy, but it is not in the bionic. [Test Case] open a online video on the firefox, while it is playing, suspend the system, wait for 30 seconds, resume the system, the audio and video is still on the sync. [Regression Risk] Low, these 2 patches are already in the mainline pulseaudio, and already in the eoan, focal and groovy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882042/+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 1876693] Update Released
The verification of the Stable Release Update for gobject-introspection has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1876693 Title: [SRU] New stable release 1.64.1 Status in gobject-introspection package in Ubuntu: Fix Released Status in gobject-introspection source package in Focal: Fix Released Bug description: [ Description ] GNOME upstream have released a new stable version of gobject- introspection. Changes: 1.64.1 - 2020-04-05 --- * Replace calls to deprecated xml.etree.cElementTree removed in Python 3.9 :mr:`202` (:user:`Stephen Gallagher `) * gimarshallingtests: Use g_assert_cmpfloat_with_epsilon. Fixes tests on some architectures :mr:`200` (:user:`Iain Lane `) [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. Do this: - Install the update, smoke test some of the reverse depends (apt rdepends libgirepository-1.0-1 and more importantly the indirect rdepends via python3-gi) - Run "reverse-depends -b src:gobject-introspection" and test rebuild a few of them [ Regression potential ] g-i being broken will break pretty much the whole desktop, but you'd know that quite fast. The .py changes, if they're wrong or bad, could break the build of r -build-deps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gobject-introspection/+bug/1876693/+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 1876693] Re: [SRU] New stable release 1.64.1
This bug was fixed in the package gobject-introspection - 1.64.1-1~ubuntu20.04.1 --- gobject-introspection (1.64.1-1~ubuntu20.04.1) focal; urgency=medium * Backport new stable release from unstable / groovy. (LP: #1876693) * control, gbp.conf: Update for focal gobject-introspection (1.64.1-1) unstable; urgency=medium * Team upload * New upstream release - d/p/gimarshallingtests-Use-g_assert_cmpfloat_with_epsilon.patch: Drop patch, applied upstream -- Iain Lane Mon, 04 May 2020 11:13:36 +0100 ** Changed in: gobject-introspection (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1876693 Title: [SRU] New stable release 1.64.1 Status in gobject-introspection package in Ubuntu: Fix Released Status in gobject-introspection source package in Focal: Fix Released Bug description: [ Description ] GNOME upstream have released a new stable version of gobject- introspection. Changes: 1.64.1 - 2020-04-05 --- * Replace calls to deprecated xml.etree.cElementTree removed in Python 3.9 :mr:`202` (:user:`Stephen Gallagher `) * gimarshallingtests: Use g_assert_cmpfloat_with_epsilon. Fixes tests on some architectures :mr:`200` (:user:`Iain Lane `) [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. Do this: - Install the update, smoke test some of the reverse depends (apt rdepends libgirepository-1.0-1 and more importantly the indirect rdepends via python3-gi) - Run "reverse-depends -b src:gobject-introspection" and test rebuild a few of them [ Regression potential ] g-i being broken will break pretty much the whole desktop, but you'd know that quite fast. The .py changes, if they're wrong or bad, could break the build of r -build-deps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gobject-introspection/+bug/1876693/+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 1875796] Re: HP Envy 5530 printer/scanner does not work
Since having installed Kubuntu 20.04, and having ONLY one printer/scanner attached to our home network (Envy 5542), I see multiple printers with names with "Envy" in it, but with different extra characters. It isn't at all clear why it is so difficult to have Ubuntu (and Windows 10 of other people on our network) see multiple Envy's. In Windows 10 the printer often (but not always) doesn't work, OR only prints one-sided. In Ubuntu it usually works, but it keeps being confusing: I see at least 3 "versions" of Envy on the printer-list. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1875796 Title: HP Envy 5530 printer/scanner does not work Status in cups package in Ubuntu: Confirmed Bug description: ubuntu 20.04 LTS see troubleshoot.txt please ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 08:15:00 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for ENVY_5530_series_CN4A5310HJ067B_: implicitclass://ENVY_5530_series_CN4A5310HJ067B_/ device for HP-ENVY-5530-series: hp:/usb/ENVY_5530_series?serial=CN4A5310HJ067B Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52e Logitech, Inc. MK260 Wireless Combo Receiver Bus 001 Device 003: ID 03f0:c311 HP, Inc ENVY 5530 series Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-ENVY-5530-series.ppd', '/etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-ENVY-5530-series.ppd: Permission denied grep: /etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd: Permission denied ProcEnviron: LANGUAGE=nl_BE:nl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=77c5fdfc-4b0d-48ce-93d9-8aba51f17f9b ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 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.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2: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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1875796/+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 1882034] Re: cannot start X session with NIS account
This is a very serious bug. I tested with couple computers to which only addition after standard installation was NIS and NFS and the error is always there. Local users can login to gdm3 session but NIS users cannot and the error is always the same. If this is a single issue I could live with it replacing gdm3 with lightdm but I am sure this will create other problems and I also found that the NIS users cannot open teamviewer session. -- 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/1882034 Title: cannot start X session with NIS account Status in systemd package in Ubuntu: Incomplete Bug description: When login with a NIS account, X does not start, or more precisely it starts and exits immediately. Only errors in logs is: (EE) systemd-logind: failed to get session: PID 4335 does not belong to any known session X11/gdm login works fine with local accounts. SSH/terminal console login with NIS accounts works fine. /etc/X11/Xwrapper.config: allowed_users=anybody I've seen several reports of such problems under other versions (eg 19.10), but no working solutions was found. It seems that the problem is the same with lightdm. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 08:59:25 2020 InstallationDate: Installed on 2019-11-26 (190 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882034/+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 1407928] Re: [phone] Does not auto-switch to available, known WiFi
** Changed in: network-manager (Ubuntu) Assignee: Tony Espy (awe) => (unassigned) -- 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/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+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 1835660] Re: initramfs unpacking failed
Given that the change to the compression format is one of the headline features of Ubuntu 20, and that Ubuntu 20 is a LTS release (and thus, for one thing, a release upon which other Linux distributions are based) I am surprised that this problem made it into the final release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 I am experiencing this issue as well, but don't know how to extract the 19.10 default.pa from the .deb package. Can someone who has successfully applied this solution please post which lines they changed/added? -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 @David is it sustainable in your case and works also after a power down of the machine? unfortunately, in my case it only works when I first boot ubuntu 19.10 via live iso and reboot into installed ubuntu 20.04. however, after a complete power down my 20.04 fails back to not working hsp/hfp mode. -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1884079] [NEW] unmkinitramfs in initramfs-tools-core doesn't fully extract an initrd in bionic
Public bug reported: I am running Ubuntu 18.04.4 I am looking at the initrd found in the desktop live cd (/casper/initrd). If you execute `binwalk initrd`, binwalk informs that the initrd file contains 2 cpio archives and a lzma archive The first cpio archive is supposed to contain kernel/x86/microcode/AuthenticAMD.bin The second cpio archive is supposed to contain kernel/x86/microcode/GenuineIntel.bin The third file is a LZMA compressed data Now, if you execute `unmkinitramfs /casper/initrd new- directory` , you will see 2 directories, "early" and "main". "early" has the AuthenticAMD.bin, which means it corresponds to the first cpio. "main" is the actual initial ram disk file system, which comes from the LZMA compressed data. What I expect to see is also the GenuineIntel.bin firmware. `binwalk` says it's there, but `unmkinitramfs` is not able to extract it out. Why? I see binwalk is at version 2.1.1-16, while initramfs-tools-core (which provides unmkinitramfs) is at version 0.130ubuntu3.9. How do I extract the ubuntu 18 initramfs and get all the contents that binwalk is able to see? ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: initrd ** Summary changed: - unmkinitramfs in initramfs-tools-core doesn't fully extract an initrd + unmkinitramfs in initramfs-tools-core doesn't fully extract an initrd in bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1884079 Title: unmkinitramfs in initramfs-tools-core doesn't fully extract an initrd in bionic Status in initramfs-tools package in Ubuntu: New Bug description: I am running Ubuntu 18.04.4 I am looking at the initrd found in the desktop live cd (/casper/initrd). If you execute `binwalk initrd`, binwalk informs that the initrd file contains 2 cpio archives and a lzma archive The first cpio archive is supposed to contain kernel/x86/microcode/AuthenticAMD.bin The second cpio archive is supposed to contain kernel/x86/microcode/GenuineIntel.bin The third file is a LZMA compressed data Now, if you execute `unmkinitramfs /casper/initrd new- directory` , you will see 2 directories, "early" and "main". "early" has the AuthenticAMD.bin, which means it corresponds to the first cpio. "main" is the actual initial ram disk file system, which comes from the LZMA compressed data. What I expect to see is also the GenuineIntel.bin firmware. `binwalk` says it's there, but `unmkinitramfs` is not able to extract it out. Why? I see binwalk is at version 2.1.1-16, while initramfs-tools-core (which provides unmkinitramfs) is at version 0.130ubuntu3.9. How do I extract the ubuntu 18 initramfs and get all the contents that binwalk is able to see? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1884079/+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 1884082] [NEW] package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Popped up just like dat. Had boot problems just befo dat du 2 2 less space. Keep up da gud work. Peace! Ps: sry fo ma dumb langauge. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cellardoor 1500 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jun 17 12:16:57 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-28 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: LENOVO 4243W4K ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2115cb1b-ab29-42d1-8560-2ded1bfc06c3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: initramfs-tools Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET65WW (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243W4K dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET65WW(1.45):bd05/14/2015:svnLENOVO:pn4243W4K:pvrThinkPadT520:rvnLENOVO:rn4243W4K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 4243W4K dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1884082 Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Popped up just like dat. Had boot problems just befo dat du 2 2 less space. Keep up da gud work. Peace! Ps: sry fo ma dumb langauge. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cellardoor 1500 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jun 17 12:16:57 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-28 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: LENOVO 4243W4K ProcFB: 0 i915drmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed
All LXD virtual machines are hitting this too. Run: - lxc launch images:ubuntu/focal/cloud f1 && lxc console f1 And you'll see it show that message. As mentioned above, boot then still goes ahead and you get a login prompt, but as that may not always be the case. For example in linux-kvm, that fallback mechanism doesn't appear to work and we instead get a kernel panic unless we've manually modified the initrd to be gzip: https://bugs.launchpad.net/cloud-images/+bug/1873809 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1884082] Re: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1884082 Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Popped up just like dat. Had boot problems just befo dat du 2 2 less space. Keep up da gud work. Peace! Ps: sry fo ma dumb langauge. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cellardoor 1500 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jun 17 12:16:57 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-28 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: LENOVO 4243W4K ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2115cb1b-ab29-42d1-8560-2ded1bfc06c3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: initramfs-tools Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET65WW (1.45 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243W4K dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET65WW(1.45):bd05/14/2015:svnLENOVO:pn4243W4K:pvrThinkPadT520:rvnLENOVO:rn4243W4K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 4243W4K dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1884082/+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 1879206] Re: cups hplip not install printer
I believe this bug affects me, also, but I have a different printer, and I get a different message. I have posted my issue here: https://bugs.launchpad.net/hplip/+bug/1884084 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1884086] [NEW] [TGL-CET] libunwind isn't CET enabled
Private bug reported: [TGL-CET] libunwind isn't CET enabled it seems, Do you have patches / bug reports to get it enabled? ** Affects: intel Importance: High Status: Incomplete ** Affects: libunwind (Ubuntu) Importance: Undecided Status: New ** Tags: intel-cet-20.10 ** Also affects: libunwind (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Changed in: intel Status: New => Incomplete ** Changed in: intel Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1884086 Title: [TGL-CET] libunwind isn't CET enabled Status in intel: Incomplete Status in libunwind package in Ubuntu: New Bug description: [TGL-CET] libunwind isn't CET enabled it seems, Do you have patches / bug reports to get it enabled? To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1884086/+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 1874717] Re: devices cannot connect to ubuntu hotspot
Similar issue I am also facing. When the hotspot is ON with internet connection connected to 20.04 , ssid is not visible on devices to connect to the newtork -- 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/1874717 Title: devices cannot connect to ubuntu hotspot Status in network-manager package in Ubuntu: Incomplete Bug description: I upgraded to ubuntu 20.04 focal-fosa. Now I cannot share the ethernet based internet connection to my ubuntu system via the hotspot connection to my other devices.I am able to connect to my hospot though. My ethernet connection works fine hotspot too but my devices report:"This device has no connection to internet."Earlier in v18.04 it worked fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 17:49:30 2020 InstallationDate: Installed on 2019-06-18 (310 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago) VarLogDistupgradeTermlog: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-06-18 (310 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 10.20.2.1 dev enp2s0 proto static metric 100 10.20.2.0/25 dev enp2s0 proto kernel scope link src 10.20.2.32 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874717/+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 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
** Also affects: packagekit (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1829401 Title: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support Status in packagekit package in Ubuntu: Triaged Status in packagekit source package in Eoan: Triaged Status in packagekit source package in Focal: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.98.2, the problem page at https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. [Back trace] Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 86, in on_pktask_finish results = self._pktask.generic_finish(result) gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support (8) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 89, in on_pktask_finish Gtk.ButtonsType.CANCEL, _("Error while refreshing cache")) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in __init__ self._init(*args, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in __init__ _window_init(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) TypeError: could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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 1557739] Re: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device')
** Tags removed: rls-ff-incoming ** Tags added: rls-ff-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1557739 Title: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device') Status in apport package in Ubuntu: Confirmed Bug description: While running through the install, ubiquity crashed, then apport crashed so couldn't file a bug on ubiquity. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.367 CrashReports: 640:999:999:18776:2016-03-15 16:19:14.974973678 -0400:2016-03-15 16:19:15.974973678 -0400:/var/crash/_usr_bin_apport-bug.999.crash Date: Tue Mar 15 16:19:15 2016 ExecutablePath: /usr/bin/apport-bug InterpreterPath: /usr/bin/python3.5 LiveMediaBuild: Xubuntu Core 16.04 - amd64 - 20160314 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli ubiquity ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/apport-bug', 'ubiquity'] SourcePackage: apport Title: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device') UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1557739/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
** Tags removed: rls-ff-incoming ** Tags added: rls-ff-notfixing -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in Release Notes for Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Triaged Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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-release-notes/+bug/1867465/+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 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
Didier, there is a long-standing grub2 task on this bug, but from the comment history it's not clear to me that there are further changes required to grub or what those are, can you have another look at this please? (Given the description is "zfs-initramfs" failing, I would think that's not a grub bug, but I'm not sure.) ** Changed in: grub2 (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) -- 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/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in Release Notes for Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Triaged Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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-release-notes/+bug/1867465/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
[ 129.282522] brcmsmac bcma0:1 wlp2s0b1: renamed from wlan0 [ 491.516220] wl :02:00.0 wlp2s0: renamed from wlan0 So, i would have expected for systemd udev net_id to produce the same name for the wlan0 device, irrespective of the two drivers used. I wonder where the b1 is coming from and why it's present for one driver, and not the other. -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in Release Notes for Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Triaged Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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-release-notes/+bug/1867465/+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 1878517] Re: please apply bash 5.0 patch 17
** Changed in: bash (Ubuntu) Assignee: (unassigned) => Matthieu Clemenceau (mclemenceau) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1878517 Title: please apply bash 5.0 patch 17 Status in bash package in Ubuntu: Triaged Status in bash source package in Focal: Triaged Bug description: I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0 patch 16. I can't reproduce it in pure bash, but with bats from https://github.com/bats-core/bats-core/ it is very easy to repro: ``` # cat << EOF > ya.bats check() { echo "check $@" ls -l /proc/self/fd } @test "here file" { check -p <(echo "hey") false } EOF $ bats ya.bats ``` Normally the output should contain the line lr-x-- 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918] which is a result of a "here file" created by bash via <(echo "hey"). In my testing, about 50% of runs don't have /dev/fd/63 listed. I found out this is a manifest of a bug introduced in bash 5.0 patch 16 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016) The bug is fixed in 5.0 patch 17 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017). Please update bash to patchlevel 17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+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 1882636] Re: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777
Glib-networking is installed I'm getting an error that it's not installed from the accounts app in settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1882636 Title: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777 Status in glib-networking package in Ubuntu: Incomplete Bug description: OS: Pop!_OS 20.04 LTS x86_64 Host: XPS 13 9370 Kernel: 5.4.0-7634-generic Uptime: 2 hours, 50 mins Packages: 1817 (dpkg), 20 (snap) Shell: bash 5.0.16 Resolution: 1920x1080 DE: GNOME WM: Mutter WM Theme: Pop Theme: Pop-dark [GTK2/3] Icons: Pop [GTK2/3] Terminal: gnome-terminal CPU: Intel i5-8250U (8) @ 3.400GHz GPU: Intel UHD Graphics 620 Memory: 3322MiB / 15729MiB Summary(cont) - Attempt to input Google account info into online account util and get error--> TLS/SSL support not available; install glib-networking. https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777 Referenced this BUG REPORT ##Downloaded Deb build but I'm having an issue applying appropriate inputs in the provided documentation. Please help!## To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1882636/+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 1884101] [NEW] jackdbus produces high cpu load
Public bug reported: if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd tends to take all availabl CPU power bringing the system to slow down remarkably. Killing jackd and jackdbus frees cpu and system load drops from 100%/per CPU down to ~4% overall. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sct-muc1800 F pulseaudio /dev/snd/pcmC0D0c: sct-muc1800 F...m pulseaudio /dev/snd/pcmC0D0p: sct-muc1800 F...m pulseaudio /dev/snd/timer: sct-muc1800 f pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 18 18:08:25 2020 InstallationDate: Installed on 2019-09-09 (282 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1884101 Title: jackdbus produces high cpu load Status in pulseaudio package in Ubuntu: New Bug description: if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd tends to take all availabl CPU power bringing the system to slow down remarkably. Killing jackd and jackdbus frees cpu and system load drops from 100%/per CPU down to ~4% overall. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sct-muc1800 F pulseaudio /dev/snd/pcmC0D0c: sct-muc1800 F...m pulseaudio /dev/snd/pcmC0D0p: sct-muc1800 F...m pulseaudio /dev/snd/timer: sct-muc1800 f pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 18 18:08:25 2020 InstallationDate: Installed on 2019-09-09 (282 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1884101/+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 1882636] Re: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777
I'll follow up after work tonight work more specifics -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1882636 Title: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777 Status in glib-networking package in Ubuntu: Incomplete Bug description: OS: Pop!_OS 20.04 LTS x86_64 Host: XPS 13 9370 Kernel: 5.4.0-7634-generic Uptime: 2 hours, 50 mins Packages: 1817 (dpkg), 20 (snap) Shell: bash 5.0.16 Resolution: 1920x1080 DE: GNOME WM: Mutter WM Theme: Pop Theme: Pop-dark [GTK2/3] Icons: Pop [GTK2/3] Terminal: gnome-terminal CPU: Intel i5-8250U (8) @ 3.400GHz GPU: Intel UHD Graphics 620 Memory: 3322MiB / 15729MiB Summary(cont) - Attempt to input Google account info into online account util and get error--> TLS/SSL support not available; install glib-networking. https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777 Referenced this BUG REPORT ##Downloaded Deb build but I'm having an issue applying appropriate inputs in the provided documentation. Please help!## To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1882636/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
it seems the brcmsmac driver creates a device whose direct parent doesn't report that it's a pci device, so udev's net_id builtin moves past the NET_PCI naming and instead uses the NET_BCMA naming, since it's a BCMA device. That naming format is the same as pci, but appends bcma_core, which is set to 'b%u' for all cores > 0. -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in Release Notes for Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Triaged Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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-release-notes/+bug/1867465/+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 1878517] Re: please apply bash 5.0 patch 17
This patch applies upstream patch 017 to groovy's bash-5..0 ** Patch added: "bash-5.0-6ubuntu2-groovy.debdiff" https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+attachment/5385047/+files/bash-5.0-6ubuntu2-groovy.debdiff ** Changed in: bash (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1878517 Title: please apply bash 5.0 patch 17 Status in bash package in Ubuntu: In Progress Status in bash source package in Focal: Triaged Bug description: I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0 patch 16. I can't reproduce it in pure bash, but with bats from https://github.com/bats-core/bats-core/ it is very easy to repro: ``` # cat << EOF > ya.bats check() { echo "check $@" ls -l /proc/self/fd } @test "here file" { check -p <(echo "hey") false } EOF $ bats ya.bats ``` Normally the output should contain the line lr-x-- 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918] which is a result of a "here file" created by bash via <(echo "hey"). In my testing, about 50% of runs don't have /dev/fd/63 listed. I found out this is a manifest of a bug introduced in bash 5.0 patch 16 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016) The bug is fixed in 5.0 patch 17 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017). Please update bash to patchlevel 17. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
I appreciate everyone's time looking into this. I just wanted to add: if it is a driver problem, and can't be any better than that, I still think it would be friendlier if the installer informed the user that "a new driver is available. Your connection will disconnect while this driver is installed. It should automatically reconnect. If not, please wait at least until you see the next page, and reconnect manually." Maybe even a "yes/no" prompt so the person could elect to keep the working driver? To me, it wasn't so much about whose fault it is, but that I thought my router dropped the connection (that it was a coincidence, and I needed to go reset my router). Even if the underlying bug with the device name didn't exist, I think there could be a better user experience in this "on the fly" replacement of the driver. The "wifi connection lost" msg is a little unnerving if you don't know what's happening. It seems like it should be simple for the installer maintainers to make that more informative. Thanks again! -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in Release Notes for Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Triaged Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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-release-notes/+bug/1867465/+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 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1829401 Title: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support Status in packagekit package in Ubuntu: Triaged Status in packagekit source package in Eoan: Triaged Status in packagekit source package in Focal: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.98.2, the problem page at https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. [Back trace] Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 86, in on_pktask_finish results = self._pktask.generic_finish(result) gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support (8) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", line 89, in on_pktask_finish Gtk.ButtonsType.CANCEL, _("Error while refreshing cache")) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in __init__ self._init(*args, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in __init__ _window_init(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, in new_init return super_init_func(self, **new_kwargs) TypeError: could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
Proposed patch on OVS Mailing list to check status at configure time for OVS 2.14 using the method Bruce mentioned above: https://patchwork.ozlabs.org/project/openvswitch/patch/20200618165354.87787-7-harry.van.haa...@intel.com/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1883880 Title: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Bionic: New Bug description: Hi, DPDK has run into some issues in the past https://bugs.dpdk.org/show_bug.cgi?id=97 https://bugs.dpdk.org/show_bug.cgi?id=249 Eventually the issues got resolved in binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=23465 After binutils is fixed people rebuilding DPDK themselve can use http://patches.dpdk.org/patch/71679/ to gain more performance while on Bionics bintuils level. Note: Bionic is on DPDK 17.11.x which will not get further stable release afaik. But quite often people build their own DPDK. In fact this came up as a request from Openvswitch upstream/Intel to allow such builds on Bionic. I'd ping those people about the bug and ask them to participate in the verification if this becomes an SRU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
** Changed in: ubiquity (Ubuntu) Status: Triaged => Won't Fix -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in Release Notes for Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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-release-notes/+bug/1867465/+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 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
I will have a look (I don’t remember if the grub task is due to the grub.cfg generation or to grub code itself), but TBH, this is low priority on my list (downgrading the bug task priority as such, as this is a multi-system corner-case) ** Changed in: systemd (Ubuntu) Importance: Medium => Low ** Changed in: grub2 (Ubuntu) Importance: Medium => 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/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1877726] Re: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1877726 Title: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Please see https://askubuntu.com/questions/1229085/ubuntu-with-rodecaster-pro-usb-soundcard/1236257#1236257 for most background. tl;dr: - The Rodecaster Pro is a USB audio standard compliant device - lsusb sees it, but alsa cannot use it - trying the exact same setup with a Scarlett 2i2 USB device works (with some caveats, see the mentioned post) Somehow the Rodecaster is ignored by Alsa. I am more than happy to help debug. Alsa info is at http://alsa-project.org/db/?f=94fd609fa23912ab0a39b67676a026fd163f3f3b and also attached. nils@blackbox:~/tmp/soundtest$ aplay -l List of PLAYBACK Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 nils@blackbox:~/tmp/soundtest$ arecord --list-devices List of CAPTURE Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 2: ALC887-VD Alt Analog [ALC887-VD Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nils 90077 F pulseaudio /dev/snd/controlC0: nils 90077 F pulseaudio /dev/snd/controlC1: nils 90077 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:45:20 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-23 (1354 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AudioUsers: pulse Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nils 90077 F pulseaudio /dev/snd/controlC0: nils 90077 F pulseaudio /dev/snd/controlC1: nils 90077 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: Sound works for some users but not for others Title: [HDA-Intel - HD-Audio Generic, playback] sound not working for all users UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago) dmi.bios.date: 10/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5222 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-A 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.:bvr5222:bd10/14/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-A: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 mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-09T11:23:29.080704 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877726/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
** Bug watch added: github.com/systemd/systemd/issues #16214 https://github.com/systemd/systemd/issues/16214 ** Also affects: systemd via https://github.com/systemd/systemd/issues/16214 Importance: Unknown Status: Unknown -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Unknown Status in Release Notes for Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/systemd/+bug/1867465/+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 1884126] [NEW] Trying to add google account fails with AUTH-1140
Public bug reported: Trying to add a google account that redirects to another site for sign in results in a window with the following error: {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is an invalid header value that can't be parsed."}]} ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jun 18 11:41:17 2020 InstallationDate: Installed on 2019-08-17 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1884126 Title: Trying to add google account fails with AUTH-1140 Status in gnome-online-accounts package in Ubuntu: New Bug description: Trying to add a google account that redirects to another site for sign in results in a window with the following error: {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is an invalid header value that can't be parsed."}]} ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jun 18 11:41:17 2020 InstallationDate: Installed on 2019-08-17 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1884126/+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 1875699] Re: python3-venv missing ensurepip
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3-defaults (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1875699 Title: python3-venv missing ensurepip Status in python3-defaults package in Ubuntu: Confirmed Bug description: I believe that I cannot even report this correctly because it appears the problem is in a package called python3-venv, however, launchpad tells me '"python3-venv" does not exist in Ubuntu.' despite it clearly being both installed and recommended by python itself. When trying to create a python3 virtual environment, I get errors about ensurepip missing, however I have installed python3-venv. The python3-venv package does not include ensurepip: python3.8 -mvenv .env The virtual environment was not created successfully because ensurepip is not available. On Debian/Ubuntu systems, you need to install the python3-venv package using the following command. apt-get install python3-venv You may need to use sudo with that command. After installing the python3-venv package, recreate your virtual environment. Failing command: ['/mnt/d/src/.env/bin/python3.8', '-Im', 'ensurepip', '--upgrade', '--default-pip'] This is on Focal Fossa: Description: Ubuntu 20.04 LTS Release: 20.04 python3-venv: Installed: 3.8.2-0ubuntu2 Candidate: 3.8.2-0ubuntu2 Version table: *** 3.8.2-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1875699/+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 1884135] [NEW] [LE_WH-1000XM3, playback] Playback problem: BT headset only plays gnome-terminal's bell (Ctrl-G), any media/audio is still output via builtin intel audio
Public bug reported: After today's update, no audio can be played via connected Bluetooth headset (Sony LE_WH-1000XM3). The sound setting offers internal speakers or wireless headset, but either way any media (RhythmBox, Web video, ...) plays through the internal speakers. The notable exception is gnome-console's ping (played as output of a BELL character, like from hitting the backspace key on an empty bash command line, or from echo -e \\007 which does play through wireless headset (or internal speaker) as set by the sound setting. Before today's update, the Bluetooth headset did play audio (yet not immediately upon connecting; for though the sound setting had switched to the external headset, any sound was still output to via internal speakers. But switching once to the internal speakers and back to the BT headset was a viable workaround to get sound out to the BT headset.) >From apt log: Start-Date: 2020-06-18 17:19:14 Commandline: aptdaemon role='role-commit-packages' sender=':1.315' Upgrade: bind9-dnsutils:amd64 (1:9.16.1-0ubuntu2.1, 1:9.16.1-0ubuntu2.2), alsa-ucm-conf:amd64 (1.2.2-1, 1.2.2-1ubuntu0.1), bind9-host:amd64 (1:9.16.1-0ubuntu2.1, 1:9.16.1-0ubuntu2.2), dnsutils:amd64 (1:9.16.1-0ubuntu2.1, 1:9.16.1-0ubuntu2.2), initramfs-tools-bin:amd64 (0.136ubuntu6, 0.136ubuntu6.1), busybox-static:amd64 (1:1.30.1-4ubuntu6, 1:1.30.1-4ubuntu6.1), bind9-libs:amd64 (1:9.16.1-0ubuntu2.1, 1:9.16.1-0ubuntu2.2), initramfs-tools-core:amd64 (0.136ubuntu6, 0.136ubuntu6.1), initramfs-tools:amd64 (0.136ubuntu6, 0.136ubuntu6.1), gnome-shell-extension-ubuntu-dock:amd64 (67ubuntu20.04.5, 68ubuntu1~20.04.1), busybox-initramfs:amd64 (1:1.30.1-4ubuntu6, 1:1.30.1-4ubuntu6.1) Remove: linux-image-5.3.0-55-generic:amd64 (5.3.0-55.49), linux-modules-extra-5.3.0-55-generic:amd64 (5.3.0-55.49), linux-headers-5.3.0-55-generic:amd64 (5.3.0-55.49), linux-modules-5.3.0-55-generic:amd64 (5.3.0-55.49), linux-headers-5.3.0-55:amd64 (5.3.0-55.49) End-Date: 2020-06-18 17:20:14 Could the issue be caused by one of these packages? alsa-ucm-conf:amd64 (1.2.2-1, 1.2.2-1ubuntu0.1) gnome-shell-extension-ubuntu-dock:amd64 (67ubuntu20.04.5, 68ubuntu1~20.04.1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernhard 2078 F pulseaudio /dev/snd/pcmC0D0c: bernhard 2078 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 18 18:42:49 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-11 (919 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: LE_WH-1000XM3 Symptom_Type: Only some of outputs are working Title: [LE_WH-1000XM3, playback] Playback problem UpgradeStatus: Upgraded to focal on 2020-06-05 (13 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.01. dmi.board.name: Woody_KL dmi.board.vendor: KBL dmi.board.version: V1.01. dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.01. dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.01.:bd09/13/2017:svnAcer:pnSpinSP513-52N:pvrV1.01.:rvnKBL:rnWoody_KL:rvrV1.01.:cvnAcer:ct31:cvrV1.01.: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-52N dmi.product.sku: dmi.product.version: V1.01. dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-06-18T18:32:11.193118 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1884135 Title: [LE_WH-1000XM3, playback] Playback problem: BT headset only plays gnome-terminal's bell (Ctrl-G), any media/audio is still output via builtin intel audio Status in alsa-driver package in Ubuntu: New Bug description: After today's update, no audio can be played via connected Bluetooth headset (Sony LE_WH-1000XM3). The sound setting offers internal speakers or wireless headset, but either way any media (RhythmBox, Web video, ...) plays through the internal speakers. The notable exception is gnome-console's ping (played as output of a BELL character, like from hitting the backspace key on an empty bash command line, or from echo -e \\007 which does play through wireless headset (or internal speaker) as set by the sound setting. Before today's update, the Bluetooth headset did play audio (yet not immediately upon connecting; for though the sound setting had switched to the external hea
[Touch-packages] [Bug 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Unknown Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/systemd/+bug/1867465/+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 1867465] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Unknown Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/systemd/+bug/1867465/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
@ddstreet Indeed, https://www.freedesktop.org/software/systemd/man/systemd.net- naming-scheme.html b1 seems to stand for "Broadcom bus (BCMA) core number" So it seems to me that our stock vanilla kernel has gained support for this broadcom wifi chip with proper Broadcom bus support. Yet we also have some other implementation that claims to support the same chip, and then doesn't quite work the same way. I guess wl & bcmwl-kernel-source should not be both declaring support for the same chip? Such that user is not receiving one or the other, at random, or switching between the two, just because they ask installer to enable Nvidia. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: bcmwl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Unknown Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/systemd/+bug/1867465/+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 1883702] Re: [Satellite P55W-C, Realtek ALC233, Mic, Internal] Recording problem
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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1883702 Title: [Satellite P55W-C, Realtek ALC233, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: input mic does not work. It worked after for a day and become muted again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kyu3620 F pulseaudio /dev/snd/pcmC0D0c: kyu3620 F...m pulseaudio /dev/snd/pcmC0D0p: kyu3620 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 16 21:35:26 2020 InstallationDate: Installed on 2020-05-28 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: 내장 오디오 - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: Only some of inputs are working Title: [Satellite P55W-C, Realtek ALC233, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.30 dmi.board.name: 0693 dmi.board.vendor: FF40 dmi.board.version: 2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.30:bd12/09/2015:svnTOSHIBA:pnSatelliteP55W-C:pvrPSPVTU-008001:rvnFF40:rn0693:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: PEGA Family dmi.product.name: Satellite P55W-C dmi.product.sku: PSPVTU dmi.product.version: PSPVTU-008001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883702/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
@Alberto Milone Something odd is happening for the user of BCM4313 wifi chip. The devices appears to jump from bus1 to bus0, and thus getting a new name. Or as if, there are two different drivers offered to the user and/or operational via different buses. Such that udev identifies the same card on bus1 at first, and then later at bus0 and thus generates wlp2s0b1 name at first, and then wlp2s0 device name (not that when bus is 0, b0 is ommitted). -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Unknown Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/systemd/+bug/1867465/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
@MarkF (az2008) What you have experienced is abnormal. Normally there is only one driver for device, we offer the best driver we have, and once connected to the internet, the connection persists without any disconnects. And copies wifi config into the target installed system. Such that one never has to type the WiFi password a second time. I'm trying to troubleshoot what went wrong. As normally, we shouldn't cause such disruption at all. And thus there should be no need for confusing popups saying things about disconnects, waiting, redoing things. ** Tags removed: rls-ff-notfixing -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Unknown Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/systemd/+bug/1867465/+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 1884126] Re: Trying to add google account fails with AUTH-1140
Thank you for your bug report, could you report it upstream on https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues ? ** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1884126 Title: Trying to add google account fails with AUTH-1140 Status in gnome-online-accounts package in Ubuntu: New Bug description: Trying to add a google account that redirects to another site for sign in results in a window with the following error: {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is an invalid header value that can't be parsed."}]} ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jun 18 11:41:17 2020 InstallationDate: Installed on 2019-08-17 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1884126/+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 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.
@cpg100: did you made an update-initramfs -u ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1870260 Title: initramfs unpacking failed: Decoding failed", message appears on boot up. Status in linux package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: OS : Ubuntu 20.04(20200401) Problem: "initramfs unpacking failed: Decoding failed", message appears on boot up solution: If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to COMPRESS=gzip then the error is fixing . Expected solution: This but in there from a long time I have seen this from Ubuntu 18.04,19.04,19.10 now in 20.04 So please fix it or change it from lz4 to gzip. an early reply is highly appreciated Thank you . --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tamal 1451 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx Package: ubuntu-meta ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY34PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870260/+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 1884101] Re: jackdbus produces high cpu load
** Package changed: pulseaudio (Ubuntu) => jackd2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1884101 Title: jackdbus produces high cpu load Status in jackd2 package in Ubuntu: Incomplete Bug description: if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd tends to take all availabl CPU power bringing the system to slow down remarkably. Killing jackd and jackdbus frees cpu and system load drops from 100%/per CPU down to ~4% overall. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sct-muc1800 F pulseaudio /dev/snd/pcmC0D0c: sct-muc1800 F...m pulseaudio /dev/snd/pcmC0D0p: sct-muc1800 F...m pulseaudio /dev/snd/timer: sct-muc1800 f pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 18 18:08:25 2020 InstallationDate: Installed on 2019-09-09 (282 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1884101/+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 1884101] Re: jackdbus produces high cpu load
Please install the version of jackd2 in the Ubuntu Studio Backports PPA found at https://launchpad.net/~ubuntustudio- ppa/+archive/ubuntu/backports/+packages to see if that fixes the problem. If it does, then I might be able to set-up a Stable Release Update (SRU) to get it into 20.04. Setting as "Incomplete" for now simply to ensure a response happens in the next 60 days or this bug expires since this is critical to troubleshooting this problem. ** Changed in: jackd2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1884101 Title: jackdbus produces high cpu load Status in jackd2 package in Ubuntu: Incomplete Bug description: if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd tends to take all availabl CPU power bringing the system to slow down remarkably. Killing jackd and jackdbus frees cpu and system load drops from 100%/per CPU down to ~4% overall. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sct-muc1800 F pulseaudio /dev/snd/pcmC0D0c: sct-muc1800 F...m pulseaudio /dev/snd/pcmC0D0p: sct-muc1800 F...m pulseaudio /dev/snd/timer: sct-muc1800 f pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 18 18:08:25 2020 InstallationDate: Installed on 2019-09-09 (282 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1884101/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
** Changed in: systemd Status: Unknown => Fix Released -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/systemd/+bug/1867465/+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 1884142] Re: evolution-addressbook-factory crashed with signal 5 in g_thread_new()
*** This bug is a duplicate of bug 1858320 *** https://bugs.launchpad.net/bugs/1858320 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1858320, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1884142/+attachment/5385101/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1884142/+attachment/5385103/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1884142/+attachment/5385107/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1884142/+attachment/5385108/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1884142/+attachment/5385109/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1884142/+attachment/5385110/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1884142/+attachment/5385111/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1858320 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1884142 Title: evolution-addressbook-factory crashed with signal 5 in g_thread_new() Status in evolution-data-server package in Ubuntu: New Bug description: it crashed in the background. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 18 21:41:28 2020 ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory InstallationDate: Installed on 2017-10-13 (979 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory Signal: 5 SourcePackage: evolution-data-server StacktraceTop: g_thread_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 e_data_factory_spawn_subprocess_backend () at /usr/lib/x86_64-linux-gnu/libebackend-1.2.so.10 () at /usr/lib/x86_64-linux-gnu/libedata-book-1.2.so.25 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: evolution-addressbook-factory crashed with signal 5 in g_thread_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1884142/+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 1884147] [NEW] package libssl1.1 1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] failed to install/upgrade: trying
Public bug reported: Attempting to install legacy 32 bit version of libssl.so.1.0.0 to allow an old app to run. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libssl1.1 1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 AptOrdering: libssl1.1:i386: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 18 14:37:52 2020 DpkgTerminalLog: Preparing to unpack .../libssl1.1_1.1.1f-1ubuntu2_i386.deb ... Unpacking libssl1.1:i386 (1.1.1f-1ubuntu2) over (1.1.1-1ubuntu2.1~18.04.5) ... dpkg: error processing archive /var/cache/apt/archives/libssl1.1_1.1.1f-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 DuplicateSignature: package:libssl1.1:1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] Unpacking libssl1.1:i386 (1.1.1f-1ubuntu2) over (1.1.1-1ubuntu2.1~18.04.5) ... dpkg: error processing archive /var/cache/apt/archives/libssl1.1_1.1.1f-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 InstallationDate: Installed on 2020-02-21 (118 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: openssl Title: package libssl1.1 1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 UpgradeStatus: Upgraded to focal on 2020-05-09 (40 days ago) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1884147 Title: package libssl1.1 1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 Status in openssl package in Ubuntu: New Bug description: Attempting to install legacy 32 bit version of libssl.so.1.0.0 to allow an old app to run. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libssl1.1 1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 AptOrdering: libssl1.1:i386: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 18 14:37:52 2020 DpkgTerminalLog: Preparing to unpack .../libssl1.1_1.1.1f-1ubuntu2_i386.deb ... Unpacking libssl1.1:i386 (1.1.1f-1ubuntu2) over (1.1.1-1ubuntu2.1~18.04.5) ... dpkg: error processing archive /var/cache/apt/archives/libssl1.1_1.1.1f-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 DuplicateSignature: package:libssl1.1:1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] Unpacking libssl1.1:i386 (1.1.1f-1ubuntu2) over (1.1.1-1ubuntu2.1~18.04.5) ... dpkg: error processing archive /var/cache/apt/archives/libssl1.1_1.1.1f-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 InstallationDate: Installed on 2020-02-21 (118 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Py
[Touch-packages] [Bug 1884147] Re: package libssl1.1 1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] failed to install/upgrade: trying to
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1884147 Title: package libssl1.1 1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 Status in openssl package in Ubuntu: New Bug description: Attempting to install legacy 32 bit version of libssl.so.1.0.0 to allow an old app to run. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libssl1.1 1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 AptOrdering: libssl1.1:i386: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 18 14:37:52 2020 DpkgTerminalLog: Preparing to unpack .../libssl1.1_1.1.1f-1ubuntu2_i386.deb ... Unpacking libssl1.1:i386 (1.1.1f-1ubuntu2) over (1.1.1-1ubuntu2.1~18.04.5) ... dpkg: error processing archive /var/cache/apt/archives/libssl1.1_1.1.1f-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 DuplicateSignature: package:libssl1.1:1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] Unpacking libssl1.1:i386 (1.1.1f-1ubuntu2) over (1.1.1-1ubuntu2.1~18.04.5) ... dpkg: error processing archive /var/cache/apt/archives/libssl1.1_1.1.1f-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 InstallationDate: Installed on 2020-02-21 (118 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: openssl Title: package libssl1.1 1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from other instances of package libssl1.1:i386 UpgradeStatus: Upgraded to focal on 2020-05-09 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1884147/+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 1884148] [NEW] /usr/share/apport/package_hook:ValueError:__getitem__:_apt_pkg:__getitem__:/usr/share/apport/package_hook@48:get_source:_apt_pkg
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu40, the problem page at https://errors.ubuntu.com/problem/976abccbca7b548c9ccf155c80c8eb6f36efa7de contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco eoan focal groovy kylin-19.04 rls-gg-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1884148 Title: /usr/share/apport/package_hook:ValueError:__getitem__:_apt_pkg:__getitem__:/usr/share/apport/package_hook@48:get_source:_apt_pkg Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu40, the problem page at https://errors.ubuntu.com/problem/976abccbca7b548c9ccf155c80c8eb6f36efa7de contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1884148/+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 1884150] [NEW] /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@424:parse_arguments:print_usage:_print_message
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu33, the problem page at https://errors.ubuntu.com/problem/c423b68efab8e4531186d40a742be0b9811da8f9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: bionic eoan focal groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1884150 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@424:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu33, the problem page at https://errors.ubuntu.com/problem/c423b68efab8e4531186d40a742be0b9811da8f9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1884150/+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 1884148] Re: /usr/share/apport/package_hook:ValueError:__getitem__:_apt_pkg:__getitem__:/usr/share/apport/package_hook@48:get_source:_apt_pkg
It looks to me like the hook which is supposed to report package installation failures is now not working likely because '-p' is expecting or being passed the wrong value. Here are some examples: /usr/bin/python3 /usr/share/apport/package_hook -p 016-google-chrome-stable --tags dist-upgrade ... /usr/bin/python3 /usr/share/apport/package_hook -p 364-openjdk-11-jdk-headless --tags dist-upgrade ... /usr/bin/python3 /usr/share/apport/package_hook -p 687-pop-icon-theme --tags dist-upgrade ... ** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1884148 Title: /usr/share/apport/package_hook:ValueError:__getitem__:_apt_pkg:__getitem__:/usr/share/apport/package_hook@48:get_source:_apt_pkg Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu40, the problem page at https://errors.ubuntu.com/problem/976abccbca7b548c9ccf155c80c8eb6f36efa7de contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1884148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877987] Re: apt search coredumping
This bug was fixed in the package apt - 2.1.6 --- apt (2.1.6) unstable; urgency=medium [ David Kalnischkies ] * Fix small memory leak in MethodConfig * Consider protected packages for removal if they are marked as such * Consider if a fix is successful before claiming it is * Allow 20 instead of 10 loops for pkgProblemResolver * Deal with duplicates in the solution space of a dep -- Julian Andres Klode Wed, 03 Jun 2020 18:25:22 +0200 ** Changed in: apt (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1877987 Title: apt search coredumping Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Triaged Bug description: root@citoyx:/var/crash# apt search jdk Sorting... Done Segmentation fault (core dumped) May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in libapt-pkg.so.6.0.0[7f6309bb5000+147000] May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 8d 04 c2 0f root@citoyx:/var/crash# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" apt search is coredumping While apt install/upgrade/update is running fine crash file in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884148] Re: /usr/share/apport/package_hook:ValueError:__getitem__:_apt_pkg:__getitem__:/usr/share/apport/package_hook@48:get_source:_apt_pkg
Here's the traceback too: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apt/cache.py", line 297, in __getitem__ rawpkg = self._cache[key] KeyError: '23-gimp-data' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 156, in _apt_pkg return self._cache()[package] File "/usr/lib/python3/dist-packages/apt/cache.py", line 299, in __getitem__ raise KeyError('The cache has no package named %r' % key) KeyError: "The cache has no package named '23-gimp-data'" During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/apport/package_hook", line 48, in pr['SourcePackage'] = apport.packaging.get_source(options.package) File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 189, in get_source if self._apt_pkg(package).installed: File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 158, in _apt_pkg raise ValueError('package %s does not exist' % package) ValueError: package 23-gimp-data does not exist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1884148 Title: /usr/share/apport/package_hook:ValueError:__getitem__:_apt_pkg:__getitem__:/usr/share/apport/package_hook@48:get_source:_apt_pkg Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu40, the problem page at https://errors.ubuntu.com/problem/976abccbca7b548c9ccf155c80c8eb6f36efa7de contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1884148/+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 1884150] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@424:parse_arguments:print_usage:_print_message
Traceback (most recent call last): File "/usr/share/apport/apport", line 424, in options = parse_arguments() File "/usr/share/apport/apport", line 369, in parse_arguments parser.print_usage() File "/usr/lib/python3.7/argparse.py", line 2484, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.7/argparse.py", line 2495, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' The traceback happens when trying to print the usage for the apport command. However, the real issue is why is apport not being called correctly. Looking at a few of the crash reports we can see a pattern similar to the following: PythonArgs ['/usr/share/apport/apport', '14750', '11', '0', '1', '14750', '!opt!VBoxGuestAdditions-6.1.4!bin!VBoxClient', '(deleted)'] The "(deleted)" bit is likely coming from the %E part of the core pattern. From man core. Since kernel 5.3.0, the pipe template is split on spaces into an argument list before the template parameters are expanded. In earlier kernels, the template parameters are expanded first and the resulting string is split on spaces into an argument list. This means that in earlier kernels executable names added by the %e and %E template parameters could get split into multiple arguments. So the core dump handler needs to put the executable names as the last argument and ensure it joins all parts of the executable name using spaces. Executable names with multiple spaces in them are not correctly represented in earlier kernels, meaning that the core dump handler needs to use mechanisms to find the executable name. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1884150 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@424:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu33, the problem page at https://errors.ubuntu.com/problem/c423b68efab8e4531186d40a742be0b9811da8f9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1884150/+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 1884126] Re: Trying to add google account fails with AUTH-1140
** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #126 https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126 ** Also affects: gnome-online-accounts via https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1884126 Title: Trying to add google account fails with AUTH-1140 Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: New Bug description: Trying to add a google account that redirects to another site for sign in results in a window with the following error: {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is an invalid header value that can't be parsed."}]} ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jun 18 11:41:17 2020 InstallationDate: Installed on 2019-08-17 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1884126/+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 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()
Hello Alfred, or anyone else affected, Accepted gnome-shell into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.36.3-1ubuntu1~20.04.2 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. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1865300 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() Status in GNOME Shell: Unknown Status in glib2.0 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Bug description: [ Impact ] gnome-shell-hotplug-sniffer crashes when attaching some device that may have files with unknown content type [ Test case ] - Plug a media, but it's not yet known which kind of files cause this issue, so we should just monitor the e.u.c crash: https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9 [ Regression potential ] - No valid application for opening a media is shown by gnome-shell --- This is for 3.34: https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec --- Happened during normal use of the desktop. ProblemType: CrashDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 19:51:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-01-25 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax PC (0x7f5f54fa6444) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865300/+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 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
Hello BavarianPH, or anyone else affected, Accepted libxau into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libxau/1:1.0.8-1ubuntu1 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: libxau (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: Fix Committed Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 41000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+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 1880968] Re: fixrtc fails due to bad format of input to the date command
Hello Alfonso, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.2 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. ** Changed in: initramfs-tools (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1880968 Title: fixrtc fails due to bad format of input to the date command Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Committed Bug description: The fixrtc script is failing with message: date: invalid date ' Wed Apr 1 17:23:44 2020' when calling the date command. It looks like it does not like the leading spaces for the input date. The date is taken from 'dumpe2fs -h' ouptput, and some clean-up on it happens, but it looks like it is not enough for BusyBox' date command, at least for the version in focal. Backporting this to focal is needed. [Impact] The system date shown on first boot is incorrect, which can be problematic on first boot if at that point in time there is no network connection. If fixrtc works correctly at least we get the date of the last time the rootfs was mounted, which is modern enough to avoid problems with snap assertions validation, etc. [Test case] Boot an image with fixrtc in the kernel command line in a system with no network. snap seeding will fail without the patch. [Regression Potential] Quite small, as the fix is small and targeted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+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 725126]
This problem still exists on binutils 2.33 when -fvisibility=hidden is passed to cflags. I imagine this is so due to some conflicting code where the forced B.W is only generated for static functions, since non- static ones will be relocated differently, but then because of -fvisibility=hidden, they get treated like statics, only B is used instead of the forced B.W, causing this issue to crop up again. OpenWRT experienced this when including WireGuard on a new board. I fixed it like this: https://git.zx2c4.com/wireguard-linux- compat/commit/?id=178cdfffb99f2fd6fb4a5bfd2f9319461d93f53b -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/725126 Title: gas may assemble b to locally-defined, preemptible global symbol as "b.n" Status in binutils: Fix Released Status in Linaro Binutils: Won't Fix Status in Cortex String Routines: Invalid Status in armel-cross-toolchain-base package in Ubuntu: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: There's no guarantee that R_ARM_THM_JUMP11 relocation can be resolved correctly if the symbol gets preempted. Observed in binutils-arm-linux-gnueabi 2.20.51.20100908-0ubuntu2cross1.52. Observed on binutils trunk on 2011-02-25. The problem seems to strike when the compiler optimises a sibling call to "b ", for which the assembler generates a b.n. As a side-effect of the presence of this relocation, Thumb-2 kernel modules may fail to load, since the kernel doesn't support fixing up this relocation. I believe the kernel doesn't do any symbol preemption processing when loading modules -- if so, the relocation is actually redundant. But there's no way for the kernel to detect at module load time that the relocation can safely be ignored. In kernel builds, about 1 out every 6 modules suffers from this problem. It's not clear to me whether the method used by the kernel to link .ko objects is wrong or not. It seems that either the tools should support symbol preemption in this scenario (implying that a short branch is not adequate to guarantee that preemption will work -- i.e., a gas bug) or not (in this case the fixup should be done locally and there should presumably be no relocation -- i.e., a different gas bug). It appears that passing -fno-optimize-sibling-calls to GCC can work around the problem by avoiding the generation of local branches to global symbols, but this is clearly not the correct fix. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/725126/+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 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
** Description changed: [Impact] - gnome-shell crashes a lot. Over 41000 times in bionic so far: + gnome-shell crashes a lot. Over 42000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: Fix Committed Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 42000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+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 1870058] Re: Collect deleted users
Hello Didier, or anyone else affected, Accepted zsys into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zsys/0.4.6 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. ** Changed in: zsys (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1870058 Title: Collect deleted users Status in shadow package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Fix Released Status in shadow source package in Focal: New Status in zsys source package in Focal: Fix Committed Bug description: [Impact] * Deleting users were preserving corresponding ZFS user datasets, without marking them for cleanup. * This is covered by dedicated use cases. [Test Case] 1. Ensure you have a foo user: 2. Run userdel --remove foo 3. Check that rpool/USERDATA/foo_ has its content removed and is not mounted 4. zfs get com.ubuntu.zsys:bootfs-dataset rpool/USERDATA/foo_ is not associated with current system dataset --- Other use case: 1.Ensure you have a foo user: 2. Run userdel foo 3. Check that rpool/USERDATA/foo_ still has its content, but is not mounted. 4. zfs get com.ubuntu.zsys:bootfs-dataset rpool/USERDATA/foo_ is not associated with current system dataset --- On a non ZFS installation : 1. Ensure you have a foo user: 2. Run userdel --remove foo 3. The user is deleted, no error occured. --- On a non ZFS installation with ZSys installed : 1. Ensure you have a foo user: 2. Run userdel --remove foo 3. The user is deleted, no error occured. [Regression Potential] * A new hidden command is added, triggered by userdel. * Tests are covering this new command and GRPC request. * The methodology is similar to useradd and usermod. The dependency between shadow and zsys is weak on purpose: - the ZSys hidden command is available and is a no-op if not called - if calling the command failed on userdel, nothing is done on ZSys side, but the code path is similar to ZSys not being installed or running on a non ZFS system. Ideally, we would untag them as part of GC so that we can clean them up later. However, those can be linked to states on other pools with same pool name than targetted one, and it will be hard to match them. Give a command for users to see them in status and then manually remove suspicious datasets ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1870058/+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 1881982] Re: memory exhaustion in parse_report()
** Description changed: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. - ## Vulnerability in whoopsie - - It was discovered that whoopsie incorrectly handled certain malformed crash files. If a user using whoopsie were tricked into parsing and uploading a specially crafted crash file, an attacker could exploit this to cause a denial of service. + # Vulnerability description + The parse_report() function in whoopsie.c allows attackers to cause a denial of service (memory leak) via a crafted file. + Exploitation of this issue causes excessive memory consumption which results in the Linux kernel triggering OOM killer on arbitrary process. + This results in the process being terminated by the OOM killer. - ## Basic - When a program has been crashed, Linux system tries to create a '.crash' file on '/var/crash/' directory with python script located in '/usr/share/apport/apport'. - The file contains a series of system crash information including core dump, syslog, stack trace, memory map info, etc. - A user is given read and write permission to the file. - After then, whoopsie parses key-value pairs in ‘.crash’ file and encodes it into binary json (bson) format. - Lastly, whoopsie forwards the data to a remotely connected Ubuntu error report system. - ## Vulnerability + # Details We have found a memory leak vulnerability during the parsing the crash file, when a collision occurs on GHashTable through g_hash_table_insert(). According to [1], if the key already exists in the GHashTable, its current value is replaced with the new value. If 'key_destory_func' and 'value_destroy_func' are supplied when creating the table, the old value and the passed key are freed using that function. Unfortunately, whoopsie does not handle the old value and the passed key when collision happens. If a crash file contains same repetitive key-value pairs, it leads to memory leak as much as the amount of repetition and results in denial-of-service. - ## Attack + [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g + -hash-table-insert + + + # PoC (*Please check the below PoC: whoopsie_killer.py) 1) Generates a certain malformed crash file that contains same repetitive key-value pairs. 2) Trigger the whoopsie to read the generated crash file. 3) After then, the whoopsie process has been killed. - ## Mitigation + + # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch) We should use g_hash_table_new_full() with ‘key_destroy_func’ and ‘value_destroy_func’ functions instead of g_hash_table_new(). Otherwise, before g_hash_table_insert(), we should check the collision via g_hash_table_lookup_extended() and obtain pointer to the old value and remove it. Sincerely, - - [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g - -hash-table-insert ** Summary changed: - memory exhaustion in parse_report() + DoS vulnerability: cause resource exhaustion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1881982 Title: DoS vulnerability: cause resource exhaustion Status in whoopsie package in Ubuntu: New Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. # Vulnerability description The parse_report() function in whoopsie.c allows attackers to cause a denial of service (memory leak) via a crafted file. Exploitation of this issue causes excessive memory consumption which results in the Linux kernel triggering OOM killer on arbitrary process. This results in the process being terminated by the OOM killer. # Details We have found a memory leak vulnerability during the parsing the crash file, when a collision occurs on GHashTable through g_hash_table_insert(). According to [1], if the key already exists in the GHashTable, its current value is replaced with the new value. If 'key_destory_func' and 'value_destroy_func' are supplied when creating the table, the old value and the passed key are freed using that function. Unfortunately, whoopsie does not handle the old value and the passed key when collision happens. If a crash file contains same repetitive key-value pairs, it leads to memory leak as much as the amount of repetition and results in denial-of-service. [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g -hash-table-insert # PoC (*Please check the below PoC: whoopsie_killer.py) 1) Generates a certain malformed crash file that contains same repetitive key-value pairs. 2) Trigger the whoopsie to read the generated crash file. 3) After then, the whoopsie process has been killed. # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch) We should use g_hash_table_new_full() with ‘key_destroy_func’ and ‘value_destroy_func’ functions instead of g_hash_table