cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
report automatically generated by the system
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: cups-browsed 1.0.67-0ubuntu1
ProcVersionSign
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CupsErrorLog: W [15/Mar/
Date: Fri Mar 13 19:01:13 2015
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2015-03-09 (5 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
Lpstat: device for HP-Deskjet-
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2
Papersize: a4
PpdFiles: HP-Deskjet-
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=es_AR.UTF-8
LANGUAGE=es_AR:es
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f44f30a115a: movl $0x1,0xa8(%rax)
PC (0x7f44f30a115a) ok
source "$0x1" ok
destination "0xa8(%rax)" (0x000000a8) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: cups-filters
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
Title: cups-browsed crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 08/14/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: GA-78LMT-S2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: GA-78LMT-S2
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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 #1431041, 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.