[Bug 1914411] Re: Fix broken efifb on graphics device without driver
Hello, With this patch linux-image-5.11.0-13-generic is not booting anymore a raspberry pi 4 with UEFI firmware (https://github.com/pftf/RPi4) (on hirsute) I compiled from https://kernel.ubuntu.com/git/ubuntu/ubuntu-hirsute.git , without this patch, and the raspberry is booting Ok. Cheers, Olivier ** Attachment added: "kernel panic with linux-image-5.11.0-13-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914411/+attachment/5483313/+files/IMG_1707.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914411 Title: Fix broken efifb on graphics device without driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
This is to confirm that kubuntu-21.04-beta-desktop-amd64.iso fails as an installation media on my PC. I have nvidia graphics, amd m/board and am using 'safe graphics' when attempting to boot up the installation media from a thumb drive. The usual "Installation failed" message is displayed. If more info would help please give me any further instructions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922315] Re: Ubuntu 21.04 Beta Installer - Error Installing grub-efi-amd64-signed
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1922315/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922315 Title: Ubuntu 21.04 Beta Installer - Error Installing grub-efi-amd64-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1922315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 357243] Re: hydrogen 100% network usage
[Expired for hydrogen (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hydrogen (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/357243 Title: hydrogen 100% network usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hydrogen/+bug/357243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559586] Re: post-fader setting of Hydrogen doesn't work
[Expired for hydrogen (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hydrogen (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/559586 Title: post-fader setting of Hydrogen doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hydrogen/+bug/559586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 428360] Re: Hydrogen's OSS driver doesn't work
[Expired for hydrogen (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hydrogen (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/428360 Title: Hydrogen's OSS driver doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hydrogen/+bug/428360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 718387] Re: std:bad_alloc while adding new instrument
[Expired for hydrogen (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hydrogen (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/718387 Title: std:bad_alloc while adding new instrument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hydrogen/+bug/718387/+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
Minor correction to the patch: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=30bf11d2759499ec94d3b82eaf22f55583f4758b Uploaded as the next xenial version to the upload queue -- 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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
The original driver must carry out this behavior: When the touchpad is tapped, Check if the Touchpad Numlock is engaged. If engaged, use tap position to decide on psuedo-number pad input. If not engaged, click mouse. NumLk on/off: yes; a program with an appropriate hotkey csn send the i2c commands. Touchpad position to numpad function: we have this in Python, and could be refactored "On touchpad tap, check if Touchpad Numlock is engaged, and do stuff." -Not yet We have all these things, except for the ugly work of "run program whenever touchpad is tapped." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922315] Re: Ubuntu 21.04 Beta Installer - Error Installing grub-efi-amd64-signed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: 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/1922315 Title: Ubuntu 21.04 Beta Installer - Error Installing grub-efi-amd64-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1922315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922315] Re: Ubuntu 21.04 Beta Installer - Error Installing grub-efi-amd64-signed
I faced this issue while ago. It seems like grub-installer is not able to fetch efi variables while installing. In live boot I ran "modprobe efivars" as root and did installation. Everything worked just fine. I am assuming you are installing in efi mode.Let me know if it works -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922315 Title: Ubuntu 21.04 Beta Installer - Error Installing grub-efi-amd64-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1922315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922318] [NEW] gnome-shell-extension-multi-monitors out of date
Public bug reported: gnome-shell-extension-multi-monitors crashes on LTS 20.04 gnome-shell-extension-multi-monitors crashes because it's out of date and the new version on github isn't in the package manager The code crashing it has been removed in this commit https://github.com/spin83/multi-monitors-add- on/commit/15a0d3ceea6a601d4c4b709a0fd655ff7d6d27ea#diff- a90eb6aeed84b64a03b86f59cbf3d134dd1037ed6f29bdb6eb389530f32dd435 but the version from the package manager is stale and doesn't work anymore on LTS20.04 https://pastebin.com/yv4FVbqj related https://askubuntu.com/questions/1325486/ubuntu-20-04-show-date-time-volume-on-every-screen/1327910?noredirect=1#comment2264469_1327910 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-multi-monitors (not installed) ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 22:30:53 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-25 (2077 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-multi-monitors UpgradeStatus: Upgraded to focal on 2021-03-19 (14 days ago) ** Affects: gnome-shell-extension-multi-monitors (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922318 Title: gnome-shell-extension-multi-monitors out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-multi-monitors/+bug/1922318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922317] Re: package bluez 5.53-0ubuntu3 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922317 Title: package bluez 5.53-0ubuntu3 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922317] [NEW] package bluez 5.53-0ubuntu3 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
Public bug reported: I cannot seem to get my bluetooth to work. When I go to bluetooth settings the "switch" is grayed out and I cannot turn it off or on. I'm trying to install bluez and I am getting an error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 1 20:17:40 2021 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-01-15 (443 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bnep bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b509 Chicony Electronics Co., Ltd HP Truevision HD Bus 001 Device 009: ID :3100 MacAlly Macally ECOMouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 3: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 5: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=93ef3a52-1422-4313-abac-a02f96bcecc3 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: bluez Title: package bluez 5.53-0ubuntu3 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-04-02 (0 days ago) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.vendor: HP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd03/06/2018:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn:rvr:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N5Z06UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922317 Title: package bluez 5.53-0ubuntu3 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922315] [NEW] Ubuntu 21.04 Beta Installer - Error Installing grub-efi-amd64-signed
Public bug reported: Release: Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Installing Ubuntu 21.04 Beta and installation process executes as expected. At the end of the installation receive a pop up as below: Title: Error installing grub-efi-amd64-signed Body: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit1. After clicking OK, get another pop up as below: Title: An error occurred while installing packages: E:Sub-process /usr/bin/dpkg returned error code (1) The body of the second pop up is to much to type, but says "More details may be found in /var/log/syslog". I found the entries below in /var/log/installer/syslog and believe them to be from the error: Apr 2 02:31:38 ubuntu ubiquity: Trying to migrate /boot/efi into esp config#015 Apr 2 02:31:38 ubuntu ubiquity: Installing grub to /boot/efi.#015 Apr 2 02:31:38 ubuntu ubiquity: Installing for x86_64-efi platform.#015 Apr 2 02:31:39 ubuntu ubiquity: grub-install: warning: Cannot read EFI Boot* variables.#015 Apr 2 02:31:39 ubuntu ubiquity: grub-install: warning: read_file: could not read from file: Input/output error.#015 Apr 2 02:31:39 ubuntu ubiquity: grub-install: warning: vars_get_variable: read_file(/sys/firmware/efi/vars/Boot0009-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var) failed: Input/output error.#015 Apr 2 02:31:39 ubuntu ubiquity: grub-install: warning: efi_get_variable: ops->get_variable failed: Input/output error.#015 Apr 2 02:31:39 ubuntu ubiquity: grub-install: error: failed to register the EFI boot entry: Input/output error.#015 Apr 2 02:31:40 ubuntu ubiquity: dpkg: error processing package grub-efi-amd64-signed (--configure):#015 Apr 2 02:31:40 ubuntu ubiquity: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1#015 I have pictures of the two popup windows if needed. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "Popup windows" https://bugs.launchpad.net/bugs/1922315/+attachment/5483293/+files/bug.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922315 Title: Ubuntu 21.04 Beta Installer - Error Installing grub-efi-amd64-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1922315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922310] [NEW] GIMP crashed 2.10.24
Public bug reported: Following what the crash window told me to do, so I copy/pasted here GIMP crashed with a fatal error: fatal error: Segmentation fault ``` GNU Image Manipulation Program version 2.10.24 git-describe: GIMP_2_10_24 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.3.0-17ubuntu1~20.04' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-9-HskZEa/gcc-9-9.3.0/debian/tmp-nvptx/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) # Libraries # using babl version 0.1.86 (compiled against version 0.1.86) using GEGL version 0.4.30 (compiled against version 0.4.30) using GLib version 2.64.6 (compiled against version 2.64.6) using GdkPixbuf version 2.40.0 (compiled against version 2.40.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.44.7 (compiled against version 1.44.7) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Segmentation fault Stack trace: ``` # Stack traces obtained from PID 15365 - Thread 15365 # [New LWP 15367] [New LWP 15368] [New LWP 15369] [New LWP 15370] [New LWP 15371] [New LWP 15372] [New LWP 15374] [New LWP 15397] [New LWP 15458] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fa472a5e36c in read () from /lib/x86_64-linux-gnu/libpthread.so.0 Id Target IdFrame * 1Thread 0x7fa471b34340 (LWP 15365) "gimp-2.10"0x7fa472a5e36c in read () from /lib/x86_64-linux-gnu/libpthread.so.0 2Thread 0x7fa4713e5700 (LWP 15367) "worker" 0x7fa47297389d in syscall () from /lib/x86_64-linux-gnu/libc.so.6 3Thread 0x7fa470be4700 (LWP 15368) "worker" 0x7fa47297389d in syscall () from /lib/x86_64-linux-gnu/libc.so.6 4Thread 0x7fa4703e3700 (LWP 15369) "worker" 0x7fa47297389d in syscall () from /lib/x86_64-linux-gnu/libc.so.6 5Thread 0x7fa46e5fe700 (LWP 15370) "gmain"0x7fa47296daff in poll () from /lib/x86_64-linux-gnu/libc.so.6 6Thread 0x7fa46ddfd700 (LWP 15371) "dconf worker" 0x7fa47296daff in poll () from /lib/x86_64-linux-gnu/libc.so.6 7Thread 0x7fa46d5fc700 (LWP 15372) "gdbus"0x7fa47296daff in poll () from /lib/x86_64-linux-gnu/libc.so.6 8Thread 0x7fa44697d700 (LWP 15374) "async"0x7fa47297389d in syscall () from /lib/x86_64-linux-gnu/libc.so.6 9Thread 0x7fa44594b700 (LWP 15397) "threaded-ml" 0x7fa47296daff in poll () from /lib/x86_64-linux-gnu/libc.so.6 10 Thread 0x7fa42bfff700 (LWP 15458) "swap writer" 0x7fa47297389d in syscall () from /lib/x86_64-linux-gnu/libc.so.6 Thread 10 (Thread 0x7fa42bfff700 (LWP 15458)): #0 0x7fa47297389d in syscall () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fa472c63623 in g_cond_wait () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4731683ad in () at /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0 #3 0x7fa472c3fad1 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa472a53609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7fa47297a293 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 9 (Thread 0x7fa44594b700 (LWP 15397)): #0 0x7fa47296daff in poll () at /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fa46ecee1d6 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fa46ecdf841 in pa_mainloop_poll () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fa46ecdfec3 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fa46ecdff70 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fa46ecee11d in () at
[Bug 1922308] Re: Please add Pennsylvania German locale file
Thanks for your suggested locale. Ubuntu uses the locales provided by glibc, though, so the right place to request a new locale is here: https://sourceware.org/bugzilla/enter_bug.cgi?product=glibc;component=localedata If you submit a request to upstream glibc, please post the URL to it here for tracking purposes. On 2021-04-02 03:13, Cole Huther wrote: > I have completed a degree of translations Have you? I can't see that the language exists in Launchpad, for instance. Some hints before you proceed: You should keep in mind that translating Ubuntu is not only about Ubuntu. It's about translating free software for Linux, i.e. a huge undertaking. Would there be enough translators to translate tens of thousands of strings (at least) into Pennsylvania German and then maintain those translations when software is upgraded or replaced? And how many users would find it useful to have menus and windows displayed in Pennsylvania German? ** Package changed: langpack-locales (Ubuntu) => glibc (Ubuntu) ** Changed in: glibc (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922308 Title: Please add Pennsylvania German locale file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1922308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922306] Re: Unable to boot into previous installation after installing Kylin.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1922306 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922306 Title: Unable to boot into previous installation after installing Kylin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1922306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)
** Changed in: hplip (Debian) Status: Unknown => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714659 Title: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1714659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915923] Re: [SRU] update-pciids in pciutils fails to create hard link
I've sponsored this for Focal. ** Changed in: pciutils (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/1915923 Title: [SRU] update-pciids in pciutils fails to create hard link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pciutils/+bug/1915923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
** Changed in: qemu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922279] Re: package libpam-systemd:amd64 245.4-4ubuntu3.5 failed to install/upgrade: пакунок знаходиться у поганому стані; потрібно перевстановити його до початку налаштування
*** This bug is a duplicate of bug 1699360 *** https://bugs.launchpad.net/bugs/1699360 This seems to be the same as explained here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1921574/comments/2 so marking this as dup of bug 1699360 for your specific system, you probably can fix your local problem by running: $ sudo apt install --fix-broken and then try apt upgrade again. ** This bug has been marked a duplicate of bug 1699360 package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922279 Title: package libpam-systemd:amd64 245.4-4ubuntu3.5 failed to install/upgrade: пакунок знаходиться у поганому стані; потрібно перевстановити його до початку налаштування To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1922279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775131] Re: Ubuntu 18.04 networking issue (connection drops after approx. 15 minutes)
Not sure if this will overlap with anyone else, but my experience was a combination of 2 things: 1. Reboots were happening, caused by unattended-upgrade 2. The device causing trouble was a renamed device. Turns out it was trying to get renamed twice: Once very early in boot from eth1 to eno2, then again based on my neplan from eno2 to the name I wanted. This was failing, and leaving the device down. See my comment #117 on this issue for more details: https://bugs.launchpad.net/netplan/+bug/1770082 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775131 Title: Ubuntu 18.04 networking issue (connection drops after approx. 15 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
Clarifying what worked for me across all the servers where I need this config: cat
[Bug 1922308] [NEW] Please add Pennsylvania German locale file
Public bug reported: Please add the PA German locale file I made. I have completed a degree of translations ** Affects: langpack-locales (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Pennsylvania German locale file" https://bugs.launchpad.net/bugs/1922308/+attachment/5483290/+files/pdc_US -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922308 Title: Please add Pennsylvania German locale file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1922308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913284] Re: [plugin] [bcache] add a new bcache plugin
SRU verification for Bionic passed. Attached a text file w/ steps and relevant info. ** Attachment added: "bcache-bionic-verification.txt" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1913284/+attachment/5483289/+files/bcache-bionic-verification.txt ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913284 Title: [plugin] [bcache] add a new bcache plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1913284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922307] [NEW] package libaacs0 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libaacs0/changelog.Debian.gz« zu überschreiben, welches verschieden von and
Public bug reported: How to reproduce? First, we install libaacs0 for amd64. sudo apt install libaacs0:amd64 Now we realize that we need libaacs0 for wine, so we install libaacs0 for i386 which should remove the first package. sudo apt install libaacs0:i386 The installation fails as /usr/share/doc/libaacs0/changelog.Debian.gz from libaacs0:amd64 has not yet been deleted when libaacs0:i386 tries to write this file. Manually removing libaacs0:amd64 before installing libaacs0:i386 works as expected. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libaacs0 (not installed) ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 2 02:36:23 2021 ErrorMessage: Versuch, gemeinsam benutztes »/usr/share/doc/libaacs0/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libaacs0:i386 ist InstallationDate: Installed on 2018-12-11 (843 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: libaacs Title: package libaacs0 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libaacs0/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libaacs0:i386 ist UpgradeStatus: Upgraded to focal on 2020-10-26 (157 days ago) ** Affects: libaacs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922307 Title: package libaacs0 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libaacs0/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libaacs0:i386 ist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libaacs/+bug/1922307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
removing block-proposed tags as the fix has been released in hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1887744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
fixed in hirsute in version: https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu2 ** Tags removed: block-proposed-focal block-proposed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1887744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922306] [NEW] Unable to boot into previous installation after installing Kylin.
Public bug reported: when performing the daily build testcase for an installation with auto- resizing, the install completed successfully, but I am unable to boot into any of the Grub menu entries for my previous Linux installation. The previous installation was a Arch install making use of Grub. $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.04-1ubuntu44 Version table: 2.04-1ubuntu44 500 500 http://za.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu Kylin 21.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 2 02:37:55 2021 InstallationDate: Installed on 2021-04-02 (0 days ago) InstallationMedia: Ubuntu-Kylin 21.04 "Hirsute Hippo" - Beta amd64 (20210401) ProcEnviron: LANGUAGE=en_ZA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922306 Title: Unable to boot into previous installation after installing Kylin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1922306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
Is it possible this regressed sometime between Bionic and Focal? I am
observing this in 20.04. Early in dmesg I see my interface renamed from
eth1 to eno2, then my netplan attempts to rename with a match (on
name=eno2) to my desired name ("ceph" in this case). I see syslog
message:
systemd-udevd[844]: eno2: Config file /run/systemd/network/10-netplan-
eno2.link matches device based on renamed interface name, ignoring
but after boot and login, netplan apply is succsesful.
Steps in #11 do not work, even though I verify the link file is in the
new initrd.img at usr/lib/systemd/network/10-netplan-eno2.link
What _did_ work for me, is editing this file first to refer to the eth1
name instead of eno2 (the file was written, I believe, by netplan).
After this I can change my netplan to refer to the desired name with no
set-name rule. Obvs. I can cut out some steps as I replicate this
solution to the other servers.
To summarize: write out /etc/systemd/network/10-netplan-eno2.link in a
way that refers to eth1 (instead of eno2) and sets ultimately desired
name. update-initramfs. netplan uses desired name without rename rules.
I suppose I can/should rename that file to 10-netplan-ceph.link :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Title:
systemd-networkd not renaming devices on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922260] Re: `make olddefconfig` results in a kernel missing support for touchpad and wifi
** 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/1922260 Title: `make olddefconfig` results in a kernel missing support for touchpad and wifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed f
I'm running Ubuntu 20.10. But I think I can answer my own question. It just happened again, and this time all I needed to run was run `apt update`. I didn't even install anything! A quick google search found this page: https://www.linuxuprising.com/2020/07/how-to-restart-gnome-shell-from- command.html. I pressed Alt-F2 and then r, and that stopped the logging without a reboot! I'd still like to know why this suddenly keeps happening. 21.04 is due out in a few weeks and I'm hoping that will fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905519 Title: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913284] Re: [plugin] [bcache] add a new bcache plugin
SRU verification for Groovy passed. Attached a text file w/ steps and relevant info. ** Attachment added: "bcache-groovy-verification.txt" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1913284/+attachment/5483278/+files/bcache-groovy-verification.txt ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913284 Title: [plugin] [bcache] add a new bcache plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1913284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output
** Changed in: mate-desktop Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922276 Title: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1922276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922293] Re: Snaps appear broken on 21.04 Beta
Just an update. A classic'ly confined snap (like slack) does appear to keep working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922293 Title: Snaps appear broken on 21.04 Beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915923] Re: [SRU] update-pciids in pciutils fails to create hard link
Debdiff attached. ** Patch added: "pciutils.debdiff" https://bugs.launchpad.net/ubuntu/+source/pciutils/+bug/1915923/+attachment/5483276/+files/pciutils.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915923 Title: [SRU] update-pciids in pciutils fails to create hard link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pciutils/+bug/1915923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
This bug was fixed in the package systemd - 247.3-3ubuntu2 --- systemd (247.3-3ubuntu2) hirsute; urgency=medium [ Dan Streetman ] * d/p/lp1887744-basic-unit-file-when-loading-linked-unit-files-use-l.patch: Use src name, not dst name, of symlinked unit files (LP: #1887744) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=667a881ab3bace6c4a7550067d4ecf2e4b9ece82 -- Balint Reczey Mon, 29 Mar 2021 12:22:06 +0200 ** Changed in: systemd (Ubuntu Hirsute) Status: In Progress => 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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1887744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911830] Re: alsa/sdw: support soundwire audio for TGL-H machines
This bug was fixed in the package linux-firmware - 1.196 --- linux-firmware (1.196) hirsute; urgency=medium * Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git 3f026a2f13a8f130cde849168a111ec80f12e27b - silabs: add new firmware for WF200 - brcm: Fix Raspberry Pi 4B NVRAM file - Add symlink for BananaPi M2 to brcmfmac43430-sdio config - WHENCE: add missing symlink for BananaPi M3 - rtw89: 8852a: add firmware v0.9.12.2 - linux-firmware: add frimware for mediatek bluetooth chip (MT7921) - Mellanox: Add new mlxsw_spectrum firmware xx.2008.2406 - iwlwifi: update 7265D firmware - iwlwifi: update 9000-family firmwares - iwlwifi: add new FWs from core59-66 release - rtw88: 8822c: Update normal firmware to v9.9.6 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - amdgpu: add initial support for navy flounder - amdgpu: update raven firmware for 20.50 - amdgpu: update raven2 firmware for 20.50 - amdgpu: update navi10 firmware for 20.50 - amdgpu: update renoir firmware for 20.50 - amdgpu: update vega10 firmware for 20.50 - amdgpu: update navi12 firmware for 20.50 - amdgpu: update vega12 firmware for 20.50 - amdgpu: update navi14 firmware for 20.50 - amdgpu: update picasso firmware for 20.50 - amdgpu: update vega20 firmware for 20.50 - amdgpu: update sienna cichlid firmware for 20.50 - rtl_bt: Update RTL8822C BT(UART I/F) FW to 0x59A_76A3 * alsa/sdw: support soundwire audio for TGL-H machines (LP: #1911830) - SAUCE: sof-firmware: add TGL-H firmware from sof-bin v1.6.1 -- Seth Forshee Wed, 31 Mar 2021 13:49:18 -0500 ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Fix Committed => 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/1911830 Title: alsa/sdw: support soundwire audio for TGL-H machines To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1911830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915905] Re: Application menu logo is trimmed (not correct size) for default panel size (of 28)
This bug was fixed in the package ubuntu-mate-artwork - 21.04.6 --- ubuntu-mate-artwork (21.04.6) hirsute; urgency=medium * Fix trimmed Application menu logo (LP: #1915905) * Sync Yaru MATE with upstream Yaru -- Martin Wimpress Thu, 01 Apr 2021 10:22:59 +0100 ** Changed in: ubuntu-mate-artwork (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-mate-settings (Ubuntu) Status: Fix Committed => 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/1915905 Title: Application menu logo is trimmed (not correct size) for default panel size (of 28) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1915905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918076] Re: MATE Panel shows two keyboard layout indicators - one from MATE Control Center, one from Ayatana
This bug was fixed in the package ubuntu-mate-settings - 21.04.5 --- ubuntu-mate-settings (21.04.5) hirsute; urgency=medium * Only show one keyboard indicator (LP: #1918076) -- Martin Wimpress Thu, 01 Apr 2021 12:09:46 +0100 ** Changed in: ubuntu-mate-settings (Ubuntu) Status: Fix Committed => 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/1918076 Title: MATE Panel shows two keyboard layout indicators - one from MATE Control Center, one from Ayatana To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-keyboard/+bug/1918076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915905] Re: Application menu logo is trimmed (not correct size) for default panel size (of 28)
This bug was fixed in the package ubuntu-mate-settings - 21.04.5 --- ubuntu-mate-settings (21.04.5) hirsute; urgency=medium * Only show one keyboard indicator (LP: #1918076) -- Martin Wimpress Thu, 01 Apr 2021 12:09:46 +0100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915905 Title: Application menu logo is trimmed (not correct size) for default panel size (of 28) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1915905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915492] Re: ayatana-indicator-keyboard-service crashed with SIGSEGV in keyboard_GetLayout()
This bug was fixed in the package ubuntu-mate-settings - 21.04.5 --- ubuntu-mate-settings (21.04.5) hirsute; urgency=medium * Only show one keyboard indicator (LP: #1918076) -- Martin Wimpress Thu, 01 Apr 2021 12:09:46 +0100 ** Changed in: ubuntu-mate-settings (Ubuntu) Status: Fix Committed => 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/1915492 Title: ayatana-indicator-keyboard-service crashed with SIGSEGV in keyboard_GetLayout() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-keyboard/+bug/1915492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920825] Re: FTBFS and autopkgtest failure in Hirsute (badly generated symbols files)
This bug was fixed in the package ldb - 2:2.2.0-3ubuntu1 --- ldb (2:2.2.0-3ubuntu1) hirsute; urgency=medium * Fix symbols generation (LP: #1920825). On hirsute, dh-exec is showing different behavior based on the value of DEB_BUILD_PROFILES. This is causing it to sometimes generate a file with the leading whitespace removed, which is resulting in a bad symbols file. Set DEB_BUILD_PROFILES to empty gives a good symbols file. -- Matthias Klose Tue, 30 Mar 2021 16:11:59 +0200 ** Changed in: ldb (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: talloc (Ubuntu Hirsute) Status: Fix Committed => 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/1920825 Title: FTBFS and autopkgtest failure in Hirsute (badly generated symbols files) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-exec/+bug/1920825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920825] Re: FTBFS and autopkgtest failure in Hirsute (badly generated symbols files)
This bug was fixed in the package talloc - 2.3.1-2ubuntu1 --- talloc (2.3.1-2ubuntu1) hirsute; urgency=medium * Fix symbols generation (LP: #1920825). On hirsute, dh-exec is showing different behavior based on the value of DEB_BUILD_PROFILES. This is causing it to sometimes generate a file with the leading whitespace removed, which is resulting in a bad symbols file. Set DEB_BUILD_PROFILES to empty gives a good symbols file, but what does this matter? -- Dan Bungert Mon, 29 Mar 2021 17:23:59 -0600 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920825 Title: FTBFS and autopkgtest failure in Hirsute (badly generated symbols files) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-exec/+bug/1920825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
This bug was fixed in the package alsa-lib - 1.2.4-1.1ubuntu2 --- alsa-lib (1.2.4-1.1ubuntu2) hirsute; urgency=medium * d/p/0001-conf-USB-add-Cmedia-Audio-to-USB-Audio.pcm.iec958_de.patch: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device https://github.com/alsa-project/alsa-lib/pull/122 (LP: #1921452) -- Shengyao Xue Fri, 26 Mar 2021 12:03:07 +0800 ** Changed in: alsa-lib (Ubuntu Hirsute) Status: Fix Committed => 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/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921539] Re: Add support for SBAT
This bug was fixed in the package fwupd - 1.5.8-0ubuntu1 --- fwupd (1.5.8-0ubuntu1) hirsute; urgency=medium * New upstream version (1.5.8) * Backport a patch to fix SBAT (LP: #1921539) * Drop all other patches, upstream. -- Mario Limonciello Fri, 26 Mar 2021 14:07:35 -0500 ** Changed in: fwupd (Ubuntu Hirsute) Status: In Progress => 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/1921539 Title: Add support for SBAT To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908771] Re: install crashed
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1908771 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908771 Title: install crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1908771/+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
xenial: $ pull-lp-source systemd 229-4ubuntu21.30 ... $ stat -c '%y' systemd-229/NEWS 2016-02-11 11:28:00.0 -0500 $ lxc launch --vm ubuntu:xenial lp1878969-x $ lxc console lp1878969-x ... ubuntu@lp1878969-x:~$ sudo systemctl disable systemd-timesyncd.service Removed symlink /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service. $ sudo date -s '1990-01-01' Mon Jan 1 00:00:00 UTC 1990 $ lxc start lp1878969-x $ lxc console lp1878969-x ... ubuntu@lp1878969-x:~$ dpkg -l systemd|grep systemd ii systemd229-4ubuntu21.29 amd64system and service manager ubuntu@lp1878969-x:~$ date Thu Feb 11 16:28:17 UTC 2016 >From https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.30 " -- Dan Streetman Wed, 17 Mar 2021 17:41:20 -0400" $ date Mon Jan 1 00:03:49 UTC 1990 $ lxc start lp1878969-x $ lxc console lp1878969-x ... ubuntu@lp1878969-x:~$ dpkg -l systemd|grep systemd ii systemd229-4ubuntu21.30 amd64system and service manager ubuntu@lp1878969-x:~$ date Thu Feb 11 16:28:40 UTC 2016 verification failed, unfortunately; the patch didn't properly set the time epoch. ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- 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 1905370] Re: Qt-based tray icons not displayed on start-up
Yes, the fix is in the focal queue for some days now, once SRU team will approve it will be available in proposed repositories for user verification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905370 Title: Qt-based tray icons not displayed on start-up To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1905370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919380] Re: Bionic update: upstream stable patchset 2021-03-16
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919380 Title: Bionic update: upstream stable patchset 2021-03-16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922298] [NEW] Activities panel on wrong display
Public bug reported: The activities panel is showing up on the wrong display. Selecting the "primary display" as 3 in the display settings puts the top bar on display 3 , but the activities bar on screen 2. Screenshot attached Similarly, selecting primary display = 2 then activities bar ends up on 1 primary display = 1 then activities bar ends up on 3 I'm hoping this is just an off by one error somewhere. I think gnome-shell is the correct package. Feel free to move to the correct package ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 17:16:30 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-12 (293 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2021-04-01 17-05-08.png" https://bugs.launchpad.net/bugs/1922298/+attachment/5483269/+files/Screenshot%20from%202021-04-01%2017-05-08.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922298 Title: Activities panel on wrong display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922124] Re: Bionic update: upstream stable patchset 2021-03-31
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922124 Title: Bionic update: upstream stable patchset 2021-03-31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905370] Re: Qt-based tray icons not displayed on start-up
Any update on its status on Focal? Will it be back ported? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905370 Title: Qt-based tray icons not displayed on start-up To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1905370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922297] [NEW] 20.10 to 21.04: snap does not upgrade channel
Public bug reported: # Overview Per LP: #1827951 and LP: #1748581, it would appear that if a snap is tracking a release channel (e.g. latest/stable/ubuntu-20.10), during a do-release-upgrade the snap channel should update to the new release. Testing of a Google cloud image, from 20.10 to 21.04 the google-cloud- sdk does not get updated. # Expected result After a do-release-upgrade, the snap channel for google-cloud-sdk should be updated from "latest/stable/ubuntu-20.10" to "latest/stable/ubuntu-21.04". # Actual result After install, the snap continues to track "latest/stable/ubuntu-20.10". # Steps to reproduce 1. Boot 20.10 GCE image 2. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.10" 3. do-release-upgrade -d 4. accept defaults and reboot 5. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.10" # Logs main.log https://paste.ubuntu.com/p/kbSvM5JMzP/ screenlog.0 https://paste.ubuntu.com/p/h5kvtcX5Z6/ apt-term.log https://paste.ubuntu.com/p/gNJVzbtT4Z/ ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Description changed: # Overview Per LP: #1827951 and LP: #1748581, it would appear that if a snap is tracking a release channel (e.g. latest/stable/ubuntu-20.10), during a do-release-upgrade the snap channel should update to the new release. Testing of a Google cloud image, from 20.10 to 21.04 the google-cloud- sdk does not get updated. # Expected result After a do-release-upgrade, the snap channel for google-cloud-sdk should be updated from "latest/stable/ubuntu-20.10" to "latest/stable/ubuntu-21.04". # Actual result After install, the snap continues to track "latest/stable/ubuntu-20.10". # Steps to reproduce 1. Boot 20.10 GCE image 2. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.10" 3. do-release-upgrade -d 4. accept defaults and reboot - 5. snap info google-cloud-sdk --> "latest/stable/ubuntu-21.04" + 5. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.10" # Logs main.log https://paste.ubuntu.com/p/kbSvM5JMzP/ screenlog.0 https://paste.ubuntu.com/p/h5kvtcX5Z6/ apt-term.log https://paste.ubuntu.com/p/gNJVzbtT4Z/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922297 Title: 20.10 to 21.04: snap does not upgrade channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921960] Re: Groovy update: upstream stable patchset 2021-03-30
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921960 Title: Groovy update: upstream stable patchset 2021-03-30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922295] Re: lvm.conf activation/auto_activation_volume_list not honored, VG is always activated at startup
** Description changed: On a freshly installed Ubuntu 20.04 LTS (raw minimal installation) with LVM on LUKS using https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019 as a basis /dev/sda2 => luks encrypted with LVM VG named "ubuntu" and LVM tag "ubuntu_vg" LV /boot named boot and LVM tag "ubuntu_vg,boot" LV /root named root with LVM tag "ubuntu_vg,root" LV /home named home with LVM tag "ubuntu_vg,home" LV /swap named swap with LVM tag "ubuntu_vg,swap" /dev/sda3 => LVM VG named "tools" VG and two LVs The tools VG and related LVs are always activated at startup despite the settings in /etc/lvm/lvm.conf. According to lvm2-activation-generator The lvm2-activation-generator is called by systemd(1) on boot to generate systemd units at runtime to activate LVM Logical Volumes (LVs) when global/event_activation=0 is set in lvm.conf(5). These units use vgchange -aay to activate LVs. (vgchange -aay that honours the activation/auto_activation_volume_list setting) With the following settings in lvm.conf: /etc/lvm/lvm.conf: global/event_activation event_activation = 0 activation/auto_activation_volume_list auto_activation_volume_list = [ "ubuntu", "@ubuntu_vg" ] activation/volume_list volume_list = [ "ubuntu", "@ubuntu_vg" ] >> tools VG/LV is activated at startup => KO even with journalctl log line: lvm[PID]: pvscan[PID] VG tools skip autoactivation lvm.conf settings are working because - Can be deactivated with vgchange -an tools - Can't be reactivated with vgchange -ay tools due to tools VG/Tags not listed in volume_list /etc/lvm/lvm.conf: global/event_activation event_activation = 0 activation/auto_activation_volume_list auto_activation_volume_list = [ "ubuntu", "@ubuntu_vg" ] activation/auto_activation_volume_list #auto_activation_volume_list = [ "ubuntu", "@ubuntu_vg" ] >> tools VG/LV is activated at startup => KO even with journalctl log line : lvm[PID]: pvscan[PID] VG tools skip autoactivation lvm.conf settings are working because - Can be deactivated with vgchange -an tools - Can be reactivated due to activation/volume_list is commented /etc/lvm/lvm.conf: global/event_activation event_activation = 0 global/global_filter global_filter = [ "r|.*sda3|" ] activation/auto_activation_volume_list auto_activation_volume_list = [ "ubuntu", "@ubuntu_vg" ] >> tools VG/LV is activated at startup => KO even if vgs do not show the tools VG due to the global/global_filter settings. lvm.conf settings are working because - Can't be deactivated with vgchange -an tools due to the global/global_filter or nor list this tools VG/LV. + Can't be deactivated with vgchange -an tools due to the global/global_filter /etc/lvm/lvm.conf: global/event_activation event_activation = 0 activation/auto_activation_volume_list auto_activation_volume_list = [ ] >> tools VG/LV is activated at startup => KO even with an empty auto_activation_volume_list [ ] which disable any auto activation. A process or script bypass and does not honor the activation/auto_activation_volume_list, global/global_filter and global/event_activation settings in lvm.conf at startup and activate all available VG/LV without any trace in boot log. Any new VG/LV is always activated during startup even if these VG/LV are not related to the running system and configured to be not auto activated. Regards ** Description changed: On a freshly installed Ubuntu 20.04 LTS (raw minimal installation) with LVM on LUKS using https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019 as a basis /dev/sda2 => luks encrypted with LVM VG named "ubuntu" and LVM tag "ubuntu_vg" LV /boot named boot and LVM tag "ubuntu_vg,boot" LV /root named root with LVM tag "ubuntu_vg,root" LV /home named home with LVM tag "ubuntu_vg,home" LV /swap named swap with LVM tag "ubuntu_vg,swap" /dev/sda3 => LVM VG named "tools" VG and two LVs The tools VG and related LVs are always activated at startup despite the settings in /etc/lvm/lvm.conf. According to lvm2-activation-generator The lvm2-activation-generator is called by systemd(1) on boot to generate systemd units at runtime to activate LVM Logical Volumes (LVs) when global/event_activation=0 is set in lvm.conf(5). These units use vgchange -aay to activate LVs. - (vgchange -aay that honours the activation/auto_activation_volume_list setting) + (vgchange -aay that honors the activation/auto_activation_volume_list setting) With the following settings in lvm.conf: /etc/lvm/lvm.conf: global/event_activation event_activation = 0 activation/auto_activation_volume_list auto_activation_volume_list = [ "ubuntu", "@ubuntu_vg" ] activation/volume_list volume_list = [ "ubuntu", "@ubuntu_vg" ] >> tools VG/LV is activated at startup => KO even
[Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)
** Also affects: hplip (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793675 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714659 Title: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1714659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922295] [NEW] lvm.conf activation/auto_activation_volume_list not honored, VG is always activated at startup
Public bug reported: On a freshly installed Ubuntu 20.04 LTS (raw minimal installation) with LVM on LUKS using https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019 as a basis /dev/sda2 => luks encrypted with LVM VG named "ubuntu" and LVM tag "ubuntu_vg" LV /boot named boot and LVM tag "ubuntu_vg,boot" LV /root named root with LVM tag "ubuntu_vg,root" LV /home named home with LVM tag "ubuntu_vg,home" LV /swap named swap with LVM tag "ubuntu_vg,swap" /dev/sda3 => LVM VG named "tools" VG and two LVs The tools VG and related LVs are always activated at startup despite the settings in /etc/lvm/lvm.conf. According to lvm2-activation-generator The lvm2-activation-generator is called by systemd(1) on boot to generate systemd units at runtime to activate LVM Logical Volumes (LVs) when global/event_activation=0 is set in lvm.conf(5). These units use vgchange -aay to activate LVs. (vgchange -aay that honours the activation/auto_activation_volume_list setting) With the following settings in lvm.conf: /etc/lvm/lvm.conf: global/event_activation event_activation = 0 activation/auto_activation_volume_list auto_activation_volume_list = [ "ubuntu", "@ubuntu_vg" ] activation/volume_list volume_list = [ "ubuntu", "@ubuntu_vg" ] >> tools VG/LV is activated at startup => KO even with journalctl log line: lvm[PID]: pvscan[PID] VG tools skip autoactivation lvm.conf settings are working because - Can be deactivated with vgchange -an tools - Can't be reactivated with vgchange -ay tools due to tools VG/Tags not listed in volume_list /etc/lvm/lvm.conf: global/event_activation event_activation = 0 activation/auto_activation_volume_list auto_activation_volume_list = [ "ubuntu", "@ubuntu_vg" ] activation/auto_activation_volume_list #auto_activation_volume_list = [ "ubuntu", "@ubuntu_vg" ] >> tools VG/LV is activated at startup => KO even with journalctl log line : lvm[PID]: pvscan[PID] VG tools skip autoactivation lvm.conf settings are working because - Can be deactivated with vgchange -an tools - Can be reactivated due to activation/volume_list is commented /etc/lvm/lvm.conf: global/event_activation event_activation = 0 global/global_filter global_filter = [ "r|.*sda3|" ] activation/auto_activation_volume_list auto_activation_volume_list = [ "ubuntu", "@ubuntu_vg" ] >> tools VG/LV is activated at startup => KO even if vgs do not show the tools VG due to the global/global_filter settings. lvm.conf settings are working because Can't be deactivated with vgchange -an tools due to the global/global_filter /etc/lvm/lvm.conf: global/event_activation event_activation = 0 activation/auto_activation_volume_list auto_activation_volume_list = [ ] >> tools VG/LV is activated at startup => KO even with an empty auto_activation_volume_list [ ] which disable any auto activation. A process or script bypass and does not honor the activation/auto_activation_volume_list, global/global_filter and global/event_activation settings in lvm.conf at startup and activate all available VG/LV without any trace in boot log. Any new VG/LV is always activated during startup even if these VG/LV are not related to the running system and configured to be not auto activated. Regards ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Description changed: On a freshly installed Ubuntu 20.04 LTS (raw minimal installation) with LVM on LUKS using https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019 as a basis - /dev/sda2 => luks encrypted with LVM - VG named "ubuntu" and LVM tag "ubuntu_vg" - LV /boot named boot and LVM tag "ubuntu_vg,boot" - LV /root named root with LVM tag "ubuntu_vg,root" - LV /home named home with LVM tag "ubuntu_vg,home" - LV /swap named swap with LVM tag "ubuntu_vg,swap" + /dev/sda2 => luks encrypted with LVM + VG named "ubuntu" and LVM tag "ubuntu_vg" + LV /boot named boot and LVM tag "ubuntu_vg,boot" + LV /root named root with LVM tag "ubuntu_vg,root" + LV /home named home with LVM tag "ubuntu_vg,home" + LV /swap named swap with LVM tag "ubuntu_vg,swap" /dev/sda3 => LVM VG named "tools" VG and two LVs The tools VG and related LVs are always activated at startup despite the settings in /etc/lvm/lvm.conf. According to lvm2-activation-generator The lvm2-activation-generator is called by systemd(1) on boot to -generate systemd units at runtime to activate LVM Logical Volumes -(LVs) when global/event_activation=0 is set in lvm.conf(5). -These units use vgchange -aay to activate LVs. + generate systemd units at runtime to activate LVM Logical Volumes + (LVs) when global/event_activation=0 is set in lvm.conf(5). + These units use vgchange -aay to activate LVs. (vgchange -aay that honours the activation/auto_activation_volume_list setting) With the following settings in lvm.conf: /etc/lvm/lvm.conf: global/event_activation
[Bug 1921445] Re: bootstrapping 1.50
1.50.0+dfsg1+llvm-0ubuntu5 is allowed to migrate. ** Changed in: rustc (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/1921445 Title: bootstrapping 1.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1921445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922212] Re: SSHD does not honor configuration files
Hello Jeffrey, this reminds me a little of https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1876320 -- but it's also something that should have been addressed last year. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922212 Title: SSHD does not honor configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922293] [NEW] Snaps appear broken on 21.04 Beta
Public bug reported: I've attempted to use two different userland snaps (qownnotes and keepassxc) neither function. When attempting to launch I get the following error: ``` chalbersma@abdos:~$ qownnotes cannot perform operation: mount --rbind /dev /tmp/snap.rootfs_t3kehe//dev: No such file or directory ``` Additionally the snaps installed "by default" have a note of "broken" next to them : ``` chalbersma@abdos:~$ sudo snap list Name Version RevTracking Publisher Notes core18 1997 latest/stablecanonical✓ broken gnome-3-34-1804 66 latest/stable/… canonical✓ broken gtk-common-themes 1514 latest/stable/… canonical✓ broken qownnotes 21.3.9 8183 latest/stablepbek- snap-store 518latest/stable/… canonical✓ broken snapd 11402 latest/stablecanonical✓ broken ``` ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922293 Title: Snaps appear broken on 21.04 Beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898152] Re: upgrade fails to calculate if gnuradio-dev is installed
The python-dev test case also continues to pass with the dist-upgrader from -proposed. bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-j0n9zh89$ head /var/log/dist-upgrade/main.log 2021-04-01 13:38:43,120 INFO Using config files '['./DistUpgrade.cfg.bionic']' 2021-04-01 13:38:43,120 INFO uname information: 'Linux clean-bionic-amd64 5.4.0-70-generic #78~18.04.1-Ubuntu SMP Sat Mar 20 14:10:07 UTC 20 21 x86_64' 2021-04-01 13:38:43,503 INFO apt version: '1.6.12ubuntu0.2' 2021-04-01 13:38:43,503 INFO python version: '3.6.9 (default, Jan 26 2021, 15:33:00) [GCC 8.4.0]' 2021-04-01 13:38:43,507 INFO release-upgrader version '20.04.31' started 2021-04-01 13:38:43,511 INFO locale: 'en_US' 'UTF-8' 2021-04-01 13:38:43,558 DEBUG Using 'DistUpgradeViewText' view 2021-04-01 13:38:43,597 DEBUG enable dpkg --force-overwrite 2021-04-01 13:38:43,620 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-j0n9zh89$ apt-cache policy python-dev python-dev: Installed: (none) Candidate: (none) Version table: bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-j0n9zh89$ apt-cache policy python2-dev python2-dev: Installed: 2.7.17-2ubuntu4 Candidate: 2.7.17-2ubuntu4 Version table: *** 2.7.17-2ubuntu4 500 500 http://ubuntu.osuosl.org/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-j0n9zh89$ apt-cache policy python-dev-is-python2 python-dev-is-python2: Installed: 2.7.17-4 Candidate: 2.7.17-4 Version table: *** 2.7.17-4 500 500 http://ubuntu.osuosl.org/ubuntu focal/universe amd64 Packages 500 http://ubuntu.osuosl.org/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ** 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/1898152 Title: upgrade fails to calculate if gnuradio-dev is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922260] Re: `make olddefconfig` results in a kernel missing support for touchpad and wifi
** Patch added: "This patch resolves one part of the issue." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922260/+attachment/5483260/+files/0001-Add-a-configuration-option-for-8821CE-wireless-cards.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922260 Title: `make olddefconfig` results in a kernel missing support for touchpad and wifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921425] Re: rabbitmq-server logrotate issue
This bug was fixed in the package rabbitmq-server - 3.8.9-2 --- rabbitmq-server (3.8.9-2) unstable; urgency=medium * Do not use the /usr/sbin/rabbitmq-server wrapper in systemd service file (Closes: #947873). * Use logrotate daily instead of weekly, and do not override the number of logs, so we don't keep too much of them. * Do not use a sharedscripts, as rabbitmq-server detects the log rotation by itself (LP: #1921425). -- Thomas Goirand Fri, 26 Mar 2021 14:24:52 +0100 ** Changed in: rabbitmq-server (Ubuntu) Status: Triaged => 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/1921425 Title: rabbitmq-server logrotate issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1921425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922291] Re: day of the week is missing
** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+attachment/5483255/+files/Dependencies.txt ** Attachment removed: "ShellJournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+attachment/5483259/+files/ShellJournal.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+attachment/5483258/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+attachment/5483257/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "GsettingsChanges.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+attachment/5483256/+files/GsettingsChanges.txt ** Summary changed: - day of the week is missing + Day of the week is missing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922291 Title: Day of the week is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922291] [NEW] Day of the week is missing
Public bug reported: For several days now, the day of the week is not displayed on the time sub-menu like the screenshot in the attachment, it seems to be a bug from the last update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 22:51:53 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Capture d’écran de 2021-03-30 20-57-24.png" https://bugs.launchpad.net/bugs/1922291/+attachment/5483254/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-03-30%2020-57-24.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922291 Title: Day of the week is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922290] Re: nautilus crashed with SIGSEGV in update_dbus_opened_locations()
** 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/1922290 Title: nautilus crashed with SIGSEGV in update_dbus_opened_locations() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1922290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922290] Re: nautilus crashed with SIGSEGV in update_dbus_opened_locations()
executing the command nautilus --version in a terminal window also crashes. ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922290 Title: nautilus crashed with SIGSEGV in update_dbus_opened_locations() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1922290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905020] Re: [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel-debug package
** Changed in: ubuntu-z-systems Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905020 Title: [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel- debug package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1905020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922289] [NEW] Rust-src does not contain libsrc & libcore sources
Public bug reported: I have installed rust-src package to provide IDE support for Rust, yet it lacked libstd/libcore sources that were actually desired. Older version, 1.43, does contain those sources, and you can easily see that upgrading to 1.47 removes about 28 MiB of files. I've tried looking up other packages to check if libstd sources are there using apt-file and haven't found any. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: rust-src 1.43.0+dfsg1+llvm-1~exp1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 23:22:11 2021 Dependencies: InstallationDate: Installed on 2017-03-05 (1488 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: rustc UpgradeStatus: Upgraded to groovy on 2020-12-22 (100 days ago) ** Affects: rustc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922289 Title: Rust-src does not contain libsrc & libcore sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1922289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921963] Re: SRU 3.36.9
Amr, Thanks for pointing it out! I've uploaded a yaru package 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/1921963 Title: SRU 3.36.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905491] Re: Recent (Nov 2020) ISO copied to USB Drive cannot load
Besides that, I don't known if it is better to continue with this bug or create a new one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905491 Title: Recent (Nov 2020) ISO copied to USB Drive cannot load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1905491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905491] Re: Recent (Nov 2020) ISO copied to USB Drive cannot load
Same happens to me on an Ubuntu 21.04 beta iso. It boots perfectly on an EFI laptop but fails on my PC with BIOS. I tried creating the bootable usb drive with startup-disk-creator and get the same results too with gnome-disks using the restore disk image. And it is not the first time I see that. I tried with several daily builds of Hirsute Hippo and always fails. I get the same error message too: Error can't find grub_platform. I think that is clearly a bug. But I don't know against which package should be filled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905491 Title: Recent (Nov 2020) ISO copied to USB Drive cannot load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1905491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
As I cannot update my kernel unless the second problem (freeze after suspend/resume) is fixed, and so can't many others, I'd love to hear if anyone plans to fix this bug. Using w/o problem : 5.4.0-66-generic Problem started from: 5.4.0-67-generic Linux Mint 20.1 Cinnamon Cinnamon 4.8.6 32GB RAM Intel© Core™ i7-7700K CPU @ 4.20GHz × 4 Intel Corporation HD Graphics 630 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905020] Re: [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel-debug package
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905020 Title: [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel- debug package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1905020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922267] Re: this program cannot be set as the default program (rhythmbox)
1. Right click an audio file and select "Properties" menu item. 2. Select "Open With" Tab in Properties Window. 3. Select "Rhythmbox" from the below application list and click "Set as default". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922267 Title: this program cannot be set as the default program (rhythmbox) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1922267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898152] Re: upgrade fails to calculate if gnuradio-dev is installed
I tested the python-doc test case with the version of the dist-upgrader from -proposed and it passed. bdmurray@clean-bionic-amd64:~$ head /var/log/dist-upgrade/main.log 2021-04-01 12:01:19,195 INFO Using config files '['./DistUpgrade.cfg.bionic']' 2021-04-01 12:01:19,196 INFO uname information: 'Linux clean-bionic-amd64 5.4.0-70-generic #78~18.04.1-Ubuntu SMP Sat Mar 20 14:10:07 UTC 2021 x86_64' 2021-04-01 12:01:19,594 INFO apt version: '1.6.12ubuntu0.2' 2021-04-01 12:01:19,594 INFO python version: '3.6.9 (default, Jan 26 2021, 15:33:00) [GCC 8.4.0]' 2021-04-01 12:01:19,597 INFO release-upgrader version '20.04.31' started 2021-04-01 12:01:19,601 INFO locale: 'en_US' 'UTF-8' 2021-04-01 12:01:19,671 DEBUG Using 'DistUpgradeViewText' view 2021-04-01 12:01:19,713 DEBUG enable dpkg --force-overwrite 2021-04-01 12:01:19,741 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' bdmurray@clean-bionic-amd64:~$ apt-cache policy python-doc python-doc: Installed: (none) Candidate: (none) Version table: bdmurray@clean-bionic-amd64:~$ apt-cache policy python2-doc python2-doc: Installed: 2.7.17-2ubuntu4 Candidate: 2.7.17-2ubuntu4 Version table: *** 2.7.17-2ubuntu4 500 500 http://ubuntu.osuosl.org/ubuntu focal/universe amd64 Packages 500 http://ubuntu.osuosl.org/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898152 Title: upgrade fails to calculate if gnuradio-dev is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676042] Update bug:, status confirmed, importance medium
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 status confirmed importance medium done -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmHRQACgkQH1G0ZBEH M/E/AAf+MZaZWPdkBWLx6pZV/wxe6uj8ONurmdDQokXiXWyCflydf9gJxCUX1FKb M51L4nlApghWR9uYf5lX0JYb8oaSsspIu8JMz5IS/7l29MeGS6b0wt0shPmQM6fY c2gcLdq9cbuLGw98ZonZf8Q2hCfYjtBI4SL2VxWSXZ3mcEWY4YP140iv053DmLnp BFtdQpgFX+1V5a7TC5B8UwzQ+i6eW7B7OIUM2J4KJrVcqdp9AOsYkWXKfiNVVCjj 0cB3PE4jsk/S+Q4DvJJR4A8FE7uJnfZGv0r01ugC0JMcxbRqOsOnv3VfNHKpPvCT PwsSlp9CfJKLto64SymqJU3SWIUTWw== =CdqP -END PGP SIGNATURE- ** Changed in: duplicity Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/676042 Title: duplicity falsely reports succeeded backup, empty manifest file To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/676042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908452] Re: MAAS stops working and deployment fails after `Loading ephemeral` step
We've hit this again on our production MAAS server, see below. We're in a position where we regularly need to check if our regiond processes are hung and restart them. I'd therefore like to ask for a bump in priority here. Any chance for a fix soon on the 2.9 branch? Does MAAS need simplestreams to cut a release before this fix can be picked up? ubuntu@maas:~$ ps -ef | grep region root 633597 633491 0 14:07 ?00:02:28 python3 /snap/maas/11778/sbin/regiond root 633814 633597 0 14:07 ?00:33:34 python3 /snap/maas/11778/sbin/regiond root 633816 633597 0 14:07 ?00:34:25 python3 /snap/maas/11778/sbin/regiond root 633817 633597 0 14:07 ?00:35:24 python3 /snap/maas/11778/sbin/regiond root 633818 633597 0 14:07 ?00:34:17 python3 /snap/maas/11778/sbin/regiond ubuntu648515 648489 0 18:19 pts/000:00:00 grep --color=auto region ubuntu@maas:~$ sudo strace -p 633597 strace: Process 633597 attached epoll_wait(3, [], 10, 94) = 0 epoll_wait(3, [], 10, 0)= 0 epoll_wait(3, [], 10, 99) = 0 epoll_wait(3, [], 10, 399) = 0 epoll_wait(3, [], 10, 0)= 0 epoll_wait(3, ^Cstrace: Process 633597 detached ubuntu@maas:~$ sudo strace -p 633814 strace: Process 633814 attached recvfrom(30, ^Cstrace: Process 633814 detached ubuntu@maas:~$ sudo lsof -i -a -p 633814 COMMANDPID USER FD TYPEDEVICE SIZE/OFF NODE NAME python3 633814 root 10u IPv6 696471999 0t0 TCP maas:5240->10.229.192.54:54706 (ESTABLISHED) python3 633814 root 14u IPv6 680163730 0t0 TCP *:5251 (LISTEN) python3 633814 root 15u IPv4 696151424 0t0 TCP localhost:51510->localhost:postgresql (ESTABLISHED) python3 633814 root 16u IPv6 683429160 0t0 TCP maas:5240->1.general.morphis.uk.vpn:38664 (CLOSE_WAIT) python3 633814 root 17u IPv4 680183835 0t0 TCP localhost:59674->localhost:postgresql (ESTABLISHED) python3 633814 root 18u IPv4 696173835 0t0 TCP localhost:51520->localhost:postgresql (ESTABLISHED) python3 633814 root 19u IPv6 680176399 0t0 TCP maas:5251->maas:45382 (CLOSE_WAIT) python3 633814 root 20u IPv4 696078469 0t0 TCP localhost:51486->localhost:postgresql (ESTABLISHED) python3 633814 root 21u IPv6 680176401 0t0 TCP *:5240 (LISTEN) python3 633814 root 22u IPv4 696206297 0t0 TCP localhost:51932->localhost:postgresql (ESTABLISHED) python3 633814 root 23u IPv6 680199940 0t0 TCP maas:5240->2.general.dannf.us.vpn:55866 (CLOSE_WAIT) python3 633814 root 26u IPv6 680154669 0t0 TCP maas:5240->2.general.dannf.us.vpn:55848 (ESTABLISHED) python3 633814 root 27u IPv4 696430193 0t0 TCP localhost:51948->localhost:postgresql (ESTABLISHED) python3 633814 root 28u IPv6 680199946 0t0 TCP maas:5240->2.general.dannf.us.vpn:55868 (CLOSE_WAIT) python3 633814 root 29u IPv4 696373443 0t0 TCP localhost:51938->localhost:postgresql (ESTABLISHED) python3 633814 root 30u IPv4 696457905 0t0 TCP maas:49652->images-maas-io.sawo.canonical.com:http (ESTABLISHED) python3 633814 root 31u IPv4 696394600 0t0 TCP localhost:51944->localhost:postgresql (ESTABLISHED) python3 633814 root 32u IPv4 696155256 0t0 TCP localhost:51502->localhost:postgresql (ESTABLISHED) ubuntu@maas:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908452 Title: MAAS stops working and deployment fails after `Loading ephemeral` step To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1908452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913284] Re: [plugin] [bcache] add a new bcache plugin
SRU verification for Focal passed. Attached a text file w/ steps and relevant info. ** Attachment added: "bcache-focal-verification2.txt" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1913284/+attachment/5483242/+files/bcache-focal-verification2.txt ** Tags removed: verification-needed-focal ** Tags added: 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/1913284 Title: [plugin] [bcache] add a new bcache plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1913284/+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
@kanashiro I believe you uploaded runc, can you perform verification for it ** Changed in: systemd (Ubuntu Xenial) 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/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 1916485] Re: test -x fails inside shell scripts in containers
marking verification-done-bionic for systemd (I don't see any verification steps listed for runc) -- 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 1916485] Re: test -x fails inside shell scripts in containers
root@lp1916485-b:~# wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz ... root@lp1916485-b:~# mkdir h root@lp1916485-b:~# cd h root@lp1916485-b:~/h# tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz ... root@lp1916485-b:~/h# dpkg -l systemd|grep systemd ii systemd237-3ubuntu10.45 amd64system and service manager root@lp1916485-b:~/h# dpkg -l libseccomp2|grep seccomp ii libseccomp2:amd64 2.4.3-1ubuntu3.18.04.3 amd64high level interface to Linux seccomp filter root@lp1916485-b:~/h# systemd-nspawn Spawning container h on /root/h. Press ^] three times within 1s to kill container. root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 root root 1083472 Feb 22 09:33 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail root@lp1916485-b:~/h# dpkg -l systemd|grep systemd ii systemd237-3ubuntu10.46 amd64system and service manager root@lp1916485-b:~/h# dpkg -l libseccomp2|grep seccomp ii libseccomp2:amd64 2.5.1-1ubuntu1~18.04.1 amd64high level interface to Linux seccomp filter root@lp1916485-b:~/h# systemd-nspawn Spawning container h on /root/h. Press ^] three times within 1s to kill container. root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 root root 1083472 Feb 22 09:33 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" root@h:~# ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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 918489] Re: duplicity allows a new, different passphrase if an archive cache exists
** Changed in: duplicity Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918489 Title: duplicity allows a new, different passphrase if an archive cache exists To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/918489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576051] Update bug #1576051, status confirmed, importance medium
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 status confirmed importance medium done -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmFfMACgkQH1G0ZBEH M/FnDQgAhImWqh76T9WUH4NzzfarEEZsdLKXg6lspkK14v3nEV0J1kd4PnsgxmL0 k0c2q3vcUOuB0QTyydWb5Jzf4C6JzmIRZEkJaHNojU7oFgyzu+AFq3r56/UdVFh/ yw84Ly3vaxN25BlR+T5kHENHtzmp9sMS8KdcECwh7EfxtxluItF/bkXk8kYukhlO WhnEkiyw/Fb6+5sQ0tl73t+V9zLOn2WrTLpSxaAsiZMel33aOBYgoPOic0v+Wpsv B407MFxAen5Z4EKHWwpQ2HLHik6OXiir6ZVX400+6inSJflqBCobJM0Lm/NH8OKu NacHNc7wXXHVGI9vKMliwg36OTJvCg== =/NIB -END PGP SIGNATURE- ** Changed in: duplicity Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576051 Title: Duplicity cannot handle sparse files efficiently To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1576051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652410] Update bug #1652410, status confirmed, importance medium
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 status confirmed importance medium done -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmFc0ACgkQH1G0ZBEH M/GUCwgAoXIyBDb6kUITjvrIJVhKO8CXv/94R1PxitsoYebTWK1D8TUkOWFmy+mS 2NFM/IsMk5XbIrMgPvaJCyp/CuGzehzIV6hBaQVyhOg9VcuAKSNJ4bSNeABmXqrM dh7GoiuY7ECn6gybCUznONyDvMJXbhR6/hqZgfOqDZGeNHNMtFpa+72qgcdpnuQh +ymv+CO9ZyVMqv2Zuh53U53AuBpB9O3NWKhTbYTB3uS8C546jvAzfUEApuSFVYS8 yerauyOPF+BoX6Kcvv2zT52exvrVjTFD6Nmrr3W1SItGP8ayg0lVgdgez3UDaZ/0 W0Euv6sOx6i5LUFmPkgVoJ9pfw6VbQ== =HUg5 -END PGP SIGNATURE- ** Changed in: duplicity Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652410 Title: Undescriptive duplicity/collection-status error when the backup directory contains two volumes with different file names and same volume number in the same backup set To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1652410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
FWIW, I tried reproducing this artificially by running 200 Kubernetes Pods on a freshly installed Focal and the issue did not occur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+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
marking verification-done-focal for systemd (I don't see any verification steps listed for runc) -- 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 1916485] Re: test -x fails inside shell scripts in containers
root@lp1916485-f:~# dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.5 amd64system and service manager root@lp1916485-f:~# wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz ... root@lp1916485-f:~# mkdir h root@lp1916485-f:~# cd h root@lp1916485-f:~/h# tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz ... root@lp1916485-f:~/h# systemd-nspawn Spawning container h on /root/h. Press ^] three times within 1s to kill container. root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 root root 1083472 Feb 22 09:33 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail root@lp1916485-f:~/h# dpkg -l libseccomp2|grep libseccomp ii libseccomp2:amd64 2.5.1-1ubuntu1~20.04.1 amd64high level interface to Linux seccomp filter root@lp1916485-f:~/h# dpkg -l systemd|grep systemd ii systemd245.4-4ubuntu3.6 amd64system and service manager root@lp1916485-f:~/h# systemd-nspawn Spawning container h on /root/h. Press ^] three times within 1s to kill container. root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 root root 1083472 Feb 22 09:33 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" root@h:~# ** Tags removed: verification-needed-focal ** Tags added: 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/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 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
groovy: fail with systemd 246.6-1ubuntu1.2 and libseccomp/2.5.1-1ubuntu1~20.10.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/s/systemd/20210330_120842_8a4eb@/log.gz pass with systemd/246.6-1ubuntu1.3 libseccomp/2.5.1-1ubuntu1~20.10.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/s/systemd/20210401_180916_9d4c2@/log.gz ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918696 Title: libseccomp 2.5.1 will break unit tests on ppc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898152] Re: upgrade fails to calculate if gnuradio-dev is installed
I tested the python-dbg scenario with the dist-upgrader from -proposed and that scenario continues to work and the upgrade is calculable. ** Description changed: Impact -- Users with the package gnuradio-dev installed on their system are unable to upgrade from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS as the upgrade is not calculatable. Given that changes to the python to python2 quirk have been previously made to ubuntu-release-upgrader we should ensure those previous test cases (LP: #1887544) still work. It isn't necessary to run the full upgrade go though, just calculating it should be sufficient. Test Case - [gnuradio-dev] 1) On an Ubuntu 18.04 LTS system install gnuradio-dev (or some set of packages which depend on it) 2) Run do-release-upgrade 3) Observe a message regarding the failure to calculate the upgrade With the dist-upgrader from -proposed there will be no such failure to calculate the upgrade. [python-dbg] 1) On an Ubuntu 18.04 LTS system install python-qt4-dbg (or some set of packages which depend on it) 2) Run do-release-upgrade - 3) Observe a message regarding a failure to calculate the upgrade + 3) The upgrade will be calculable. - With the dist-upgrader from -proposed there will be no such failure to - calculate the upgrade. + With the dist-upgrader from -proposed the upgrade should still be + calculable. [python-doc] 1) On an Ubuntu 18.04 LTS system install python-doc 2) Run do-release-upgrade 3) Say Y to removing obsolete packages 4) Observe that python-doc is still installed on the system With the version of the dist-upgrader from -proposed python-doc will not be installed after the upgrade and python2-doc will be. [python-dev] 1) On an Ubuntu 18.04 LTS system install python-dev 2) Run do-release-upgrade 3) Say Y to removing obsolete packages 4) Observe that python-dev is still installed on the system With the version of the dist-ugprader from -proposed python-dev will not be installed after the upgrade and python2-dev will be installed. Additionally, python-dev-is-python2 will be installed. Where Problems Could Occur -- As mentioned previously we could cause working upgrade paths with python- packages installed to failed. However, test cases have been added which cover those scenarios. SRU Team Special Note - This has not been fixed in Groovy because the code is not relevant for the upgrade path to Groovy. Original Description Fails complaining about possible issue with PPAs. When these are removed fails with no complaints about PPAs or anything else. Just asks for bug to be reported. - ProblemType: Bug - DistroRelease: Ubuntu 18.04 + ProblemType: BugDistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Oct 2 17:14:41 2020 InstallationDate: Installed on 2016-09-07 (1485 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) - PackageArchitecture: all - SourcePackage: ubuntu-release-upgrader + PackageArchitecture: allSourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-02 (0 days ago) VarLogDistupgradeTermlog: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898152 Title: upgrade fails to calculate if gnuradio-dev is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910264] Re: [plugin][ceph] include time-sync-status for ceph mon
SRU verification: Verification done on Bionic, Focal, and Groovy. Please refer comments above and let me know if there are questions. Thanks, Pon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910264 Title: [plugin][ceph] include time-sync-status for ceph mon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1910264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910264] Re: [plugin][ceph] include time-sync-status for ceph mon
Verified on Groovy with 4.1-1ubuntu0.20.10.1. Time sync status is collected as expected. Attached a reference. ** Attachment added: "time-sync-groovy-sru-verify.txt" https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1910264/+attachment/5483241/+files/time-sync-groovy-sru-verify.txt ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910264 Title: [plugin][ceph] include time-sync-status for ceph mon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1910264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
focal: fail with systemd 245.4-4ubuntu3.5 and libseccomp/2.5.1-1ubuntu1~20.04.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20210329_180851_bca64@/log.gz pass with systemd/245.4-4ubuntu3.6 and libseccomp/2.5.1-1ubuntu1~20.04.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20210401_173335_98ce7@/log.gz ** Tags removed: verification-needed-focal ** Tags added: 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/1918696 Title: libseccomp 2.5.1 will break unit tests on ppc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922280] [NEW] Trying to upgrade from 18.0.4 to 20.0.4
Public bug reported: Trying to upgrade from 18.0.4 to 20.0.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18 Uname: Linux 4.15.0-140-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 23:33:52 2021 InstallationDate: Installed on 2019-07-23 (618 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-04-01 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922280 Title: Trying to upgrade from 18.0.4 to 20.0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc
bionic: fails with systemd 237-3ubuntu10.45 and libseccomp/2.5.1-1ubuntu1~18.04.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20210330_001358_e01e0@/log.gz pass with systemd/237-3ubuntu10.46 and libseccomp/2.5.1-1ubuntu1~18.04.1 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20210401_151939_a172a@/log.gz ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918696 Title: libseccomp 2.5.1 will break unit tests on ppc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922279] [NEW] package libpam-systemd:amd64 245.4-4ubuntu3.5 failed to install/upgrade: пакунок знаходиться у поганому стані; потрібно перевстановити його до початку налаштування
Public bug reported: libpam-systemd:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) Description:Ubuntu 20.04.2 LTS Release:20.04 How to fix this Bug Thanks ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-systemd:amd64 245.4-4ubuntu3.5 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 31 15:52:24 2021 ErrorMessage: пакунок знаходиться у поганому стані; потрібно перевстановити його до початку налаштування InstallationDate: Installed on 2020-11-07 (144 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: systemd Title: package libpam-systemd:amd64 245.4-4ubuntu3.5 failed to install/upgrade: пакунок знаходиться у поганому стані; потрібно перевстановити його до початку налаштування UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922279 Title: package libpam-systemd:amd64 245.4-4ubuntu3.5 failed to install/upgrade: пакунок знаходиться у поганому стані; потрібно перевстановити його до початку налаштування To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1922279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output
** Also affects: vte2.91 (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/1922276 Title: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1922276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output
** Bug watch added: github.com/mate-desktop/mate-terminal/issues #372 https://github.com/mate-desktop/mate-terminal/issues/372 ** Also affects: mate-desktop via https://github.com/mate-desktop/mate-terminal/issues/372 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922276 Title: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1922276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
