Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18893 - [cups] Slow certificate creation, cups appears "frozen"
Attached to Project:
Arch Linux
Opened by David Johansson (nullvoid) - Wednesday, 31 March 2010, 11:48 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 14 August 2010, 21:53 GMT
Opened by David Johansson (nullvoid) - Wednesday, 31 March 2010, 11:48 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 14 August 2010, 21:53 GMT
|
DetailsDescription:
When printing from a Windows machine using Samba, CUPS needs a proper certificate installed in /etc/cups/ssl/. If no certificates are present, it will generate a new self signed certificate. This process does not use any PRNG and requires a lot of entropy from the kernel which takes time to collect. During the time the certificate is generated, which may range from a few minutes to hours, cups appears frozen and will not respond on the web interface and will not print either. I myself had a huge issue with finding out what the problem was. I kept reinstalling cups and was confused in why I was unable to print. This can probably be solved by having the post-install script generating a certificate using OpenSSL. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Saturday, 14 August 2010, 21:53 GMT
Reason for closing: Fixed
Additional comments about closing: added a install msg for this to svn for the next build. any other manual cert creation with openssl is less safe.
Saturday, 14 August 2010, 21:53 GMT
Reason for closing: Fixed
Additional comments about closing: added a install msg for this to svn for the next build. any other manual cert creation with openssl is less safe.
http://bbs.archlinux.org/viewtopic.php?id=93100