So, I'm not Steve, but as this is a priority and I know Steve is off
this week I've taken a look at this to hopefully resolve some review
questions before he's back.
A number of the bugs referenced in this upload don't have the relevant
SRU information attached, which would be helpful.
The
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
The followings seem the same problems.
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1986841
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
The followings seem the same problems.
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1986841
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1946016
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
It seems the same problem.
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1982551
--
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/1986841
Title:
canon pixma g2010
This is missing the SRU template information.
Particularly: what is the test plan to verify (a) that this does what we
need, and (b) doesn't accidentally break existing apparmor profiles?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
This is missing the SRU template information - there seems to be a test
case there, but the rest is missing.
--
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/1964636
Title:
I can confirm here that I have sucessfully installed only 2 local
printers on cups, and I can see only them in cups admin.
But on Gnome's settings printers, there are all printers on my network.
I am in a corporate lan with like 30 printers in my print dialogue...
So gnome is getting data from
Is Cody actively working on this? If not, should he be unassigned?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/387957
Title:
Improve Save As Dialog Box (focus issues)
[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This bug was fixed in the package apport - 2.20.11-0ubuntu82.2
---
apport (2.20.11-0ubuntu82.2) jammy; urgency=medium
* Point Vcs-* URIs to git
* Grab a slice of JournalErrors around the crash time (LP: #1962454)
* data/apport:
- Initialize error log as first step (LP:
This bug was fixed in the package apport - 2.20.11-0ubuntu82.2
---
apport (2.20.11-0ubuntu82.2) jammy; urgency=medium
* Point Vcs-* URIs to git
* Grab a slice of JournalErrors around the crash time (LP: #1962454)
* data/apport:
- Initialize error log as first step (LP:
This bug was fixed in the package apport - 2.20.11-0ubuntu82.2
---
apport (2.20.11-0ubuntu82.2) jammy; urgency=medium
* Point Vcs-* URIs to git
* Grab a slice of JournalErrors around the crash time (LP: #1962454)
* data/apport:
- Initialize error log as first step (LP:
This bug was fixed in the package apport - 2.20.11-0ubuntu82.2
---
apport (2.20.11-0ubuntu82.2) jammy; urgency=medium
* Point Vcs-* URIs to git
* Grab a slice of JournalErrors around the crash time (LP: #1962454)
* data/apport:
- Initialize error log as first step (LP:
This bug was fixed in the package apport - 2.20.11-0ubuntu27.25
---
apport (2.20.11-0ubuntu27.25) focal; urgency=medium
* Point Vcs-* URIs to git
* whoopsie-upload-all: Catch FileNotFoundError during process_report
(LP: #1867204)
* Grab a slice of JournalErrors around the
This bug was fixed in the package apport - 2.20.11-0ubuntu27.25
---
apport (2.20.11-0ubuntu27.25) focal; urgency=medium
* Point Vcs-* URIs to git
* whoopsie-upload-all: Catch FileNotFoundError during process_report
(LP: #1867204)
* Grab a slice of JournalErrors around the
This bug was fixed in the package apport - 2.20.11-0ubuntu27.25
---
apport (2.20.11-0ubuntu27.25) focal; urgency=medium
* Point Vcs-* URIs to git
* whoopsie-upload-all: Catch FileNotFoundError during process_report
(LP: #1867204)
* Grab a slice of JournalErrors around the
This bug was fixed in the package apport - 2.20.11-0ubuntu27.25
---
apport (2.20.11-0ubuntu27.25) focal; urgency=medium
* Point Vcs-* URIs to git
* whoopsie-upload-all: Catch FileNotFoundError during process_report
(LP: #1867204)
* Grab a slice of JournalErrors around the
This bug was fixed in the package apport - 2.20.11-0ubuntu27.25
---
apport (2.20.11-0ubuntu27.25) focal; urgency=medium
* Point Vcs-* URIs to git
* whoopsie-upload-all: Catch FileNotFoundError during process_report
(LP: #1867204)
* Grab a slice of JournalErrors around the
The verification of the Stable Release Update for apport has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for apport has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for apport has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for apport has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for apport has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The issue still exists as of Ubuntu 22.04.1 LTS and Ubuntu 18.04.6 LTS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1873920
Title:
default vi on focal emits escape
*** This bug is a duplicate of bug 1971538 ***
https://bugs.launchpad.net/bugs/1971538
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Remaining differences with tiff from Debian unstable:
* Merge from Debian unstable (LP #1997278). Also we take Debian's security
fixes for the recent CVEs, except for CVE-2022-2519_2520_2521_2953.patch
which is not included in Debian, at least as of now.
* Don't build with LERC on
And here's a debdiff to 4.4.0-5 from debian unstable, for reference.
** Patch added: "debdiff to the 4.4.0-5 version in debian unstable"
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1997278/+attachment/5632154/+files/tiff_4.4.0-5ubuntu1-from-4.4.0-5.debdiff
** Changed in: tiff
Ok please disregard the two earlier debdiffs, and use the following
instead.
** Patch added: "debdiff to the 4.4.0-4ubuntu3.1 version in kinetic"
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1997278/+attachment/5632153/+files/tiff_4.4.0-5ubuntu1-from-4.4.0-4ubuntu3.1.debdiff
--
You
@Craig The limit in Debian is actually much lower than in Ubuntu even,
but fixing it there is even harder as that misses a lot more patches.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
I managed to get audio output going using amixer:
amixer sset Master mute unmute 1- 1+
Both parts are necessary (mute/unmute and volume adjustment). Just
muting/unmuting or adjusting the volume does not bring back audio
output.
I can put it in my start script without adding any possibly
Tested on focal. Test script:
```
#!/bin/sh
set -u
log() {
local msg="$1"
echo "I: $msg"
sudo sh -c "echo '$msg' > /dev/kmsg"
}
sudo rm /var/crash/*
date
log "some messages"
sleep 1
log "more messages"
sleep 3600 &
killall -11 sleep
log 'message after crash'
sleep 5
log
Hello everyone, I applied Jeffersons version of the solution and it
helped (great!), but then I reverted '/etc/apparmor.d/usr.bin.evince' to
the original version and printing with evince still works, even after
reboot. Is it possible that this setting has to be applied only once?
--
You received
Successfully retried verification for jammy:
https://errors.ubuntu.com/oops/b0c797d4-6a6c-11ed-b539-fa163ef35206
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1962454
The issue is that the current base image was built on kinetic and
included dbus binaries from kinetic-security which are newer than what
is in lunar, or the lunar env doesn't enable proposed anymore. We are
talking to the autopkgtest team about regenerating an image on lunar
--
You received this
> This seems to be affecting a lot more stuff than just libatk-
bridge2.0-0 and more architectures than just i386.
Seems that the base testbed (see 'testbed-packages' from
artefacts.tar.gz) on many runs includes packages from proposed. e.g. the
dbus 1.14.0-2ubuntu3 and curl 7.86.0-2 proposed
** Changed in: tiff (Ubuntu)
Assignee: (unassigned) => Amin Bandali (bandali)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tiff in Ubuntu.
https://bugs.launchpad.net/bugs/1997278
Title:
Merge tiff 4.4.0-5 (main)
** Description changed:
+ * Impact
+
+ The gnome-online-accounts sometime crash after resuming from suspend
+
+
+ * Test case
+
+ Install the gnome-online-accounts update, restart your system and verify
+ that configured online accounts keep working. Taking a Google account
+ example,
** Also affects: librest (Ubuntu)
Importance: Undecided
Status: New
** Changed in: librest (Ubuntu)
Importance: Undecided => High
** Changed in: librest (Ubuntu)
Status: New => Fix Committed
** Changed in: librest (Ubuntu)
Assignee: (unassigned) => Sebastien Bacher
** Changed in: ubuntu-release-notes
Status: Confirmed => Incomplete
** Changed in: sudo (Ubuntu Xenial)
Assignee: (unassigned) => lolo (lolo2020)
** Changed in: sudo (Ubuntu Bionic)
Assignee: (unassigned) => lolo (lolo2020)
--
You received this bug notification because you are
Since I did not find a crash report with the updated apport, I created
one myself.
```
sudo sh -c "echo 'some messages' > /dev/kmsg"
sudo sh -c "echo 'more messages' > /dev/kmsg"
divide-by-zero
sudo sh -c "echo 'message after crash' > /dev/kmsg"
```
I waited over 10 second to actual act on the
** Description changed:
* Impact
We did a git snapshot before Kinetic feature freeze on oem request to
add support for newer hardware but upstream didn't roll out stable
tarballs before release. The stable release is available now and fixing
some issues found during the serie
** Description changed:
* Impact
We did a git snapshot before Kinetic feature freeze on oem request to
add support for newer hardware but upstream didn't roll out stable
tarballs before release. The stable release is available now and fixing
some issues found during the serie
** Tags added: lunar rls-ll-incoming update-excuse
** Summary changed:
- libatk-bridge2.0-0 uninstallable on i386
+ libdbus-1-3 uninstallable on autopkgtest
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
Thank you for reporting this issue.
This seems to be affecting a lot more stuff than just libatk-bridge2.0-0
and more architectures than just i386.
See https://lists.ubuntu.com/archives/ubuntu-
devel/2022-November/042352.html
** Also affects: dbus (Ubuntu)
Importance: Undecided
Verified focal: apport 2.20.11-0ubuntu27.25 does not appear on
https://errors.ubuntu.com/problem/3adc63930455e99063ec1f77bf461d975492e9b4
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification
** Description changed:
* Impact
We did a git snapshot before Kinetic feature freeze on oem request to
add support for newer hardware but upstream didn't roll out stable
tarballs before release. The stable release is available now and fixing
some issues found during the serie
can this be a solution ?
https://stackoverflow.com/questions/2895816/how-do-i-strip-local-
symbols-from-linux-kernel-module-without-breaking-it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Also affects: libqmi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libqmi (Ubuntu)
Status: New => Fix Released
** Changed in: libqmi (Ubuntu)
Importance: Undecided => High
** Also affects: libmbim (Ubuntu)
Importance: Undecided
Status: New
**
Public bug reported:
* Impact
We did a git snapshot before Kinetic feature freeze on oem request to
add support for newer hardware but upstream didn't roll out stable
tarballs before release. The stable release is available now and fixing
some issues found during the serie stabilization.
* Test
--- Comment From i...@de.ibm.com 2022-11-22 04:52 EDT---
As a comprehensive test plan I would suggest the following:
* Run zlib-ng testsuite against Ubuntu zlib. This is possible since
https://github.com/zlib-ng/zlib-
ng/commit/e63f36b1cf615a81e2cfa2d97fc54a5f493c9c19, the testsuite is
** Tags added: upgrade-software-version
--
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/1997201
Title:
BlueZ 5.66 release
Status in bluez package in Ubuntu:
Triaged
Bug
Hi Ijlal,
That's correct - the SRU to focal (and thus core 20) is the important
one for the customer.
Cheers,
Isaac
--
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/1994146
Public bug reported:
https://autopkgtest.ubuntu.com/results/autopkgtest-
lunar/lunar/i386/v/vlc/20221121_104906_b4207@/log.gz
Starting pkgProblemResolver with broken count: 9
Starting 2 pkgProblemResolver with broken count: 9
Investigating (0) libvlccore9:i386 < none -> 3.0.17.4-5 @un puN Ib >
57 matches
Mail list logo
