[Bug 1925985] Re: CVE-2021-22204
Following https://wiki.ubuntu.com/SecurityTeam/SponsorsQueue , I can now subscribe ubuntu-security-sponsors : 1. Your patch is in debdiff format It is. 2. The patch follows the security team update procedures. Especially: - targeted against the security pocket of a stable release I think so, but I'm not exactly sure what a "security pocket" is. This is a patch against 20.04 LTS to fix an arbitrary code execution, so it seems appropriate. I've updated the patch to have 'focal-security' as distribution, as described in https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Packaging. - uses the correct version The version 11.88-1ubuntu1 is created by dch, so I'm assuming it is correct. (Maybe it should be 11.88-1ubuntu0.1 ?) - mentions a CVE, and preferably a LP bug #. The diff mentions CVE-2021-22204 and (LP: #1925985), which is this bug. - Check your .changes file to make sure that you have the right revision and distribution I've put 'focal-security' as distribution, which seemed the most appropriate. 3. All changes in the patch are intentional They are. 4. Your patch applies cleanly It does. 5. The Status and Assignment are correct I cannot change the status, but it seems OK. 6. Please comment on the testing performed. I've tested the patched package with echo_vakzz.jpg from https://hackerone.com/reports/1154542 on a development workstation. (So not on a clean Ubuntu installation.) - If all of the above is in order, please subscribe ubuntu-security-sponsors OK. ** Patch added: "update with focal-security as distribution" https://bugs.launchpad.net/ubuntu/+source/libimage-exiftool-perl/+bug/1925985/+attachment/5503783/+files/libimage-exiftool-perl_11.88-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925985 Title: CVE-2021-22204 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimage-exiftool-perl/+bug/1925985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910312] Re: semctl09 from ubuntu_ltp_syscalls failed on X / F-oem-5.6 / F-oracle-5.4
https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=9b829a2c645847624d744a32358b9bd0df863bb6 ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910312 Title: semctl09 from ubuntu_ltp_syscalls failed on X / F-oem-5.6 / F-oracle-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1910312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931509] Re: System hang with kernel general protection fault due to dell-wmi-sysman sysman_init failure
** Description changed: [Impact] Encountered below protection fault while doing reboot test since Ubuntu-oem-5.10-5.10.0-1028.29. Ubuntu Hirsute and Impish already have all the fixes. Jun 9 09:06:02 ubuntu kernel: [6.216367] general protection fault, probably for non-canonical address 0x213146a124f901ea: [#1] SMP NOPTI Jun 9 09:06:02 ubuntu kernel: [6.216371] CPU: 3 PID: 447 Comm: systemd-udevd Not tainted 5.10.0-1030-oem #31-Ubuntu Jun 9 09:06:02 ubuntu kernel: [6.216372] Hardware name: Dell Inc. Latitude 5300/, BIOS 1.13.1 01/22/2021 Jun 9 09:06:02 ubuntu kernel: [6.216376] RIP: 0010:kobject_put+0xd/0x60 Jun 9 09:06:02 ubuntu kernel: [6.216378] Code: 02 0f 85 64 ff ff ff 45 31 ff e9 6e ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 48 85 ff 74 3e 55 48 89 e5 53 48 89 fb 47 3c 01 74 1a 48 8d 7b 38 b8 ff ff ff ff f0 0f c1 43 38 83 f8 Jun 9 09:06:02 ubuntu kernel: [6.216379] RSP: 0018:b233406a7c38 EFLAGS: 00010202 Jun 9 09:06:02 ubuntu kernel: [6.216381] RAX: RBX: 213146a124f901ea RCX: Jun 9 09:06:02 ubuntu kernel: [6.216383] RDX: 0001 RSI: RDI: 213146a124f901ea Jun 9 09:06:02 ubuntu kernel: [6.216384] RBP: b233406a7c40 R08: 0001 R09: 9ac66400 Jun 9 09:06:02 ubuntu kernel: [6.216384] R10: 9c41106d7fa0 R11: 0001 R12: 9c4114011438 Jun 9 09:06:02 ubuntu kernel: [6.216385] R13: 213146a124f901ea R14: R15: b233406a7e70 Jun 9 09:06:02 ubuntu kernel: [6.216387] FS: 7f9e33410880() GS:9c485e4c() knlGS: Jun 9 09:06:02 ubuntu kernel: [6.216388] CS: 0010 DS: ES: CR0: 80050033 Jun 9 09:06:02 ubuntu kernel: [6.216389] CR2: 7ffe51396080 CR3: 00011211e003 CR4: 003706e0 Jun 9 09:06:02 ubuntu kernel: [6.216390] Call Trace: Jun 9 09:06:02 ubuntu kernel: [6.216394] kset_unregister+0x2a/0x40 Jun 9 09:06:02 ubuntu kernel: [6.216399] sysman_init+0x20e/0x1000 [dell_wmi_sysman] Jun 9 09:06:02 ubuntu kernel: [6.216401] ? 0xc0ce4000 Jun 9 09:06:02 ubuntu kernel: [6.216404] do_one_initcall+0x48/0x1d0 Jun 9 09:06:02 ubuntu kernel: [6.216406] ? _cond_resched+0x19/0x30 Jun 9 09:06:02 ubuntu kernel: [6.216408] ? kmem_cache_alloc_trace+0x37a/0x430 Jun 9 09:06:02 ubuntu kernel: [6.216410] ? do_init_module+0x28/0x250 Jun 9 09:06:02 ubuntu kernel: [6.216412] do_init_module+0x62/0x250 Jun 9 09:06:02 ubuntu kernel: [6.216414] load_module+0x11ac/0x1370 Jun 9 09:06:02 ubuntu kernel: [6.216417] ? security_kernel_post_read_file+0x5c/0x70 Jun 9 09:06:02 ubuntu kernel: [6.216419] ? security_kernel_post_read_file+0x5c/0x70 Jun 9 09:06:02 ubuntu kernel: [6.216421] __do_sys_finit_module+0xc2/0x120 Jun 9 09:06:02 ubuntu kernel: [6.216423] ? __do_sys_finit_module+0xc2/0x120 Jun 9 09:06:02 ubuntu kernel: [6.216427] __x64_sys_finit_module+0x1a/0x20 Jun 9 09:06:02 ubuntu kernel: [6.216429] do_syscall_64+0x38/0x90 Jun 9 09:06:02 ubuntu kernel: [6.216431] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] - Clean cherry pick below commits + The first commit fixes the issue, but also cherry pick some other commits for some other potential regressions. + bdda39673fde platform/x86: dell-wmi-sysman: Fix crash caused by calling kset_unregister twice eaa1dcc79694 platform/x86: dell-wmi-sysman: Cleanup sysman_init() error-exit handling f4c4e9ad1523 platform/x86: dell-wmi-sysman: Fix release_attributes_data() getting called twice on init_bios_attributes() failure ececdb898376 platform/x86: dell-wmi-sysman: Fix possible NULL pointer deref on exit 9b95665a83ec platform/x86: dell-wmi-sysman: Make sysman_init() return -ENODEV of the interfaces are not found 5e3f5973c8df platform/x86: dell-wmi-sysman: Make init_bios_attributes() ACPI object parsing more robust 42f38dcccfb3 platform/x86: dell-wmi-sysman: Cleanup create_attributes_level_sysfs_files() [Test] It passed 300 and 400 times reboot tests with 2 different platforms [Where problems could occur] ** Description changed: [Impact] Encountered below protection fault while doing reboot test since Ubuntu-oem-5.10-5.10.0-1028.29. Ubuntu Hirsute and Impish already have all the fixes. Jun 9 09:06:02 ubuntu kernel: [6.216367] general protection fault, probably for non-canonical address 0x213146a124f901ea: [#1] SMP NOPTI Jun 9 09:06:02 ubuntu kernel: [6.216371] CPU: 3 PID: 447 Comm: systemd-udevd Not tainted 5.10.0-1030-oem #31-Ubuntu Jun 9 09:06:02 ubuntu kernel: [6.216372] Hardware name: Dell Inc. Latitude 5300/, BIOS 1.13.1 01/22/2021 Jun 9 09:06:02 ubuntu kernel: [6.216376] RIP: 0010:kobject_put+0xd/0x60 Jun 9 09:06:02 ubuntu kernel: [6.216378] Code: 02 0f 85
[Bug 1908375] Re: ceph-volume lvm list calls blkid numerous times for differrent devices
I have reuploaded the patch removing unnecessary entries (debdiff attached for reference). ** Patch added: "bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1908375/+attachment/5503781/+files/bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908375 Title: ceph-volume lvm list calls blkid numerous times for differrent devices To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1908375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
Without the recent PPC fixes s390x was broken as well, so I'm not saying "the ppc fixes broke s390x": https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210608_073451_f187d@/log.gz Instead there seems to be a new crash affecting s390x that has to be looked at to be able to rev up the nss version. Tagging server-next and subscribing the team as this is no more a +1 task. If we are lucky the always dilligent locutus (who often merges nss) might come by and give it a short as well when we have latter nss versions. ** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931104 Title: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish- proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1931104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
Reproducible, ppc64 is fixed and s390x broken by the latest 3.66 + fixes from master. Links: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210609_065306_2e698@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210609_121610_a71da@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210609_124415_d071b@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931104 Title: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish- proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1931104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931288] Re: Touchpad doesn't work in 'Ideapad 5 14ALC05' after OS installation restart.
@Antti, can you try mainline kernel and also provide dmesg? Download deb files from AMD64, https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc5/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931288 Title: Touchpad doesn't work in 'Ideapad 5 14ALC05' after OS installation restart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1931288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931518] Re: grub-efi-amd64-signed 1.167~18.04.1+2.04-1ubuntu44 has broken non-EFI install
It is safe to install on non efi systems, and as shipped, Ubuntu provides an EFI system partition mounted at /boot/efi. It appears on your system this partition is no longer mounted, causing the error. It is correct for grub to fail the upgrade rather than leaving the ESP contents not updated. If you are not going to have /boot/efi mounted, the other option is to uninstall shim-signed and grub-efi-amd64-signed; this will prevent you from transitioning this install to use UEFI in the future. ** Changed in: grub2-signed (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931518 Title: grub-efi-amd64-signed 1.167~18.04.1+2.04-1ubuntu44 has broken non-EFI install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1931518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931527] Re: I have artifacts on Youtube videos in Firefox.
Heavy artifacts on youtube videos ** Attachment added: "Firefox Bug.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931527/+attachment/5503776/+files/Firefox%20Bug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931527 Title: I have artifacts on Youtube videos in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931527] [NEW] I have artifacts on Youtube videos in Firefox.
Public bug reported: I use a Raspberry Pi 4, and now I have artifacts on Youtube videos in Firefox after update. Ubuntu 20.10, Firefox 89.0+build2-0ubuntu0.20.10.1 arm64 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firefox 89.0+build2-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1398 F pulseaudio /dev/snd/pcmC1D0p: daniel 1398 F...m pulseaudio /dev/snd/controlC0: daniel 1398 F pulseaudio BuildID: 20210527174632 CasperMD5CheckResult: skip Channel: Unavailable Date: Thu Jun 10 07:55:19 2021 ForcedLayersAccel: False ImageMediaBuild: 20201022 IpRoute: default via 192.168.1.1 dev eth0 proto dhcp metric 100 default via 192.168.1.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.113 metric 100 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.114 metric 600 NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image groovy raspi-image -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931527 Title: I have artifacts on Youtube videos in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931530] [NEW] ubuntu software is not running.
Public bug reported: whenever I try to run ubuntu software it shows that it is starting but never shows up. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 10 11:35:19 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-06-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931530 Title: ubuntu software is not running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1931530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
Ok, the line that concerns me is: " enP53p0s0.171: link pending udev initialization... " It looks like systemd-networkd thinks that udev is not done with enP53p0s0.171 --> "pending", but configuring it with ip works - so could be networkd or also udevd. So lets expand the journal output with the udev messages and share it again: journalctl -b -u systemd-networkd -u systemd-udevd --no-pager Please can you also share the output of: apt-cache policy systemd udev netplan.io Investigations pointed me to: https://github.com/systemd/systemd/issues/15445#issuecomment-776856604 (changing the interface name at some point could be interesting, too...) Anyway, I'll mark this bug as affecting systemd now. ** Bug watch added: github.com/systemd/systemd/issues #15445 https://github.com/systemd/systemd/issues/15445 ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931526] [NEW] Screen freeze at login or after running a graphical session
Public bug reported: After upgrade to Ubuntu 21.04 my laptop Dell Latitude 7480 with Intel graphic card freezes either: * during entering to boot password (encrypted file system), sometimes * during entering my password, often * after my X-session was started, sometimes When I boot in recovery mode (and resume to normal boot), the problem disappers ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.12 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Jun 10 07:48:22 2021 InstallationDate: Installed on 2020-07-07 (337 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to hirsute on 2021-06-04 (5 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931526 Title: Screen freeze at login or after running a graphical session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931524] Re: package texlive-binaries 2020.20200327.54578-7 failed to install/upgrade: installed texlive-binaries package post-installation script subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931524 Title: package texlive-binaries 2020.20200327.54578-7 failed to install/upgrade: installed texlive-binaries package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1931524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931524] [NEW] package texlive-binaries 2020.20200327.54578-7 failed to install/upgrade: installed texlive-binaries package post-installation script subprocess returned error exit status 2
Public bug reported: Situation arose after trying to install RoseGarden and LilyPond on this newly upgraded system. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: texlive-binaries 2020.20200327.54578-7 Uname: Linux 5.4.73v64 aarch64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Jun 10 00:14:07 2021 DuplicateSignature: package:texlive-binaries:2020.20200327.54578-7 Setting up texlive-binaries (2020.20200327.54578-7) ... update-alternatives: error: unable to open file '/var/lib/dpkg/alternatives/my.cnf': No such device or address dpkg: error processing package texlive-binaries (--configure): installed texlive-binaries package post-installation script subprocess returned error exit status 2 ErrorMessage: installed texlive-binaries package post-installation script subprocess returned error exit status 2 ImageMediaBuild: 20201022 Python3Details: /usr/bin/python3.9, Python 3.9.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: texlive-bin Title: package texlive-binaries 2020.20200327.54578-7 failed to install/upgrade: installed texlive-binaries package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to hirsute on 2021-06-09 (0 days ago) ** Affects: texlive-bin (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 arm64-image hirsute raspi-image -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931524 Title: package texlive-binaries 2020.20200327.54578-7 failed to install/upgrade: installed texlive-binaries package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1931524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526507] Re: cal 2016 , 4th week of Jan,Feb & Mar is missing
Thanks Alain, I will close as unverified. ** Changed in: bsdmainutils (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526507 Title: cal 2016 , 4th week of Jan,Feb & Mar is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsdmainutils/+bug/1526507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931522] [NEW] Radeon 7 - [drm] perform_link_training_with_retries: Link training attempt failed
Public bug reported: One of two Displayport connected monitors does not properly wake. Ubuntu 20.04.2 LTS - this was when they went to sleep after being locked for a while for power save. Ubuntu 21.04 LTS - Occurred when display when switching to a tty and back to the gnome gui. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: babak 2491 F pulseaudio /dev/snd/controlC2: babak 2491 F pulseaudio /dev/snd/controlC0: babak 2491 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 9 22:12:30 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Micro-Star International Co., Ltd. MS-7C34 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=3d216401-e070-4d87-8a07-3cc2f5bf2650 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.D0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MEG X570 GODLIKE (MS-7C34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.D0:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGX570GODLIKE(MS-7C34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931522 Title: Radeon 7 - [drm] perform_link_training_with_retries: Link training attempt failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
So we will just let it go? Or, somebody from mainline kernel team is looking into the matter? This is ridiculous, what is the point of having a 5 year LTS which can't support the newest kernels that are necessary for newer hardware? In simple words, one cannot use Ubuntu LTS with new hardware. One needs to use the latest ubuntu OS which might be plagued with bugs and many other issues, and furthermore keep changing it every 6 months? I am dying to hear any sensible argument in favour of this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931519] [NEW] bug while upgrading to 20.10
Public bug reported: Errors were encountered while processing: grub-pc linux- image-5.8.0-53-generic linux-image-5.8.0-55-generic this is always a error and for upgarding to 20.10 a bug has occured ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.33 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Thu Jun 10 09:43:14 2021 InstallationDate: Installed on 2021-04-15 (55 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2021-06-10 (0 days ago) VarLogDistupgradeAptlog: Log time: 2021-06-10 09:34:37.830485 Log time: 2021-06-10 09:34:45.998689 Log time: 2021-06-10 09:41:57.713207 Log time: 2021-06-10 09:43:13.018407 VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2021-06-03T13:04:47.731147 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931519 Title: bug while upgrading to 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908279] Re: Unable to upgrade from 18.04LTS to 20.04LTS
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908279 Title: Unable to upgrade from 18.04LTS to 20.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921798] Re: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921798 Title: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1921798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system
I am running with the custom kernel but I ran into the error now. As earlier, the first line was Error while async write back metadata Couldn't take a photo of the screen with the remaining lines. The specific scenario was that I was working with the system, thought I should check something in Windows, rebooted, picked windows, started booting, came to the windows repair screen (I had wiped and restored windows earlier because I was getting the system ready to be returned), clicked on restart instead of repair as I didn't want to set up windows user etc, hot restarted back into ubuntu and the system crashed on the login screen when I entered password. I will try to replicate this error now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927866 Title: Root filesystem becomes readonly frequenty freezing system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931514] Re: The NVIDIA X server Settings is blank when under Intel mode
And I made a patch for it. https://github.com/tseliot/ubuntu-drivers-common/pull/53 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: The NVIDIA X server Settings is blank when under Intel mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931514] Re: The NVIDIA X server Settings is blank when under Intel mode
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: The NVIDIA X server Settings is blank when under Intel mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931518] [NEW] grub-efi-amd64-signed 1.167~18.04.1+2.04-1ubuntu44 has broken non-EFI install
Public bug reported: On our hosts we are seeing --- $ sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up grub-efi-amd64-signed (1.167~18.04.1+2.04-1ubuntu44) ... Installing for x86_64-efi platform. grub-install: error: cannot find EFI directory. dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent processing triggers for shim-signed: shim-signed depends on grub-efi-amd64-signed | grub-efi-arm64-signed; however: Package grub-efi-amd64-signed is not configured yet. Package grub-efi-arm64-signed is not installed. dpkg: error processing package shim-signed (--configure): dependency problems - leaving triggers unprocessed Errors were encountered while processing: grub-efi-amd64-signed shim-signed E: Sub-process /usr/bin/dpkg returned an error code (1) --- Indeed grub-install as called is failing --- $ sudo grub-install --target=x86_64-efi --auto-nvram Installing for x86_64-efi platform. grub-install: error: cannot find EFI directory. --- This is a VM that is not booting via EFI I feel pretty sure this has come in via http://launchpadlibrarian.net/541948832/grub2-signed_1.167~18.04.1_1.167~18.04.3.diff.gz * key on grub-efi-$(DEB_HOST_ARCH) as the binary package for download-signed since grub-efi-* and grub2-common are now built from separate sources. This seemed to come in via our unatteneded upgrades @ --- Log started: 2021-06-02 06:52:59 files and directories currently installed.) Preparing to unpack .../python3-apport_2.20.9-0ubuntu7.24_all.deb ... Unpacking python3-apport (2.20.9-0ubuntu7.24) over (2.20.9-0ubuntu7.23) ... Setting up python3-apport (2.20.9-0ubuntu7.24) ... Setting up grub-efi-amd64-signed (1.167~18.04.1+2.04-1ubuntu44) ... Installing for x86_64-efi platform. grub-install: error: cannot find EFI directory. dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent processing triggers for shim-signed: shim-signed depends on grub-efi-amd64-signed | grub-efi-arm64-signed; however: Package grub-efi-amd64-signed is not configured yet. Package grub-efi-arm64-signed is not installed. --- Is this supposed to be safe to install on non-EFI systems? ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Package changed: shim-signed (Ubuntu) => grub2-signed (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931518 Title: grub-efi-amd64-signed 1.167~18.04.1+2.04-1ubuntu44 has broken non-EFI install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1931518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931514] Re: The NVIDIA X server Settings is blank when under Intel mode
The root cause is that the nvidia_loaded is false cause in Power Saving Mode,
and nvidia_kmod_available is also false cause couldn't find nvidia.ko
correctly, so it wont' do set_offloading() which cause nvidia-settings is blank.
Now we used the linux-modules-nvidia-5.10.0-xxx-oem package to support secure
boot, and it will install the nvidia.ko in
/lib/modules/5.10.0-xxx-oem/kernel/nvidia-460/, so we need fix the source code
to detect the nvidia modules correctly.
else if ((intel_loaded || amdgpu_loaded) && !nouveau_loaded &&
(nvidia_loaded || nvidia_kmod_available)) {
fprintf(log_handle, "NVIDIA hybrid system\n");
/* Try to enable prime */
if (enable_prime(prime_settings,
&discrete_device, current_devices, cards_n)) {
/* Write permanent settings about offloading */
set_offloading();
}
** Tags added: oem-priority originate-from-1931328 sutton
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931514
Title:
The NVIDIA X server Settings is blank when under Intel mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1931514/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931514] [NEW] The NVIDIA X server Settings is blank when under Intel mode
Public bug reported: [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: The NVIDIA X server Settings is blank when under Intel mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1931514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793124]
Also recently ran into this problem. I have to copy out the contents of the cell into a separate text editor to see everything. I hope this get fixed some time ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793124 Title: [upstream] Scrolling on Calc leaves content invisible if cell is higher than screen To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793124]
I'd really like this bug solved / feature added. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793124 Title: [upstream] Scrolling on Calc leaves content invisible if cell is higher than screen To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931511] Re: It just crashed
Thank you for reporting this bug to Ubuntu. Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931511 Title: It just crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1931511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115153] Re: Counter intuitive ordering for threaded Email ordered by "order received'
** Changed in: thunderbird Importance: Wishlist => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/115153 Title: Counter intuitive ordering for threaded Email ordered by "order received' To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/115153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115153]
Not sure if I'm seeing the same bug, or a different one, for me it has started happening a month or two ago, affecting news but not mail. I normally view sorted by order received, threaded, ascending I quite frequently switch between all and unread messages Using the menu/view/sort-by/order received, I see the "selected" indicator dot against "order received" and I see the "^" sort indicator in the order received column header of the message list pane. If I then swap between unread and all messages using the dropdown in the toolbar, I see the "^" indicator moves to the date column header, at this point the menu/view/sort-by still shows the selected indicator dot next to the order received entry But if I then navigate to a different group, and then switch back to the original group, there is no longer *any* indicator in the menu under view/sort-by and the sorting is messed up. I can always reselect order received and it will sort properly until I alter the all/unread toggle and navigate between different groups, then the sort is broken again. Running 45.6.0 on Win10 64 bit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/115153 Title: Counter intuitive ordering for threaded Email ordered by "order received' To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/115153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115153]
Within a thread, being able to use the received date order instead of the default reply-to tree is indeed a major missing feature for my TB usage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/115153 Title: Counter intuitive ordering for threaded Email ordered by "order received' To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/115153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115153]
Created attachment 8811578 Order received thread ordering.PNG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/115153 Title: Counter intuitive ordering for threaded Email ordered by "order received' To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/115153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115153]
Created attachment 8811577 Date thread ordering.PNG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/115153 Title: Counter intuitive ordering for threaded Email ordered by "order received' To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/115153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115153]
I'm not sure if I have the same problem but I'll explain it. Messages I received in Thunderbird did not actually have the right 'Received' date. So I added mailnews.customDBHeaders = " Received" and now the received column shows the date when my mail was actually received. But sorting by 'Received' is still no different from supporting by date. So I tried 'Order Received' and that seems to work except with threaded messages. For example ascending threaded: foo 100 bar 102 -re:bar 105 qux 103 So I would expect that the 'bar' thread would come after qux but it doesn't. This is actually a big problem sometimes because I have a lot of messages in my inbox and sometimes when they don't arrive for several days they end up way back earlier in the list and I don't even notice them. I will upload two screenshots. In fairness that happens rarely but I'm surprised this bug has been open for a decade. How do we get it handed off to someone? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/115153 Title: Counter intuitive ordering for threaded Email ordered by "order received' To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/115153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
This bug was fixed in the package thermald - 2.4.6-1 --- thermald (2.4.6-1) unstable; urgency=medium * sync with latest upstream release 2.4.6: - fix overheating Latitude 7400 (LP: #1930422) - Use Adaptive PPCC limits for RAPL MMIO - Increase power limit for disabled RAPL-MMIO - Special case for default PSVT * 2.4.5 fixes: - Set a very high RAPL MSR PL1 with --adaptive -- Colin King Wed, 9 Jun 2021 16:58:23 +0100 ** Changed in: thermald (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1930422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage
Wonderful, thanks Daniel! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926548 Title: The gatt protocol has out-of-bounds read that leads to information leakage To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931499] Re: cannot upgrade from 16 to 18
Thank you for taking the time to report this bug and helping to make Ubuntu better. The 'ppc' architecture is no longer a supported architecture. This was announced long ago, ie. https://lists.ubuntu.com/archives/ubuntu-devel- announce/2016-December/001199.html Because of this, I've changed the bug status to 'Invalid' as you are not on a supported architecture for the intended upgrade process. If you believe I'm in error, please leave a comment explaining why and the status can be returned to "New". ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931499 Title: cannot upgrade from 16 to 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931509] Re: System hang with kernel general protection fault due to dell-wmi-sysman sysman_init failure
** Tags added: oem-priority originate-from-1931125 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931509 Title: System hang with kernel general protection fault due to dell-wmi- sysman sysman_init failure To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864961] Re: tests ignore RC and have 15 fails left
Debian is now shipping two sets of code in php-imagick, one for PHP 7.x and earlier and one for PHP 8.0 and newer. Current results on impish (with the former codebase, i.e. PHP 7.4): = TEST RESULT SUMMARY - Exts skipped:0 Exts tested : 15 - Number of tests : 276 252 Tests skipped : 24 ( 8.7%) Tests warned:2 ( 0.7%) ( 0.8%) Tests failed:0 ( 0.0%) ( 0.0%) Tests passed: 250 ( 90.6%) ( 99.2%) - Time taken : 37 seconds = With the newer (PHP 8.0-enabled) codebase the original test skips appear to be resolved, however there are now some test failures. These are due to minor text changes of assertion messages, e.g.: 8) /tmp/autopkgtest.Y9KiYn/build.1Fn/src/imagick-3.4.4/tests/180_ImagickDraw_matte_basic.phpt Failed asserting that string matches format description. --- Expected +++ Actual @@ @@ -Deprecated: Function ImagickDraw::matte() is deprecated in %s +Deprecated: Method ImagickDraw::matte() is deprecated in Standard input code on line 17 These will need to get fixed up to make php-imagick transition, however the original problem this bug report was filed about seems to now be long in the past, so I think we can close this as resolved. ** Changed in: php-imagick (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864961 Title: tests ignore RC and have 15 fails left To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-imagick/+bug/1864961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931485] Re: DaVinci Resolve is not identifying my integrated Intel Graphics card
Thanks for the bug report. The attached files seem to show that your Intel graphics drivers are working properly for Ubuntu. Whatever the problem is you see in DaVinci Resolve appears to be specific to that application. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931485 Title: DaVinci Resolve is not identifying my integrated Intel Graphics card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931488] Re: Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade
** Package changed: xorg (Ubuntu) => plasma-workspace (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931488 Title: Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1931488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318951] Re: kernel update fails with /boot on FAT32
I just ran into this on a 18.04 LTS to 20.04 LTS upgrade Note that I was actually able to use the /etc/kernel-img.conf workaround with two properties: do_symlinks = No no_symlinks = Yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318951 Title: kernel update fails with /boot on FAT32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931387] Re: Ubuntu UI screen image freezes randomly during usage after fresh 21.04 install, suspecting Wayland
Thanks for the bug report. Please run this command to send us additional system info: apport-collect 1931387 Please also follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: hirsute nouveau ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931387 Title: Ubuntu UI screen image freezes randomly during usage after fresh 21.04 install, suspecting Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1931387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931475] Re: Ubuntu only stable in safe graphics mode
Thanks for the bug report. Please reproduce the bug (unwanted reboot) again, then boot in safe mode and run: journalctl -b-1 > prevboot1.txt journalctl -b-2 > prevboot2.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931475 Title: Ubuntu only stable in safe graphics mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
This is not hardware-specific. ** Summary changed: - [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem [17aa:a814]: Can't turn bluetooth on again after turning it off + [hirsute/impish] Can't turn bluetooth on again after turning it off -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930409] Re: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...
When you run 'apport-cli' it should give you a link to click on. Did you follow that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930409 Title: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
Bas, please remember to follow the instructions in comment #4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage
(checks again) Yes, fixed in 5.56 looks right. commit 3a40bef49305f8327635b81ac8be52a3ca063d5a Author: Luiz Augusto von Dentz AuthorDate: Mon Jan 4 10:38:31 2021 -0800 Commit: Luiz Augusto von Dentz CommitDate: Tue Jan 5 10:41:27 2021 -0800 landed on master before the next tag, which was: commit 482929f12b645f652d378fbe8d0a5b7c05d65c4f (tag: 5.56) Author: Marcel Holtmann AuthorDate: Mon Feb 22 21:12:40 2021 +0100 Commit: Marcel Holtmann CommitDate: Mon Feb 22 21:12:40 2021 +0100 However, it doesn't look like it's present on master anymore because it was rewritten 6 hours later: commit 6a50b6aeda78a88eafb177718109c256eec077a6 Author: Luiz Augusto von Dentz AuthorDate: Tue Jan 5 16:45:37 2021 -0800 Commit: Luiz Augusto von Dentz CommitDate: Tue Jan 5 16:55:32 2021 -0800 I assume the rewrite is free of the original bug, and so still fixed in 5.56. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926548 Title: The gatt protocol has out-of-bounds read that leads to information leakage To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931312] Re: i386 version of libpipewire-0.3 for Ubuntu Focal 20.04
This user found a solution. https://www.reddit.com/r/linux_gaming/comments/nw1shz/steam_wont_launch_on_pop_os_2004_2010_solution/ I use this and work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931312 Title: i386 version of libpipewire-0.3 for Ubuntu Focal 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1931312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926062] Re: [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem [17aa:a814]: Can't turn bluetooth on again after turning it off
** Summary changed: - [hirsute/impish] Can't turn bluetooth on again after turning it off + [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem [17aa:a814]: Can't turn bluetooth on again after turning it off ** Description changed: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS + + Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: - LANGUAGE=en_IN:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_IN - SHELL=/bin/bash + LANGUAGE=en_IN:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IN + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: - hci0:Type: Primary Bus: USB - BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 - DOWN - RX bytes:744804 acl:76 sco:0 events:105989 errors:0 - TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 + hci0:Type: Primary Bus: USB + BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 + DOWN + RX bytes:744804 acl:76 sco:0 events:105989 errors:0 + TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Realtek RTL8821AE 802.11ac PCIe [10ec:8821] Subsystem [17aa:a814]: Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] Re: SD card initialization on insertion fails
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Status: New => Triaged ** Changed in: linux (Ubuntu Impish) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931511] [NEW] It just crashed
Public bug reported: Was creating an account and it crashed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 Date: Wed Jun 9 20:49:55 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubiquity-2.18.7 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931511 Title: It just crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1931511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897712] Re: Graphics corruption (mixed up texture memory) makes game unusable
** Summary changed: - Ugly image output make game unusable + Graphics corruption (mixed up texture memory) makes game unusable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897712 Title: Graphics corruption (mixed up texture memory) makes game unusable To manage notifications about this bug go to: https://bugs.launchpad.net/gweled/+bug/1897712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931510] Re: [SRU] Thunar CVE-2021-32563 (focal, groovy, hirsute)
Attaching debdiff for hirsute. ** Patch added: "hirsute debdiff" https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1931510/+attachment/5503696/+files/thunar_4.16.6-0ubuntu1_to_4.16.6-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931510 Title: [SRU] Thunar CVE-2021-32563 (focal, groovy, hirsute) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1931510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931510] Re: [SRU] Thunar CVE-2021-32563 (focal, groovy, hirsute)
Attaching debdiff for focal. ** Patch added: "focal debdiff" https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1931510/+attachment/5503694/+files/thunar_1.8.14-0ubuntu1_to_1.8.14-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931510 Title: [SRU] Thunar CVE-2021-32563 (focal, groovy, hirsute) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1931510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931510] Re: [SRU] Thunar CVE-2021-32563 (focal, groovy, hirsute)
Attaching debdiff for groovy. ** Patch added: "groovy debdiff" https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1931510/+attachment/5503695/+files/thunar_1.8.15-1_to_1.8.15-1ubuntu0.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931510 Title: [SRU] Thunar CVE-2021-32563 (focal, groovy, hirsute) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1931510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931510] [NEW] [SRU] Thunar CVE-2021-32563 (focal, groovy, hirsute)
*** This bug is a security vulnerability *** Public security bug reported: [Impact] CVE-2021-32563 affects Thunar versions found in supported releases. https://nvd.nist.gov/vuln/detail/CVE-2021-32563 >From the CVE: An issue was discovered in Thunar before 4.16.7 and 4.17.x before 4.17.2. When called with a regular file as a command-line argument, it delegates to a different program (based on the file type) without user confirmation. This could be used to achieve code execution. Related upstream issues: - https://gitlab.xfce.org/xfce/thunar/-/issues/121 - https://gitlab.xfce.org/xfce/thunar/-/issues/575 The patches required for each supported release can be found here: 1.8.x for focal, groovy: https://gitlab.xfce.org/xfce/thunar/-/commit/1b85b96ebf7cb9bf6a3ddf1acee7643643fdf92d 4.16.x for hirsute: https://gitlab.xfce.org/xfce/thunar/-/commit/9165a61f95e43cc0b5abf9b98eee2818a0191e0b https://gitlab.xfce.org/xfce/thunar/-/commit/3b54d9d7dbd7fd16235e2141c43a7f18718f5664 [Test Plan] 1. Execute `thunar ~/Pictures/icon.png` 2. The default application loads the file. Expected behavior: Thunar should instead open, selecting the file. [Where problems could occur] Scripts and applications depending on the previous functionality will be adversely affected. Since this functionality (opening the default application instead of navigating to it) is specific to Thunar and not found in other file managers, this change should have minimal regression impact. [Other Info] We've done some preliminary work to resolve this issue. https://github.com/Xubuntu/xubuntu-development/issues/6 with a verification for the fix. Builds can be found here: https://launchpad.net/~xubuntu-dev/+archive/ubuntu/sru-staging ** Affects: thunar (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: thunar (Ubuntu Focal) Importance: Undecided Status: New ** Affects: thunar (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: thunar (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: thunar (Ubuntu Impish) Importance: Undecided Status: Fix Released ** Also affects: thunar (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: thunar (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: thunar (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: thunar (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: thunar (Ubuntu Impish) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931510 Title: [SRU] Thunar CVE-2021-32563 (focal, groovy, hirsute) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1931510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage
Daniel, are you sure about that fixed-in-5.56 bug tag? I can't spot the referenced commit in the tarballs 5.55, 5.56, 5.57, 5.58 from: http://www.bluez.org/ nor in the github sources: https://github.com/bluez/bluez/blob/master/src/gatt-database.c#L1054 nor the kernel.org sources: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/src/gatt-database.c#n1054 Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926548 Title: The gatt protocol has out-of-bounds read that leads to information leakage To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931509] Re: System hang with kernel general protection fault due to dell-wmi-sysman sysman_init failure
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Hirsute) ** No longer affects: linux (Ubuntu Impish) ** Description changed: [Impact] - Encountered below protection fault while doing reboot test since Ubuntu-oem-5.10-5.10.0-1028.29 + Encountered below protection fault while doing reboot test since Ubuntu-oem-5.10-5.10.0-1028.29. Ubuntu Hirsute and Impish already have all the fixes. Jun 9 09:06:02 ubuntu kernel: [6.216367] general protection fault, probably for non-canonical address 0x213146a124f901ea: [#1] SMP NOPTI Jun 9 09:06:02 ubuntu kernel: [6.216371] CPU: 3 PID: 447 Comm: systemd-udevd Not tainted 5.10.0-1030-oem #31-Ubuntu Jun 9 09:06:02 ubuntu kernel: [6.216372] Hardware name: Dell Inc. Latitude 5300/, BIOS 1.13.1 01/22/2021 Jun 9 09:06:02 ubuntu kernel: [6.216376] RIP: 0010:kobject_put+0xd/0x60 Jun 9 09:06:02 ubuntu kernel: [6.216378] Code: 02 0f 85 64 ff ff ff 45 31 ff e9 6e ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 48 85 ff 74 3e 55 48 89 e5 53 48 89 fb 47 3c 01 74 1a 48 8d 7b 38 b8 ff ff ff ff f0 0f c1 43 38 83 f8 Jun 9 09:06:02 ubuntu kernel: [6.216379] RSP: 0018:b233406a7c38 EFLAGS: 00010202 Jun 9 09:06:02 ubuntu kernel: [6.216381] RAX: RBX: 213146a124f901ea RCX: Jun 9 09:06:02 ubuntu kernel: [6.216383] RDX: 0001 RSI: RDI: 213146a124f901ea Jun 9 09:06:02 ubuntu kernel: [6.216384] RBP: b233406a7c40 R08: 0001 R09: 9ac66400 Jun 9 09:06:02 ubuntu kernel: [6.216384] R10: 9c41106d7fa0 R11: 0001 R12: 9c4114011438 Jun 9 09:06:02 ubuntu kernel: [6.216385] R13: 213146a124f901ea R14: R15: b233406a7e70 Jun 9 09:06:02 ubuntu kernel: [6.216387] FS: 7f9e33410880() GS:9c485e4c() knlGS: Jun 9 09:06:02 ubuntu kernel: [6.216388] CS: 0010 DS: ES: CR0: 80050033 Jun 9 09:06:02 ubuntu kernel: [6.216389] CR2: 7ffe51396080 CR3: 00011211e003 CR4: 003706e0 Jun 9 09:06:02 ubuntu kernel: [6.216390] Call Trace: Jun 9 09:06:02 ubuntu kernel: [6.216394] kset_unregister+0x2a/0x40 Jun 9 09:06:02 ubuntu kernel: [6.216399] sysman_init+0x20e/0x1000 [dell_wmi_sysman] Jun 9 09:06:02 ubuntu kernel: [6.216401] ? 0xc0ce4000 Jun 9 09:06:02 ubuntu kernel: [6.216404] do_one_initcall+0x48/0x1d0 Jun 9 09:06:02 ubuntu kernel: [6.216406] ? _cond_resched+0x19/0x30 Jun 9 09:06:02 ubuntu kernel: [6.216408] ? kmem_cache_alloc_trace+0x37a/0x430 Jun 9 09:06:02 ubuntu kernel: [6.216410] ? do_init_module+0x28/0x250 Jun 9 09:06:02 ubuntu kernel: [6.216412] do_init_module+0x62/0x250 Jun 9 09:06:02 ubuntu kernel: [6.216414] load_module+0x11ac/0x1370 Jun 9 09:06:02 ubuntu kernel: [6.216417] ? security_kernel_post_read_file+0x5c/0x70 Jun 9 09:06:02 ubuntu kernel: [6.216419] ? security_kernel_post_read_file+0x5c/0x70 Jun 9 09:06:02 ubuntu kernel: [6.216421] __do_sys_finit_module+0xc2/0x120 Jun 9 09:06:02 ubuntu kernel: [6.216423] ? __do_sys_finit_module+0xc2/0x120 Jun 9 09:06:02 ubuntu kernel: [6.216427] __x64_sys_finit_module+0x1a/0x20 Jun 9 09:06:02 ubuntu kernel: [6.216429] do_syscall_64+0x38/0x90 Jun 9 09:06:02 ubuntu kernel: [6.216431] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] [Test] [Where problems could occur] ** Description changed: [Impact] Encountered below protection fault while doing reboot test since Ubuntu-oem-5.10-5.10.0-1028.29. Ubuntu Hirsute and Impish already have all the fixes. Jun 9 09:06:02 ubuntu kernel: [6.216367] general protection fault, probably for non-canonical address 0x213146a124f901ea: [#1] SMP NOPTI Jun 9 09:06:02 ubuntu kernel: [6.216371] CPU: 3 PID: 447 Comm: systemd-udevd Not tainted 5.10.0-1030-oem #31-Ubuntu Jun 9 09:06:02 ubuntu kernel: [6.216372] Hardware name: Dell Inc. Latitude 5300/, BIOS 1.13.1 01/22/2021 Jun 9 09:06:02 ubuntu kernel: [6.216376] RIP: 0010:kobject_put+0xd/0x60 Jun 9 09:06:02 ubuntu kernel: [6.216378] Code: 02 0f 85 64 ff ff ff 45 31 ff e9 6e ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 48 85 ff 74 3e 55 48 89 e5 53 48 89 fb 47 3c 01 74 1a 48 8d 7b 38 b8 ff ff ff ff f0 0f c1 43 38 83 f8 Jun 9 09:06:02 ubuntu kernel: [6.216379] RSP: 0018:b233406a7c38 EFLAGS: 00010202 Jun 9 09:06:02 ubuntu kernel: [6.216381] RAX: RBX: 213146a124f901ea RCX: Jun 9 09:06:02 ubuntu kernel: [6.216383] RDX: 0001 RSI: RDI: 213146a124f901ea Jun 9 09:06:02 ubuntu kernel: [6.216384] RBP: b233406a7c40 R08: 0001 R09: 9ac66400 Jun 9 09:06:02 ubuntu kernel: [6.216384] R10: 9c41106d7fa0 R11: 0
[Bug 1931509] Re: System hang with kernel general protection fault due to dell-wmi-sysman sysman_init failure
** Description changed: [Impact] + Encountered below protection fault while doing reboot test since Ubuntu-oem-5.10-5.10.0-1028.29 + + Jun 9 09:06:02 ubuntu kernel: [6.216367] general protection fault, probably for non-canonical address 0x213146a124f901ea: [#1] SMP NOPTI + Jun 9 09:06:02 ubuntu kernel: [6.216371] CPU: 3 PID: 447 Comm: systemd-udevd Not tainted 5.10.0-1030-oem #31-Ubuntu + Jun 9 09:06:02 ubuntu kernel: [6.216372] Hardware name: Dell Inc. Latitude 5300/, BIOS 1.13.1 01/22/2021 + Jun 9 09:06:02 ubuntu kernel: [6.216376] RIP: 0010:kobject_put+0xd/0x60 + Jun 9 09:06:02 ubuntu kernel: [6.216378] Code: 02 0f 85 64 ff ff ff 45 31 ff e9 6e ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 48 85 ff 74 3e 55 48 89 e5 53 48 89 fb 47 3c 01 74 1a 48 8d 7b 38 b8 ff ff ff ff f0 0f c1 43 38 83 f8 + Jun 9 09:06:02 ubuntu kernel: [6.216379] RSP: 0018:b233406a7c38 EFLAGS: 00010202 + Jun 9 09:06:02 ubuntu kernel: [6.216381] RAX: RBX: 213146a124f901ea RCX: + Jun 9 09:06:02 ubuntu kernel: [6.216383] RDX: 0001 RSI: RDI: 213146a124f901ea + Jun 9 09:06:02 ubuntu kernel: [6.216384] RBP: b233406a7c40 R08: 0001 R09: 9ac66400 + Jun 9 09:06:02 ubuntu kernel: [6.216384] R10: 9c41106d7fa0 R11: 0001 R12: 9c4114011438 + Jun 9 09:06:02 ubuntu kernel: [6.216385] R13: 213146a124f901ea R14: R15: b233406a7e70 + Jun 9 09:06:02 ubuntu kernel: [6.216387] FS: 7f9e33410880() GS:9c485e4c() knlGS: + Jun 9 09:06:02 ubuntu kernel: [6.216388] CS: 0010 DS: ES: CR0: 80050033 + Jun 9 09:06:02 ubuntu kernel: [6.216389] CR2: 7ffe51396080 CR3: 00011211e003 CR4: 003706e0 + Jun 9 09:06:02 ubuntu kernel: [6.216390] Call Trace: + Jun 9 09:06:02 ubuntu kernel: [6.216394] kset_unregister+0x2a/0x40 + Jun 9 09:06:02 ubuntu kernel: [6.216399] sysman_init+0x20e/0x1000 [dell_wmi_sysman] + Jun 9 09:06:02 ubuntu kernel: [6.216401] ? 0xc0ce4000 + Jun 9 09:06:02 ubuntu kernel: [6.216404] do_one_initcall+0x48/0x1d0 + Jun 9 09:06:02 ubuntu kernel: [6.216406] ? _cond_resched+0x19/0x30 + Jun 9 09:06:02 ubuntu kernel: [6.216408] ? kmem_cache_alloc_trace+0x37a/0x430 + Jun 9 09:06:02 ubuntu kernel: [6.216410] ? do_init_module+0x28/0x250 + Jun 9 09:06:02 ubuntu kernel: [6.216412] do_init_module+0x62/0x250 + Jun 9 09:06:02 ubuntu kernel: [6.216414] load_module+0x11ac/0x1370 + Jun 9 09:06:02 ubuntu kernel: [6.216417] ? security_kernel_post_read_file+0x5c/0x70 + Jun 9 09:06:02 ubuntu kernel: [6.216419] ? security_kernel_post_read_file+0x5c/0x70 + Jun 9 09:06:02 ubuntu kernel: [6.216421] __do_sys_finit_module+0xc2/0x120 + Jun 9 09:06:02 ubuntu kernel: [6.216423] ? __do_sys_finit_module+0xc2/0x120 + Jun 9 09:06:02 ubuntu kernel: [6.216427] __x64_sys_finit_module+0x1a/0x20 + Jun 9 09:06:02 ubuntu kernel: [6.216429] do_syscall_64+0x38/0x90 + Jun 9 09:06:02 ubuntu kernel: [6.216431] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] [Test] [Where problems could occur] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931509 Title: System hang with kernel general protection fault due to dell-wmi- sysman sysman_init failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931509] [NEW] System hang with kernel general protection fault due to dell-wmi-sysman sysman_init failure
Public bug reported: [Impact] [Fix] [Test] [Where problems could occur] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Impish) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux-oem-5.10 (Ubuntu Hirsute) ** No longer affects: linux-oem-5.10 (Ubuntu Impish) ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931509 Title: System hang with kernel general protection fault due to dell-wmi- sysman sysman_init failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup
Just fwi, this is in 4.0.6 which is up for SRU in LP: #1923232. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918955 Title: SRU network: fix LXC_NET_NONE cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1918955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923232] Re: SRU of LXC 4.0.6 to focal (upstream bugfix release)
This would fix LP: #1918955. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923232 Title: SRU of LXC 4.0.6 to focal (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1923232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage
** Changed in: bluez Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926548 Title: The gatt protocol has out-of-bounds read that leads to information leakage To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931243] Re: FTBFS in Impish on s390x
I've now released GPT fdisk version 1.0.8, which incorporates this bug fix, as well as a new feature in gdisk and sgdisk that enables correcting partition names that have already been corrupted by the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931243 Title: FTBFS in Impish on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931508] [NEW] ubuntu_kernel_selftests net linux ADT test failure with linux/5.11.0-20.21(unavailability of vmlinux)
Public bug reported: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-20.21 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210607_172050_4f1dc@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210609_182341_08ee8@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210607_180458_58645@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210607_180455_68857@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux ADT test failure with linux/5.11.0-20.21 + ubuntu_kernel_selftests net linux ADT test failure with linux/5.11.0-20.21(unavailability of vmlinux) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931508 Title: ubuntu_kernel_selftests net linux ADT test failure with linux/5.11.0-20.21(unavailability of vmlinux) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931506] Re: Display wakes up after locking screen (backlight on, black screen)
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1931506/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931506 Title: Display wakes up after locking screen (backlight on, black screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922186] Re: ibus very difficult to restart
Hey, how about getting a more constructive hobby than killing various important processes on your system? ;) More seriously: I'm not sure that "ibus restart" is intended to handle such situations. But please feel free to comment on the issue I submitted — the upstream maintainer hasn't attended to it yet. Or, probably better, submit an own upstream issue since they are separate things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922186 Title: ibus very difficult to restart To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1922186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931306] Re: bionic: postfix-dbgsym package lacks DWARF information
OK, I was able to determine that a rebuild of the package will likely solve this issue. Here's a PPA with the rebuild: https://launchpad.net/~sergiodj/+archive/ubuntu/postfix-debuginfo You can verify that the .debug files that were generated by this build contain the proper DWARF information that is needed to debug postfix. Note: I haven't tried to actually debug postfix using GDB; I just inspected the .debug file using eu-readelf. Also, if you want to enable the debug repository you will have to edit the corresponding source list and add the following line: deb http://ppa.launchpad.net/sergiodj/postfix-debuginfo/ubuntu focal main/debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931306 Title: bionic: postfix-dbgsym package lacks DWARF information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1931306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931507] [NEW] rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2
Public bug reported: Failure with new rpcbind version. Reverting to the previous version fixes it. Bad: rpcbind_0.2.3-0.6ubuntu0.18.04.2_amd64.deb Good: rpcbind_0.2.3-0.6ubuntu0.18.04.1_amd64.deb $ journalctl -u rpcbind.service Jun 09 23:41:00 MYSYSTEM systemd[1]: Started RPC bind portmap service. Jun 09 23:41:30 MYSYSTEM rpcbind[25504]: rpcbind: pmap_prot.c:50: xdr_pmap: Assertion `regs != NULL' failed. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Main process exited, code=killed, status=6/ABRT Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Failed with result 'signal'. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Service hold-off time over, scheduling restart. Jun 09 23:41:30 MYSYSTEM systemd[1]: rpcbind.service: Scheduled restart job, restart counter is at 477. Jun 09 23:41:30 MYSYSTEM systemd[1]: Stopped RPC bind portmap service. $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ uname -a Linux MYSYSTEM 5.4.0-1044-gcp #47~18.04.2-Ubuntu SMP Mon May 17 03:48:15 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy rpcbind rpcbind: Installed: 0.2.3-0.6ubuntu0.18.04.1 Candidate: 0.2.3-0.6ubuntu0.18.04.2 Version table: 0.2.3-0.6ubuntu0.18.04.2 500 500 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 0.2.3-0.6ubuntu0.18.04.1 100 100 /var/lib/dpkg/status 0.2.3-0.6 500 500 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: rpcbind (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931507 Title: rpcbind failing on 0.2.3-0.6ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1931507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838334] Re: aeskeyfind problem with constraints results
** Changed in: aeskeyfind (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838334 Title: aeskeyfind problem with constraints results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aeskeyfind/+bug/1838334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922186] Re: ibus very difficult to restart
+ Added the PPA and installed, now ibus stays "on" after openning the dialog. 👍️ - `ibus restart` still doesnt work: "Can't connect to IBus" Would be nice to also have a cmd-line option working for this case. FYI: Btw: here's another reason for quitting/restarting ibus: if I call `killall python3` on my machine, ibus/anthy (?) seems to get into an inconsistent state, which prevents input on certain apps. I guess the reason for this is somehow connected to what I've described earlier. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922186 Title: ibus very difficult to restart To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1922186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
This update is now available in all Ubuntu releases (except impish where it is currently still sitting in -proposed) - once it migrates to the release pocket of impish then it should get included in the daily ISO builds at http://cdimage.ubuntu.com/daily-live/current/ so hopefully a live image will be available in the next few days including this update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
Also seeing this failure on Hirsute & Groovy systemd armhf through ADT: https://autopkgtest.ubuntu.com/results/autopkgtest- hirsute/hirsute/armhf/s/systemd/20210609_190755_3e0ab@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest- groovy/groovy/armhf/s/systemd/20210609_190741_7c920@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1931088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931506] [NEW] Display wakes up after locking screen (backlight on, black screen)
Public bug reported: Software: Ubuntu 21.04, all updates installed (2021-06-10). Hardware: Xeon 1230 v3 (Haswell platform), 16GB ECC ram, AMDGPU (Polaris) Expected behaviour: When locking the screen - it turn off and stays off until I touch mouse or keyboard (I have turned off lock screen notifications) Actual behaviour: Display turns on, just a black screen (display backlight on) and sometimes I can see the mouse coursor. I have no idea what triggers it and don't really know where to look. What I have tried: Different dp outputs and X11 and Wayland. Nothing has helped. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amdgpu ** Tags added: amdgpu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931506 Title: Display wakes up after locking screen (backlight on, black screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1931088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931505] [NEW] systemd/247.3-3ubuntu3 ADT test failure with linux/5.11.0-20.21
*** This bug is a duplicate of bug 1931088 *** https://bugs.launchpad.net/bugs/1931088 Public bug reported: This is a scripted bug report about ADT failures while running systemd tests for linux/5.11.0-20.21 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/armhf/s/systemd/20210609_190755_3e0ab@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** This bug has been marked a duplicate of bug 1931088 boot-and-services tests fails in impish on armhf (248.3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931505 Title: systemd/247.3-3ubuntu3 ADT test failure with linux/5.11.0-20.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931380] Re: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child
As per Ken's comment on the associated forum post, this is actually now on stable, being phased out. You should automatically get the stable refresh within 24 hours, if you don't see it automatically, please wait 24 hours and then try again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931380 Title: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1931380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931315] Re: Please drop php-laravel-framework (and associated components), and movim from impish
** Also affects: php-laravel-framework (Ubuntu) Importance: Undecided Status: New ** Description changed: Please drop the Laravel eco-system from impish. This includes the following binary packages: - php-illuminate-auth - Illuminate Auth library component for PHP - php-illuminate-broadcasting - Illuminate Broadcasting library component for PHP - php-illuminate-bus - Illuminate Bus library component for PHP - php-illuminate-cache - Illuminate Cache library component for PHP - php-illuminate-config - Illuminate Config library component for PHP - php-illuminate-console - Illuminate Console library component for PHP - php-illuminate-container - Illuminate Container library component for PHP - php-illuminate-contracts - Illuminate Contracts library component for PHP - php-illuminate-cookie - Illuminate Cookie library component for PHP - php-illuminate-database - Illuminate Database library component for PHP - php-illuminate-encryption - Illuminate Encryption library component for PHP - php-illuminate-events - Illuminate Events library component for PHP - php-illuminate-filesystem - Illuminate Filesystem library component for PHP - php-illuminate-hashing - Illuminate Hashing library component for PHP - php-illuminate-http - Illuminate Http library component for PHP - php-illuminate-log - Illuminate Log library component for PHP - php-illuminate-mail - Illuminate Mail library component for PHP - php-illuminate-notifications - Illuminate Notifications library component for PHP - php-illuminate-pagination - Illuminate Pagination library component for PHP - php-illuminate-pipeline - Illuminate Pipeline library component for PHP - php-illuminate-queue - Illuminate Queue library component for PHP - php-illuminate-redis - Illuminate Redis library component for PHP - php-illuminate-routing - Illuminate Routing library component for PHP - php-illuminate-session - Illuminate Session library component for PHP - php-illuminate-support - Illuminate Support library component for PHP - php-illuminate-translation - Illuminate Translation library component for PHP - php-illuminate-validation - Illuminate Validation library component for PHP - php-illuminate-view - Illuminate View library component for PHP - php-laravel-framework - web application framework for PHP - php-laravel-lumen-framework - micro-framework for building web applications in PHP - movim - + php-illuminate-auth + php-illuminate-broadcasting + php-illuminate-bus + php-illuminate-cache + php-illuminate-config + php-illuminate-console + php-illuminate-container + php-illuminate-contracts + php-illuminate-cookie + php-illuminate-database + php-illuminate-encryption + php-illuminate-events + php-illuminate-filesystem + php-illuminate-hashing + php-illuminate-http + php-illuminate-log + php-illuminate-mail + php-illuminate-notifications + php-illuminate-pagination + php-illuminate-pipeline + php-illuminate-queue + php-illuminate-redis + php-illuminate-routing + php-illuminate-session + php-illuminate-support + php-illuminate-translation + php-illuminate-validation + php-illuminate-view + php-laravel-framework + php-laravel-lumen-framework + movim [Discussion] - Movim is a distributed social network built on XMPP. + Movim is a distributed social network built on XMPP. Laravel is a PHP-based, commercially-supported web framework that builds atop the Symfony web framework, providing a number of "1st-party" plugins for billing, auth, browser testing, etc. Laravel 6.20 was introduced in Debian ubuntu in Dec 2020, and auto- sync'd into Ubuntu hirsute at that time. (Current upstream is releasing Laravel 8.45, however 6.x is their LTS series, with security support through Sep. 2022.) For Ubuntu impish we are introducing PHP 8.0, and updating a number of PHP ecosystem pieces to their PHP 8 versions. Technically, Laravel 6.20 indicates support for PHP 8.0 itself (https://github.com/laravel/framework/commit/897a47136c2da2fdc7e19cee89c2f3a514192dee), however Laravel 6.20 appears to not be compatible with some of the other ecosystem pieces being introduced, and looks like significant work will be needed to get it transitioned. Upstream recommends to their new users to install Laravel via their Docker container [https://laravel.com/docs/8.x/installation]. Experienced users are directed to use PHP's package manager, 'composer', to install Laravel's PHP components from the web. 3rd party install guides found via google also walk users through using composer to install laravel, rather than install via apt. In general it appe
[Bug 1838334] Re: aeskeyfind problem with constraints results
** Bug watch added: Debian Bug tracker #989179 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989179 ** Also affects: aeskeyfind (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989179 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838334 Title: aeskeyfind problem with constraints results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aeskeyfind/+bug/1838334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916066] Re: Focal update: v5.4.97 upstream stable release
I have Kingston A2000 SSD. I found that this patch fixed: " nvme-pci: avoid the deepest sleep state on Kingston A2000 SSDs" I would like to know if this patch is also aplied in the newest version of kernel 5.8 for Ubuntu 20.04.2 LTS? Should I install latest 5.4 kernel instead 5.8 or I can use 5.8 because this patch was applied also in this kernel version? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916066 Title: Focal update: v5.4.97 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931380] Re: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child
A fix for this is in the beta channel AIUI, you can refresh to try out the fix with: ``` snap refresh snap-store --beta --ignore-running ``` You can omit the --ignore-running if you do not have refresh app awareness enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931380 Title: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1931380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931498] Re: cannot upgrade from 16 to 18
** Tags added: xenial2bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931498 Title: cannot upgrade from 16 to 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931499] Re: cannot upgrade from 16 to 18
** Tags added: xenial2bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931499 Title: cannot upgrade from 16 to 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931383] Re: ipp-usb ftbfs with lto
It looks like Go compiler bug (or, more strictly, cgo bug; cgo is a tool that comes with Go compiler and allows direct calling of C functions from Go) https://github.com/golang/go/issues/43830 The solution could be to build without LTO. In general, LTO should not make a lot of sense for Go programs. ** Bug watch added: github.com/golang/go/issues #43830 https://github.com/golang/go/issues/43830 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931383 Title: ipp-usb ftbfs with lto To manage notifications about this bug go to: https://bugs.launchpad.net/golang/+bug/1931383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] journalctl_deamon-reload
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-09 17:14 EDT--- ** Attachment added: "journalctl_deamon-reload" https://bugs.launchpad.net/bugs/1929657/+attachment/5503691/+files/journalctl_daemon-reload.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-09 17:17 EDT--- Attaching output of 'journalctl -b -u systemd-networkd --no-pager' after 'systemctl daemon-reload && systemctl restart systemd-networkd' execution File -> journalctl_deamon-reload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931470] Re: wrong icon path in desktop file
The attachment "Proposed solution to this bug" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931470 Title: wrong icon path in desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltris/+bug/1931470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931501] [NEW] Stack trace when --help flag added to the end of a command
Public bug reported: If I add --help to the end of an enable command, I get a stack trace: ``` ubuntu@pro1604:~$ sudo ua enable fips --help ERROR:root:Unhandled exception, please file a bug Traceback (most recent call last): File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 937, in wrapper return func(*args, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 987, in main args = parser.parse_args(args=cli_arguments) File "/usr/lib/python3.5/argparse.py", line 1735, in parse_args args, argv = self.parse_known_args(args, namespace) File "/usr/lib/python3.5/argparse.py", line 1767, in parse_known_args namespace, args = self._parse_known_args(args, namespace) File "/usr/lib/python3.5/argparse.py", line 1955, in _parse_known_args positionals_end_index = consume_positionals(start_index) File "/usr/lib/python3.5/argparse.py", line 1932, in consume_positionals take_action(action, args) File "/usr/lib/python3.5/argparse.py", line 1841, in take_action action(self, namespace, argument_values, option_string) File "/usr/lib/python3.5/argparse.py", line 1138, in __call__ subnamespace, arg_strings = parser.parse_known_args(arg_strings, None) File "/usr/lib/python3.5/argparse.py", line 1767, in parse_known_args namespace, args = self._parse_known_args(args, namespace) File "/usr/lib/python3.5/argparse.py", line 1973, in _parse_known_args start_index = consume_optional(start_index) File "/usr/lib/python3.5/argparse.py", line 1913, in consume_optional take_action(action, args, option_string) File "/usr/lib/python3.5/argparse.py", line 1841, in take_action action(self, namespace, argument_values, option_string) File "/usr/lib/python3.5/argparse.py", line 1025, in __call__ parser.print_help() File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 93, in print_help super().print_help(file=file) File "/usr/lib/python3.5/argparse.py", line 2367, in print_help self._print_message(self.format_help(), file) File "/usr/lib/python3.5/argparse.py", line 2351, in format_help return formatter.format_help() File "/usr/lib/python3.5/argparse.py", line 287, in format_help help = self._root_section.format_help() File "/usr/lib/python3.5/argparse.py", line 217, in format_help func(*args) File "/usr/lib/python3.5/argparse.py", line 217, in format_help func(*args) File "/usr/lib/python3.5/argparse.py", line 524, in _format_action help_text = self._expand_help(action) File "/usr/lib/python3.5/argparse.py", line 611, in _expand_help return self._get_help_string(action) % params TypeError: unsupported operand type(s) for %: 'tuple' and 'dict' Unexpected error(s) occurred. For more details, see the log: /var/log/ubuntu-advantage.log To file a bug run: ubuntu-bug ubuntu-advantage-tools ``` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-advantage-tools 26.3~16.04.1 ProcVersionSignature: User Name 4.15.0-1113.126~16.04.1-azure 4.15.18 Uname: Linux 4.15.0-1113-azure x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Wed Jun 9 21:14:41 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-advantage-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages uec-images xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931501 Title: Stack trace when --help flag added to the end of a command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1931501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931488] Re: Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931488 Title: Kubuntu: No more file search results in Krunner or Kickoff after Hirsute Upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1931488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta/5.4.0.75.78)
All autopkgtests for the newly accepted linux-meta (5.4.0.75.78) for focal have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, arm64, armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931498] [NEW] cannot upgrade from 16 to 18
Public bug reported: cannot find ubuntu minimal ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.32 ProcVersionSignature: Ubuntu 4.4.0-210.242-powerpc64-smp 4.4.262 Uname: Linux 4.4.0-210-powerpc64-smp ppc64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: powerpc CrashDB: ubuntu Date: Wed Jun 9 13:27:45 2021 InstallationDate: Installed on 2017-10-11 (1336 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2021-06-09 (0 days ago) VarLogDistupgradeAptlog: Log time: 2021-06-09 13:26:00.692081 Log time: 2021-06-09 13:26:19.002197 Log time: 2021-06-09 13:27:08.049965 Log time: 2021-06-09 13:28:01.390176 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug dist-upgrade powerpc xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931498 Title: cannot upgrade from 16 to 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931497] Re: Patch To Fix Bug in the Linux Block Layer Responsible For Merging BIOs
** Description changed:
There is a bug in the Linux block layer responsible for merging BIOs
that go across the page boundary. This bug was introduced in Linux 5.1
when the block layer BIO page tracking is enhanced to support multiple
pages.
Without this patch, data corruption can occur. The change to the kernel
block layer in Linux 5.1 changes the way multiple pages are merged to a
single block I/O descriptor, and how contiguous block I/O descriptors
are merged with previous descriptors.
If contiguous block I/O requests cross a page boundary of 4k, defined by
the hv_storvsc driver, the new block merge process can create two pages
of block I/O requests (the latter page with an offset) that refer to the
same physical sector on disk. This page list is then assembled for the
SCSI generic driver.
In the above scenario, when the block I/O request sizes are 512 bytes,
the Azure LIS driver (hv_storvsc module) is not able to correctly parse
the page array from the SCSI generic driver due to this bug in Linux
block layer and creates a potential overflow of offset I/O requests and
corruption of data on disk.
Mitigation of data loss is proven with filesystems with block size 4k.
When block I/O requests are of sizes 4k or multiples of 4k, they are the
page aligned in the memory and are not affected by the block I/O merging
algorithm introduced in Linux 5.1. Most modern file systems use 4k I/O
block size by default, thus mitigating this problem.
We have submitted a patch to Linux mainline kernel to fix this:
- https://patchwork.kernel.org/project/linux-
- block/patch/1623094445-22332-1-git-send-email-lon...@linuxonhyperv.com/
+ https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-
+ block.git/commit/?h=for-next&id=c9c9762d4d44dcb1b2ba90cfb4122dc11ceebf31
c9c9762d4d44 ("block: return the correct bvec when checking for gaps")
Please include this patch in any supported kernels that are 5.1 or
later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931497
Title:
Patch To Fix Bug in the Linux Block Layer Responsible For Merging
BIOs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1931497/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931499] [NEW] cannot upgrade from 16 to 18
Public bug reported: cannot find ubuntu minimal ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.32 ProcVersionSignature: Ubuntu 4.4.0-210.242-powerpc64-smp 4.4.262 Uname: Linux 4.4.0-210-powerpc64-smp ppc64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: powerpc CrashDB: ubuntu Date: Wed Jun 9 13:27:45 2021 InstallationDate: Installed on 2017-10-11 (1336 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2021-06-09 (0 days ago) VarLogDistupgradeAptlog: Log time: 2021-06-09 13:26:00.692081 Log time: 2021-06-09 13:26:19.002197 Log time: 2021-06-09 13:27:08.049965 Log time: 2021-06-09 13:28:01.390176 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug dist-upgrade powerpc xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931499 Title: cannot upgrade from 16 to 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931497] [NEW] Patch To Fix Bug in the Linux Block Layer Responsible For Merging BIOs
Public bug reported:
There is a bug in the Linux block layer responsible for merging BIOs
that go across the page boundary. This bug was introduced in Linux 5.1
when the block layer BIO page tracking is enhanced to support multiple
pages.
Without this patch, data corruption can occur. The change to the kernel
block layer in Linux 5.1 changes the way multiple pages are merged to a
single block I/O descriptor, and how contiguous block I/O descriptors
are merged with previous descriptors.
If contiguous block I/O requests cross a page boundary of 4k, defined by
the hv_storvsc driver, the new block merge process can create two pages
of block I/O requests (the latter page with an offset) that refer to the
same physical sector on disk. This page list is then assembled for the
SCSI generic driver.
In the above scenario, when the block I/O request sizes are 512 bytes,
the Azure LIS driver (hv_storvsc module) is not able to correctly parse
the page array from the SCSI generic driver due to this bug in Linux
block layer and creates a potential overflow of offset I/O requests and
corruption of data on disk.
Mitigation of data loss is proven with filesystems with block size 4k.
When block I/O requests are of sizes 4k or multiples of 4k, they are the
page aligned in the memory and are not affected by the block I/O merging
algorithm introduced in Linux 5.1. Most modern file systems use 4k I/O
block size by default, thus mitigating this problem.
We have submitted a patch to Linux mainline kernel to fix this:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-
block.git/commit/?h=for-next&id=c9c9762d4d44dcb1b2ba90cfb4122dc11ceebf31
c9c9762d4d44 ("block: return the correct bvec when checking for gaps")
Please include this patch in any supported kernels that are 5.1 or
later.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931497
Title:
Patch To Fix Bug in the Linux Block Layer Responsible For Merging
BIOs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1931497/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931179] Re: /usr/lib/python3/dist-packages/genshi/filters/i18n.py:352: SyntaxWarning: "is not" with a literal. Did you mean "!="?
Was fixed in 0.7.3 and in debian with 0.7.4-2. Needs this patch: https://salsa.debian.org/python- team/packages/genshi/-/blob/debian/0.7.4-2/debian/patches/fix-syntax- warning.patch But yeah, it looks innocuous. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931179 Title: /usr/lib/python3/dist-packages/genshi/filters/i18n.py:352: SyntaxWarning: "is not" with a literal. Did you mean "!="? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/genshi/+bug/1931179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
