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 (
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
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2111551
Title:
fwupd cr
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
** Tags added: dcr-freezer
--
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/2111551
Title:
fwupd crash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
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
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2111551
Title:
