Arch Linux

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!
Tasklist

FS#46196 - Cups: failing at adding a printer using the web gui : strange error

Attached to Project: Arch Linux
Opened by oty yugh (otyugh) - Friday, 04 September 2015, 01:30 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 04 September 2015, 17:03 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Trying to add a printer using the CUPS web interface at http://localhost:631/ :
0)Browse to http://localhost:631/
1)"add printer"
2)Select any printer (or any IP, to a valid printer or not the issue is the same afterward : there it was valid)
3)You get there
-> http://i.imgur.com/1nFE37x.png
Now you go ahead, "continue".

4)Instantly in /var/log/cups/error-log it will pop the following line :
E [04/Sep/2015:01:32:40 +0200] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!

I guessed this file shouldn't be here so I moved it elsewhere and the error line was gone when doing this step again. But I think it does not matter (it does not change the issue that comes afterward). The real problem is, that the result showed is this after minutes of waiting:
-> http://i.imgur.com/hztcfPS.png

And nothing shows up in the error_log...



I must add that having several computers I did tried the same steps under debian jessie, and the 3)->4) step takes 0 sec and I'm asked to give by myself the ".ppd" of the printer : which is very straightforward. There I am not, it's like as if it was looking by itself to find the apropriate drivers, failing at it (I have no idea what it is going on in the 1-2 minutes of waiting everytime), but showing a really weird output "Error : success".

I know it's kind of a messy explanation, I'm totally up to take the step you say to confirm it is really a bug.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Friday, 04 September 2015, 17:03 GMT
Reason for closing:  Fixed
Additional comments about closing:  20150904-1

Loading...