cupsd crashed with SIGSEGV in avahi_entry_group_free()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
this bug happened during booting, the reason i issued it in a new report is i'm using newer version of ubuntu (16.04 beta)
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSign
Uname: Linux 4.4.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CupsErrorLog:
Date: Tue Apr 5 02:50:48 2016
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2016-02-14 (50 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lpstat: device for Hewlett-
MachineType: ASUSTeK COMPUTER INC. N56JRH
Papersize: letter
PpdFiles: Hewlett-
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f5c18765954 <avahi_
PC (0x7f5c18765954) ok
source "$0x0" ok
destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
avahi_
?? ()
?? ()
?? ()
?? ()
Title: cupsd crashed with SIGSEGV in avahi_entry_
UpgradeStatus: Upgraded to xenial on 2016-04-03 (1 days ago)
UserGroups:
dmi.bios.date: 09/02/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56JRH.202
dmi.board.
dmi.board.name: N56JRH
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: N56JRH
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER 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 #1442169, 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.