[Desktop-packages] [Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
Hi Luka/@zapduke, Can you test/verify bionic-proposed? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Description ] Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. [ Test case ] Install gsconnect extension in gnome-shell: https://extensions.gnome.org/extension/1319/gsconnect/ - Start Up system - first Notification from connected device - Hangs for about 20 sec + This should not happen [ Regression potential ] Persistent state is not kept, although the patch is living upstream for many cycles already, so it's pretty safe. - I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817738] Re: Can't change virtual terminal on login screen or when auto-login is enabled
** Patch added: "plymouth_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817738/+attachment/5252486/+files/plymouth_bionic.debdiff
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: plymouth (Ubuntu)
Status: New => Confirmed
** Changed in: plymouth (Ubuntu)
Importance: Undecided => Medium
** No longer affects: gdm3 (Ubuntu)
** No longer affects: gdm3 (Ubuntu Bionic)
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: plymouth (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: plymouth (Ubuntu Bionic)
Status: New => In Progress
** Changed in: plymouth (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: plymouth (Ubuntu Bionic)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1817738
Title:
Can't change virtual terminal on login screen or when auto-login is
enabled
Status in OEM Priority Project:
Confirmed
Status in plymouth package in Ubuntu:
Fix Released
Status in plymouth source package in Bionic:
In Progress
Bug description:
[Impact]
When AutomaticLogin is enabled in gdm3, or it is showing the login screen,
the "chvt" command blocks indefinitely (usually resumes with gdm3 restart).
This prevents users to change the foreground virtual terminal, and it can
also prevent pm-suspend to complete (as it invokes chvt).
This problem happens in Bionic; it's already fixed in Cosmic and
later.
This patch to plymouth helps it not to revert the VT/tty to VT_AUTO
(after gdm calls 'plymouth deactivate' and changes it to VT_PROCESS)
which causes the ioctl(VT_SETACTIVE) not to generate the event that
the ioctl(VT_WAITACTIVE) will block/wait on just afterward.
Workarounds are to either disable plymouth / remove 'splash' from the
kernel command line or change it to use a different/non-graphical VT
for console (console=tty0 [default] or console=tty1 [equivalent] are
affected, but console=ttyS0 or console=ttyS1 are not, being serial).
[Test case]
1) Install Bionic/18.04 LTS Desktop
2) Ensure plymouth / 'splash' is enabled (default)
$ grep splash /proc/cmdline
BOOT_IMAGE=... root=... splash ...
3) Ensure console is tty0 (default) or tty1
$ dmesg | grep console
[0.004000] console [tty0] enabled
A) Login screen, regardless of automatic login
4) Ensure the login screen/tty 1 is the displaying
(i.e., it's foregound/active VT) or change to it:
$ sudo chvt 1 # this works/finishes.
$
5) $ ssh 'sudo fgconsole' # check tty1 is foreground VT
1
6) $ ssh 'sudo chvt 4' # this blocks/doesn't finish
B) Automatic login, regardless of login screen
4) Enable AutomaticLogin in /etc/gdm3/custom.conf
[daemon]
AutomaticLoginEnable = true
AutomaticLogin =
5) Reboot your system and make sure AutoLogin works by not
requesting password before opening the session.
6) Print active VT
(in Bionic, autologin user session runs on tty1)
$ sudo fgconsole
1
7) sudo chvt 4 # this blocks/doesn't finish
From SSH one can check that chvt is blocked waiting
on new VT to become active, which doesn't happen in
this case (old VT in VT_AUTO + KB_GRAPHICS mode):
$ cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
[Potential regression]
Low. This plymouth patch is upstream and it's already applied
in Cosmic and later for ~6 months (0.9.3-1ubuntu10 / Oct 2018)
for LP: #1795637 (different problem/effect, same root cause).
Besides, it's conservative in nature, and it's spirit makes a
lot of sense (stop handling more udev events after deactivate).
There are no additional fixes to its code changes upstream.
[Original Description]
$ sudo strace chvt 4
<...>
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
ioctl(3, VT_ACTIVATE, 0x4) = 0
ioctl(3, VT_WAITACTIVE, 0x4
VT_ACTIVATE will cause a switch to VT number.
VT_WAITACTIVE will sleep/wait until the specified VT has been activated.
$ sudo cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0
[Desktop-packages] [Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
** Tags added: se-sponsor-dgadomski -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: Fix Released Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: In Progress Status in gjs source package in Kinetic: Triaged Status in gjs source package in Lunar: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] gnome-shell often crashes on logout causing annoyance to the user as an error report dialog is displayed at the next login. [ Test Plan ] 1. Log into gnome-shell 2. Use gnome-shell for long enough to trigger a garbage collection cycle: Scroll the app grid and repeatedly open the calendar from the top bar for 30 seconds. 3. Log out. 4. Verify no new gnome-shell crash files appear in /var/crash/ [ Where problems could occur ] Only gnome-shell shutdown/logout is affected. [ Other Info ] https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020641] Re: Installing or removing apps through snap-store launches another gdm session
Marking Kinetic as Won't Fix (release close to EOL, as mentioned in an email thread). ** Also affects: gdm3 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2020641 Title: Installing or removing apps through snap-store launches another gdm session Status in gdm3 package in Ubuntu: Fix Committed Status in gdm3 source package in Jammy: Fix Committed Status in gdm3 source package in Kinetic: Won't Fix Status in gdm3 source package in Lunar: Fix Committed Status in gdm3 source package in Mantic: Fix Committed Bug description: gdm3 version: 42.0-1ubuntu7.22.04.2 Ubuntu version: Ubuntu 22.04.2 LTS [Description] Installing or removing snap packages through NICE DCV on AWS will cause the user to be kicked out of their session. The issue happens on machines running nvidia GPUs (passed through to a VM) with the GRID driver installed as well as the normal nvidia driver. [Steps to reproduce] Simply install or remove any snap through the snap store will trigger the issue, for example: $ snap install skype also running any of the following commands will also trigger the issue: $ snap connect skype:opengl :opengl $ snap disconnect skype:opengl :opengl $ snap connect skype:camera :camera $ snap disconnect skype:camera :camera After further investigation I was able to pin down the issue to udev and could reproduce the issue by running the following command: $ sudo udevadm trigger --parent-match=/sys/devices/pci:00/:00:1e.0/drm/card0 where "/sys/devices/pci:00/:00:1e.0/drm/card0" corresponds to the nvidia GPU of my instance. A more generic way of triggering the issue would be running: $ sudo udevadm trigger [Solution] I have investigated the issue and discovered that it lies within GDM3 in the "udev_is_settled" function (daemon/gdm-local-display-factory.c). In the case where the udev is settled the line "g_clear_signal_handler (&factory->uevent_handler_id, factory->gudev_client);" at the end of the function is triggered however this is not the case when the function returns early and will lead to the user being logged out. In its current implementation there are three different return points before "g_clear_signal_handler" is executed where the udev devices would already have settled. I have written a patch that fixes this issue by making sure the function "g_clear_signal_handler" is executed in all cases for which the udev is settled. [possible regressions] Excessive clearing of the signal handler might cause a case where it is not being re-initialized the next time it is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
I tested this with a local package build and local repo in a mantic container,
doing an `apt --dry-run dist-upgrade` without/with that repo (w/ noble apt
sources list),
and manually download/run noble's release upgrader without/with that repo.
The behavior is the same (ie, no regressions) as expected;
libglib2.0-0 is removed in favor of libglib2.0-0t64 in all cases.
Test 1)
Just Noble:
$ apt-cache show libglib2.0-bin | grep Version:
Version: 2.80.0-6ubuntu1
Version: 2.78.0-2
$ sudo apt --dry-run dist-upgrade 2>&1 | awk '{ print NR ": " $0 }' |
fgrep libglib2.0
17: libevent-core-2.1-7 libext2fs2 libgdbm-compat4 libgdbm6
libglib2.0-0
30: libgdbm6t64 libglib2.0-0t64 libgnutls30t64 libgpgme11t64
79: libglib2.0-bin libglib2.0-data libgmp10 libgomp1 libgpg-error-l10n
154: Remv libelf1 [0.189-4] [libglib2.0-bin:amd64 libbpf1:amd64
iproute2:amd64 ]
156: Inst libglib2.0-bin [2.78.0-2] (2.80.0-6ubuntu1 Ubuntu:24.04/noble
[amd64]) []
378: Remv libglib2.0-0 [2.78.0-2] [libappstream4:amd64
open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64
libnetplan0:amd64 ]
379: Inst libglib2.0-0t64 (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
[open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 ]
611: Inst libglib2.0-data [2.78.0-2] (2.80.0-6ubuntu1
Ubuntu:24.04/noble [all])
927: Conf libglib2.0-bin (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
1070: Conf libglib2.0-0t64 (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
1201: Conf libglib2.0-data (2.80.0-6ubuntu1 Ubuntu:24.04/noble [all])
Noble and local build/repo:
$ apt-cache show libglib2.0-bin | grep Version:
Version: 2.80.0-6ubuntu3
Version: 2.80.0-6ubuntu1
Version: 2.78.0-2
$ sudo apt --dry-run dist-upgrade 2>&1 | awk '{ print NR ": " $0 }' |
fgrep libglib2.0
17: libevent-core-2.1-7 libext2fs2 libgdbm-compat4 libgdbm6
libglib2.0-0
30: libgdbm6t64 libglib2.0-0t64 libgnutls30t64 libgpgme11t64
79: libglib2.0-bin libglib2.0-data libgmp10 libgomp1 libgpg-error-l10n
154: Remv libelf1 [0.189-4] [libglib2.0-bin:amd64 libbpf1:amd64
iproute2:amd64 ]
156: Inst libglib2.0-bin [2.78.0-2] (2.80.0-6ubuntu3 localhost [amd64])
[]
378: Remv libglib2.0-0 [2.78.0-2] [libappstream4:amd64
open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64
libnetplan0:amd64 ]
379: Inst libglib2.0-0t64 (2.80.0-6ubuntu3 localhost [amd64])
[open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 ]
611: Inst libglib2.0-data [2.78.0-2] (2.80.0-6ubuntu3 localhost [all])
927: Conf libglib2.0-bin (2.80.0-6ubuntu3 localhost [amd64])
1070: Conf libglib2.0-0t64 (2.80.0-6ubuntu3 localhost [amd64])
1201: Conf libglib2.0-data (2.80.0-6ubuntu3 localhost [all])
Test 2)
Just Noble:
$ dpkg -l | fgrep libglib2.0
rc libglib2.0-0:amd64 2.78.0-2
amd64GLib library of C routines
ii libglib2.0-0t64:amd64 2.80.0-6ubuntu1
amd64GLib library of C routines
ii libglib2.0-bin 2.80.0-6ubuntu1
amd64Programs for the GLib library
ii libglib2.0-data 2.80.0-6ubuntu1
all Common files for GLib library
$ dpkg -l | grep thunderbird
ii thunderbird 2:1snap1-0ubuntu3
amd64Transitional package - thunderbird -> thunderbird snap
$ snap list thunderbird
Name Version Rev Tracking Publisher Notes
thunderbird 115.10.1-1 470 latest/stable canonical✓ -
Noble and local build/repo:
$ dpkg -l | fgrep libglib2.0
rc libglib2.0-0:amd64 2.78.0-2
amd64GLib library of C routines
ii libglib2.0-0t64:amd64 2.80.0-6ubuntu3
amd64GLib library of C routines
ii libglib2.0-bin 2.80.0-6ubuntu3
amd64Programs for the GLib library
ii libglib2.0-data 2.80.0-6ubuntu3
all Common files for GLib library
$ dpkg -l | grep thunderbird
ii thunderbird 2:1snap1-0ubuntu3
amd64Transitional package - thunderbird -> thunderbird snap
$ snap list thunderbird
Name Version Rev Tracking Publisher Notes
thunderbird 115.10.1-1 470 latest/stable canonical✓ -
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitio
[Desktop-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
Hi Jeremy, This looks mostly good, AFAICT. Could you please complete the SRU bug template by adding the section 'Where problems could occur' / 'Regression potential'? [1] And although the 'Test Case' is feasible to understand, based on the 'Impact' section, it would be nice to have a 'functional' test, if at all possible/reasonably doable. For example, I tried to reproduce the thunderbird deb2snap issue, but it didn't. I realize there might be a more complex package setup/install list to trigger it, but maybe there's something simpler that you are aware of. (Or if it's too complex / not worth it, just clarifying that and mentioning what shouldn't change / how to check for no regressions, would be OK too; I tried to convey that in comment #1). Thanks! [1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ** Changed in: glib2.0 (Ubuntu Noble) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: Incomplete Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Where Problems Could Occur -- We have landed the change from this SRU in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. This SRU was recommended by Julian Klode, the apt maintainer for Debian and Ubuntu. The original transitional package was added by Simon McVittie in hopes that it would help apt be able to calculate the upgrade easier. At least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was the opposite. Hmm, we can't actually drop libglib2.0-0 after release, can we? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
The updates look good, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: Confirmed Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Technically, Steve Langasek already removed libglib2.0-0 from noble release just before release. This upload is necessary to ensure that we don't accidentally bring it back. Test Case - 1. Is libglib2.0-0 built? 2. Run rmadison libglib2.0-0 There should be 0 results for noble, noble-proposed, or noble-updates 3. Ensure that libglib2.0-0 is removed during the upgrade from Ubuntu 22.04 LTS to 24.04 LTS. Technically, ubuntu-release-upgrader is currently set to disallow upgrades to 24.04 LTS. If this is still the case when it is time to verify this SRU, you can manually substitute jammy → noble in /etc/apt/sources.list for purposes of testing this upgrade, probably in a VM since that's not the supported way to upgrade. Where Problems Could Occur -- Doing an upload to not build a package that already does not exist in Ubuntu 24.04 LTS should have no regression potential. The only other change in this SRU is bumping the Breaks version to ensure that the transitional libglib2.0-0 is also removed for people who were using Ubuntu 24.04 LTS early. That also should not cause problems since the package was an empty transitional package for early Ubuntu 24.04 LTS users. Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by removing the transitional package and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 We have landed the removal in Debian Unstable and it successfully migrated to Debian Testing on April 27 as one of the first t64 packages to migrate there. The removal was recommended by Julian Klode, the apt maintainer for Debian and Ubuntu. The original transitional package was added by Simon McVittie in hopes that it would help apt be able to calculate the upgrade easier. At least in the Ubuntu Desktop 22.04 LTS → 24.04 LTS case, it looks like it was the opposite. (Although that particular detail was fixed by the removal that already happened.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
Just for doc purposes,
ubuntu-meta's server-minimal binary package dependencies no longer list
`ssh-import-id` [1, 2], as expected.
$ wget -q
https://launchpad.net/ubuntu/+archive/primary/+files/ubuntu-server-minimal_1.481.{2,3}_amd64.deb
$ debdiff ubuntu-server-minimal_1.481.{2,3}_amd64.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Depends: apparmor, apport, apt, bcache-tools, btrfs-progs, cloud-init,
cryptsetup, dbus, lvm2, mdadm, multipath-tools, netbase, ntfs-3g, open-iscsi,
pollinate, snapd, [-ssh-import-id,-] sudo, systemd, systemd-sysv,
ubuntu-drivers-common, ubuntu-release-upgrader-core, udev, xfsprogs
Version: [-1.481.2-] {+1.481.3+}
[1] https://launchpad.net/ubuntu/jammy/amd64/ubuntu-server-minimal/1.481.2
[2] https://launchpad.net/ubuntu/jammy/amd64/ubuntu-server-minimal/1.481.3
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1974483
Title:
autoinstall ssh:install-server:false is misleading in 22.04
Status in subiquity:
Fix Released
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in ubuntu-meta package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Jammy:
Fix Released
Status in ubuntu-meta source package in Jammy:
Fix Released
Bug description:
[ Impact ]
openssh-server is always installed to the target machine regardless of the
user's explicit choice to not have it installed.
Backporting the fix will allow image builds to pick up it up and
become available for the next point release.
The upload fixes the bug by removing ssh-import-id from the server-
minimal seed and meta-package such that it's not part of the base
layer copied over during install.
[ Test Plan ]
live images -- Test 1:
1. Download the latest server installer image from
https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-live/
2. Perform a regular install using the image and on the "SSH configuration"
screen make sure "Install OpenSSH server" is NOT selected.
3. Finish the install and reboot the machine.
4. Login to the rebooted machine using the credentials provided during
install.
5. Using "apt-cache policy openssh-server" and "apt-cache policy
ssh-import-id" confirm neither are installed.
live images -- Test 2:
- Perform Test 1 but instead opt-in to installing openssh-server and ensure
it is installed in the target system.
live-images -- Test 3:
- Perform Test 2 but in a completely offline fashion.
pre-installed images:
- Download the latest preinstalled image from:
https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/
- Boot the image and, using the same commands as above, confirm
openssh-server and ssh-import-id ARE installed
[ Where problems could occur ]
- openssh-server could be included in the build through other means than
identified by the proposed upload, causing the package to be still installed by
default.
- openssh-server and ssh-import-id could fail to become part of the pool,
prohibiting offline install of the packages.
- Changes to the seeds could cause preinstalled images to lack the package.
- The image build(s) may produce errors if they rely on openssh-server or
ssh-import-id already being available in a layer in which it's now no longer
included. (I can't say it's likely but it is worth mentioning)
[ Other Info ]
* I have built test images for ubuntu-cpc, both minimized and non-minimized,
with my seed changes and verified those images will still correctly contain
ssh-import-id and open-ssh-server
[ Original Description]
With 22.04, openssh-server is baked into the image curtin copies to
the target. The ssh:install-server key no longer controls whether
openssh-server gets installed. It should be easy enough to have the
bit of code that installs openssh-server when the key is true also
remove it when the key is false.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1974483/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2076340] Re: SRU: no-change rebuild to pick up changed build flags on ppc64el and s390x
Hi Frank Heimes,
Comment #67:
> A new upload of the s390-tools package always also requires an upload of the
> s390-tools-signed package with the same version as well.
> I've attached the debdiff for it here...
Thanks for that.
The upload contains removals of d/{changelog,control}.orig which aren't
mentioned in d/changelog.
While that seems obvious to understand (apparently, such files aren't
referenced, and this is done also in Oracular in 2.33.1-0ubuntu1), for
SRU process reasons (see Procedure [1], item 4), could you please
clarify that in the changelog?
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
"The upload must have [...], and no other unrelated changes."
** Changed in: s390-tools-signed (Ubuntu Noble)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nettle in Ubuntu.
https://bugs.launchpad.net/bugs/2076340
Title:
SRU: no-change rebuild to pick up changed build flags on ppc64el and
s390x
Status in atlas package in Ubuntu:
New
Status in bzip2 package in Ubuntu:
Fix Released
Status in containerd-app package in Ubuntu:
New
Status in curl package in Ubuntu:
New
Status in cyrus-sasl2 package in Ubuntu:
New
Status in dbus package in Ubuntu:
Fix Released
Status in docker.io-app package in Ubuntu:
New
Status in dotnet8 package in Ubuntu:
New
Status in gnutls28 package in Ubuntu:
New
Status in golang-1.22 package in Ubuntu:
New
Status in icu package in Ubuntu:
Fix Released
Status in lapack package in Ubuntu:
Fix Released
Status in libdeflate package in Ubuntu:
New
Status in libseccomp package in Ubuntu:
Fix Released
Status in libzdnn package in Ubuntu:
Fix Released
Status in libzstd package in Ubuntu:
New
Status in lz4 package in Ubuntu:
New
Status in mysql-8.0 package in Ubuntu:
New
Status in nettle package in Ubuntu:
New
Status in openssh package in Ubuntu:
New
Status in openssl package in Ubuntu:
New
Status in p11-kit package in Ubuntu:
New
Status in postgresql-16 package in Ubuntu:
New
Status in postgresql-common package in Ubuntu:
New
Status in powerpc-utils package in Ubuntu:
Fix Released
Status in python-greenlet package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
New
Status in runc-app package in Ubuntu:
Fix Released
Status in rustc package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
New
Status in s390-tools-signed package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in util-linux package in Ubuntu:
New
Status in xz-utils package in Ubuntu:
New
Status in zlib package in Ubuntu:
New
Status in atlas source package in Noble:
Fix Committed
Status in bzip2 source package in Noble:
Fix Committed
Status in containerd-app source package in Noble:
Fix Committed
Status in curl source package in Noble:
Fix Committed
Status in cyrus-sasl2 source package in Noble:
Fix Committed
Status in dbus source package in Noble:
Fix Committed
Status in docker.io-app source package in Noble:
Fix Committed
Status in dotnet8 source package in Noble:
Fix Committed
Status in gnutls28 source package in Noble:
Fix Committed
Status in golang-1.22 source package in Noble:
Fix Committed
Status in icu source package in Noble:
Fix Committed
Status in lapack source package in Noble:
Fix Committed
Status in libdeflate source package in Noble:
Fix Committed
Status in libseccomp source package in Noble:
Fix Committed
Status in libzdnn source package in Noble:
Fix Committed
Status in libzstd source package in Noble:
Fix Committed
Status in lz4 source package in Noble:
Fix Committed
Status in mysql-8.0 source package in Noble:
Fix Committed
Status in nettle source package in Noble:
Fix Committed
Status in openssh source package in Noble:
Fix Committed
Status in openssl source package in Noble:
Fix Committed
Status in p11-kit source package in Noble:
Fix Committed
Status in postgresql-16 source package in Noble:
Fix Committed
Status in postgresql-common source package in Noble:
Fix Committed
Status in powerpc-utils source package in Noble:
Fix Committed
Status in python-greenlet source package in Noble:
Fix Committed
Status in qemu source package in Noble:
Fix Committed
Status in runc-app source package in Noble:
Fix Committed
Status in rustc source package in Noble:
Fix Committed
Status in s390-tools source package in Noble:
Fix Committed
Status in s390-tools-signed source package in Noble:
Incomplete
Status in systemd source package in Noble:
Fix Committed
Status in util-linux source package in Noble:
Fix Committed
Status in xz-utils source package in Noble:
Fix Committed
Status in zlib source package in Noble:
Fix Committed
Bug description:
SRU: no-change rebuild to pick up changed build flags on ppc64el and
s390x
This is batch of packages that we want to rebuild to pick up the
changed build flags on ppc64el (LP: #2064539) and s390x
[Desktop-packages] [Bug 2071877] Re: Support sending AT commnad by mbim-cli for Compal WWAN module
Apparently, this is still waiting on actions to comment #5. If that is not the case (or once it is no longer the case), please clarify in a comment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2071877 Title: Support sending AT commnad by mbim-cli for Compal WWAN module Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libmbim source package in Noble: Incomplete Bug description: [ Impact ] * Add a service to make mbim-cli be able to send AT command to Compal WWAN module DW5826e through mbimcli [ Test Plan ] * On the platform with Compal SDX12 WWAN module with ID: usb:v413Cp8217 usb:v413Cp8218 * Open terminal Ctrl + Alt + t * Try command $ sudo mbimcli -d /dev/cdc-wdm0 -p --compal-query-at-command=AT * Output: AT OK * Without the patch it will show error: Unknown options --compal-query-at-command=AT [ Where problems could occur ] * It adds new mbim service for supporting Compal module, there is no existing service modification. * The mbim relies on transaction task to handle sending AT command to the modem. It will send the command asynchronously, if there is a bug or system issue in GLib, the AT command may not send to modem successfully. [ Other Info ] * Upstream commit: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/commit/c275e4f1422291b933464880c37bd9cfd14b5bca To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2071877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
The changes are not yet in the development release (Noble). Submitted MR [1] with noble series update + these changes. [1] https://code.launchpad.net/~mfo/ubuntu/+source/ubuntu- meta/+git/ubuntu-meta/+merge/455081 ** Merge proposal linked: https://code.launchpad.net/~mfo/ubuntu/+source/ubuntu-meta/+git/ubuntu-meta/+merge/455081 ** Also affects: ubuntu-meta (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: New => Confirmed ** Changed in: ubuntu-meta (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: ubuntu-meta (Ubuntu Noble) Status: New => Confirmed ** Changed in: ubuntu-meta (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: ubuntu-meta (Ubuntu Noble) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-meta source package in Noble: Confirmed Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
Updated regression potential with theoretical issues, and other info with status in main for protection-domain-mapper and qrtr. ** Description changed: [ Impact ] - * ubuntu-seeds were changed since last meta update - * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release + * ubuntu-seeds were changed since last meta update + * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] - * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to + * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] - * This is automatically generated change + * This is automatically generated change based on ubuntu-seeds commit + [1]. + + * Theoretically, regressions would occur if new desktop-minimal-recommends +dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): +- have issues on install during release-upgrade; +- have issues on regular system usage (after installed). [ Other Info ] - - * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image + + * ubuntu-meta was not uploaded during final freeze, to prevent + rebuilding all images as changes affect arm64 only, which is a brand new + release image + + [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu- + seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a ** Description changed: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. - * Theoretically, regressions would occur if new desktop-minimal-recommends -dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): -- have issues on install during release-upgrade; -- have issues on regular system usage (after installed). + * Theoretically, regressions would occur if new desktop-minimal-recommends + dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): + - have issues on install during release-upgrade; + - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image + * protection-domain-mapper and qrtr moved from universe to main in Mantic. + * flash-kernel is/was already in main. + [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a ** Description changed: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image - * protection-domain-mapper and qrtr moved from universe to main in Mantic. - * flash-kernel is/was already in main. + * protection-domain-mapper [2] and qrtr moved from universe to main in Mantic. + * flash-kernel is/was already in main. - [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu- - seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a + [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a + [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory + [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package i
[Desktop-packages] [Bug 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
** Description changed: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image - * protection-domain-mapper [2] and qrtr moved from universe to main in Mantic. + * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-meta source package in Noble: Confirmed Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
** Changed in: ubuntu-meta (Ubuntu Noble) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Fix Committed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-meta source package in Noble: Fix Committed Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
Marking Noble as Fix Released (11.6.3-1). $ git log --oneline -1 pkg/ubuntu/noble | cat 03517080d29d 11.6.3-1 (patches unapplied) $ git show pkg/ubuntu/noble -- libqpdf/QPDFTokenizer.cc ** Changed in: qpdf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Fix Released Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Fix Released Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and consistent contributor who has made may improvements to qpdf's performance. The fix follows the established pattern of how to handle instances in which a character triggers a state change a
[Desktop-packages] [Bug 2039804] Re: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits
Happy to (in addition to comment #19) confirm that qpdf + libqpdf29 from noble-release and mantic/lunar-proposed fix the issue. noble: --- $ lsb_release -cs No LSB modules are available. noble $ wget -q https://github.com/qpdf/qpdf/files/12885974/018.pdf $ sudo apt update && sudo apt install -y qpdf $ dpkg -s qpdf | grep Version: Version: 11.6.3-1 $ qpdf --check 018.pdf checking 018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect mantic: --- $ lsb_release -cs No LSB modules are available. mantic $ wget -q https://github.com/qpdf/qpdf/files/12885974/018.pdf $ sudo apt update && sudo apt install -y qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.5.0-1 Version: 11.5.0-1 $ qpdf --check 018.pdf WARNING: 018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: 018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: 018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: 018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: 018.pdf: file is damaged WARNING: 018.pdf (offset 110267): xref not found WARNING: 018.pdf: Attempting to reconstruct cross-reference table qpdf: 018.pdf: unable to find trailer dictionary while recovering damaged file $ sudo add-apt-repository -yp proposed $ sudo apt install -y -t mantic-proposed qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.5.0-1ubuntu1 Version: 11.5.0-1ubuntu1 $ qpdf --check 018.pdf checking 018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect lunar: --- $ lsb_release -cs lunar $ wget -q https://github.com/qpdf/qpdf/files/12885974/018.pdf $ sudo apt update && sudo apt install -y qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.3.0-1 Version: 11.3.0-1 $ qpdf --check 018.pdf WARNING: 018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: 018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: 018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: 018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: 018.pdf: file is damaged WARNING: 018.pdf (offset 110267): xref not found WARNING: 018.pdf: Attempting to reconstruct cross-reference table qpdf: 018.pdf: unable to find trailer dictionary while recovering damaged file $ sudo add-apt-repository -yp proposed $ sudo apt install -y -t lunar-proposed qpdf $ dpkg -s qpdf libqpdf29 | grep Version: Version: 11.3.0-1ubuntu1 Version: 11.3.0-1ubuntu1 $ qpdf --check 018.pdf checking 018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Fix Released Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Fix Released Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
Summary for Mantic SRUs. There are 3 LP bugs combined in mantic-proposed (list sorted by package version so it's helpful). 1) Bug 2034986, used twice, 1A) First for 1:23.10.9, for 'fix v1': * Temporary font for Ubuntu MATE (LP: #2034986) It's released to mantic-updates with 1:23.10.10 (fix for autopkgtests). 1B) Later for 1:23.10.11, for XDG_CURRENT_DESKTOP: * do-release-upgrade: pass XDG_CURRENT_DESKTOP env var (LP: #2034986) It's reverted in 1:23.10.12: * Temporarily revert "do-release-upgrade: pass XDG_CURRENT_DESKTOP env var" and reapplied in 1:23.10.13: * do-release-upgrade: pass XDG_CURRENT_DESKTOP env var (LP: #2034986) 2) Bug 2039356, used for 'fix v2' in 1:23:10.12: * Adjustments of unreadable text workaround (LP: #2039356) 3) Bug 2039172, used for an unrelated quirk: * DistUpgradeQuirks: prevent upgrades on BIOS systems with XFS /boot (LP: #2039172) ... So, for verification, we have to consider 1:23.10.11 up to .14. .11 doesn't need verification, as it's reverted in .12 .12 is verified (comment #65 / bug 2039356 comment #3) .13 is not yet verified (comment #65, #66) .14 is verified, but pending questions (bug 2039172 comment #9) Thus, it seems what is pending for releasing mantic-proposed is verification for .13 (that I'm happy to do synthetically), plus a question for .14 (I'd be be happy to help, if needed). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Releas
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
Verification (synthetic) of the XDG_SESSION_TYPE fix in Mantic:
$ lsb_release -cs
No LSB modules are available.
mantic
The packages are downloaded from Launchpad librarian
since previous versions are not available in archive.
Before the fix (reverted) // 1:23.10.12
---
The XDG_CURRENT_DESKTOP variable IS NOT passed in `pkexec ... --env=`.
$ wget https://launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/1:23.10.12/+build/26929436/+files/{ubuntu-release-
upgrader-{core,gtk},python3-distupgrade}_23.10.12_all.deb
$ sudo apt install -y ./ubuntu-release-upgrader-
core_23.10.12_all.deb ./ubuntu-release-upgrader-gtk_23.10.12_all.deb
./python3-distupgrade_23.10.12_all.deb
$ dpkg -s ubuntu-release-upgrader-core | grep Version:
Version: 1:23.10.12
$ export XDG_CURRENT_DESKTOP=just:testing
$ strace -s 128 do-release-upgrade -d -f DistUpgradeViewGtk3 2>&1 |
grep '^execve("/usr/bin/pkexec"' | grep -o -- '--env=[^"]\+'
--env=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,XDG_SESSION_TYPE=tty
After the fix (reapplied) // 1:23.10.13
---
The XDG_CURRENT_DESKTOP variable IS passed in `pkexec ... --env=`.
$ wget https://launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/1:23.10.13/+build/26932072/+files/{ubuntu-release-
upgrader-{core,gtk},python3-distupgrade}_23.10.13_all.deb
$ sudo apt install -y ./ubuntu-release-upgrader-
core_23.10.13_all.deb ./ubuntu-release-upgrader-gtk_23.10.13_all.deb
./python3-distupgrade_23.10.13_all.deb
$ dpkg -s ubuntu-release-upgrader-core | grep Version:
Version: 1:23.10.13
$ export XDG_CURRENT_DESKTOP=just:testing
$ strace -s 128 do-release-upgrade -d -f DistUpgradeViewGtk3 2>&1 |
grep '^execve("/usr/bin/pkexec"' | grep -o -- '--env=[^"]\+'
--env=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,XDG_SESSION_TYPE=tty,XDG_CURRENT_DESKTOP=just:testing
Latest version (mantic-proposed) // 1:23.10.14
---
The XDG_CURRENT_DESKTOP variable IS passed in `pkexec ... --env=`.
$ sudo add-apt-repository -yp proposed
$ sudo apt install -y -t mantic-proposed ubuntu-release-
upgrader-core
$ dpkg -s ubuntu-release-upgrader-core | grep Version:
Version: 1:23.10.14
$ strace -s 128 do-release-upgrade -d -f DistUpgradeViewGtk3 2>&1 |
grep '^execve("/usr/bin/pkexec"' | grep -o -- '--env=[^"]\+'
--env=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,XDG_SESSION_TYPE=tty,XDG_CURRENT_DESKTOP=just:testing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986
Title:
some text became unreadable during a distribution upgrade
Status in Cinnamon:
New
Status in Ubuntu MATE:
New
Status in ubuntu-meta package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
Fix Released
Status in ubuntu-meta source package in Mantic:
Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
Fix Committed
Bug description:
[ Impact ]
* On Ubuntu Mate with the Lunar series, when running
ubuntu-release-upgrader, the displayed font of running
applications (including the upgrader) becomes very corrupted.
* This is not just a display problem, it is also a functional one.
The release upgrader will have text corrupted to the point
where a dialog asks a decision, and displays two buttons, but the
text is unreadable and one has to guess which button is the one
that carries out their desired action.
* In the early parts of the upgrader tool, users are told in bold:
"To prevent data loss close all open applications and documents."
This is just before the "Start Upgrade" button is available.
But they may not do so. Many applications may have a corrupted
font.
* To address this, an additional environment variable is being
passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
critical criteria for making the Mate version of the fix work.
* Also in the change are
* an update to tests
* from pre-build.sh
* an update of the mirrors.cfg, adding and removing several
mirrors
* a refresh of the po files
[ Test Plan ]
* acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64
* as user, run "update-manager -d"
* monitor the "Distribution Upgrade" screen. During the "Installing
the upgrades" step (and mind that this step will be long), observe
the text of the "Distribution Upgrade" screen and verify that the
font does not corrupt.
* Repeat the above for Ubuntu Desktop
[ Where problems could occur ]
* We are changing, at release time, ubuntu-release u
[Desktop-packages] [Bug 2044019] Re: [SRU] libreoffice 7.6.3 for mantic
Hi Rico,
Thanks for the nice and detailed SRU template, and all the testing.
While looking at this, particularly the changes in the packaging,
there are a few points that seem to warrant clarification, since
are apparently not related/supporting the upstream bug fixes, or
are not justified as to why included in a SRU (ie, which issues
or bugs are being addressed).
I checked most of these points with Andreas yesterday, and he too
agreed more details would be required before proceeding with this.
Could please address the points below? That's very appreciated.
Thanks again for all the effort on this!
cheers,
Mauricio
...
Changes:
$ debdiff libreoffice_7.6.2-0ubuntu1.dsc
libreoffice_7.6.3-0ubuntu0.23.10.1.dsc | filterdiff -i '*/debian/*'
There are some changes in debian/ that may warrant some clarification
as they do not fit into the SRU policy for minor release updates
(ie, bug-fix only) or to be related to the bugs fixed by upstream
(ie, to support a bug-fix).
I've looked for similarities in the changelog of previous releases,
but apparently haven't found them as precedents. This is the first
time I'm looking at this package, so I might be missing something.
I'll note specific changes in changelog/rules below, for clarity.
1)
d/changelog
18 +- don't try to install dbreport config modules into
19 + -uiconfig-report-builder if the report builder is disabled
d/rules
413 +ifeq "$(ENABLE_REPORTBUILDER)" "y"
414 mv
$(PKGDIR)-common/$(OODIR)/share/config/soffice.cfg/modules/dbreport \
415
$(PKGDIR)-uiconfig-report-builder/$(OODIR)/share/config/soffice.cfg/modules
416 +else
417 + rm -rf
$(PKGDIR)-common/$(OODIR)/share/config/soffice.cfg/modules/dbreport
418 +endif
Is this possibly a separate bug, as apparently it's not related to
an upstream bug fix; it would be nice to have some clarification.
Maybe this is covered in the SRU policy under "it is also acceptable to
upload new microreleases with many bug fixes without individual
Launchpad bugs for each of them", but I considered such 'many bug fixes'
to be related to the upstream bugs, and this change is on packaging.
2)
d/changelog
20 +- switch OOO_BASE_ARCHS/OOO_REPORTBUILDER_ARCHS variables
21 + (build base on all architectures instead of Java architectures
22 + and report-builder-* only on archs where Java is enabled, not on
23 + "all base archs"); there's -sdbc-{mysql,postgresql,firebird} anyway
d/rules
356 -OOO_BASE_ARCHS := $(OOO_JAVA_ARCHS)
357 +OOO_BASE_ARCHS := $(OOO_ARCHS)
358 $(eval $(call gen_no_archs,OOO_BASE_ARCHS))
359 -OOO_REPORTBUILDER_ARCHS := $(OOO_BASE_ARCHS)
360 +OOO_REPORTBUILDER_ARCHS := $(OOO_JAVA_ARCHS)
Similarly; it would be nice to have some clarification,
and perhaps explain the trailing note about '-sdbc-* anyway'.
3)
d/changelog
24 +- don't try to build Jar_{OOoRunner,test,ConnectivityTools} if Java is
25 + disabled as an extra safety net (instead of checking for junit only)
Similary, it would be nice to have some clarification.
d/rules
399 -ifeq "$(BUILD_TEST_PACKAGES)" "y"
400 - ifeq "$(ENABLE_JUNIT4)" "y"
401 +ifeq "$(ENABLE_JAVA)" "y"
402 + ifeq "$(BUILD_TEST_PACKAGES)" "y"
403 +ifeq "$(ENABLE_JUNIT4)" "y"
404 PATH=$(BUILD_PATH) LD_LIBRARY_PATH=$(BUILD_LD_LIBRARY_PATH)
ARCH_FLAGS=$(ARCH_FLAGS) TMP=`mktemp -q -d` $(MAKE) Jar_{OOoRunner,tes
t,ConnectivityTools}
405 +endif
4)
d/changelog
26 +- re-enable cmis; bump libcmis build-dep to >= 0.6.1
Similarly; it would be nice to have some clarification.
And also the reason to enable it in an SRU? Maybe some relation to
an upstream bug or ubuntu bug? Any changes at behavior/runtime?
(apparently just an internal build dep; why is this needed, and
isn't the archive version (older) sufficient?)
d/rules
343 @@ -356,7 +356,7 @@
344 DICT_DIR=/usr/share/hunspell
345 HYPH_DIR=/usr/share/hyphen
346 THES_DIR=/usr/share/mythes
347 -ENABLE_LIBCMIS=n
348 +ENABLE_LIBCMIS=y
386 @@ -1423,7 +1429,7 @@
387endif
388ifeq "$(ENABLE_LIBCMIS)" "y"
389 ifneq (,$(filter libcmis, $(SYSTEM_STUFF)))
390 - BUILD_DEPS += , libcmis-dev (>= 0.5.2~), libcmis-dev (<< 0.6~)
391 + BUILD_DEPS += , libcmis-dev (>= 0.6.1~), libcmis-dev (<< 0.7~)
392 endif
393else
394 CONFIGURE_FLAGS += --disable-libcmis
5)
27 +- build against libcurl4-openssl-dev instead of gnutls
334 @@ -271,7 +271,7 @@
335 USE_GSTREAMER=y
336 endif
337 ENABLE_CURL=y
338 -CURL_SECTYPE=gnutls
339 +CURL_SECTYPE=openssl
Similarly; it would be nice to have some clarification on its reason,
and potential changes to runtime behavior or functionality.
This is a significant change.
6)
30 + * debian/control.ure.in:
31 +- make ure-java actutally Architecture: %OOO_JAVA_ARCHS%
Similarly, it would be nice to have some clarification.
** Changed in: libreoffice (Ubuntu Mantic)
Status: In Progress => Incomplete
--
You received this bug notification because
[Desktop-packages] [Bug 2044019] Re: [SRU] libreoffice 7.6.3 for mantic
Hi Rico,
Thanks for the clarifications!
> 1) 2) 3) 6) are packaging bugs regarding Java support
> Those are needed to allow Java support to be disabled on specific archs if
> needed.
> Fortunately this wasn't required yet while the already applied mitigations to
> the bridgetests still are sufficient.
So, it does look like this is not _required_ right now, correct?
(i.e., no archs are getting Java support disabled in this SRU.)
I take this from your comment ("if needed" and "wasn't required yet")
_and_ `d/rules` assignments of OOO_BASE_ARCHS and OOO_REPORTBUILDER_ARCHS,
which remain the same value ("amd64 arm64 armhf ppc64el riscv64 s390x").
In this case, I guess such changes should not be included in this SRU,
but left for when it is actually needed; maybe others can comment too.
And perhaps a separate bug report with more details would be recommended,
but please do not work on this at the moment, while others don't comment.
> 4) 5) follow the upstream CMIS changes
> Upstream bumped the internal requirement of libcmis which finally allows the
> proper CMIS service support.
> Unfortunately it had to be disabled before because it was broken.
Understood.
I reviewed some of the docs/changes related to this, and this scenario
is more complex, since this (CMIS support) is a feature, with different
considerations for SRU (e.g., support in LTS and newer interim releases).
I'll have to ask for others with more experience in such case to comment,
but these are some thoughts for now:
CMIS is a standard related to a feature for opening/saving files on remote
servers [1].
"LibreOffice supports many document servers ... that implement the OASIS CMIS
standard."
[1] https://help.libreoffice.org/7.6/en-US/text/shared/guide/cmis-
remote-files.html
In general, features only land in the development release, until feature freeze
[2],
but there are cases for stable releases as well, when considering LTS releases:
[3]
[2] https://wiki.ubuntu.com/FeatureFreeze
[3] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
"""
For Long Term Support releases we sometimes want to introduce new features.
...
To avoid regressions on upgrade, any such feature must then also be added to
any newer supported Ubuntu release.
...
For new upstream versions of packages which provide new features, but don't fix
critical bugs, a backport should be requested instead.
"""
So, theoretically, enabling CMIS in Mantic could meet the requirement to have it
in Jammy, and it is (jammy-updates 1:7.3.7-0ubuntu0.22.04.3 has ENABLE_CMIS=y).
It just turns out to be disabled in Lunar (lunar-updates
4:7.5.8-0ubuntu0.23.04.1
has ENABLE_LIBCMIS=n, I guess it might be due to issues/broken as you
mentioned?),
so there's some intermediary release with it disabled.
> (continuing)
> Upstream chose Openssl as official choice for this feature/combination which
> was followed here.
> But it would be possible to continue using gnutls if the SRU requires it.
Ack, thanks for clarifying.
In this case, if libcurl4-gnutls/openssl were only being used due to
ENABLE_CMIS,
which is disabled in mantic-release, then maybe we could change it, as it would
be
effectively the only usage of it.
But it turns out it's apparently already used due to ENABLE_WEBDAV, so changing
it
would affect something already present in mantic-release, so at least initially,
keeping it as-is sounds better -- unless there's an upstream rationale that
gives
good reasons for switching, sure (and assessing/dealing with the change in
Mantic).
I'll ask for an additional review on these points.
Thanks again for all your work on this SRU and its review!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2044019
Title:
[SRU] libreoffice 7.6.3 for mantic
Status in libreoffice package in Ubuntu:
Fix Released
Status in libreoffice source package in Mantic:
Incomplete
Bug description:
[Impact]
* LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line:
https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release
* Version 7.6.2 is currently released in mantic. For a list of fixed bugs
compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3
(that's a total of 116 bugs):
https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs
7.6.3 RC2 is identical to the 7.6.3 release
* Given the nature of the project, the complexity of the codebase and
the high level of quality assurance upstream, it is preferable to SRU
a minor release rather than cherry-pick selected bug fixes.
[Testing]
* Upstream testing. Bugs fixed upstream typically include
unit/regression tests, and the release itself is extensively exercised
(both in an automated manner and manually).
* A recent set of upstr
[Desktop-packages] [Bug 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
Verification done on mantic-proposed. On arm64 with ubuntu-desktop-minimal installed, running do-release-upgrade from lunar to mantic (with mantic-proposed enabled and pinning setup) does install `protection-domain-mapper` and `qrtr-tools` (`flash-kernel` already installed). Test Steps: --- Part 1) - launch aws arm64 instance with Ubuntu 22.04/jammy Part 2) - do-release-upgrade to 22.10/lunar - install ubuntu-desktop-minimal - enable lunar-proposed (converted to mantic-proposed in do-release-upgrade later) Part 3) - set pin priority for mantic-proposed/ubuntu-desktop-minimal - do-release-upgrade to 23.04/mantic Details: --- Start on Jammy: $ lsb_release -cs jammy $ dpkg --print-architecture arm64 $ uname -m aarch64 $ sudo apt update && sudo apt -y dist-upgrade && sudo reboot Upgrade to Lunar: $ sudo sed -i 's/^Prompt=.*/Prompt=normal/' -i /etc/update-manager/release-upgrades $ do-release-upgrade Checking for a new Ubuntu release = Welcome to Ubuntu 23.04 'Lunar Lobster' = ... $ lsb_release -cs No LSB modules are available. lunar Prepare for testing: $ sudo apt install -y ubuntu-desktop-minimal Test/Before: (only 1 out of 3 packages installed) $ dpkg -s flash-kernel protection-domain-mapper qrtr-tools | grep -e Package: -e Version: dpkg-query: package 'protection-domain-mapper' is not installed and no information is available dpkg-query: package 'qrtr-tools' is not installed and no information is available Use dpkg --info (= dpkg-deb --info) to examine archive files. Package: flash-kernel Version: 3.106ubuntu14 Enable -proposed: $ sudo add-apt-repository -yp proposed cat
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
It looks like this wasn't needed in practice; marking as Won't Fix.
** Changed in: ghostscript (Ubuntu Xenial)
Status: In Progress => Won't Fix
** Changed in: ghostscript (Ubuntu Xenial)
Importance: Medium => Undecided
** Changed in: ghostscript (Ubuntu Xenial)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
** Changed in: ghostscript (Ubuntu Bionic)
Status: In Progress => Won't Fix
** Changed in: ghostscript (Ubuntu Bionic)
Importance: Medium => Undecided
** Changed in: ghostscript (Ubuntu Bionic)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1848210
Title:
ghostscript: ensure update of cups-filter
Status in cups-filters package in Ubuntu:
Invalid
Status in ghostscript package in Ubuntu:
Fix Released
Status in cups-filters source package in Xenial:
Invalid
Status in ghostscript source package in Xenial:
Won't Fix
Status in cups-filters source package in Bionic:
Invalid
Status in ghostscript source package in Bionic:
Won't Fix
Bug description:
[Impact]
* After an update of ghostscript but not cups-filters
users may hit errors printing PDF files (LP#1828401).
* This is possible as Landscape does not consider the
-security pocket (has both ghostscript/cups-filters)
but rather USN notices and ghostscript had a notice [0].
The regression on cups-filters was identified later,
and doesn't warrant a USN notice.
* So, to ensure that ghostscript and cups-filters are
both updated, add a versioned 'Breaks:' relationship
to ghostscript for older cups-filters versions which
are not yet fixed.
Per Debian Policy [1]:
"""
Normally a Breaks entry will have an “earlier than” version clause;
such a Breaks is introduced in the version ... [that] reveals a bug
in earlier versions of the broken package ...
This use of Breaks will inform higher-level package management tools
that the broken package must be upgraded before the new one.
"""
* A versioned 'Depends:' relationship is not possible
as ghostscript doesn't depend on cups-filters, thus
it's possible to have ghostscript installed without
cups-filters at all.
* This doesn't fix the current situation with Landscape
and USNs so this same problem might still occur again,
but at least it is already in place on future updates.
[Test Case]
* Install cups-filters version without fix for LP#1828401:
1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.
* Update ghostscript to/later than fix for CVE-2019-3839-1/-2
9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.
* Notice it does _not_ update cups-filters to version with fix:
1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.
* $ wget -O ppd-with-pdf-support.ppd \
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1'
* $ wget -O dummy.pdf \
https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf
* $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
...
Filetype: PDF
GPL Ghostscript 9.26: Unrecoverable error, exit code 1
Process is dying with "Unable to determine number of pages, page count: -1
", exit stat 3
...
* Note it's broken.
* Install ghostscript (test) packages with the relationships
'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.
* Note it _does_ update cups-filters to version with fix.
* $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
...
Filetype: PDF
File contains 1 pages
Starting renderer with command: <...>
...
* Note it's now working.
[Regression Potential]
* Low. This only causes an update to cups-filters to a version
that fixes an already identified/resolved problem (LP#1828401),
which is available in bionic- & xenial-updates since May 2019.
[Other Info]
* This is only required in Xenial and Bionic.
* Trusty doesn't have the ghostscript update that causes the problem.
* Disco/Eoan have the cups-filters fix that it requires (1.22.5+).
[Links]
[0] https://usn.ubuntu.com/3970-1/
[1]
https://www.debian.org/doc/debian-policy/ch-relationships.html#packages-which-break-other-packages-breaks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1848210/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848210] [NEW] ghostscript: add Breaks: relationship to cups-filter
Public bug reported: Add a Breaks: relationship to cups-filter to prevent LP#1828401. Landscape allows packages updates to only USNs, so ghostscript can be updated to a version that breaks the older cups-filters. Patches to be provided shortly. ** Affects: ghostscript (Ubuntu) Importance: Undecided Status: Invalid ** Affects: ghostscript (Ubuntu Xenial) Importance: Medium Assignee: Mauricio Faria de Oliveira (mfo) Status: In Progress ** Affects: ghostscript (Ubuntu Bionic) Importance: Medium Assignee: Mauricio Faria de Oliveira (mfo) Status: In Progress ** Tags: sts ** Also affects: ghostscript (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ghostscript (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ghostscript (Ubuntu) Status: New => Invalid ** Changed in: ghostscript (Ubuntu Xenial) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: ghostscript (Ubuntu Bionic) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: ghostscript (Ubuntu Bionic) Status: New => In Progress ** Changed in: ghostscript (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: add Breaks: relationship to cups-filter Status in ghostscript package in Ubuntu: Invalid Status in ghostscript source package in Xenial: In Progress Status in ghostscript source package in Bionic: In Progress Bug description: Add a Breaks: relationship to cups-filter to prevent LP#1828401. Landscape allows packages updates to only USNs, so ghostscript can be updated to a version that breaks the older cups-filters. Patches to be provided shortly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848210] Re: ghostscript: add breaks relationship to cups-filter
** Changed in: ghostscript (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: ghostscript (Ubuntu Bionic) Importance: Undecided => Medium ** Tags added: sts ** Summary changed: - ghostscript: add breaks relationship to cups-filter + ghostscript: add Breaks: relationship to cups-filter -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: add Breaks: relationship to cups-filter Status in ghostscript package in Ubuntu: Invalid Status in ghostscript source package in Xenial: In Progress Status in ghostscript source package in Bionic: In Progress Bug description: Add a Breaks: relationship to cups-filter to prevent LP#1828401. Landscape allows packages updates to only USNs, so ghostscript can be updated to a version that breaks the older cups-filters. Patches to be provided shortly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
** Summary changed: - ghostscript: add Breaks: relationship to cups-filter + ghostscript: ensure update of cups-filter -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in ghostscript package in Ubuntu: Invalid Status in ghostscript source package in Xenial: In Progress Status in ghostscript source package in Bionic: In Progress Bug description: Add a Breaks: relationship to cups-filter to prevent LP#1828401. Landscape allows packages updates to only USNs, so ghostscript can be updated to a version that breaks the older cups-filters. Patches to be provided shortly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
** Description changed: - Add a Breaks: relationship to cups-filter to prevent LP#1828401. + [Impact] - Landscape allows packages updates to only USNs, so ghostscript - can be updated to a version that breaks the older cups-filters. + * After an update of ghostscript but not cups-filters +(which is possible, including via Landscape tooling) +users may hit errors printing PDF files (LP#1828401). - Patches to be provided shortly. + * Landscape allows packages updates to USN-only thus +ghostscript is updated for CVE-2019-3839-1 and -2 +(version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) +which may break printing PDF files on cups-filters. + + * So, to ensure that ghostscript and cups-filters are +both updated, add a versioned 'Breaks:' relationship +to ghostscript for older cups-filters versions which +are not yet fixed. + + * A versioned 'Depends:' relationship is not possible +as ghostscript doesn't depend on cups-filters, thus +it's possible to have ghostscript installed without +cups-filters at all. + + [Test Case] + + * Install cups-filters version without fix for LP#1828401: +1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. + + * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 +9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. + + * Notice it does _not_ update of cups-filters. + + * $ wget -O ppd-with-pdf-support.ppd \ + 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' + + * $ wget -O dummy.pdf \ + https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf + + * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf +... +Filetype: PDF +GPL Ghostscript 9.26: Unrecoverable error, exit code 1 +Process is dying with "Unable to determine number of pages, page count: -1 +", exit stat 3 +... + + * Note it's broken. + + * Install ghostscript (test) packages with the relationships +'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or +'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. + + * Note it _does_ update cups-filters. + + * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf +... +Filetype: PDF +File contains 1 pages +Starting renderer with command: <...> +... + + * Note it's now working. + + [Regression Potential] + + * Low. This only causes an update to cups-filters to a version +that fixes an already identified/resolved problem (LP#1828401), +which is available in bionic- & xenial-updates since May 2019. ** Description changed: [Impact] - * After an update of ghostscript but not cups-filters -(which is possible, including via Landscape tooling) -users may hit errors printing PDF files (LP#1828401). + * After an update of ghostscript but not cups-filters + (which is possible, including via Landscape tooling) + users may hit errors printing PDF files (LP#1828401). - * Landscape allows packages updates to USN-only thus -ghostscript is updated for CVE-2019-3839-1 and -2 -(version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) -which may break printing PDF files on cups-filters. + * Landscape allows packages updates to USN-only thus + ghostscript is updated for CVE-2019-3839-1 and -2 + (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) + which may break printing PDF files on cups-filters. - * So, to ensure that ghostscript and cups-filters are -both updated, add a versioned 'Breaks:' relationship -to ghostscript for older cups-filters versions which -are not yet fixed. + * So, to ensure that ghostscript and cups-filters are + both updated, add a versioned 'Breaks:' relationship + to ghostscript for older cups-filters versions which + are not yet fixed. - * A versioned 'Depends:' relationship is not possible -as ghostscript doesn't depend on cups-filters, thus -it's possible to have ghostscript installed without -cups-filters at all. + * A versioned 'Depends:' relationship is not possible + as ghostscript doesn't depend on cups-filters, thus + it's possible to have ghostscript installed without + cups-filters at all. [Test Case] - * Install cups-filters version without fix for LP#1828401: -1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. + * Install cups-filters version without fix for LP#1828401: + 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. - * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 -9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. + * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 + 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. - * Notice it does _not_ update of cups-filters. + * Notice it does _not_ update cups-filters to version with fix: +1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. - * $ wge
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
Testing on Bionic --- Files) $ wget -O ppd-with-pdf-support.ppd 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer =Brother-HL-1020&show=1' $ wget -O dummy.pdf https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf Test 0) Before updating ghostscript or cups-filters $ dpkg -s cups-filters ghostscript | grep ^Version: Version: 1.20.2-0ubuntu3 Version: 9.26~dfsg+0-0ubuntu0.18.04.8 $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... Test 1) After updating ghostscript (not cups-filters) $ dpkg -s cups-filters ghostscript | grep ^Version: Version: 1.20.2-0ubuntu3 Version: 9.26~dfsg+0-0ubuntu0.18.04.11 $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... Test 2) Checking before updating ghostscript with test package (thus cups-filters too) Checking update of cups-filters with apt: $ sudo apt install --dry-run ghostscript ... The following packages will be upgraded: cups-filters ghostscript libgs9 libgs9-common ... Inst cups-filters [1.20.2-0ubuntu3] (1.20.2-0ubuntu3.1 Ubuntu:18.04/bionic-updates, Ubuntu:18.04/bionic-security [amd64]) Inst ghostscript [9.26~dfsg+0-0ubuntu0.18.04.11] (9.26~dfsg+0-0ubuntu0.18.04.11+test20191510b1 mfo-sf246942:18.04/bionic [amd64]) [] ... Checking update of cups-filters with apt-get: $ sudo apt-get install --dry-run ghostscript ... The following packages will be upgraded: cups-filters ghostscript libgs9 libgs9-common ... Inst cups-filters [1.20.2-0ubuntu3] (1.20.2-0ubuntu3.1 Ubuntu:18.04/bionic-updates, Ubuntu:18.04/bionic-security [amd64]) Inst ghostscript [9.26~dfsg+0-0ubuntu0.18.04.11] (9.26~dfsg+0-0ubuntu0.18.04.11+test20191510b1 mfo-sf246942:18.04/bionic [amd64]) [] ... Test 3) After updating ghostscript with test package (thus cups-filters too) $ dpkg -s cups-filters ghostscript | grep ^Version: Version: 1.20.2-0ubuntu3.1 Version: 9.26~dfsg+0-0ubuntu0.18.04.11+test20191510b1 $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in ghostscript package in Ubuntu: Invalid Status in ghostscript source package in Xenial: In Progress Status in ghostscript source package in Bionic: In Progress Bug description: [Impact] * After an update of ghostscript but not cups-filters (which is possible, including via Landscape tooling) users may hit errors printing PDF files (LP#1828401). * Landscape allows packages updates to USN-only thus ghostscript is updated for CVE-2019-3839-1 and -2 (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) which may break printing PDF files on cups-filters. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cup
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
Test packages used for verification in comments #1 and #2 built successfully on all architectures, ppa:mfo/sf246942 [1]. [1] https://launchpad.net/~mfo/+archive/ubuntu/sf246942 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in ghostscript package in Ubuntu: Invalid Status in ghostscript source package in Xenial: In Progress Status in ghostscript source package in Bionic: In Progress Bug description: [Impact] * After an update of ghostscript but not cups-filters (which is possible, including via Landscape tooling) users may hit errors printing PDF files (LP#1828401). * Landscape allows packages updates to USN-only thus ghostscript is updated for CVE-2019-3839-1 and -2 (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) which may break printing PDF files on cups-filters. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
** Patch added: "lp1848210_bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297380/+files/lp1848210_bionic.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in ghostscript package in Ubuntu: Invalid Status in ghostscript source package in Xenial: In Progress Status in ghostscript source package in Bionic: In Progress Bug description: [Impact] * After an update of ghostscript but not cups-filters (which is possible, including via Landscape tooling) users may hit errors printing PDF files (LP#1828401). * Landscape allows packages updates to USN-only thus ghostscript is updated for CVE-2019-3839-1 and -2 (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) which may break printing PDF files on cups-filters. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
Testing on Xenial --- Files) $ wget -O ppd-with-pdf-support.ppd 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer =Brother-HL-1020&show=1' $ wget -O dummy.pdf https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf Test 0) Before updating ghostscript or cups-filters $ dpkg -s cups-filters ghostscript | grep ^Version: Version: 1.8.3-2ubuntu3.4 Version: 9.26~dfsg+0-0ubuntu0.16.04.8 $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... Test 1) After updating ghostscript (not cups-filters) $ dpkg -s cups-filters ghostscript | grep ^Version: Version: 1.8.3-2ubuntu3.4 Version: 9.26~dfsg+0-0ubuntu0.16.04.11 $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... Test 2) Checking before updating ghostscript with test package (thus cups-filters too) Checking update of cups-filters with apt-get and apt: $ sudo apt-get install --dry-run ghostscript ... The following packages will be upgraded: cups-filters cups-filters-core-drivers ghostscript libgs9 libgs9-common ... Inst cups-filters [1.8.3-2ubuntu3.4] (1.8.3-2ubuntu3.5 Ubuntu:16.04/xenial-updates, Ubuntu:16.04/xenial-security [amd64]) Inst ghostscript [9.26~dfsg+0-0ubuntu0.16.04.11] (9.26~dfsg+0-0ubuntu0.16.04.11+test20191510b1 mfo-sf246942:16.04/xenial [amd64]) [] ... $ sudo apt install --dry-run ghostscript ... The following packages will be upgraded: cups-filters cups-filters-core-drivers ghostscript libgs9 libgs9-common ... Inst cups-filters [1.8.3-2ubuntu3.4] (1.8.3-2ubuntu3.5 Ubuntu:16.04/xenial-updates, Ubuntu:16.04/xenial-security [amd64]) Inst ghostscript [9.26~dfsg+0-0ubuntu0.16.04.11] (9.26~dfsg+0-0ubuntu0.16.04.11+test20191510b1 mfo-sf246942:16.04/xenial [amd64]) [] ... Test 3) After updating ghostscript with test package (thus cups-filters too) $ dpkg -s cups-filters ghostscript | grep ^Version: Version: 1.8.3-2ubuntu3.5 Version: 9.26~dfsg+0-0ubuntu0.16.04.11+test20191510b1 $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in ghostscript package in Ubuntu: Invalid Status in ghostscript source package in Xenial: In Progress Status in ghostscript source package in Bionic: In Progress Bug description: [Impact] * After an update of ghostscript but not cups-filters (which is possible, including via Landscape tooling) users may hit errors printing PDF files (LP#1828401). * Landscape allows packages updates to USN-only thus ghostscript is updated for CVE-2019-3839-1 and -2 (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) which may break printing PDF files on cups-filters. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
** Patch added: "lp1848210_xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297381/+files/lp1848210_xenial.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in ghostscript package in Ubuntu: Invalid Status in ghostscript source package in Xenial: In Progress Status in ghostscript source package in Bionic: In Progress Bug description: [Impact] * After an update of ghostscript but not cups-filters (which is possible, including via Landscape tooling) users may hit errors printing PDF files (LP#1828401). * Landscape allows packages updates to USN-only thus ghostscript is updated for CVE-2019-3839-1 and -2 (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) which may break printing PDF files on cups-filters. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
** Description changed: [Impact] * After an update of ghostscript but not cups-filters (which is possible, including via Landscape tooling) users may hit errors printing PDF files (LP#1828401). * Landscape allows packages updates to USN-only thus ghostscript is updated for CVE-2019-3839-1 and -2 (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) which may break printing PDF files on cups-filters. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. + +Per Debian Policy [1]: + + """ + Normally a Breaks entry will have an “earlier than” version clause; + such a Breaks is introduced in the version ... [that] reveals a bug + in earlier versions of the broken package ... + + This use of Breaks will inform higher-level package management tools + that the broken package must be upgraded before the new one. + """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. + + [1] https://www.debian.org/doc/debian-policy/ch-relationships.html + #packages-which-break-other-packages-breaks ** Description changed: [Impact] * After an update of ghostscript but not cups-filters (which is possible, including via Landscape tooling) users may hit errors printing PDF files (LP#1828401). * Landscape allows packages updates to USN-only thus ghostscript is updated for CVE-2019-3839-1 and -2 (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) which may break printing PDF files on cups-filters. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. -Per Debian Policy [1]: + Per Debian Policy [1]: - """ - Normally a Breaks entry will have an “earlier than” version clause; - such a Breaks is introduced in the version ... [that] reveals a bug - in earlier versions of the broken package ... + """ + Normally a Breaks entry will have an “earlier than” version clause; + such a Breaks is introduced in the version ... [that] reveals a bug + in earlier versions of the broken package ... - This use of Breaks will inform higher-level package management tools - that the broken package must be upgraded before the new one. - """ + This use of Breaks will inform higher-level package management tools + that the broken package must be upgraded before the new one. + """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
** Description changed: [Impact] * After an update of ghostscript but not cups-filters - (which is possible, including via Landscape tooling) + (which is possible; eg unattended-upgrade/landscape) users may hit errors printing PDF files (LP#1828401). - * Landscape allows packages updates to USN-only thus + * Landscape and unattended-upgrade allows packages +updates to security updates / USN-only, thus ghostscript is updated for CVE-2019-3839-1 and -2 (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) which may break printing PDF files on cups-filters. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. Per Debian Policy [1]: """ Normally a Breaks entry will have an “earlier than” version clause; such a Breaks is introduced in the version ... [that] reveals a bug in earlier versions of the broken package ... This use of Breaks will inform higher-level package management tools that the broken package must be upgraded before the new one. """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. [Other Info] * This is only required in Xenial and Bionic. * Trusty doesn't have the ghostscript update that causes the problem. * Disco/Eoan have the cups-filters fix that it requires (1.22.5+). [1] https://www.debian.org/doc/debian-policy/ch-relationships.html #packages-which-break-other-packages-breaks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in ghostscript package in Ubuntu: Invalid Status in ghostscript source package in Xenial: In Progress Status in ghostscript source package in Bionic: In Progress Bug description: [Impact] * After an update of ghostscript but not cups-filters (which is possible; eg unattended-upgrade/landscape) users may hit errors printing PDF files (LP#1828401). * Landscape and unattended-upgrade allows packages updates to security updates / USN-only, thus ghostscript is updated for CVE-2019-3839-1 and -2 (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) which may break printing PDF files on cups-filters. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. Per Debian Policy [1]: """ Normally a Breaks entry will have an “earlier than” version clause; such a Breaks is introduced in the version ... [that] reveals a bug in earlier versions of the broken package ... This use of Breaks will inform higher-level package management tools that the broken package must be upgraded before the new one. """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
The approach to fix/deliver this is under discussion for a bit. We'll move forward once that's more clearly defined. ** Patch removed: "lp1848210_bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297380/+files/lp1848210_bionic.debdiff ** Patch removed: "lp1848210_xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297381/+files/lp1848210_xenial.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in ghostscript package in Ubuntu: Invalid Status in ghostscript source package in Xenial: In Progress Status in ghostscript source package in Bionic: In Progress Bug description: [Impact] * After an update of ghostscript but not cups-filters (which is possible; eg unattended-upgrade/landscape) users may hit errors printing PDF files (LP#1828401). * Landscape and unattended-upgrade allows packages updates to security updates / USN-only, thus ghostscript is updated for CVE-2019-3839-1 and -2 (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) which may break printing PDF files on cups-filters. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. Per Debian Policy [1]: """ Normally a Breaks entry will have an “earlier than” version clause; such a Breaks is introduced in the version ... [that] reveals a bug in earlier versions of the broken package ... This use of Breaks will inform higher-level package management tools that the broken package must be upgraded before the new one. """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. [Other Info] * This is only required in Xenial and Bionic. * Trusty doesn't have the ghostscript update that causes the problem. * Disco/Eoan have the cups-filters fix that it requires (1.22.5+). [1] https://www.debian.org/doc/debian-policy/ch-relationships.html #packages-which-break-other-packages-breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
** Description changed: [Impact] * After an update of ghostscript but not cups-filters - (which is possible; eg unattended-upgrade/landscape) +(which is possible) users may hit errors printing PDF files (LP#1828401). - - * Landscape and unattended-upgrade allows packages -updates to security updates / USN-only, thus - ghostscript is updated for CVE-2019-3839-1 and -2 - (version 9.26~dfsg+0-0ubuntu0.18.04.9 and 16.04.9) - which may break printing PDF files on cups-filters. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. Per Debian Policy [1]: """ Normally a Breaks entry will have an “earlier than” version clause; such a Breaks is introduced in the version ... [that] reveals a bug in earlier versions of the broken package ... This use of Breaks will inform higher-level package management tools that the broken package must be upgraded before the new one. """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. [Other Info] * This is only required in Xenial and Bionic. * Trusty doesn't have the ghostscript update that causes the problem. * Disco/Eoan have the cups-filters fix that it requires (1.22.5+). [1] https://www.debian.org/doc/debian-policy/ch-relationships.html #packages-which-break-other-packages-breaks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in cups-filters package in Ubuntu: New Status in ghostscript package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: New Status in ghostscript source package in Xenial: In Progress Status in cups-filters source package in Bionic: New Status in ghostscript source package in Bionic: In Progress Bug description: [Impact] * After an update of ghostscript but not cups-filters (which is possible) users may hit errors printing PDF files (LP#1828401). * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. Per Debian Policy [1]: """ Normally a Breaks entry will have an “earlier than” version clause; such a Breaks is introduced in the version ... [that] reveals a bug in earlier versions of the broken package ... This use of Breaks will inform higher-level package management tools that the broken package must be upgraded before the new one. """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Updat
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
** Description changed: [Impact] * After an update of ghostscript but not cups-filters -(which is possible) users may hit errors printing PDF files (LP#1828401). + + * This is possible as Landscape does not consider the +-security pocket (has both ghostscript/cups-filters) +but rather USN notices and ghostscript had a notice [0]. +The regression on cups-filters was identified later, +and doesn't warrant a USN notice. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. Per Debian Policy [1]: """ Normally a Breaks entry will have an “earlier than” version clause; such a Breaks is introduced in the version ... [that] reveals a bug in earlier versions of the broken package ... This use of Breaks will inform higher-level package management tools that the broken package must be upgraded before the new one. """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. + + * This doesn't fix the current situation with Landscape +and USNs so this same problem might still occur again, +but at least it is already in place on future updates. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. [Other Info] * This is only required in Xenial and Bionic. * Trusty doesn't have the ghostscript update that causes the problem. * Disco/Eoan have the cups-filters fix that it requires (1.22.5+). - [1] https://www.debian.org/doc/debian-policy/ch-relationships.html - #packages-which-break-other-packages-breaks + [Links] + + [0] https://usn.ubuntu.com/3970-1/ + [1] https://www.debian.org/doc/debian-policy/ch-relationships.html#packages-which-break-other-packages-breaks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in cups-filters package in Ubuntu: New Status in ghostscript package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: New Status in ghostscript source package in Xenial: In Progress Status in cups-filters source package in Bionic: New Status in ghostscript source package in Bionic: In Progress Bug description: [Impact] * After an update of ghostscript but not cups-filters users may hit errors printing PDF files (LP#1828401). * This is possible as Landscape does not consider the -security pocket (has both ghostscript/cups-filters) but rather USN notices and ghostscript had a notice [0]. The regression on cups-filters was identified later, and doesn't warrant a USN notice. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. Per Debian Policy [1]: """ Normally a Breaks entry will have an “earlier than” version clause; such a Breaks is introduced in the version ... [that] reveals a bug in earlier ver
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
After discussing this with Eric (slashd) and Marc (mdeslaur), it seems like the Breaks: approach is indeed the way to go. Nonetheless, it doesn't warrant an USN notice (security-only), which is the bit that could make Landscape (problem trigger) to pick up the new ghostscript fix then update cups-filters. So, we agreed on likely folding this fix/update into another SRU, as the impact to other audiences (non-Landscape) is small, because both ghostscript/cups-filters are on -security pocket. If other users are hit by this issue, we can sure enough revisit that option and consider some form to deliver it. cheers, Mauricio -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in cups-filters package in Ubuntu: Invalid Status in ghostscript package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: Invalid Status in ghostscript source package in Xenial: In Progress Status in cups-filters source package in Bionic: Invalid Status in ghostscript source package in Bionic: In Progress Bug description: [Impact] * After an update of ghostscript but not cups-filters users may hit errors printing PDF files (LP#1828401). * This is possible as Landscape does not consider the -security pocket (has both ghostscript/cups-filters) but rather USN notices and ghostscript had a notice [0]. The regression on cups-filters was identified later, and doesn't warrant a USN notice. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. Per Debian Policy [1]: """ Normally a Breaks entry will have an “earlier than” version clause; such a Breaks is introduced in the version ... [that] reveals a bug in earlier versions of the broken package ... This use of Breaks will inform higher-level package management tools that the broken package must be upgraded before the new one. """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. * This doesn't fix the current situation with Landscape and USNs so this same problem might still occur again, but at least it is already in place on future updates. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. [Other Info] * This is only required in Xenial and Bionic. * Trusty doesn't have the ghostscript update that causes the problem. * Disco/Eoan have the cups-filters fix that it requires (1.22.5+). [Links] [0] https://usn.ubuntu.com/3970-1/ [1] https://www.debian.org/doc/debian-policy/ch-relationships.html#packages-which-break-other-packages-breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1848210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
** Patch added: "lp1848210_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297503/+files/lp1848210_xenial.debdiff
** Changed in: cups-filters (Ubuntu)
Status: New => Invalid
** Changed in: cups-filters (Ubuntu Xenial)
Status: New => Invalid
** Changed in: cups-filters (Ubuntu Bionic)
Status: New => Invalid
** Changed in: cups-filters (Ubuntu Xenial)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
** Changed in: cups-filters (Ubuntu Bionic)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
** Changed in: cups-filters (Ubuntu Xenial)
Importance: Medium => Undecided
** Changed in: cups-filters (Ubuntu Bionic)
Importance: Medium => Undecided
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1848210
Title:
ghostscript: ensure update of cups-filter
Status in cups-filters package in Ubuntu:
Invalid
Status in ghostscript package in Ubuntu:
Fix Released
Status in cups-filters source package in Xenial:
Invalid
Status in ghostscript source package in Xenial:
In Progress
Status in cups-filters source package in Bionic:
Invalid
Status in ghostscript source package in Bionic:
In Progress
Bug description:
[Impact]
* After an update of ghostscript but not cups-filters
users may hit errors printing PDF files (LP#1828401).
* This is possible as Landscape does not consider the
-security pocket (has both ghostscript/cups-filters)
but rather USN notices and ghostscript had a notice [0].
The regression on cups-filters was identified later,
and doesn't warrant a USN notice.
* So, to ensure that ghostscript and cups-filters are
both updated, add a versioned 'Breaks:' relationship
to ghostscript for older cups-filters versions which
are not yet fixed.
Per Debian Policy [1]:
"""
Normally a Breaks entry will have an “earlier than” version clause;
such a Breaks is introduced in the version ... [that] reveals a bug
in earlier versions of the broken package ...
This use of Breaks will inform higher-level package management tools
that the broken package must be upgraded before the new one.
"""
* A versioned 'Depends:' relationship is not possible
as ghostscript doesn't depend on cups-filters, thus
it's possible to have ghostscript installed without
cups-filters at all.
* This doesn't fix the current situation with Landscape
and USNs so this same problem might still occur again,
but at least it is already in place on future updates.
[Test Case]
* Install cups-filters version without fix for LP#1828401:
1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.
* Update ghostscript to/later than fix for CVE-2019-3839-1/-2
9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.
* Notice it does _not_ update cups-filters to version with fix:
1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.
* $ wget -O ppd-with-pdf-support.ppd \
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1'
* $ wget -O dummy.pdf \
https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf
* $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
...
Filetype: PDF
GPL Ghostscript 9.26: Unrecoverable error, exit code 1
Process is dying with "Unable to determine number of pages, page count: -1
", exit stat 3
...
* Note it's broken.
* Install ghostscript (test) packages with the relationships
'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.
* Note it _does_ update cups-filters to version with fix.
* $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
...
Filetype: PDF
File contains 1 pages
Starting renderer with command: <...>
...
* Note it's now working.
[Regression Potential]
* Low. This only causes an update to cups-filters to a version
that fixes an already identified/resolved problem (LP#1828401),
which is available in bionic- & xenial-updates since May 2019.
[Other Info]
* This is only required in Xenial and Bionic.
* Trusty doesn't have the ghostscript update that causes the problem.
* Disco/Eoan have the cups-filters fix that it requires (1.22.5+).
[Links]
[0] https://usn.ubuntu.com/3970-1/
[1]
https://www.debian.org/doc/debian-policy/ch-relationships.html#packages-which-break-other-packages-breaks
To manage notifications about this bug go to:
https://bugs.launchpad.net
[Desktop-packages] [Bug 1848210] Re: ghostscript: ensure update of cups-filter
** Patch added: "lp1848210_bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297502/+files/lp1848210_bionic.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1848210 Title: ghostscript: ensure update of cups-filter Status in cups-filters package in Ubuntu: Invalid Status in ghostscript package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: Invalid Status in ghostscript source package in Xenial: In Progress Status in cups-filters source package in Bionic: Invalid Status in ghostscript source package in Bionic: In Progress Bug description: [Impact] * After an update of ghostscript but not cups-filters users may hit errors printing PDF files (LP#1828401). * This is possible as Landscape does not consider the -security pocket (has both ghostscript/cups-filters) but rather USN notices and ghostscript had a notice [0]. The regression on cups-filters was identified later, and doesn't warrant a USN notice. * So, to ensure that ghostscript and cups-filters are both updated, add a versioned 'Breaks:' relationship to ghostscript for older cups-filters versions which are not yet fixed. Per Debian Policy [1]: """ Normally a Breaks entry will have an “earlier than” version clause; such a Breaks is introduced in the version ... [that] reveals a bug in earlier versions of the broken package ... This use of Breaks will inform higher-level package management tools that the broken package must be upgraded before the new one. """ * A versioned 'Depends:' relationship is not possible as ghostscript doesn't depend on cups-filters, thus it's possible to have ghostscript installed without cups-filters at all. * This doesn't fix the current situation with Landscape and USNs so this same problem might still occur again, but at least it is already in place on future updates. [Test Case] * Install cups-filters version without fix for LP#1828401: 1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial. * Update ghostscript to/later than fix for CVE-2019-3839-1/-2 9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial. * Notice it does _not_ update cups-filters to version with fix: 1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial. * $ wget -O ppd-with-pdf-support.ppd \ 'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0&printer=Brother-HL-1020&show=1' * $ wget -O dummy.pdf \ https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Process is dying with "Unable to determine number of pages, page count: -1 ", exit stat 3 ... * Note it's broken. * Install ghostscript (test) packages with the relationships 'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or 'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial. * Note it _does_ update cups-filters to version with fix. * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf ... Filetype: PDF File contains 1 pages Starting renderer with command: <...> ... * Note it's now working. [Regression Potential] * Low. This only causes an update to cups-filters to a version that fixes an already identified/resolved problem (LP#1828401), which is available in bionic- & xenial-updates since May 2019. [Other Info] * This is only required in Xenial and Bionic. * Trusty doesn't have the ghostscript update that causes the problem. * Disco/Eoan have the cups-filters fix that it requires (1.22.5+). [Links] [0] https://usn.ubuntu.com/3970-1/ [1] https://www.debian.org/doc/debian-policy/ch-relationships.html#packages-which-break-other-packages-breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1848210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)
Christian, Thanks for handling this. > But the more that are affected the more I think then general solution in lightdm would be the right thing to do. Yes, that's my interpretation too -- and it was my impression from the beginning, with your report/analysis, as I couldn't find anything we were doing wrong with the useradd of a system account, and specially due to this documentation statement (comment #7): > [...] filters out those with UID values which are below a threshold point to screen out system users [...] Which does not cover the possible conditions for a system user (man 8 useradd): -r, --system Create a system account. System users will be created with no aging information in /etc/shadow, and their numeric identifiers are chosen in the SYS_UID_MIN-SYS_UID_MAX range, defined in /etc/login.defs, instead of UID_MIN-UID_MAX (and their GID counterparts for the creation of groups). Note that useradd will not create a home directory for such an user, regardless of the default setting in /etc/login.defs (CREATE_HOME). You have to specify the -m options if you want a home directory for a system account to be created. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1667113 Title: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types) Status in accountsservice package in Ubuntu: New Status in base-passwd package in Ubuntu: Invalid Status in ceph package in Ubuntu: Confirmed Status in ifmail package in Ubuntu: Confirmed Status in libvirt package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Status in netqmail package in Ubuntu: Confirmed Bug description: "Technical" user libvirt Qemu appears in the list of user in Ligthdm, among the real regular users. It probably shouldn't ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libvirt-bin 2.5.0-3ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Feb 22 22:09:24 2017 InstallationDate: Installed on 2017-02-01 (21 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201) KernLog: SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
