Actually, upon a closer look, it appears like command-not-found has been
entirely unmaintained for more than 2 years now, so efforts to get this fixed
upstream, let alone backported to focal, are probably futile.
We should probably just remove this package from our base image and let the end
I'm aware of that, but that workaround defeats the point of enabling compressed
list storage.
We're using the patch linked above to solve the real issue without that space
overhead, but such local fixes are a maintenance issue. Sadly there appears to
be no intention to accept the fix upstream.
Public bug reported:
On all Ubuntu releases since at least 19.10, enabling compressed APT
package list storage with command-not-found installed leads to this
crash in the cnf-update-db hook called by apt update:
Traceback (most recent call last):
File "/usr/lib/cnf-update-db", line 26, in
Hm, it's been a while...
I think back then I made some btrfs developers aware of it on IRC, but never
got around to sending it to the mailing list.
I'm running my own kernel builds for now (I had to do that to fix some other
issues anyway) with the patch from comment #4 applied, which seems to
So far I have not been able to reproduce it on the mainline kernel linked above.
However, given the intermittent nature of the problem, I'm not convinced that
this was actually fixed.
The source code related to the underlying root cause looks unchanged, and the
symptoms may well be hidden away
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765998
Title:
FS access
I can confirm that the issue still exists in the mainline kernel build
linked above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765998
Title:
FS access deadlock with btrfs quotas enabled
To
This patch seems to fix it for me (running that for several days now).
** Patch added: "0002-qgroup_accounting_fix.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765998/+attachment/5126022/+files/0002-qgroup_accounting_fix.patch
--
You received this bug notification because
I cannot run the affected (production) system using a broken kernel, and it
will lockup after boot within seconds.
If necessary, I can provide additional information or testing upon request.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
** Description changed:
I've spent the last few days tracking down an issue where an attempt to
shutdown an LXD container after several hours of host uptime on Ubuntu
Bionic (4.15.0-15.16-generic) would cause a kworker thread to start
spinning on one CPU core and all subsequent container
The cause of the issue is already understood, and the machine currently isn't
running an unmodified kernel for debugging reasons. Apport logs won't help here.
Contact me if you need specific information.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this
Public bug reported:
I'm running into an issue on Ubuntu Bionic (but not Xenial) where
shortly after boot, under heavy load from many LXD containers starting
at once, access to the btrfs filesystem that the containers are on
deadlocks.
The issue is quite hard to reproduce on other systems, quite
Public bug reported:
I've spent the last few days tracking down an issue where an attempt to
shutdown an LXD container after several hours of host uptime on Ubuntu
Bionic (4.15.0-15.16-generic) would cause a kworker thread to start
spinning on one CPU core and all subsequent container start/stop
The fix does not seem to work, it just changes the error message to "Cannot
open your terminal '' - please check." for me.
The reason seems to be that the patch relies on attach_fd to be set by code
that's inside an ifndef NAMEDPIPE block, which isn't being compiled for the
ubuntu package.
That
I just had something very similar after statefully stopping a container
(in order to do a kernel update from 4.4.0-59 to 4.4.0-62) and
attempting to start it back up.
I have saved the state files and logs in case they can be of any help,
please let me know how I can send those to you: ~7MB of log
Seen on several ARM devices (ODROID-X2, Cubieboard1,
OLinuXino-A20-MICRO) on Ubuntu 14.04 as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1247107
Title:
Runaway
Seen on several ARM devices (ODROID-X2, Cubieboard1,
OLinuXino-A20-MICRO) on Ubuntu 14.04 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247107
Title:
Runaway irqbalance consuming CPU and
This crash occurred in a certain situation after nouveau switches to
software rendering because of a GPU lockup. This used to happen once
every few days on 13.04.
After the upgrade to 13.10 nouveau became completely unusable with GPU lockups
and Xorg crashes happening every few minutes, causing
Does not appear to be fixed in the official repositories yet, despite
being in Fix Released state since more than 6 weeks?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132555
Title:
*** This bug is a duplicate of bug 1155327 ***
https://bugs.launchpad.net/bugs/1155327
** This bug has been marked a duplicate of bug 1155327
skype crashed with SIGSEGV in malloc@plt()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This crash happened to me shortly after a release upgrade from quantal
to raring, but only once. GNOME shell seems to work well apart from this
single crash so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Happened to me yesterday while using RDP to a Windows Server 2003
system. It usually works nicely, but yesterday it just suddenly crashed
while I was using the session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same here with 3.5.0-5 on precise. (I think I got it through the xorg-edgers
PPA or something.)
3.5.0-4 worked fine, 3.5.0-5 hangs on resume, with bluetooth LED on, wifi LED
off, black screen on Lenovo T410.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Seems like the X input device is missing a bunch of properties expected by
synaptiks, in my case:
- Synaptics Edge Motion Always
- Synaptics Tap FastTap
- Synaptics Circular Pad
This is on a Lenovo T410 with a SynPS/2 Synaptics TouchPad.
After making it assume [False] as the value of those
Unbelievable that this bug is still present in 11.10.
I had to redo the whole installation because of this, as attempting to go back
to the partitioning step to add the missing partition makes all later steps
fail irrecoverably because of the installer forgetting that partitioning was
already
I ran the tests again, with the noop, cfq and deadline I/O schedulers,
and the results differed in interesting ways. See attached logs.
** Attachment added: noop test run 1
https://bugs.launchpad.net/linux-linaro/+bug/709245/+attachment/2256614/+files/speedtest-noop.log
--
You received this
** Attachment added: cfq test run 1
https://bugs.launchpad.net/linux-linaro/+bug/709245/+attachment/2256615/+files/speedtest-cfq.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/709245
Title:
** Attachment added: deadline test run 1
https://bugs.launchpad.net/linux-linaro/+bug/709245/+attachment/2256616/+files/speedtest-deadline.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/709245
** Attachment added: noop test run 2
https://bugs.launchpad.net/linux-linaro/+bug/709245/+attachment/2256617/+files/speedtest-noop%20%282%29.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: cfq test run 2
https://bugs.launchpad.net/linux-linaro/+bug/709245/+attachment/2256618/+files/speedtest-cfq%20%282%29.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/709245
** Attachment added: deadline test run 2
https://bugs.launchpad.net/linux-linaro/+bug/709245/+attachment/2256619/+files/speedtest-deadline%20%282%29.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Let me quote from #pandaboard:
prpplague TheSeven: the direction the debugging is going is that this is a
thread issue, i suspect that the .0099 is just under the thread timing
prpplague TheSeven: linaro folks and fedora folks are working on debugging
this
prpplague TheSeven: it doesn't appear
I just tried the 3.0 kernel, and it behaves in exactly the same way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/709245
Title:
panda: USB disk IO slow
To manage notifications about this bug go
*** This bug is a duplicate of bug 709245 ***
https://bugs.launchpad.net/bugs/709245
** This bug has been marked a duplicate of bug 709245
panda: USB disk IO slow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Guess what, this issue indeed seems to be completely unrelated to USB.
Something similar is going on for SD card access (see Bug #787246), and
accessing LAN/WLAN has only an indirect influence.
Look at this: http://paste.ubuntu.com/656410/
Seems like the CPU entering sleep states or something
No noticable improvement: http://paste.ubuntu.com/656498/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/709245
Title:
panda: USB disk IO slow
To manage notifications about this bug go to:
Further testing points towards thread switching behavior being related:
Nothing running in parallel: 10MB/s at big block sizes
perl -e while (1) { }: 5MB/s
perl -e use Time::HiRes qw( usleep ); while (1) { usleep(1) }: 20-25MB/s
perl -e use Time::HiRes qw( nanosleep ); while (1) { nanosleep(1) }:
When running just dd at 1MB block size, I get ~5.5MB/s.
When running with sudo ping -q -i.0100 localhost in the background, ping causes
1% CPU load, and I get ~10MB/s at 1MB block size and these ping statistics:
6228 packets transmitted, 6227 received, 0% packet loss, time 97329ms
rtt
This bug seems to have gone away in 2.6.39, as indicated by the upstream bug
report.
I updated to 2.6.39 amd64 yesterday and haven't had a single freeze since that,
while it happened every couple of minutes before.
(Lenovo T410, Nvidia NVS 3100m)
--
You received this bug notification because
Public bug reported:
I'm observing weird I/O behavior with natty's 2.6.38-1209-omap4 kernel running
on a pandaboard:
When reading from a USB HDD, the relationship between read block sizes and
throughput looks like this: http://paste.ubuntu.com/604616/
(the buffer cache has been flushed with
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787246
Title:
Slow SD card and USB HDD I/O for block sizes bigger than a couple of
bytes
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
When trying to connect to a not yet configured network, NM asks for the
certificates etc.
In the bottom right corner of the Window is the confirmation button, which will
save the information provided and try to connect to the network, in German it's
called Verbinden, so Connect is a guess.
--
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Confirmed
--
Grayed out Connect button when using WPA2 Entreprise+TLS authentication
https://bugs.launchpad.net/bugs/290285
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same issue here. When I try to connect to a WPA2 TLS network, the OK button
in the form asking me for the certificates is grayed out no matter what I do.
nm-applet says the following:
** (nm-applet:11940): WARNING **: Invalid connection: 'NMSettingWireless' /
'ssid' invalid: 2
repeated 13 times
I can confirm this; it turned up after the update to 2.6.24-20, along
with some other weirdnesses.
--
b44 module does not load anymore
https://bugs.launchpad.net/bugs/251538
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I can confirm this. If you enable sound, the text output will freeze
unless it's running at root in current hardy.
--
bb freeze when begin music
https://bugs.launchpad.net/bugs/212401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
46 matches
Mail list logo
