[Bug 1875475] Re: Unison from Ubuntu 20.04 is incompatible with Unison from Ubuntu 18.04, Windows or Mac OS X
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 Ubuntu 18.04, Windows or Mac OS X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unison/+bug/1875475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878115] Re: logged luks passwords
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 subiquity-curtin-install.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878115 Title: logged luks passwords To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1878115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492621] Re: Cannot start VMs without routable IPv4 address
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: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492621 Title: Cannot start VMs without routable IPv4 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1492621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788322] Re: Approximately every 2mins this is written to syslog - rsyslogd: action 'action 3' resumed (module 'builtin:omfile') [v8.32.0 try http://www.rsyslog.com/e/2359
@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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788322 Title: Approximately every 2mins this is written to syslog - rsyslogd: action 'action 3' resumed (module 'builtin:omfile') [v8.32.0 try http://www.rsyslog.com/e/2359 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1788322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758775] Re: DHCP-received NTP servers override the configuration of the NTP charm
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 DHCP client. I think the preferred solution would be for the charm to disable the DHCP client from modifying the NTP configuration by removing "ntp-servers" from the "request" entry in /etc/dhcp/dhclient.conf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758775 Title: DHCP-received NTP servers override the configuration of the NTP charm To manage notifications about this bug go to: https://bugs.launchpad.net/ntp-charm/+bug/1758775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838146] Re: ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on *.ntp.org
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):
root@ip-172-31-7-27:~# grep ubuntu /etc/ntp.conf
pool 0.ubuntu.pool.ntp.org iburst
pool 1.ubuntu.pool.ntp.org iburst
pool 2.ubuntu.pool.ntp.org iburst
pool 3.ubuntu.pool.ntp.org iburst
pool ntp.ubuntu.com
root@ip-172-31-7-27:~# awk '/ubuntu/ {print $2}' /etc/ntp.conf | xargs -n1 host
0.ubuntu.pool.ntp.org has address 142.147.92.5
0.ubuntu.pool.ntp.org has address 12.71.198.242
0.ubuntu.pool.ntp.org has address 45.76.244.193
0.ubuntu.pool.ntp.org has address 104.168.88.15
1.ubuntu.pool.ntp.org has address 27.124.125.252
1.ubuntu.pool.ntp.org has address 129.250.35.250
1.ubuntu.pool.ntp.org has address 129.250.35.251
1.ubuntu.pool.ntp.org has address 13.55.50.68
2.ubuntu.pool.ntp.org has address 144.48.166.166
2.ubuntu.pool.ntp.org has address 203.7.149.149
2.ubuntu.pool.ntp.org has address 103.38.120.36
2.ubuntu.pool.ntp.org has address 103.76.40.123
2.ubuntu.pool.ntp.org has IPv6 address 2404:cc80:166::166
2.ubuntu.pool.ntp.org has IPv6 address 2407:f100:4:1::3
2.ubuntu.pool.ntp.org has IPv6 address 2a00:fd80:::::ff2
2.ubuntu.pool.ntp.org has IPv6 address 2001:19f0:5801:1daa:5400:1ff:fe95:cf80
3.ubuntu.pool.ntp.org has address 220.158.215.20
3.ubuntu.pool.ntp.org has address 27.124.125.251
3.ubuntu.pool.ntp.org has address 103.38.120.36
3.ubuntu.pool.ntp.org has address 103.214.220.220
ntp.ubuntu.com has address 91.189.89.198
ntp.ubuntu.com has address 91.189.89.199
ntp.ubuntu.com has address 91.189.91.157
ntp.ubuntu.com has address 91.189.94.4
ntp.ubuntu.com has IPv6 address 2001:67c:1560:8003::c8
ntp.ubuntu.com has IPv6 address 2001:67c:1560:8003::c7
So for the stock configuration on released Ubuntu versions, this is
factually incorrect. Can you provide any further details to explain how
this is a problem?
** Changed in: ntp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838146
Title:
ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on
*.ntp.org
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1838146/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069543] Re: ntpd crashes when network interface goes down
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]: ./../lib/isc/unix/ifiter_getifaddrs.c:163: INSIST(ifa->ifa_name != ((void *)0)) failed Dec 6 00:25:53 s0lp3 ntpd[238439]: exiting (due to assertion failure) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069543 Title: ntpd crashes when network interface goes down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1069543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744072] Re: [MIR] Chrony in 18.04
** 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 to: https://bugs.launchpad.net/ntp-charm/+bug/1744072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797872] Re: ntpd keeps Soliciting pool server
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 the problem lies. # Check whether your system can resolve DNS names correctly: dig 0.ubuntu.pool.ntp.org # Check whether you can ask for time from these hosts: ntpdate -d 0.ubuntu.pool.ntp.org To run the above commands successfully, you'll need the dnsutils and ntpdate packages installed. Here's what a successful run might look like (abbreviated): https://pastebin.ubuntu.com/p/zmzgj4nrwS/ If the dig fails, you've got a problem with DNS resolution. Check for a broken local DNS resolver or upstream DNS server. If the dig succeeds but the ntpdate fails, you might have an outbound firewall blocking access or connection tracking problem in that firewall. If both of the above succeed, but NTP still fails, your problem is likely a firewall blocking outbound NTP access. The firewalls might be on your local machine, your local network, or your ISP's network (unfortunately, the last is more common that it should be). Other causes might be a local apparmor profile override which prevents ntpd from doing DNS lookups. Hope this helps you track it down! ** Changed in: ntp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797872 Title: ntpd keeps Soliciting pool server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1797872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744072] Re: [MIR] Chrony in 18.04
** 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 to: https://bugs.launchpad.net/ntp-charm/+bug/1744072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786146] Re: ceilometer meter_time_to_live has no effect if applied to existing mongodb database
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1786146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786146] [NEW] ceilometer meter_time_to_live has no effect if applied to existing mongodb database
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:
https://pastebin.canonical.com/p/4vJNXQgDNM/
https://docs.mongodb.com/manual/core/index-ttl/ states "If a non-TTL
single-field index already exists for a field, you cannot create a TTL
index on the same field ... To change a non-TTL single-field index to a
TTL index, you must drop the index first and recreate with the
expireAfterSeconds option."
This index was added in the fix for lp:1193906; however those commits
did so without taking into account the TTL index.
In the default configuration of ceilometer and ceilometer-charm, this
isn't a problem, because data is never expired. But because the manual
expiry of data is gated on whether TTL indexes are supported by the
mongodb version in use (see _is_natively_ttl_supported in
https://github.com/openstack/ceilometer/blob/e984f28b00e3a073c176f6435507f5bce1c82d30/ceilometer/storage/impl_mongodb.py),
positive TTLs can result in data not being expired correctly.
Ideally, the code should be updated to create a TTL index if it is
supported and a positive TTL is configured, and a non-TTL index if it is
not supported (mongodb versions before 2.2), or TTL is non-positive.
Because mongodb is a deprecated storage driver for ceilometer, this
isn't likely to be high priority or to be accepted by upstream, so I'll
document the workaround here:
- Check if there's a TTL index on mongodb:
myset:PRIMARY> use ceilometer
switched to db ceilometer
myset:PRIMARY> db.meter.getIndexes()
...
- If an index called "meter_ttl" is present, ceilometer has configured a
TTL index. Drop the non-TTL index:
myset:PRIMARY> db.meter.dropIndex("timestamp_idx")
Unfortunately, there's no indication in the mongodb documentation as to
what will happen if "timestamp_idx" is recreated (which ceilometer seems
to do on connection to mongodb). Hopefully the presence of the
"meter_ttl" index should prevent "timestamp_idx" from breaking an
existing TTL index, but I don't have any evidence to suggest one way or
the other yet.
** Affects: ceilometer (Ubuntu)
Importance: Undecided
Status: New
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1786146/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759787] Re: Very inaccurate TSC clocksource with kernel 4.13 on selected CPUs
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 4.13.0-38 or 4.13.0-39. -- 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 with kernel 4.13 on selected CPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759787] Re: Very inaccurate TSC clocksource with kernel 4.13 on selected CPUs
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 HP ProLiant DL380 Gen10 with kernel 4.13 + Very inaccurate TSC clocksource with kernel 4.13 on selected CPUs -- 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 with kernel 4.13 on selected CPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50093] Re: Some sysctls are ignored on boot
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416039] Re: Broken apparmor profile
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: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1416039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759787] Re: Very inaccurate TSC clocksource on HP ProLiant DL380 Gen10 with kernel 4.13
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759787] [NEW] Very inaccurate TSC clocksource on HP ProLiant DL380 Gen10 with kernel 4.13
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 kernels default to the TSC clocksource, which is supposed to be very reliable on Skylake-X CPUs. On 4.4 (linux-image-generic-lts- xenial) it works as expected; on 3.13 (trusty default kernel) it works a little worse, and on 4.13 (linux-image-generic-hwe-16.04) it is much worse. Today I switched 4.13 from the TSC clocksource to the HPET clocksource and it improved the situation dramatically. I've produced loopstats & peerstats graphs from NTP corresponding to the dates in the pastebin above and placed them at https://people.canonical.com/~paulgear/ntp/. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: User Name 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 27 18:26 seq crw-rw 1 root audio 116, 33 Mar 27 18:26 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [ 6280.259121] perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750 [10463.378558] perf: interrupt took too long (3133 > 3131), lowering kernel.perf_event_max_sample_rate to 63750 [32314.949747] perf: interrupt took too long (4000 > 3916), lowering kernel.perf_event_max_sample_rate to 5 [129804.100274] clocksource: Switched to clocksource hpet [132747.312089] perf: interrupt took too long (5004 > 5000), lowering kernel.perf_event_max_sample_rate to 39750 Date: Thu Mar 29 07:45:22 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0bda:0329 Realtek Semiconductor Corp. Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0424:2660 Standard Microsystems Corp. Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HPE ProLiant DL380 Gen10 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=b33fdcbd-a949-41a0-86d2-03d0c6808284 ro console=tty0 console=ttyS0,115200 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2018 dmi.bios.vendor: HPE dmi.bios.version: U30 dmi.board.name: ProLiant DL380 Gen10 dmi.board.vendor: HPE dmi.chassis.type: 23 dmi.chassis.vendor: HPE dmi.modalias: dmi:bvnHPE:bvrU30:bd02/15/2018:svnHPE:pnProLiantDL380Gen10:pvr:rvnHPE:rnProLiantDL380Gen10:rvr:cvnHPE:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL380 Gen10 dmi.sys.vendor: HPE ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty uec-images -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755070] Re: [18.04] apt update failed
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 deploy bionic cloud images and run apt updates on them, so my guess is that you're dealing with a local DNS override or troublesome transparent proxy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755070 Title: [18.04] apt update failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1755070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 715141] Re: Default NTP servers do not have AAAA records
@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 implementation, and (possibly) fear that the small number of IPv6 servers in the pool would be overwhelmed. IPv6 on all ntp.ubuntu.com servers is doable, but subject to Canonical IS work priorities. Best to drop us a ticket about this. -- 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 records To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/715141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754358] Re: Default Ubuntu configuration violates the ntp pool policy
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 violates the ntp pool policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1754358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754358] Re: Default Ubuntu configuration violates the ntp pool policy
@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 1.ubuntu.pool.ntp.org iburst maxsources 1 pool 2.ubuntu.pool.ntp.org iburst maxsources 1 pool 3.ubuntu.pool.ntp.org iburst maxsources 1 I personally don't feel that it's great to have a maximum of 4 hosts, but pool resources are very limited, and badly-behaved clients can cause massive problems [1], so I understand the restriction. Perhaps a config which would balance the requirements of v4-only, v6-only, and dual-stack hosts would be: pool 0.ubuntu.pool.ntp.org iburst maxsources 1 pool 1.ubuntu.pool.ntp.org iburst maxsources 1 pool 2.ubuntu.pool.ntp.org iburst maxsources 2 pool ntp.ubuntu.com iburst -- 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 violates the ntp pool policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1754358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744072] Re: [MIR] Chrony in 18.04
I've added initial support for chrony to the ntp charm: https://code.launchpad.net/~paulgear/ntp-charm/+git/ntp- charm/+merge/340780 Very lightly tested at present - nagios check known to be non-working, other features should work. It's available as cs:~paulgear/ntp if anyone would like to test: 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 -- 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 to: https://bugs.launchpad.net/ntp-charm/+bug/1744072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740407] Re: package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 failed to install/upgrade: EOF on stdin at conffile prompt
@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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740407 Title: package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 failed to install/upgrade: EOF on stdin at conffile prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1740407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744072] Re: [MIR] Chrony in 18.04
@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 progress to report. ** Changed in: ntp-charm Status: New => Triaged ** Changed in: ntp-charm Importance: Undecided => Medium -- 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 to: https://bugs.launchpad.net/ntp-charm/+bug/1744072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746860] Re: CPU Soft Lockup Causing Trusty (4.4.0-111-generic) to become unresponsive
** 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
- Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
+ 2) The version of the package you are using, via 'apt-cache policy
+ pkgname' or by checking in Software Center
+
+ linux-image-3.16.0-38-generic 3.16.0-38.52~14.04.1 (ksplice effective version
3.16.0-45-generic)
qemu-system 2.0.0+dfsg-2ubuntu1.36
3) What you expected to happen
The system should not have crashed
4) What happened instead
The system crashed and reported CPU soft lockup errors.
Hi,
we had a system lock up completely today, we noticed the following in the
logs:
[84070301.087602] BUG: soft lockup - CPU#1 stuck for 23s!
[qemu-system-x86:30908]
[84070301.271530] BUG: soft lockup - CPU#8 stuck for 22s! [khugepaged:238]
[84070314.314615] INFO: rcu_sched detected stalls on CPUs/tasks: { 0}
(detected by 19, t=150024 jiffies, g=8647354832, c=8647354831, q=0)
[84070341.072534] BUG: soft lockup - CPU#1 stuck for 22s!
[qemu-system-x86:30908]
** Summary changed:
- CPU Soft Lockup Causing Trusty (4.4.0-111-generic) to become unresponsive
+ CPU soft lockup causing trusty (3.16.0-38-generic) to become unresponsive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746860
Title:
CPU soft lockup causing trusty (3.16.0-38-generic) to become
unresponsive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746860/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1744072] Re: MIR Chrony in 18.04
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 modified to use chrony from 18.04 onward, > would that break it completely as chrony has no direct ntpdate > counterpart that I'd know of? > > [1]: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818 > Hi Christian, My current plan is to write a new reactive charm for chrony rather than trying to retrofit the ntp charm to support chrony. I would expect that the functionality which relies on ntpdate will drop out. I don't have a timeframe for this, however. Regards, Paul -- 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 to: https://bugs.launchpad.net/ntp-charm/+bug/1744072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649727] Re: No sound card detected with device: Intel Corporation Device 9d71
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738619] [NEW] VM fails to start after zesty to artful upgrade
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 shut off root@localhost:~# virsh start test error: Failed to start domain test error: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules. root@localhost:~# lsmod|grep kvm kvm 581632 0 irqbypass 16384 1 kvm root@localhost:~# dmesg|tail [ 29.757516] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 29.866191] Ebtables v2.0 registered [ 30.347237] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 30.350299] virbr0: port 1(virbr0-nic) entered blocking state [ 30.350302] virbr0: port 1(virbr0-nic) entered disabled state [ 30.350366] device virbr0-nic entered promiscuous mode [ 30.584263] nf_conntrack version 0.5.0 (65536 buckets, 262144 max) [ 30.695375] virbr0: port 1(virbr0-nic) entered blocking state [ 30.695379] virbr0: port 1(virbr0-nic) entered listening state [ 30.774039] virbr0: port 1(virbr0-nic) entered disabled state root@localhost:~# lsb_release -rd Description:Ubuntu 17.10 Release:17.10 Dec 17 21:02:18 localhost libvirtd[1513]: 2017-12-17 11:02:18.161+: 1682: error : qemuProcessStartValidate:4619 : unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Summary changed: - VMs fail to start after zesty to artful upgrade + VM fails to start after zesty to artful upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738619 Title: VM fails to start after zesty to artful upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1738619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737657] Re: Failure to be root is repored in a misleading message
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 addition, it's completely legitimate to run ntpdate as a non-root user in order to see the offset from a remote server without setting the time (see the man page for details on the -d option). ** Changed in: ntp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737657 Title: Failure to be root is repored in a misleading message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1737657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
@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 the remaining VMs did not restart reliably (failing on 2/3 reboots), and the last 2 failed on 3/3 reboots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
@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) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
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. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705988] Re: snap install --classic juju fails
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 --classic juju fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1705988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705988] Re: snap install --classic juju fails
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) in the creation of this bug report. :-) -- 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 --classic juju fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1705988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649727] Re: No sound card detected with device: Intel Corporation Device 9d71
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649727 Title: No sound card detected with device: Intel Corporation Device 9d71 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676635] Re: [Hyper-V] Implement Hyper-V PTP Source
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 Title: [Hyper-V] Implement Hyper-V PTP Source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241305] Re: security.ubuntu.com not accessible in IPv6 (AAAA record missing in the DNS)
** 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 by
+ both internal and 3rd party monitoring systems.
+
+ If you experience problems with IPv6 connectivity to the archive
+ servers, please DO NOT comment on this bug. Instead, email
+ r...@ubuntu.com explaining the problem, and include the output of the
+ following commands:
+
+ - date -u --rfc-3339=seconds
+ - ip -6 addr
+ - mtr -6 --report --no-dns -c 3 security.ubuntu.com
+ - host security.ubuntu.com # requires bind9-host to be installed
+ - ip -6 route get $(host security.ubuntu.com|awk '/has IPv6 address/ {print
$NF}') # also requires bind9-host to be installed
+
+ ---
+
Dear,
- The apt source list for security update is by default configured to
+ The apt source list for security update is by default configured to
security.ubuntu.com.
- When you have a system using only IPv6 (and having not access to IPv4 via
NAT-PT),
- security.ubuntu.com is only reachable in IPv4.
+ When you have a system using only IPv6 (and having not access to IPv4
+ via NAT-PT), security.ubuntu.com is only reachable in IPv4.
- It would be wise to configure an record to security.ubuntu.com to at
least
- point to one of the many mirrors supporting IPv6 connectivity.
+ It would be wise to configure an record to security.ubuntu.com to
+ at least point to one of the many mirrors supporting IPv6 connectivity.
- That would avoid system running natively in IPv6 to lack by default the
security
- update.
+ That would avoid system running natively in IPv6 to lack by default the
+ security update.
Thanks a lot,
Kind regards
- PS : I checked this as being a security vulnerability but this is more a
configuration issue
- on the Ubuntu network infrastructure than a real security vulnerability:
+ PS : I checked this as being a security vulnerability but this is more a
+ configuration issue on the Ubuntu network infrastructure than a real
+ security vulnerability:
A DNS request :
dig -t security.ubuntu.com
; <<>> DiG 9.4.1-P1 <<>> -t security.ubuntu.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26872
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;security.ubuntu.com. IN
;; AUTHORITY SECTION:
ubuntu.com. 3600IN SOA ns1.canonical.com.
hostmaster.canonical.com. 2008061805 10800 3600 604800 3600
;; Query time: 134 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jun 19 15:17:39 2008
;; MSG SIZE rcvd: 98
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/241305
Title:
security.ubuntu.com not accessible in IPv6 ( record missing in the
DNS)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-website/+bug/241305/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685397] [NEW] Profile Manager no longer works as documented
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 options simply open a blank window in the running Firefox instance. If there's no Firefox running, Profile Manager will display as normal, but this is no different to when Firefox is started without parameters. Expected behaviour: -ProfileManager or -P without a profile specified should open the Firefox Profile Manager regardless of whether a Firefox instance is running. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685397 Title: Profile Manager no longer works as documented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1685397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319195] Re: indicator-datetime set for 24 hours does not show 24 hour clock for "Other Locations"
@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: indicator-datetime set for 24 hours does not show 24 hour clock for "Other Locations" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1319195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319195] Re: indicator-datetime set for 24 hours does not show 24 hour clock for "Other Locations"
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" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1319195/+attachment/4836646/+files/Menu_001.png -- 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: indicator-datetime set for 24 hours does not show 24 hour clock for "Other Locations" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1319195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666345] Re: nagios-nrpe-server daemon stops responding
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666345 Title: nagios-nrpe-server daemon stops responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1666345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656801] Re: ntp: changing the default config from server to pool broke the dhcp hook
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656801 Title: ntp: changing the default config from server to pool broke the dhcp hook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1656801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656801] Re: ntp: changing the default config from server to pool broke the dhcp hook
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. https://bugs.launchpad.net/bugs/1656801 Title: ntp: changing the default config from server to pool broke the dhcp hook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1656801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656801] Re: ntp: changing the default config from server to pool broke the dhcp hook
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 removing those specified in /etc/ntp.conf. The patch would eliminate this option, and would allow only DHCP- specified servers OR /etc/ntp.conf servers, not both. Thus, my opinion is -1 for that patch as-is, and +1 for the upstream Debian version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656801 Title: ntp: changing the default config from server to pool broke the dhcp hook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1656801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
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 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610650] Re: can't sync sources
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610650 Title: can't sync sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1610650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652695] Re: GCE default NTP configuration uses both leap-smeared and true UTC sources
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 'server' rather than 'pool' for ntp.ubuntu.com, to ensure that it is included in the configuration at least once. ** Also affects: ntp (Ubuntu) Importance: Undecided Status: New ** Changed in: ntp (Ubuntu) Importance: Undecided => Low ** Changed in: cloud-images Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652695 Title: GCE default NTP configuration uses both leap-smeared and true UTC sources To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1652695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651707] Re: ntpd[1243]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
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 72.14.179.135 Directly after the last occurrence of the resolver failure, your ntpd resolved a large list of pool servers, including 5 within the same second as the error message. Without knowing your configuration, I'd guess this was a network- manager-initiated restart, and your resolver setup simply wasn't finished by the time ntpd was asking for DNS names. If you're using the default ntp configuration (or similar to it), this will not be a problem, because ntpd will retry the DNS lookups. ** Changed in: ntp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651707 Title: ntpd[1243]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1651707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581990] Re: Profile reload leads to kernel NULL pointer dereference
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. https://bugs.launchpad.net/bugs/1581990 Title: Profile reload leads to kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1581990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610111] Re: apache2 restart problems
** 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: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1610111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581990] Re: Profile reload leads to kernel NULL pointer dereference
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581990 Title: Profile reload leads to kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1581990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581990] Re: Profile reload leads to kernel NULL pointer dereference
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 leads to kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1581990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** 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: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 715141] Re: Default NTP servers do not have AAAA records
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 records To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/715141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1104339] Re: Move to mod_wsgi from mod_python as mod_python is deprecated
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+. Remove the mod_python module from the Apache configuration. ** Summary changed: - Move to mod_wsgi from mod_python as mod_python is depricated + Move to mod_wsgi from mod_python as mod_python is deprecated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1104339 Title: Move to mod_wsgi from mod_python as mod_python is deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache-openid/+bug/1104339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596638] Re: python2 cannot import lsb_release on yakkety and now xenial
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1596638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1531768] Re: [arm64] lockups when idle if tickless (nohz=on) is used
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] lockups when idle if tickless (nohz=on) is used To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable
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 working address] - mtr -r -c 10 [a non-working address] Then email r...@ubuntu.com using the subject "security.ubuntu.com unreachable via IPv6", and provide a link to your pastebin results. (If your problem relates to another site, please substitute its name for security.ubuntu.com in the email subject and mtr command above.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412943 Title: security.ubuntu.com (2001:67c:1562::XXX) not reachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1412943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241305] Re: security.ubuntu.com not accessible in IPv6 (AAAA record missing in the DNS)
@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. https://bugs.launchpad.net/bugs/241305 Title: security.ubuntu.com not accessible in IPv6 ( record missing in the DNS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-website/+bug/241305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554848] Re: Please randomise automatic updates over a longer period
@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. https://bugs.launchpad.net/bugs/1554848 Title: Please randomise automatic updates over a longer period To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465050] Re: Size of /boot partition is too small
> 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 still use LUKS encryption, without jumping over some fairly significant hurdles. >From memory, the workaround steps to get a larger /boot were: - create preferred partition setup using a server install ISO - boot using the desktop ISO - manually enable the encrypted LVM VG - run the installer and tell it to use the existing partition setup - boot from the server CD again, run recovery, and reconfigure the initrd to include encryption support There may have been an easier way to do this, but all the ways I tried based on the server ISO ended up with non-working graphics, and the desktop ISO resulted in a unbootable system due to missing encryption support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465050 Title: Size of /boot partition is too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1465050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465050] Re: Size of /boot partition is too small
@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 talking about relative to the size of modern hard disks. This bug was previously tagged as a duplicate of the lack of kernel autoremove, and but they're not the same thing, and should not be conflated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465050 Title: Size of /boot partition is too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1465050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554848] [NEW] Please randomise automatic updates over a longer period
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 charm also, because they are hitting a squid cache which is backed by the main archive. This effect will be even more pronounced under the recently- announced automatic update policy for xenial. One solution which would alleviate this to some extent would be to spread the load over a longer period by increasing the random sleep time in the daily update script from 30 minutes to, say, 1-2 hours. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554848 Title: Please randomise automatic updates over a longer period To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
@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 from attempts. This would work for both IPv4 and IPv6, regardless of the presence of NAT, because NAT still requires a route to the destination in order to function. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
@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 from attempts. This would work for both IPv4 and IPv6, regardless of the presence of NAT, because NAT still requires a route to the destination in order to function. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
@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 of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
@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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
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 bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511911] Re: Installer creates /boot partition which is too small
*** 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. https://bugs.launchpad.net/bugs/1511911 Title: Installer creates /boot partition which is too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1511911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465050] Re: Size of /boot partition is too small
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 longer a duplicate of bug 1357093 Kernels not autoremoving, causing out of space error on LVM or Encrypted install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465050 Title: Size of /boot partition is too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1465050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted install
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 intend to unmark 1465050 as a duplicate, and mark 1511911 as a duplicate of that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] Re: system lockup, console logs kernel BUG at /build/linux-lts-trusty-HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515828 Title: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] Re: system lockup, console logs kernel BUG at /build/linux-lts-trusty-HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310
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 /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] Re: system lockup, console logs kernel BUG at /build/linux-lts-trusty-HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310
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 for precise? According to http://packages.ubuntu.com/trusty/kmod it was not in the main archive before trusty. Regards, Paul -- 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- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] CurrentDmesg.txt
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. https://bugs.launchpad.net/bugs/1515828 Title: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] Lsusb.txt
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: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] ProcModules.txt
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 Title: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] ProcCpuinfo.txt
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 Title: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] ProcInterrupts.txt
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. https://bugs.launchpad.net/bugs/1515828 Title: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] UdevLog.txt
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: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] IwConfig.txt
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 Title: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] Re: system lockup, console logs kernel BUG at /build/linux-lts-trusty-HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310
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: linux-image-3.13.0-68-generic 3.13.0-68.111~precise1 ProcVersionSignature: Ubuntu 3.13.0-68.111~precise1-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 ApportVersion: 2.12-0ubuntu2~0.IS.12.04.1 Architecture: amd64 Date: Fri Nov 13 01:16:14 2015 MarkForUpload: True ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) + --- + AlsaDevices: + total 0 + crw-rw---T 1 root audio 116, 1 Nov 16 04:40 seq + crw-rw---T 1 root audio 116, 33 Nov 16 04:40 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.12-0ubuntu2~0.IS.12.04.1 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 12.04 + HibernationDevice: RESUME=UUID=dd29704b-6519-4acc-a914-839bd69f55ca + MachineType: HP ProLiant DL380p Gen8 + MarkForUpload: True + Package: linux-lts-trusty + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic root=UUID=26f87a1c-69ca-4830-84af-e934b0ec5283 ro console=tty0 console=ttyS1,38400 nosplash initrd=amd64/generic/precise/release/di-initrd BOOTIF=01-2c-44-fd-81-23-e8 quiet + ProcVersionSignature: Ubuntu 3.13.0-68.111~precise1-generic 3.13.11-ckt27 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-68-generic N/A + linux-backports-modules-3.13.0-68-generic N/A + linux-firmware 1.79.18 + RfKill: Error: [Errno 2] No such file or directory + Tags: precise uec-images + Uname: Linux 3.13.0-68-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm + dmi.bios.date: 09/22/2013 + dmi.bios.vendor: HP + dmi.bios.version: P70 + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrP70:bd09/22/2013:svnHP:pnProLiantDL380pGen8:pvr:cvnHP:ct23:cvr: + dmi.product.name: ProLiant DL380p Gen8 + dmi.sys.vendor: HP ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1515828/+attachment/4521102/+files/BootDmesg.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: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] Lspci.txt
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: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] UdevDb.txt
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: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] WifiSyslog.txt
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 to Ubuntu. https://bugs.launchpad.net/bugs/1515828 Title: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] Re: system lockup, console logs kernel BUG at /build/linux-lts-trusty-HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310
** 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- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] Re: system lockup, console logs kernel BUG at /build/linux-lts-trusty-HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310
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. https://bugs.launchpad.net/bugs/1515828 Title: system lockup, console logs kernel BUG at /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] Re: system lockup, console logs kernel BUG at /build/linux-lts-trusty-HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310
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 /build/linux-lts-trusty- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] Re: system lockup, console logs kernel BUG at /build/linux-lts-trusty-HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310
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- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] Re: system lockup, console logs kernel BUG at /build/linux-lts-trusty-HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310
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- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515828] [NEW] system lockup, console logs kernel BUG at /build/linux-lts-trusty-HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310
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 3.13.0-68.111~precise1-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 ApportVersion: 2.12-0ubuntu2~0.IS.12.04.1 Architecture: amd64 Date: Fri Nov 13 01:16:14 2015 MarkForUpload: True ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise third-party-packages uec-images -- 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- HlNG0J/linux-lts-trusty-3.13.0/kernel/hrtimer.c:1310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1515828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509622] Re: Xorg crash
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509622 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511911] Re: Installer creates /boot partition which is too small
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: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1511911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511911] [NEW] Installer creates /boot partition which is too small
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 failing to upgrade to wily (due to insufficient space in /boot). Please allow customising of the partition sizes when using an LVM + cryptsetup install. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- 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: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1511911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509622] Re: Xorg crash
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: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509622] [NEW] Xorg crash
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 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 24 18:04:11 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fa] MachineType: LENOVO CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/peleg0-lv01 ro splash quiet nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET33WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET33WW(1.13):bd07/24/2012:svnLENOVO:pnCTO:pvrThinkPadX230:rvnLENOVO:rnCTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Oct 24 17:58:31 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.2-1ubuntu9 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 crash ubuntu wily ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622/+attachment/4503887/+files/CurrentDmesg.txt -- 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: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
