Christopher,
Thank-you for the work you have put into researching this. It is really
appreciated.
The system I originally used to reproduce this bug has since been updated to:
linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1
I have just attempted to reproduce the issue and I have been unable
CentOS version of this bug report:
https://bugs.centos.org/view.php?id=18383
** Bug watch added: bugs.centos.org/ #18383
https://bugs.centos.org/view.php?id=18383
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When accepting client connections under load, duplicate endpoints may be
returned. These endpoints will have different (usually sequential) file
descriptors but will refer to the same connection (same server IP, same
server port, same client IP, same client port). Both copies
** Changed in: pciutils (Ubuntu)
Assignee: Mark Thomas (markthomas) => (unassigned)
** Changed in: pciutils (Ubuntu Disco)
Assignee: Mark Thomas (markthomas) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
/controller/mime/respond_to_test.rb
actionpack/test/controller/new_base/content_negotiation_test.rb
** Affects: rails (Ubuntu)
Importance: Undecided
Assignee: Mark Thomas (markthomas)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This was erroneously marked as released. Verification is not yet done.
** Changed in: linux (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792044
Public bug reported:
** DRAFT in progress...**
[Impact]
The urllib3 library is not using the alternative name field on a TLS
certificate to validate the certificate. The problem has been fixed, and we
want to take advantage of the fix in Xenial.
"Initial error that was hit while using
Public bug reported:
Specifying "vfs objects = recycle full_audit" Results in the audit
behavior working but the recycle behavior not working:
Jul 5 20:46:05 sambatest smbd_audit:
mark|192.168.12.120|myclient|test|unlink|ok|test-b.txt
However, specifying "vfs objects = full_audit recycle"
I just tested this with a 20171220 daily build of 17.10 in us-east-1, in
a custom VPC, and it appears to be working fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729573
Title:
netplan breaks
Proposed for Zesty and Xenial so that you can discuss the path to a
Xenial SRU for IPv6 support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639030
Title:
Configure networking based on EC2
I performed this test in EC2:
- Launched an instance of latest Xenial AMI in us-west-1 (ami-2afbde4a, kernel
4.4.0-1013-aws) with 8GB root EBS volume
- Created a second EBS volume, 100GB, and attached as /dev/sdf.
- Ran sudo udevadm monitor --kernel --udev and resized both volumes. No udev
Public bug reported:
A Xen blkfront(xen-blkfront:) patch has been submitted upstream, regarding the
resizing of a blkfront device from dom0. This patch would emit a KOBJ_CHANGE
uevent, to notify a guest of the change. This allows for custom udev rules, such
as automatically resizing a
Confirmed.
** Changed in: unity-control-center (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658118
Title:
Network applet should warn or generate a
Confirmed.
** Changed in: unity-control-center (Ubuntu)
Status: New => Triaged
** Changed in: unity-control-center (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: unity-control-center (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
David,
That's not lubuntu, it's 1 (one) ubuntu 4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1495178
Title:
Failed to set wall message, ignoring: Message recipient disconnected
from message
Public bug reported:
installing mythbuntu onto a acer aspire ao110 for the first time crashed
the installer
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.7
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion:
Public bug reported:
installing mythbuntu onto a acer aspire ao110 for the first time crashed
the installer
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.7
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion:
Bruce Cowan is correct, the 03_fix_xinerama_stack patch introduces this
problem, however upstream still has the problem that that patch is
attempting to fix.
I have attached another patch that attempts to solve both problems.
It's still not perfect; ideally we would like the default monitor to be
This is still present in Intrepid.
--
Blinking cursor can not be deactivated anymore
https://bugs.launchpad.net/bugs/188732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Clarification: in Intrepid, the gconf entry apps/gnome-
terminal/profiles/*/cursor_blink_mode exists and works, but the
preference control is still missing from the edit profile preferences
dialog. It took me ages to find that, though.
--
Blinking cursor can not be deactivated anymore
I have been experiencing the same problem.
I keep my profile on an SMB file share so I can sometimes run Firefox
from Windows XP and sometimes from Ubuntu. When it occurs under Ubuntu,
I can repair it by running Firefox instead from Windows XP and
immediately exiting. When I open it under
We are talking about wear and tear, not drives catching fire. It's
expected that a drive will break eventually, and load cycling is just a
(relatively new) way that drives can reach end of life.
However, the crux of this bug is that Ubuntu is, by default, causing
_excessive_ wear and tear on
Bart,
Disabling the APM feature of a drive can never be a fix. Parking the
drives is a feature of the disk, and the The Load_Cycle_Count is
supposed to go up, albeit slowly, during normal usage. The point of
this bug is that the pathological worst case for load cycling is one
access every 30
The Debian update is the workaround not the fix:
* Set hdparm power management to 254 for all hard drives.
I'd be happier to see the known idle-writers fixed first, so we can
start finding out what else causes the problem. I'm concerned that with
a workaround in place this will get neglected
William,
It should work without the hdparm -B 254 workaround. If it doesn't then
you have some other program running that is also accessing the disk
(suggestions have been thunderbird amongst other things). This is one
of those annoying bugs where you have to squash all of them before the
@ Chris Jones:
ThinkPad X40 drives' raw value is a packed 48 bit number:
3037783573354 = 0x02C34A02C36A
0x02C34A = 181066
0x02C36A = 181098
One of these is your current load cycle count. The other is the load
cycle count at some recent event (most recent power cycle or something,
not sure
I've done some investigation, and I think the hard drive killing bug
that has been infamous lately is caused by bug 31512. See my comments
there for the rationale, but essentially the problem boils down to a
process writing to the disk once every 15 seconds or so (the actual
interval is probably
This is causing bug 59695 (the infamous laptop-killing bug), or rather,
is the actual cause of the drive problem.
On my laptop, ACPID gets a battery event roughly every 15 seconds, each
of these produces a write to the log file.
Laptop hard drives seem to be set up for bursty I/O (a reasonably
Christian Vogler commented in bug 31512 that his ACPID log doesn't seem
to grow but he still gets the bug, so there may be other logging
programs out there too.
I'm using Debian at work at the moment, so I can't write an exact how-
to. You can disable logging entirely by adding -l /dev/null to
Are you seeing battery events at all in that log? Seems strange that
they wouldn't appear.
You are right that it could be any process that's causing the writes,
though specifically it has to be something that writes regularly with
intervals greater than the hard disk park time. If several
What did lm-profiler claim was touching the hard disk? That's probably
the easiest way to work out what's causing the disk to unpark in each
case, as it seems that various programs can cause the effect of bug
59695. There should probably be some kind of review of installed
services to see what
To Bart Samwel:
If the laptop is idling, with no apps doing anything that requires the
disk, then I expect the disk to park, then spin down and stay spun down.
You are correct that dirty pages will get flushed out within 30s, but
the point is that if the user is not doing anything (or is doing
34 matches
Mail list logo
