Public bug reported:
v5.2.18 dkms fails to build on bionic with the recently released 5.0
kernel from hwe-18.04-edge
I've attached a patch which doesn't seem to not work. It should
definitely be reviewed by someone with domain knowledge, though. The
problems were all use of interfaces
Terrific! Thanks for the quick response!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827804
Title:
Bash completion not working
To manage notifications about this bug go to:
Public bug reported:
The bash completions file is installed improperly by default. It is
currently installed as /usr/share/bash-
completion/completions/cargo.bashcomp.sh, but files in this directory
need to be named to match the command they complete. So it should
either be installed as
Reinstalled from bionic-updates and confirmed working.
Thanks again to all involved in resolving this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs
Tested working! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about
Thanks Dimitri!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage notifications about this
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to
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)
Confirmed with 4.10.0-38-generic from zesty-proposed.
Will this be hitting the 4.11.0 branch as well? I'm actually using the
generic-hwe-16.04-edge package on xenial.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification
Sorry, I missed Robie's comment yesterday. Upstream seems
inactive/dead. Nothing from Lennart on
https://bugs.freedesktop.org/buglist.cgi?product=libatasmart since 2011.
No commits to http://git.0pointer.net/libatasmart.git since 2012. I
didn't see any indication the development had been picked
I've added support for SSD Life Left via the quirks infrastructure. The
two devices I have access to, that abuse attribute 231, store the value
differently, so I had to use separate quirks.
The attached patch adds support for Kingston A400 and V300 series SSDs.
Side-effect, correct temperature
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
Will this be making its way to a release build?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706243
Title:
Stranded with ENODEV after mdadm --readonly
To manage notifications about this bug go
Confirmed working!
Thanks for the quick response!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706243
Title:
Stranded with ENODEV after mdadm --readonly
To manage notifications about this bug
For reference, https://www.spinics.net/lists/raid/msg57989.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706243
Title:
Stranded with ENODEV after mdadm --readonly
To manage notifications
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1706243/+attachment/4921162/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706243
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1706243/+attachment/4921165/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1706243/+attachment/4921164/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706243
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1706243/+attachment/4921163/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706243
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1706243/+attachment/4921159/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706243
Title:
apport information
** Tags added: apport-collected xenial
** Description changed:
Please backport upstream fix.
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
- stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
+
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1706243/+attachment/4921156/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706243
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1706243/+attachment/4921161/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1706243/+attachment/4921160/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1706243/+attachment/4921157/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1706243/+attachment/4921158/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Please backport upstream fix.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589605
Title:
evolution-calendar-factory uses lots of
Nathan,
The linked Debian bug is unrelated to this crash. It disabled the
internal media router component, which was initially broken on Linux and
conflicted with the external cast plugin. With the fixes here, Debian
should be able to re-enable the internal media router component in their
David,
That looks to be totally unrelated to the issue addressed in this bug
report. You should start a new one.
Olivier,
I've had the same chromium process running for several hours now,
intermittently messing with the cast extension and cycling wifi. Still
going strong. I think this one
Test builds seem to work here! Casting didn't even break :)
Thanks Olivier!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on xenial
Andrew,
Try the workaround in #19.
Note: --disable-extensions with an S, not --disable-extension.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to
Rohan,
Confirmed. I did have to interact with the cast extension after
enabling wifi to get it to crash though. It may have just been
coincidence though (wireless network list was probably cached).
I also tried plugging and unplugging the ethernet cable with wifi off,
which did not seem to
I was able to wget the diff from
https://bugs.chromium.org/p/chromium/issues/attachment?aid=116063. I
believe adapting it to the current code base should resolve the crash.
However I do not have a 16.04 build env to test on my system with wifi
nor a wifi adapter to test on my 14.04 system.
Just an FYI, this can be worked around by disabling the media router
extension.
1) Start chromium on the command line with: chromium-browser
--disable-extensions
2) Navigate to chrome://flags
3) Search for "media router" and set it to "Disabled"
I have tested 59.0.3071.109-0ubuntu0.16.04.1289
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545308
Title:
Backport upstream fix for
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
The patch is just a work around for our upcoming release. The plan is
to remove it once ATI/Xorg fix the real problem.
--
xbmc not working with opensource radeon driver in jaunty
https://bugs.launchpad.net/bugs/363139
You received this bug notification because you are a member of Ubuntu
Bugs,
42 matches
Mail list logo
