Hello, this is probably what we should do for mantic
release?field.comment=Hello, this is probably what we should do for
mantic release?
---
7.8.git20221117.28daf24+dfsg-3/debian/patches/0022-Always-build-rk_strlcat-and-rk_strlcpy-symbols.patch
1970-01-01 00:00:00.0 +
+++
** Patch added: "heimdal_7.8.git20221117.28daf24+dfsg-4.patch"
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+attachment/5736213/+files/heimdal_7.8.git20221117.28daf24+dfsg-4.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The build is failing:
https://launchpad.net/ubuntu/+source/bluez/5.71-0ubuntu1
But I don't know how to reproduce the failure. Certainly it builds on
both noble and mantic, and installs, and works for me. Is this because
Launchpad is using a focal toolchain?
--
You received this bug notification
Public bug reported:
Make 22.04.3 usb live
make ubuntu-bug firefox
it says cant- its snap app
learn how to update snap
sudo snap refresh
sudo snap refresh
ubuntu-bug firefox
see screenshot- asks about 2 different snaps
why previous is not removed?
why before it said that snap cant be reported?
> 34174 lines in this case is not plausibly reviewable.
I typically use filterdiff to get the packaging changes, and review
specific source files as necessary (including copyright changes in the
diff, which can be important, even if you're just using a script for
it).
Thanks for your help here.
Public bug reported:
(Sticky Keys is an accessibility feature. Settings->Typing Assist
(AccessX)->Sticky Keys. Sticky Keys is not just for the disabled!
Sticky Keys is a feature that helps prevent or attenuate repetitive
stress injuries (RSI) by helping the user avoid problematic "deviations"
It's usually Seb sponsoring these, but he's on vacation. To avoid any
future complaints in case he's away again I will also include debdiffs
in future.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Sync has made it to -proposed
libmnl | 1.0.4-3build2 | jammy | source
libmnl | 1.0.4-3ubuntu1 | lunar | source
libmnl | 1.0.4-3ubuntu1 | mantic | source
libmnl | 1.0.4-3ubuntu1 | noble | source
libmnl | 1.0.5-2| noble-proposed | source
** Changed
Here's the debdiff. We don't usually use them for major updates though
because of the size. 34174 lines in this case is not plausibly
reviewable.
** Patch added: "bluez_5.71-0ubuntu1.debdiff"
This bug was fixed in the package zeitgeist - 1.0.4-5ubuntu1
---
zeitgeist (1.0.4-5ubuntu1) noble; urgency=low
* Merge with Debian unstable. Remaining changes: (LP: #2044300)
- Add nodisplay_autostart.patch: Don't show in Startup Applications
- Add pre_populator.patch:
rsyslog - 8.2312.0-2ubuntu1 is available in ppa:xypron/merge-from-
debian.
** Changed in: rsyslog (Ubuntu)
Assignee: Heinrich Schuchardt (xypron) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog
** Package changed: ubuntu => systemd (Ubuntu)
--
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/2047975
Title:
package systemd-resolved 253.5-1ubuntu7 failed to
Of course a user can write 'colorscheme lunaperche' or alike to his
.vimrc. But it still makes sense to start with something readable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
You have been subscribed to a public bug:
upgraded from 22.04 -> 24.04
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: systemd-resolved 253.5-1ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
** Description changed:
With vim 2:9.0.2189-1ubuntu1 the coloring of patches has been changed.
The result is that in konsole patches have become illegible. See
appendix.
Deleted lines have foreground cyan #18b2b2 and background light blue
#7f7fff. Kind of blue on blue.
-
I very much dislike reviewing packages this way. For a package to be in
the sponsorship queue, it needs to have a debdiff, not a debian.tar.xz.
I understand that it's a new upstream release, but that does not excuse
the need for a debdiff, even if you *also* include these files.
I'm uploading
The only Ubuntu delta is now in Debian. Requesting a sync.
** Merge proposal linked:
https://code.launchpad.net/~mitchdz/ubuntu/+source/libmnl/+git/libmnl/+merge/457925
** Tags removed: needs-merge
** Tags added: needs-sync
** Summary changed:
- Merge libmnl from Debian unstable for noble
Public bug reported:
With vim 2:9.0.2189-1ubuntu1 the coloring of patches has been changed.
The result is that in konsole patches have become illegible. See
appendix.
Deleted lines have foreground cyan #18b2b2 and background light blue
#7f7fff. Kind of blue on blue.
Please, provide sane color
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
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/2046459
Title:
systemd-gpt-auto-generator is
** Changed in: libmnl (Ubuntu)
Assignee: (unassigned) => Mitchell Dzurick (mitchdz)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/2040389
Title:
Merge libmnl from
There is no workaround for this with the stock netplan config on
raspberry pi, which trips this bug. But you can customize /etc/netplan/
on your system to mark your expected/required network interfaces as
"optional: false" (which is the default if unspecified); AIUI that would
avoid this issue
This is the apparmor denial:
audit: type=1400 audit(1704299091.131:665): apparmor="DENIED"
operation="mount" class="mount" info="failed flags match" error=-13
profile="lxd-noble_" name="/dev/shm/"
pid=71828 comm="(sd-mkdcreds)" flags="ro, nosuid, nodev, noexec,
remount, bind"
which corresponds
https://salsa.debian.org/ssh-
team/openssh/-/commit/da06b7ef32c20de4dd18cd578025d96a9221984b
** Changed in: openssh (Ubuntu)
Status: New => Fix Committed
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
You received this bug notification because
Please, review
https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/457913
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Heinrich Schuchardt (xypron)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Description changed:
+ [ Impact ]
+
+ Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop of
+ playback of a midi song, causing issues for a multitude of players
+ including EasyABC. This will cause said player to be unable to playback
+ again and perhaps even crash. See
+
All the failing autopkgtests currently reported for this update also
failed a migration-reference/0 run
mutter/42.9-0ubuntu5 (arm64, ppc64el)
vtk9/9.1.0+really9.1.0+dfsg2-3build1 (armhf)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
"Where problems could occur" says "...in [Other Info] section I included
some query examples for well-known domains, so we can be more confident
with this change", but I don't see these carried out as part of the SRU
verification.
Admittedly they weren't documented as part of the Test Plan, but
** Summary changed:
- libfluidsynth3 2.3.3-2.1 does not contain the version 2.3.3 but only version
2.3.2
+ [SRU] Players terminate after stopping and restarting
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fluidsynth in
** Changed in: fluidsynth (Ubuntu Mantic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fluidsynth in Ubuntu.
https://bugs.launchpad.net/bugs/2047656
Title:
libfluidsynth3 2.3.3-2.1
Yep, false alarm, the patch works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2045570
Title:
dnsmasq crash when no servers in resolv.conf
Status in dnsmasq package
Ah, never mind, I built the package incorrectly. It's not a quilt
package... :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2045570
Title:
dnsmasq crash when no
So with the upstream patch, I see no crash, but dnsmasq starts spinning
CPU at 100%. This is not a good enough fix.
** Description changed:
[ Impact ]
dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the
file is updated. When that happens and for some reason there
** Also affects: bubblewrap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor user namespace
** Also affects: steam (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor user namespace
** Description changed:
[ Impact ]
dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the
file is updated. When that happens and for some reason there were no
"nameserver" declarations in the updated file, dnsmasq can crash.
Here is a log of a reproducer:
$ dig
** Description changed:
[ Impact ]
dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the
file is updated. When that happens and for some reason there were no
"nameserver" declarations in the updated file, dnsmasq can crash.
Here is a log of a reproducer:
$ dig
** Changed in: tzdata (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2047939
Title:
Let tzdata not recommend tzdata-icu
** Description changed:
[ Impact ]
dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the
file is updated. When that happens and for some reason there were no
"nameserver" declarations in the updated file, dnsmasq can crash.
Here is a log of a reproducer:
$ dig
** Description changed:
+ [ Impact ]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [
Public bug reported:
tzdata-icu was split out of tzdata in 2022g-7ubuntu1 in lunar. Stop
letting tzdata recommend tzdata-icu. All packages that need the files in
/usr/share/zoneinfo-icu should directly depend on tzdata-icu.
** Affects: tzdata (Ubuntu)
Importance: Medium
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1981995
Title:
incorrect system load format
Status
I am marking this bug as invalid, because adding time zones should be
done upstream first. We do not want to maintain a different set of zones
in Ubuntu. Please look at https://www.iana.org/time-zones and contribute
via the t...@iana.org mailing list.
** Changed in: tzdata (Ubuntu)
Status:
** Changed in: base-files (Ubuntu Xenial)
Status: New => In Progress
** Changed in: base-files (Ubuntu Bionic)
Status: New => In Progress
** Changed in: base-files (Ubuntu Focal)
Status: New => In Progress
** Changed in: base-files (Ubuntu Jammy)
Status: New => In
Therefore, marking it as done, not incomplete. It would have been
incomplete had there been nothing to merge.
** Changed in: krb5 (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Summary changed:
- matchit vim matching parentheses tex files
+ vim Matchit's parentheses matching function breaks in tex files
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
Public bug reported:
** lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04
**apt-cache policy vim
vim:
Installed: 2:8.2.3995-1ubuntu2.15
Candidate: 2:8.2.3995-1ubuntu2.15
Version table:
*** 2:8.2.3995-1ubuntu2.15 500
500 http://de.archive.ubuntu.com/ubuntu
Weirdly simple, but wow, this cannot be it. Hallelujah After a few
days reading and testing many things, I finally have audio! Apparently,
it was missing (some?) library required for pipewire. I have a Legion 7i
Pro running popOS on kernel 6.6.6-76060606-generic. Try running this
command:
** Changed in: pm-utils (Debian)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/224697
Title:
Disable hibernation if swap is on file
** Changed in: heimdal (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/2036253
Title:
FTBFS: missing strl* symbols fail the
** Attachment added: "bluez_5.71-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5735865/+files/bluez_5.71-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Updated source files are attached above. And the source is in:
https://git.launchpad.net/~bluetooth/bluez/log/
--
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/2047780
Title:
** Attachment added: "bluez_5.71.orig.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5735864/+files/bluez_5.71.orig.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Changed in: bluez (Ubuntu)
Status: Triaged => In Progress
--
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/2047780
Title:
BlueZ release 5.71
Status in bluez
What is the make and model of the machine? It seems to identify itself
as "Default string".
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
54 matches
Mail list logo
