Public bug reported:
The qemu build reaches (and always did) a step where it tries to link some
img files. That is done via the command:
$ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s
-o multiboot.img multiboot.o
Recently that still works in Debian [1] but no more in Ubuntu [2]
** Attachment added: "linuxboot.o - build artifact to re-create the issue"
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/+attachment/5442724/+files/linuxboot.o
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Attachment added: "flat.lds - build artifact to re-create the issue"
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/+attachment/5442723/+files/flat.lds
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bi
** Changed in: binutils (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1907789
Title:
2.35.50 breaks ld -no-pie
Status in bi
I checked on kernel 5.9.12 Ubuntu 20.04 Huawei amd D13 , problem not
solved
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1887968
Title:
Pairing with Bluetooth LE mice fail
Public bug reported:
This is a special case of Bug 559345 somewhere between a question and a
request for better/more discoverable error message/documentation.
In apport, because thats what people encountering bugs are going to use.
In USN, because the one thing worse than no security notices is i
please reboot with this kernel boot parameter added:
systemd.log_level=debug
Then let the system boot up, and then perform a shutdown, to reproduce
the problem. Then start the system back up (you can remove the kernel
boot parameter) and capture the previous boot's journal, which should
include t
can you boot with the kernel param 'systemd.log_level=debug' and
recreate the problem, and then provide the full journal logs, e.g.:
$ journalctl -b > /tmp/lp1891358.log
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a mem
** Tags added: resolved-resolvconf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1874337
Title:
resolvconf should never touch /etc/resolv.conf in Ubuntu; all DNS
confi
it sounds like this bug is a dup of bug 1872159? I'm assuming so, and
marking this invalid for systemd.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sys
Just to follow up, a quick read of the upstream bug seems to indicate
there are kernel patch(es) involved in fixing this as well as systemd
patch(es). The upstream bug isn't yet marked fixed, so hopefully we can
check back in the new year to start backporting.
--
You received this bug notificatio
please boot with kernel boot parameter 'systemd.log_level=debug' and
reproduce this, then provide the journal logs (before rebooting) with:
$ journalctl -k -b > /tmp/lp1830955.log
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
marking as invalid for systemd as i believe the bug was in maas, per
previous comments.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
ht
marking this as invalid for systemd as arbitrary code can be run using
networkd-dispatcher and/or suggestions from comment 4.
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This has been happening for ages now.
18.04 to 20.10 are all affected
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1846334
Title:
cupsd assert failure: free(): invalid poin
I'm hesitant to backport, because the change causes significant issues on
upgrade, e.g.:
https://github.com/systemd/systemd/issues/17605
if we do backport the 'sticky' udev tags, we'll need to make sure to also pull
back the proper commits to handle the new udev format across daemon-reexec,
e.g
** Description changed:
This is a special case of Bug 559345 somewhere between a question and a
request for better/more discoverable error message/documentation.
In apport, because thats what people encountering bugs are going to use.
In USN, because the one thing worse than no security
@sampie you have a reference to the upstream issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1902891
Title:
"Too many levels of symbolic links” error when using syst
*** This bug is a duplicate of bug 1905245 ***
https://bugs.launchpad.net/bugs/1905245
you didn't say specifically what's causing ansible to fail, but the fix
you referenced suggests this is a dup of 1905245, so i'll mark it as
such.
** This bug has been marked a duplicate of bug 1905245
"
per comment in bug description, marking as affecting only focal
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch s
@kaihengfeng, can we skip Xenial since that goes ESM soon?
** Description changed:
[Impact]
Micmute hotkey on many HP EliteBooks don't work.
[Fix]
Commit b6eb208b29ae ("hwdb: Add EliteBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the
@kaihengfeng can you review this bug to see if you can tell what the
correct change to the hwdb should be?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1890186
Title:
Fa
Public bug reported:
[Impact]
In bug 1161743 we discovered that if a system is configured with multiple
locales, only the locales of the user who generated the apt-cache will be
available for translated descriptions.
[Test case]
# apt install locales-all # get the locale
# export LANG=sv_SE.UT
try disabling the 'ondemand' service and install cpufrequtils package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1889668
Title:
set-cpufreq error when cpu is offline
Hi, first of all I don' t know why I did' t receive any notification of
this bug report.
Second, and to clarify, I being using screen command since 2000 (which
Is my beginning as Linux admin). This being said, I know how it works.
All my other Ubuntu upgrades from 18.04 to 20.04, this does not ha
That's interesting, I just performed your suggested test, and I couldn't
reproduce - it's a fresh Ubuntu 20.04 install, running MATE (not KDE!)
and GNU screen 4.8.0-1. After closing the terminal, I've opened another
one and "screen -x" worked fine, as expected.
Could you try to use MATE / Gnome to
Well, is a really close (or same) behaviur like exposed in
https://bugs.debian.org/825394 (shared by Axel).
Screen version 4.8.0-1. The system (or either systemd) has modifications
at all, so is really weird.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
To my knowledge, networkd-dispatcher has no way to do 'pre' hooks on
systemd-networkd events, so this is still a valid feature request.
** Changed in: systemd (Ubuntu)
Status: Invalid => Triaged
** Changed in: systemd (Ubuntu)
Milestone: ubuntu-17.05 => None
** Changed in: systemd (Ub
Public bug reported:
I can't reliably reproduce this crash, and I don't know, even
approximately, what's causing it, or what I might be doing to possibly
cause it. It just randomly crashes, and dumps me back to the login
screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19
Hello Rolf, or anyone else affected,
Accepted cyrus-sasl2 into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cyrus-
sasl2/2.1.27~101-g0780600+dfsg-3ubuntu2.3 in a few hours, and then in
the -proposed repository.
Please help us by testing this
All autopkgtests for the newly accepted cyrus-sasl2
(2.1.27~101-g0780600+dfsg-3ubuntu2.2) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
kimap/17.12.3-0ubuntu1 (s390x)
Please visit the excuses page listed below and investigate t
Public bug reported:
Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS.
The problem:
When i connect to my external monitor (a Samsung BX2250) via HDMI, the
screen is detected (i can see it in display settings) but the external
monitor remains black. Seams like a bad frequency
All autopkgtests for the newly accepted cyrus-sasl2
(2.1.27~101-g0780600+dfsg-3ubuntu2.2) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
kimap/17.12.3-0ubuntu1 (s390x)
Please visit the excuses page listed below and investigate t
I have followed this guide
https://davidwpearson.wordpress.com/2020/01/10/lenovo-laptop-subwoofers-and-linux/#fix
i don't think it did a thing for the subwoofer, but it manages to sound a bit
nicer
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.n
Installer Crashed Error
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1871268
Title:
Installation fails due to useless immediate configuration error when
"Install Third-Par
All autopkgtests for the newly accepted cyrus-sasl2
(2.1.27~101-g0780600+dfsg-3ubuntu2.3) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
postfix/3.3.0-1ubuntu0.3 (amd64)
kimap/17.12.3-0ubuntu1 (armhf, ppc64el, arm64)
Please visi
37 matches
Mail list logo
