cups-browsed crashed with SIGSEGV in g_main_context_dispatch()

Bug #1430504 reported by Unixuser
10
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 10 22:49:43 2015
ExecutablePath: /usr/sbin/cups-browsed
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/HP_LaserJet_Professional_P1102w?zc=NPIC61F98
MachineType: ASUSTeK COMPUTER INC. U38DT
Papersize: a4
PpdFiles: hp02: HP LaserJet Pro P1102w Foomatic/foo2zjs-z2 (recommended)
ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
ProcCmdline: /usr/sbin/cups-browsed
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic.efi.signed root=UUID=6335f52f-ce68-4707-8365-51f310d9fabc ro quiet splash vt.handoff=7
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/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: 05/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U38DT.209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U38DT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU38DT.209:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnU38DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnU38DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: U38DT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Unixuser (unixuser) 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 #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.

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.