hp crashed with SIGSEGV in _IO_vfprintf_internal()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hplip (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
no details
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: hplip 3.16.2+repack0-3
ProcVersionSign
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CupsErrorLog:
E [19/Mar/
E [19/Mar/
Date: Sat Mar 19 10:34:44 2016
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2016-01-20 (58 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160119)
Lpstat: device for psc-1300-series: hp:/usb/
MachineType: Dell Inc. Dell System XPS L702X
Papersize: a4
PpdFiles: psc-1300-series: HP PSC 1300 Series, hpcups 3.16.2
ProcCmdline: hp:/usb/
ProcEnviron:
PATH=(custom, no user)
LANG=fr_BE.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 11
SourcePackage: hplip
StacktraceTop:
_IO_vfprintf_
___vfprintf_chk (fp=fp@
__GI___vsyslog_chk (pri=<optimized out>, flag=1, fmt=0x7f6fc5e08358 "io/hpmud/musb.c 1457: unable to write data (len = %d) %s: %m\n", ap=0x7ffc2dfc9158) at ../misc/
__syslog_chk (pri=<optimized out>, flag=<optimized out>, fmt=<optimized out>) at ../misc/
?? () from /usr/lib/
Title: hp crashed with SIGSEGV in _IO_vfprintf_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 09/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.
dmi.board.vendor: Dell Inc.
dmi.board.version: FAB1
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Dell System XPS L702X
dmi.sys.vendor: Dell Inc.
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 #1553571, 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.