[Bug 2111551] Re: fwupd crash with "Creating pipes for GWakeup: Too many open files"

2025-06-09 Thread Daniel van Vugt
** Changed in: fwupd (Ubuntu Questing) Importance: Low => Medium ** Changed in: fwupd (Ubuntu Plucky) Importance: Undecided => Medium ** Changed in: fwupd (Ubuntu Plucky) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, whi

[Bug 2111551] Re: fwupd crash with "Creating pipes for GWakeup: Too many open files"

2025-06-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fwupd (Ubuntu Plucky) 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/2111551 Title:

[Bug 2111551] Re: fwupd crash with "Creating pipes for GWakeup: Too many open files"

2025-06-09 Thread Daniel van Vugt
** Also affects: fwupd (Ubuntu Questing) Importance: Low Status: Triaged ** Also affects: fwupd (Ubuntu Plucky) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Plucky) Milestone: None => plucky-updates -- You received this bug notification because you are

[Bug 2111551] Re: fwupd crash with "Creating pipes for GWakeup: Too many open files"

2025-06-09 Thread Bug Watch Updater
** Changed in: fwupd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111551 Title: fwupd crash with "Creating pipes for GWakeup: Too many open files" To manage

[Bug 2111551] Re: fwupd crash with "Creating pipes for GWakeup: Too many open files"

2025-06-08 Thread Daniel van Vugt
** Bug watch added: github.com/fwupd/fwupd/issues #8712 https://github.com/fwupd/fwupd/issues/8712 ** Also affects: fwupd via https://github.com/fwupd/fwupd/issues/8712 Importance: Unknown Status: Unknown ** Changed in: fwupd (Ubuntu) Milestone: None => ubuntu-25.10 ** Tags a

[Bug 2111551] Re: fwupd crash

2025-06-06 Thread Mario Limonciello
The "fwupd fix" is https://github.com/fwupd/fwupd/commit/53bd09f66508050ea1d958a09c3db1b4dd4c6778. It will be fixed when upgrading to 2.0.10, as explained in bug 2112372. ** Summary changed: - fwupd crash + fwupd crash with "Creating pipes for GWakeup: Too many open files" ** Changed in: fwupd (

[Bug 2111551] Re: fwupd crash

2025-06-06 Thread Sebastien Bacher
Agreed with Daniel, it is not a glib issue ** Changed in: glib2.0 (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111551 Title: fwupd crash To manage noti

[Bug 2111551] Re: fwupd crash

2025-06-05 Thread Daniel van Vugt
Sounds like bug 2093824, but you already have that fix. I don't think it makes sense to blame glib when it's just reporting a descriptor leak. Such a leak is more likely to be the app's fault. ** Also affects: fwupd (Ubuntu) Importance: Undecided Status: New -- You received this bug n

[Bug 2111551] Re: fwupd crash

2025-06-05 Thread Simon Poirier
** Tags added: dcr-freezer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111551 Title: fwupd crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+

[Bug 2111551] Re: fwupd crash

2025-06-05 Thread Mario Limonciello
It looks like the crash itself is in glib, I'll reassign there. ** Package changed: fwupd (Ubuntu) => glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111551 Title: fwupd crash To m

[Bug 2111551] Re: fwupd crash

2025-06-04 Thread Laurent Bonnaud
Bug #2111551 is for the root cause of the problem. Bug #2112372 is for an easy workaround. Therefore, each one has its own purpose. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111551 Title: fwup

[Bug 2111551] Re: fwupd crash

2025-06-03 Thread Mario Limonciello
I'm tempted to mark this as a duplicate of https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2112372 as they're both boiling down to the same suspected root cause. ** Changed in: fwupd (Ubuntu) Status: New => Triaged ** Changed in: fwupd (Ubuntu) Importance: Undecided => Wishlist --

[Bug 2111551] Re: fwupd crash

2025-05-23 Thread Laurent Bonnaud
And yet more info: StacktraceAddressSignature: /usr/libexec/fwupd/fwupd:5:/usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.8400.1+55123:/usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.8400.1+b266a:/usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.8400.1+431e0:/usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.8400.1+43

[Bug 2111551] Re: fwupd crash

2025-05-23 Thread Laurent Bonnaud
And yet more info: StacktraceAddressSignature: /usr/libexec/fwupd/fwupd:5:/usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.8400.1+55123:/usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.8400.1+b266a:/usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.8400.1+431e0:/usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.8400.1+43

[Bug 2111551] Re: fwupd crash

2025-05-23 Thread Laurent Bonnaud
Here is a stacktrace I extracted from /var/crash/ : Stacktrace: #0 _g_log_abort (breakpoint=) at ../../../glib/gmessages.c:431 debugger_present = 1 debugger_present = #1 g_logv (log_domain=0x797c3b6746de "GLib", log_level=G_LOG_LEVEL_ERROR, format=, args=) at ../../../glib/

[Bug 2111551] Re: fwupd crash

2025-05-23 Thread Laurent Bonnaud
Here is a complete log of fwupd. ** Attachment added: "fwupd-bug.txt" https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2111551/+attachment/5879887/+files/fwupd-bug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bu