cups-browsed crashed with SIGSEGV

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

Bug Description

This issue triggered on boot of Ubuntu 17.10

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: cups-browsed 1.14.0-1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CupsErrorLog:

Date: Wed Jun 14 08:06:46 2017
ExecutablePath: /usr/sbin/cups-browsed
InstallationDate: Installed on 2017-06-01 (12 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: System manufacturer System Product Name
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.10.0-22-generic.efi.signed root=UUID=c97344fb-bea5-4dd5-adcb-605bfd830551 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x564f05caf339: mov (%r15),%edx
 PC (0x564f05caf339) ok
 source "(%r15)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups-filters
StacktraceTop:
 ()
 avahi_service_resolver_event () at /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 () at /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
 () at /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
Title: cups-browsed crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-06-10 (4 days ago)
UserGroups:

dmi.bios.date: 01/25/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3401
dmi.board.asset.tag: Default string
dmi.board.name: Z170-DELUXE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd01/25/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Dylan Taylor (dylanmtaylor) 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 #1693632, 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.