[Bug 2064909] Re: Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on encrypted partition
Oooh, good catch. That *is* a bug that we should fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064909 Title: Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on encrypted partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2064909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055044] Re: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)
** Changed in: gimp (Ubuntu Oracular) 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/2055044 Title: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/2055044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061954] Re: filezilla crashed with SIGABRT in start_thread()
Hey, thanks for taking the time to make the patch! There are some problems that I noticed that I think you might want to fix so that we can get this into Ubuntu. Firstly, the SRU paperwork. The bug you're fixing may very well be a good one to SRU a fix for, but the SRU justification in your comment above is insufficient. Please read https://wiki.ubuntu.com/StableReleaseUpdates carefully, especially section 4 "Procedure". In particular: * The impact section could be made more verbose so that the SRU team has an understanding of *why* something is going wrong, not just *what* is going wrong. * The test plan is inadequate. We need a full, step-by-step list of instructions on how someone other than yourself should set up their systems for testing, and then the exact steps to take for testing. This doesn't have to be crazily detailed (you don't have to describe every single button and keystroke to use), but it needs to be detailed enough that someone else can do it themselves and verify both that the old version is broken and that the new version is fixed. * The "Where problems could occur" section has been left out entirely. This section is mandatory, as any fix, **no matter how small**, comes with regression potential. (This is slightly hard to imagine until you've mangled packages the way I have. :P) Show that you're "expecting the unexpected" here. * The "OTHER INFO" section appears to contain info that was intended for "Where problems could occur". The info in this section is insufficient for a "Where problems could occur" section as it simply states that the regression possibility is low, rather than describing what could go wrong. According to the SRU process documentation, "This (the "Where problems could occur" section) must **never** be "None" or "Low", or entirely an argument as to why your upload is low risk.". * The SRU template goes in the bug report description, not in a comment. Usually the way I do this without overwriting old changes is I edit the bug report, leave the original bug report at the bottom, and place the SRU paperwork at the top. Secondly, the patch itself has some problems: +libfilezilla (0.46.0-3.1build4) noble; urgency=medium ^^ * This version number is wrong. You're introducing an Ubuntu delta, so you need an "ubuntu" version number here, not a "build" version number. According to https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging (which is linked to from the SRU documentation), the version number that should be used here is 0.46.0-3.1ubuntu0.1. (And yes, I think that my suggested version number looks as insane as you think it does. Ubuntu version numbers are hard.) * Speaking of an Ubuntu delta, when you make Ubuntu-specific changes to a package, you need to modify debian/control to show that the package has Ubuntu changes. To do this, the 'Maintainer' field in debian/control needs to be converted to an 'XSBC-Original-Maintainer' field, and a new 'Maintainer' field put in its place identifying the Ubuntu Developers as being the maintainer, like so: Maintainer: Ubuntu Developers * The patch is missing Debian dep3 headers. See https://dep- team.pages.debian.net/deps/dep3/ for more information. You can add these pretty easily using `quilt header --dep3 -e`. I hope this is helpful! Thanks for taking the time to make and test the patch, and hopefully we'll be able to get it into Ubuntu soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061954 Title: filezilla crashed with SIGABRT in start_thread() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfilezilla/+bug/2061954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062071] Re: gff2gff.py crashed with ModuleNotFoundError in Noble
Fix is already in Debian and has been pulled into Oracular. ** Also affects: bcftools (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: bcftools (Ubuntu Oracular) Importance: Medium Status: Confirmed ** Changed in: bcftools (Ubuntu Noble) Status: New => Confirmed ** Changed in: bcftools (Ubuntu Oracular) 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/2062071 Title: gff2gff.py crashed with ModuleNotFoundError in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcftools/+bug/2062071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060740] Re: fsattr fails to run
At least at first glance, I think this is SRU-able: 2.2. Other safe cases ... Bugs which do not fit under above categories, but (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages (like X.org or the kernel). ... From https://wiki.ubuntu.com/StableReleaseUpdates All that's being done is adding a couple of build dependencies, the program appears to be useless without them so it can't get much worse, and this isn't critical infrastructure, so I think it can be SRU'd. ** Also affects: fstransform (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: fstransform (Ubuntu Oracular) Importance: Undecided Status: Confirmed ** Changed in: fstransform (Ubuntu Noble) Status: New => Confirmed ** Also affects: fstransform (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: fstransform (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: fstransform (Ubuntu Focal) 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/2060740 Title: fsattr fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstransform/+bug/2060740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Also note that even the system's build of Bubblewrap is not granted the ability to bypass user namespace restrictions as that would allow the restrictions to be bypassed by any application. Doing this to your own build of Bubblewrap will pose the same security issue. If you can avoid doing things the way you're doing, that would be best, otherwise just turning off the restriction or granting your build of Bubblewrap an exception at install time is probably the best you can do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Unless your app and Bubblewrap can both work without any capabilities in an unprivileged user namespace, things will probably go south. You should probably be installing an AppArmor profile for your app that allows you to use unprivileged user namespaces normally again, as described in Comment 5 (https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/comments/5). You can look at `/etc/apparmor.d/chrome` as an example profile, and make your profile similar. This will require that your build of Bubblewrap be installed into a static location on the filesystem - if you're depending on Bubblewrap working no matter where the binary is on the filesystem (for instance, if your app is portable and is shipped as a .tar.gz that people unpack into their home dir and then use), you'll need to turn off the user namespace restrictions entirely during the install process, as described in the Ubuntu 24.04 release notes (https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release- notes/39890): * Disable this restriction using a persistent setting by adding a new file (/etc/sysctl.d/60-apparmor-namespace.conf) with the following contents: kernel.apparmor_restrict_unprivileged_userns=0 Reboot. This is similar to the previous behaviour, but it does not mitigate against kernel exploits that abuse the unprivileged user namespaces feature. Try to avoid using the "disable unprivileged user namespace restriction" solution if at all possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055044] Re: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)
The regression mentioned above appears to have been a glitch in the s390x autopkgtest infra. I requested a retry. The test plan succeeded using the GIMP from noble-proposed - I can export an image as a PNG, then close GIMP and click "Discard" when prompted to save my changes and it closes cleanly. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055044 Title: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/2055044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
The Tor Browser is actually installable on Ubuntu, and we have privacy-conscious folks here who are Ubuntu Developers. We just were absolutely slammed in more ways than we imagined would happen this cycle and things slipped through the cracks. This is probably one of them. You can follow the instructions for adding an AppArmor profile to work around the issue (they're up somewhere in the comments, near the top). Also, where is your Tor Browser binary on your filesystem? We may be able to add a profile specifically for it. On Mon, May 6, 2024 at 2:55 PM Zed <2046...@bugs.launchpad.net> wrote: > > Probably not in scope but the Tor Browser also fails to start properly: > https://forum.torproject.org/t/ubuntu-24-04-daily-and-tor-tabs-crashing- > immediately/11822/7. I can see why Ubuntu might not want to allow such > programs but, a universal distribution should be cognizant that some of > its users value privacy and that default apparmor profiles make it > problematic for such users to maintain their privacy. > > -- > You received this bug notification because you are a member of Lubuntu > Packages Team, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/2046844 > > Title: > AppArmor user namespace creation restrictions cause many applications > to crash with SIGTRAP > > Status in AppArmor: > New > Status in Wike: > New > Status in akonadiconsole package in Ubuntu: > Fix Released > Status in akregator package in Ubuntu: > Fix Released > Status in angelfish package in Ubuntu: > Fix Released > Status in apparmor package in Ubuntu: > Fix Released > Status in bubblewrap package in Ubuntu: > Won't Fix > Status in cantor package in Ubuntu: > Fix Released > Status in devhelp package in Ubuntu: > Fix Released > Status in digikam package in Ubuntu: > Fix Released > Status in epiphany-browser package in Ubuntu: > Fix Released > Status in evolution package in Ubuntu: > Fix Released > Status in falkon package in Ubuntu: > Fix Released > Status in firefox package in Ubuntu: > Confirmed > Status in foliate package in Ubuntu: > Fix Committed > Status in freecad package in Ubuntu: > Invalid > Status in geary package in Ubuntu: > Fix Released > Status in ghostwriter package in Ubuntu: > Fix Released > Status in gnome-packagekit package in Ubuntu: > Invalid > Status in goldendict-webengine package in Ubuntu: > Fix Released > Status in guix package in Ubuntu: > New > Status in kalgebra package in Ubuntu: > Fix Released > Status in kchmviewer package in Ubuntu: > Fix Released > Status in kdeplasma-addons package in Ubuntu: > Fix Released > Status in kgeotag package in Ubuntu: > Fix Released > Status in kiwix package in Ubuntu: > Incomplete > Status in kmail package in Ubuntu: > Fix Released > Status in konqueror package in Ubuntu: > Fix Released > Status in kontact package in Ubuntu: > Fix Released > Status in loupe package in Ubuntu: > Fix Released > Status in marble package in Ubuntu: > Fix Released > Status in notepadqq package in Ubuntu: > Fix Released > Status in opam package in Ubuntu: > Fix Released > Status in pageedit package in Ubuntu: > Fix Released > Status in plasma-desktop package in Ubuntu: > Fix Released > Status in plasma-welcome package in Ubuntu: > Fix Released > Status in privacybrowser package in Ubuntu: > Invalid > Status in qmapshack package in Ubuntu: > Fix Released > Status in qutebrowser package in Ubuntu: > Fix Released > Status in rssguard package in Ubuntu: > Fix Released > Status in steam package in Ubuntu: > Fix Released > Status in supercollider package in Ubuntu: > Fix Released > Status in tellico package in Ubuntu: > Fix Released > Status in wike package in Ubuntu: > Fix Committed > > Bug description: > Hi, I run Ubuntu development branch 24.04 and I have a problem with > Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get > this error > > $ epiphany > bwrap: Creating new namespace failed: Permission denied > > ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch > dbus-proxy: Le processus fils s’est terminé avec le code 1 > Trappe pour point d'arrêt et de trace (core dumped) > > $ epiphany > bwrap: Creating new namespace failed: Permission denied > > ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch > dbus-proxy: Le processus fils s’est terminé avec le code 1 > Trappe pour point d'arrêt et de trace (core dumped) > > Thanks for your help! > > To manage notifications about this bug go to: > https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to:
[Bug 2055044] Re: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)
** Changed in: gimp (Ubuntu Noble) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055044 Title: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/2055044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055044] Re: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)
Fix verified on Noble. Will be uploading and submitting to the SRU team soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055044 Title: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/2055044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064909] Re: Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on encrypted partition
It looks like you don't have a separate /boot partition being created? All Ubuntu flavors use Canonical's build of GRUB (naturally), and Canonical explicitly **does not support /boot being located on an encrypted partition.** It actually creates additional security risks to do so as Canonical doesn't test the code that handles encrypted /boot. Most likely what broke this is we changed from LUKS1 to LUKS2 in Lubuntu to increase security. I do not believe GRUB supports LUKS2. As encrypted /boot is not supported, and as there are security concerns when using LUKS1, I don't think we probably should fall back to LUKS1. If you're *really* determined to install with /boot on an encrypted partition despite the fact that this is dangerous, try running `sudo nano /etc/calamares/modules/partition.conf`, and change `luksGeneration: luks2` to `luksGeneration: luks1`. Then try installing with one big encrypted partition again. Again, **this is dangerous**, and also it has a good chance of breaking if you use a keyboard layout other than US. Hope this is helpful! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064909 Title: Lubuntu and Kubuntu 24.04 fail to decrypt on boot when installed on encrypted partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2064909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055044] Re: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)
Looks like Jeremy Bicha has a new GIMP uploaded to Oracular which will fix this there. The fix will still need backported to Noble, which I intend on doing. ** Changed in: gimp (Ubuntu Oracular) Status: New => Triaged ** Changed in: gimp (Ubuntu Oracular) 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/2055044 Title: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/2055044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055044] Re: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)
m /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #30 0x55b1368d45b6 in ?? () No symbol table info available. #31 0x7f43ecccef77 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #32 0x7f43ecba3c42 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #33 0x7f43eccd0adb in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #34 0x7f43eccd40a6 in g_object_run_dispose () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #35 0x55b1368d5f96 in ?? () No symbol table info available. #36 0x7f43eccc51fa in g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #37 0x7f43eccf41fc in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #38 0x7f43ecce4f31 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #39 0x7f43ecce5161 in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #40 0x7f43ecce5223 in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #41 0x7f43eccc51fa in g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #42 0x7f43eccf41fc in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #43 0x7f43ecce4f31 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #44 0x7f43ecce5161 in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #45 0x7f43ecce5223 in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #46 0x7f43ed6989c6 in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 No symbol table info available. #47 0x7f43eccc51fa in g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #48 0x7f43eccf4340 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #49 0x7f43ecce4f31 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #50 0x7f43ecce5161 in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #51 0x7f43ecce5223 in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #52 0x7f43ed6991d9 in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 No symbol table info available. #53 0x7f43ed7434d7 in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 No symbol table info available. #54 0x7f43eccc51fa in g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #55 0x7f43eccf4888 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #56 0x7f43ecce4892 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #57 0x7f43ecce5161 in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #58 0x7f43ecce5223 in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #59 0x7f43ed86f024 in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 No symbol table info available. #60 0x7f43ed741094 in gtk_propagate_event () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 No symbol table info available. #61 0x7f43ed7426db in gtk_main_do_event () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 No symbol table info available. #62 0x7f43edbcb16b in ?? () from /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 No symbol table info available. #63 0x7f43ecbc51c5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #64 0x7f43ecc24247 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #65 0x7f43ecbc5b87 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #66 0x55b13688a515 in app_run () No symbol table info available. #67 0x55b13688041f in main () No symbol table info available. [Inferior 1 (process 23798) detached] ``` ** Changed in: gimp (Ubuntu) Status: Confirmed => Triaged ** Changed in: gimp (Ubuntu) Importance: Undecided => High ** Changed in: gimp (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) ** Also affects: gimp (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gimp (Ubuntu Oracular) Importance: High Assignee: Aaron Rainbolt (arraybolt3) Status: Tr
[Bug 2064973] [NEW] GIMP crashes when closed just after exporting a PNG image
Public bug reported: Steps to reproduce: 1. Launch GIMP on Kubuntu 24.04. 2. Create a new image. 3. Draw something in it (a black squiggly line with the default brush is fine) 4. Export the image as a PNG. 5. Close GIMP. Expected result: GIMP closes normally. Actual result: Segmentation fault. Debugging info and GDB backtrace: /usr/bin/gimp: Gimp-Widgets-CRITICAL: gimp_message_box_set_primary_text: assertion 'GIMP_IS_MESSAGE_BOX (box)' failed (gimp:22119): Gtk-CRITICAL **: 19:09:22.189: IA__gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed (gimp:22119): GLib-GObject-CRITICAL **: 19:09:22.189: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Thread 1 "gimp" received signal SIGSEGV, Segmentation fault. Downloading source file /build/gtk+2.0-ngwfxy/gtk+2.0-2.24.33/debian/build/shared/gtk/../../../../gtk/gtkbutton.c 0x77a97968 in gtk_button_construct_child (button=button@entry=0x59f767a0) at ../../../../gtk/gtkbutton.c:955 warning: 955../../../../gtk/gtkbutton.c: No such file or directory (gdb) bt #0 0x77a97968 in gtk_button_construct_child (button=button@entry=0x59f767a0) at ../../../../gtk/gtkbutton.c:955 #1 0x77a989ed in IA__gtk_button_set_label (label=, button=0x59f767a0) at ../../../../gtk/gtkbutton.c:1816 #2 IA__gtk_button_set_label (button=0x59f767a0, label=) at ../../../../gtk/gtkbutton.c:1805 #3 0x76fc51fa in object_set_property (object=0x59f767a0, pspec=0x58f50170, value=0x7fffb770, nqueue=0x0, user_specified=) at ../../../gobject/gobject.c:2169 #4 0x76fc84b6 in g_object_set_valist (var_args=0x7fffb820, first_property_name=, object=0x7fffb820) at ../../../gobject/gobject.c:3138 #5 g_object_set_valist (object=object@entry=0x59f767a0, first_property_name=first_property_name@entry=0x55aedc5b "label", var_args=var_args@entry=0x7fffb820) at ../../../gobject/gobject.c:3099 #6 0x76fc892d in g_object_set (_object=0x59f767a0, first_property_name=first_property_name@entry=0x55aedc5b "label") at ../../../gobject/gobject.c:3314 #7 0x55693445 in quit_close_all_dialog_container_changed (images=, image=, private=0x59fb0710) at dialogs/quit-dialog.c:363 #8 0x76fb42fa in g_closure_invoke (closure=0x59f8adc0, return_value=0x0, n_param_values=2, param_values=0x7fffbb30, invocation_hint=0x7fffba80) at ../../../gobject/gclosure.c:834 #9 0x76fe390c in signal_emit_unlocked_R.isra.0 (node=node@entry=0x7fffbc20, detail=detail@entry=0, instance=instance@entry=0x59fa5cb0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffbb30) at ../../../gobject/gsignal.c:3888 #10 0x76fd4591 in signal_emit_valist_unlocked (instance=instance@entry=0x59fa5cb0, signal_id=signal_id@entry=33, detail=detail@entry=0, var_args=var_args@entry=0x7fffbd90) at ../../../gobject/gsignal.c:3520 #11 0x76fd47c1 in g_signal_emit_valist (instance=0x59fa5cb0, signal_id=33, detail=0, var_args=var_args@entry=0x7fffbd90) at ../../../gobject/gsignal.c:3263 #12 0x76fd4883 in g_signal_emit (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3583 #13 0x559391b3 in gimp_container_remove (container=0x59fa5cb0, object=0x59cc0330) at core/gimpcontainer.c:684 #14 0x559b9f3c in gimp_list_clear (container=0x59fa5cb0) at core/gimplist.c:313 #15 0x55938cf4 in gimp_container_clear (container=0x59fa5cb0) at core/gimpcontainer.c:822 #16 gimp_container_clear (container=0x59fa5cb0) at core/gimpcontainer.c:815 #17 0x55939fa5 in gimp_container_dispose (object=0x59fa5cb0) at core/gimpcontainer.c:247 #18 0x76fc33fe in g_object_unref (_object=0x59fa5cb0) at ../../../gobject/gobject.c:4381 #19 0x556912de in quit_close_all_dialog_free (private=0x59fb0710) at dialogs/quit-dialog.c:290 #20 0x76fbe137 in weak_refs_notify (data=0x59ec3140) at ../../../gobject/gobject.c:3643 #21 0x76e924e3 in g_data_set_internal (datalist=, key_id=, new_data=, new_destroy_func=, dataset=0x0) at ../../../glib/gdataset.c:468 #22 0x76fc032b in g_object_real_dispose (object=0x59f868c0) at ../../../gobject/gobject.c:1752 #23 0x76fc36c4 in g_object_run_dispose (object=0x59f868c0) at ../../../gobject/gobject.c:1839 #24 g_object_run_dispose (object=0x59f868c0) at ../../../gobject/gobject.c:1829 #25 0x55692d5f in quit_close_all_dialog_response (dialog=, response_id=-5, private=) at dialogs/quit-dialog.c:304 #26 0x76fb42fa in g_closure_invoke (closure=0x59fa5e00, return_value=0x0, n_param_values=2, param_values=0x7fffc270, invocation_hint=0x7fffc1c0) at ../../../gobject/gclosure.c:834 #27 0x76fe390c in signal_emit_unlocked_R.isra.0
[Bug 2060352] Re: Terminator cannot resize window anymore
This bug still affects me. I can still resize with Alt+F8, but mouse interactions are limited to the original window size (i.e., if I resize with Alt+F8, I can only click on an area the size of the original window to focus the terminal). Purging and re-installing had no effect. DistroRelease: Ubuntu 24.04 Package: terminator 2.1.3-1 Uname: Linux 6.8.0-31-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 6 2024 17:47 ET -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060352 Title: Terminator cannot resize window anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/2060352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900266] Re: Lubuntu Installer does not provide LVM
LUKS2 works just fine in the manual partitioner of Calamares, but LVM does not last I tried. If you use LUKS2 *without* LVM, everything works great. I'm not sure why the upstream Calamares devs exposed LVM in the user interface when it was still incomplete, but they did, and I think it's *still* incomplete in the version that ended up on the released 24.04 ISO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900266 Title: Lubuntu Installer does not provide LVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1900266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
Would it still get fixed even if the bug is invalid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064483] Re: Ubuntu 24.04 doesn't respect vm.swappiness
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: Ubuntu Noble Importance: Undecided Status: New ** No longer affects: ubuntu ** No longer affects: Ubuntu Noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
I also saw that it would boot the 6.9-rc kernel and the 6.8.7 kernel 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/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062436] Re: Kubuntu: slideshow states that we ship VLC by default. we do not
Screenshot of the problematic slide ** Description changed: + [ Impact ] + + Due to an oversight during the creation of refreshed branding, it was + mistakenly stated that the VLC media player ships by default in Kubuntu. + This is false, Kubuntu ships the Haruna media player by default. See the + attached screenshot. This should be easily fixable by changing "VLC" to + "Haruna Media Player" in the problematic slide. + + [ Test Plan ] + + * Boot a Kubuntu 24.04 live ISO. + * Install into the live session an updated calamares-settings-kubuntu and calamares-settings-ubuntu-common package pair that comes with the fixed slide. + * Install Kubuntu, and ensure that the slide is properly updated and contains accurate info during the installation. + + [ Where problems could occur ] + + If the slide somehow becomes corrupted during saving (which I have seen + happen!), it could break that slide (or even the whole slideshow or + installer) entirely. This would be rather severe, however the test plan + above will easily catch such issues. + + - + + Original bug report: + Kubuntu: slideshow states that we ship VLC by default. we do not Release: noble In 03_Built-in_Applications.png We have shipped haruna media player for a release or 2 instead. ** Attachment added: "bad-slide.jpg" https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2062436/+attachment/5773340/+files/bad-slide.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062436 Title: Kubuntu: slideshow states that we ship VLC by default. we do not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2062436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
@juergh I'm now able to boot 6.8.0-31-generic with that package (from that PPA) added to my system! Nicely done! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
Once I'm back with the system I'll test and let you know ASAP! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] [NEW] Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
Public bug reported: [ Impact ] During the 24.04 cycle, an update was made to Plymouth. This update apparently mandated the includsion of a lot more keyboard layouts into the `keymap-render.png` file for each Plymouth theme, which is used by Plymouth to display what keyboard layout the user should type in when providing a disk decryption passphrase. The changes made to Plymouth are not compatible with the older `keymap-render.png` files, meaning that if a user installs with FDE enabled, the keyboard layout shown to them on the Plymouth screen will **not** be the keyboard layout actually in use. For instance, if you install a system using the US English keyboard layout, you will be told you should type in Norse (layout `no`) to decrypt the disk, despite the fact that the layout actually in use is indeed `us`. While the `spinner` Plymouth theme in use by Ubuntu got the needed update, and Kubuntu and Ubuntu Cinnamon both got the needed updates, many if not all of the remaining Plymouth themes were not updated, meaning FDE users are being shown confusing keyboard layout information every time they boot their system. The solution is to copy the `keymap-render.png` file from the `spinner` Plymouth theme into the Plymouth themes for each affected flavor. So far Lubuntu and Ubuntu Unity are known to be affected. It is likely that other flavors are as well. [ Test Plan ] * For each flavor, do an encrypted installation and observe whether the wrong keyboard layout is shown on the decryption screen. Ideally, do each installation with a different keyboard layout selected. * For each affected flavor, install a Plymouth theme package that has the updated keymap-render.png file, then reboot the system. * Observe the decryption screen and ensure the proper keyboard layout is shown. [ Where problems could occur ] If the keymap-render.png file from `spinner` is also wrong in some way (which I have not seen yet), then applying updates in this way will result in everyone's decryption keyboard layout indicator being broken in the same way. Doing each installation with a different keyboard layout should detect if the image is obviously broken and only just so happens to work with the couple of keyboard layouts I've already tried. ** Affects: lubuntu-artwork (Ubuntu) Importance: High Status: New ** Affects: plymouth-theme-ubuntu-unity (Ubuntu) Importance: High Status: New ** Affects: lubuntu-artwork (Ubuntu Noble) Importance: High Status: New ** Affects: plymouth-theme-ubuntu-unity (Ubuntu Noble) Importance: High Status: New ** Also affects: plymouth-theme-ubuntu-unity (Ubuntu) Importance: Undecided Status: New ** Also affects: lubuntu-artwork (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: plymouth-theme-ubuntu-unity (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: lubuntu-artwork (Ubuntu Noble) Importance: Undecided => High ** Changed in: plymouth-theme-ubuntu-unity (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
For the record 6.8.0-31-generic also does not boot on the hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063403] Re: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable
This affects all of Kubuntu, Lubuntu, Ubuntu Unity. However, since the fix only affects OEM mode, we will not have to entirely retest all three after respinning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063403 Title: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063403] [NEW] /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable
Public bug reported: Steps to reproduce: 1: Boot an ISO of Kubuntu 24.04 Release Candidate. 2: Select "OEM mode (for manufacturers)" at bootup. 3: Proceed through the installation. 4: Boot into the OEM user. Expected result: The system should boot normally. Actual result: Plasma will fail to start. Reason: I foolishly instructed a fellow Ubuntu Developer to add code to calamares-settings-ubuntu that drops a desktop file into /home/oem/Desktop that allows exiting OEM configuration mode easily (similar to how oem-config works). I failed to take into account that having the code drop this file into place when the code runs as root would mean that /home/oem/Desktop (and also /home/oem) would end up owned by root. Because they are owned by root, Plasma is unable to start. LXQt starts, but probably won't function as expected. It's not yet known what Unity will do but it can't be too pretty. This requires only one line of code to fix per release - a simple `chown -R oem:oem /home/oem` is needed after extracting the OEM mode tarball into the root filesystem of the installed system. This is a very safe change to make because it's confined only to OEM mode (the code never runs outside of an OEM installation context), and, well, OEM mode is already hopelessly broken, we can't break it much more :P ** Affects: calamares-settings-ubuntu (Ubuntu) Importance: Critical Assignee: Aaron Rainbolt (arraybolt3) Status: Triaged ** Changed in: calamares-settings-ubuntu (Ubuntu) Status: New => Triaged ** Changed in: calamares-settings-ubuntu (Ubuntu) Importance: Undecided => Critical ** Changed in: calamares-settings-ubuntu (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063403 Title: /home/oem and /home/oem/Desktop is owned by root after oem installation, causing the OEM configuration environment to be (nearly) unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063379] Re: Disk decryption prompt is broken
** Changed in: ubuntucinnamon-artwork (Ubuntu) Status: New => 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/2063379 Title: Disk decryption prompt is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntucinnamon-artwork/+bug/2063379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063379] [NEW] Disk decryption prompt is broken
Public bug reported: Steps to reproduce: 1. Boot the Ubuntu Cinnamon ISO on any UEFI-capable computer. 2. Install Ubuntu Cinnamon with LVM and encryption enabled. 3. Reboot and wait for the passphrase prompt to appear. Expected result: The passphrase prompt should be in the lower area of the screen and should show the keyboard layout that was in use when using the installer. Actual result: The passphrase prompt is in the upper area of the screen, potentially covering over parts of the UEFI firmware logo, and the keyboard layout displayed is incorrect (for instance if you used the US keyboard layout, it will show "no" instead). This should be fixable with some Plymouth theme tweaks. The issue with the keyboard layout indicator can be fixed by copying over /usr/share/plymouth/themes/spinner/keymap-render.png into the Plymouth theme for Ubuntu Cinnamon. The positioning of the passphrase prompt is, I believe, configurable. ** Affects: ubuntucinnamon-artwork (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/2063379 Title: Disk decryption prompt is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntucinnamon-artwork/+bug/2063379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063366] [NEW] Xubuntu Minimal fails to install when using LVM + encryption
Public bug reported: Steps to reproduce: 1. Launch the installer. 2. Proceed through accepting default values. 3. When prompted how to install Xubuntu, use the "Erase disk" option, then click "Advanced options" and select LVM + encryption. (I'm not sure what the exact words here are as I did the installation in Spanish for testing purposes and couldn't read it.) 4. Finish the rest of the installer wizard, and allow the installation to begin. Expected result: The installation should succeed. Actual result: The installation fails. Relevant logs (typed across, may contain typos): curtin.util.ProcessExecution Error: Unexpected error while running command. Command: ['cryptsetup', 'luksFormat', '/dev-sda3', '/tmp/luks-key-nubsqc2w'] Exit code: - Reason: [Errno 2] No such file or directory: 'cryptsetup' Suggested solution: Seed cryptsetup in Xubuntu Minimal. ** Affects: xubuntu-meta (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/2063366 Title: Xubuntu Minimal fails to install when using LVM + encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/2063366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
I've seen a report of the 6.9-rc5 kernel booting on the hardware. I have also had issues with Fedora Rawhide and NixOS booting on the hardware so I think it is an upstream issue with the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063354] Re: Calamares based flavours do not set grub-{efi, pc}/install_devices debconf
Oh, and this could result in failure to boot if Canonical ever rotates
their SBAT key again, since if GRUB doesn't update and the SBAT variable
does, SHIM will refuse to boot it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063354
Title:
Calamares based flavours do not set grub-{efi,pc}/install_devices
debconf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063354] Re: Calamares based flavours do not set grub-{efi, pc}/install_devices debconf
This is a release blocker for all of Lubuntu, Kubuntu, Ubuntu Unity
24.04. It will result in either confusing and unsightly debconf prompts
(in the case of Lubuntu), or it could result in GRUB never being updated
at all, presenting a security hole that could lead to Secure Boot bypass
(in the case of Kubuntu). It's unclear whether Ubuntu Unity will do the
former or the latter, but in either event this is NOT something we want
to let people end up with on their systems.
** Changed in: calamares-settings-ubuntu (Ubuntu)
Status: New => Confirmed
** Changed in: calamares-settings-ubuntu (Ubuntu)
Importance: Undecided => Critical
** Changed in: calamares-settings-ubuntu (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
** Changed in: calamares-settings-ubuntu (Ubuntu)
Milestone: None => ubuntu-24.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063354
Title:
Calamares based flavours do not set grub-{efi,pc}/install_devices
debconf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2063354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062438] Re: pkgselect module offers Thunderbird as a third-party app on Kubuntu when Thunderbird ships with Kubuntu
Marking as Critical as this is a very user-visible papercut that cannot be fixed via 0-day SRU for the initial release. ** Changed in: calamares-settings-ubuntu (Ubuntu) Status: New => Confirmed ** Changed in: calamares-settings-ubuntu (Ubuntu) Importance: Undecided => Critical ** Changed in: calamares-settings-ubuntu (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062438 Title: pkgselect module offers Thunderbird as a third-party app on Kubuntu when Thunderbird ships with Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2062438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062075] Re: installer does not detect an installation of DragonflyBSD with UFS, HAMMER, or HAMMER2 filesystems
I haven't heard of UFS until today, and I don't think Calamares supports it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062075 Title: installer does not detect an installation of DragonflyBSD with UFS, HAMMER, or HAMMER2 filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2062075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061313] Re: New Kubuntu icon's transparent background looks broken in some areas
This is happening on the SDDM screen too. ** Changed in: kubuntu-settings (Ubuntu) Importance: Undecided => Critical ** Changed in: kubuntu-settings (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061313 Title: New Kubuntu icon's transparent background looks broken in some areas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2061313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061313] Re: New Kubuntu icon's transparent background looks broken in some areas
Marking this as High as it is an ugly glitch in an otherwise nicely refreshed user experience. The fix is trivial and safe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061313 Title: New Kubuntu icon's transparent background looks broken in some areas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2061313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062075] Re: Ubuntu installer does not detect other operating systems
Installed Windows 10 Home allowing it to use the entire SSD of my test system. Booted Kubuntu 24.04 ISO. Install alongside option appeared, used it. Installation succeeded. Upon reboot, I was presented with a GRUB menu, providing both "Ubuntu" and "Windows Boot Manager" options. Selecting "Ubuntu" boots me into Kubuntu 24.04, selecting "Windows Boot Manager" boots me into Windows 10. I cannot reproduce this bug. ** Changed in: calamares (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062075 Title: Ubuntu installer does not detect other operating systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2062075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062438] [NEW] pkgselect module offers Thunderbird as a third-party app on Kubuntu when Thunderbird ships with Kubuntu
Public bug reported: On the "Customize" screen of the installer, one of the additional apps you can install is Thunderbird. This makes sense on Lubuntu, where Thunderbird isn't installed by default, but Thunderbird *is* installed by default on Kubuntu, making the checkbox confusing and unnecessary there. ** Affects: calamares-settings-ubuntu (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/2062438 Title: pkgselect module offers Thunderbird as a third-party app on Kubuntu when Thunderbird ships with Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2062438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061676] Re: plymouth luks input prompt fails to display current locale and
Looks like our keymap render image is out-of-date and that's what causes this. If I copy the keymap-render.png from the `spinner` theme into the kubuntu-logo theme, things appear to work. ** Changed in: kubuntu-settings (Ubuntu) Importance: Undecided => Critical ** Summary changed: - plymouth luks input prompt fails to display current locale and + plymouth luks input prompt displays wrong keyboard layout locale -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061676 Title: plymouth luks input prompt displays wrong keyboard layout locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2061676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061676] Re: plymouth luks input prompt fails to display current locale and
Alright, so this is fun. Apparently there's an image full of keyboard layout labels in Kubuntu's plymouth theme. There also appears to be code that handles the password prompt, my assumption is that code extracts a slice of this image to show the keyboard layout to the user. Evidently it's doing it wrong. So now the question is what changed to break it and how to make it do it right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061676 Title: plymouth luks input prompt fails to display current locale and To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2061676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061676] Re: plymouth luks input prompt fails to display current locale and
This bug should be visual-only, there's code in the Calamares configuration specifically meant to make sure the real keyboard layout is set correctly. However, the wrong one being displayed even with the right one in use is definitely very confusing. Interesting that it doesn't happen with BGRT, I'll have to check that out. Thank you! ** Changed in: kubuntu-settings (Ubuntu) Status: New => Confirmed ** Changed in: kubuntu-settings (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061676 Title: plymouth luks input prompt fails to display current locale and To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2061676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062060] Re: Calamares automatically creates swapfile with manual partitioning without any warning
There's not really any good way around this. The default behavior in the old Ubiquity installer was (IIRC): * Don't create a swapfile by default when doing manual partitioning. * Create a swapfile by default for any other installation mode. With Calamares, we only have two options that aren't the same as this behavior: * Always create swap unless using Erase Disk mode and the user explicitly turns it off OR * Never create swap unless using Erase Disk mode and the user explicitly turns it on Both of these are different from Ubiquity's behavior. Going with "never create swap" has slightly more danger than going with "always create swap", and it has a higher chance of confusing a user who's used to Ubiquity. At some point (perhaps for the OO cycle), we should try and get in a feature that allows the user to customize which filesystem they want the swapfile to be on, like wxl mentioned. That would be my favorite solution, though it's too late to try it for this cycle. In the short term, we may need to just release note this bug and try to fix it via an SRU to add some notice that a swapfile is being created on the Summary screen, or disable swapfile creation when using manual partitioning (both options that wxl covered above). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062060 Title: Calamares automatically creates swapfile with manual partitioning without any warning To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/2062060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060429] Re: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
How long does it usually take to generate an initramfs on that system? The timeout was bumped up to 300 seconds (5 minutes). It seems very strange that it would take *longer* than that to run loadkeys (fast), setupcon (fast), and update-initramfs (slow but grief, not *that* slow I wouldn't think). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060429 Title: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061849] Re: Segmentation fault when calling standard library functions via `print` or `call` while debugging a `main()` function that accepts arguments
This does NOT occur on Noble. Trying it there, the following happens (note that I allowed debuginfod to be used but I'm not sure if that makes any difference): ``` (gdb) print strlen(statstr) 'strlen' has unknown return type; cast the call to its declared return type (gdb) print (size_t)strlen(statstr) $1 = 12 ``` However, attempting to use `print (size_t)strlen(statstr)` under Jammy still segfaults. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061849 Title: Segmentation fault when calling standard library functions via `print` or `call` while debugging a `main()` function that accepts arguments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2061849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061849] [NEW] Segmentation fault when calling standard library functions via `print` or `call` while debugging a `main()` function that accepts arguments
Public bug reported:
Steps to reproduce:
1: Create a file `test.c` with the following very simple program:
#include /* for printf */
#include /* for strlen */
int main(int argc, char **argv) {
const char *statstr = "hello there!";
printf("%s\n", statstr);
}
2: Save this file and compile it with `gcc -g test.c`.
3: Debug it with `gdb a.out`.
4: Run `b test.c:6` to set a breakpoint on the printf call.
5: Run `r` to start the program.
6: Run `print strlen(statstr)` to attempt to get the length of the statstr
string.
Expected result: The length of the string should be printed like so: `$1
= 12`
Actual result: gdb segfaults.
Segfault backtrace and info:
```
(gdb) print strlen(statstr)
Fatal signal: Segmentation fault
- Backtrace -
0x5ac45237f077 ???
0x5ac452481859 ???
0x5ac452481a22 ???
0x72ec6204251f ???
./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x5ac45232f020 ???
0x5ac4524d6637 ???
0x5ac45247f24a ???
0x5ac45247b827 ???
0x5ac45259e79f ???
0x5ac45259ecef ???
0x5ac4523b4654 ???
0x5ac4526aa394 ???
0x5ac4524829a4 ???
0x5ac452482d43 ???
0x5ac4524834c6 ???
0x72ec633a7e0d ???
0x5ac452481a95 ???
0x5ac452483374 ???
0x5ac45248168b ???
0x5ac452833815 ???
0x5ac452833caa ???
0x5ac45253f36c ???
0x5ac452541054 ???
0x5ac4522d715f ???
0x72ec62029d8f __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
0x72ec62029e3f __libc_start_main_impl
../csu/libc-start.c:392
0x5ac4522dcbf4 ???
0x ???
-
A fatal error internal to GDB has been detected, further
debugging is not possible. GDB will now terminate.
This is a bug, please report it. For instructions, see:
[Bug 2060845] Re: New branding Kubuntu
** Also affects: kubuntu-installer-prompt (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/2060845 Title: New branding Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061313] [NEW] New Kubuntu icon's transparent background looks broken in some areas
Public bug reported: Steps to reproduce: 1: Install the latest daily image of Kubuntu 24.04. 2: Log into the installed system. 3: Click on the application menu, then click "Shut Down". Expected result: The Kubuntu logo used as the user's avatar should be blue on a white background. Actual result: The Kubuntu logo used as the user's avatar is blue on a transparent background, and looks much too dark. Suggested solution: Remove transparency from the PNG image that contains the Kubuntu logo and replace it with white. ** Affects: kubuntu-settings (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/2061313 Title: New Kubuntu icon's transparent background looks broken in some areas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2061313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061260] Re: FFe: Package and seed fonts-space-grotesk, fonts-dm-mono
Both of these fonts have now been packaged and uploaded to the NEW queue. They build without problems and place the fonts in question into the correct locations. The packaging is based on the packaging for fonts-cabin (plus some extra guidance from fonts-tlwg-typist for the OTF vs. TTF font package separation in fonts-space-grotesk). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061260 Title: FFe: Package and seed fonts-space-grotesk, fonts-dm-mono To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/2061260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061260] Re: Package and seed fonts-space-grotesk, fonts-dm-mono, seed fonts-ibm-plex
** Changed in: kubuntu-meta (Ubuntu) Milestone: None => ubuntu-24.04 ** Changed in: kubuntu-meta (Ubuntu) Importance: Undecided => High ** Summary changed: - Package and seed fonts-space-grotesk, fonts-dm-mono, seed fonts-ibm-plex + FFe: Package and seed fonts-space-grotesk, fonts-dm-mono -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061260 Title: FFe: Package and seed fonts-space-grotesk, fonts-dm-mono To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/2061260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061260] [NEW] Package and seed fonts-space-grotesk, fonts-dm-mono, seed fonts-ibm-plex
Public bug reported: Space Grotesk and DM Mono are fonts used in Kubuntu's branding refresh. As these are intended to be a part of Kubuntu's branding, it is necessary that these fonts be included in the Kubuntu 24.04 final ISOs. (IBM Plex is also used in the branding refresh but is already packaged in Ubuntu and needs only to be seeded, assuming it isn't seeded already.) ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Package and seed fonts-space-grotesk, fonts-dm-mono + Package and seed fonts-space-grotesk, fonts-dm-mono, seed fonts-ibm-plex -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061260 Title: Package and seed fonts-space-grotesk, fonts-dm-mono, seed fonts-ibm- plex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/2061260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061251] [NEW] Ethernet connection doesn't resolve for atlantic driver
Public bug reported: Distribution Linux Mint 21.3 Cinnamon Package version Cinnamon 6.0.4 Graphics hardware in use Advanced Micro Devices, Inc. [AMD/ATI] Device 744c Frequency Always Bug description Connection to wifi but no ethernet. "Cable unplugged" Steps to reproduce Installed linux mint cinnamon 5.15.0-102 with the following motherboard. [GIGABYTE Z790 AORUS MASTER] (https://www.newegg.com/p/N82E16813145415?Item=N82E16813145415) Wifi and Ethernet didn't work correctly on initialization but after letting the update manager update all packages the Wi-fi began to work. Additional information Results of inxi -Fazy: aaron@aaron-Z790-AORUS-MASTER:~$ inxi -Fazy System: Kernel: 6.5.0-27-generic x86_64 bits: 64 compiler: N/A parameters: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic root=UUID=aa4e9320-2832-4baa-b801-2ff1f400b709 ro quiet splash Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy Machine: Type: Desktop System: Gigabyte product: Z790 AORUS MASTER v: -CF serial: Mobo: Gigabyte model: Z790 AORUS MASTER v: x.x serial: UEFI: American Megatrends LLC. v: F7 date: 03/07/2023 Battery: Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus M705 serial: charge: 55% (should be ignored) rechargeable: yes status: Discharging CPU: Info: model: Intel Core i9-14900K bits: 64 type: MST AMCP arch: N/A family: 6 model-id: 0xB7 (183) stepping: 1 microcode: 0x11D Topology: cpus: 1x cores: 24 mt: 8 tpc: 2 st: 16 threads: 32 smt: enabled cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32 KiB, 16x64 KiB L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB Speed (MHz): avg: 888 high: 1100 min/max: 800/5700:6000:4400 scaling: driver: intel_pstate governor: powersave cores: 1: 1045 2: 800 3: 1069 4: 800 5: 1100 6: 800 7: 1100 8: 800 9: 1097 10: 1061 11: 827 12: 800 13: 1100 14: 800 15: 1092 16: 1035 17: 800 18: 800 19: 800 20: 800 21: 800 22: 800 23: 800 24: 800 25: 800 26: 800 27: 800 28: 1100 29: 800 30: 800 31: 800 32: 800 bogomips: 203980 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: mmio_stale_data status: Not affected Type: retbleed status: Not affected Type: spec_rstack_overflow status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel vendor: Gigabyte driver: i915 v: kernel ports: active: none empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:a780 class-ID: 0300 Device-2: AMD vendor: XFX driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: HDMI-A-2 empty: DP-2,DP-3,DP-4 bus-ID: 03:00.0 chip-ID: 1002:744c class-ID: 0300 Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati,modesetting unloaded: fbdev,radeon,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") s-diag: 777mm (30.6") Monitor-1: HDMI-A-1 mapped: HDMI-A-2 model: GA01 serial: built: 2023 res: 2560x1440 dpi: 93 gamma: 1.2 size: 698x393mm (27.5x15.5") diag: 806mm (31.7") ratio: 16:9 modes: max: 2560x1440 min: 720x400 OpenGL: renderer: GFX1100 (gfx1100 LLVM 15.0.7 DRM 3.54 6.5.0-27-generic) v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes Audio: Device-1: Intel vendor: Gigabyte driver: snd_hda_intel v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403 Device-2: AMD driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab30 class-ID: 0403 Device-3: Kingston HyperX 7.1 Audio type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-7.1:5 chip-ID: 0951:16a4 class-ID: 0300 serial: Sound Server-1: ALSA v: k6.5.0-27-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Intel vendor: Rivet Networks driver: iwlwifi v: kernel port: N/A bus-ID: 00:14.3 chip-ID: 8086:7a70 class-ID: 0280 IF: wlo1 state: up mac: Device-2: Aquantia vendor: Gigabyte driver: atlantic v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 2 port: N/A bus-ID: 05:00.0 chip-ID: 1d6a:14c0 class-ID: 0200 IF: enp5s0 state: down mac: Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus
[Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
** Changed in: linux (Ubuntu Noble) 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/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
I'm able to recreate this issue as well. I also want to note that the 24.04 LTS Beta also does not boot with the "Try or Install" option in GRUB but it does boot the ISO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060928] Re: First boot after OEM install should have a desktop icon installed for finishing setup
** Changed in: calamares-settings-ubuntu (Ubuntu Noble) Milestone: None => ubuntu-24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060928 Title: First boot after OEM install should have a desktop icon installed for finishing setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060928] Re: First boot after OEM install should have a desktop icon installed for finishing setup
The user in the OEM session is always called "oem" (if I remember correctly) and the installer does not allow the user to change this, so it should be easy enough to drop the right desktop file in place. ** Also affects: calamares-settings-ubuntu (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: calamares-settings-ubuntu (Ubuntu Noble) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) ** Changed in: calamares-settings-ubuntu (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060928 Title: First boot after OEM install should have a desktop icon installed for finishing setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060905] [NEW] Plymouth screen does not appear during startup and shutdown of an installed system
Public bug reported: OS: Ubuntu Cinnamon Noble Beta. Steps to reproduce: 1: Boot the Ubuntu Cinnamon ISO. 2: Install Ubuntu Cinnamon. 3: Boot into the installed system. 4: Log in. 5: Shut down. Expected result: You should see a Plymouth screen in steps 1, 3, and 5. Actual result: A Plymouth screen can be seen in step 1, but it is not seen in steps 3 and 5 - you see terminal output (mostly from systemd) similar to Ubuntu Server. ** Affects: ubuntucinnamon-meta (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/2060905 Title: Plymouth screen does not appear during startup and shutdown of an installed system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntucinnamon-meta/+bug/2060905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060905] Re: Plymouth screen does not appear during startup and shutdown of an installed system
It appears that the root cause of this is that the `quiet splash` arguments are not getting passed to the Linux kernel, as determined by looking at /etc/default/grub and /boot/grub/grub.cfg in the installed system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060905 Title: Plymouth screen does not appear during startup and shutdown of an installed system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntucinnamon-meta/+bug/2060905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu
** Also affects: ubuntu-meta (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu Noble) Milestone: None => ubuntu-24.04 ** Changed in: wslu (Ubuntu Noble) Milestone: None => ubuntu-24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060898 Title: Trying to install gimp-help-en threatens to install wslu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2060898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060898] [NEW] Trying to install gimp-help-en threatens to install wslu
Public bug reported: Filing this against ubuntu-meta since I believe this is a seed problem that potentially affects all variants of Ubuntu (flavors or otherwise). wslu is "a collection of utilities for the Windows 10 Linux Subsystem, such as for converting Linux paths to a Windows paths or creating Linux application shortcuts on the Windows 10 Desktop." Obviously this package should *never* be installed on a desktop or even on most VMs, but only within WSL instances. However... wslu provides the virtual package www-browser, as one of its features is to open links in Windows 10 using the default browser set there. This means that if a package depends or recommends www-browser, it may attempt to pull in one of several packages, wslu included. In the past, this hasn't been a problem because Firefox was present on all flavor images, and Firefox provides www-browser as well. However, now that Firefox is a Snap, it is possible for Firefox to be installed without the firefox transitional apt package being installed. (This is the case in a default installation of Kubuntu Noble Beta.) As it turns out, Kubuntu Noble Beta ships with *no* packages that provide www-browser, meaning that any package that depends on it will have to install a new browser. Due to some stroke of misfortune, apt is picking wslu out of all packages as the package for this use case. Installing gimp-help-en will also install www-browser, which results in wslu becoming installed. wslu causes quite a few problems when installed on a desktop system - among them, the syslog is spammed with errors due to the system not in fact being a WSL VM, audio breaks in weird ways, and application launchers sometimes fail. Why this happens is unclear, but the issues appear to resolve once wslu is removed from the system. It is therefore probably a good idea to avoid wslu becoming installed on accident in this way. Probably the best way to resolve this is to ensure that some package that provides www-browser is available on every Ubuntu image. This could be done via seeding or by adding a package to ubuntu-minimal. Alternatively, wslu could be set to no longer provide www-browser, though it's unclear if that would break its functionality. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Affects: wslu (Ubuntu) Importance: Undecided Status: New ** Also affects: wslu (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/2060898 Title: Trying to install gimp-help-en threatens to install wslu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2060898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060879] [NEW] pkgselect module is broken in Kubuntu and Ubuntu Unity
Public bug reported: Due to an oversight in development, Kubuntu was left without any functional configuration for the "Customize" screen of the installer (the pkgselect module), while Ubuntu Unity was left with pkgselect misconfigured. This causes all package customization features to do nothing in Kubuntu, and will likely result in similar (or worse) misbehavior in Ubuntu Unity. The fix is to copy Lubuntu's pkgselect configuration to Kubuntu and Ubuntu Unity, and then customize the "packages to purge for a minimal install" list for both. In my opinion this should be fixed prior to beta release, as the pkgselect module is *glaringly* obvious in the installers for Kubuntu and Ubuntu Unity. If it does nothing (or causes the installer to crash), the user experience will be very degraded. ** Affects: calamares-settings-ubuntu (Ubuntu) Importance: Undecided Status: New ** Description changed: Due to an oversight in development, Kubuntu was left without any functional configuration for the "Customize" screen of the installer (the pkgselect module), while Ubuntu Unity was left with pkgselect misconfigured. This causes all package customization features to do nothing in Kubuntu, and will likely result in similar (or worse) misbehavior in Ubuntu Unity. The fix is to copy Lubuntu's pkgselect configuration to Kubuntu and Ubuntu Unity, and then customize the "packages to purge for a minimal install" list for both. - In my opinion this is a beta blocker, as the pkgselect module is - *glaringly* obvious in the installers for Kubuntu and Ubuntu Unity. If - it does nothing (or causes the installer to crash), the user experience - will be very degraded. + In my opinion this should be fixed prior to beta release, as the + pkgselect module is *glaringly* obvious in the installers for Kubuntu + and Ubuntu Unity. If it does nothing (or causes the installer to crash), + the user experience will be very degraded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060879 Title: pkgselect module is broken in Kubuntu and Ubuntu Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] Re: Lubuntu OEM install doesn't work; it simply starts Lubuntu
OEM support with Calamares was added to Lubuntu Noble, so once 24.04 releases it should be usable in that way again. The way of enabling OEM mode is different than before, but it should do the same job. ** Changed in: calamares (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047295] Re: Keyboard layout is ignored
I took a swing at this a while ago. The problem is that a setxkbmap run in the installer prompt doesn't actually manage to carry over to the desktop session. The keyboard layout ends up on `us` anyway. I suspect something in both LXQt and Plasma (both of which have this issue) is resetting the keyboard layout to the one configured in the DE (which is the normal and right thing to do but quite annoying at the same time). I could be wrong about the underlying cause, but those are the symptoms. I think this will require doing something to reconfigure the target DE so *it* sets the keyboard layout right. If so, this will likely require separate solutions for Lubuntu and Kubuntu. (Ubuntu Unity doesn't have an installer prompt and so doesn't need any action here.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047295 Title: Keyboard layout is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-installer-prompt/+bug/2047295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2016912] Re: Installing with full disk encryption when using a non-English keyboard layout results in difficulties unlocking the disk
This is already fixed for all Calamares-using flavors. Switching to unencrypted /boot and doing some trickery in the Calamares configuration did the trick if I remember correctly. I simply forgot to close this bug :P ** Changed in: calamares-settings-ubuntu (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2016912 Title: Installing with full disk encryption when using a non-English keyboard layout results in difficulties unlocking the disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2016912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
We rewrote the update notifier in Qt/C++ and got rid of the aptdaemon dependency earlier in the Noble cycle, so this is now resolved in Noble. ** Changed in: lubuntu-update-notifier (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
** Also affects: open-vm-tools (Ubuntu Noble) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
I believe bwrap was ignored intentionally, as the point of the apparmor change was to prevent arbitrary apps from making unprivileged user namespaces with capabilities. Allowing Bubblewrap to do so would provide a loophole. Same reason `unshare` isn't allowed to make unprivileged namespaces with capabilities. Perhaps something about libgnome-desktop is incorrectly assuming it needs capabilities that it doesn't actually need? Or is the ability to make unprivileged user namespaces with no capabilities failing somehow? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
I might try to SRU it into Jammy eventually (perhaps after the release
of Noble), but Focal is now unsupported from the perspective of all
flavors and I don't think Ubuntu Desktop has any use for software-
properties-qt as it has software-properties-gtk (I believe). Marking
Focal as Won't Fix for this reason.
** Changed in: software-properties (Ubuntu Focal)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060091] Re: lubuntu noble daily never starts.. black screen; Lubuntu box & Connecting..
I left this as "Fix Committed" as the package that once migrated to the release pocket was removed and the package awaiting migration is still in the proposed pocket. The fix is not released yet, as it was unreleased. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060091 Title: lubuntu noble daily never starts.. black screen; Lubuntu box & Connecting.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-installer-prompt/+bug/2060091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060091] Re: lubuntu noble daily never starts.. black screen; Lubuntu box & Connecting..
This should be fixed in lubuntu-installer-prompt 24.04.4build1 once it migrates and an ISO builds against it. ** Changed in: lubuntu-installer-prompt (Ubuntu) Status: New => 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/2060091 Title: lubuntu noble daily never starts.. black screen; Lubuntu box & Connecting.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-installer-prompt/+bug/2060091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2015318] Re: in 22.04.2 on April 4 the kscreen utility stopped working and screen was stuck at 1024x768
still using the computer On Tue, Mar 5, 2024, 06:56 Scarlett Gately Moore <2015...@bugs.launchpad.net> wrote: > Please forgive the delay, I only recently started back working on > kubuntu, am I to understand enabling backports did fix the issue or is > this still an issue? Thanks > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2015318 > > Title: > in 22.04.2 on April 4 the kscreen utility stopped working and screen > was stuck at 1024x768 > > Status in kscreen package in Ubuntu: > New > > Bug description: > We have an unusuable computer after an apt upgrade > > I run kubuntu 22.04.2 > > The screen is stuck at 1024x768 and the menus and everything are close > to unusable. > > I went to the virtual console and it works fine at 1920x1080, > i ran an update again and restarted the computer > no packages updated. > > I went back and poked thru the KDE menus and tried to change the > screen resolution, but it said the kkscreen was unavailable. I > verified it is installed. > > on reddit it said to upgrade to ppa backports to fix the problem, this > has happened before > > Our computer uses an older integrated intel graphics > on an optiplex 3010 with a pentium circa windows 7. > > when the computer restarts i may be able to add details but this is a > very severe problem the computer is unusable > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/kscreen/+bug/2015318/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015318 Title: in 22.04.2 on April 4 the kscreen utility stopped working and screen was stuck at 1024x768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kscreen/+bug/2015318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051343] Re: unity: FTBFS in Noble
** Changed in: unity-scope-home (Ubuntu) Status: New => In Progress ** Changed in: unity-lens-music (Ubuntu) Status: Fix Committed => In Progress ** Changed in: unity-lens-files (Ubuntu) Status: Fix Committed => In Progress ** Changed in: unity-lens-applications (Ubuntu) Status: Fix Committed => In Progress ** Changed in: unity (Ubuntu) Status: New => 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/2051343 Title: unity: FTBFS in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/2051343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051343] Re: unity: FTBFS in Noble
unity-lens-video is building just fine, marked as invalid. The other four are suffering from Vala incompatibilities and I'm working through them now. ** Changed in: unity-lens-applications (Ubuntu) Status: New => Fix Committed ** Changed in: unity-lens-files (Ubuntu) Status: New => Fix Committed ** Changed in: unity-lens-music (Ubuntu) Status: New => Fix Committed ** Changed in: unity-lens-video (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051343 Title: unity: FTBFS in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/2051343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059365] [NEW] r-cran-datawizard 0.9.1+dfsg-1 crashes during noble autopkgtest on s390x
Public bug reported:
Relevant logs section:
434s autopkgtest [23:22:09]: test run-unit-test: [---
434s BEGIN TEST testthat.R
434s
434s R version 4.3.3 (2024-02-29) -- "Angel Food Cake"
434s Copyright (C) 2024 The R Foundation for Statistical Computing
434s Platform: s390x-ibm-linux-gnu (64-bit)
434s
434s R is free software and comes with ABSOLUTELY NO WARRANTY.
434s You are welcome to redistribute it under certain conditions.
434s Type 'license()' or 'licence()' for distribution details.
434s
434s R is a collaborative project with many contributors.
434s Type 'contributors()' for more information and
434s 'citation()' on how to cite R or R packages in publications.
434s
434s Type 'demo()' for some demos, 'help()' for on-line help, or
434s 'help.start()' for an HTML browser interface to help.
434s Type 'q()' to quit R.
434s
434s > library(testthat)
435s > library(datawizard)
435s >
435s > test_check("datawizard")
435s Starting 2 test processes
497s
497s
497s Error in `private$handle_error()`:
497s ! testthat subprocess exited in file `test-data_tabulate.R`
497s Caused by error:
497s ! R session closed the process connection, killed
497s Backtrace:
497s ▆
497s 1. └─testthat::test_check("datawizard")
497s 2. └─testthat::test_dir(...)
497s 3. └─testthat:::test_files(...)
497s 4. └─testthat:::test_files_parallel(...)
497s 5. ├─withr::with_dir(...)
497s 6. │ └─base::force(code)
497s 7. ├─testthat::with_reporter(...)
497s 8. │ └─base::tryCatch(...)
497s 9. │ └─base (local) tryCatchList(expr, classes, parentenv,
handlers)
497s 10. │ └─base (local) tryCatchOne(expr, names, parentenv,
handlers[[1L]])
497s 11. │ └─base (local) doTryCatch(return(expr), name,
parentenv, handler)
497s 12. └─testthat:::parallel_event_loop_chunky(queue, reporters, ".")
497s 13. └─queue$poll(Inf)
497s 14. └─base::lapply(...)
497s 15. └─testthat (local) FUN(X[[i]], ...)
497s 16. └─private$handle_error(msg, i)
497s 17. └─rlang::abort(...)
497s Execution halted
497s autopkgtest [23:23:12]: test run-unit-test: ---]
498s autopkgtest [23:23:13]: test run-unit-test: - - - - - - - - - - results -
- - - - - - - - -
498s run-unit-testFAIL non-zero exit status 1
** Affects: r-cran-datawizard (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- r-cran-datawizard crashes during autopkgtest on s390x
+ r-cran-datawizard 0.9.1+dfsg-1 crashes during noble autopkgtest on s390x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059365
Title:
r-cran-datawizard 0.9.1+dfsg-1 crashes during noble autopkgtest on
s390x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/r-cran-datawizard/+bug/2059365/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055799] Re: FFe: Switch Ubuntu Unity to using Calamares
ubuntu-unity-installer-prompt ended up being unnecessary (and prohibitively difficult to implement), so this has been dropped from the list of things that this FFe involves. ** Description changed: Filing this under calamares-settings-ubuntu as this is where the majority of the code will be. Ubuntu Unity intends on moving away from the Ubiquity installer this cycle. As discussed with team lead Rudra Saraswat on Matrix, the goal is to move to the Calamares installer currently used by Lubuntu and Kubuntu. (The Ubuntu Desktop Installer was considered but does not appear to be Ubuntu Unity's intended installer at the moment.) I believe this is relatively safe change to make, as I did the majority of the work to port Calamares to Kubuntu, and it was able to be ported to using Calamares in a couple of days. The remaining work was mainly due to development of brand new features (almost all of which will simply be ported to Ubuntu Unity rather than being created from scratch). Furthermore, a thorough testing checklist exists for flavors that use Calamares, helping to catch both flavor-specific and Ubuntu- wide bugs in Calamares. This checklist is used regularly by Lubuntu for every release, and would easily be applicable to Ubuntu Unity as well. Upon completion, all existing Ubuntu Calamares features will be enabled for Ubuntu Unity, including OEM installation mode, a try or install screen with network and localization selection menus, and full disk encryption with unencrypted /boot. This will require the following packages to be modified: * calamares-settings-ubuntu: Add config for Ubuntu Unity - * ubuntu-unity-installer-prompt (which will be a NEW package): Port installer prompt screen to Ubuntu Unity * casper: Automatically log into an ubuntu-unity-live-environment X session to start the installer prompt screen, provide the installation icon on Ubuntu Unity's desktop * debian-cd: Remove Ubiquity preseed, adjust GRUB menu entries to only provide a "Try or Install Ubuntu Unity" entry, as the OEM installation mode will be triggered from within the live environment rather than from the GRUB menu + + REMOVED: + + * ubuntu-unity-installer-prompt (which will be a NEW package): Port + installer prompt screen to Ubuntu Unity ** Description changed: Filing this under calamares-settings-ubuntu as this is where the majority of the code will be. Ubuntu Unity intends on moving away from the Ubiquity installer this cycle. As discussed with team lead Rudra Saraswat on Matrix, the goal is to move to the Calamares installer currently used by Lubuntu and Kubuntu. (The Ubuntu Desktop Installer was considered but does not appear to be Ubuntu Unity's intended installer at the moment.) I believe this is relatively safe change to make, as I did the majority of the work to port Calamares to Kubuntu, and it was able to be ported to using Calamares in a couple of days. The remaining work was mainly due to development of brand new features (almost all of which will simply be ported to Ubuntu Unity rather than being created from scratch). Furthermore, a thorough testing checklist exists for flavors that use Calamares, helping to catch both flavor-specific and Ubuntu- wide bugs in Calamares. This checklist is used regularly by Lubuntu for every release, and would easily be applicable to Ubuntu Unity as well. Upon completion, all existing Ubuntu Calamares features will be enabled for Ubuntu Unity, including OEM installation mode, a try or install screen with network and localization selection menus, and full disk encryption with unencrypted /boot. This will require the following packages to be modified: * calamares-settings-ubuntu: Add config for Ubuntu Unity * casper: Automatically log into an ubuntu-unity-live-environment X session to start the installer prompt screen, provide the installation icon on Ubuntu Unity's desktop * debian-cd: Remove Ubiquity preseed, adjust GRUB menu entries to only provide a "Try or Install Ubuntu Unity" entry, as the OEM installation mode will be triggered from within the live environment rather than from the GRUB menu - REMOVED: + NO LONGER APPLICABLE: * ubuntu-unity-installer-prompt (which will be a NEW package): Port installer prompt screen to Ubuntu Unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055799 Title: FFe: Switch Ubuntu Unity to using Calamares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2055799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054795] Re: Calamares - Installation failed - Bad main script file
** Changed in: calamares (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054795 Title: Calamares - Installation failed - Bad main script file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2054795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049280] Re: udisks2 core dump
Hi!! I present a similar issue Here my data. Hope can help me. $ sudo systemctl status udisks2 × udisks2.service - Disk Manager Loaded: loaded (/lib/systemd/system/udisks2.service; enabled; preset: enabled) Active: failed (Result: core-dump) since Sun 2024-03-24 03:23:50 CST; 19min ago Docs: man:udisks(8) Process: 2615 ExecStart=/usr/libexec/udisks2/udisksd (code=dumped, signal=TRAP) Main PID: 2615 (code=dumped, signal=TRAP) CPU: 11ms mar 24 03:23:50 OldMachine systemd[1]: Starting udisks2.service - Disk Manager... mar 24 03:23:50 OldMachine udisksd[2615]: udisks daemon version 2.10.1 starting mar 24 03:23:50 OldMachine udisksd[2615]: failed to load module swap: /lib/x86_64-linux-gnu/libbd_swap.so.3: invalid ELF header mar 24 03:23:50 OldMachine udisksd[2615]: Failed to load the 'swap' libblockdev plugin mar 24 03:23:50 OldMachine systemd[1]: udisks2.service: Main process exited, code=dumped, status=5/TRAP mar 24 03:23:50 OldMachine systemd[1]: udisks2.service: Failed with result 'core-dump'. mar 24 03:23:50 OldMachine systemd[1]: Failed to start udisks2.service - Disk Manager. $ sudo apt search udisks2|grep -i install WARNING: apt does not have a stable CLI interface. Use with caution in scripts. $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ uname -a Linux OldMachine 6.5.0-26-generic #26-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 5 21:19:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ swapon -s FilenameTypeSizeUsed Priority /swapfile file2097148 0 -2 $ apt search udisks2|grep -i install WARNING: apt does not have a stable CLI interface. Use with caution in scripts. $ sudo lshw -c storage *-nvme descripción: NVMe device producto: SKHynix_HFS512GD9TNI-L2B0B fabricante: SK hynix id físico: 0 información del bus: pci@:55:00.0 nombre lógico: /dev/nvme0 versión: 11720C10 serie: CJA4N765010304Q5N anchura: 64 bits reloj: 33MHz capacidades: nvme pm msi msix pciexpress nvm_express bus_master cap_list configuración: driver=nvme latency=0 nqn=nqn.2014.08.org.nvmexpress:1c5c1c5cCJA4N765010304Q5N SKHynix_HFS512GD9TNI-L2B0B state=live recursos: irq:16 memoria:ae00-ae003fff memoria:ae005000-ae005fff memoria:ae004000-ae004fff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049280 Title: udisks2 core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2049280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892558] Re: binhex always segfaults
** Also affects: macutils (Ubuntu Focal) 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/1892558 Title: binhex always segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/macutils/+bug/1892558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056696] Re: All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors
I assume you didn't install Kubuntu Noble on a VM due to a Calamares bug who's fix isn't managing to migrate out of -proposed. There's a fairly easy workaround for that issue (`vim /lib/x86_64-linux- gnu/calamares/modules/networkcfg/main.py`, search for "0o" via `/0o` and then change the `f` to `f.fileno()`, save and quit with `:wq` and then everything works), so you might try that. (It might also work to just install Calamares from noble-proposed while on the live ISO, then install.) You can probably compare your list of installed packages with the list of packages in the latest Kubuntu Noble ISO's manifest (https://cdimage.ubuntu.com/kubuntu/daily-live/pending/noble-desktop- amd64.manifest) to see what you're missing, but if you have an additional DE installed alongside, a component of it could be interfering with reproducing the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056696 Title: All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2056696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970521] Re: boinc-client crashes when started with core dump on Xubuntu 22.04
** Also affects: boinc (Ubuntu Jammy) 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/1970521 Title: boinc-client crashes when started with core dump on Xubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1970521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056061] Re: FFe: Calamares customize menu
Hey Łukasz! The feature Scarlett is referring to here (pkgselect) is actually already in the archive. It is currently only enabled in Lubuntu though, and due to some UI and architectural bugs, it is going to be rewritten and moved to the Calamares package rather than being in calamares- settings-ubuntu where it is now. All of this is bugfix-only work and can be done regardless of whether this FFe is approved. The pkgselect module provides the ability for users to customize what packages are installed on their system during OS installation. Some of the ways this customization is provided to the user is via a full/default/minimal install option, and the ability to pick recommended applications such as Element to be installed at OS install time. Scarlett is simply asking for permission to turn on the pkgselect module once it is in a functional and good-looking state. It will be a feature addition to Kubuntu, but only because it will require changing some config files to enable it. The actual change that needs FFe approved is a trivial config file patch to calamares-settings-ubuntu as follows: --- kubuntu/settings.conf.old 2024-03-13 13:42:51.588625334 -0500 +++ kubuntu/settings.conf 2024-03-13 13:43:12.812953441 -0500 @@ -20,6 +20,12 @@ - id: add386arch module: shellprocess config: shellprocess_add386arch.conf +- id: pkgselect_action + module: contextualprocess + config: pkgselect_context.conf +- id: pkgselect_snap_action + module: contextualprocess + config: pkgselect_snap_context.conf - id: oemprep module: shellprocess config: shellprocess_oemprep.conf @@ -29,6 +35,7 @@ - welcome - locale - keyboard + - pkgselect - partition - users - summary @@ -57,6 +64,8 @@ - automirror - shellprocess@add386arch - packages + - contextualprocess@pkgselect_action + - contextualprocess@pkgselect_snap_action - shellprocess@logs - umount - show: This config is already shipping in Lubuntu and builds, installs, and (when needed) upgrades properly. You can look at the build logs of the latest upload of calamares-settings-ubuntu as a test package to see that this config builds properly. Also, I see this FFe appears to have been filed against the wrong package. I'll change it while I'm right here. Thanks for your help! ** Also affects: calamares-settings-ubuntu (Ubuntu) Importance: Undecided Status: New ** No longer affects: calamares (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056061 Title: FFe: Calamares customize menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2056061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055893] Re: Lubuntu-installer-prompt fails to pass selected language to calamares
Nevermind, I didn't read thoroughly. I'll try on my end and see what happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055893 Title: Lubuntu-installer-prompt fails to pass selected language to calamares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-installer-prompt/+bug/2055893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055893] Re: Lubuntu-installer-prompt fails to pass selected language to calamares
What language were you trying? Calamares might just not have supported it. I tried this yesterday or the day before (if I remember correctly) and the language got through to Calamares just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055893 Title: Lubuntu-installer-prompt fails to pass selected language to calamares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-installer-prompt/+bug/2055893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969984] Re: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen
nevermind, it looks like this is a new bug. I'll file one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969984 Title: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1969984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969984] Re: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen
Somehow this got dropped or the fix is obsolete, since this has resurfaced in Noble. ** Also affects: kubuntu-settings (Ubuntu Noble) Importance: Medium Assignee: Erich Eickmeyer (eeickmeyer) Status: Fix Released ** Changed in: kubuntu-settings (Ubuntu Noble) Status: Fix Released => Confirmed ** Changed in: kubuntu-settings (Ubuntu Noble) Importance: Medium => High ** Changed in: kubuntu-settings (Ubuntu Noble) Assignee: Erich Eickmeyer (eeickmeyer) => Aaron Rainbolt (arraybolt3) ** No longer affects: kubuntu-settings (Ubuntu Noble) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969984 Title: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1969984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054795] Re: Calamares - Installation failed - Bad main script file
For the record, the fix for this bug is uploaded (I believe), but it's stuck in the -proposed pocket because of a giant change happening at the same time (the time_t64 transition for avoiding the Year 2038 problem). It may be a bit before we see ISOs with the fix on it. ** Changed in: calamares (Ubuntu) Status: Confirmed => 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/2054795 Title: Calamares - Installation failed - Bad main script file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2054795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056696] Re: All Snaps are denied the ability to use DBus for notifications and apptray indicators in Kubuntu
** Summary changed: - All Snaps are denied the ability to use DBus for notifications and apptray indicators + All Snaps are denied the ability to use DBus for notifications and apptray indicators in Kubuntu ** Summary changed: - All Snaps are denied the ability to use DBus for notifications and apptray indicators in Kubuntu + All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056696 Title: All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2056696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056605] Re: HWE 6.5.0-25-generic kernel does not boot due to VirtualBox
I am unable to reproduce this with Ubuntu Desktop 22.04.4 (all updates installed), VirtualBox 6.1.50 (from Ubuntu repos), VBox Extension Pack installed, with kernel 6.5.0-25-generic running. Using a Dell Optiplex 9020 with 32 GB RAM, an Intel Core i5-4570, and an NVIDIA 1050 Ti GPU with Nouveau graphics. System boots into the latest HWE kernel without issues, and I can boot a Tiny Core Linux VM just fine. I even enabled the xHCI controller from the extension pack to see if that would change things and it did not - both the system and the VM boot after making that change. (I'm using a TeamGroup SATA SSD too, though I doubt that matters - also as a passing note I've not had the best experience with TeamGroup's flash storage.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056605 Title: HWE 6.5.0-25-generic kernel does not boot due to VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2056605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056603] [NEW] FFe: Open WiFi network support
Public bug reported: As it stands, the network connectivity features of lubuntu-installer- prompt and kubuntu-installer-prompt are only capable of connecting to WiFi networks that have a password. This is non-ideal, as some users may want to connect to the Internet during installation via public WiFi. The code to enable this should be relatively simple (detect if the WiFi network requires authentication when trying to connect, and skip password-related code if not), and as kubuntu-installer-prompt shares a massive amount of code with lubuntu-installer-prompt it will be easy to port once finished. This FFe applies to both lubuntu-installer-prompt and kubuntu-installer- prompt. ** Affects: kubuntu-installer-prompt (Ubuntu) Importance: Undecided Assignee: Aaron Rainbolt (arraybolt3) Status: New ** Affects: lubuntu-installer-prompt (Ubuntu) Importance: Undecided Assignee: Aaron Rainbolt (arraybolt3) Status: New ** Also affects: kubuntu-installer-prompt (Ubuntu) Importance: Undecided Status: New ** Changed in: kubuntu-installer-prompt (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) ** Changed in: lubuntu-installer-prompt (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056603 Title: FFe: Open WiFi network support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-installer-prompt/+bug/2056603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056379] [NEW] Lubuntu Update notifications show up in the wrong spot and are incorrectly themed
Public bug reported: OS: Lubuntu Noble Development Edition. Hardware: virt-manager VM. Steps to reproduce: 1: Boot a Lubuntu Noble VM that hasn't been updated in a while (there needs to be updates available to trigger the bug). 2: Open Lubuntu Update. 3: Click "Check for Updates". 4: Provide your password. Expected result: Updates should appear in the window, and a notification should be shown in the upper-right corner with white text on a greyish background. Actual result: Updates do indeed appear in the window, but the notification is shown in the upper-left corner with black text on a yellow background shaped like a speech bubble. Additional info: This appears to be a race condition - Lubuntu Update is probably starting before lxqt-notificationd fully starts, and Qt is falling back to some sort of "default" notification display mechanism as a result. One can kill lxqt-notificationd and still get notifications from Lubuntu Update (incorrectly positioned and themed). Unless LXQt provides a way to require one service to fully start before another, this will probably be easiest to work around by adding a check in the code that waits for lxqt-notificationd to be available before actually starting the app (and times out if it doesn't show up for a long time, 30 seconds or so). ** Affects: lubuntu-update-notifier (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/2056379 Title: Lubuntu Update notifications show up in the wrong spot and are incorrectly themed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-update-notifier/+bug/2056379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056375] [NEW] Ubuntu Studio ISO fails to build: "/usr/sbin/grub-probe: error: failed to get canonical path of `overlay'."
Public bug reported: Full build log is at https://launchpadlibrarian.net/717896339/buildlog_ubuntu_noble_amd64_ubuntustudio_BUILDING.txt.gz. Relevant section: Preconfiguring packages ... Fetched 692 MB in 4s (169 MB/s) (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 347331 files and directories currently installed.) Removing os-prober (1.81ubuntu3) ... Removing memtest86+ (7.00-1) ... Removing ubuntustudio-lowlatency-settings (24.04.14) ... Removing plymouth-theme-ubuntustudio (24.04.1) ... update-alternatives: removing manually selected alternative - switching default.plymouth to auto mode update-alternatives: using /usr/share/plymouth/themes/bgrt/bgrt.plymouth to provide /usr/share/plymouth/themes/default.plymouth (default.plymouth) in auto mode update-alternatives: using /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth to provide /usr/share/plymouth/themes/text.plymouth (text.plymouth) in auto mode update-initramfs: deferring update (trigger activated) /usr/sbin/grub-probe: error: failed to get canonical path of `overlay'. dpkg: error processing package plymouth-theme-ubuntustudio (--remove): installed plymouth-theme-ubuntustudio package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: plymouth-theme-ubuntustudio Processing was halted because there were too many errors. ** Affects: grub2 (Ubuntu) Importance: Critical Status: New ** Tags: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056375 Title: Ubuntu Studio ISO fails to build: "/usr/sbin/grub-probe: error: failed to get canonical path of `overlay'." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2056375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055799] Re: FFe: Switch Ubuntu Unity to using Calamares
** Description changed: Filing this under calamares-settings-ubuntu as this is where the majority of the code will be. Ubuntu Unity intends on moving away from the Ubiquity installer this cycle. As discussed with team lead Rudra Saraswat on Matrix, the goal is to move to the Calamares installer currently used by Lubuntu and Kubuntu. (The Ubuntu Desktop Installer was considered but does not appear to be Ubuntu Unity's intended installer at the moment.) - It is the belief of the Lubuntu team (who are the primary maintainers of - the Calmares package in Ubuntu at the moment) that this is a relatively - safe change to make, as Kubuntu was able to be ported to using Calamares - in a couple of days, and the remaining work was mainly due to - development of brand new features (almost all of which will simply be - ported to Ubuntu Unity rather than being created from scratch). - Furthermore, Lubuntu has a thorough testing checklist for flavors that - use Calamares, helping to catch both flavor-specific and Ubuntu-wide - bugs in Calamares. + I believe this is relatively safe change to make, as I did the majority + of the work to port Calamares to Kubuntu, and it was able to be ported + to using Calamares in a couple of days. The remaining work was mainly + due to development of brand new features (almost all of which will + simply be ported to Ubuntu Unity rather than being created from + scratch). Furthermore, a thorough testing checklist exists for flavors + that use Calamares, helping to catch both flavor-specific and Ubuntu- + wide bugs in Calamares. This checklist is used regularly by Lubuntu for + every release, and would easily be applicable to Ubuntu Unity as well. Upon completion, all existing Ubuntu Calamares features will be enabled for Ubuntu Unity, including OEM installation mode, a try or install screen with network and localization selection menus, and full disk encryption with unencrypted /boot. This will require the following packages to be modified: * calamares-settings-ubuntu: Add config for Ubuntu Unity * ubuntu-unity-installer-prompt (which will be a NEW package): Port installer prompt screen to Ubuntu Unity * casper: Automatically log into an ubuntu-unity-live-environment X session to start the installer prompt screen, provide the installation icon on Ubuntu Unity's desktop * debian-cd: Remove Ubiquity preseed, adjust GRUB menu entries to only provide a "Try or Install Ubuntu Unity" entry, as the OEM installation mode will be triggered from within the live environment rather than from the GRUB menu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055799 Title: FFe: Switch Ubuntu Unity to using Calamares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2055799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055799] Re: FFe: Switch Ubuntu Unity to using Calamares
** Description changed: Filing this under calamares-settings-ubuntu as this is where the majority of the code will be. Ubuntu Unity intends on moving away from the Ubiquity installer this cycle. As discussed with team lead Rudra Saraswat on Matrix, the goal is to move to the Calamares installer currently used by Lubuntu and Kubuntu. (The Ubuntu Desktop Installer was considered but does not appear to be Ubuntu Unity's intended installer at the moment.) - It is the belief of the Ubuntu Calamares maintainers (the Lubuntu team) - that this is a relatively safe change to make, as Kubuntu was able to be - ported to using Calamares in a couple of days, and the remaining work - was mainly due to development of brand new features (almost all of which - will simply be ported to Ubuntu Unity rather than being created from - scratch). Furthermore, Lubuntu has a thorough testing checklist for - flavors that use Calamares, helping to catch both flavor-specific and - Ubuntu-wide bugs in Calamares. + It is the belief of the Lubuntu team (who are the primary maintainers of + Calamares at the moment) that this is a relatively safe change to make, + as Kubuntu was able to be ported to using Calamares in a couple of days, + and the remaining work was mainly due to development of brand new + features (almost all of which will simply be ported to Ubuntu Unity + rather than being created from scratch). Furthermore, Lubuntu has a + thorough testing checklist for flavors that use Calamares, helping to + catch both flavor-specific and Ubuntu-wide bugs in Calamares. Upon completion, all existing Ubuntu Calamares features will be enabled for Ubuntu Unity, including OEM installation mode, a try or install screen with network and localization selection menus, and full disk encryption with unencrypted /boot. This will require the following packages to be modified: * calamares-settings-ubuntu: Add config for Ubuntu Unity * ubuntu-unity-installer-prompt (which will be a NEW package): Port installer prompt screen to Ubuntu Unity * casper: Automatically log into an ubuntu-unity-live-environment X session to start the installer prompt screen, provide the installation icon on Ubuntu Unity's desktop * debian-cd: Remove Ubiquity preseed, adjust GRUB menu entries to only provide a "Try or Install Ubuntu Unity" entry, as the OEM installation mode will be triggered from within the live environment rather than from the GRUB menu ** Description changed: Filing this under calamares-settings-ubuntu as this is where the majority of the code will be. Ubuntu Unity intends on moving away from the Ubiquity installer this cycle. As discussed with team lead Rudra Saraswat on Matrix, the goal is to move to the Calamares installer currently used by Lubuntu and Kubuntu. (The Ubuntu Desktop Installer was considered but does not appear to be Ubuntu Unity's intended installer at the moment.) It is the belief of the Lubuntu team (who are the primary maintainers of - Calamares at the moment) that this is a relatively safe change to make, - as Kubuntu was able to be ported to using Calamares in a couple of days, - and the remaining work was mainly due to development of brand new - features (almost all of which will simply be ported to Ubuntu Unity - rather than being created from scratch). Furthermore, Lubuntu has a - thorough testing checklist for flavors that use Calamares, helping to - catch both flavor-specific and Ubuntu-wide bugs in Calamares. + the Calmares package in Ubuntu at the moment) that this is a relatively + safe change to make, as Kubuntu was able to be ported to using Calamares + in a couple of days, and the remaining work was mainly due to + development of brand new features (almost all of which will simply be + ported to Ubuntu Unity rather than being created from scratch). + Furthermore, Lubuntu has a thorough testing checklist for flavors that + use Calamares, helping to catch both flavor-specific and Ubuntu-wide + bugs in Calamares. Upon completion, all existing Ubuntu Calamares features will be enabled for Ubuntu Unity, including OEM installation mode, a try or install screen with network and localization selection menus, and full disk encryption with unencrypted /boot. This will require the following packages to be modified: * calamares-settings-ubuntu: Add config for Ubuntu Unity * ubuntu-unity-installer-prompt (which will be a NEW package): Port installer prompt screen to Ubuntu Unity * casper: Automatically log into an ubuntu-unity-live-environment X session to start the installer prompt screen, provide the installation icon on Ubuntu Unity's desktop * debian-cd: Remove Ubiquity preseed, adjust GRUB menu entries to only provide a "Try or Install Ubuntu Unity" entry, as the OEM installation mode will be triggered from within the live environment rather than from the GRUB menu -- You received this bug notification because you are a
[Bug 2055799] [NEW] FFe: Switch Ubuntu Unity to using Calamares
Public bug reported: Filing this under calamares-settings-ubuntu as this is where the majority of the code will be. Ubuntu Unity intends on moving away from the Ubiquity installer this cycle. As discussed with team lead Rudra Saraswat on Matrix, the goal is to move to the Calamares installer currently used by Lubuntu and Kubuntu. (The Ubuntu Desktop Installer was considered but does not appear to be Ubuntu Unity's intended installer at the moment.) It is the belief of the Ubuntu Calamares maintainers (the Lubuntu team) that this is a relatively safe change to make, as Kubuntu was able to be ported to using Calamares in a couple of days, and the remaining work was mainly due to development of brand new features (almost all of which will simply be ported to Ubuntu Unity rather than being created from scratch). Furthermore, Lubuntu has a thorough testing checklist for flavors that use Calamares, helping to catch both flavor-specific and Ubuntu-wide bugs in Calamares. Upon completion, all existing Ubuntu Calamares features will be enabled for Ubuntu Unity, including OEM installation mode, a try or install screen with network and localization selection menus, and full disk encryption with unencrypted /boot. This will require the following packages to be modified: * calamares-settings-ubuntu: Add config for Ubuntu Unity * ubuntu-unity-installer-prompt (which will be a NEW package): Port installer prompt screen to Ubuntu Unity * casper: Automatically log into an ubuntu-unity-live-environment X session to start the installer prompt screen, provide the installation icon on Ubuntu Unity's desktop * debian-cd: Remove Ubiquity preseed, adjust GRUB menu entries to only provide a "Try or Install Ubuntu Unity" entry, as the OEM installation mode will be triggered from within the live environment rather than from the GRUB menu ** Affects: calamares-settings-ubuntu (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/2055799 Title: FFe: Switch Ubuntu Unity to using Calamares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2055799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055726] [NEW] If Kubuntu installation fails, Plasma crashes when attempting to launch once Calamares quits
Public bug reported: OS: Kubuntu Noble. Hardware: Raw QEMU VM. Attempt to install Kubuntu using Calamares. It will fail due to https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2054795. After installation failure however, Plasma will attempt to launch, and then crash, possibly multiple times. This is because Calamares is causing /home/kubuntu/.cache to be owned by root. This trips up Plasma and causes it to crash. The solution is to `chown -R 1000:1000 /home/kubuntu/.cache` immediately after kubuntu-installer-prompt exits in /usr/libexec/start-kubuntu-live- env. This fixes the ownership of the directory before Plasma starts. I've tested this in a VM and it works. ** Affects: calamares (Ubuntu) Importance: Critical Assignee: Aaron Rainbolt (arraybolt3) Status: Triaged ** Changed in: calamares (Ubuntu) Status: New => Confirmed ** Changed in: calamares (Ubuntu) Status: Confirmed => Triaged ** Changed in: calamares (Ubuntu) Importance: Undecided => Critical ** Changed in: calamares (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055726 Title: If Kubuntu installation fails, Plasma crashes when attempting to launch once Calamares quits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2055726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975393] Re: Calamares - unable to select option "Next" after selecting "No Swap"
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/249365/testcases/1701/results After updating the latest Lubuntu Kinetic ISO with Proposed (which pulled in calamares 3.2.59-0ubuntu1), this bug no longer appears - selecting "No Swap" does not gray-out the Next button. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975393 Title: Calamares - unable to select option "Next" after selecting "No Swap" To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1975393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945371] Re: QtPass never finishes generating GnuPG key pair
Successfully reproduced bug on latest Lubuntu Kinetic daily ISO. The workaround by @rinni worked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945371 Title: QtPass never finishes generating GnuPG key pair To manage notifications about this bug go to: https://bugs.launchpad.net/qtpass-backports/+bug/1945371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
I don't believe that my system ever was able to wake from the touchpad - I seem to remember having to use the power button or open the lid in the past. I thought maybe I just had something misconfigured back then, but maybe not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
I installed the same kernel that is in 20.04 onto a Lubuntu Kinetic (22.10 alpha) installation, and the touchpad wake didn't work on my laptop. I then tried USB wake on the kernel that's part of Kinetic, and USB wake did work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input
Sadly, I have to correct myself - I thought I had replicated the issue, but it turns out my particular laptop doesn't use USB to attach the mousepad. I tried plugging a USB mouse into my system while running a "bad" kernel, and it was able to wake from suspend when I moved the mouse. Also, it appears my system is using s2idle. So sadly, I cannot reproduce the bug on my hardware after all. What I can do is leave a hint for the next person who goes to bisect the kernel. Due to a change in initrd compression, if you try to install a kernel that's too old onto Ubuntu Jammy or Kinetic, it won't be able to boot since it won't be able to mount the initrd image. To fix this, do "sudo nano /etc/initramfs-tools/initramfs.conf", and change the "COMPRESS" option to "gzip" (it will probably be set to "zstd" by default). That should get your older kernels booting, so you can actually have a fighting chance at bisecting the kernel. Sorry I couldn't do it myself on my hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971933 Title: [Regression] Unable to wake laptop using trackpad input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
