[Desktop-packages] [Bug 2054868] Re: invalid escape sequence
*** This bug is a duplicate of bug 2029480 ***
https://bugs.launchpad.net/bugs/2029480
** This bug has been marked a duplicate of bug 2029480
SyntaxWarnings with Python3.12
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2054868
Title:
invalid escape sequence
Status in hplip package in Ubuntu:
Confirmed
Bug description:
Todays update with python 3.12
/usr/share/hplip/base/LedmWifi.py:34: SyntaxWarning: invalid escape sequence
'\d
'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/device.py:49: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/g.py:304: SyntaxWarning: invalid escape sequence '\|'
spinner = "\|/-\|/-"
/usr/share/hplip/base/g.py:354: SyntaxWarning: invalid escape sequence '\d'
m = re.search('python(\d(\.\d){0,2})', ext_path)#get the python
ve
rsion where the .so file is found
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape
sequence '
\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape
sequence '
\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape
sequence '
\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/base/logger.py:439: SyntaxWarning: invalid escape sequence
'\<'
elem_start = re.findall("(\<\W{0,1}\w+) ?", line)[0]
/usr/share/hplip/base/logger.py:440: SyntaxWarning: invalid escape sequence
'\]'
elem_finished = re.findall("([?|\]\]]*\>)", line)[0]
/usr/share/hplip/base/logger.py:442: SyntaxWarning: invalid escape sequence
'\S'
attrs = re.findall("(\S*?\=\".*?\")", line)
/usr/share/hplip/base/models.py:37: SyntaxWarning: invalid escape sequence
'\d'
pat_prod_num = re.compile("""(\d+)""", re.I)
/usr/share/hplip/base/models.py:428: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:429: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:430: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:431: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:432: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-virgin', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:433: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-dvc', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:434: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:435: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:436: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-id', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:437: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-hp-ink', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:438: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-health-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:439: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-health$', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:440: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-known', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:441: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-level', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:442: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-ack', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:443: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:444: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^in-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:445: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^out-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:446: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^model(\d+)', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/password.py:212: SyntaxWarning: invalid escape
[Desktop-packages] [Bug 2028054] Re: [MIR] python-rlpycairo
As I said in comment #4 - The binary package libsane-hpaio DOES NOT depend on the binary package hplip, not even indirectly, so the binary package hplip can get demoted to Universe. the binary package printer-driver-hpcups also does not depend on the binary package hplip, but printer-driver-hpcups itself can already get demoted to Universe as we replace the printer drivers by Printer Application Snaps (this driver provided by the HPLIP Printer Application, hplip-printer-app). So hp-scan as part of the binary package hplip will go to Universe, hp-sendfax as part of the binary package hplip-gui is already in Universe. - Now, keeping CUPS as DEB packages for the time being, we continue with libsane-hpaio and printer-driver-hpcups in Main, but we can demote the binary package hplip into Universe, so the dependency on python- reportlab goes completely into Universe, eliminating the need of this MIR at least from the printing-stack side. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2028054 Title: [MIR] python-rlpycairo Status in hplip package in Ubuntu: Confirmed Status in python-reportlab package in Ubuntu: Incomplete Status in python-rlpycairo package in Ubuntu: Incomplete Bug description: python-rlpycairo is a new dependency of python-reportlab (currently owned by Foundations). The only consumer of python-reportlab is hplip (owned by Desktop), apparently it needs it for scanning: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=651240 $ reverse-depends src:python-reportlab -c main -r mantic Reverse-Depends === * hplip (for python3-reportlab) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x src:hplip -> src:python-reportlab -> src:python-rlpycairo -> src:freetype-py & src:ttf-bitstream-vera So from the above, it sounds like this new dependency is actually needed (after the reportlab package dropped its renderpm extension). It should be discussed between Foundations and Desktop who's owning those dependencies and doing the MIRs for python-rlpycairo, freetype- py and ttf-bitstream-vera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2028054/+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 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git
My upload got approved now: https://launchpad.net/ubuntu/+source/cups/2.4.7-1.2ubuntu7 This means that the package is in noble-proposed now. The autopkgtests of the package itself and its dependencies get run on all the 6 supported architectures. When they all pass, the package gets into noble-release, the actual release of Noble. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2060692 Title: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git Status in cups package in Ubuntu: Fix Committed Bug description: While checking out the latest versions of cups (2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5), I noticed that cupsd crashes consistently after closing my Firefox tab / window. The title of the crash (from the bug-report window) is "cupsd crashed with SIGSEGV in ???()" I'm running the noble-desktop-amd64.iso from 2024-03-25 after applying some updates from the noble and noble-proposed pockets. Reproduction steps: 1. Open Firefox and manage CUPS on http://localhost:631 2. Go to Administration -> Printers -> Add Printer and choose your printer 3. Add your printer (I used the ipps:// protocol to manage the printer) 4. After clicking the "Add printer" button, immediately close your Firefox tab 5. cupsd will crash and Ubuntu will display a bug-report popup Versions: Firefox - 124.0.1-1 r4033 CUPS - 2.4.7-1.2ubuntu5 Printer: Lexmark MS415dn (supported) I am unable to reproduce this bug on versions prior to 2.4.7-1.2ubuntu4 (Tried with 2.4.7-1.2ubuntu1 and 2.4.7-1.2ubuntu2). Versions 2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5 only backported commits from the 2.4.x upstream git branch, so I also opened an issue on GitHub: https://github.com/OpenPrinting/cups/issues/934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2060692/+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 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git
I have uploaded it, but starting from beta freeze until the final release all uploads have to be approved by the release team. As I have done the upload on Friday late at night (CEST) there was probably nobody of the release team around to pass this upload through. Probably this will happen only on Monday. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2060692 Title: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git Status in cups package in Ubuntu: Fix Committed Bug description: While checking out the latest versions of cups (2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5), I noticed that cupsd crashes consistently after closing my Firefox tab / window. The title of the crash (from the bug-report window) is "cupsd crashed with SIGSEGV in ???()" I'm running the noble-desktop-amd64.iso from 2024-03-25 after applying some updates from the noble and noble-proposed pockets. Reproduction steps: 1. Open Firefox and manage CUPS on http://localhost:631 2. Go to Administration -> Printers -> Add Printer and choose your printer 3. Add your printer (I used the ipps:// protocol to manage the printer) 4. After clicking the "Add printer" button, immediately close your Firefox tab 5. cupsd will crash and Ubuntu will display a bug-report popup Versions: Firefox - 124.0.1-1 r4033 CUPS - 2.4.7-1.2ubuntu5 Printer: Lexmark MS415dn (supported) I am unable to reproduce this bug on versions prior to 2.4.7-1.2ubuntu4 (Tried with 2.4.7-1.2ubuntu1 and 2.4.7-1.2ubuntu2). Versions 2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5 only backported commits from the 2.4.x upstream git branch, so I also opened an issue on GitHub: https://github.com/OpenPrinting/cups/issues/934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2060692/+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 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git
Sorry, I completely overlooked that there were 2 fixes. I have applied the patch of PR #935 now, too, and uploaded this as cups 2.4.7-1.2ubuntu7. ** Changed in: cups (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2060692 Title: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git Status in cups package in Ubuntu: Fix Committed Bug description: While checking out the latest versions of cups (2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5), I noticed that cupsd crashes consistently after closing my Firefox tab / window. The title of the crash (from the bug-report window) is "cupsd crashed with SIGSEGV in ???()" I'm running the noble-desktop-amd64.iso from 2024-03-25 after applying some updates from the noble and noble-proposed pockets. Reproduction steps: 1. Open Firefox and manage CUPS on http://localhost:631 2. Go to Administration -> Printers -> Add Printer and choose your printer 3. Add your printer (I used the ipps:// protocol to manage the printer) 4. After clicking the "Add printer" button, immediately close your Firefox tab 5. cupsd will crash and Ubuntu will display a bug-report popup Versions: Firefox - 124.0.1-1 r4033 CUPS - 2.4.7-1.2ubuntu5 Printer: Lexmark MS415dn (supported) I am unable to reproduce this bug on versions prior to 2.4.7-1.2ubuntu4 (Tried with 2.4.7-1.2ubuntu1 and 2.4.7-1.2ubuntu2). Versions 2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5 only backported commits from the 2.4.x upstream git branch, so I also opened an issue on GitHub: https://github.com/OpenPrinting/cups/issues/934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2060692/+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 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git
Andreas, thanks a lot for the quick fix! I have applied it now in Ubuntu's CUPS, version 2.4.7-1.2ubuntu6. Note that the package will probably only land in the distro after the release of 24.04 beta. ** Changed in: cups (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2060692 Title: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git Status in cups package in Ubuntu: Fix Committed Bug description: While checking out the latest versions of cups (2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5), I noticed that cupsd crashes consistently after closing my Firefox tab / window. The title of the crash (from the bug-report window) is "cupsd crashed with SIGSEGV in ???()" I'm running the noble-desktop-amd64.iso from 2024-03-25 after applying some updates from the noble and noble-proposed pockets. Reproduction steps: 1. Open Firefox and manage CUPS on http://localhost:631 2. Go to Administration -> Printers -> Add Printer and choose your printer 3. Add your printer (I used the ipps:// protocol to manage the printer) 4. After clicking the "Add printer" button, immediately close your Firefox tab 5. cupsd will crash and Ubuntu will display a bug-report popup Versions: Firefox - 124.0.1-1 r4033 CUPS - 2.4.7-1.2ubuntu5 Printer: Lexmark MS415dn (supported) I am unable to reproduce this bug on versions prior to 2.4.7-1.2ubuntu4 (Tried with 2.4.7-1.2ubuntu1 and 2.4.7-1.2ubuntu2). Versions 2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5 only backported commits from the 2.4.x upstream git branch, so I also opened an issue on GitHub: https://github.com/OpenPrinting/cups/issues/934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2060692/+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 2060814] Re: dist-upgrade in noble fails when using TPM FDE
I have uploaded printer-driver-foo2zjs 20200505dfsg0-2ubuntu6 where I have moved the firmware file directory to /var/lib/foo2zjs/firmware/. Ken VanDine has tested this version and it works on Ubuntu 24.04 with TPM-based FDE, not interfering with the snapped kernel any more. This will not break printing. /lib/firmware is only for firmware files which are managed by the kernel. Printer firmware files are solely managed by foo2zjs, totally in user space. ** Changed in: foo2zjs (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foo2zjs in Ubuntu. https://bugs.launchpad.net/bugs/2060814 Title: dist-upgrade in noble fails when using TPM FDE Status in foo2zjs package in Ubuntu: Fix Committed Bug description: When doing a dist-upgrade of noble during the devel cycle I'm hitting this upgrade bug in the package. /lib/firmware is read-only because it's provided by the pc-kernel snap. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libpoppler134 poppler-utils The following packages will be upgraded: printer-driver-foo2zjs 1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 416 not fully installed or removed. Need to get 0 B/142 kB of archives. After this operation, 12.3 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 140132 files and directories currently installed.) Preparing to unpack .../printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb ... Unpacking printer-driver-foo2zjs (20200505dfsg0-2ubuntu5) over (20200505dfsg0-2ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb (--unpack) : error creating directory './lib/firmware/hp': Read-only file system dpkg: error while cleaning up: unable to remove newly-extracted version of '/lib/firmware/hp': Read-only file system Errors were encountered while processing: /var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: printer-driver-foo2zjs 20200505dfsg0-2ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 10 09:39:01 2024 InstallationDate: Installed on 2024-03-08 (33 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: foo2zjs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/2060814/+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 2060814] Re: dist-upgrade in noble fails when using TPM FDE
This means that /lib/firmware is repurposed, at least on some systems. So no problem for me to move the firmware directory to /usr/lib or /usr/share. Questions is now, do we have a kernel Snap on standard *.deb-based Ubuntu? If we had kernel Snaps only on Ubuntu Core (Desktop) there the printer-driver-foo2zjs package does not make sense. We work with the CUPS Snap on such systems and printer drivers work only in the new Printer Application format. For the printers supported by foo2zjs one would use the Ghostscript Printer Application. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foo2zjs in Ubuntu. https://bugs.launchpad.net/bugs/2060814 Title: dist-upgrade in noble fails when using TPM FDE Status in foo2zjs package in Ubuntu: New Bug description: When doing a dist-upgrade of noble during the devel cycle I'm hitting this upgrade bug in the package. /lib/firmware is read-only because it's provided by the pc-kernel snap. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libpoppler134 poppler-utils The following packages will be upgraded: printer-driver-foo2zjs 1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 416 not fully installed or removed. Need to get 0 B/142 kB of archives. After this operation, 12.3 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 140132 files and directories currently installed.) Preparing to unpack .../printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb ... Unpacking printer-driver-foo2zjs (20200505dfsg0-2ubuntu5) over (20200505dfsg0-2ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb (--unpack) : error creating directory './lib/firmware/hp': Read-only file system dpkg: error while cleaning up: unable to remove newly-extracted version of '/lib/firmware/hp': Read-only file system Errors were encountered while processing: /var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: printer-driver-foo2zjs 20200505dfsg0-2ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 10 09:39:01 2024 InstallationDate: Installed on 2024-03-08 (33 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: foo2zjs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/2060814/+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 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git
Andreas, thanks for also reporting upstream. Michael, Sweet, author of CUPS, has already found a solution. See: https://github.com/OpenPrinting/cups/issues/934 I will apply this solution soon. ** Bug watch added: github.com/OpenPrinting/cups/issues #934 https://github.com/OpenPrinting/cups/issues/934 ** Changed in: cups (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2060692 Title: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git Status in cups package in Ubuntu: In Progress Bug description: While checking out the latest versions of cups (2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5), I noticed that cupsd crashes consistently after closing my Firefox tab / window. The title of the crash (from the bug-report window) is "cupsd crashed with SIGSEGV in ???()" I'm running the noble-desktop-amd64.iso from 2024-03-25 after applying some updates from the noble and noble-proposed pockets. Reproduction steps: 1. Open Firefox and manage CUPS on http://localhost:631 2. Go to Administration -> Printers -> Add Printer and choose your printer 3. Add your printer (I used the ipps:// protocol to manage the printer) 4. After clicking the "Add printer" button, immediately close your Firefox tab 5. cupsd will crash and Ubuntu will display a bug-report popup Versions: Firefox - 124.0.1-1 r4033 CUPS - 2.4.7-1.2ubuntu5 Printer: Lexmark MS415dn (supported) I am unable to reproduce this bug on versions prior to 2.4.7-1.2ubuntu4 (Tried with 2.4.7-1.2ubuntu1 and 2.4.7-1.2ubuntu2). Versions 2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5 only backported commits from the 2.4.x upstream git branch, so I also opened an issue on GitHub: https://github.com/OpenPrinting/cups/issues/934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2060692/+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 2060038] Re: splix version 2.0.0+svn315-7fakesync1ubuntu0.22.04.1 in jammy is higher than versions in mantic and noble
** Changed in: splix (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to splix in Ubuntu. https://bugs.launchpad.net/bugs/2060038 Title: splix version 2.0.0+svn315-7fakesync1ubuntu0.22.04.1 in jammy is higher than versions in mantic and noble Status in splix package in Ubuntu: Fix Released Bug description: This package cannot be upgraded, we're going to need a mantic SRU and an ubuntu1 for noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/2060038/+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 2060038] Re: splix version 2.0.0+svn315-7fakesync1ubuntu0.22.04.1 in jammy is higher than versions in mantic and noble
Uploaded 2.0.0+svn315-7fakesync1ubuntu1 without any changes. ** Changed in: splix (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to splix in Ubuntu. https://bugs.launchpad.net/bugs/2060038 Title: splix version 2.0.0+svn315-7fakesync1ubuntu0.22.04.1 in jammy is higher than versions in mantic and noble Status in splix package in Ubuntu: Fix Committed Bug description: This package cannot be upgraded, we're going to need a mantic SRU and an ubuntu1 for noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/2060038/+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 2059281] Re: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd
I have uploaded c2esp 27-11ubuntu4 now. In the code of c2esp I have found some logging statements which cast pointer addresses to long int. Probably this works only on 64-bit and not on 32-bit and so caused the crashes in the autopkgtest. I could not test whether it is really the fix, I am simply giving it a try. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to c2esp in Ubuntu. https://bugs.launchpad.net/bugs/2059281 Title: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd Status in c2esp package in Ubuntu: In Progress Status in cups package in Ubuntu: Fix Released Bug description: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059281/+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 2059281] Re: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd
Problem seems to be rather the broken cups.pc file from Debian in the cups package, which is fixed in 2.4.7-1.2ubuntu2, as after this cups release the tests of said packages have passed. ** Package changed: libcupsfilters (Ubuntu) => cups (Ubuntu) ** Changed in: cups (Ubuntu) Status: Triaged => Fix Released ** Also affects: c2esp (Ubuntu) Importance: Undecided Status: New ** Changed in: c2esp (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to c2esp in Ubuntu. https://bugs.launchpad.net/bugs/2059281 Title: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd Status in c2esp package in Ubuntu: In Progress Status in cups package in Ubuntu: Fix Released Bug description: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059281/+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 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1
Debian had added their own cups.pc file to CUPS 2.4.7, overlooking that already in 2.4.6 upstream has introduced a cups.pc file which is much more comprehensive. This broke the autopkgtest of cups-browsed in noble. Fixed in cups 2.4.7-1.2ubuntu2. ** Changed in: cups (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to c2esp in Ubuntu. https://bugs.launchpad.net/bugs/2059157 Title: proposed-migration for cups 2.4.7-1.2ubuntu1 Status in c2esp package in Ubuntu: New Status in cups package in Ubuntu: Fix Committed Bug description: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+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 2029480] Re: SyntaxWarnings with Python3.12
This is the patch adapted to the actual Ubuntu/Debian package of HPLIP, as used in the hplip 3.23.12+dfsg0-0ubuntu2 release for Noble. The adaptations were most probably needed because, before applying this patch ~80 other patches got applied to the original source code of HPLIP. Especially the transition from "is not" to "!=" seems already done. ** Patch added: "0086-hplip-use-raw-strings.patch" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2029480/+attachment/5756456/+files/0086-hplip-use-raw-strings.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2029480 Title: SyntaxWarnings with Python3.12 Status in HPLIP: Confirmed Status in hplip package in Ubuntu: Fix Committed Bug description: Fedora 39 uses Python 3.12 by default, which generates many SyntaxWarnings when running hplip scripts. Most warnings are due regular expressions in strings, so making them raw fixes the issue. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/2029480/+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 2029480] Re: SyntaxWarnings with Python3.12
@zdohnal, thanks a lot for the patch, I have applied it now (with slight adjustments) to the Ubuntu package, fixing bug #2054869. ** Also affects: hplip (Ubuntu) Importance: Undecided Status: New ** Changed in: hplip (Ubuntu) Status: New => Fix Committed ** Changed in: hplip Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2029480 Title: SyntaxWarnings with Python3.12 Status in HPLIP: Confirmed Status in hplip package in Ubuntu: Fix Committed Bug description: Fedora 39 uses Python 3.12 by default, which generates many SyntaxWarnings when running hplip scripts. Most warnings are due regular expressions in strings, so making them raw fixes the issue. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/2029480/+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 2054869] Re: Lot of SyntaxWarning messages during install
*** This bug is a duplicate of bug 2029480 ***
https://bugs.launchpad.net/bugs/2029480
** This bug has been marked a duplicate of bug 2029480
SyntaxWarnings with Python3.12
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2054869
Title:
Lot of SyntaxWarning messages during install
Status in HPLIP:
Confirmed
Status in hplip package in Ubuntu:
Confirmed
Bug description:
Ubuntu 24.04 lot of SyntaxWarning messages during install
running python rtupdate hooks for python3.12...
/usr/share/hplip/base/LedmWifi.py:34: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/device.py:49: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/g.py:304: SyntaxWarning: invalid escape sequence '\|'
spinner = "\|/-\|/-"
/usr/share/hplip/base/g.py:354: SyntaxWarning: invalid escape sequence '\d'
m = re.search('python(\d(\.\d){0,2})', ext_path)#get the python
version where the .so file is found
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape
sequence '\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape
sequence '\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape
sequence '\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/base/logger.py:439: SyntaxWarning: invalid escape sequence
'\<'
elem_start = re.findall("(\<\W{0,1}\w+) ?", line)[0]
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: hplip 3.22.10+dfsg0-2ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 10:31:07 2024
InstallationDate: Installed on 2024-02-20 (4 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240220)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: Gigabyte Technology Co., Ltd. H510M H
Papersize: a4
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic
root=UUID=46acaa02-3641-4fce-877b-03fb0f9525e5 ro quiet splash vt.handoff=7
SourcePackage: hplip
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F14
dmi.board.asset.tag: Default string
dmi.board.name: H510M H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF14:bd03/25/2022:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH510MH:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH510MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: H510 MB
dmi.product.name: H510M H
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/2054869/+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 2054879] Re: Syntax warnings after upgrade to Python 3.12
*** This bug is a duplicate of bug 2029480 ***
https://bugs.launchpad.net/bugs/2029480
** This bug is no longer a duplicate of bug 2054869
Lot of SyntaxWarning messages during install
** This bug has been marked a duplicate of bug 2029480
SyntaxWarnings with Python3.12
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2054879
Title:
Syntax warnings after upgrade to Python 3.12
Status in hplip package in Ubuntu:
New
Bug description:
Today during regular system updates, I was presented with this
information:
Setting up python3 (3.12.1-0ubuntu1) ...
running python rtupdate hooks for python3.12...
/usr/share/hplip/base/LedmWifi.py:34: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/device.py:49: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/g.py:304: SyntaxWarning: invalid escape sequence '\|'
spinner = "\|/-\|/-"
/usr/share/hplip/base/g.py:354: SyntaxWarning: invalid escape sequence '\d'
m = re.search('python(\d(\.\d){0,2})', ext_path)#get the python
version where the .so file is found
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape
sequence '\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape
sequence '\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape
sequence '\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/base/logger.py:439: SyntaxWarning: invalid escape sequence
'\<'
elem_start = re.findall("(\<\W{0,1}\w+) ?", line)[0]
/usr/share/hplip/base/logger.py:440: SyntaxWarning: invalid escape sequence
'\]'
elem_finished = re.findall("([?|\]\]]*\>)", line)[0]
/usr/share/hplip/base/logger.py:442: SyntaxWarning: invalid escape sequence
'\S'
attrs = re.findall("(\S*?\=\".*?\")", line)
/usr/share/hplip/base/models.py:37: SyntaxWarning: invalid escape sequence
'\d'
pat_prod_num = re.compile("""(\d+)""", re.I)
/usr/share/hplip/base/models.py:428: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:429: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:430: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:431: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:432: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-virgin', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:433: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-dvc', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:434: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:435: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:436: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-id', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:437: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-hp-ink', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:438: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-health-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:439: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-health$', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:440: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-known', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:441: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-level', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:442: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-ack', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:443: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:444: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^in-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:445: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^out-tray(\d+)',
[Desktop-packages] [Bug 2055346] Re: Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for noble
** Patch added: "ipp-usb_0.9.23-1build1_0.9.24-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/ipp-usb/+bug/2055346/+attachment/5750424/+files/ipp-usb_0.9.23-1build1_0.9.24-0ubuntu1.debdiff ** Also affects: golang-github-openprinting-goipp (Ubuntu) Importance: Undecided Status: New ** Changed in: golang-github-openprinting-goipp (Ubuntu) Importance: Undecided => High ** Changed in: golang-github-openprinting-goipp (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ipp-usb in Ubuntu. https://bugs.launchpad.net/bugs/2055346 Title: Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for noble Status in golang-github-openprinting-goipp package in Ubuntu: New Status in ipp-usb package in Ubuntu: New Bug description: These packages are for IPP-over-USB and they contain not only bug fixes but also several quirk workarounds to especially make printers from Pantum but also devices of other manufacturers working. Unfortunately, goipp is not in my PPU list (I do not know whether ipp- usb is there). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-openprinting-goipp/+bug/2055346/+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 2055346] [NEW] Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for noble
Public bug reported: These packages are for IPP-over-USB and they contain not only bug fixes but also several quirk workarounds to especially make printers from Pantum but also devices of other manufacturers working. Unfortunately, goipp is not in my PPU list (I do not know whether ipp- usb is there). ** Affects: golang-github-openprinting-goipp (Ubuntu) Importance: High Assignee: Thomas Ward (teward) Status: New ** Affects: ipp-usb (Ubuntu) Importance: High Assignee: Thomas Ward (teward) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ipp-usb in Ubuntu. https://bugs.launchpad.net/bugs/2055346 Title: Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for noble Status in golang-github-openprinting-goipp package in Ubuntu: New Status in ipp-usb package in Ubuntu: New Bug description: These packages are for IPP-over-USB and they contain not only bug fixes but also several quirk workarounds to especially make printers from Pantum but also devices of other manufacturers working. Unfortunately, goipp is not in my PPU list (I do not know whether ipp- usb is there). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-openprinting-goipp/+bug/2055346/+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 2054869] Re: Lot of SyntaxWarning messages during install
To the upstream developers of HPLIP:
In a recent version of Python (3.12?) backslashes in regular expressions
need to get quoted or the expressions defined as raw strings (r'...').
Could you change it that way? Using raw strings should not break older
versions of Python.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2054869
Title:
Lot of SyntaxWarning messages during install
Status in HPLIP:
Confirmed
Status in hplip package in Ubuntu:
Confirmed
Bug description:
Ubuntu 24.04 lot of SyntaxWarning messages during install
running python rtupdate hooks for python3.12...
/usr/share/hplip/base/LedmWifi.py:34: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/device.py:49: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/g.py:304: SyntaxWarning: invalid escape sequence '\|'
spinner = "\|/-\|/-"
/usr/share/hplip/base/g.py:354: SyntaxWarning: invalid escape sequence '\d'
m = re.search('python(\d(\.\d){0,2})', ext_path)#get the python
version where the .so file is found
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape
sequence '\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape
sequence '\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape
sequence '\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/base/logger.py:439: SyntaxWarning: invalid escape sequence
'\<'
elem_start = re.findall("(\<\W{0,1}\w+) ?", line)[0]
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: hplip 3.22.10+dfsg0-2ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 10:31:07 2024
InstallationDate: Installed on 2024-02-20 (4 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240220)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: Gigabyte Technology Co., Ltd. H510M H
Papersize: a4
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic
root=UUID=46acaa02-3641-4fce-877b-03fb0f9525e5 ro quiet splash vt.handoff=7
SourcePackage: hplip
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F14
dmi.board.asset.tag: Default string
dmi.board.name: H510M H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF14:bd03/25/2022:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH510MH:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH510MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: H510 MB
dmi.product.name: H510M H
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/2054869/+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 2054869] Re: Lot of SyntaxWarning messages during install
I have seen similar warnings also during building of the HPLIP package.
Looking into the Python documentation
https://docs.python.org/3/library/re.html
I have found out that the search patterns need to be supplied as raw
strings:
'^\d+' -> r'^\d+'
or backslashes need to get quoted:
'^\d+' -> '^\\d+'
As HPLIP contains hundreds of regular expressions it would be very
awkward to distro-patch this for Debian and Ubuntu, as the upstream code
is all the time changing.
An upstream fix would be the best solution.
Adding upstream task ...
** Also affects: hplip
Importance: Undecided
Status: New
** Changed in: hplip
Status: New => Incomplete
** Changed in: hplip
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2054869
Title:
Lot of SyntaxWarning messages during install
Status in HPLIP:
Confirmed
Status in hplip package in Ubuntu:
Confirmed
Bug description:
Ubuntu 24.04 lot of SyntaxWarning messages during install
running python rtupdate hooks for python3.12...
/usr/share/hplip/base/LedmWifi.py:34: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/device.py:49: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/g.py:304: SyntaxWarning: invalid escape sequence '\|'
spinner = "\|/-\|/-"
/usr/share/hplip/base/g.py:354: SyntaxWarning: invalid escape sequence '\d'
m = re.search('python(\d(\.\d){0,2})', ext_path)#get the python
version where the .so file is found
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape
sequence '\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape
sequence '\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape
sequence '\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/base/logger.py:439: SyntaxWarning: invalid escape sequence
'\<'
elem_start = re.findall("(\<\W{0,1}\w+) ?", line)[0]
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: hplip 3.22.10+dfsg0-2ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 10:31:07 2024
InstallationDate: Installed on 2024-02-20 (4 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240220)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: Gigabyte Technology Co., Ltd. H510M H
Papersize: a4
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic
root=UUID=46acaa02-3641-4fce-877b-03fb0f9525e5 ro quiet splash vt.handoff=7
SourcePackage: hplip
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F14
dmi.board.asset.tag: Default string
dmi.board.name: H510M H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF14:bd03/25/2022:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH510MH:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH510MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: H510 MB
dmi.product.name: H510M H
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/2054869/+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 2052925] Re: lpoptions -d as root
Uploaded cups 2.4.1op1-1ubuntu4.8 with the patch from upstream (same as also used in Debian) applied. ** Also affects: cups (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: cups (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: cups (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Status in cups source package in Jammy: Fix Committed Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups:   Installed: 2.4.1op1-1ubuntu4.7   Candidate: 2.4.1op1-1ubuntu4.7   Version table:  *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status  2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2052925/+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 2028326] Re: cups-browsed uses a CPU thread at 100%
*** This bug is a duplicate of bug 2049315 *** https://bugs.launchpad.net/bugs/2049315 ** This bug is no longer a duplicate of bug 2018504 cups-browsed is using an excessive amount of CPU ** This bug has been marked a duplicate of bug 2049315 cups-browsed running non-stop on two cores -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2028326 Title: cups-browsed uses a CPU thread at 100% Status in cups-browsed package in Ubuntu: Confirmed Bug description: On my Kubuntu Lunar system, with package cups-browsed (2.0~rc1-0ubuntu1.1), cups-browsed is getting stuck inconsistently and some hours after initial boot in a 100% CPU usage loop (seems to use a single thread at 100%). Looks like https://bugs.launchpad.net/ubuntu/+source/cups- browsed/+bug/2018504 but I am already using the package that appears to contain a fix for that bug, so this may be a different root cause. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups-browsed 2.0~rc1-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: CurrentDesktop: KDE Date: Thu Jul 20 23:00:50 2023 InstallationDate: Installed on 2023-06-10 (40 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) Lpstat: device for Canon_TR4500_series: implicitclass://Canon_TR4500_series/ MachineType: Dell Inc. Inspiron 1520 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon_TR4500_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon_TR4500_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic root=UUID=db9a1f13-abe0-456b-b50a-f9ee27bea5eb ro quiet splash vt.handoff=7 SourcePackage: cups-browsed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2008 dmi.bios.release: 0.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/03/2008:br0.7:efr0.7:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:sku: dmi.product.name: Inspiron 1520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2028326/+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 2030685] Re: cups-browsed 2.0~rc1-0ubuntu1.1 high cpu usage
*** This bug is a duplicate of bug 2049315 *** https://bugs.launchpad.net/bugs/2049315 ** This bug is no longer a duplicate of bug 2018504 cups-browsed is using an excessive amount of CPU ** This bug has been marked a duplicate of bug 2049315 cups-browsed running non-stop on two cores -- 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/2030685 Title: cups-browsed 2.0~rc1-0ubuntu1.1 high cpu usage Status in cups-filters package in Ubuntu: New Bug description: I exhibited cups-browsed causing high CPU usage upon upgrading to 23.04. This led me to bug #2018504 which seemed to be describing the same behaviour I was experiencing. Bug #2018504 was closed with cups- browsed version 2.0~rc1-0ubuntu1.1 being released which was deemed to have resolved the issue. I have cups-browsed 2.0~rc1-0ubuntu1.1 and I still see the same behaviour, so potentially there is another issue causing the same behaviour. I also note that both bug #2018504 and #2017907 (its duplicate) have been updated with other people who have also upgraded to version 2.0~rc1-0ubuntu1.1 but are still seeing the same behaviour. I'm opening this bug because I'm concerned the other two reports will not be noticed since they were reported after the release of cups- browsed 2.0~rc1-0ubuntu1.1 which was expected to fix this issue 1) The release of Ubuntu you are using No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 2) The version of the package you are using cups-browsed: Installed: 2.0~rc1-0ubuntu1.1 Candidate: 2.0~rc1-0ubuntu1.1 Version table: *** 2.0~rc1-0ubuntu1.1 500 500 http://nz.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.0~rc1-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 3) What you expected to happen cups-browsed 2.0~rc1-0ubuntu1.1 would prevent cups-browsed from having high cpu usage 4) What happened instead High CPU usage still happening To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2030685/+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 2049315] Re: cups-browsed running non-stop on two cores
** This bug is no longer a duplicate of bug 2018504
cups-browsed is using an excessive amount of CPU
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-browsed in Ubuntu.
https://bugs.launchpad.net/bugs/2049315
Title:
cups-browsed running non-stop on two cores
Status in cups-browsed package in Ubuntu:
Confirmed
Bug description:
After waking up from standby cups-browsed runs incessantly on two
cores:
  18243 cups-br+ 20 0 432256 26348 17848 R 99.7 0.2 66:54.73
cups-br+
  85147 cups-br+ 20 0 432256 26348 17848 R 99.7 0.2 66:52.08
cups-br+
cups-br+ 18243 18.9 0.1 432256 26348 ?Rsl 08:30 135:06
/usr/sbin/cups-browsed
Best regards
Heinrich
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: cups-browsed 2.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Sun Jan 14 20:19:22 2024
InstallationDate: Installed on 2021-07-01 (927 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic
root=/dev/mapper/vgubuntu-root ro
SourcePackage: cups-browsed
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2023
dmi.bios.release: 1.63
dmi.bios.vendor: LENOVO
dmi.bios.version: R0UET83W (1.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KV0008GE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.63
dmi.modalias:
dmi:bvnLENOVO:bvrR0UET83W(1.63):bd02/08/2023:br1.63:efr1.63:svnLENOVO:pn20KV0008GE:pvrThinkPadE585:rvnLENOVO:rn20KV0008GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KV_BU_Think_FM_ThinkPadE585:
dmi.product.family: ThinkPad E585
dmi.product.name: 20KV0008GE
dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
dmi.product.version: ThinkPad E585
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2049315/+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 2049315] Re: cups-browsed running non-stop on two cores
** This bug has been marked a duplicate of bug 2018504
cups-browsed is using an excessive amount of CPU
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-browsed in Ubuntu.
https://bugs.launchpad.net/bugs/2049315
Title:
cups-browsed running non-stop on two cores
Status in cups-browsed package in Ubuntu:
Confirmed
Bug description:
After waking up from standby cups-browsed runs incessantly on two
cores:
  18243 cups-br+ 20 0 432256 26348 17848 R 99.7 0.2 66:54.73
cups-br+
  85147 cups-br+ 20 0 432256 26348 17848 R 99.7 0.2 66:52.08
cups-br+
cups-br+ 18243 18.9 0.1 432256 26348 ?Rsl 08:30 135:06
/usr/sbin/cups-browsed
Best regards
Heinrich
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: cups-browsed 2.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Sun Jan 14 20:19:22 2024
InstallationDate: Installed on 2021-07-01 (927 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic
root=/dev/mapper/vgubuntu-root ro
SourcePackage: cups-browsed
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2023
dmi.bios.release: 1.63
dmi.bios.vendor: LENOVO
dmi.bios.version: R0UET83W (1.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KV0008GE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.63
dmi.modalias:
dmi:bvnLENOVO:bvrR0UET83W(1.63):bd02/08/2023:br1.63:efr1.63:svnLENOVO:pn20KV0008GE:pvrThinkPadE585:rvnLENOVO:rn20KV0008GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KV_BU_Think_FM_ThinkPadE585:
dmi.product.family: ThinkPad E585
dmi.product.name: 20KV0008GE
dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
dmi.product.version: ThinkPad E585
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2049315/+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 2028326] Re: cups-browsed uses a CPU thread at 100%
*** This bug is a duplicate of bug 2018504 *** https://bugs.launchpad.net/bugs/2018504 ** This bug has been marked a duplicate of bug 2018504 cups-browsed is using an excessive amount of CPU -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2028326 Title: cups-browsed uses a CPU thread at 100% Status in cups-browsed package in Ubuntu: Confirmed Bug description: On my Kubuntu Lunar system, with package cups-browsed (2.0~rc1-0ubuntu1.1), cups-browsed is getting stuck inconsistently and some hours after initial boot in a 100% CPU usage loop (seems to use a single thread at 100%). Looks like https://bugs.launchpad.net/ubuntu/+source/cups- browsed/+bug/2018504 but I am already using the package that appears to contain a fix for that bug, so this may be a different root cause. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups-browsed 2.0~rc1-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: CurrentDesktop: KDE Date: Thu Jul 20 23:00:50 2023 InstallationDate: Installed on 2023-06-10 (40 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) Lpstat: device for Canon_TR4500_series: implicitclass://Canon_TR4500_series/ MachineType: Dell Inc. Inspiron 1520 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon_TR4500_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon_TR4500_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic root=UUID=db9a1f13-abe0-456b-b50a-f9ee27bea5eb ro quiet splash vt.handoff=7 SourcePackage: cups-browsed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2008 dmi.bios.release: 0.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/03/2008:br0.7:efr0.7:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:sku: dmi.product.name: Inspiron 1520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2028326/+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 2030685] Re: cups-browsed 2.0~rc1-0ubuntu1.1 high cpu usage
*** This bug is a duplicate of bug 2018504 *** https://bugs.launchpad.net/bugs/2018504 ** This bug is no longer a duplicate of bug 2028326 cups-browsed uses a CPU thread at 100% ** This bug has been marked a duplicate of bug 2018504 cups-browsed is using an excessive amount of CPU -- 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/2030685 Title: cups-browsed 2.0~rc1-0ubuntu1.1 high cpu usage Status in cups-filters package in Ubuntu: New Bug description: I exhibited cups-browsed causing high CPU usage upon upgrading to 23.04. This led me to bug #2018504 which seemed to be describing the same behaviour I was experiencing. Bug #2018504 was closed with cups- browsed version 2.0~rc1-0ubuntu1.1 being released which was deemed to have resolved the issue. I have cups-browsed 2.0~rc1-0ubuntu1.1 and I still see the same behaviour, so potentially there is another issue causing the same behaviour. I also note that both bug #2018504 and #2017907 (its duplicate) have been updated with other people who have also upgraded to version 2.0~rc1-0ubuntu1.1 but are still seeing the same behaviour. I'm opening this bug because I'm concerned the other two reports will not be noticed since they were reported after the release of cups- browsed 2.0~rc1-0ubuntu1.1 which was expected to fix this issue 1) The release of Ubuntu you are using No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 2) The version of the package you are using cups-browsed: Installed: 2.0~rc1-0ubuntu1.1 Candidate: 2.0~rc1-0ubuntu1.1 Version table: *** 2.0~rc1-0ubuntu1.1 500 500 http://nz.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.0~rc1-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 3) What you expected to happen cups-browsed 2.0~rc1-0ubuntu1.1 would prevent cups-browsed from having high cpu usage 4) What happened instead High CPU usage still happening To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2030685/+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 2025526] Re: Printer is not available in chromium snap
@wallento and @jose+ubu1, could you please run the command ps aux | grep cups-proxyd and post the output here and also could you attach the files /var/snap/cups/current/var/log/cups-proxyd_log /var/snap/cups/current/var/log/error_log /var/log/cups/error_log Attach the files one by one, in separate comments, and do not compress them, this way I will be able to easily read right out of the browser. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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
Thanks, Jay, marking as verified ... ** Tags removed: verification-needed verification-needed-lunar verification-needed-mantic ** Tags added: verification-done verification-done-lunar verification-done-mantic -- 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 Committed Status in qpdf source package in Lunar: Fix Committed Status in qpdf source package in Mantic: Fix Committed Status in qpdf package in Debian: Confirmed 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 and has to be reprocessed in the new state. qpdf
[Desktop-packages] [Bug 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
Thanks Jay, for elaborating on the test procedures and also for providing instructions for manual testing so that users can easily verify the fix. I have copied your instructions to the "[ Test Plan ]" section of the initial description of the bug so that they get easily found. ** Description changed: 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 and has to be reprocessed in the new state. qpdf has a rigorous test suite and an extremely good quality record. It processes millions of documents daily by many commercial entities. My current employer runs millions of pages a day through qpdf. [ Other Info ] See also Upstream bug report: https://github.com/qpdf/qpdf/issues/1050 Corresponding debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054158 Debian stable release
[Desktop-packages] [Bug 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
Thank you very much, Jay, for writing up this SRU bug report and providing the debdiffs with the fix. This is the usual way how you contribute if you do not have upload rights to the Ubuntu archives. You post debdiffs in a bug report and a person with appropriate rights (the so-called "sponsor") applies the debdiff and uploads the resulting package. I have uploaded the appropriate packages right now and subscribed the SRU team (ubuntu-sru group) to this report. Now the SRU Team will check the uploaded packages and put them into the -proposed repositories of the distro versions affected. Then they call for testing by a comment here. Once somebody tests the packages and finds that the bug is actually fixed, and nobody reports a regression, the fixed packages get released into the affected distros. ** Bug watch added: Debian Bug tracker #1054158 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054158 ** Also affects: qpdf via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054158 Importance: Unknown Status: Unknown ** No longer affects: qpdf ** Bug watch added: github.com/qpdf/qpdf/issues #1050 https://github.com/qpdf/qpdf/issues/1050 ** Also affects: qpdf via https://github.com/qpdf/qpdf/issues/1050 Importance: Unknown Status: Unknown -- 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: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 Status in Qpdf: Unknown Status in qpdf package in Ubuntu: New Status in qpdf source package in Lunar: New Status in qpdf source package in Mantic: New 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 [ 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 and has to be reprocessed in the new state. qpdf has a rigorous test suite and an extremely good quality record. It processes millions of documents daily by many commercial entities. My current employer runs millions of pages a day through qpdf. [ Other Info ] See also Upstream bug report: https://github.com/qpdf/qpdf/issues/1050
[Desktop-packages] [Bug 2039804] Re: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2
** Also affects: qpdf (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: qpdf (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: qpdf (Ubuntu Lunar) Importance: Undecided => High ** Changed in: qpdf (Ubuntu Mantic) Importance: Undecided => High -- 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: SRU request: qpdf: data loss bug affecting versions 11.0.0 through 11.6.2 Status in Qpdf: Unknown Status in qpdf package in Ubuntu: New Status in qpdf source package in Lunar: New Status in qpdf source package in Mantic: New 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 [ 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 and has to be reprocessed in the new state. qpdf has a rigorous test suite and an extremely good quality record. It processes millions of documents daily by many commercial entities. My current employer runs millions of pages a day through qpdf. [ Other Info ] See also Upstream bug report: https://github.com/qpdf/qpdf/issues/1050 Corresponding debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054158 Debian stable release approval: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 To manage notifications about this bug go to: https://bugs.launchpad.net/qpdf/+bug/2039804/+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 1971242] Re: printing PDF appears always grey, no color
Marc, thanks a lot for completing this one, as it has badly coincided
with my trip to India. And sorry for having let anyone to wait so long
...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Released
Status in cups source package in Lunar:
Fix Released
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 1971242] Re: printing PDF appears always grey, no color
@ahasenak, I have uploaded an SRU for this bug for Lunar right now. As
soon as it gets approved, please test it as described in the initial
description (there is an option to do it without an affected printer)
and report back here.
I will not upload an SRU for Kinetic, as this version is already EOL.
** Also affects: okular (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: cups (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: atril (Ubuntu Lunar)
Importance: Undecided
Status: New
** No longer affects: atril (Ubuntu Lunar)
** No longer affects: okular (Ubuntu Lunar)
** Changed in: cups (Ubuntu Lunar)
Importance: Undecided => High
** Changed in: cups (Ubuntu Lunar)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Committed
Status in cups source package in Lunar:
In Progress
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 2028054] Re: [MIR] python-rlpycairo
The binary package libsane-hpaio DOES NOT depend on the binary package hplip, not even indirectly, so the binary package hplip can get demoted to Universe. the binary package printer-driver-hpcups also does not depend on the binary package hplip, but printer-driver-hpcups itself can already get demoted to Universe as we replace the printer drivers by Printer Application Snaps (this driver provided by the HPLIP Printer Application, hplip-printer-app). So hp-scan as part of the binary package hplip will go to Universe, hp- sendfax as part of the binary package hplip-gui is already in Universe. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2028054 Title: [MIR] python-rlpycairo Status in hplip package in Ubuntu: New Status in python-reportlab package in Ubuntu: New Status in python-rlpycairo package in Ubuntu: Incomplete Bug description: python-rlpycairo is a new dependency of python-reportlab (currently owned by Foundations). The only consumer of python-reportlab is hplip (owned by Desktop), apparently it needs it for scanning: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=651240 $ reverse-depends src:python-reportlab -c main -r mantic Reverse-Depends === * hplip (for python3-reportlab) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x src:hplip -> src:python-reportlab -> src:python-rlpycairo -> src:freetype-py & src:ttf-bitstream-vera So from the above, it sounds like this new dependency is actually needed (after the reportlab package dropped its renderpm extension). It should be discussed between Foundations and Desktop who's owning those dependencies and doing the MIRs for python-rlpycairo, freetype- py and ttf-bitstream-vera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2028054/+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 2028054] Re: [MIR] python-rlpycairo
So all python3-reportlab dependencies go to Universe ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2028054 Title: [MIR] python-rlpycairo Status in hplip package in Ubuntu: New Status in python-reportlab package in Ubuntu: New Status in python-rlpycairo package in Ubuntu: Incomplete Bug description: python-rlpycairo is a new dependency of python-reportlab (currently owned by Foundations). The only consumer of python-reportlab is hplip (owned by Desktop), apparently it needs it for scanning: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=651240 $ reverse-depends src:python-reportlab -c main -r mantic Reverse-Depends === * hplip (for python3-reportlab) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x src:hplip -> src:python-reportlab -> src:python-rlpycairo -> src:freetype-py & src:ttf-bitstream-vera So from the above, it sounds like this new dependency is actually needed (after the reportlab package dropped its renderpm extension). It should be discussed between Foundations and Desktop who's owning those dependencies and doing the MIRs for python-rlpycairo, freetype- py and ttf-bitstream-vera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2028054/+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 2028054] Re: [MIR] python-rlpycairo
Generally, python-reportlab is used only by HPLIP's utilities, not by the printer and scanner drivers by themselves. It is used by hp-scan to convert image files of scanned pages into PDF files and by hp-sendfax to generate fax cover sheets. Most users do not care as they use simple-scan or XSane for scanning. As HPLIP's scanner driver is a SANE driver all these frontends work, and probably also more reliable than HP's tool. hp-sendfax is very really used, probably already because fax is only rarely used nowadays. at most places it got already completely replaced by other electronic communication means. Also use of HPLIP at all is diminishing as modern HP printers and multi- function devices support driverless (IPP) printing and (eSCL) scanning. hp-sendfax is in hplip-gui which is in Universe. hp-scan is a command line tool but not necessarily needed, there is also scanimage of SANE, so one should check whether the binary package "hplip" is actually needed by sane-hpaio and/or printer-driver-hpcups and if not, demote it to Universe. In addition, from Ubuntu 23.10 printing will be provided by the CUPS Snap and Printer Application Snaps, which makes printer-driver-hpcups not needed any more, and so also subject to be moved to Universe. So for me it looks like that we can move most of HPLIP to Universe as practically only sane-hpaio is needed to support scanners (and sane- hpaio will also get removed in favor of Snaps in a later version of Ubuntu). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2028054 Title: [MIR] python-rlpycairo Status in hplip package in Ubuntu: New Status in python-reportlab package in Ubuntu: New Status in python-rlpycairo package in Ubuntu: Incomplete Bug description: python-rlpycairo is a new dependency of python-reportlab (currently owned by Foundations). The only consumer of python-reportlab is hplip (owned by Desktop), apparently it needs it for scanning: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=651240 $ reverse-depends src:python-reportlab -c main -r mantic Reverse-Depends === * hplip (for python3-reportlab) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x src:hplip -> src:python-reportlab -> src:python-rlpycairo -> src:freetype-py & src:ttf-bitstream-vera So from the above, it sounds like this new dependency is actually needed (after the reportlab package dropped its renderpm extension). It should be discussed between Foundations and Desktop who's owning those dependencies and doing the MIRs for python-rlpycairo, freetype- py and ttf-bitstream-vera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2028054/+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 1971242] Re: printing PDF appears always grey, no color
Thank you very much. Marking the SRU for Jammy as verified ...
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Committed
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
Dalik, there is an upstream bug report about your observation of missing *.bin files for CUPS on /var/lib/snapd/seccomp/bpf/: https://github.com/OpenPrinting/cups-snap/issues/16 It is reported by GitHub user d3al. Is that you? I am not able to reproduce this problem on Ubuntu 23.04 and 23.10. ** Bug watch added: github.com/OpenPrinting/cups-snap/issues #16 https://github.com/OpenPrinting/cups-snap/issues/16 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Confirmed Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
Anyone suffering the described problem, could you follow Nathan's instructions if you have not done so yet, and could you run the following commands and paste the output here? lpstat -r lpstat -v lpstat -p cuos.lpstat -r cups.lpstat -v cups.lpstat -p Aleo try to print through the CUPS Snap, for example via cups.lp -d PRINTER FILE.PDF Replace PRINTER by the name of a working print queue and FILE.PDF by the name of a PDF file which you have. Does this work? If not, could you also try lp -d PRINTER FILE.PDF Does this work? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2025526] Re: Printer is not available in chromium snap
Heiko, even that you have found a workaround, could you continue help us what was going on? Could you follow the instructions of comment #4? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 2025526] Re: Printer is not available in chromium snap
Heiko, please run the following commands and post their output here: lpstat -v lpstat -p cups.lpstat -v cups.lpstat -p snap list | grep cups snap connections cups -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 2025526] Re: Printer is not available in chromium snap
** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 1971242] Re: printing PDF appears always grey, no color
** Description changed:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers are
affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-PDF_Printer-
PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
- editor. Chcke whether it contains a line
+ editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints about
color printing. So the regression potential is very low.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Committed
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is
[Desktop-packages] [Bug 1971242] Re: printing PDF appears always grey, no color
Fixed in Mantic via cups 2.4.5-0ubuntu1:
cups (2.4.5-0ubuntu1) mantic; urgency=medium
* Update to new upstream version 2.4.5.
- Fixes color printing on printers with "CMYK" choice instead of "RGB"
in "ColorModel" option of their PPD (Upstream issues #451 and #500,
LP: 1971242).
* Merge from Debian unstable. Remaining changes:
- Added "--enable-snapped-clients" to the "./configure" options to use
the correct Snap mediation mode for an unsnapped cupsd, like provided
by this package.
- In the AppArmor profile allow CUPS to access (/var)/run/snapd.socket
to allow cupsd to determine which interfaces a snapped client
is plugging.
- Build-depend on libapparmor-dev, libsnapd-glib-dev, needed for
Snap mediation.
- Added fully automatic generation of PPD option setting presets to
be applied depending on the settings of the job IPP attributes
"print-color-mode", "print-quality", and "print-content-optimize".
This allows easy control of any printer with only standard IPP
attributes, as for example from a phone (functionality overtaken
from cups-filters, mot (yet) upstream in CUPS).
- In debian/rules updated ./configure arguments from --enable-gnutls to
--with-tls=gnutls. Now libcups has support for all hash types again,
especially can provide sha2-256 to PAPPL.
- When polling capabilities of a driverless printer via
get-printer-attributes IPP request, do a separate poll of the
media-col-database attribute in case it did not get obtained by the
first polls.
- In libcupsimage2 recommend libcupsfilters2 instead of libcupsfilters1.
* Manually refreshed patch 9100-ppd-cache-add-auto-presets.patch.
* Removed patches included upstream:
- 9110-create-local-printer-localhost-fix.patch
- CVE-2022-26691-2.patch
- snapd-glib-2.patch
- poll-media-col-database-separately.patch
- CVE-2023-32324.patch
cups (2.4.2-4) unstable; urgency=medium
* CVE-2023-32324
A heap buffer overflow vulnerability would allow a remote attacker to
lauch a dos attack.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-26691
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32324
** Changed in: cups (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Committed
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems
[Desktop-packages] [Bug 2012178] Re: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined
** Description changed: + [ Impact ] + + HP's GUI tool hp-toolbox does not start at all, independent which + printer(s) is used. + + With this users lose GUI-based maintenance functionality like ink level + check, print head cleaning, ... + + As a workaround on all network printers (independent whether they are + driverless IPP or not) the printer's web administration interface can be + used, going to http://HOSTNAME/ with a browser, HOSTNAME being host name + or IP of the printer. On USB only driverless printers allow access to + the web administration interface, via http://localhost:6/, but most + modern printers are driverless. + + hp-toolbox only supports HP printers, no other manufacturers. + + Also, hp-toolbox, being part of hplip-gui is only used by very few + users, as it is not installed by default. + + Printing and scanning is not affected. Your printer gets set up fully + automatically or you can set up as any non-HP printer with GNOME Control + Center, system-config-printer, or via HTTP://localhost:631/. + + Scanners in HP's devices will get automatically discovered by scanning + frontends, like simple-scan. + + [ Test plan ] + + Start the toolbox with + +hp-toolbox + + Without the fix you will get the crash mentioned in the title of this + bug report. With the SRU applied, the toolbox starts normally and can be + used. + + This test can be done independently of whether one has an HP printer or + not. + + [ Where problems could occur ] + + The changes are very small and easy to understand, so the risk of a + regression is low, and as this is code for HPLIP's GUI there cannot + happen more than now, that the GUI tools crash. The patch only applies + to GUI code, printing and scanning cannot get affected by it. + + [ Original description ] + Error occurred after installing hplip-gui ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: hplip-data 3.22.10+dfsg0-1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Mar 19 05:07:34 2023 ExecutablePath: /usr/share/hplip/toolbox.py InstallationDate: Installed on 2023-03-18 (0 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230318) InterpreterPath: /usr/bin/python3.11 JournalErrors: -- No entries -- Lpstat: device for HP_Color_LaserJet_Pro_MFP_M177fw_0342B1: implicitclass://HP_Color_LaserJet_Pro_MFP_M177fw_0342B1/ MachineType: HP HP ZBook 17 G4 PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/bin/hp-toolbox ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + Â LANG=en_US.UTF-8 + Â PATH=(custom, no user) + Â SHELL=/bin/bash + Â XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=20a0c66a-2dc4-41ec-a5f0-7eb86e995862 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonArgs: ['/usr/bin/hp-toolbox'] PythonDetails: N/A SourcePackage: hplip Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users dmi.bios.date: 04/08/2022 dmi.bios.release: 1.41 dmi.bios.vendor: HP dmi.bios.version: P70 Ver. 01.41 dmi.board.name: 8270 dmi.board.vendor: HP dmi.board.version: KBC Version 46.80 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 70.128 dmi.modalias: dmi:bvnHP:bvrP70Ver.01.41:bd04/08/2022:br1.41:efr70.128:svnHP:pnHPZBook17G4:pvr:rvnHP:rn8270:rvrKBCVersion46.80:cvnHP:ct10:cvr:skuY3J83AV: dmi.product.family: 103C_5336AN dmi.product.name: HP ZBook 17 G4 dmi.product.sku: Y3J83AV dmi.sys.vendor: HP -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2012178 Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined Status in hplip package in Ubuntu: Fix Released Status in hplip source package in Lunar: In Progress Bug description: [ Impact ] HP's GUI tool hp-toolbox does not start at all, independent which printer(s) is used. With this users lose GUI-based maintenance functionality like ink level check, print head cleaning, ... As a workaround on all network printers (independent whether they are driverless IPP or not) the printer's web administration interface can be used,
[Desktop-packages] [Bug 2012178] Re: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined
** Changed in: hplip (Ubuntu Lunar) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2012178 Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined Status in hplip package in Ubuntu: Fix Released Status in hplip source package in Lunar: In Progress Bug description: Error occurred after installing hplip-gui ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: hplip-data 3.22.10+dfsg0-1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Mar 19 05:07:34 2023 ExecutablePath: /usr/share/hplip/toolbox.py InstallationDate: Installed on 2023-03-18 (0 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230318) InterpreterPath: /usr/bin/python3.11 JournalErrors: -- No entries -- Lpstat: device for HP_Color_LaserJet_Pro_MFP_M177fw_0342B1: implicitclass://HP_Color_LaserJet_Pro_MFP_M177fw_0342B1/ MachineType: HP HP ZBook 17 G4 PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/bin/hp-toolbox ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=20a0c66a-2dc4-41ec-a5f0-7eb86e995862 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonArgs: ['/usr/bin/hp-toolbox'] PythonDetails: N/A SourcePackage: hplip Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users dmi.bios.date: 04/08/2022 dmi.bios.release: 1.41 dmi.bios.vendor: HP dmi.bios.version: P70 Ver. 01.41 dmi.board.name: 8270 dmi.board.vendor: HP dmi.board.version: KBC Version 46.80 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 70.128 dmi.modalias: dmi:bvnHP:bvrP70Ver.01.41:bd04/08/2022:br1.41:efr70.128:svnHP:pnHPZBook17G4:pvr:rvnHP:rn8270:rvrKBCVersion46.80:cvnHP:ct10:cvr:skuY3J83AV: dmi.product.family: 103C_5336AN dmi.product.name: HP ZBook 17 G4 dmi.product.sku: Y3J83AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2012178/+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 2012178] Re: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined
3.22.10+dfsg0-2 got already synced from Debian into Mantic, so it is fixed in Mantic. ** Changed in: hplip (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2012178 Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined Status in hplip package in Ubuntu: Fix Released Status in hplip source package in Lunar: Triaged Bug description: Error occurred after installing hplip-gui ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: hplip-data 3.22.10+dfsg0-1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Mar 19 05:07:34 2023 ExecutablePath: /usr/share/hplip/toolbox.py InstallationDate: Installed on 2023-03-18 (0 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230318) InterpreterPath: /usr/bin/python3.11 JournalErrors: -- No entries -- Lpstat: device for HP_Color_LaserJet_Pro_MFP_M177fw_0342B1: implicitclass://HP_Color_LaserJet_Pro_MFP_M177fw_0342B1/ MachineType: HP HP ZBook 17 G4 PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/bin/hp-toolbox ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=20a0c66a-2dc4-41ec-a5f0-7eb86e995862 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonArgs: ['/usr/bin/hp-toolbox'] PythonDetails: N/A SourcePackage: hplip Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users dmi.bios.date: 04/08/2022 dmi.bios.release: 1.41 dmi.bios.vendor: HP dmi.bios.version: P70 Ver. 01.41 dmi.board.name: 8270 dmi.board.vendor: HP dmi.board.version: KBC Version 46.80 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 70.128 dmi.modalias: dmi:bvnHP:bvrP70Ver.01.41:bd04/08/2022:br1.41:efr70.128:svnHP:pnHPZBook17G4:pvr:rvnHP:rn8270:rvrKBCVersion46.80:cvnHP:ct10:cvr:skuY3J83AV: dmi.product.family: 103C_5336AN dmi.product.name: HP ZBook 17 G4 dmi.product.sku: Y3J83AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2012178/+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 1971242] Re: printing PDF appears always grey, no color
Uploaded CUPS 2.4.5 to Mantic. This version has the mentioned fixes
included.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Committed
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
In Progress
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
ans start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Chcke whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 1971242] Re: printing PDF appears always grey, no color
** Changed in: cups (Ubuntu Lunar)
Status: New => In Progress
** Changed in: cups (Ubuntu)
Status: Confirmed => Fix Committed
** Also affects: okular (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: cups (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: atril (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: cups (Ubuntu Lunar)
** Changed in: cups (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: cups (Ubuntu Jammy)
Status: New => In Progress
** No longer affects: okular (Ubuntu Lunar)
** No longer affects: okular (Ubuntu Jammy)
** No longer affects: atril (Ubuntu Lunar)
** No longer affects: atril (Ubuntu Jammy)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Committed
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
In Progress
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
ans start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Chcke whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 1971242] Re: printing PDF appears always grey, no color
Sample PPD file for the SRU test plan.
** Description changed:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
+
+ [ Impact ]
+
+ If the PPD file for a printer has a ColorModel option and the only
+ choice in it for printing in color is not named RGB but CMYK instead,
+ the printer cannot be made printing in color with intuitive methods,
+ usually selcting the color choice in the print dialog (which makes
+ ColorModel=CMYK be sent along with the job).
+
+ Only an ugly command-line-based workaround, running the command
+
+ lpadmin -p PRINTER -o print-color-mode-default=color
+
+ makes the printer print in color.
+
+ An example for printers with such PPDs are printers from RICOH and OEM
+ (Lanier, InfoTec, Savin, ..), so many high-end color laser printers are
+ affected.
+
+ [ Test Plan ]
+
+ Remove the workaround if you had applied it:
+
+ lpadmin -p PRINTER -R print-color-mode-default
+
+ If you have an affected printer, print a PDF file (or use the print
+ functionality in an application) with colored content and choose the
+ setting for color printing in the print dialog. When printing via
+ command line do
+
+ lp -d PRINTER -o ColorModel=CMYK FILE.pdf
+
+ Without the SRU applied you will get a grayscale/monochrome printout,
+ with it applied, you will get a colored printout.
+
+ To test without a printer:
+
+ Stop CUPS:
+
+ sudo systemctl stop cups
+
+ Edit /etc/cups/cups-files.conf to have a line
+
+ FiileDevice Yes
+
+ ans start CUPS again:
+
+ sudo systemctl start cups
+
+ Then create a queue using the attached sample PPD file:
+
+ lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-PDF_Printer-
+ PDF.ppd
+
+ Print a file to this queue as described above. When the job is done
+ ("lpstat" does not show it any more), open /tmp/printout with a text
+ editor. Chcke whether it contains a line
+
+ @PJL SET RENDERMODE=COLOR
+
+ near its beginning, and NOT a line
+
+ @PJL SET RENDERMODE=GRAYSCALE
+
+ [ Where problems could occur ]
+
+ The patches are simple and they are also for some time in newer CUPS
+ versions (2.4.2 and newer) which are included in several distributions
+ (Ubuntu 22.10, 23.04, and others) and did not cause any complaints about
+ color printing. So the regression potential is very low.
** Attachment added: "Ricoh-PDF_Printer-PDF.ppd"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1971242/+attachment/5679703/+files/Ricoh-PDF_Printer-PDF.ppd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Confirmed
Status in okular package in Ubuntu:
Confirmed
Status in atril source package in Lunar:
New
Status in cups source package in Lunar:
New
Status in okular source package in Lunar:
New
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
ans start CUPS again:
[Desktop-packages] [Bug 1971242] Re: printing PDF appears always grey, no color
** Also affects: okular (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: atril (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: cups (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color Status in CUPS: Fix Released Status in atril package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Status in okular package in Ubuntu: Confirmed Status in atril source package in Lunar: New Status in cups source package in Lunar: New Status in okular source package in Lunar: New Bug description: After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF document. The print appears always b/w regardless color printing was enabled or not. Printing from LibreOffice produces a color print. This behavior (bug) is reproducible on three upgraded machines. It would be nice to have color print back again. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+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 2022929] [NEW] Bugs in resolution handling, especially garbage printed when invalid resolution value supplied
Public bug reported: This bug was originally reported upstream as https://github.com/OpenPrinting/libcupsfilters/issues/29 The reporter uses Fedora 38, besides Ubuntu 23.04 the second distro using cups-filters 2.x and libcupsfilters 2.x. As I am able to reproduce the bug on Ubuntu 23.04 and it is a problem many users could run into (it especially happens with driverless IPP printers) I post this bug report as base for an SRU in 23.04. What happens is that if a job is printed and along with it a resolution setting is supplied which is not supported by the printer, garbage is printed as the job gets actually rasterized with the wrong resolution. This was discovered by the Chromium Browser sending print jobs with `-o resolution=96dpi` regardless which resolutions the printer actually supports. Most driverless printers receive their jobs rasterrized into Apple Raster or PWG Raster and so for them this bug occurs. I have already fixed the bug upstream in libcupsfilters via https://github.com/OpenPrinting/libcupsfilters/commit/2892e9a63 The fix makes the function cfIPPAttrResolutionForPrinter() more intensely, in which another bug showed, the list of supported resolutions searched for as a range data type which was wrong and so the list not being found. So I fixed this here, also in libcupsfilters: https://github.com/OpenPrinting/libcupsfilters/commit/9ff1341c2 Now unsupported resolutions supplied to jobs are ignored so that the default resolution gets used then. The bug masked another bug in resolution handling which got revealed once the above-mentioned fix was applied.Here the problem is that for driverless IPP printers, printing in Apple Raster or PWG Raster always the minimum resolution got used, even if I higher one was requested, as the default resolution or by a job attribute/option which sets a higher resolution. This I fixed in libppd via: https://github.com/OpenPrinting/libppd/commit/e2190988ff6c1 Now always the correct resolution gets used for the rasterization of the job and so the correct print quality obtained. The fixes get applied to the libcupsfilters and libppd source packages both in Mantic and in Lunar (SRU). ** Affects: libcupsfilters (Ubuntu) Importance: High Status: New ** Affects: libppd (Ubuntu) Importance: High Status: New ** Affects: libcupsfilters (Ubuntu Lunar) Importance: High Status: New ** Affects: libppd (Ubuntu Lunar) Importance: High Status: New ** Affects: libcupsfilters (Ubuntu Mantic) Importance: High Status: New ** Affects: libppd (Ubuntu Mantic) Importance: High Status: New ** Also affects: libcupsfilters (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: libcupsfilters (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libppd (Ubuntu) Importance: Undecided Status: New ** Changed in: libcupsfilters (Ubuntu Lunar) Importance: Undecided => Critical ** Changed in: libcupsfilters (Ubuntu Lunar) Importance: Critical => High ** Changed in: libcupsfilters (Ubuntu Mantic) Importance: Undecided => High ** Changed in: libppd (Ubuntu Lunar) Importance: Undecided => High ** Changed in: libppd (Ubuntu Mantic) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcupsfilters in Ubuntu. https://bugs.launchpad.net/bugs/2022929 Title: Bugs in resolution handling, especially garbage printed when invalid resolution value supplied Status in libcupsfilters package in Ubuntu: New Status in libppd package in Ubuntu: New Status in libcupsfilters source package in Lunar: New Status in libppd source package in Lunar: New Status in libcupsfilters source package in Mantic: New Status in libppd source package in Mantic: New Bug description: This bug was originally reported upstream as https://github.com/OpenPrinting/libcupsfilters/issues/29 The reporter uses Fedora 38, besides Ubuntu 23.04 the second distro using cups-filters 2.x and libcupsfilters 2.x. As I am able to reproduce the bug on Ubuntu 23.04 and it is a problem many users could run into (it especially happens with driverless IPP printers) I post this bug report as base for an SRU in 23.04. What happens is that if a job is printed and along with it a resolution setting is supplied which is not supported by the printer, garbage is printed as the job gets actually rasterized with the wrong resolution. This was discovered by the Chromium Browser sending print jobs with `-o resolution=96dpi` regardless which resolutions the printer actually supports. Most driverless printers receive their jobs rasterrized into Apple Raster or PWG Raster and so for them this bug occurs. I have already fixed the bug upstream in libcupsfilters via https://github.com/OpenPrinting/libcupsfilters/commit/2892e9a63
[Desktop-packages] [Bug 2018504] Re: cups-browsed is using an excessive amount of CPU
** Also affects: cups-browsed (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: cups-browsed (Ubuntu Lunar) Status: New => In Progress ** Changed in: cups-browsed (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2018504 Title: cups-browsed is using an excessive amount of CPU Status in cups-browsed package in Ubuntu: In Progress Status in cups-browsed source package in Lunar: In Progress Bug description: [ Impact ] One observes that a certain time after booting cups-browsed suddenly starts to occupy a certain percentage or all of one CPU core. This slows down other processes on the system, consumes battery power, causes noise of the CPU fan. It does not require to have any local printers set up on ones machine, but there must be printers available in the local network. A typical trigger for this bug is a sudden disappearing of a printer in the network, for example if a laptop shares a printer and it gets suspended by closing the lid. This way the shared printer most probably disappears without the laptop's Avahi sending out some "disappered" notification. cups-browsed does not recover from the failure, once failed it consumes CPU and stops working, until being restarted, for most with the next boot. The problem got introduced on the transition from cups-browsed 1.x to 2.x (in Ubuntu 23.04). cups-browsed got a multi-threading feature added to be able to create more local queues at a time, especially when there are many printers available in the network.. The bug is in the error handling: If cups-browsed fails to access a remote printer in a sub-thread, it sets a flag to inform the main thread, to stop an update loop. The main thread misses to reset the flag once it has stopped the loop and so any further update loop during the rest of the life of cups-browsed gets stopped immediately, no printers updated at all, and as because of the updates not performed, updates are still needed and so the loop called again immediately, ending up in an infinite busy loop. And these access errors happen especially if a remote printer goes away without any DNS-SD/Avahi notification about it disappearing. So not only CPU load is caused but cups-browsed ceases completely to work. [ Test Plan ] This bug is not easy to reproduce, but at least for everyone who reported it here it occurs again and again. So everyone already suffering it is asked to test the proposed SRU package. To try to reproduce it one ideally takes 2 computers, one running Ubuntu 23.04 with the affected cups-browsed (the client) and one running any Linux and sharing printers by means of CUPS queues, Printer Applications, or the ippeveprinter utility (the server). Some ways to try to trigger the failure on the client: - Suspend the server, either by closing its laptpp lid or by selecting the "Suspend" function in its desktop's menus. - On the server start a Printer Application or ippeveprinter manually (this way no systemd watch dog applies to it). Then hard-kill its process with "kill -9 ...". - If the server is connected to the local network only by wired Ethernet, unplug its Ethernet cable. - If the server is connected to the local network only by Wi-Fi, switch it into flight mode. All these methods should make (a) shared printer(s) on the server go away without getting it properly de-registered from Avahi on the server, and so no notification being broadcasted into the local network. So the client's cups-browsed would not remove the corresponding local print queue and keep maintaining it, sooner or later failing to access the printer and then getting stuck as described above. Anyone who is suffering this bug could also simply install the proposed package and observe and when the CPU load by cups-browsed does not appear again after some days consider the fix as verified. [ Where problems could occur ] The fix does nothing more than removing the mentioned flag, and instead mark the remote printer as disappeared. This way the update loop is not stopped but finishes normally, which is no problem as the remote printers are independent, there is no reason to skip updating printers because one printer failed. After the update loop having completed, in the next update loop the local queue for the faulty printer gets removed, as it is marked as disappeared. If cups-browsed gets notified about a disappeared printer by Avahi, it also marks it as disappeared so that the queue gets removed in the next update loop. So now we do the same with faulty printers, which simply do not answer to an IPP request. As the regular procedure when a remote printer gets shut down works correctly
[Desktop-packages] [Bug 2021956] Re: crash cups-proxyd
cups-proxyd is replicating your system CUPS' print queues and IPP print services available to your system on the CUPS of the CUPS Snap. Therefore | need to know what is available on your system. So please run the following commands and post the output here: lpstat -v driverless driverless --std-ipp-uris ippfind Also please attach your file /var/snap/cups/current/var/log/cups-proxyd_log Do not compress the file. ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2021956 Title: crash cups-proxyd Status in cups package in Ubuntu: Incomplete Bug description: Ubuntu IOT Desktop 22.04 LTS # cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy Kernel Version: 5.15.0-1028-intel-iotg # journalctl --no-hostname -b --no-pager | grep cups-proxyd mai 31 11:51:22 cups.cupsd[949]: + PROXY_DAEMON=cups-proxyd mai 31 11:51:22 cups.cupsd[3032]: exec cups-proxyd /var/snap/cups/common/run/cups.sock /run/cups/cups.sock -l --logdir /var/snap/cups/872/var/log mai 31 11:51:23 audit[3032]: SECCOMP auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:23 kernel: audit: type=1326 audit(1685523083.773:85): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:24 kernel: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Error: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Snap list: # snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base chromium 113.0.5672.1262477 latest/stable canonical✓ - core20 20230503 1891 latest/stable canonical✓ base core22 20230503 634latest/stable canonical✓ base cups 2.4.2-5 872latest/stable openprinting✓ - firefox111.0-2 2432 latest/stable/… mozilla✓ - gnome-3-38-20040+git.6f39565 140latest/stable/… canonical✓ - gnome-42-2204 0+git.587e965 102latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-71-g709398e 959latest/stable/… canonical✓ - snapd 2.59.219122 latest/stable canonical✓ snapd snapd-desktop-integration 0.9 83 latest/stable/… canonical✓ - Reproduced: At every boot OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2021956/+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 2018538] Re: All PDFs when printed come out mirror image
I could reproduce it now with Ondrej's PPD file, thank you very much, Ondrej. I also found the default PPD file for the HP Colour LaserJet CP2025dn (the PostScript one of HPLIP), the printer of the original poster, Hugo Squelch, thanks, Hugo. With this I fixed it upstream now: https://github.com/OpenPrinting/libppd/commit/a86f9993674f1 All PPD files with "MirrorPrint" option cuased mirrored printout If a PPD contains an option "MirrorPrint", the ppdFilterLoadPPD() sent the option "mirror=true" to the filter functions, regardless of the actual setting of "MirrorPrint" (which is usually "False" by default). This made all printouts on printers using a PPD file with a "MirrorPrint" option coming out mirrored, with no way to counteract this by any options or attributes. This is fixed now by checking the setting of "MirrorPrint". ** Changed in: cups (Ubuntu) Status: Incomplete => In Progress ** Package changed: cups (Ubuntu) => libppd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2018538 Title: All PDFs when printed come out mirror image Status in libppd package in Ubuntu: In Progress Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libppd/+bug/2018538/+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 2018538] Re: All PDFs when printed come out mirror image
I am not able to reproduce this bug. Could anyone of you please provide me your queue's PPD file from the /etc/cups/ppd/ directory? Thanks. Could you please also run the command cupsctl --debug-logging then print a job which comes out mirrored and after that attach the file /var/log/cups/error_log to this bug report? Thanks. Please attach your files one by one, do not compress them and do not package them together. Thanks. ** Changed in: cups (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2018538 Title: All PDFs when printed come out mirror image Status in cups package in Ubuntu: Incomplete Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 2018538] Re: All PDFs when printed come out mirror image
Could you attach your print queue's PPD file(s), from /etc/cups/ppd/? Please do not compress the files, nor package them together. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2018538 Title: All PDFs when printed come out mirror image Status in cups package in Ubuntu: Confirmed Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 2017907] Re: cups-browsed high CPU usage
*** This bug is a duplicate of bug 2018504 *** https://bugs.launchpad.net/bugs/2018504 ** This bug has been marked a duplicate of bug 2018504 cups-browsed is using an excessive amount of CPU -- 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/2017907 Title: cups-browsed high CPU usage Status in cups-filters package in Ubuntu: Confirmed Bug description: Hi, Using Lunar wifi connected to an enterprise network. cups-browsed uses a lot of CPU %, I need to kill it to save my battery. 2.0rc1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2017907/+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 2016014] Re: Printing via CUPS still takes ages to start
*** This bug is a duplicate of bug 2014976 *** https://bugs.launchpad.net/bugs/2014976 The file Dependencies.txt, automatically attached to this bug report when you created it, shows that you ahve still the old cups-browsed 2.0b4 installed and not the new 2.0rc1. Only the latter contains my fix for your bug. Please update your system again. Perhaps the new cups-browsed has already arrived. ** This bug has been marked a duplicate of bug 2014976 CUPS doesnt work anymore with my HP Printer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2016014 Title: Printing via CUPS still takes ages to start Status in cups package in Ubuntu: New Bug description: The printer now prints colour again, but it is still extreme slow. When I print a page, it takes about 5 minutes to start. Again this is on all Ubuntu 23.04 but not on 22.10. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Apr 12 16:27:33 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: ASUS System Product Name Papersize: a4 PpdFiles: HP_Color_LaserJet_MFP_M280nw_83DB46: HP ColorLaserJet MFP M278-M281, driverless, 2.0rc1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (11 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016014/+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 2014976] Re: CUPS doesnt work anymore with my HP Printer
I was able to reproduce the bug with the IPP printer emulation utility ippeveprinter (package cups-ipp-utils). It is actually 2 bugs: One is that cups-browsed (which automatically creates a CUPS queue for your printer) sends PDF and not Apple Raster to your printer, and your printer is slow on processing the complex PDF format. I have done a fix on the upstream code now that if the destination printer supports both Apple Raster and PDF, the former gets preferred. This way the computer and not the printer renders and rasterizes the PDF input, and the computer has usually a much higher performance for doing this work. Upstream fix in cups-browsed: https://github.com/OpenPrinting/cups-browsed/commit/3eb66da The monochrome output is due to a bug in the PPD file generator for driverless IPP printers. If the printer reports "auto" as default for the color output mode, it selects gray instead of RGB as default. This I have fixed in libppd now: https://github.com/OpenPrinting/libppd/commit/1934a6c341 These fixes will be included in the next uploads of libppd and cups- browsed. ** Changed in: cups (Ubuntu) Importance: Undecided => High ** Package changed: cups (Ubuntu) => cups-browsed (Ubuntu) ** Also affects: libppd (Ubuntu) Importance: Undecided Status: New ** Changed in: libppd (Ubuntu) Status: New => In Progress ** Changed in: libppd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2014976 Title: CUPS doesnt work anymore with my HP Printer Status in cups-browsed package in Ubuntu: In Progress Status in libppd package in Ubuntu: In Progress Bug description: With 22.10, the autogenerated PPD has much more info inside then with 23.10. My printer needs about 5 Minutes now to start printing and prints only black and white, no colour. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 2 00:57:13 2023 InstallationDate: Installed on 2022-10-13 (170 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: ASUS System Product Name Papersize: a4 PpdFiles: HP_Color_LaserJet_MFP_M280nw_83DB46: HP ColorLaserJet MFP M278-M281, driverless, 2.0b4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (1 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2014976/+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 2014976] Re: CUPS doesnt work anymore with my HP Printer
** Changed in: cups (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2014976 Title: CUPS doesnt work anymore with my HP Printer Status in cups package in Ubuntu: In Progress Bug description: With 22.10, the autogenerated PPD has much more info inside then with 23.10. My printer needs about 5 Minutes now to start printing and prints only black and white, no colour. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 2 00:57:13 2023 InstallationDate: Installed on 2022-10-13 (170 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: ASUS System Product Name Papersize: a4 PpdFiles: HP_Color_LaserJet_MFP_M280nw_83DB46: HP ColorLaserJet MFP M278-M281, driverless, 2.0b4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (1 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2014976/+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 2003259] Re: [MIR] libcupsfilters libppd cups-browsed
** Changed in: libppd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2003259 Title: [MIR] libcupsfilters libppd cups-browsed Status in cups-browsed package in Ubuntu: Fix Released Status in libcupsfilters package in Ubuntu: Fix Released Status in libppd package in Ubuntu: New Bug description: == Summary = Source packages to be promoted to Main: - libcupsfilters - libppd - cups-browsed Binary packages to be promoted to Main: - libcupsfilters2 - libcupsfilters2-common - libppd-dev - libppd2 - libppd2-common - ppdc No source packages and no binary packages which are in Main should get demoted to Universe. == Overview Due to a major change in the printing architecture [1] the cups-filters upstream project at OpenPrinting got split into 5 components [2]: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed [1] https://openprinting.github.io/current/#the-new-architecture-for-printing-and-scanning [2] https://openprinting.github.io/cups-filters-Second-Generation-First-Beta-Release/ To reflect this in the Debian/Ubuntu packaging also the cups-filters source package there is getting split, rendering 3 new source packages (+) and therefore we need this MIR: Binaries: Source BEFORE (1.x) Source AFTER (2.x) - cups-browsed cups-filters cups-browsed + cups-filters cups-filters cups-filters cups-filters-core-drivers cups-filters cups-filters libcupsfilters-dev cups-filters libcupsfilters + libcupsfilters1 X cups-filters Replaced by   libcupsfilters2 * libcupsfilters2 + libcupsfilters + (NEW) libcupsfilters2-common +libcupsfilters + (NEW) libfontembed-dev X cups-filters REMOVED ** libfontembed X cups-filters REMOVED ** libppd-dev +libppd + (NEW) *** libppd2 + libppd + (NEW) *** libppd2-common +libppd + (NEW) *** ppdc + libppd + (NEW) *** * : libcupsfilters has new API generation/SONAME 1 -> 2 ** : libfontembed code folded into libcupsfilters, API removed, no other  package is using it. ***: libppd contains all PPD-supporting code of CUPS, as in CUPS 3.x  this code will get removed. libppd is for legacy-retro-fitting of  classic CUPS drivers with PPD files. Code comes from CUPS source:  cups/ppd*.[ch], scheduler/cups-driverd.cxx, ppdc/* X: Binary package getting REMOVED from Lunar +: Source or binary package to be promoted to Main via this MIR The purposes of the new generation's binary packages are principally the same as before: - cups-browsed: Daemon to auto-create queues for network printers and to form printer clusters - cups-filters: Print data format conversion filters and printer communication backends for CUPS 2.x - Complete set - cups-filters-core-drivers: Print data format conversion filters and printer communication backends for CUPS 2.x - Essential ones for minimum configurations, like mobile or IoT - libcupsfilters-dev: C Header files for libcupsfilters2 - libcupsfilters2: Shared library containing common code for print data conversion filters, printer drivers, printer model identification and distinction, PDF file manipulation, PDF font embedding, color space conversion, ... - libcupsfilters2-common: Architecture-indpendent auxiliary files - libppd2-dev: C Header files for libppd2 - libppd2: Shared library for support of PPD files, parsing the files, converting PPD options into IPP attributes, managing collections of PPDs, finding PPD for given printer, generating PPDs from CUPS' *.drv files - libppd2-common: Architecture-indpendent auxiliary files - ppdc: Command line tools to generate PPD files from *.drv files (only for development and debugging, or to keep scripts using them working, not end-user-facing) --> ALL THESE BINARY PACKAGES MUST BE IN MAIM, SO THE FOLLOWING BINARY PACKAGES NEED TO GET PROMOTED:   - libcupsfilters2   - libcupsfilters2-common   - libppd-dev   - libppd2   - libppd2-common   - ppdc For current CUPS (2.x, provided by Debian packages) there is
[Desktop-packages] [Bug 2008780] Re: please sync qpdf 11.3.0
The Feature Freeze got delayed, not yet in place. So I have simply synced it. Thanks for reporting ... ** Changed in: qpdf (Ubuntu) Status: New => 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/2008780 Title: please sync qpdf 11.3.0 Status in qpdf package in Ubuntu: Fix Released Bug description: I'm not sure whether a feature freeze exception is required to sync 11.3.0 given that it was uploaded just before feature freeze. In any case, 11.3.0 has a couple of bug fixes, one very localized feature enhancement (whose implementation doesn't touch any existing code), and some dramatic performance enhancements. It would be great if that can be the version in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/2008780/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
Looking at all what you told and posted here, your printer actually does not keep the input image size when getting jobs in PDF. The most reliable format for printing on driverless printers is Apple Raster. But your printer seems to simply do not print anything when receiving Apple Raster and telling to the client that everything is correctly printed. This can be due to the low toner, but then the printer has to report back to the client when not being able to print. Have you already tried to update the firmware of the printer (via appropriate functionality in the printer's web admin interface)? Have you already tried to print in monochrome (black-and-white) mode? (At least if the culprit for the "toner low" is not the black toner, see printer's web interface). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
Thanks. Please attach the PPD and error_log from that 18.04 computer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 2003259] Re: [MIR] libcupsfilters libppd cups-browsed
** Also affects: libcupsfilters (Ubuntu) Importance: Undecided Status: New ** Also affects: libppd (Ubuntu) Importance: Undecided Status: New ** Also affects: cups-browsed (Ubuntu) Importance: Undecided Status: New ** Changed in: cups-browsed (Ubuntu) Milestone: None => ubuntu-23.04-feature-freeze ** Changed in: libcupsfilters (Ubuntu) Milestone: None => ubuntu-23.04-feature-freeze ** Changed in: libppd (Ubuntu) Milestone: None => ubuntu-23.04-feature-freeze ** Changed in: libcupsfilters (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) ** Changed in: libppd (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) ** Changed in: cups-browsed (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) ** Changed in: cups-browsed (Ubuntu) Status: New => Incomplete ** Changed in: libcupsfilters (Ubuntu) Status: New => Incomplete ** Changed in: libppd (Ubuntu) Status: New => Incomplete ** No longer affects: cups-filters (Ubuntu) -- 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/2003259 Title: [MIR] libcupsfilters libppd cups-browsed Status in cups-browsed package in Ubuntu: Incomplete Status in libcupsfilters package in Ubuntu: Incomplete Status in libppd package in Ubuntu: Incomplete Bug description: This is a simplified MIR for the splitting of the cups-filters source package. With the second generation (2.x) cups-filters upstream got split into 5 independent component repositories: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed See https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ braille-printer-app still needs some upstream work for getting released, the others were already released as 2.0b2. libcupsfilters, cups-filters, and cups-browsed contain mainly the code from the former cups-filters (1.x) which is already in Main. libppd contains code from CUPS (libcups and cups-ppdc) which is also in Main. As of https://github.com/canonical/ubuntu-mir -- If a new source package contains only code which is already in main (e.g. the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a MIR bug with an explanation (but without the full template) or updating/extending on the existing old MIR bug and re-opening it by setting it to "NEW" is sufficient. -- This report does not need the full template. The original packages (cups-filters and cups) are in Main already for more than a decade, so repetition of the original MIR would not be useful. cups was already in Ubuntu from the very beginning on and therefore probably in Main since the differentiation of Main and Universe got introduced. The binary packages are named as before (except SONAME of libraries being 2 instead of 1 now), binary packages for libppd added. So current dependencies and seeding should pull in everything (libppd is a library and cups-filters depends on it). libfontembed has been discontinued (folded into libcupsfilters, API removed) but no package uses it (except the components of cups-filters 1.x thenselves). braille-printer-app will be added to this report (or a new simplified MIR report created) as soon as it gets released upstream. Its binary package(s) will need to get seeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2003259/+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 2003259] Re: [MIR] libcupsfilters libppd cups-browsed
The 4 packages of the new generation of cups-filters are uploaded to Lunar now: libcupsfilters 2.0~b2, libppd 2:2.0~b2, cups-filters 2.0~b2, cups-browsed 2.0~b2, all but cups-filters considered NEW. As soon as the NEW packages land in Universe I will add tasks for them to this MIR bug report. -- 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/2003259 Title: [MIR] libcupsfilters libppd cups-browsed Status in cups-filters package in Ubuntu: Incomplete Bug description: This is a simplified MIR for the splitting of the cups-filters source package. With the second generation (2.x) cups-filters upstream got split into 5 independent component repositories: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed See https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ braille-printer-app still needs some upstream work for getting released, the others were already released as 2.0b2. libcupsfilters, cups-filters, and cups-browsed contain mainly the code from the former cups-filters (1.x) which is already in Main. libppd contains code from CUPS (libcups and cups-ppdc) which is also in Main. As of https://github.com/canonical/ubuntu-mir -- If a new source package contains only code which is already in main (e.g. the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a MIR bug with an explanation (but without the full template) or updating/extending on the existing old MIR bug and re-opening it by setting it to "NEW" is sufficient. -- This report does not need the full template. The original packages (cups-filters and cups) are in Main already for more than a decade, so repetition of the original MIR would not be useful. cups was already in Ubuntu from the very beginning on and therefore probably in Main since the differentiation of Main and Universe got introduced. The binary packages are named as before (except SONAME of libraries being 2 instead of 1 now), binary packages for libppd added. So current dependencies and seeding should pull in everything (libppd is a library and cups-filters depends on it). libfontembed has been discontinued (folded into libcupsfilters, API removed) but no package uses it (except the components of cups-filters 1.x thenselves). braille-printer-app will be added to this report (or a new simplified MIR report created) as soon as it gets released upstream. Its binary package(s) will need to get seeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2003259/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
Sorry, what I have asked you for in the previous comment is not correct in this case, you do not need to do it. Instead, do the following: Run the command lpadmin -p testipp -E -v ipp://NPI61F41D.local:631/ipp/printer -m driverless:ipp://NPI61F41D.local:631/ipp/printer -o PageSize=A4 Test this queue by the following 2 commands: lp -d testipp 170x230.pdf lp -d testipp -o print-scaling=none 170x230.pdf Independent whether you get a correct or wrong printout, please attach the error_log and /etc/cups/ppd/testipp.ppd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
Could you stop CUPS via sudo systenctl stop cups then edit your PPD file /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd changing the line (line 21) *cupsFilter2: "application/vnd.cups-pdf application/pdf 200 -" to *%cupsFilter2: "application/vnd.cups-pdf application/pdf 200 -" The added % after the * in the beginning makes a comment line out of the line, making it inactive. This makes CUPS not trying to send PDF to your printer any more but the alternative URF Apple Raster) format (via line 22). Save the modified PPD file and start CUPS again: sudo systenctl start cups Try to print. Is the output the correct size now? It seems that if your printer receives PDF, it tries to scale the PDF pages down into the frame defined by the printer's unprintable margins, making them slightly smaller. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
I am trying to find out what exactly is happening and therefore I need to know somewhat more. Could you switch to debug logging via cupsctl --debug-logging and then print a job where the problem occurs. After that attach the file /var/log/cups/error_log to this bug report. Also attach your print queue's PPD file from /etc/cups/ppd/ to this bug report. It is the one named as your print queue. Please do not compress the files and do not package them together. Attach them one by one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1917074] Re: cups ppi parameter should be a string
Fix in cups-filters should already be in Ubuntu. Closing ... ** Changed in: cups (Ubuntu) Status: New => Invalid ** Changed in: cups-filters (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1917074 Title: cups ppi parameter should be a string Status in CUPS: Fix Released Status in cups package in Ubuntu: Invalid Status in cups-filters package in Ubuntu: Fix Released Bug description: cups encode.c treats parameter ppi as an integer, but it should be a string. the image filter drivers expect the form ppi=300x600 to specify source image dpi for images where it is asymmetric. I encountered this issue trying to print full-sized images without scaling on a dymo 450 label printer. This bug causes images to print across 2 labels when trying to use the 300x600dpi graphics mode. This should print a single label: lpr -o ppi=300x600 -o scaling=0 -o PageSize=w167h288 -o PageRegion=w167h288 -o Resolution=300x600dpi -o DymoHalftoning=Default -o DymoPrintDensity=Medium -o DymoPrintQuality=Graphics -o MediaDimensions=w167h288 ~/Desktop/test_Graphics_portrait.png where the png is a 664*2224 image without any dpi metadata. Instead the ppi option gets sanitized to 300, and the image gets printed across 2 labels. Description: Ubuntu 20.04.2 LTS Release: 20.04 cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1917074/+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 1920730] Re: gstoraster: Ghostscript runs to long while converting djvu files to Xerox`s 3210 format
After that long time the upstream fix is already in Ubuntu. Closing ...
** Changed in: cups-filters (Ubuntu)
Status: In Progress => Fix Released
--
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/1920730
Title:
gstoraster: Ghostscript runs to long while converting djvu files to
Xerox`s 3210 format
Status in cups-filters package in Ubuntu:
Fix Released
Bug description:
My OS:
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Package version: cups-filters version 1.27.4-1
When I try to print djvu files on my Xerox WorkCentre 3210 gstoraster filter,
which calls ghostscript inside runs to long while converting djvu files to
Xerox`s 3210 format.
E.x.: For 155 pages of djvu files, it runs more then 15 minutes.
I found a solution by adding -dDEVICEWIDTHPOINTS -dDEVICEHEIGHTPOINTS params
to ghostscript command inside gstoraster filter. Now the time of converting the
same file is about 30 seconds.
I`ve made patch which solves this problem.
--- a/filter/gstoraster.c
+++ b/filter/gstoraster.c
@@ -733,8 +733,17 @@
char output[31] = "";
int pagecount;
size_t bytes;
-snprintf(gscommand, 65536, "%s -q -dNOPAUSE -dBATCH -sDEVICE=bbox %s
2>&1 | grep -c HiResBoundingBox",
- CUPS_GHOSTSCRIPT, filename);
+// Ghostscript runs to long while converting djvu files to Xerox`s 3210
format
+// Using -dDEVICEWIDTHPOINTS -dDEVICEHEIGHTPOINTS params solves the
problem
+if (ppd) {
+ cupsRasterInterpretPPD(,ppd,num_options,options,0);
+ snprintf(gscommand, 65536, "%s -q -dNOPAUSE -dBATCH
-dDEVICEWIDTHPOINTS=%d -dDEVICEHEIGHTPOINTS=%d -sDEVICE=bbox %s 2>&1 | grep -c
HiResBoundingBox",
+ CUPS_GHOSTSCRIPT, h.PageSize[0], h.PageSize[1], filename);
+}
+else {
+ snprintf(gscommand, 65536, "%s -q -dNOPAUSE -dBATCH -sDEVICE=bbox %s
2>&1 | grep -c HiResBoundingBox",
+ CUPS_GHOSTSCRIPT, filename);
+}
FILE *pd = popen(gscommand, "r");
if (!pd) {
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1920730/+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 2003259] Re: [MIR] libcupsfilters libppd cups-browsed
Note that this is reported for "cups-filters" for now as the actual packages are not yet uploaded to Lunar. You can find them, plus the new cups-filters source package with the appropriate components removed, in this PPA: https://launchpad.net/~till-kamppeter/+archive/ubuntu/new-arch- dev/+packages ** Changed in: cups-filters (Ubuntu) Milestone: None => ubuntu-23.04-feature-freeze -- 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/2003259 Title: [MIR] libcupsfilters libppd cups-browsed Status in cups-filters package in Ubuntu: New Bug description: This is a simplified MIR for the splitting of the cups-filters source package. With the second generation (2.x) cups-filters upstream got split into 5 independent component repositories: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed See https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ braille-printer-app still needs some upstream work for getting released, the others were already released as 2.0b2. libcupsfilters, cups-filters, and cups-browsed contain mainly the code from the former cups-filters (1.x) which is already in Main. libppd contains code from CUPS (libcups and cups-ppdc) which is also in Main. As of https://github.com/canonical/ubuntu-mir -- If a new source package contains only code which is already in main (e.g. the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a MIR bug with an explanation (but without the full template) or updating/extending on the existing old MIR bug and re-opening it by setting it to "NEW" is sufficient. -- This report does not need the full template. The original packages (cups-filters and cups) are in Main already for more than a decade, so repetition of the original MIR would not be useful. cups was already in Ubuntu from the very beginning on and therefore probably in Main since the differentiation of Main and Universe got introduced. The binary packages are named as before (except SONAME of libraries being 2 instead of 1 now), binary packages for libppd added. So current dependencies and seeding should pull in everything (libppd is a library and cups-filters depends on it). libfontembed has been discontinued (folded into libcupsfilters, API removed) but no package uses it (except the components of cups-filters 1.x thenselves). braille-printer-app will be added to this report (or a new simplified MIR report created) as soon as it gets released upstream. Its binary package(s) will need to get seeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2003259/+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 2003259] [NEW] [MIR] libcupsfilters libppd cups-browsed
Public bug reported: This is a simplified MIR for the splitting of the cups-filters source package. With the second generation (2.x) cups-filters upstream got split into 5 independent component repositories: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed See https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ braille-printer-app still needs some upstream work for getting released, the others were already released as 2.0b2. libcupsfilters, cups-filters, and cups-browsed contain mainly the code from the former cups-filters (1.x) which is already in Main. libppd contains code from CUPS (libcups and cups-ppdc) which is also in Main. As of https://github.com/canonical/ubuntu-mir -- If a new source package contains only code which is already in main (e.g. the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a MIR bug with an explanation (but without the full template) or updating/extending on the existing old MIR bug and re-opening it by setting it to "NEW" is sufficient. -- This report does not need the full template. The original packages (cups-filters and cups) are in Main already for more than a decade, so repetition of the original MIR would not be useful. cups was already in Ubuntu from the very beginning on and therefore probably in Main since the differentiation of Main and Universe got introduced. The binary packages are named as before (except SONAME of libraries being 2 instead of 1 now), binary packages for libppd added. So current dependencies and seeding should pull in everything (libppd is a library and cups-filters depends on it). libfontembed has been discontinued (folded into libcupsfilters, API removed) but no package uses it (except the components of cups-filters 1.x thenselves). braille-printer-app will be added to this report (or a new simplified MIR report created) as soon as it gets released upstream. Its binary package(s) will need to get seeded. ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New -- 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/2003259 Title: [MIR] libcupsfilters libppd cups-browsed Status in cups-filters package in Ubuntu: New Bug description: This is a simplified MIR for the splitting of the cups-filters source package. With the second generation (2.x) cups-filters upstream got split into 5 independent component repositories: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed See https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ braille-printer-app still needs some upstream work for getting released, the others were already released as 2.0b2. libcupsfilters, cups-filters, and cups-browsed contain mainly the code from the former cups-filters (1.x) which is already in Main. libppd contains code from CUPS (libcups and cups-ppdc) which is also in Main. As of https://github.com/canonical/ubuntu-mir -- If a new source package contains only code which is already in main (e.g. the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a MIR bug with an explanation (but without the full template) or updating/extending on the existing old MIR bug and re-opening it by setting it to "NEW" is sufficient. -- This report does not need the full template. The original packages (cups-filters and cups) are in Main already for more than a decade, so repetition of the original MIR would not be useful. cups was already in Ubuntu from the very beginning on and therefore probably in Main since the differentiation of Main and Universe got introduced. The binary packages are named as before (except SONAME of libraries being 2 instead of 1 now), binary packages for libppd added. So current dependencies and seeding should pull in everything (libppd is a library and cups-filters depends on it). libfontembed has been discontinued (folded into libcupsfilters, API removed) but no package uses it (except the components of cups-filters 1.x thenselves). braille-printer-app will be added to this report (or a new simplified MIR report created) as soon as it gets released upstream. Its binary package(s) will need to get seeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2003259/+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 2002573] Re: Printer test page still emits the pre-2022 Ubuntu logo
Exact file in the source package (cups-filters) is debian/local/default-testpage-ubuntu.pdf Please keep the white area in the lower half of the page, when printing, cups-filters fills this part with printer property information. -- 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/2002573 Title: Printer test page still emits the pre-2022 Ubuntu logo Status in cups-filters package in Ubuntu: New Bug description: As it says on the tin. This is on 23.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2002573/+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 2002573] Re: Printer test page still emits the pre-2022 Ubuntu logo
Elio, looks like someone in your team would be needed here to update said PDF file with the new logo ... Please forward if needed ... ** Changed in: cups-filters (Ubuntu) Importance: Undecided => High -- 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/2002573 Title: Printer test page still emits the pre-2022 Ubuntu logo Status in cups-filters package in Ubuntu: New Bug description: As it says on the tin. This is on 23.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2002573/+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 2002573] Re: Printer test page still emits the pre-2022 Ubuntu logo
The template for the test page is /usr/share/cups/data/default- testpage.pdf which belongs to the cups-filters binary package. Moving to cups-filters ... ** Package changed: system-config-printer (Ubuntu) => cups-filters (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/2002573 Title: Printer test page still emits the pre-2022 Ubuntu logo Status in cups-filters package in Ubuntu: New Bug description: As it says on the tin. This is on 23.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2002573/+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 2002451] Re: Accidentally uploaded: cups-filters 2.0~b2-0ubuntu1
@vorlon, thank you very much! -- 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/2002451 Title: Accidentally uploaded: cups-filters 2.0~b2-0ubuntu1 Status in cups-filters package in Ubuntu: Fix Released Bug description: I have released the second generation of cups-filters some weeks ago: https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ It is an architecture change needed for the transition into the New Architecture of printing, where we will go all-IPP and classic CUPS printer drivers/filters and PPD files will get replaced by Printer Applications (emulations of driverless IPP printers). To get a smooth transition and to fade out the PPD file support code and its need to get maintained, I have split the upstream source package cups-filters into libcupsfilters, libppd, cups-filters, braille-printer-app, and cups-browsed. This especially allows to use the library libcupsfilters in Printer Applications without pulling in the PPD file support code in libppd. The Debian/Ubuntu packages will also be based on the the 5 source packages libcupsfilters, libppd, cups-filters, braille-printer-app, and cups-browsed and not come from a single cups-filters source package any more. For testing this and also solving the problem that there is a package named libppd in Debian which got abandoned 20 years ago (bug #2000411) I decided to put all the new packages, of the 2nd generation of cups- filters and also new packages depending on these, into a PPA: https://launchpad.net/~till-kamppeter/+archive/ubuntu/new-arch- dev/+packages On one of these uploads, the one of the cups-filters package, I accidentally uploaded directly to lunar and not to the PPA and it got accepted into lunar-proposed. It will not migrate to the release, as it FTBFS due to its build dependencies libcupsfilters (>= 2~) and libppd (>= 2~) not being in lunar. I want to ask you with this bug report to remove/reject this accidental upload, so that in the time being until everything with the 2nd-gen cups-filters is solved, I can upload cups-filters 1.x packages again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2002451/+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 2002451] [NEW] Accidentally uploaded: cups-filters 2.0~b2-0ubuntu1
Public bug reported: I have released the second generation of cups-filters some weeks ago: https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ It is an architecture change needed for the transition into the New Architecture of printing, where we will go all-IPP and classic CUPS printer drivers/filters and PPD files will get replaced by Printer Applications (emulations of driverless IPP printers). To get a smooth transition and to fade out the PPD file support code and its need to get maintained, I have split the upstream source package cups-filters into libcupsfilters, libppd, cups-filters, braille-printer- app, and cups-browsed. This especially allows to use the library libcupsfilters in Printer Applications without pulling in the PPD file support code in libppd. The Debian/Ubuntu packages will also be based on the the 5 source packages libcupsfilters, libppd, cups-filters, braille-printer-app, and cups-browsed and not come from a single cups-filters source package any more. For testing this and also solving the problem that there is a package named libppd in Debian which got abandoned 20 years ago (bug #2000411) I decided to put all the new packages, of the 2nd generation of cups- filters and also new packages depending on these, into a PPA: https://launchpad.net/~till-kamppeter/+archive/ubuntu/new-arch- dev/+packages On one of these uploads, the one of the cups-filters package, I accidentally uploaded directly to lunar and not to the PPA and it got accepted into lunar-proposed. It will not migrate to the release, as it FTBFS due to its build dependencies libcupsfilters (>= 2~) and libppd (>= 2~) not being in lunar. I want to ask you with this bug report to remove/reject this accidental upload, so that in the time being until everything with the 2nd-gen cups-filters is solved, I can upload cups-filters 1.x packages again. ** Affects: cups-filters (Ubuntu) Importance: High Status: New ** Changed in: cups-filters (Ubuntu) Importance: Undecided => High -- 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/2002451 Title: Accidentally uploaded: cups-filters 2.0~b2-0ubuntu1 Status in cups-filters package in Ubuntu: New Bug description: I have released the second generation of cups-filters some weeks ago: https://openprinting.github.io/cups-filters-Second-Generation-First- Beta-Release/ It is an architecture change needed for the transition into the New Architecture of printing, where we will go all-IPP and classic CUPS printer drivers/filters and PPD files will get replaced by Printer Applications (emulations of driverless IPP printers). To get a smooth transition and to fade out the PPD file support code and its need to get maintained, I have split the upstream source package cups-filters into libcupsfilters, libppd, cups-filters, braille-printer-app, and cups-browsed. This especially allows to use the library libcupsfilters in Printer Applications without pulling in the PPD file support code in libppd. The Debian/Ubuntu packages will also be based on the the 5 source packages libcupsfilters, libppd, cups-filters, braille-printer-app, and cups-browsed and not come from a single cups-filters source package any more. For testing this and also solving the problem that there is a package named libppd in Debian which got abandoned 20 years ago (bug #2000411) I decided to put all the new packages, of the 2nd generation of cups- filters and also new packages depending on these, into a PPA: https://launchpad.net/~till-kamppeter/+archive/ubuntu/new-arch- dev/+packages On one of these uploads, the one of the cups-filters package, I accidentally uploaded directly to lunar and not to the PPA and it got accepted into lunar-proposed. It will not migrate to the release, as it FTBFS due to its build dependencies libcupsfilters (>= 2~) and libppd (>= 2~) not being in lunar. I want to ask you with this bug report to remove/reject this accidental upload, so that in the time being until everything with the 2nd-gen cups-filters is solved, I can upload cups-filters 1.x packages again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2002451/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
For printing PDFs via command line, it is "lp -o print-scaling=none ...". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
Does Inkscape's print dialog not have something like a "Print Scaling" option with choices like "Auto", "Auto Fill", "Fit", "Fill", and "None"? If there is such an option you have to set it to "None", this leaves the input document in its original size. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1956533] Re: Printing anything to /dev/lp0 makes Ubuntu Server 20.04 crash
Moving to the kernel. A already the command 'echo "Test" > /dev/lp0' causes the crash, it is not caused by CUPS, but by the implementation of /dev/lp0 which is the kernel. ** Package changed: cups (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1956533 Title: Printing anything to /dev/lp0 makes Ubuntu Server 20.04 crash Status in linux package in Ubuntu: New Bug description: Whenever I try to print anything to /dev/lp0 (the parallel port of my ASUS M5A78L-M LE mainboard), my Ubuntu 20.04 server freezes completely (display gets black, no keyboard input, no network reaction). Thereby it doesn't matter whether I try printing a testpage in the webinterface of CUPS (http://localhost:631), trying to print a Windows 10 test page from a SaMBa client or try entering 'echo "Test" > /dev/lp0' on the console. When trying the latter, my HP LaserJet 6L printer prints 'Te', so a little bit of the print job seams to come out before the crash. In /var/log/syslog, there are no entries about the crash (I tried waiting 5 minutes, then do the echo test, then wait another 5 minutes before restarting to be able to isolate any possible entries caused by the crash clearly by the time stamp, but there aren't any). As a workaround, I installed a DELOCK 90413 'Serial + Parallel PCI Express x1 Card' into my server, which is recognized as /dev/lp1. When using this parallel port, printing works perfectly. In my old hardware with another mainboard, the same installation (I just changed hard disks) worked perfectly with the internal /dev/lp0. I also tried printing to the problematic parallel port on my new server hardware (the problematic one) using FreeDOS 1.3, just to confirm that my hardware is not defective, and it worked perfectly. So Ubuntu 20.04 seems to have a problem with the internal parallel port of the ASUS M5A78L-M LE mainboard. Unfortunately, I cannot tell which package is affected as I can't find any log entries. However, I guess, it's not cups, as a direct echo to /dev/lp0 also does not work. So I guess, it's something deeper. What you also need: 1) Ubuntu 20.04.3 LTS 2) I don'd know. Sorry. 3) When printing to /dev/lp0, a page should come out of the printer. 4) When printing to /dev/lp0, the whole system crashed (display black, no reaction to anything). If I can provide you further information to fix this bug, please don't hesitate to contact me. However, you need to help me how to gather it, as all my ideas are already described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956533/+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 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
Joel, thank you very much for your analysis and for posting Debian bug #1016622, as the fix has to be applied in the Debian package. ** Package changed: cups (Ubuntu) => cups-filters (Ubuntu) ** Changed in: cups-filters (Ubuntu) Status: Confirmed => Triaged ** Bug watch added: Debian Bug tracker #1016622 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016622 ** Also affects: cups-filters (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016622 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1897369 Title: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE) Status in cups-filters package in Ubuntu: Triaged Status in cups-filters package in Debian: Unknown Bug description: In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents `/usr/sbin/cups-browsed` to change its nice value. $ sudo dmesg | grep apparmor [541870.509461] audit: type=1400 audit(1600898428.089:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=62030 comm="cups-browsed" capability=23 capname="sys_nice" [628298.779668] audit: type=1400 audit(1600984854.115:61): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=66850 comm="cups-browsed" capability=23 capname="sys_nice" [714667.424963] audit: type=1400 audit(1601071220.527:62): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=76828 comm="cups-browsed" capability=23 capname="sys_nice" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1897369/+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 1979079] Re: Can print to (brother) driverless printer only using aa-complain cupsd
Please could you post the lines containing "audit", "DENIED", and "cupsd" or "cups-browsed" which are in your /var/log/syslog and/or your journal here? Try to find especially the messages which appear when you print a job until you get the error message "No suitable Destination Host found by cups-browsed". Can you print in AppArmor's complain mode? Switch to complain mode with sudo aa-complain cupsd sudo aa-complain cups-browsed and back to the default enforce mode sudo aa-enforce cupsd sudo aa-enforce cups-browsed Please try at first to only put cupsd into complain mode, after that only cups-browsed, and after that both. With which of these settings are you able to print and with which not? ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1979079 Title: Can print to (brother) driverless printer only using aa-complain cupsd Status in cups package in Ubuntu: Incomplete Bug description: The apparmor configuration for cupsd is incorrect and makes it impossible to print to driverless printers (at least to the brother printer I am trying). Cups cannot obtain the IP address of the printer. You get "No suitable Destination Host found by cups-browsed" There are multiple reports of this issue on the network, also wrt debian. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups-daemon 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jun 17 18:19:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (852 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-06-03 (14 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1979079/+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 1975459] Re: Prints blank pages
Thank you very much. As this bug can easily get worked around and as it is also fixed in cups-filters 2.x, I will not provide a fix here. Closing ... ** Changed in: cups (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1975459 Title: Prints blank pages Status in cups package in Ubuntu: Won't Fix Bug description: When printing using a wireless printer from Ubuntu it only prints blank pages. Occasinally, but not reproducable, it prints 1 job after boot and then fails. Printing from ipad and android devies to the same printer always works. This problem has persisted for several years, different versions of ubuntu on different networks and computers and several different printers. The attached file contains the cups debug log. The machine was booted 24 hours earlier. The first print job succeeded, the second failed with printer busy. I then tried to log out and back in, and only got blank pages. When that happens, the printer will continue to print blank pages until the tray is empty or removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1975459/+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 1975459] Re: Prints blank pages
The bug itself is that the implicitclass CUPS backend used by cups- browsed is not able to determine the correct parameters to generate Apple Raster from the PDF input. Your printer needs 600 dpi and for some reason 1200 dpi got sent. In cups-filters 2.x (to appear in Ubuntu 22.10) this is fixed. For the time being, please create an explicit print queue for your printer (instead of letting cups-browsed auto-creating one): lpadmin -p Brother -E -v 'ipp://Brother%20HL-L2357DW._ipp._tcp.local/' -m everywhere Try to print on this queue. Does it work? ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1975459 Title: Prints blank pages Status in cups package in Ubuntu: Incomplete Bug description: When printing using a wireless printer from Ubuntu it only prints blank pages. Occasinally, but not reproducable, it prints 1 job after boot and then fails. Printing from ipad and android devies to the same printer always works. This problem has persisted for several years, different versions of ubuntu on different networks and computers and several different printers. The attached file contains the cups debug log. The machine was booted 24 hours earlier. The first print job succeeded, the second failed with printer busy. I then tried to log out and back in, and only got blank pages. When that happens, the printer will continue to print blank pages until the tray is empty or removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1975459/+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 1972856] Re: Cannot add printer
@maxroby, could you run the following command: ipptool -tv ipps://HPF80DAC5CDC21.local:631/ipp/print get-printer- attributes.test > attrs.txt and attach attrs.txt. Please also post the screen output of this ipptool command. Thanks. ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1972856 Title: Cannot add printer Status in cups package in Ubuntu: Incomplete Bug description: When I try to add a HP OfficeJet the system cannot find drivers, it shows an error. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 15:25:16 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-21 (49 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1972856/+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 1972856] Re: Cannot add printer
Could you run the command driverless and post the output here? Does it contain the printer's URI ipps://HP%20OfficeJet%20Pro%208020%20series%20%5B5CDC21%5D._ipps._tcp.local/ or ipps://HPF80DAC5CDC21.local:631/ipp/print ? could you also run driverless 'ipps://HP%20OfficeJet%20Pro%208020%20series%20%5B5CDC21%5D._ipps._tcp.local/' > 1.ppd driverless 'ipps://HPF80DAC5CDC21.local:631/ipp/print' > 2.ppd and attach the files 1.ppd and 2.ppd? Please do not compress them and do not package them together, attach them one by one. Thanks. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1972856 Title: Cannot add printer Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When I try to add a HP OfficeJet the system cannot find drivers, it shows an error. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 15:25:16 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-21 (49 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972856/+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 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer
> These two statements seem to be contradictory. If driverless printing
is more reliable, that would seem to imply that files sent directly to
the printer print more reliably than files sent through the CUPS
filters, which would seem to imply that it is the filters, not the
printer, that have bugs.
Driverless printing does not mean sending PostScript files directly to
the printer, it means that the client discovers the printer via DNS-SD,
queries the printer for its capabilities via IPP, and then prints in one
of the formats PDF, Apple Raster, PWG Raster, or PCLm to the printer,
dpending what it supports. CUPS does this automatically if no
"conventional" print queue exists (remove any queue for your printer).
Or you can create a print queue with the lpadmin command and the "-m
everywhere" model specification.
Does this perhaps work for you?
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1968722
Title:
File fails to print when rendered with CUPS, prints fine when fed
directly to printer
Status in cups package in Ubuntu:
Incomplete
Bug description:
I have a printer named "duplex" configured to print through CUPS
PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
(recommended)", "DeviceURI
socket://m551dn.kamens.brookline.ma.us:9100" in printers.conf) and the
same physical printer configured driverless in CUPS with a different
name ("MakeModel HP LaserJet 500 color M551, driverless, cups-filters
1.28.15", "DeviceURI
implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
browsed-dest-printer "1625
ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
pdf 600dpi"") in printers.conf.
The attached file prints just fine when sent to the latter printer,
i.e., prints fine with driverless printing, but fails to print when
sent through the CUPS Postscript renderer, i.e., the former printer.
In particular, the file stops printing after four pages and then the
printer spits out this error page:
ERROR:
typecheck
OFFENDING-COMMAND:
known
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 12 08:21:44 2022
InstallationDate: Installed on 2019-01-02 (1195 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
Lpstat:
device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
device for HP_LaserJet_500_color_M551_1637DA:
implicitclass://HP_LaserJet_500_color_M551_1637DA/
device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
MachineType: Acer Predator G6-710
Papersize: letter
PpdFiles:
Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd',
'/etc/cups/ppd/duplex.ppd',
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2:
grep: /etc/cups/ppd/simplex.ppd: Permission denied
grep: /etc/cups/ppd/duplex.ppd: Permission denied
grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+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 1971473] Re: Untranslated desktop file
The "Printers" part of the GNOME Control Center is not system-config- printer, moving ... ** Package changed: system-config-printer (Ubuntu) => gnome-control- center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1971473 Title: Untranslated desktop file Status in gnome-control-center package in Ubuntu: New Bug description: Hello, I am using Ubuntu MATE and on its control centre the entry "Printers" is not translated whereas 100% translated. It comes from the desktop file apparently. It happens to me in Occitan, Catalan and French, didn't try more locales. I opened an issue here: https://github.com/mate-desktop/mate-control-center/issues/693#issuecomment-1115713053 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971473/+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 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer
Do you have cups-filter 1.28.15 installed, which fixes bug #1967816? Or
did you try the option "pdftops-renderer=gs" as described there and
which you confirmed as fixing that bug? You do not need the option if
you have cups-filter 1.28.15 installed. Or could it be that this file
now needs the "pdftops-renderer=pdftops" option to print?
Generally, driverless printing is more reliable than PostScript
printing. PostScript interpreters in printers often have bugs.
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1968722
Title:
File fails to print when rendered with CUPS, prints fine when fed
directly to printer
Status in cups package in Ubuntu:
Incomplete
Bug description:
I have a printer named "duplex" configured to print through CUPS
PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
(recommended)", "DeviceURI
socket://m551dn.kamens.brookline.ma.us:9100" in printers.conf) and the
same physical printer configured driverless in CUPS with a different
name ("MakeModel HP LaserJet 500 color M551, driverless, cups-filters
1.28.15", "DeviceURI
implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
browsed-dest-printer "1625
ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
pdf 600dpi"") in printers.conf.
The attached file prints just fine when sent to the latter printer,
i.e., prints fine with driverless printing, but fails to print when
sent through the CUPS Postscript renderer, i.e., the former printer.
In particular, the file stops printing after four pages and then the
printer spits out this error page:
ERROR:
typecheck
OFFENDING-COMMAND:
known
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 12 08:21:44 2022
InstallationDate: Installed on 2019-01-02 (1195 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
Lpstat:
device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
device for HP_LaserJet_500_color_M551_1637DA:
implicitclass://HP_LaserJet_500_color_M551_1637DA/
device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
MachineType: Acer Predator G6-710
Papersize: letter
PpdFiles:
Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd',
'/etc/cups/ppd/duplex.ppd',
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2:
grep: /etc/cups/ppd/simplex.ppd: Permission denied
grep: /etc/cups/ppd/duplex.ppd: Permission denied
grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+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 1967816] Re: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it
Backported to upstream 1.x branch in https://github.com/OpenPrinting/cups-filters/commit/2134daad68 Will be included in cups-filters 1.28.15 in Ubuntu 22.04 (Jammy). -- 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/1967816 Title: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it Status in cups-filters package in Ubuntu: In Progress Bug description: I have an HP LaserJet M551dn printer which usually works just fine with CUPS. Tonight, however, I discovered that I was completely unable to print one particular PDF file (unfortunately I can't provide you with the file because it's a scan of a tax form with PII on it). CUPS claimed that it printed the file and there are no errors in the log. On the other side, the printer doesn't show any trace of the file haven't been sent to it. The print job isn't in the job log, and at no point while CUPS claims it's printing does the printer make any noise or any of its lights blink as they usually do when a job is being sent to it. I don't know how to debug this further. I'm attaching the section of /var/log/cups/error_log from the attempt to print the file. This is reproducible every time with this particular file, including immediately after updating to all current Jammy packages and rebooting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 20:51:23 2022 InstallationDate: Installed on 2019-01-02 (1188 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA: implicitclass://HP_LaserJet_500_color_M551_1637DA/ device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/duplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-02-20 (43 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1967816/+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 1967816] Re: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it
Fixed upstream in https://github.com/OpenPrinting/cups-filters/commit/607f5e9066 ** Package changed: cups (Ubuntu) => cups-filters (Ubuntu) ** Changed in: cups-filters (Ubuntu) Importance: Undecided => Medium ** Changed in: cups-filters (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1967816 Title: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it Status in cups-filters package in Ubuntu: In Progress Bug description: I have an HP LaserJet M551dn printer which usually works just fine with CUPS. Tonight, however, I discovered that I was completely unable to print one particular PDF file (unfortunately I can't provide you with the file because it's a scan of a tax form with PII on it). CUPS claimed that it printed the file and there are no errors in the log. On the other side, the printer doesn't show any trace of the file haven't been sent to it. The print job isn't in the job log, and at no point while CUPS claims it's printing does the printer make any noise or any of its lights blink as they usually do when a job is being sent to it. I don't know how to debug this further. I'm attaching the section of /var/log/cups/error_log from the attempt to print the file. This is reproducible every time with this particular file, including immediately after updating to all current Jammy packages and rebooting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 20:51:23 2022 InstallationDate: Installed on 2019-01-02 (1188 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA: implicitclass://HP_LaserJet_500_color_M551_1637DA/ device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/duplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-02-20 (43 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1967816/+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 1967816] Re: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it
Could you print your file from the command line, using lp -d duplex file.pdf lp -d duplex -o pdftops-renderer=gs file.pdf file.pdf is the file you mention which does not print on your printer. Please try the 2 command. Tell us which of them prints which of them not. Your log shows that the job gets correctly filtered and sent off to the printer. The printer might have a bug in its PostScript interpreter making it not print some files. The "-o pdftops-renderer=gs" option of the second command lets another filter for converting your PDF file into PostScript being used. The resulting different PostScript file could perhaps not trigger the bug in the printer. You can make this setting default via lpadmin -p duplex -o pdftops-renderer-default=gs and remove the default setting via lpadmin -p duplex -R pdftops-renderer-default Please tell us your experience. ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1967816 Title: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it Status in cups package in Ubuntu: Incomplete Bug description: I have an HP LaserJet M551dn printer which usually works just fine with CUPS. Tonight, however, I discovered that I was completely unable to print one particular PDF file (unfortunately I can't provide you with the file because it's a scan of a tax form with PII on it). CUPS claimed that it printed the file and there are no errors in the log. On the other side, the printer doesn't show any trace of the file haven't been sent to it. The print job isn't in the job log, and at no point while CUPS claims it's printing does the printer make any noise or any of its lights blink as they usually do when a job is being sent to it. I don't know how to debug this further. I'm attaching the section of /var/log/cups/error_log from the attempt to print the file. This is reproducible every time with this particular file, including immediately after updating to all current Jammy packages and rebooting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 20:51:23 2022 InstallationDate: Installed on 2019-01-02 (1188 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA: implicitclass://HP_LaserJet_500_color_M551_1637DA/ device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/duplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-02-20 (43 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1967816/+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 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell
If this situation occurs for me and I press ALT + TAB then, I get back to normal and can use mouse and keyboard as usual again. -- 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/1964545 Title: 42beta: moving mouse as screen is fading to screensaver prevents input to shell Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Jammy: Triaged Bug description: [Impact] If you move the mouse as the system fades into black for the screensaver, the screensaver will be prevented as normal, but the user will not be able to interact with the shell. Mouse clicks are ignored, and most key presses are ignored too. Workaround is to press super to enter shell overview, then super again to close, and mouse clicks will begin working again. gnome-shell 42~beta-1ubuntu2 from -proposed. [Testcase] 1) Leave your system idle, until the screen starts fading to black 2) As the screen is fading to black, move the mouse to prevent screensaver. 3) Attempt to click any window or type something To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964545/+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 1964095] Re: print sent to Epson ET-2810 is not printed
I your error_log I have found the following: D [21/Mar/2022:15:08:48 +0100] [Job 312] Send-Document: client-error- document-format-error (client-error-document-format-error) This looks like that the printer was not able to work with the data it received. The printer reports that it accepts PWG Raster as the only of the known data formats used for driverless printing (it supports other formats, too, but these are formats we cannot generate). Therefore we print in PWG Raster format. It is possible that some printers have firmware bugs, not able to print certain files in standard format. It is less probable that the PWG Raster provided by us has problems as otherwise I would have received many more bug reports. Now I need also CUPS error_log output from jobs which succeeded for you and also I need the files which you have actually sent, both succeeding and failing files. Could you attach these? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964095] Re: print sent to Epson ET-2810 is not printed
Seems that your version of "driverless" is too old, not yet having the " --std-ipp-uris" option (see also output of "driverless -h"). But I have found the URI you need in your error_log. Please run the following command: ipptool -tv ipp://EPSON0EF3E0.local:631/ipp/print get-printer- attributes.test > attrs.txt and attach attrs.txt. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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
