cups-browsed crashed with SIGSEGV in dbus_watch_handle()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This happens every time I boot my PC.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: cups-browsed 1.17.9-0ubuntu1
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Mon Oct 23 13:09:14 2017
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2017-10-21 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: LENOVO 20EGS0AE00
Papersize: letter
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7efe68b5bb5c <dbus_watch_
PC (0x7efe68b5bb5c) ok
source "*%rax" (0x6e4565707954
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: cups-filters
StacktraceTop:
dbus_watch_handle () from /lib/x86_
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
g_main_loop_run () from /lib/x86_
Title: cups-browsed crashed with SIGSEGV in dbus_watch_handle()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/03/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: GNET83WW (2.31 )
dmi.board.
dmi.board.name: 20EGS0AE00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad W541
dmi.product.name: 20EGS0AE00
dmi.product.
dmi.sys.vendor: LENOVO
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 #1726869, 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.