implicitclass crashed with SIGABRT in __malloc_assert()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Epson ET 2750 Series does not seem to work.
In 9.04 it worked out of the box.
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: cups-browsed 1.25.6-0ubuntu1
ProcVersionSign
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CupsErrorLog:
E [30/Sep/
W [30/Sep/
W [30/Sep/
Date: Mon Sep 30 11:32:49 2019
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2019-09-30 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
Lpstat: device for EPSON_ET_
MachineType: LENOVO 81LK
Papersize: letter
PpdFiles: EPSON_ET_
ProcCmdline: implicitclass:
ProcEnviron:
PATH=(custom, no user)
LANG=en_CA.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: cups-filters
StacktraceTop:
__malloc_assert (assertion=
sysmalloc (nb=nb@entry=384, av=av@entry=
_int_malloc (av=av@
__GI___libc_malloc (bytes=
__GI___strdup (s=0x55b7f85976d0 "ColorModel=RGB Duplex=None MediaType=
Title: implicitclass crashed with SIGABRT in __malloc_assert()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 03/21/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: BGCN17WW
dmi.board.
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: IdeaPad L340-15IRH Gaming
dmi.product.name: 81LK
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
separator:
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1845548, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.