cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
informatione gathered automatically by Apport
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: cups-browsed 1.0.66-0ubuntu1
ProcVersionSign
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 10 22:49:43 2015
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2013-10-18 (508 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Lpstat: device for hp02: hp:/net/
MachineType: ASUSTeK COMPUTER INC. U38DT
Papersize: a4
PpdFiles: hp02: HP LaserJet Pro P1102w Foomatic/foo2zjs-z2 (recommended)
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=ru_RU.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f1e37a6915a: movl $0x1,0xa8(%rax)
PC (0x7f1e37a6915a) 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: 05/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U38DT.209
dmi.board.
dmi.board.name: U38DT
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: U38DT
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 #1427344, 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.