This bug affects compatibility with unison-2.48.4-1+b1 on Debian buster
also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875475
Title:
Unison from Ubuntu 20.04 is incompatible with Unison from
I've confirmed on a 20.04 system recently installed from the official
server ISO that the passphrase for the newly-created LUKS volume appears
in the following files in /var/log/installer after install:
autoinstall-user-data curtin-install-cfg.yaml curtin-install.log
installer-journal.txt
I agree with @addyp95 - this is a bug in how libvirt works in IPv6-only
environments, and it is still present on focal. For posterity, the
exact details of the workaround are to add the following line to
/etc/libvirt/qemu.conf:
spice_listen = "::1"
** Changed in: qemu (Ubuntu)
Status:
@cpollock: I don't think this is invalid. This is a very poor error
message which gives no pointers about why, and causes logspam. It was
only because of your last update that I realised that I had incorrect
file permissions also.
** Changed in: rsyslog (Ubuntu)
Status: New => Confirmed
I don't think this is really the same problem. The init script for NTP
is designed to honour the settings provided by the DHCP client. In most
cases, this is expected, but when the charm is configured, users expect
the charm to manage the local settings for them without needing to
override the
On which version of Ubuntu did you experience this? Whilst the latest
LTS (18.04) and non-LTS (19.04) versions have moved the ntp package to
universe, they still ship with a fully working configuration. Here's an
example from a stock install on an AWS EC2 instance running disco
(19.04):
Seeing this or something very similar on xenial s390x:
Dec 6 00:25:48 s0lp3 ntpd[238439]: Deleting interface #163484 tap3c93ac38-8a,
fe80::fc16:3eff:fe05:6903%805261#123, interface stats: received=0, sent=0,
dropped=0, active_time=206 secs
Dec 6 00:25:53 s0lp3 ntpd[238439]:
** Changed in: ntp-charm
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744072
Title:
[MIR] Chrony in 18.04
To manage notifications about this bug go
Hi Manuel, ntpd keeps printing "Soliciting pool server" in syslog
because it can't contact any of the ntp servers in the pool. This is
most likely a local configuration problem on your machine or network, or
your service provider's network.
Here are some commands that should help work out where
** Changed in: ntp-charm
Status: In Progress => 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/1744072
Title:
[MIR] Chrony in 18.04
To manage notifications about this bug go
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786146
Title:
ceilometer meter_time_to_live has no effect if applied to existing
mongodb database
To manage
Public bug reported:
If metering_time_to_live is left at its default (never expire data) and
later switched to a positive value, it will have no effect. ceilometer
implements expiry by using a mongodb TTL index. However, it does so
when there is already an existing index on the timestamp field:
Any news on the xenial SRU of keepalived for this bug? It's not showing
up in http://people.canonical.com/~ubuntu-archive/pending-sru per
https://wiki.ubuntu.com/StableReleaseUpdates#Reviewing_procedure_and_tools.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Using an HP ProLiant DL380 Gen10 (Intel Xeon Gold 5118 CPU @ 2.30GHz) I
tested the following kernels (on xenial):
4.13.0-37-generic - FAIL https://pastebin.canonical.com/p/RbTzC3jgjm/
4.13.0-39-generic - PASS
4.13.0-45-generic - PASS
4.15.0-29-generic - PASS
So it seems this was fixed in
I've also seen this issue with a Dell R740 server, Xeon Gold 6132 CPU @
2.60GHz, kernel 4.13.0-37-generic. Switching to hpet clocksource
mitigated it successfully.
Unfortunately I still haven't had the opportunity to test this on 4.15.
** Summary changed:
- Very inaccurate TSC clocksource on
** Summary changed:
- Some sysctl's are ignored on boot
+ Some sysctls are ignored on boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctls are ignored on boot
To manage
Any plans to get this released for trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1416039
Title:
Broken apparmor profile
To manage notifications about this bug go to:
** Tags removed: artful
** Tags added: canonical-is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759787
Title:
Very inaccurate TSC clocksource on HP ProLiant DL380 Gen10 with kernel
4.13
To
Public bug reported:
On kernel 4.13.0-37-generic, HP ProLiant DL380 Gen10 systems have been
observed with very large clock offsets, as measured by NTP. Over the
past few days on one of our production systems, we've used 3 different
kernels: https://pastebin.ubuntu.com/p/nDkkgRqdtv/
All of these
This sort of inconsistency shouldn't happen on mirrors which use the
recommended 2-stage sync: https://wiki.ubuntu.com/Mirrors/Scripts
Currently cn.archive.ubuntu.com is redirected to us.archive.ubuntu.com,
so if the latter works for you, the former should also. I've just
confirmed that I can
@paelzer: There was a plan to enable IPv6 on all pools last year:
https://community.ntppool.org/t/intention-to-enable-ipv6-by-default-
in-2017/91 To my knowledge (and based on my brief checks just now) this
didn't happen. I suspect the reasons for this are insufficient time to
change the pool
Reference from last comment:
1. https://community.ntppool.org/t/recent-ntp-pool-traffic-increase/18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754358
Title:
Default Ubuntu configuration
@paelzer: Rather than the config you've mentioned above (3), wouldn't it
be:
server 0.ubuntu.pool.ntp.org iburst
server 1.ubuntu.pool.ntp.org iburst
server 2.ubuntu.pool.ntp.org iburst
server 3.ubuntu.pool.ntp.org iburst
or:
pool 0.ubuntu.pool.ntp.org iburst maxsources 1
pool
: https://jujucharms.com/u/paulgear/ntp/
** Merge proposal linked:
https://code.launchpad.net/~paulgear/ntp-charm/+git/ntp-charm/+merge/340780
** Changed in: ntp-charm
Assignee: (unassigned) => Paul Gear (paulgear)
** Changed in: ntp-charm
Status: Triaged => In Progress
-
@mfossett: You previously said that you would attempt to gather the
diagnostic information for which @cpaelzer asked you in comment 2. If
you are still experiencing the problem, please add the requested
information to this bug report and change the status from Expired to
New.
--
You received
@paelzer: As I looked at chrony's config and the options which would be
needed in a new chrony charm, I found that most of them were common with
ntp, so I'm going to start work on a branch of the ntp charm which
supports switching between ntp and chrony. I'll link the branch here
when I have some
** Description changed:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
- 2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
-
On 22/01/18 17:27, ChristianEhrhardt wrote:
> Hi Paul,
> I subscribed you as I wanted to clarify something.
> Back in [1], you mentioned it was important to you to get ntpdate (single
> shot cli) and ntpd (daemon) to work together nicely for the ntp charm.
>
> Now if the ntp charm would be
I'm no longer experiencing this on 4.13.0 series kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649727
Title:
No sound card detected with device: Intel Corporation Device 9d71
To manage
Public bug reported:
After upgrading from zesty to artful using do-release-upgrade, a VM
which previously started no longer does:
root@localhost:~# virsh list --all
IdName State
- test
Hi @kogorman-pacbell,
Can you explain what you think should be happening here? Running
ntpdate from sudo or a root shell gives exactly the same behaviour -
ntpdate requires a list of servers to be provided on the command line,
and it is simply indicating that this has not been provided.
In
@paelzer: Sorry for the delay - I was at a conference last week.
I've confirmed that the PPA version for xenial results in reliable
restarts for ntpd. I tested 8 systems, 3 of which were updated to the
new version from the PPA: the 3 upgraded VMs restarted reliably on each
reboot, whilst 3 of
@Robie The ntpdate command has a test mode that does not attempt to set
the clock, which the sntp command lacks.
I've confirmed on multiple systems that the installation of ntpdate
prevents ntp from starting on boot, which IMO is worthy of fixing.
** Changed in: ntp (Ubuntu Xenial)
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1593907 was recently
released to fix ntp/ntpdate interactions; if they're still broken, there
seems little need to justify this given that precedent. (Full
disclosure: I want ntp/ntpdate interactions solid so I can use ntpdate
in the ntp charm.
Maybe this is related to the fact that I'm running a generic kernel?
(The zesty kernels are unstable on my machine.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705988
Title:
snap install
root@peleg:~# snap version
snap2.26.9
snapd 2.26.9
series 16
ubuntu 17.04
kernel 4.12.0-041200-generic
root@peleg:~# snap list
Name VersionRev Developer Notes
core 16-2.26.9 2381 canonical -
root@peleg:~# snap refresh
All snaps up to date.
No containers were harmed (or used)
I'm experiencing this intermittently on a Lenovo ThinkPad T470; I'm
currently running 4.12.0-041200-generic, and it has been patchy
throughout the 4.12.0-rcX series. Anything I can do to gather info?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Azure timesync is preventing a number of our production services from
getting accurate timesync; when is the xenial SRU likely to be
available?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676635
** Description changed:
+ ---
+ READ THIS BEFORE COMMENTING ON THIS BUG
+ ---
+
+ security.ubuntu.com and archive.ubuntu.com have been IPv6 enabled since
+ March 2013 (see comment #29 below). Their connectivity is monitored
Public bug reported:
The Firefox man page documents that -ProfileManager and -P with no
profile specified should both start Firefox with the Profile Manager
dialog. As of a recent release (I'm not exactly sure which one, but has
been since the release of yakkety), this no longer works and both
@nelhage, my LANG=en_AU.UTF-8. To my knowledge, this is not a natively
24-hour locale, but I could be wrong - how does one check?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319195
Title:
I am in no way trying to suggest that there is not a bug here, but this
bug has not affected me from trusty to yakkety. Here's a screenshot
showing my indicator panel. Perhaps there is some particular
combination of options which causes this?
** Attachment added: "Menu_001.png"
I've seen this multiple times in the past; it is highly unlikely to be a
configuration issue, since the NRPE configuration is set by juju charms
in most cases, and we've only seen it in a few circumstances.
** Tags added: canonical-is
--
You received this bug notification because you are a
Given that Debian has already applied the patch which eliminates the
distinction between tabs & spaces, there doesn't seem a lot of point in
keeping a different patch in place. Best to apply the patch as is, and
deal with the issue of augmenting the list separately, if necessary.
--
You
Correction to my comment above: the patch at https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=809344 is preferable to the patch as
proposed; thanks @philroche.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
One comment on @philroche's patch: at present, there is no supported way
to allow DHCP to augment (rather than replace) NTP servers in
/etc/ntp.conf. The different handling of tabs & spaces is a known-
useful workaround for those of us who wish to allow DHCP to specify
additional servers, without
I'm seeing this on xenial on a Lenovo ThinkPad X230, but not
consistently. It only occurs occasionally - most resumes from suspend
are fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636282
This is an operational issue with gerrit, not a bug. Canonical IS are
tracking the issue. Please use r...@ubuntu.com to communicate any further
instances of this problem.
** Changed in: phablet-tools (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because
It appears that this is not a high priority issue, since the default NTP
configuration will automatically exclude the leap-smearing source, given
sufficient other good sources:
http://pastebin.ubuntu.com/23720277/
However, we may want to consider changing the default ntp configuration
to use
The global pool is certainly working and its DNS servers are resolving
correctly:
$ host 0.ubuntu.pool.ntp.org
0.ubuntu.pool.ntp.org has address 108.59.2.24
0.ubuntu.pool.ntp.org has address 129.250.35.250
0.ubuntu.pool.ntp.org has address 52.0.56.137
0.ubuntu.pool.ntp.org has address
If I remember correctly, the first of the oopses was triggered by
"service apparmor reload", whilst the second was triggered by "aa-
enforce /usr/sbin/apache2".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: canonical-is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610111
Title:
apache2 restart problems
To manage notifications about this bug go to:
I'm seeing this on a trusty box on the latest linux-image-generic-lts-
xenial. In our case, it's with apache2 rather than dovecot. Is the
debug kernel applicable to trusty?
** Tags added: canonical-is
** Changed in: apparmor (Ubuntu)
Status: Incomplete => New
--
You received this bug
Here are some of the oopses we've seen:
https://pastebin.canonical.com/162419/
https://pastebin.canonical.com/162420/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581990
Title:
Profile reload
** Tags added: canonical-is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications about this bug go to:
Additional hosts have been added to ntp.ubuntu.com today, including an
additional IPv6 address.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/715141
Title:
Default NTP servers do not have
This is affecting operational systems now; we can no longer use wsgi &
mod_python in the same apache2 install, due to the following error:
[Tue Jul 12 04:04:14.655314 2016] [wsgi:crit] [pid 18069] mod_wsgi
(pid=18069): The mod_python module can not be used on conjunction with
mod_wsgi 4.0+.
Seen on a xenial daily image in Canonistack today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596638
Title:
python2 cannot import lsb_release on yakkety and now xenial
To manage notifications
We've also been running into this issue on ScalingStack instances
recently; I got this traceback which seems to strongly implicate nohz as
the problem area: https://pastebin.canonical.com/158640/ Presently
testing @pitti's workaround on a number of different sized instances to
confirm.
--
You
For posterity: If
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/comments/143
is the cause of this issue for you, dmesg -D (which turns off console
logging of kernel messages) might be a viable workaround until you can
reboot.
--
You received this bug notification because you are a
To any future readers of this bug: please do not add further comments
here; instead, paste the output of the following commands into
http://pastebin.ubuntu.com/:
- ip -6 address
- ip -6 route
- host security.ubuntu.com # [or nslookup/dig if you don't have bind9-host
installed]
- mtr -r -c 10 [a
@babybat and all future commenters on this bug: regarding any
connectivity issues to Ubuntu IPv6 addresses, please email r...@ubuntu.com
instead of adding comments to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@geoff-short Thanks!
@mvo (or whoever is looking at this on the Canonical side): Therefore,
this bug can be considered simply as a request to change the default
value to 2 hours or so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> Customizing the size of your /boot partition is already possible in
> ubiquity. This bug report is saying that the *default* size of the /boot
> partition is too small.
Has that changed since the release of utopic? Because when I installed
this laptop it was certainly not possible to do so and
@vorlon, perhaps it was not clear enough from previous comments on this
bug, but some of us *want* to be able to install more than 4 kernels for
testing purposes, and asking for a larger (or better yet, customisable)
/boot is a perfectly reasonable thing to do, especially given the sizes
we're
Public bug reported:
Load on the main Ubuntu archive servers is rather peakish, and tends to
create a traffic peak on our Internet links at fairly regular times each
day, preventing customers from accessing the archive. This impacts the
cloud archive mirrors using the ubuntu-repository-cache
@yadi: link-local only was the proposal by @andreserl (not RFC1918, or
its IPv6 equivalent, ULA), and that is completely doable. So is
detection of an isolated, but not link-local-only network. It's simple
- if there's no route in the local routing table to the destination, it
should be excluded
@yadi: link-local only was the proposal by @andreserl (not RFC1918, or
its IPv6 equivalent, ULA), and that is completely doable. So is
detection of an isolated, but not link-local-only network. It's simple
- if there's no route in the local routing table to the destination, it
should be excluded
@yadi Won't changing the limit from 10 to 25 just put off the problem
until later? As I understand it, the main reason this issue caused
problems is that squid attempts IPv6 connections from hosts without
global IPv6 connectivity.
--
You received this bug notification because you are a member
@yadi Won't changing the limit from 10 to 25 just put off the problem
until later? As I understand it, the main reason this issue caused
problems is that squid attempts IPv6 connections from hosts without
global IPv6 connectivity.
--
You received this bug notification because you are a member
This is still affecting us on 1.25.3.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
This is still affecting us on 1.25.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications about this
*** This bug is a duplicate of bug 1465050 ***
https://bugs.launchpad.net/bugs/1465050
** This bug has been marked a duplicate of bug 1465050
Size of /boot partition is too small
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've unmarked this as a duplicate of bug 1357093, because even if
automatically installed kernels are auto-purged, 256 MB is still only
enough space to install approximately 4 kernels. For those testing
different kernels in order to track down bugs, this isn't large enough.
** This bug is no
There are a number of bugs marked duplicates of this bug that really
aren't. The size of /boot is orthogonal to the issue of purging unused
kernels. 256 MB gives the ability to install approximately 4 kernels.
For some of us that's not enough, and we need to specify a larger /boot.
Shortly, I
I've just updated to the latest BIOS, and it now is reporting 3 memory
modules are inaccessible, so this is looking more like it's hardware-
related. I'll report back as soon as we've resolved the hardware
issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
That doesn't fix the missing kmod package on precise:
https://pastebin.canonical.com/144357/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515828
Title:
system lockup, console logs kernel BUG at
Hi Joseph,
Here's what happens when I try to install http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.3-wily/linux-
image-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb:
https://pastebin.canonical.com/144314/
Is there a specific repo which needs to be enabled in order to provide
kmod
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521103/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521106/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515828
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521109/+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/1515828
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521107/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515828
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521108/+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: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/452/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515828
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521104/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515828
apport information
** Tags added: apport-collected
** Description changed:
Reproducible by trying to do any non-trivial amount of I/O to one of the
installed SSDs, e.g.: dd if=/dev/sdb of=/dev/null bs=1024k
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521105/+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/1515828
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521110/+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/1515828
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1515828/+attachment/4521112/+files/WifiSyslog.txt
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515828
Title:
system lockup, console logs kernel BUG at /build/linux-lts-trusty-
It has happened every time I have run the dd example so far (and other
I/O such as rsyncing the Ubuntu archive into it). It happened on prior
kernels as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Those kernels don't appear to be precise-compatible, which is what this
machine is using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515828
Title:
system lockup, console logs kernel BUG at
Reoccurred; console log at https://pastebin.canonical.com/144181/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515828
Title:
system lockup, console logs kernel BUG at /build/linux-lts-trusty-
Console log available at https://pastebin.canonical.com/144076/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515828
Title:
system lockup, console logs kernel BUG at /build/linux-lts-trusty-
Public bug reported:
Reproducible by trying to do any non-trivial amount of I/O to one of the
installed SSDs, e.g.: dd if=/dev/sdb of=/dev/null bs=1024k
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.13.0-68-generic 3.13.0-68.111~precise1
ProcVersionSignature: Ubuntu
This crash occurred again today, again while playing full screen video
in Google Chrome. Here's the output of the requested commands:
G2ETA5WW (2.65 )
09/17/2015
** Changed in: xorg (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of
Affects at least vivid and wily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511911
Title:
Installer creates /boot partition which is too small
To manage notifications about this bug go to:
Public bug reported:
When installing with full disk encryption, the installer does not allow
customisation of the size of /boot, resulting in a partition which is
256 MB. This is too small to be functional for more than a few months
on current versions, and was the cause of one of my machines
I have upgraded my BIOS to 2.65 and will report back with any further
crashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509622
Title:
Xorg crash
To manage notifications about this bug go to:
Public bug reported:
This is the full apport data from the crash reported as bug #1507461.
It occurred whilst watching a full-screen Flash video in Google Chrome.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
1 - 100 of 166 matches
Mail list logo
