I'm also seeing this on 16.04 systems with linux-generic-hwe-16.04
packaged kernel running. Will there be a ethtool update for 16.04 also?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750989
Title:
Dan, will you be building an updated xenial image from the contributed
patch or will only releases greater then 16.04 only have the fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Can we unmark this as "Incomplete"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To manage notifications about this bug go
Dan, could you also run these commands?? And purge all your boxes before
"vagrant up"?
vagrant ssh -- sudo grep ubuntu /etc/hosts
vagrant ssh -- sudo grep 127 /etc/hosts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
$ : vboxmanage --version
5.0.20r106931
$ : vagrant --version
Vagrant 1.8.0
$ : vagrant box list |grep -i xenial
$ : vagrant init ubuntu/xenial64
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the
Public bug reported:
I'm mirroring xenial amd64 packages with apt-mirror. When I attempt to
install xenial using the apt-mirror mirror, the installer fails after
not being able to grab i386 Release/Packages files.
** Affects: nsd (Ubuntu)
Importance: Undecided
Status: New
--
You r
Public bug reported:
I see that apt-mirror has been patch to get the files in dep-11
directory but the by-hash subdirectory isn't being mirrored or
generated.
** Affects: apt-mirror (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
How were precise and trusty images built? They worked fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To manage notific
** Also affects: cloud-images
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/1561250
Title:
Xenial vagrant image is missing its hostname in /etc/hosts
To
Public bug reported:
The sources file is being written incorrectly during the preseed
process. Its failing to prefix the last line in the sources.list file
with "deb ".
This is what we have in our preseed for xenial
# Aptly Mirror / Custom Packages
d-i apt-setup/local0/repository string deb
htt
Public bug reported:
The vagrant build for xenial is missing an in /etc/hosts. This generates
an error when running sudo.
ubuntu@ubuntu-xenial:~$ cat /etc/hosts
127.0.0.1 localhost
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00
I'm also having to add an optical drive now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546108
Title:
Latest Vagrant box for Ubuntu Xenial is failing to boot
To manage notifications about this
The 20160218.4 build still has the problem (http://cloud-
images.ubuntu.com/xenial/20160218.4/xenial-server-cloudimg-
amd64-vagrant.box)
I don't see or can't get to the grub menu with any key combo as imiciik
posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I've noticed the same thing since 20160205 if that helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546108
Title:
Latest Vagrant box for Ubuntu Xenial is failing to boot
To manage notification
Will we see this backported to precise or trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500218
Title:
Please backport on 4.2 : Important fix for tcp kernel
To manage notifications about th
I have this problem from a fresh install of 13.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1130326
Title:
No Certificate Authority Certificate Dialog doesn't receive focus
To manage notificati
Public bug reported:
Got this error when install broadcom-sta-dkms. Just recently upgraded
from 12.10.
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: broadcom-sta-dkms 5.100.82.112-9
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersi
I'm still affected by this. I'm using version 9.7.0.dfsg.P1-1ubuntu0.8
of the bind9 package. From the hosts listed above I'm still seeing it
for these hosts:
zidvox.com
edadfs.partners.extranet.microsoft.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- I can't use the service/stop/start command for procps anymore when
+ I can't use the "service procps start" command for procps anymore when
running with precise. This does work in lucid.
user@hosta:~$ sudo bash
root@hosta:~# service procps start
start: Job fail
Public bug reported:
I can't use the service/stop/start command for procps anymore when
running with precise. This does work in lucid.
user@hosta:~$ sudo bash
root@hosta:~# service procps start
start: Job failed to start
root@hosta:~# service procps stop
stop: Unknown instance:
root@hosta:~# serv
And another
puppet:~$ gdb -q -c core.2-6-12-00 /usr/lib/postgresql/8.4/bin/postgres
Reading symbols from /usr/lib/postgresql/8.4/bin/postgres...Reading symbols
from /usr/lib/debug/usr/lib/postgresql/8.4/bin/postgres...done.
done.
[New Thread 14948]
warning: Can't read pathname for load map: Inpu
postgres segfaulted again. Here is the backtrace from the second
coredump.
puppet:~$ gdb -q -c core.db8.2-2-12 /usr/lib/postgresql/8.4/bin/postgres
Reading symbols from /usr/lib/postgresql/8.4/bin/postgres...Reading symbols
from /usr/lib/debug/usr/lib/postgresql/8.4/bin/postgres...done.
done.
[
Public bug reported:
Postgres will occasionall segfault every few weeks. I was able to get a
core dump and get a backstrace. I'm running postgres-8.4 version
8.4.9-0ubuntu0.10.04 .
puppet:~$ gdb /usr/lib/postgresql/8.4/bin/postgres core
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Fo
** Attachment added: "kernel panic msg, dmesg adter reboot, lspci output"
https://bugs.launchpad.net/bugs/623211/+attachment/1515037/+files/systeminfo.log.txt
--
kernel panic - at /build/buildd/linux-2.6.28/kernel/smp.c:333
smp_call_function_mask+0x21a/0x220()
https://bugs.launchpad.net/bug
Public bug reported:
This is the second time this has happened this week. I've attached the
requested info and kernel panic message.
Normally this box is serving video files via nginx.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
kernel panic - at /build/build
Public bug reported:
Binary package hint: logrotate
Description:Ubuntu 8.10
Release:8.10
apt-cache policy logrotate
logrotate:
Installed: 3.7.1-5ubuntu1
Candidate: 3.7.1-5ubuntu1
Version table:
*** 3.7.1-5ubuntu1 0
100 /var/lib/dpkg/status
Also recompiled/packaged lo
26 matches
Mail list logo
