cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Automatic report
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: cups-browsed 1.0.67-0ubuntu1
ProcVersionSign
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Mon Mar 30 16:25:00 2015
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2014-10-24 (157 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
Lpstat: device for Samsung-ML-2160: smb://LAPTOP_
MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-1454
Papersize: a4
PpdFiles: Samsung-ML-2160: Samsung ML-2160, 2.0.0
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=es_UY.UTF-8
LANGUAGE=es_UY:es
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f7a4c5e115a: movl $0x1,0xa8(%rax)
PC (0x7f7a4c5e115a) 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: Upgraded to vivid on 2015-01-05 (84 days ago)
UserGroups:
dmi.bios.date: 03/30/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1454IMS.110
dmi.board.
dmi.board.name: MS-1454
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: REV:1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: MS-1454
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-1454
dmi.product.
dmi.sys.vendor: MICRO-STAR INTERNATIONAL 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.