[Bug 1915786] Please test proposed package
Hello Chris, or anyone else affected, Accepted nova into ussuri-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:ussuri-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-ussuri-needed to verification-ussuri-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-ussuri-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/ussuri Status: New => Fix Committed ** Tags added: verification-ussuri-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915786 Title: [SRU] Ussuri stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573192] Re: apparmor prevents using SCSI hostdevs
Hi Ermac, yeah as usual if one has a special case not covered by the automatism of libvirt/apparmor as outlined on https://ubuntu.com/server/docs/virtualization-libvirt section "Apparmor isolation" adding rules like that will help. But that is limited to either global rules (valid for all guests, which means less than preferable isolation) or a lot of manual - and thereby error prone - work. Thanks for making me re-visit this long open case (hi Simon btw). Looking at it with todays POV I think it might be resolved if I'd ever get to implement bug 1677398. That would put it after the realization of storage which should cover this as well I'd hope. I'll add a hint there to recheck this bug in that regard once we have experimental code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573192 Title: apparmor prevents using SCSI hostdevs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1573192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677398] Re: Apparmor prevents using storage pools and hostdev networks
Also check bug 1573192 if it might be resolved by this as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677398 Title: Apparmor prevents using storage pools and hostdev networks To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1677398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916716] Re: pipewire-media-session crashed with SIGSEGV in refresh_auto_default_nodes()
Even after update the bug appears again here today -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916716 Title: pipewire-media-session crashed with SIGSEGV in refresh_auto_default_nodes() To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1916716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902236] Re: Duplicated root and nobody returned by getent on Focal
Verification procedure on Focal: $ lxc launch focal lp1902236-f Creating lp1902236-f Starting lp1902236-f $ lxc exec lp1902236-f bash root@lp1902236-f:~# getent passwd | grep root root:x:0:0:root:/root:/bin/bash root:x:0:0:root:/root:/bin/sh root@lp1902236-f:~# getent passwd | grep nobody nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin nobody:x:65534:65534:nobody:/:/usr/sbin/nologin # Enable proposed root@lp1902236-f:~# vim /etc/apt/sources.list root@lp1902236-f:~# apt update && apt-get dist-upgrade Calculating upgrade... Done The following packages will be upgraded: libnss-systemd (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) libpam-systemd (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) libsystemd0 (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) libudev1 (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) systemd (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) systemd-sysv (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) systemd-timesyncd (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) udev (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) 8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 5845 kB of archives. After this operation, 15.4 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libnss-systemd amd64 245.4-4ubuntu3.5 [95.8 kB] Get:2 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 udev amd64 245.4-4ubuntu3.5 [1366 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libudev1 amd64 245.4-4ubuntu3.5 [81.2 kB] Get:4 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 systemd-sysv amd64 245.4-4ubuntu3.5 [10.3 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.5 [28.1 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libpam-systemd amd64 245.4-4ubuntu3.5 [186 kB] Get:7 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 systemd amd64 245.4-4ubuntu3.5 [3805 kB] Get:8 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libsystemd0 amd64 245.4-4ubuntu3.5 [274 kB] Fetched 5845 kB in 2s (2391 kB/s) ... Setting up libnss-systemd:amd64 (245.4-4ubuntu3.5) ... Setting up libpam-systemd:amd64 (245.4-4ubuntu3.5) ... Processing triggers for libc-bin (2.31-0ubuntu9.2) ... Processing triggers for dbus (1.12.16-2ubuntu2.1) ... root@lp1902236-f:~# getent passwd | grep root root:x:0:0:root:/root:/bin/bash root@lp1902236-f:~# getent passwd | grep nobody nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902236 Title: Duplicated root and nobody returned by getent on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1902236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881522] Re: vtun not running on ubuntu 20.04 LTS
Look like the build process has missing `HAVE_WORKING_FORK` at the build stage. For me, the issue was fixed on by rebuild from the source (so the source is correct), probably original build process affects HAVE_WORKING_FORK Unfortunately, I have no idea, how to fix the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881522 Title: vtun not running on ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/1881522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918137] [NEW] Ubuntu 21.04 Hirsute: i386 package cleaning process seems incomplete
Public bug reported: Hello, - The i386 package cleaning process seems incomplete: There are still i386 boot images for Ubuntu 20.10 or Ubuntu 21.04 Hirsute Hippo: http://archive.ubuntu.com/ubuntu/dists/hirsute/main/installer-i386/current/images/netboot/ - The i386 architecture is always listed for Ubuntu 21.04 Hirsute Hippo: https://launchpad.net/ubuntu/+mirror/bouygues-telecom - Files in the "indices" folder (http://archive.ubuntu.com/ubuntu/indices/) are not cleaned up when a distribution is deleted from the archive: there are files from Ubuntu 5.04: Hoary Hedgehog! In order to reduce the environmental footprint of the mirrors which contains these unnecessary files, which are copied in thousands of copies, would it be possible to do some cleaning? Is-it necessary to keep in the mirrors Ubuntu 12.04 LTS Precise Pangolin? Ubuntu Extended Security Maintenance ended since April 2019 and the mirror files have not changed since may 2018: http://archive.ubuntu.com/ubuntu/dists/precise-security/ Would it be possible to move unsupported versions, like Ubuntu 12.04, to http://old-releases.ubuntu.com/ubuntu/ ? Thank you in advance for a little cleaning, which might avoid upgrades to the mirror servers (actual size of Ubuntu archives: 1558 GB). Regards, Vivien. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: cleaning hippo i386 mirror ** Attachment added: "There are still i386 boot images for Ubuntu 21.04 Hirsute Hippo" https://bugs.launchpad.net/bugs/1918137/+attachment/5474505/+files/hirsute_i386.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918137 Title: Ubuntu 21.04 Hirsute: i386 package cleaning process seems incomplete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1918137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573192] Re: apparmor prevents using SCSI hostdevs
Thanks for taking the time to file this bug. I am not able to reproduce this bug since I do not have an scsi device to test it. I am subscribing Christian, he might have a better idea on how to address this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573192 Title: apparmor prevents using SCSI hostdevs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1573192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903864] Re: qemu-system-x86_64: -device tpm-tis, tpmdev=tpm-tpm0, id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0'
Hey Christian, thanks for taking a look at this, indeed this is somehow confinement related and I can make it work by removing the apparmor profile for the swtpm snap. I guess I assumed that this bug was related to that since it had the same exact error message and I definitely remembered doing this setup before only like a month or two ago on Groovy and the swtpm-mvo snap has not been updated in ages so I assumed that updating qemu was to blame. What I actually find now is that it seems actually to be due to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1849753, since what changed for me to trigger my bug around swtpm and qemu is that I started using VS Code as a snap, and so when I run my qemu commands they are effectively being run from inside a classic snap, and swtpm is a strict snap so it cannot inherit all the FD's that VS code has open. If I run from a normal terminal shell and not from within the VS Code integrated terminal the setup works the same again. So all that is to say that indeed there is no regression here, thanks for the insight that this is confinement related, I should be able to easily work around this for my purposes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903864 Title: qemu-system-x86_64: -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1903864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917609] Re: [Regression] ubuntu_bpf failed to build on Groovy
** Tags removed: kqa-blocker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917609 Title: [Regression] ubuntu_bpf failed to build on Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906684] Re: [SRU] libreoffice 6.4.7 for Focal
** Changed in: libreoffice (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906684 Title: [SRU] libreoffice 6.4.7 for Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1906684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918134] [NEW] LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key
Public bug reported: To allow decoupling of nvidia-graphics-drivers- streams and versions from the underlying kernel versions we wish to be able to sign new kernel modules into an existing kernel after the fact. Under bug #1898716 we added support for an Ubuntu Modules signing key certificate. Rebuild the LRM package to make use of this new signature. This involves splitting the LRM package into three. linux-restricted- modules first builds the nvidia-graphics-drivers-* we require signed. linux-restricted-generate then consumes the .o's produced in that build and forms a signing custom binary upload for this. linux-restricted- signatures then consumes the signing result from the LRG upload and expresses clean redistributible signatures which are consumed by LRM at installation time. LRG must be embargoed as it (necessarily) generates fully formed .ko files for signing. Additional process is added to the kernel build life-cycle to handle the privacy requirements of the LRG/LRS interaction. ** Affects: linux-restricted-modules (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/1918134 Title: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1918134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cron (Ubuntu Groovy) 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/1779767 Title: Default cron PATH does not include /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: anacron (Ubuntu Groovy) 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/1779767 Title: Default cron PATH does not include /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cron (Ubuntu Focal) 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/1779767 Title: Default cron PATH does not include /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: anacron (Ubuntu Focal) 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/1779767 Title: Default cron PATH does not include /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cron (Ubuntu Bionic) 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/1779767 Title: Default cron PATH does not include /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: anacron (Ubuntu Bionic) 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/1779767 Title: Default cron PATH does not include /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: anacron (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/1779767 Title: Default cron PATH does not include /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917812] Re: extracting archives from within nautilus omits subfolders
** Also affects: gnome-autoar (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-autoar (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-autoar (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gnome-autoar (Ubuntu Hirsute) Importance: High Status: Fix Released ** Also affects: gnome-autoar (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: gnome-autoar (Ubuntu Xenial) Status: New => In Progress ** Changed in: gnome-autoar (Ubuntu Bionic) Status: New => In Progress ** Changed in: gnome-autoar (Ubuntu Xenial) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: gnome-autoar (Ubuntu Bionic) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: gnome-autoar (Ubuntu Focal) Status: New => In Progress ** Changed in: gnome-autoar (Ubuntu Focal) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: gnome-autoar (Ubuntu Groovy) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: gnome-autoar (Ubuntu Groovy) Status: New => In Progress ** No longer affects: gnome-autoar (Ubuntu Xenial) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917812 Title: extracting archives from within nautilus omits subfolders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/+bug/1917812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918109] Re: lttng-modules-dkms: build errors with linux >= 5.11
** 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/1918109 Title: lttng-modules-dkms: build errors with linux >= 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1918109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917812] Re: extracting archives from within nautilus omits subfolders
The follow up fix is in the 0.3 update in hirsute which is why it works there, other series still need to be fixed ** Changed in: gnome-autoar (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/1917812 Title: extracting archives from within nautilus omits subfolders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/+bug/1917812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917812] Re: extracting archives from within nautilus omits subfolders
Checking the details, that's a regression from the recent gnome-autoar security update, the fix from https://gitlab.gnome.org/GNOME/gnome- autoar/-/commit/cc4e8b7c is needed ** Package changed: nautilus (Ubuntu) => gnome-autoar (Ubuntu) ** Changed in: gnome-autoar (Ubuntu) Importance: Low => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917812 Title: extracting archives from within nautilus omits subfolders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/+bug/1917812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852290] Re: DS8870 path fails to restore during DS8K EI (error injection) test on z15 LPAR
** Changed in: multipath-tools (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntu-z-systems 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/1852290 Title: DS8870 path fails to restore during DS8K EI (error injection) test on z15 LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1852290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918131] Re: pipewire-media-session crashed with SIGSEGV
*** This bug is a duplicate of bug 1916716 *** https://bugs.launchpad.net/bugs/1916716 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1916716, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1918131/+attachment/5474493/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1918131/+attachment/5474495/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1918131/+attachment/5474498/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1918131/+attachment/5474499/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1918131/+attachment/5474500/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1918131/+attachment/5474501/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1918131/+attachment/5474502/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1916716 pipewire-media-session crashed with SIGSEGV in refresh_auto_default_nodes() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918131 Title: pipewire-media-session crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1918131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918122] Re: Background picture not changed correctly
** 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/1918122 Title: Background picture not changed correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1918122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852290] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-03-08 06:50 EDT--- IBM Bugzilla status->closed, Problem could currently not reproduced. Once showing up again, new ticket will be created. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852290 Title: DS8870 path fails to restore during DS8K EI (error injection) test on z15 LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1852290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897784] Re: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData
Upstream bug is https://bugs.documentfoundation.org/show_bug.cgi?id=140700 ** Bug watch added: Document Foundation Bugzilla #140700 https://bugs.documentfoundation.org/show_bug.cgi?id=140700 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918033] Re: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor))
$ gsettings get org.gnome.shell enabled-extensions @as [] All extensions are uninstalled, and the problem still occurs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918033 Title: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter- stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918128] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918128 Title: Touchpad only works when it wants on Ubuntu Budgie 20.10 system menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801588] Re: Syntax error when running python rtupdate hooks for python3.7
Fixed long time ago, closing ** Changed in: pyzo (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/1801588 Title: Syntax error when running python rtupdate hooks for python3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyzo/+bug/1801588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)
systemd-resolved still crashing more-or-less every 10 minutes. Some update arrived (I installed it 15 minutes ago) - 245.4-4ubuntu3.5~202103051349~ubuntu20.04.1 - it also crashed few mins since the installation. I tried various approaches to kernel.core_pattern, but nothing is gathered. As I understand, the way it aborts itself doesn't lead to core creation. There are few failing assertions leading to the failure (stats for the version mentioned in #12) a) Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at src/resolve /resolved-dns-query.c:520, function dns_query_complete(). Aborting Most frequent one, 753 times this week b) Assertion '*_head == _item' failed at src/resolve/resolved-dns- query.c:372, function dns_query_free(). Aborting. 49 times this week c) Assertion 'p->n_ref > 0' failed at src/libsystemd/sd-event/sd- event.c:1912, function sd_event_source_unref(). Aborting. 9 times this week d) Assertion 'q->auxiliary_for->n_auxiliary_queries > 0' failed at src/resolve/resolved-dns-query.c:370, function dns_query_free(). Aborting 6 times this week e) Assertion 'p->n_ref > 0' failed at src/resolve/resolved-dns- question.c:33, function dns_question_unref(). Aborting. 2 times this week -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906331 Title: systemd-resolve crashes fairly often (and reports various assertions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918128] [NEW] Touchpad only works when it wants on Ubuntu Budgie 20.10 system menu
Public bug reported: I'm facing strange issue when I try to scroll in system menu with my touchpad. It only works for few moments after booting the OS, after that it seems like the touchpad is locked. But I don't have any power or control over my touchpad to do something similar... What you expected to happen: System menu should scroll with my touchpad gestures too. What happened instead: It seems locked when trying to scroll after some time. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abnilson991 F pulseaudio /dev/snd/pcmC0D0p: abnilson991 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon Mar 8 13:34:38 2021 InstallationDate: Installed on 2021-03-04 (3 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP 250 G6 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=71d4b172-c19f-45e6-8193-e5ac6374bb3a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux StagingDrivers: atomisp_gmin_platform atomisp_ov5693 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2019 dmi.bios.release: 15.52 dmi.bios.vendor: Insyde dmi.bios.version: F.52 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832C dmi.board.vendor: HP dmi.board.version: 25.53 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 25.53 dmi.modalias: dmi:bvnInsyde:bvrF.52:bd03/04/2019:br15.52:efr25.53:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832C:rvr25.53:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G6 Notebook PC dmi.product.sku: 1WY14EA#ACQ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy staging ** Description changed: I'm facing strange issue when I try to scroll in system menu with my touchpad. It only works for few moments after booting the OS, after that it seems like the touchpad is locked. - But I don't have any power or control over my touchpad. - + But I don't have any power or control over my touchpad to do something + similar... What you expected to happen: System menu should scroll with my touchpad gestures too. What happened instead: It seems locked when trying to scroll after some time. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: abnilson991 F pulseaudio - /dev/snd/pcmC0D0p: abnilson991 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: abnilson991 F pulseaudio + /dev/snd/pcmC0D0p: abnilson991 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon Mar 8 13:34:38 2021 InstallationDate: Installed on 2021-03-04 (3 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP 250 G6 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=71d4b172-c19f-45e6-8193-e5ac6374bb3a ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.8.0-44-generic N/A - linux-backports-modules-5.8.0-44-generic N/A - linux-firmware1.190.3 + linux-restricted-modules-5.8.0-44-generic N/A + linux-backports-modules-5.8.0-44-generic N/A + linux-firmware1.190.3 SourcePackage: linux StagingDrivers: atomisp_gmin_platform atomisp_ov5693 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2019 dmi.bios.release: 15.52 dmi.bios.vendor: Insyde dmi.bios.version: F.52 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832C dmi.board.vendor: HP dmi.board.version: 25.53 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 25.53 dmi.modalias: dmi:bvnInsyde:bvrF.52:bd03/04/2019:br15.52:efr25.53:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832C:rvr25.53:cvnHP:ct10:cvrChassisVersion:
[Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
The same. HP ZBook x360 G5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
** 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/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
Forwarded to upstream open-vm-tools as https://github.com/vmware/open-vm-tools/issues/500 Uploaded a fix for Ubuntu in https://launchpad.net/ubuntu/+source/open-vm-tools/2:11.2.5-2ubuntu1 ** Bug watch added: github.com/vmware/open-vm-tools/issues #500 https://github.com/vmware/open-vm-tools/issues/500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916705 Title: glib2.0 >=2.67.3 breaks include from an extern C context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900775] Fix included in openstack/cinder 17.1.0
This issue was fixed in the openstack/cinder 17.1.0 release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900775 Title: Cinder fails to create image-based volume if mirroring is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-rbd-mirror/+bug/1900775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917774] Re: package bind9 1:9.9.5.dfsg-3ubuntu0.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. On upgrading a service this service has to be restarted to pick up the fixes. Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration. But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state. Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart. Therefore the update of that package has to consider itself incomplete. Depending on your particular case there are two solutions: - either remove the offending package if you don't want to continue using it. - Or if you do want to keep it please fix the configuration so that re-starting the service will work. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: bind9 (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/1917774 Title: package bind9 1:9.9.5.dfsg-3ubuntu0.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1917774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917774] Re: package bind9 1:9.9.5.dfsg-3ubuntu0.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hi, this seems to be a service that fails on upgrade. Setting up bind9 (1:9.9.5.dfsg-3ubuntu0.19) ... * Starting domain name service... bind9 fail In the logs I can further see: Mar 4 09:14:52 named[3701]: loading configuration from '/etc/bind/named.conf' Mar 4 09:14:52 named[3701]: /etc/bind/named.conf.options:22: expected IP address near 'dnssec-validation' Mar 4 09:14:52 named[3701]: loading configuration: unexpected token So it seems there is a local modification to that config file that is breaking the server restart. I checked and none of the recent updates to bind9 has messed with conffile handling in any way. So most likely this isn't a regression due to the upgrade, but instead a config file that was in a bad state and the package upgrade now makes you aware of that. Please look into your config file, fix the issue and restart named. Once that works, the package upgrade will likely work as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917774 Title: package bind9 1:9.9.5.dfsg-3ubuntu0.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1917774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918127] Re: gnome-shell crash when using panel
Problem occurs on Wayland as well as Xorg. Please let me know what kind of info you need. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918127 Title: gnome-shell crash when using panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916230] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-03-08 06:19 EDT--- IBM bugzilla status-> closed, Fix Released by hirsuite -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916230 Title: [Ubuntu 21.04] QEMU is missing virtio-9p-ccw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1916230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918127] [NEW] gnome-shell crash when using panel
Public bug reported: Whenever I perform an action in the Gnome Panel (Activate a VPN has 100% failure-rate, but I have seen it when clearing notifications and other things too), the entire session crashes and I'm back at login. I'm running gnome-session on Hirsute. journalctl /usr/bin/gnome-shell shows the following just before the crash: Mar 08 07:02:40 localhost gnome-shell[67382]: ** Mar 08 07:02:40 localhost gnome-shell[67382]: Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) Mar 08 07:02:40 localhost gnome-shell[67382]: Bail out! Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) The problem is 100% reproducible. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute ** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918127 Title: gnome-shell crash when using panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903312] Re: Ubiquity not selecting correct timezone when connected to Internet
Testing daily build Xubuntu Hirsute 20210308 Test machine : Lenovo L450 i5-5200U,8GB,Intel HD5500,WiFi/Ethernet,Bluetooth,500GB hd I am still receiving this bug - please note that this only occurs when using WiFi connection - ethernet connection to the Internet - all normal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903312 Title: Ubiquity not selecting correct timezone when connected to Internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1903312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918122] [NEW] Background picture not changed correctly
Public bug reported: I have changed my background picture to a external picture everything is good but when I changed my screen to the bottom one(super+pate down) my prevision background coming back ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:13:07 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1002:67ef] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1458:22de] InstallationDate: Installed on 2021-03-01 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2e09764a-1fb8-4580-868d-0660951ab9a2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2010 dmi.bios.release: 22.9 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2209 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2209:bd03/11/2010:br22.9:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "a screen record of bug" https://bugs.launchpad.net/bugs/1918122/+attachment/5474443/+files/simplescreenrecorder-2021-03-08_14.33.19.mkv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918122 Title: Background picture not changed correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1918122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906684] Re: [SRU] libreoffice 6.4.7 for Focal
** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Rico Tzschichholz (ricotz) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906684 Title: [SRU] libreoffice 6.4.7 for Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1906684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918120] [NEW] dpkg/debhelper building with noudebs by default broken linitian
Public bug reported: dpkg/debhelper building with noudebs by default broken linitian New dpkg/debhelper in ubunty imply "DEB_BUILD_OPTIONS=noudeb" build profile, which makes lintian FTBFS and fail its autopkgtest, as somehow when building udebs as part of the testsuite doesn't produce them, and everything is sad. This is now holding up migrations. Please mark linitian as badtest, i will try to fix the next upload of lintian to work correctly with now implied `noudeb` build profile. Please badtest current lintian in hirsute-release & hirsute-proposed. ** Affects: lintian (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/1918120 Title: dpkg/debhelper building with noudebs by default broken linitian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1918120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474442/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474441/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474440/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474439/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474438/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474437/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474436/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474435/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474434/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474433/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474432/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474431/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474430/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474428/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474429/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474427/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474426/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917624] Re: no sound at all
apport information ** Tags added: apport-collected ** Description changed: 1. Description: Ubuntu 20.04.2 LTS Release: 20.04 2. alsa-base 1.0.25+dfsg-0ubuntu5 3. I hope can hear sound from my laptop speaker 4. I can not hear any sound from my speaker + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + HibernationDevice: RESUME=UUID=a41d1dde-25d3-4612-9f49-5fbccfc5c9bb + InstallationDate: Installed on 2017-08-15 (1301 days ago) + InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. USB2.0 VGA UVC WebCam + Bus 001 Device 004: ID 13d3:3423 IMC Networks + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: ASUSTeK COMPUTER INC. X441SA + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=cf46127a-fce8-4b98-bb92-7431d2167216 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-66-generic N/A + linux-backports-modules-5.4.0-66-generic N/A + linux-firmware1.187.9 + Tags: focal + Uname: Linux 5.4.0-66-generic x86_64 + UpgradeStatus: Upgraded to focal on 2021-02-11 (24 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/08/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: X441SA.301 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: X441SA + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: ATN12345678901234567 + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: X + dmi.product.name: X441SA + dmi.product.sku: ASUS-NotebookSKU + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1917624/+attachment/5474425/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917624 Title: no sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers
LGTM! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883447 Title: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1883447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918110] Re: overlay_map.dtb is in wrong location
** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918110 Title: overlay_map.dtb is in wrong location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1918110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918110] Re: overlay_map.dtb is in wrong location
The kernel package seems correct: $ find /lib/firmware/ -name overlay_map.dtb /lib/firmware/5.8.0-1006-raspi/device-tree/overlays/overlay_map.dtb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918110 Title: overlay_map.dtb is in wrong location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1918110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918110] Re: overlay_map.dtb is in wrong location
flash-kernel treats all dtb files as - well - dtbs and copies them to boot/firmware. I guess we need an exception for overlay_map.dtb? Or rename overlay_map.dtb to overlay_map.dtbo? ** Also affects: flash-kernel (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-raspi (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/1918110 Title: overlay_map.dtb is in wrong location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1918110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918112] Re: Deal with rred shortcomings around empty patch files
We're actually not backporting this to stable releases just future stable one :) ** Changed in: apt (Ubuntu Groovy) Status: New => Won't Fix ** Changed in: apt (Ubuntu Focal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918112 Title: Deal with rred shortcomings around empty patch files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918109] Re: lttng-modules-dkms: build errors with linux >= 5.11
Attached debdiff seems to fix all the build errors with kernel 5.11 (all upstream changes). ** Patch added: "lttng-modules-dkms-linux-5.11.debdiff" https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1918109/+attachment/5474424/+files/lttng-modules-dkms-linux-5.11.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918109 Title: lttng-modules-dkms: build errors with linux >= 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1918109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918112] [NEW] Deal with rred shortcomings around empty patch files
Public bug reported: [Impact] Merge request https://salsa.debian.org/apt-team/apt/-/merge_requests/159 has a bunch of fixes for empty pdiff files, cleaning up pdiff files, as well as correcting some bugs with index files in the mirror method. While we don't use pdiffs ourselves, third party repositories might, and people might want to use rred on Ubuntu to create merged pdiff files, and hence benefit from those patches, so we want to backport it to 2.0, such that it is not more buggy than Debian's 1.8 and forces you to run Debian if you want to do those things. [Test plan] Each commit comes with a change to the test suite that tests it, and the test suite is fairly exhaustive too. [Where problems could occur] Changes are limited to adding headers to Index file downloads (so that mirror works correctly), and pdiff-specific code, so problems could occur with mirror method or pdiff. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: apt (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: apt (Ubuntu Groovy) Importance: Undecided Status: Won't Fix ** Affects: apt (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Groovy) 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/1918112 Title: Deal with rred shortcomings around empty patch files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918110] [NEW] overlay_map.dtb is in wrong location
Public bug reported: overlay_map.dtb is supposed to be located in /boot/firmware/overlays and *not* in /boot/firmware. ** Affects: linux-raspi (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/1918110 Title: overlay_map.dtb is in wrong location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1918110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918109] [NEW] lttng-modules-dkms: build errors with linux >= 5.11
Public bug reported: [Impact] I'm getting the following build errors when I try to install lttng- modules-dkms on the latest hirsute 5.11 kernel: In file included from /var/lib/dkms/lttng-modules/2.12.2/build/probes/../probes/define_trace.h:87, from /var/lib/dkms/lttng-modules/2.12.2/build/probes/../instrumentation/events/lttng-module/block.h:1122, from /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-block.c:30: /var/lib/dkms/lttng-modules/2.12.2/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_block_rq_requeue’ 131 | void trace_##_name(_proto); | ^~ /var/lib/dkms/lttng-modules/2.12.2/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) | ^~~ /var/lib/dkms/lttng-modules/2.12.2/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name,\ | ^~ /var/lib/dkms/lttng-modules/2.12.2/build/probes/../instrumentation/events/lttng-module/block.h:279:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 279 | LTTNG_TRACEPOINT_EVENT(block_rq_requeue, | ^~ In file included from ./include/trace/events/block.h:11, from /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-block.c:19: ./include/linux/tracepoint.h:238:21: note: previous definition of ‘trace_block_rq_requeue’ was here 238 | static inline void trace_##name(proto)\ | ^~ ./include/linux/tracepoint.h:413:2: note: in expansion of macro ‘__DECLARE_TRACE’ 413 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \ | ^~~ ./include/linux/tracepoint.h:549:2: note: in expansion of macro ‘DECLARE_TRACE’ 549 | DECLARE_TRACE(name, PARAMS(proto), PARAMS(args)) | ^ ./include/trace/events/block.h:73:1: note: in expansion of macro ‘TRACE_EVENT’ 73 | TRACE_EVENT(block_rq_requeue, | ^~~ In file included from /var/lib/dkms/lttng-modules/2.12.2/build/probes/../probes/define_trace.h:87, from /var/lib/dkms/lttng-modules/2.12.2/build/probes/../instrumentation/events/lttng-module/block.h:1122, from /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-block.c:30: /var/lib/dkms/lttng-modules/2.12.2/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_block_rq_insert’. 131 | void trace_##_name(_proto); | ^~ [Test plan] Install lttng-modules-dkms to trigger the build errors. [Fix] Apply lttng upstream patches to properly support linux 5.11. [Regresssion potential] To properly support 5.11 the patches that are required are going to touch the block layer code, uprobes and kprobes in lttng, so potentially we could introduce specific lttng failures at tracing these subsystems in old kernels. However these are all upstream patches, so it is unlikely to trigger such failures. ** Affects: lttng-modules (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/1918109 Title: lttng-modules-dkms: build errors with linux >= 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1918109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915786] Re: [SRU] Ussuri stable releases
Hello Chris, or anyone else affected, Accepted nova into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nova/2:21.1.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nova (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915786 Title: [SRU] Ussuri stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1915786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
Indeed, I'm running the daily build and toggling the percentage setting on and off has the expected result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837037] Re: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp failed with i386
** Summary changed: - memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp failed with D i386 / E-oracle + memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp failed with i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837037 Title: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp failed with i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837037] Re: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp failed with D i386 / E-oracle
On B-i386 node pepe 4.15.0-137.141, it's failing with: memcg_move_charge_at_immigrate_test 2 TFAIL: cache is 135168, 270336 expected ** Tags added: sru-20210222 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837037 Title: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp failed with i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918033] Re: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor))
To be sure, please reboot and then run: gsettings get org.gnome.shell enabled-extensions because it sounds like some extensions are still enabled. At least when the apport-collect command was last run. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918033 Title: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter- stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918055] Re: blurry resolution after resume on second screen
Thanks but that did not do what I had hoped. Instead please run: lspci -kv > lspci.txt and run this before suspending: journalctl -b0 > journalbefore.txt xrandr --verbose > xrandrbefore.txt and run this after resuming from suspend: journalctl -b0 > journalafter.txt xrandr --verbose > xrandrafter.txt and attach all five text files here. ** 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/1918055 Title: blurry resolution after resume on second screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878969] Re: time-epoch never changes in SRUs
Hello Dimitri, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878969 Title: time-epoch never changes in SRUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
Hello MarcH, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902553] Re: TEST-03 sometimes fails during autopkgtests
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902553 Title: TEST-03 sometimes fails during autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers
Hello Steve, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883447 Title: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1883447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911187] Re: scheduled reboot reboots immediately if dbus or logind is not available
Hello Ioanna, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911187 Title: scheduled reboot reboots immediately if dbus or logind is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890448] Re: hwdb: Add EliteBook to use micmute hotkey
Hello Kai-Heng, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890448 Title: hwdb: Add EliteBook to use micmute hotkey To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1890448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
Hello Etienne, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: 'systemd --user' unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913189] Re: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1
Hello Kleber, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913189 Title: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1913189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913423] Re: getgrouplist is not thread safe with libnss_systemd
Hello Daniel, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913423 Title: getgrouplist is not thread safe with libnss_systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913763] Re: hyperv: unable to distinguish PTP devices
Hello Gauthier, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913763 Title: hyperv: unable to distinguish PTP devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916229] Re: udev reports error due to NIS usage
@ddstreet Well, after thinking about it, I'm actually not sure if this is an issue after all. Or if this should/must be handled by the system administrator itself, when using NIS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916229 Title: udev reports error due to NIS usage To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1916229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918107] [NEW] renderPM can't set font
Public bug reported:
Since the `gsfonts` dependency was removed in bug #1862641, some reportlab
functionalities are failing.
It can be reproduced with a simple example. First, ensure that `gsfonts`
package is not installed.
In python3:
```
from reportlab.graphics.barcode import createBarcodeDrawing
barcode = createBarcodeDrawing('EAN13', value='1234')
barcode.asString('png')
```
This leads to the following traceback:
```
Warn: Can't find .pfb for face 'Times-Roman'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line
242, in _setFont
gs.setFont(fontName,fontSize)
ValueError: _renderPM.gstate_setFont: Can't find font!
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line
248, in _setFont
_renderPM.makeT1Font(fontName,f.face.findT1File(),f.encoding.vector,open_and_read)
TypeError: makeT1Font() argument 2 must be str, not None
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/reportlab/graphics/shapes.py", line 854,
in asString
return renderPM.drawToString(self,
fmt=format,showBoundary=getattr(self,'showBorder',
File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line
685, in drawToString
drawToFile(d,s,fmt=fmt, dpi=dpi, bg=bg, configPIL=configPIL)
File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line
680, in drawToFile
c = drawToPMCanvas(d, dpi=dpi, bg=bg, configPIL=configPIL,
showBoundary=showBoundary)
File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line
666, in drawToPMCanvas
draw(d, c, 0, 0, showBoundary=showBoundary)
File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line
51, in draw
R.draw(renderScaledDrawing(drawing), canvas, x, y,
showBoundary=showBoundary)
File "/usr/lib/python3/dist-packages/reportlab/graphics/renderbase.py", line
204, in draw
self.initState(x,y) #this is the push()
File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line
98, in initState
self.applyState()
File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line
92, in applyState
self._canvas.setFont(s['fontName'], s['fontSize'])
File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line
399, in setFont
_setFont(self._gs,fontName,fontSize)
File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line
251, in _setFont
raise RenderPMError("Can't setFont(%s) missing the T1 files?\nOriginally
%s: %s" % (fontName,s1,s2))
reportlab.graphics.renderPM.RenderPMError: Can't setFont(Times-Roman) missing
the T1 files?
Originally : makeT1Font() argument 2 must be str, not None
```
After installing the `gsfonts` package, the traceback does not occurs
and the code works as expected.
lsb release: Ubuntu 20.04.1 LTS
python3-renderpm:amd64 3.5.34-1ubuntu1
** Affects: python-reportlab (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/1918107
Title:
renderPM can't set font
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-reportlab/+bug/1918107/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878969] Re: time-epoch never changes in SRUs
Hello Dimitri, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878969 Title: time-epoch never changes in SRUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
Hello MarcH, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902236] Re: Duplicated root and nobody returned by getent on Focal
Hello Simon, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902236 Title: Duplicated root and nobody returned by getent on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1902236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911187] Re: scheduled reboot reboots immediately if dbus or logind is not available
Hello Ioanna, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911187 Title: scheduled reboot reboots immediately if dbus or logind is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913189] Re: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1
Hello Kleber, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913189 Title: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1913189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913423] Re: getgrouplist is not thread safe with libnss_systemd
Hello Daniel, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913423 Title: getgrouplist is not thread safe with libnss_systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913763] Re: hyperv: unable to distinguish PTP devices
Hello Gauthier, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913763 Title: hyperv: unable to distinguish PTP devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915959] Re: Crashes with SIGSEGV due to undefined behaviour when calling perl_parse
** Description changed: While setting up a perl web application with mod_perl & apache, apache kept segfaulting. Broke out gdb, and found that it was segfaulting within perl itself Program received signal SIGSEGV, Segmentation fault. - 0x77358ff5 in perl_parse () from /lib/x86_64-linux- - gnu/libperl.so.5.30 + 0x77358ff5 in perl_parse () from /lib/x86_64-linux-gnu/libperl.so.5.30 (gdb) bt - #0 0x77358ff5 in perl_parse () from /lib/x86_64-linux- - gnu/libperl.so.5.30 - #1 0x7764cd0c in modperl_startup () from - /usr/lib/apache2/modules/mod_perl.so - #2 0x7764cc97 in modperl_startup () from - /usr/lib/apache2/modules/mod_perl.so - #3 0x7764d0fa in modperl_init () from - /usr/lib/apache2/modules/mod_perl.so - #4 0x7764d27b in modperl_hook_init () from - /usr/lib/apache2/modules/mod_perl.so + #0 0x77358ff5 in perl_parse () from /lib/x86_64-linux-gnu/libperl.so.5.30 + #1 0x7764cd0c in modperl_startup () from /usr/lib/apache2/modules/mod_perl.so + #2 0x7764cc97 in modperl_startup () from /usr/lib/apache2/modules/mod_perl.so + #3 0x7764d0fa in modperl_init () from /usr/lib/apache2/modules/mod_perl.so + #4 0x7764d27b in modperl_hook_init () from /usr/lib/apache2/modules/mod_perl.so #5 0x555b23d4 in ap_run_open_logs () #6 0x5558c440 in main () - # valgrind apache2 -k start -X + # valgrind apache2 -k start -X ==22529== Memcheck, a memory error detector - ==22529== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et - al. - ==22529== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright - info + ==22529== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. + ==22529== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==22529== Command: apache2 -k start -X ==22529== ==22529== Invalid read of size 8 - ==22529==at 0x564AFF5: perl_parse (in /usr/lib/x86_64-linux- - gnu/libperl.so.5.30.0) - ==22529==by 0x55A8D0B: modperl_startup (in - /usr/lib/apache2/modules/mod_perl.so) - ==22529==by 0x55A8C96: modperl_startup (in - /usr/lib/apache2/modules/mod_perl.so) - ==22529==by 0x55A90F9: modperl_init (in - /usr/lib/apache2/modules/mod_perl.so) - ==22529==by 0x55A927A: modperl_hook_init (in - /usr/lib/apache2/modules/mod_perl.so) + ==22529==at 0x564AFF5: perl_parse (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0) + ==22529==by 0x55A8D0B: modperl_startup (in /usr/lib/apache2/modules/mod_perl.so) + ==22529==by 0x55A8C96: modperl_startup (in /usr/lib/apache2/modules/mod_perl.so) + ==22529==by 0x55A90F9: modperl_init (in /usr/lib/apache2/modules/mod_perl.so) + ==22529==by 0x55A927A: modperl_hook_init (in /usr/lib/apache2/modules/mod_perl.so) ==22529==by 0x1663D3: ap_run_open_logs (in /usr/sbin/apache2) ==22529==by 0x14043F: main (in /usr/sbin/apache2) - ==22529== Address 0x5a44000 is not stack'd, malloc'd or (recently) - free'd + ==22529== Address 0x5a44000 is not stack'd, malloc'd or (recently) free'd ==22529== ==22529== ==22529== Process terminating with default action of signal 11 (SIGSEGV) ==22529== Access not within mapped region at address 0x5A44000 - ==22529==at 0x564AFF5: perl_parse (in /usr/lib/x86_64-linux- - gnu/libperl.so.5.30.0) - ==22529==by 0x55A8D0B: modperl_startup (in - /usr/lib/apache2/modules/mod_perl.so) - ==22529==by 0x55A8C96: modperl_startup (in - /usr/lib/apache2/modules/mod_perl.so) - ==22529==by 0x55A90F9: modperl_init (in - /usr/lib/apache2/modules/mod_perl.so) - ==22529==by 0x55A927A: modperl_hook_init (in - /usr/lib/apache2/modules/mod_perl.so) + ==22529==at 0x564AFF5: perl_parse (in /usr/lib/x86_64-linux-gnu/libperl.so.5.30.0) + ==22529==by 0x55A8D0B: modperl_startup (in /usr/lib/apache2/modules/mod_perl.so) + ==22529==by 0x55A8C96: modperl_startup (in /usr/lib/apache2/modules/mod_perl.so) + ==22529==by 0x55A90F9: modperl_init (in /usr/lib/apache2/modules/mod_perl.so) + ==22529==by 0x55A927A: modperl_hook_init (in /usr/lib/apache2/modules/mod_perl.so) ==22529==by 0x1663D3: ap_run_open_logs (in /usr/sbin/apache2) ==22529==by 0x14043F: main (in /usr/sbin/apache2) gdb indicated that it was erroring in very early in perl's runtime, before it had got to any perl code. When using debug symbols, the exact line it was failing on was `scriptname = argv[0];` (perl.c:2365) It wasn't possible to reason beyond that as stepping through optimised code even with debug symbols is next to impossible to make any sense of. I did find that building an unoptimised perl made the error go away. I found the following closed issue: https://github.com/Perl/perl5/issues/15806 which describes the same issue I was having. Looking at the source for mod_perl, I found that the argv array passed to perl_parse() is not NULL terminated as is required by perl - ( documentation:
[Bug 1917098] Re: Doesn't work with 3.38.3
Tracking in https://github.com/gicmo/gamemode-extension/issues/31 ** Bug watch added: github.com/gicmo/gamemode-extension/issues #31 https://github.com/gicmo/gamemode-extension/issues/31 ** Tags added: groovy hirsute ** Changed in: gnome-shell-extension-gamemode (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-gamemode (Ubuntu) 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/1917098 Title: Doesn't work with 3.38.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-gamemode/+bug/1917098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
