Tested working! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
Thanks Dimitri!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
Status in
Thanks for the confirmation @Thorsten!
Now to get some maintainer eyes on it...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs
The upstream commit to fix this issues is this one:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/advertising.c?id=1873096352f518d3247f8efb3c2e0aa8804e50ac
I've applied it to Ubuntu's bluez 5.48 and confirmed that it works, as
expected.
Please backport!
--
You received this bug
I took a crack at patching this. Works without complaints for
cryptroot-unlock as shipped with Ubuntu 18.04 Server.
Apply with:
$ cd /usr/share/cryptsetup/initramfs/bin/
$ sudo patch -bp1 < /path/to/cryptroot-unlock-neutered-busybox-progs.patch
$ sudo update-initramfs -uk all
Problems were:
1)
Public bug reported:
This is probably a long shot given the age, but any chance of getting
the following patches backported to the Trusty build from upstream?
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=d8090022f66cc6cff6af5ed2ae702212fd172ff7
TitanKing,
I'd posted a bit less intrusive workaround at
https://askubuntu.com/a/894387/653294.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1589605
Title:
Hey Brian,
I was going to let this run longer, but I think we're safe. I've
observed RSS of both xfce4-power-manager and NetworkManager grow by over
1.5MB from usage at start up and have now dropped back to more than 1MB
below usage at start up. These observations were made with swap
disabled,
I finally got around to enabling the package from proposed. I'll report
back in a few days with results.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1545308
Title:
Sorry, I spaced this. Description updated. :)
** Description changed:
https://bugzilla.gnome.org/show_bug.cgi?id=758641
Please consider taking this memleak fix from upstream. I've built the
package with it locally and confirmed that it fixes the leak in xfce4
-power-manager, which
Thanks fellas!
Iain,
Was the SRU comment directed at me or Sebastien? I would be happy to
update what I can later this evening, but some of the information
requested there seems like it would better come from someone more
familiar with the glib code base (potential regressions, etc).
--
You
Public bug reported:
https://bugzilla.gnome.org/show_bug.cgi?id=758641
Please consider taking this memleak fix from upstream. I've built the
package with it locally and confirmed that it fixes the leak in xfce4
-power-manager, which is mentioned in the upstream report. It also
fixes a
12 matches
Mail list logo
