[Bug 1881932] Re: subiquity isn't able to create btrfs subvolumes during installation
** Changed in: subiquity Importance: Undecided => Medium ** Changed in: curtin Status: New => Triaged ** Changed in: curtin Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1881932 Title: subiquity isn't able to create btrfs subvolumes during installation To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1881932/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881932] Re: subiquity isn't able to create btrfs subvolumes during installation
@Jonas - please don't knowingly create duplicates. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1881932 Title: subiquity isn't able to create btrfs subvolumes during installation To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1881932/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059187] [NEW] fails in autopkgtest on gnome-desktop-testing
Public bug reported: flatpak fails autopkgtest like so: 1125s Updating appstream branch 1125s Updating summary 1125s ok app with mismatched metadata (in summary) can't be installed 1125s test-metadata-validation.sh:158 - app with mismatched metadata (in summary) can't be installed 1125s OK closing connection 1125s fusermount: entry for /tmp/test-flatpak-MPRPRX/runtime/doc not found in /etc/mtab 1125s PASS: Flatpak/test-metadata-validation.sh.test 1125s SUMMARY: total=45; passed=38; skipped=0; failed=7; user=205.6s; system=150.8s; maxrss=423860 1125s FAIL: Flatpak/test-bun...@system.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/testlibrary.test (Child process killed by signal 6) 1125s FAIL: Flatpak/test-bun...@system-norevokefs.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system-norevokefs,deltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system,deltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system,nodeltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system-norevokefs,nodeltas.wrap.test (Child process exited with code 1) 1125s /tmp/autopkgtest.Kstx4F/wrapper.sh: Killing leaked background processes: 9343 1125s PID TTY STAT TIME COMMAND 1125s9343 ?S 0:00 /usr/bin/python3 /usr/libexec/installed-tests/Flatpak/web-server.py repos 1125s autopkgtest [07:37:45]: test gnome-desktop-testing: ---] 1126s autopkgtest [07:37:46]: test gnome-desktop-testing: - - - - - - - - - - results - - - - - - - - - - 1126s gnome-desktop-testing FAIL non-zero exit status 2 https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/f/flatpak/20240324_073939_33ef3@/log.gz ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/2059187 Title: fails in autopkgtest on gnome-desktop-testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2059187/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
Hi Kai-Heng, It looks like you're working on this through Salsa. The debdiffs on this bug mean that this shows in the sponsor queue, so I'm removing Ubuntu Sponsors from this bug since there looks like no action to take for Sponsors. Please re-subscribe Sponsors if you feel otherwise. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037569] Re: udev issues with mantic beta
Marking invalid in systemd, other than long-standing udev rules being involved I'm not sure this will be fixed in systemd. Exploring if libblockdev with the s390 plugin enabled helps. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Also affects: libblockdev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libblockdev in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031172] Re: Please take a stand on "screen: Use clean env when creating new tab"
> it exposes a deficiency in the desktop > environment in that the WM/shell's environment contains necessary > env vars (e.g. ssh-agent variables) that are missing from the > systemd --user / d-bus activation environment -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2031172 Title: Please take a stand on "screen: Use clean env when creating new tab" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2031172/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
Thanks, uploaded! ** Changed in: openbox (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
Thanks for the patch, Aaron. I'm able to reproduce this bug using the firefox f11 -> open link in new window, when using the live session of the daily-live lubuntu iso. And the attached patch does seem to help. Overall the patch is what I was hoping to see, but I will request some changes. * The Maintainer field currently reads "Maintainer: Lubuntu Developers". I'd like you to go with the more conventional "Ubuntu Developers" attribution. `seeded-in-ubuntu` says that openbox is also used in Ubuntu Mate, and of course people can use openbox otherwise. The `update-maintainer` script is a convenient way to set this field to the value I'm suggesting (when starting from the original value). * There is a sponsorship process listed on the wiki, I think https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue is a good summary. This can also help, in the future, find someone to take a look at the patch as doing so means your work show up in the queue. http://reports.qa.ubuntu.com/reports/sponsoring/ Since I'm already looking at this I won't demand the SponsorsQueue bug changes but please keep that in mind for the next one. * I forget where I saw it but I like the convention that the patch has a change number, like it looks like you're on v4 of the patch. So it might have been called glib_crash_bugfix-v4.patch or something. A nice convention for when these keep changing. * One item also mentioned on the wiki is forwarding this patch to Debian. It is likely that the same problem applies there. https://wiki.ubuntu.com/Debian/Bugs talks about this in detail. I will ask that you do this before upload. For this particular bug I'd feel comfortable sharing the patch with Debian without reproducing on Debian, since it's already known to be happening elsewhere. Just say so when forwarding. * A tweak to the changelog would be nice. It isn't necessary to note the update to the maintainer field, that will be the case for most if not all packages with an Ubuntu delta. Also, the first segment about the patch is in my opinion too developer focused. I'd probably start with "Cherry-pick patch from A for crash issue when B + C happens", fill in appropriate details you think might be interesting for someone who might not look at the code. So Maintainer + Debian + Changelog tweaks and I will be happy to upload. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
Partial review of the patch so far. I haven't read much openbox code so take this with a grain of salt. https://bugzilla.icculus.org/show_bug.cgi?id=6669#c9 mentions a concern that itPrev may still be pointing to invalid data. I share this concern. I think some interesting testcases are what happens with lists that have one or two elements, which then are modified by this function. In the single element case, I believe your itPrev now points to the deleted item, and in the two element case, itPrev may be ok but itPrev->prev or itPrev->next are both probably not valid. https://bugzilla.icculus.org/show_bug.cgi?id=6669#c5 mentions a work branch. I suggest tracking that down and considering it. It's presumably this patch https://bugzilla.icculus.org/attachment.cgi?id=3646&action=diff. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
Thanks for the report. > do you think this bug will be corrected soon ? or i change parent directory name of mountpoints ? Probably better off changing the parent directory name, I'm afraid. ** Changed in: glib2.0 (Ubuntu) Status: New => Triaged ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
