[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#916149: marked as done (Segfault on systemctl stop or systemctl restart)

Your message dated Fri, 14 Dec 2018 11:19:24 +0000
with message-id <E1gXlV6-000Agi-If@fasolo.debian.org>
and subject line Bug#916149: fixed in cups-filters 1.21.5-2
has caused the Debian Bug report #916149,
regarding Segfault on systemctl stop or systemctl restart
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
916149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916149
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cups-browsed
Version: 1.21.4-1
Severity: important

(Note: I'm currently running 1.21.5-1, but have set the version above
because I believe this started with 1.21.4-1. I apologize for not
reporting it earlier — I hadn't noticed it...)

Every time cups-browsed is stopped (or restarted), it segfaults. Since
its restarted every night, I checked the journal to see when this
behavior started (note the logs go back to September — so it started on
December 4). There are a bunch more on the 5th, from restarting it many
times about the now-fixed job-loss bug.

Dec 04 00:00:04 Zia systemd[1]: cups-browsed.service: Main process exited, code=killed, status=11/SEGV
Dec 05 00:00:08 Zia systemd[1]: cups-browsed.service: Main process exited, code=killed, status=11/SEGV
Dec 05 11:28:13 Zia systemd[1]: cups-browsed.service: Main process exited, code=killed, status=11/SEGV
Dec 05 11:28:42 Zia systemd[1]: cups-browsed.service: Main process exited, code=killed, status=11/SEGV
Dec 05 11:29:03 Zia systemd[1]: cups-browsed.service: Main process exited, code=killed, status=11/SEGV

The logs continue like that through present, including a few test stops
I just did to be sure.

I looked at the dpkg log and found:

2018-12-03 16:04:59 upgrade cups-browsed:amd64 1.21.3-3 1.21.4-1
2018-12-03 16:04:59 status half-configured cups-browsed:amd64 1.21.3-3
2018-12-03 16:04:59 status unpacked cups-browsed:amd64 1.21.3-3
2018-12-03 16:04:59 status half-installed cups-browsed:amd64 1.21.3-3
2018-12-03 16:05:00 status unpacked cups-browsed:amd64 1.21.4-1
⋮
2018-12-03 16:15:11 configure cups-browsed:amd64 1.21.4-1 <none>
2018-12-03 16:15:11 status unpacked cups-browsed:amd64 1.21.4-1
2018-12-03 16:15:26 conffile /etc/cups/cups-browsed.conf keep
2018-12-03 16:15:26 status half-configured cups-browsed:amd64 1.21.4-1
2018-12-03 16:15:28 status installed cups-browsed:amd64 1.21.4-1

So I think that 1.21.4-1 introduced this.

I installed systemd-coredump to get a core dump and thus back trace (via
gdb), which I have attached.


-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 'unstable-debug'), (200, 'unstable'), (150, 'stable'), (100, 'experimental-debug'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en_GB (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups-browsed depends on:
ii  cups-daemon       2.2.9-2
ii  libavahi-client3  0.7-4+b1
ii  libavahi-common3  0.7-4+b1
ii  libavahi-glib1    0.7-4+b1
ii  libc6             2.27-8
ii  libcups2          2.2.9-2
ii  libcupsfilters1   1.21.4-1
ii  libglib2.0-0      2.58.1-2
ii  libldap-2.4-2     2.4.46+dfsg-5+b1
ii  lsb-base          9.20170808

Versions of packages cups-browsed recommends:
ii  avahi-daemon  0.7-4+b1

cups-browsed suggests no packages.

-- Configuration Files:
/etc/cups/cups-browsed.conf changed:
BrowseRemoteProtocols none
BrowseLocalProtocols none
BrowsePoll watt.home
NewIPPPrinterQueuesShared No
AutoClustering No


-- no debconf information

Attachment: cups-browsed-backtrace.gz
Description: application/gzip


--- End Message ---
--- Begin Message --- 
Source: cups-filters
Source-Version: 1.21.5-2

We believe that the bug you reported is fixed in the latest version of
cups-filters, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 916149@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Didier Raboud <odyx@debian.org> (supplier of updated cups-filters package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 14 Dec 2018 11:54:44 +0100
Source: cups-filters
Binary: libcupsfilters1 libfontembed1 cups-filters cups-filters-core-drivers libcupsfilters-dev libfontembed-dev cups-browsed
Architecture: source
Version: 1.21.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team <debian-printing@lists.debian.org>
Changed-By: Didier Raboud <odyx@debian.org>
Description:
 cups-browsed - OpenPrinting CUPS Filters - cups-browsed
 cups-filters - OpenPrinting CUPS Filters - Main Package
 cups-filters-core-drivers - OpenPrinting CUPS Filters - Driverless printing
 libcupsfilters-dev - OpenPrinting CUPS Filters - Development files for the library
 libcupsfilters1 - OpenPrinting CUPS Filters - Shared library
 libfontembed-dev - OpenPrinting CUPS Filters - Development files for font embed libr
 libfontembed1 - OpenPrinting CUPS Filters - Font Embed Shared library
Closes: 916149
Changes:
 cups-filters (1.21.5-2) unstable; urgency=medium
 .
   * Backport upstream patch:
     - cups-browsed: Fixed crashes caused by checking HTTP timeouts
       (Closes: #916149)
   * Cleanup d/control thanks to `cme`
   * Add gitlab-ci.yml from Salsa CI Team
Checksums-Sha1:
 e986037d2ec5e4cc9a9f3fdf9d72d46fa4a0fadf 2775 cups-filters_1.21.5-2.dsc
 9c15560b869bb8425031db0e3256bd3d97e27fb6 74896 cups-filters_1.21.5-2.debian.tar.xz
Checksums-Sha256:
 dea6a5e0401637644d1fa61eed0b71ae921769cbb57014335934b837dd402ae9 2775 cups-filters_1.21.5-2.dsc
 6ccb49d2906758b29bf3a348e9cdc62d8ce60f5bc6845d392dcb6425f28acf11 74896 cups-filters_1.21.5-2.debian.tar.xz
Files:
 2fd4cb20a87d8a4ae5858d94b4612827 2775 net optional cups-filters_1.21.5-2.dsc
 8e8e44772f8cf734b22edd9126f35358 74896 net optional cups-filters_1.21.5-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQGzBAEBCgAdFiEEe+WPIRpjNw1/GSB7i8+nHsoWNFUFAlwTjgEACgkQi8+nHsoW
NFXNWwv9HIMH1fsmU6yfZD01/j9ZWnaKqDoCZtB5gA1pISAa8v35ZfVlzKcYiTHD
JcKnRkU4SrEOCh05iAWnt25vmJQTu1FWEHAdZO9B308PDgJjF1XndTly3aR89gdT
eZ0aiel65EPueSZ+PQ0Ty4MOfnKq8ObusTZyB/RIXMjRtYex4+nvI/tvu5kac6R0
TDZUabndV83L7FvLi1sBKNRYA5z2Yad0L7BqKiAeLnO69nZbCprn/kPORb3/2BrZ
9I1pz3W1YAZ1Qo84kv+FPzZuxBApYLdwAJIeDPkWSSz860cTuWYyMw3da0M+IM0Y
haortCjcO9ppzzGWfQHuIyMas+rbSkmx9sfyF7UTKTCEoFICCzuBwmRVmytTxCSW
pFMHwSzL0qc/BmZD79RJRfzUzl6Z3rOLo+GOrGIpdIO9ddZmp3/8qEzsJB9xVzqj
02oIOEL77R4ZDl9IR2QxbDHyoAvglAgAgFsZphjp4v/T1IZjR1HF9/bdRStcTlkz
eG1R6viR
=R8xr
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: