cups-browsed crashed with SIGSEGV in g_main_context_dispatch()

Bug #1433897 reported by Sergey
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cups-filters (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash when system boot

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: cups-browsed 1.0.67-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CupsErrorLog:

Date: Wed Mar 18 01:17:36 2015
ExecutablePath: /usr/sbin/cups-browsed
InstallationDate: Installed on 2013-05-08 (679 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
Lpstat: device for Canon-MG2200-series: usb://Canon/MG2200%20series?serial=A1279F&interface=1
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
Papersize: a4
PpdFiles: Canon-MG2200-series: Canon MG2200 series - CUPS+Gutenprint v5.2.10
ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
ProcCmdline: /usr/sbin/cups-browsed
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=753d4972-e208-4a9e-8bda-109159ea1925 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fde3839115a: movl $0x1,0xa8(%rax)
 PC (0x7fde3839115a) 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/x86_64-linux-gnu/libavahi-glib.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 04/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-DS2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Sergey (djtalisman) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.