Public bug reported:
Problematic commit reverted upstream causing incorrect behavior in
Ubuntu Focal.
Discussion: https://github.com/iputils/iputils/issues/320
Fix: https://github.com/iputils/iputils/pull/321
Release: https://github.com/iputils/iputils/releases/tag/20210722
Could this patch be
Great, happy to test again if you need it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243190
Title:
Failed to connect to virtio-serial channel
To manage notifications about this bug go to:
Martin - thanks!
I had the udev package held to 175-0ubuntu29 and allowed it to update to
the released 204-0ubuntu19 version. I then built the 1.22.4-1ubuntu1
package locally using pbuilder and it works great. Both libguestfs-test-
tool and my application using libguestfs work properly.
--
You
Could we please get a decision on if this will be updated in Saucy or if
I should file a backports request for it?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243190
Title:
Failed to
I rebuilt the 1.0.6-2 source package in a pbuilder chroot and the
resulting packages all seem to work fine. I see the Trusty version has a
build1 suffix without any changes. Should something similar be done for
Saucy?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
traktor:~$ gearadmin -h
Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions:
Assertion `needed != ((void *)0)' failed!
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gearman-tools 1.0.6-2
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Is this something that will be published to saucy-updates or saucy-
backports?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243190
Title:
Failed to connect to virtio-serial channel
To manage
There is no `name` in that directory which certainly would explain the
lack of a named symlink. I provided a name (id) to the virtserialport
device in the qemu options.
-r--r--r-- 1 root root 4096 Oct 30 07:22 dev
lrwxrwxrwx 1 root root0 Oct 30 07:22 device - ../../../virtio0
drwxr-xr-x
I was wrong about the default of the name attribute to the
virtserialport and when providing it the virtio-ports symlink is created
as expected in my direct qemu test. My original problem was that
libguestfs-test-tool doesn't work with this udev version and that is
still the case even though it
This is from as similar an environment as I could recreate outside the
libguestfs-test-tool. I'd noticed the difference in that rule and tried
to remove the SUBSYSTEM check without success before, sorry I didn't
mention that.
Here is the udevadm dump, looks like the subsystem is correct, but I'm
Public bug reported:
After upgrading from Raring to Saucy, our libguestfs system stopped
working. I then tried a fresh install of Saucy with the same results. I
narrowed the issue down to the udev package. I was able to downgrade the
udev package to the previous non-systemd (175-0ubuntu29)
The official update fixed the issue for me. Thanks.
--
Font sizes in Gutsy are affected by bad X.org DPI detection
https://bugs.launchpad.net/bugs/118745
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
This seems a lot worse to me than low urgency if kickstart is supposed
to be a supported method of installing. Should we be running
`shadowconfig on` in the postinstall or something? This was working
previously with dapper, from looking back at logs it appears to have
been in the march/april
13 matches
Mail list logo
