Additional info: in my case, the cause of the file going missing is
something to do with incus image publishing. Details:
https://discuss.linuxcontainers.org/t/file-goes-missing-during-image-
publish-usr-lib-x86-64-linux-gnu-dhcpcd-dev-udev-so/19969
--
You received this bug notification because
I am getting the same error with Ubuntu 24.04, but a different file from
dhcpcd-base was missing.
With set -x in /usr/share/initramfs-tools/hooks/dhcpcd:
...
+ grep ^dhcpcd: /etc/passwd
+ ldd /usr/sbin/dhcpcd
+ sed -En s;^.*/lib(/lib[^/]*prof)?/([^/]+)/libc\.so\..*$;\2;p
+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693361
Title:
cloud-init sometimes fails on dpkg lock due to concurrent apt-
daily.service execution
To manage notifications about this bug go to:
Should have said: available in Ubuntu since 21.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805625
Title:
wpasupplicant package does not include eapol_test
To manage notifications about this
Update: it looks like Debian made a separate package "eapoltest" and
this has been available in Ubuntu since 20.10.
Unfortunately it did not arrive in time for 20.04, and the hirsute package
requires a newer libc so can't be installed on focal - you still have to build
yourself.
> thanks for the explanations, I would have never thought that the small
black triangle was something clickable.
Me neither. Bug 1742101 is now dealing with this usability issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's at the top of the body of the mail, just below the screenshot you
showed:
|> (Person Name) has invited you to (Meeting Name)
There is a small black triangle next to "Person Name". The usability
bug is that it shouldn't be necessary to point this out :-)
--
You received this bug
I didn't realise until now that the event details were folded away, and
became visible if the arrow is clicked. Thank you, this is awesome! It
would be more awesome if it was open by default - but I don't know if
this is Thunderbird's rendering of an ics file, or something controlled
by
** Summary changed:
- socat bug with SSL "filte transfers"
+ socat bug with SSL "file transfers"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936407
Title:
socat bug with SSL "file transfers"
In the socat git repository, if you diff tag 1.7.4.0 to 1.7.4.1, you see
this:
+Corrections:
+ Socat 1.7.4.0 failed to compile especially on 32 bit systems.
+ Thanks to Wang Mingyu and others for sending a patch or reporting this
+ issue.
+
+ Under certain conditions
The snap package isn't compatible with the version from macOS homebrew
either.
In the end, I just went with the binary tarballs available from
https://github.com/bcpierce00/unison/releases
The reason for these incompatibilities is described here:
Public bug reported:
In Ubuntu 20.04 (kernel 5.4.0), the /dev/md directory which contains
/dev/md/ links apparently no longer exists.
# ls -l /dev/md*
brw-rw 1 root disk 9, 127 Mar 31 08:46 /dev/md127
#
Compare to an 18.04 system:
$ ls -l /dev/md*
brw-rw 1 root disk 9, 0 Mar 26 08:01
Correction: the "Failed to connect..." message appears on stdout anyway,
so it *does* persist.
So as a second change, I suggest that /usr/lib/ubuntu-release-upgrader
/release-upgrade-motd should capture the stderr as well, by adding
"2>&1" before "&"
--
You received this bug notification
I am also getting this with 18.04.5 LTS. In /etc/apt/apt.conf.d/99proxy
I have:
Acquire::http::Proxy "http://127.0.0.1:3142/;;
Acquire::https::Proxy "DIRECT";
and sometimes the the motd displays
proxy 'DIRECT' looks invalid
I have discovered why it's intermittent: that text is the *stderr*
Seeing this on bare metal (Dell R740xd) with Ubuntu 18.04 and linux-
image-generic-hwe-18.04 (5.3.0-62-generic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820063
Title:
[Hyper-V] KVP daemon
SNMP data collection is also broken in the Ubuntu 18.04 cacti package
https://github.com/Cacti/cacti/issues/1634
https://github.com/Cacti/cacti/commit/32f1538a4a382b7b27e2340705e9b034f335ae6e
https://github.com/Cacti/cacti/commit/afa01553f574554f782bbed3d2f1efaa355df2d0
Public bug reported:
rsyslog has a parser module for Cisco IOS formatted syslog messages:
https://www.rsyslog.com/doc/master/configuration/modules/pmciscoios.html
https://github.com/rsyslog/rsyslog/tree/master/plugins/pmciscoios
It has been in rsyslog since early days (8.3.4); Bionic has 8.16.0.
*** This bug is a duplicate of bug 1641236 ***
https://bugs.launchpad.net/bugs/1641236
I believe this bug has been wrongly marked as a duplicate of #1641236.
I described in the second paragraph of the bug report why this is *not*
a duplicate.
#1641236 is when lxc exec passes an open pty from
Public bug reported:
wpasupplicant comes with an auxiliary program, eapol_test, but it is not
included in the Ubuntu wpasupplicant package. I'd like to request that
it be added.
It's very useful for testing wifi RADIUS servers: e.g. you can call it
from a Nagios check script where you want to
Yes, it worked - as soon as the new packages were installed. Thank you!
root@bionic:~# ls
libvirt-bin_4.0.0-1ubuntu8.7~ppa2_amd64.deb
libvirt-clients_4.0.0-1ubuntu8.7~ppa2_amd64.deb
libvirt-daemon-driver-storage-rbd_4.0.0-1ubuntu8.7~ppa2_amd64.deb
Sorry, but I still think it's a bug.
The reason is that "brctl setfd ..." works fine in an unprivileged
container, but libvirt-daemon fails. In other words: brctl shows that
it *is* possible to create and manage bridges in an unprivileged
container, but libvirt-daemon isn't doing it correctly.
Public bug reported:
Ubuntu 18.04 lxd container, running on Ubuntu 18.04 host (kernel
4.15.0-38-generic)
Inside the container, I installed libvirt-bin. However it fails to
start the predefined 'default' network:
root@bionic:/etc# virsh net-start default
error: Failed to start network default
> How can I make this bridge come up at boot without assigning an IP
address?
See the link earlier in this thread:
http://djanotes.blogspot.com/2018/04/anonymous-bridges-in-netplan.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Excellent, thank you. FYI, the actual application I'm using which
requires nbd is snf-image-creator.
I agree it makes sense to remove most modules relating to physical
hardware from the kvm kernel, but loopback and networking modules are
useful.
I did a quick diff. "rbd" might be another one to
Public bug reported:
The "nbd" module is missing from linux-modules-XXX-kvm in bionic
root@ubuntu:~# /sbin/modprobe nbd max_part=16
modprobe: FATAL: Module nbd not found in directory /lib/modules/4.15.0-1021-kvm
root@ubuntu:~# uname -a
Linux ubuntu 4.15.0-1021-kvm #21-Ubuntu SMP Tue Aug 28
Thank you. It looks like it was fixed in 16.04:
# dpkg-query -L apache2-bin | grep mod_xml
/usr/lib/apache2/modules/mod_xml2enc.so
The dependency isn't automatic in 16.04:
# a2enmod proxy_html
Considering dependency proxy for proxy_html:
Enabling module proxy.
Enabling module proxy_html.
To
Awesome, thanks again!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630946
Title:
ubuntu-server depends on open-iscsi and runs iscsid
To manage notifications about this bug go to:
> no matter if we succeed/fail there one can at least later remove open-
iscsid if he wants without taking out the ubuntu-server meta.
That's perfect - thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Workaround:
systemctl stop iscsid
systemctl disable iscsid
... but I still object to not being able to remove it without also
removing ubuntu-server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> So I wonder is this "just" a conflict between how libvirt expects
pools to be set up (and as it does by itself) vs the manual set up one?
(1) If libvirt is only supposed to work with a top-level pool, then it
should have refused to allow me to create a libvirt pool with a slash in
the zfs pool
I checked libvirt HEAD and the code's the same there:
src/storage/storage_backend_zfs.c
cmd = virCommandNewArgList(ZPOOL,
"get", "-Hp",
"health,size,free,allocated",
def->source.name,
> if that worked for you before or not
Did this work in ubuntu 16.04 you mean? No it didn't; I was able to
create the the libvirt zfs pool via virsh, and virt-manager would show
that the pool existed, but not any volumes within it.
--
You received this bug notification because you are a member
I looked in both 4.0.0 and HEAD source, and the call to zpool uses
def->source.name. I think it would work fine if it stripped out
everything from the first slash.
(Aside: if the zpool command fails, virStorageBackendZFSRefreshPool()
just goes straight to cleanup and returns zero, as if nothing
And using strace on libvirtd, I see it's running this:
[pid 5806] execve("/sbin/zpool", ["/sbin/zpool", "get", "-Hp",
"health,size,free,allocated", "zfs/images"], 0x7fffedc8b6c8 /* 6 vars
*/) = 0
Which is not a valid command:
root@beaver:~# /sbin/zpool get -Hp health,size,free,allocated
Aha, good thinking about reproducing with virsh. To find out what virt-
manager is doing, I did:
LIBVIRT_DEBUG=1 virt-manager --no-fork
Clicking the refresh button shows me it's doing "virStoragePoolRefresh", which
takes me to
ftp://libvirt.org/libvirt/virshcmdref/html/sect-pool-refresh.html
Public bug reported:
How to replicate:
1. Install libvirt, libvirt-daemon-driver-storage-zfs and virt-manager
2. Create a zfs pool
# zpool create -oashift=12 zfs /dev/sdb
# zfs set compression=lz4 zfs
# zfs create zfs/images
# virsh pool-define-as --name zfs --source-name zfs/images --type zfs
Ah right: I had not installed libvirt-daemon-driver-storage-zfs. Doing
so has added the ability to virsh and virt-manager to create zfs pools
and volumes. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In Ubuntu 16.04 it was possible to create zfs pools in libvirt. But
this no longer works in 18.04:
# zpool create -oashift=12 zfs /dev/sdb
# zfs set compression=lz4 zfs
# zfs create zfs/images
# virsh pool-define-as --name zfs --source-name zfs/images --type zfs
error:
Having to build the module yourself from source is not a proper
solution. This module should be pre-built and included with apache2 (or
in a separate package).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
P.S. Changelogs for 4.0.0 alpha3, beta1, rc2 and release are here:
https://doc.powerdns.com/authoritative/changelog/4.0.html#powerdns-authoritative-server-4-0-0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
PDNS 4.0.0-alpha2 in Xenial is horribly broken(*) so IMO it seems a bit
of a waste of effort backporting this specific fix, without also
backporting the critical fixes from 4.0.0 alpha 3 and later, which in
turn would be best done by going straight to 4.0.0 release (or 4.0.4+)
PDNS is a fine
Just doing an "apt-get dist-upgrade" on a 16.04 VM:
...
Setting up grub-common (2.02~beta2-36ubuntu3.11) ...
Installing new version of config file /etc/grub.d/10_linux ...
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
Setting up grub-pc-bin
2.2.5 in xenial crashes for me. Building 2.2.6 from source on xenial,
it works.
+1 for backport; the package is currently not usable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1562333
Title:
After upgrading to lxcfs/xenial-proposed (2.0.7-0ubuntu1~16.04.2), the
problem is fixed for me
Inside a container:
root@apt-cacher:~# ps auxwww | grep apt
apt-cac+ 309 0.0 0.7 653476 7128 ?Ssl Jul08 1:02
/usr/sbin/apt-cacher-ng SocketPath=/run/apt-cacher-ng/socket -c
Public bug reported:
Inside a 16.04 lxd container (running in default unprivileged mode),
inside a 16.04 host:
# /etc/cron.daily/mdadm
Segmentation fault (core dumped)
# strace -f /sbin/mdadm --monitor --scan --oneshot
...
brk(0x1ba1000) = 0x1ba1000
I guess this also makes 1.8.16-0ubuntu1.3 a "security" update, since
sudo+sssd now enforces policy which it should have done before, but
didn't.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688034
I found out how to enable debugging for sudoers:
Debug sudo /var/log/sudo-debug all@info
Debug sudoers.so /var/log/sudoers-debug all@info
With the *new* sudo I get the following logged matching 'sssd':
May 5 12:40:06 sudo[17912] sssd/ldap sudoHost 'ALL' ... MATCH!
May 5 12:40:06 sudo[17912]
Now trying with @debug instead of @info
Slight munging of output to make it diffable, then diff -u:
--- v1.debug.trim 2017-05-03 20:28:07.78400 +
+++ v2.debug.trim 2017-05-03 20:28:14.03200 +
@@ -38,87 +38,6 @@
-> parse_args @
Some additional info.
I enabled sudo debugging by creating /etc/sudo.conf containing:
Debug sudo /var/log/sudo-debug all@info
Debug sudoers /var/log/sudoers-debug all@info
With the newer (non-functioning) sudo, /var/log/sudo-debug contains:
May 3 18:55:50 sudo[8003] comparing dev 34817 to
Public bug reported:
ubuntu 16.04, enrolled with freeipa-client to FreeIPA 4.4.0 (under
CentOS 7)
With sudo 1.8.16-0ubuntu1, everything is fine:
brian.candler@api-dev:~$ sudo -s
[sudo] password for brian.candler:
root@api-dev:~#
After update to 1.8.16-0ubuntu1.3, it no longer works:
WORKAROUND: if the other application which needs to bind to a UDP port
can be configured to bind to a specific interface, then you can make
isc-dhcp-server bind to a different interface in dhcpd.conf. e.g.
ddns-local-address4 127.0.0.1;
ddns-local-address6 ::1;
--
You received this bug
strace shows that dhcpd is binding to explicit ports which it has chosen
itself:
setsockopt(20, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
setsockopt(20, SOL_IP, IP_MTU_DISCOVER, [0], 4) = 0
getsockopt(20, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
setsockopt(20, SOL_IP, IP_RECVTOS, [1], 4) = 0
Public bug reported:
When isc-dhcp-server starts up, in addition to listening on port 67, it
binds to a random UDP port on an IPv4 socket and another on an IPv6
socket:
# netstat -naup | grep dhcp
udp0 0 0.0.0.0:11075 0.0.0.0:*
8188/dhcpd
udp
Public bug reported:
[ubuntu 16.04, lxd 2.0.8 or 2.0.9, tcpdump 4.7.4 or 4.9.0]
If you ssh into an lxd container as a normal user, and inside that
container run "sudo tcpdump", the tcpdump process is blocked from
writing to stdout/stderr. This appears to be due to apparmor:
disabling apparmor
It has been pointed out to me that if you combine "vlan-raw-device" with
"pre-up" then you have a complete workaround:
-
auto eno1.100
iface eno1.100 inet manual
vlan-raw-device eno1
auto br100
iface br100 inet manual
bridge_ports eno1.100
bridge_stp off
bridge_fd 0
bridge_maxwait
To avoid the patch in #7, you can set vlan-raw-device explicitly:
-
auto eno1.100
iface eno1.100 inet manual
vlan-raw-device eno1
-
Note that if you link this to a bridge, then bringing up the bridge
doesn't bring up the vlan bridge ports:
-
auto eno1.100
iface eno1.100 inet
Rather than backporting slirp fixes from 2.7.0 to 2.5.0, how about qemu
2.7 or 2.8 in backports?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226
Title:
segfault in qemu-system-x86_64
To
> client install expects ntpd to be present
I'm not quite sure what you mean.
"freeipa-client --install" does indeed give NTP errors, but it still
proceeds. Here is a transcript of installing freeipa-client inside a
(privileged) 16.04 lxd container.
root@unifi:~# apt-get install freeipa-client
With the same nodes fully updated (kernel 4.4.0-53, lxd 2.0.8, criu
2.6-1ubuntu1~ubuntu16.04.2), I find that live migration now works - yay!
Note: this is only if I don't change the container name. If I do (e.g.
"lxc move sample nuc1:foobar") then I get:
error: migration restore failed
BTW, I reproduced the same problem in a different (and arguably more
realistic) scenario:
- install ubuntu 16.04
- configure networking with a bridge interface but a port member that doesn't
exist when you next boot up (e.g. make br0 with a member which is a USB
ethernet adapter, and then
nts if ifm->ifq_so != NULL. When freeing a socket, we thus need
to make sure that any pending message for this socket does not refer
to the socket any more.
Signed-off-by: Samuel Thibault <samuel.thiba...@ens-lyon.org>
Tested-by: Brian Candler <b.cand...@pobox.com>
Workaround is to use IPv4/NAT networking instead of link-local
IPv6/http_proxy.
1. configure your lxdbr0 network with (private) IPv4 addresses and DHCP
pool in /etc/default/lxd-bridge. Also set LXD_IPV4_NAT="true" and
LXD_IPV6_PROXY="false". Restart.
2. "lxc profile edit default" to no longer
Sorry about this - the repo was open at the time I posted but is
currently closed for layer 9 reasons. I am trying to get permission to
release this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI, update:
- I have upgraded my Mac Mini to 16.04 (plus qemu 2.7.0 from source)
- I have completely replaced the RAM in my Mac Mini
- I have replicated on someone else's Mac Mini with 16.04
I can still replicate the new segfault/libc problems, so I'm sure that
it's not a hardware issue.
The
"the client setup would fail if there's no ntp installed"
In what way?
Is what you're really saying that the client setup would fail if the
clock of the client is not within X seconds of the real time? That's
correct, but is not the same as saying ntp must be installed.
There are other ways of
Public bug reported:
ubuntu-server has a hard dependency on open-iscsi, which means there is
a daemon running (iscsid), and the package cannot be removed. All
unnecessary daemons are a cause of concern when auditing a system.
Propose moving this to "Recommends" instead, which currently has:
Or maybe what's needed is a virtual package called e.g. "synchronized-
time", which freeipa-client depends on and is provided by ntp.
Then you could install a dummy package inside the container, which also
provides "synchronized-time"
--
You received this bug notification because you are a
Public bug reported:
[Note: the package is called "freeipa-client" but launchpad only lets me
select "freeipa"]
The "freeipa-client" package has a hard dependency on "ntp".
However: when running Ubuntu inside an lxd container, ntpd cannot run:
the host is responsible for setting the clock, not
I found that when I have
[ "-smp", "8,sockets=1,cores=4,threads=2" ],
in packer_files/vtp.json, the build completes successfully on my 14.04
Mac Mini with qemu 2.7.0. It worked several times flawlessly.
But if I remove that line (so that only one CPU is emulated by KVM) then
I get
> how can we reproduce this? Can you give a precise set of steps to
download/build an image and run qemu with it?
(1) The first issue - segfault in slirp/tcp_output.c - which is also
this one:
https://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg03636.html
You can reproduce using the
I have now tried this on someone else's Mac Mini, this one running
16.04.1.
With the stock qemu (1:2.5+dfsg-5ubuntu10.5), it crashes in apparently
the same way as mine was doing originally:
Oct 5 14:59:49 s1 kernel: [3982196.302758] qemu-system-x86[20590]:
segfault at 55fc165caa20 ip
Hmm, a different malloc-type error on next run:
Program received signal SIGABRT, Aborted.
0x7f7b20acbc37 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x7f7b20acbc37 in
*** This bug is a duplicate of bug 1630226 ***
https://bugs.launchpad.net/bugs/1630226
Hmm, a different malloc-type error on next run:
Program received signal SIGABRT, Aborted.
0x7f7b20acbc37 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56
For comparison I built qemu-2.5.1.1 from the release tarball at
http://wiki.qemu.org/Download, using the same configure options. (I
picked that one as being closest to what's in xenial)
And it crashes in exactly the same place:
Program received signal SIGSEGV, Segmentation fault.
tcp_output
It depends on a ton of libraries (literally):
$ ldd /usr/bin/qemu-system-x86_64 | wc -l
100
But using the dev packages I already had around, plus libfdt-dev which
it insisted on, I have done the following:
apt-get source qemu-system-x86
cd qemu-2.0.0+dfsg
./configure --disable-strip
I installed some more *-dbg and *-devel packages (including
libstdc++6-4.8-dbg), and now the backtrace is marginally more helpful -
although possibly this is a different trace?
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f95f3fff700 (LWP 10149)]
Attaching gdb to a running process gives the same result as I got from
the core dump.
(gdb) cont
Continuing.
[Thread 0x7f2877cfe700 (LWP 10805) exited]
[Thread 0x7f2876cfc700 (LWP 10816) exited]
[Thread 0x7f28774fd700 (LWP 10815) exited]
[Thread 0x7f2c015ff700 (LWP 10735) exited]
[Thread
Public bug reported:
[Ubuntu 14.04 amd64 server, fully patched, xenial HWE kernel, on a 16GB
Mac Mini]
I am using packer (www.packer.io) to create a VM image. Packer starts a
qemu-system-x86_64 process; inside it's running an ubuntu 16.04 image
doing a bunch of work including running ansible to
Public bug reported:
[Ubuntu 14.04 amd64 server, fully patched, xenial HWE kernel, on a 16GB
Mac Mini]
I am using packer (www.packer.io) to create a VM image. Packer starts a
qemu-system-x86_64 process; inside it's running an ubuntu 16.04 image
doing a bunch of work including running ansible to
I have two Precise (12.04) servers with
Unattended-Upgrade::Remove-Unused-Dependencies "true";
in 50unattended-upgrades. One of them cleans up its kernels and only
keeps the last two; one of them accumulates kernels over time, and I
occasionally get alerts about /boot filling up.
On the latter
> The user would already have setup in the BIOS menu to either be in
UEFI or BIOS mode prior to installation. This would also be user error.
Really? What's wrong with:
- buy computer
- plug in USB stick
- boot it up
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1609475 ***
https://bugs.launchpad.net/bugs/1609475
"Comment here only if you think the duplicate status is wrong."
Yes, I think the duplicate status is wrong.
Issue 1. The installer could be more helpful when dealing with UEFI
versus Legacy mode installs.
Let me try one last time to separate the issues.
** The UEFI issue (a side issue)
The installer works in two completely different ways, depending on
whether the system booted via UEFI or BIOS. But it does not show whether
it is installing in UEFI or BIOS mode. Hence the user has little way,
Not sure about tag "bios-outdated-0055". The latest BIOS for this machine is
0055: see
https://downloadcenter.intel.com/product/85254/Intel-NUC-Kit-NUC5CPYH
As for live CD: no, it can't be reproduced that way. The specific
sequence is:
* Boot from USB in UEFI mode
* Repartition the disk, but
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735776/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735775/+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/1609475
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735771/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735772/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735778/+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/1609475
Title:
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735770/+files/Card0.Codecs.codec.2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735773/+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/1609475
Title:
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735774/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735779/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735769/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735768/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735777/+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/1609475
apport information
** Tags added: apport-collected
** Description changed:
Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
machines (with 8GB RAM and Crucial BX200 SSD).
There is a problem running on this machine, but the problem report here
is specifically about how
The second issue (not matching predictable NIC names) is #1541678
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519120
Title:
NetworkManager VLAN support fails unless vlan package is manually
Separate issue #1609715 raised about installer continuing with UEFI
installation even if there is no ESP.
This specific hardware is now working fine.
I would still like recovery mode to be more predictable in the event of
startup problems: after all, the whole point of recovery mode is for
when
Caught by this too. I get enp3s0, and have set net.ifnames=0 as a
workaround.
I agree with the suggestion that the script should be simplified to
match .N, where X is any alphanumeric. More conservatively: the
first X could match a-z only, and the last X could match 0-9 only.
Question is,
1 - 100 of 337 matches
Mail list logo
