Public bug reported:
Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
printer (was automatically detected and set up on installation of the
system).
Every other attempt to print fails with a varying message depending on
the printing app (eg. on libreoffice write, "Cannot start printer").
Waiting a few minutes and retrying prints successfully.
Looking at cups.service journal messages while attempting to print, it
looks like the second printing attempt crashes cupsd
cupsd[<pid>]: free(): invalid pointer
systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
systemd[1]: cups.service: Failed with result core-dump
The service then proceeds to restart after a few seconds, and trying to
print again succeeds. Trying to print once more thereafter triggers the
issue again.
I could not find a trace of the coredump, and cuspd's error_log shows
nothing happening around the crash (it does show some
"org.freedesktop.ColorManager.AlreadyExists" error messages on restart,
but I figured this would be normal, I can see the same message on other
machines that have no printing issues).
I would expect this kind of event to trigger an apport report, but there
is no apport popup when it happens. Maybe because it's not a user
process, not sure (this is not my usual setup, I've not been using
Ubuntu for years).
This is a pretty standard (and recent) ubuntu install, with not much
customized; in particular no apport custom config was made, and nothing
was configured on cups side or ubuntu print settings, everything is set
up as it was autodetected on install.
The same printer works flawlessly on a different computer using Arch and
cups 2.3.3 as well (albeit without any ubuntu patches, obviously).
** Affects: cups (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-collected groovy
** Tags added: apport-collected groovy
** Description changed:
Using ubuntu 20.04, cups 2.3.3-3ubuntu1, with a networked Samsung C480
printer (was automatically detected and set up on installation of the
system).
Every other attempt to print fails with a varying message depending on
the printing app (eg. on libreoffice write, "Cannot start printer").
Waiting a few minutes and retrying prints successfully.
Looking at cups.service journal messages while attempting to print, it
looks like the second printing attempt crashes cupsd
cupsd[<pid>]: free(): invalid pointer
systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
systemd[1]: cups.service: Failed with result core-dump
The service then proceeds to restart after a few seconds, and trying to
print again succeeds. Trying to print once more thereafter triggers the
issue again.
I could not find a trace of the coredump, and cuspd's error_log shows
nothing happening around the crash (it does show some
"org.freedesktop.ColorManager.AlreadyExists" error messages on restart,
but I figured this would be normal, I can see the same message on other
machines that have no printing issues).
I would expect this kind of event to trigger an apport report, but there
is no apport popup when it happens. Maybe because it's not a user
process, not sure (this is not my usual setup, I've not been using
Ubuntu for years).
This is a pretty standard (and recent) ubuntu install, with not much
customized; in particular no apport custom config was made, and nothing
was configured on cups side or ubuntu print settings, everything is set
up as it was autodetected on install.
- The same printer works flawlessly on a different computer using Arch and
- cups 2.3.3 as well (albeit without any ubuntu patches, obviously).
+ The same printer works flawlessly on a different computer using Arch and cups
2.3.3 as well (albeit without any ubuntu patches, obviously).
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50.5
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2021-01-28 (12 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ KernLog:
+
+ Lpstat: device for Samsung_C48x_Series_SEC842519933D78_:
implicitclass://Samsung_C48x_Series_SEC842519933D78_/
+ MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
+ Package: cups 2.3.3-3ubuntu1
+ PackageArchitecture: amd64
+ Papersize: a4
+ PpdFiles: Error: command ['fgrep', '-H', '*NickName',
'/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code
2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission
denied
+ ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root
resume_offset=6731776
+ ProcEnviron:
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=<set>
+ LANG=fr_FR.UTF-8
+ SHELL=/bin/bash
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root
resume_offset=6731776
+ ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
+ RebootRequiredPkgs:
+ linux-image-5.8.0-43-generic
+ linux-base
+ Tags: groovy
+ Uname: Linux 5.8.0-41-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/05/2019
+ dmi.bios.release: 5.14
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX434DA_UM433DA.302
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX434DA
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.family: ZenBook
+ dmi.product.name: ZenBook UX434DA_UM433DA
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.
--
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/1915181
Title:
cups crashes with SIGABRT every other printing attempt
Status in cups package in Ubuntu:
New
Bug description:
Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
printer (was automatically detected and set up on installation of the
system).
Every other attempt to print fails with a varying message depending on
the printing app (eg. on libreoffice write, "Cannot start printer").
Waiting a few minutes and retrying prints successfully.
Looking at cups.service journal messages while attempting to print, it
looks like the second printing attempt crashes cupsd
cupsd[<pid>]: free(): invalid pointer
systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
systemd[1]: cups.service: Failed with result core-dump
The service then proceeds to restart after a few seconds, and trying
to print again succeeds. Trying to print once more thereafter triggers
the issue again.
I could not find a trace of the coredump, and cuspd's error_log shows
nothing happening around the crash (it does show some
"org.freedesktop.ColorManager.AlreadyExists" error messages on
restart, but I figured this would be normal, I can see the same
message on other machines that have no printing issues).
I would expect this kind of event to trigger an apport report, but
there is no apport popup when it happens. Maybe because it's not a
user process, not sure (this is not my usual setup, I've not been
using Ubuntu for years).
This is a pretty standard (and recent) ubuntu install, with not much
customized; in particular no apport custom config was made, and
nothing was configured on cups side or ubuntu print settings,
everything is set up as it was autodetected on install.
The same printer works flawlessly on a different computer using Arch
and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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
