Bug#745212: marked as done ([cups] cupsd takes 100% cpu after restart or system resume)
Your message dated Mon, 12 May 2014 17:59:11 +0200
with message-id <1580944.Rboxm8hn1u@gyllingar>
and subject line Re: Bug#745212: [cups] cupsd takes 100% cpu after restart or system resume
has caused the Debian Bug report #745212,
regarding [cups] cupsd takes 100% cpu after restart or system resume
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.)
--
745212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745212
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: [cups] cupsd takes 100% cpu after restart or system resume
- From: Marek Budyn <marek.budyn@gmail.com>
- Date: Sat, 19 Apr 2014 01:14:18 +0200
- Message-id: <5351B1CA.3030005@gmail.com>
Package: cups
Version: 1.7.2-1
Severity: normal
--- Please enter the report below this line. ---
After system resume, or on daemon restart (e.g. with 'service cups restart')
cupsd takes 100% cpu and cannot be stopped until kill is send.
--- System information. ---
Architecture: amd64
Kernel: Linux 3.13-1-amd64
Debian Release: jessie/sid
500 testing-proposed-updates ftp.icm.edu.pl
500 testing-proposed-updates ftp.debian.org
500 testing www.deb-multimedia.org
500 testing security.debian.org
500 testing ftp.icm.edu.pl
500 testing ftp.debian.org
--- Package information. ---
Depends (Version) | Installed
=====================================-+-===============
libavahi-client3 (>= 0.6.16) | 0.6.31-4
libavahi-common3 (>= 0.6.16) | 0.6.31-4
libc6 (>= 2.16) |
libcups2 (= 1.7.2-1) |
libcupscgi1 (>= 1.4.2) |
libcupsimage2 (>= 1.4.0) |
libcupsmime1 (>= 1.4.0) |
libcupsppdc1 (>= 1.4.0) |
libgcc1 (>= 1:4.1.1) |
libstdc++6 (>= 4.1.1) |
libusb-1.0-0 (>= 2:1.0.8) |
debconf (>= 1.2.9) |
OR debconf-2.0 |
libc-bin (>= 2.13) |
cups-core-drivers (>= 1.7.2-1) |
cups-daemon (>= 1.7.2-1) |
poppler-utils (>= 0.12) |
procps |
ghostscript (>= 9.02~) |
lsb-base (>= 3.2-14~) |
cups-common (>= 1.7.2-1) |
cups-server-common (>= 1.7.2-1) |
cups-client (>= 1.7.2-1) |
cups-ppdc |
cups-filters (>= 1.0.24-3~) |
Recommends (Version) | Installed
==========================================-+-=============
avahi-daemon | 0.6.31-4
colord | 1.0.6-1
cups-filters (>= 1.0.42) | 1.0.52-1
OR foomatic-filters (>= 4.0) |
printer-driver-gutenprint | 5.2.9-1
cups-filters (>= 1.0.36) | 1.0.52-1
OR ghostscript-cups (>= 9.02~) |
Suggests (Version) | Installed
==========================================-+-===========
cups-bsd | 1.7.2-1
foomatic-db-compressed-ppds |
OR foomatic-db | 20140325-1
printer-driver-hpcups | 3.14.1-1
hplip | 3.14.1-1
cups-pdf | 2.6.1-9
udev | 204-8
smbclient | 2:4.1.6+dfsg-1
--- End Message ---
--- Begin Message ---
Hi Marek,
Le dimanche, 11 mai 2014, 14.14:34 Marek Budyn a écrit :
> I have performed another system upgrade, full restart and since then I
> cannot reproduce the issue.
> Thus, I believe it was caused by some incompatibility after upgrade
> without full restart.
>
> I believe you can close the bug.
Great then, thanks!
> Sorry for fake report.
No problem; glad to know it's solved!
Cheers,
OdyX
--- End Message ---
Reply to: