Bug#916765: cups-browsed: Aborts when restarted with "BrowseFilter pdl postscript"

To: 916765@bugs.debian.org, 916765-submitter@bugs.debian.org
Subject: Bug#916765: cups-browsed: Aborts when restarted with "BrowseFilter pdl postscript"
From: Bernhard Übelacker <bernhardu@mailbox.org>
Date: Tue, 18 Dec 2018 19:15:27 +0100
Message-id: <[🔎] 052584b4-b208-1460-cb16-2d2249e50a1c@mailbox.org>
Reply-to: Bernhard Übelacker <bernhardu@mailbox.org>, 916765@bugs.debian.org
In-reply-to: <[🔎] 18122018104544.6537b6688ec9@desktop.copernicus.org.uk>
References: <[🔎] 18122018104544.6537b6688ec9@desktop.copernicus.org.uk> <[🔎] 18122018104544.6537b6688ec9@desktop.copernicus.org.uk> <[🔎] 18122018104544.6537b6688ec9@desktop.copernicus.org.uk>

Hello Brian Potkin,
you might want to install a core dump collector like systemd-coredump.

With that in place you might get a more verbose message in journalctl.
Also a later inspection of the coredump might be possible:

coredumpctl list
coredumpctl gdb [PID]
  bt
  quit

And even better when having the debug symbols installed like described
in [1]. Should be in your case cups-browsed-dbgsym to start with.

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace

Reply to:

Follow-Ups:
- Bug#916765: cups-browsed: Aborts when restarted with "BrowseFilter pdl postscript"
  - From: Brian Potkin <claremont102@gmail.com>

References:
- Bug#916765: cups-browsed: Aborts when restarted with "BrowseFilter pdl postscript"
  - From: Brian Potkin <claremont102@gmail.com>

Prev by Date: Bug#916765: cups-browsed: Aborts when restarted with "BrowseFilter pdl postscript"
Next by Date: Re: cups-filters_1.21.6-1_source.changes ACCEPTED into unstable
Previous by thread: Bug#916765: cups-browsed: Aborts when restarted with "BrowseFilter pdl postscript"
Next by thread: Bug#916765: cups-browsed: Aborts when restarted with "BrowseFilter pdl postscript"
Index(es):
- Date
- Thread