cups-browsed crashed with SIGSEGV in avahi_service_browser_event()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Closed laptop lid to go to sleep. When I opened it later, it never went to sleep. Just had this crash message.
Distributor ID: Ubuntu
Description: Ubuntu Zesty Zapus (development branch)
Release: 17.04
Codename: zesty
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: cups-browsed 1.13.4-1ubuntu1
ProcVersionSign
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Sun Mar 26 18:37:05 2017
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2015-10-29 (515 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lpstat: device for HL-5470DW: dnssd:/
MachineType: Hewlett-Packard HP ProBook 6540b
Papersize: letter
PpdFiles: HL-5470DW: Brother HL-5470DW for CUPS
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 11
SourcePackage: cups-filters
StacktraceTop:
?? ()
avahi_
?? () from /usr/lib/
dbus_connectio
?? () from /usr/lib/
Title: cups-browsed crashed with SIGSEGV in avahi_service_
UpgradeStatus: Upgraded to zesty on 2017-03-25 (3 days ago)
UserGroups:
dmi.bios.date: 03/28/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CDD Ver. F.21
dmi.board.name: 1722
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 29.37
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP ProBook 6540b
dmi.sys.vendor: Hewlett-Packard
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 #1676057, 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.