Public bug reported:
On Focal, Vagrant cannot connect to a new VM I tried to create (using
debian/bookworm64).
`vagrant up my-bookworm-vm` keeps repeating:
"Warning: Authentication failure. Retrying..."
`vagrant ssh my-bookworm-vm` however works!
The reason is that public-key authentication
This was fixed in Debian already 11 months ago.
https://salsa.debian.org/toolchain-
team/gcc/-/commit/6e463cee022ffb5544fe6833fe1ad4e40d2adeb5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922711
** Patch added: "Fixed version of pr87808.diff that initializes the path
structure."
https://bugs.launchpad.net/ubuntu/+source/gcc-8/+bug/1922711/+attachment/5484746/+files/pr87808.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This crash is introduced by patch pr87808.diff:
[...]
+#ifdef FALLBACK_GCC_EXEC_PREFIX
+ if (gcc_driver_file == NULL && ::getenv ("GCC_EXEC_PREFIX") == NULL)
+{
+ struct path_prefix path;
+
+ prefix_from_env ("PATH", );
[...]
"path" is used uninitialized.
--
You received this
Public bug reported:
This test case (taken from Emacs autoconfig, "gcc-8 -o conftest -g3 -O2
conftest.c -lgccjit") randomly segfaults on Ubuntu 18.04.
christian@christian-homeoffice:~/Software/src$ ./conftest
christian@christian-homeoffice:~/Software/src$ ./conftest
Public bug reported:
(This is on xenial, but I've had similar problems on bionic as well).
The docker.io package was updated last night (via unattended-upgrades),
and this morning I could no longer start containers, the error message
being:
docker: Error response from daemon: failed to
I would still consider it a bug. AFAIK this is the correct way to bind
an interface to multiple addresses. It is explictly mentioned in
interfaces (5).
My "workaround" of removing the second address only works because I no
longer have a need for it at this time.
--
You received this bug
I have now removed the second address stanza from the interfaces file,
and the dns settings work again.
I am no longer sure the machine was in fact rebooted with these settings
in place, since my logs only reach back to the start of april (the
interfaces file was last changed in august of last
Public bug reported:
Since a recent reboot (00:00 CEST on tuesday to be precise), DNS
settings from the interfaces file are no longer present in resolvconf. A
file /run/resolvconf/interface/eth0.inet exists but is empty.
This is happening on a xenial system. I have since rebooted once more,
with
I believe the error that I ran into was caused by inadvertently
compiling with "-m32" without having linux-libc-dev:i386 installed, in
which case the preprocessor somehow falls through to including the
broken /usr/include/linux/errno.h
--
You received this bug notification because you are a
Public bug reported:
/usr/include/asm does not exist on my machine - only /usr/include/asm-generic.
This seems to be a common problem:
(https://stackoverflow.com/questions/14795608/asm-errno-h-no-such-file-or-directory
)
These are the relevant packages I have installed:
dpkg -l | egrep
Public bug reported:
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Ran into this today - under certain circumstances,
"-fsanitize=undefined" generates ambiguous local labels so that the code
cannot be assembled.
This is already fixed upstream, also backported to the gcc-5-branch, but
not
12 matches
Mail list logo
