cups-browsed crashed with SIGSEGV in g_main_context_dispatch()

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

Bug Description

Error came up directly after login to gui. No applications launched yet besides default startup apps.

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
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CrashCounter: 1
CupsErrorLog: W [19/Mar/2015:07:26:52 +0200] Notifier for subscription 143 (dbus://) went away, retrying!
Date: Wed Mar 18 14:17:43 2015
ExecutablePath: /usr/sbin/cups-browsed
InstallationDate: Installed on 2015-01-06 (71 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac (20140722.2)
Lpstat: device for Brother-MFC-8370DN: lpd://192.168.7.61/BINARY_P1
MachineType: TOSHIBA Satellite L670
Papersize: a4
PpdFiles: Brother-MFC-8370DN: Brother MFC-8370DN BR-Script3
ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
ProcCmdline: /usr/sbin/cups-browsed
ProcEnviron:
 LANG=en_ZA.UTF-8
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=7dd02d6c-3791-4ee9-bec5-489710d6b706 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f83de83515a: movl $0x1,0xa8(%rax)
 PC (0x7f83de83515a) 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: Upgraded to vivid on 2015-02-27 (19 days ago)
UserGroups:

dmi.bios.date: 08/02/11
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 2.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NALAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 9
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvr2.30:bd08/02/11:svnTOSHIBA:pnSatelliteL670:pvrPSK3EE-05U00MF3:rvnTOSHIBA:rnNALAA:rvr1.00:cvnTOSHIBA:ct9:cvrN/A:
dmi.product.name: Satellite L670
dmi.product.version: PSK3EE-05U00MF3
dmi.sys.vendor: TOSHIBA

Revision history for this message
David Campbell-Hall (1-davidc) 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.