Public bug reported:
laptop powered off after I put it in my bag for transport, so this is
definitely a real suspend/resume failure.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-4-generic 3.11.0-4.9
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
** Package changed: acpi-support (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1256636
Title:
Lenovo S531: restart after shutdown
Status in “linux” package
Public bug reported:
libsdl1.2 fails to build in trusty-proposed due to eglibc 2.18, which
rearranges headers and exposes an incompatibility between eglibc and
kernel handling of P_ALL, P_PID, P_GID.
libtool: compile: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat
Christopher,
On Wed, Aug 14, 2013 at 10:49:20AM -, Christopher M. Penalver wrote:
Steve Langasek, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest
(adding libsdl1.2 task and ftbfs tag for better qa.ubuntuwire tracking)
** Also affects: libsdl1.2 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: ftbfs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Never saw this bug again after the one time on a now-obsolete release.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
So you don't see any suspend/resume failures anymore, but apport keeps
prompting you to open bugs?
No, not at all. This *is* a suspend/resume failure.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Public bug reported:
The same as bug #1229495. Suspend/resume seems to suddenly be quite
unreliable.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-8-generic 3.11.0-8.15
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
Public bug reported:
Still happening more or less frequently.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-8-generic 3.11.0-8.15
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
Annotation: This occured during a
Do you happen to recall the last 3.11 kernel that did not exhibit this
bug?
I don't remember seeing this with 3.11.0-6, but that's not worth much;
it may have just not become an issue for me that was worth reporting
until I was traveling (and therefore suspending/resuming more often) and
A kernel oops is always a kernel bug, not a userspace bug. Reassigning
to the kernel.
** Package changed: nfs-utils (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
another instance of the failure to resume on my x201 with 3.11.0-8.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-9-generic 3.11.0-9.16
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
Annotation:
There is nothing hardware-specific about this bug. Taking the model info
back out of the title, to avoid confusion.
** Summary changed:
- [Lenovo ThinkPad X201 3249] system swapping itself to death in raring for no
good reason
+ system swapping itself to death in raring for no good reason
--
** Changed in: powerd (Ubuntu Saucy)
Status: New = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1234743
Title:
omapfb module floods system with udev events on
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
On Mon, Oct 14, 2013 at 10:09:17AM -, Colin King wrote:
One thing to try is to reset to factory defaults on the firmware and
boot (to see if it still works!). Then shutdown, remove AC and battery
and wait 5 or so minutes to ensure everything like the Embedded
Controller is completely off
If this hangs in an lsgetxattr() syscall with the raring kernel but not
when using the quantal kernel with the same userspace, then I think this
is clearly a kernel issue. Reassigning.
FWIW I never saw this issue here with the raring kernel, but all of my
krb5 NFS mounts are v4.
** Package
** Package changed: nfs-utils (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1243429
Title:
NFS Lockups with 13.04 clients to 12.04.03 server
Status in
On Wed, Oct 23, 2013 at 10:15:46PM -, Gregor Larson wrote:
init 1 root 15w REG 8,24 1134 438383
/var/log/upstart/mountall.log
mountall is a service that's supposed to run once at boot and then exit. If
mountall is still running when you shut the system down, then
*** This bug is a duplicate of bug 1238194 ***
https://bugs.launchpad.net/bugs/1238194
** This bug is no longer a duplicate of bug 229732
USB Keyboard drivers not loaded in initramfs
** This bug has been marked a duplicate of bug 1238194
keyboard doesn't work to enter password with
So when I wrote 6 months ago that:
If you can reproduce this issue, please file a new bug report against
the sysvinit-utils package with details. It is certainly unrelated to the
common issue being described here.
Rather than doing this to help yourself, you switch distros, decide that
No. I have an aftermarket wlan card in this system that prevents using
the stock bios from Lenovo, and Tue tools for unpacking bios images for
modification appear to have bit rotted.
** Tags removed: needs-upstream-testing
--
You received this bug notification because you are a member of Kernel
On Sun, Oct 27, 2013 at 01:25:26AM -, Furkan Alaca wrote:
It's been another 10 days since I last posted, and I still haven't
encountered this bug again. I have no idea if it was the new kernel
version or the BIOS that fixed it - I updated them both within a
couple of days of eachother, so
On Mon, Oct 28, 2013 at 07:21:51PM -, Colin King wrote:
I wonder if the issue is because you have a different wireless card and
this is causing the firmware some issues when coming up from a clean
start on resume.
It's not a matter of anything happening on resume, fwiw; it doesn't suspend
I'm not sure why this bug is still open, but the current isdnutils
package does use a filename with a proper .conf extension - so closing
the report.
** Changed in: isdnutils (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Kernel
** Changed in: upstart (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1066351
Title:
upstart ftbfs in quantal on arm*
Status in
your bootchart shows:
- blkid takes 29 seconds to identify your root filesystem from the initramfs.
- the initramfs spends another 5 seconds looking for a hibernate image on swap.
It doesn't find it, presumably either because the wrong UUID is encoded in
/etc/initramfs-tools or because the
** Package changed: plymouth (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1234546
Title:
Plymouth screen refresh is bad when Live USB is started in UEFI mode
I suppose this is a driver that would still be in the picture when
switching to Mir, and we can't hope to avoid the issue by changing
display servers? You could test this by following the directions at
https://wiki.ubuntu.com/Touch/Testing/Mir.
--
You received this bug notification because you
Public bug reported:
and again.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-11-generic 3.11.0-11.17
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
Annotation: This occured during a previous suspend and prevented
Public bug reported:
the problem persists.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-11-generic 3.11.0-11.17
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
Annotation: This occured during a previous suspend and
So for the first time today I had occasion to try suspending my laptop
when I wasn't in a hurry to immediately shove it in my bag, and observed
the following:
- on lid close, the suspend light blinks for a little while (as usual)
- then the machine beeps (as usual)
- the suspend light then
This behavior (fans spinning on suspend, power off after a minute) is
consistently reproducible at least back to 3.11.0-4. I definitely did
not experience this problem while 3.11.0-4 was current. So it looks
like something else may have changed to cause this bug.
I am able to reproduce the
Workaround is in place in upstart package to reduce the flood of events
that are causing this rapid memory growth, and we believe a fix to the
unity upstart client will fix the memory leak entirely; but upstart
needs to be more robust against misbehaving clients. Opening a task
against upstart
So upstart's udev bridge needs to have a capability of filtering events.
Adding an upstart upstream task
** Also affects: upstart
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Also affects: upstart
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes session upstart to consume massive
: undocked, console, echo mem: fail
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com
This error message means that one of the partitions on the disk is in
use, so the kernel is refusing to update its internal partition map
because this would clobber the in-use filesystems. This is not a kernel
bug, it looks like an installer bug.
Please reproduce this error, and attach the
So the reason the memory usage wasn't growing after re-exec was because
unity8 didn't automatically reconnect when the dbus connection dropped.
If I kill and restart unity8, the problem reappears.
So the memory usage is indeed associated with the dbus client, even
though disconnecting the client
James, how was this valgrind trace produced? The stacktrace doesn't
show anything above the low-level calls in dbus, making it difficult to
pinpoint the actual source of the problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
On Mon, Oct 14, 2013 at 11:39:01PM -, DarkStarSword wrote:
I don't think testing this should be a prerequisite
Nice selective quoting.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
On Tue, Oct 15, 2013 at 08:19:53AM -, James Hunt wrote:
Once again, the biggest offender by a huge margin is dbus:
==15329== 1,153,679,208 bytes in 12,025 blocks are still reachable in loss
record 208 of 208
==15329==at 0x402BB88: realloc (in
** Branch linked: lp:~xnox/ubuntu/saucy/systemd/udevd-ignore
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1234743
Title:
omapfb module floods system with udev events on samsung galaxy
After discussing this with Ted, I think the right answer architecturally
is to move these clients to talking to the session bus, where filtering
of messages will be done for us automatically, and have the session init
register on the session bus, rather than deploying an unreliable change
like
** Package changed: acpi-support (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1239346
Title:
Acer TravelMate P273 SMB Fn keys not working
Status in “linux”
I agree, this is a horrible, horrible patch; and thank you very much for
writing it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1234743
Title:
omapfb module floods system with udev
Hello Colin, or anyone else affected,
Accepted systemd into saucy-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/systemd/204-0ubuntu19
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
The efivarfs driver in the saucy amd64 kernel is built as a module
instead of being built in. As a consequence, when mountall checks
/proc/filesystems to see what optional filesystems are supported, it
doesn't find efivarfs there and efivarfs is never mounted at boot. This
This indicates that you had an unofficial libasound2:amd64 package
installed on your system. The official packages in the archive will
have matching contents, so there will be no file mismatches causing
unpack failures at install time.
As Luke indicates, reinstalling libasound2:amd64 will fix
** Package changed: base-files (Ubuntu) = sysstat (Ubuntu)
** Package changed: sysstat (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1226172
Title:
iostat:
The symptoms you describe (and that are described in the linked forum
discussion) point to a problem with the kernel graphics handling.
Reassigning to the kernel.
** Package changed: plymouth (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
** Changed in: crash (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) = Matthias Klose (doko)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1318809
Title:
Support for the
Public bug reported:
On ppc64el, a kernel patch and a userspace patch are needed to have
hotplugging of devices via e.g. 'virsh attach-interface' properly
detected by a guest kernel.
http://sourceforge.net/p/powerpc-utils/mailman/message/32064992/
http://patchwork.ozlabs.org/patch/327089/
If mountall is being triggered before the device is in its final
location, then this indicates you are referencing the device by uuid in
/etc/fstab instead of by its device mapper name. This is not supported;
filesystem UUIDs are not unique with device mapper, due to features
including multipath,
thanks for tracking this down, Chris!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/127
Title:
echo string to /dev/kmsg fails to appear on /var/log/syslog
Status in “linux”
Public bug reported:
utopic has been intermittently failing to suspend for me. It works
after a fresh boot, and then mysteriously stops working.
'echo mem /sys/power/state' was returning ENOENT on the write syscall.
dmesg shows the following:
[38986.394761] [drm] Enabling RC6 states: RC6 on,
** Description changed:
- utopic has been intermittently failing to suspend for me. It works after a
fresh boot, and then mysteriously stops working. The following was returning
was returning ENOENT on the write syscall:
- echo mem /sys/power/state
+ utopic has been intermittently failing to
All of the cited bugs concern desktop applications. No evidence is
provided to support the claim that Ubuntu 10.04 Server is affected.
While the kernel is common to both desktop and server flavors, you can
expect that regressions that only impact end-of-life configurations will
not be a high
On Tue, Jun 10, 2014 at 02:50:04AM -, hamish wrote:
er, seriously? the kernel and firefox don't fall under things people
might possibly need LTS for?
You seem to have misunderstood what LTS means. LTS does not mean feel
free to run this OS indefinitely, without upgrading, and expect to
So, here's something funny. The suspend/resume failures started
happening for me on September 20, almost exactly 3 years after I'd
gotten the machine; and was reproducible with older kernels and OSes
that had previously worked fine. I had joked that maybe the BIOS had a
time bomb in it, or just
I did just have a suspend/resume failure, but it was the first one after
many repeated test suspend/resume cycles and it was also the first time
I was transporting the laptop so could have been a physical connection
coming loose anyway (I thought it had suspended successfully before I
put it in
** Tags removed: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1238188
Title:
[HP Compaq dc5850 Small Form Factor PC] No desktop effects on a radeon
3100 graphics
I don't feel comfortable visually reviewing all the changes to the x86
code here. It looks sane from a high-level view, but please make sure
this gets tested on x86 before upload.
+1, *if* you make sure the existing use cases are covered on i386 and
amd64.
--
You received this bug notification
** Changed in: apparmor (Ubuntu)
Status: Fix Committed = New
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Status: Fix Committed = New
** Changed in: libvirt (Ubuntu)
Status: Fix Committed = New
** Changed in: lightdm (Ubuntu)
Status: Fix Committed = New
**
The debdiff attached for apparmor looks good, aside from missing some
Breaks: on the old versions of the packages that need to go in at the
same time (because their policies will cease to be sufficient once
ptrace/signal mediation support lands). Jamie has pushed the added
Breaks; once they're
** Changed in: linux (Ubuntu)
Status: Fix Released = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/977042
Title:
low grafic with new release/kernel
Status in The
Please do not change the state of this bug report. The bug has been
marked incomplete by the developers because it's awaiting information
from the reporter.
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: linux (Ubuntu)
Assignee: saioa (sairis37) =
Deje ya de cambar el estado del reporte.
** Changed in: linux (Ubuntu)
Status: Fix Committed = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/977042
Title:
low grafic
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/977042
Title:
low grafic with new release/kernel
Status in The Linux
** Changed in: linux (Ubuntu)
Status: Fix Released = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/977042
Title:
low grafic with new release/kernel
Status in The
** Changed in: linux (Ubuntu)
Status: Fix Released = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/743907
Title:
Performance degradation after resume
Status in
fwiw, I've investigated the dpkg segfaults, and seen the following:
$ gdb dpkg
GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7
[...]
Reading symbols from dpkg...Reading symbols from
/usr/lib/debug//usr/bin/dpkg...done.
done.
(gdb) run -l
Starting program: /usr/bin/dpkg -l
Program received signal SIGSEGV,
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/977042
Title:
low grafic with new release/kernel
Status in The Linux
I am absolutely not using btrfs. Everything is ext4 on lvm on dm-crypt.
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The issue is no longer reproducible with a current trusty kernel in my
current configuration (3.12.0-7-generic, with an SSD - I think this bug
report may have been from before I installed the SSD). So there doesn't
seem to be any point in testing further upstream kernels.
** Changed in: linux
However, I am not marking this as fixed upstream because I don't know
that it was a kernel change that resolved it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1117499
Title:
killall
This bug very clearly has nothing at all to do with the BIOS.
Christopher, it is inappropriate to ask bug submitters to test with a
new BIOS for bugs like this - the BIOS is entirely unrelated to the
network filesystem layer, and if upgrading the BIOS did have any effect,
it would be *irrelevant*
On Sat, Jan 04, 2014 at 07:28:12AM -, Andrew Radke wrote:
In the past we have also been asked to update our kernels and at no
stage has this improved the situation. Is there anything to indicate
that it is likely to help on this occasion or that it is a kernel bug
and not a problem
On Wed, Jan 08, 2014 at 06:47:03PM -, Christopher M. Penalver wrote:
Steve Langasek, thank you for your comment. While it is always appreciated
when a developer steps in and advises to a bug report, a portion of your
comments don't make sense (which I'm happy to take off report
** Tags removed: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1268830
Title:
package linux-image-2.6.32-48-generic 2.6.32-48.110 failed to
install/upgrade:
** Tags removed: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269558
Title:
3.13.0-3 can not boot
Status in “linux” package in Ubuntu:
Incomplete
Bug
** Tags removed: regression-update trusty
** Tags added: trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269296
Title:
Linux 3.13.0-3-generic doesn't boot [HP Compaq Mini 700EW]
On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote:
Lennert of systemd refers to this bug on google+. He outlines a fix for
the simple case:
The fix he outlines is not for this bug. It's not for a bug we have in
upstart in Ubuntu at all; we already reliably ensure telinit u on upgrade of
On Wed, Jan 22, 2014 at 05:11:03PM -, Clint Byrum wrote:
The other one is the one that would sweep up the mess we occasionally
see when something misbehaves.
I'd like to see Ubuntu's shutdown do more to protect against that
failure mode.
I would, too, but I don't agree that the method he
Is this reproducible for you when installing trusty (vs. saucy)?
Dimitri tells me that he's successfully installed trusty inside qemu
running with the new ovmf. It's possible that this is not a bug in edk2
at all, only a latent bug in the kernel that has been exposed by a
behavior change in edk2.
Public bug reported:
In trusty, I frequently find that unmounting NFS shares (which I do on
my laptop before roaming) frequently causes a soft lockup in the
kernel that leaves me needing to hard reboot the system, because both
network access and disk access start failing and the unmount itself
** Tags removed: regression-proposed
** Tags added: regression
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1282302
Title:
deadlock when unmounting nfs shares in trusty
Status in
3.12 final appears to be unaffected. Moving to 3.13rc3.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1282302
Title:
deadlock when unmounting nfs shares in trusty
Status in “linux”
rc3 is affected.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1282302
Title:
deadlock when unmounting nfs shares in trusty
Status in “linux” package in Ubuntu:
Confirmed
Bug
Seth, here's a copy of a lockup from /var/log/kern.log. Sorry, I wanted
to attach this sooner, but the fact that the lockup takes down both the
network and the filesystem made capturing this unreliable.
Feb 20 17:52:14 virgil kernel: [93233.532498] BUG: soft lockup - CPU#1 stuck
for 22s!
rc2 appears to be unaffected.
So it looks like rc3 is the earliest rc showing the issue.
Where do you want me to bisect next?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1282302
8aa9c36788ee5ebf7a1377742d577911bfc9cfe7 appears to be unaffected.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1282302
Title:
deadlock when unmounting nfs shares in trusty
Status in
Seth, happy to try a test kernel with that commit reverted.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1282302
Title:
deadlock when unmounting nfs shares in trusty
Status in
Ah, turns out this is resolved in 3.13.0-12-generic (and probably
earlier). Thanks!
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: Steve Langasek (vorlon) = Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1160346
Title:
do
Thanks for respecting the Ubuntu bug management guidelines, but as
Brian's manager, I get to assign bugs to him ;)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) = Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Kernel
Not just that the wiki would seem to be not quite right, but also that
some well-understood convention is needed, for use when one person
justifiably assigns a bug to another.
The convention is already well understood among Ubuntu developers...
So more than a month was wasted, when someone
Hello Adam, or anyone else affected,
Accepted debian-installer into trusty-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu318.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Package changed: linux (Ubuntu) = rsyslog (Ubuntu)
** Changed in: rsyslog (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1366829
Title:
Public bug reported:
The cross-toolchain base packages are currently failing to build,
because linux-source is trying to build the linux-cloud package. This
fails because dh-systemd isn't (and shouldn't be) installed.
The linux packaging should be fixed to not try to build the linux-cloud
1 - 100 of 2524 matches
Mail list logo
