cups-browsed crashed with SIGSEGV in g_slist_foreach()

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

Bug Description

Unknown cause, or end-user impact. Just reporting.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: cups-browsed 1.0.67-0ubuntu1
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CupsErrorLog:
 E [29/Mar/2015:06:16:44 -0500] [Client 56] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost
 E [29/Mar/2015:08:43:35 -0500] [Client 14] Returning IPP client-error-bad-request for Create-Printer-Subscriptions (/) from localhost
Date: Sun Mar 29 06:42:22 2015
ExecutablePath: /usr/sbin/cups-browsed
InstallationDate: Installed on 2015-03-27 (2 days ago)
InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: Apple Inc. MacBookPro9,2
Papersize: letter
ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
ProcCmdline: /usr/sbin/cups-browsed
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-040000rc5-generic root=UUID=89819328-5382-41f6-885e-680b552f215d ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f7c994cccd0 <g_slist_foreach+16>: mov 0x8(%rdi),%rbx
 PC (0x7f7c994cccd0) ok
 source "0x8(%rdi)" (0x00000009) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups-filters
StacktraceTop:
 g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slist_free_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 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_slist_foreach()
UpgradeStatus: Upgraded to vivid on 2015-03-27 (2 days ago)
UserGroups:

dmi.bios.date: 08/08/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D3.B08.1208081132
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
dmi.product.name: MacBookPro9,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
penalvch (penalvch) 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 #1435287, 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.