"There was an error during cups operation: success"
Describe the bug "There was an error during cups operation: success" when adding a remote printer using LPR. In cups webGUI, I'd entered the same printer address than in the Linux Mint add printer GUI, nothing happens when clicking "Continue". The page just get reloaded.
To Reproduce Steps to reproduce the behavior on CUPS webGUI:
- Go to 'Add printers'
- Fill with info
- Click continue
- nothing happens.
Steps to reproduce the behavior on Linux Mint add printers:
- Go to 'Add printers'
- Fill with info
- Click continue
- "There was an error during cups operation: success".
Expected behavior On both Linux GUI and CUPS webGUI, the select driver interface supposed to show up.
Screenshots
System Information:
- OS and its version: Linux Mint 21.3 x64
- CUPS version 2.4.1
Additional context I did search and, there was similar issues but not exactly what covering my problem. I do have 3 other printers on the system. Since few time, I do have the same error when adding other printers as well.
Hi,
please turn on CUPS debugging, reproduce the issue and upload the logs here with .txt suffix. See "REPORTING_ISSUES.md" for more info.
Hello,
Sorry for the delays.
When reproducing the issue, it only writes lines in access_log , nothing in error_log .
It also affects another computer, in the same way.
Guillaume
Edit
Should l recreate the issue as this one has been closed as no activity for a while?
Edit 2
There is another issue, and it seems to be a timeout when it's time to fetch a list of drivers. However, the thread ends with the reporter who can't reproduce the issue due to a hard disk failure and being forced to perform an OS fresh install.
Heres the link: https://github.com/OpenPrinting/cups/issues/641
Is that issue can be reopened? I still have an issue.
No logs in error_log is strange - have you enabled the CUPS debug logging? Or do you redirect logs into syslog/journal?
I don't plan to reopen until I have at least logs to examine.
This is what we're looking for:
Guillaume
Edit
The WebGUI is throwing that error:
It's seem having an issue when trying to retrieve the driver list.
The other few machines affected are also giving that error at the WebGUI.
I see from the logs:
D [11/Jul/2024:14:23:55 -0400] [CGI] Started ippfind (PID 656011)
I [11/Jul/2024:14:23:56 -0400] Expiring subscriptions...
D [11/Jul/2024:14:24:54 -0400] [Client 6] Closing on unexpected HTTP read state HTTP_STATE_POST_SEND.
D [11/Jul/2024:14:24:54 -0400] [Client 6] Closing connection.
D [11/Jul/2024:14:24:54 -0400] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"
I [11/Jul/2024:14:24:54 -0400] Expiring subscriptions...
D [11/Jul/2024:14:24:54 -0400] Report: clients=2
D [11/Jul/2024:14:24:54 -0400] Report: jobs=0
D [11/Jul/2024:14:24:54 -0400] Report: jobs-active=0
D [11/Jul/2024:14:24:54 -0400] Report: printers=0
D [11/Jul/2024:14:24:54 -0400] Report: stringpool-string-count=397
D [11/Jul/2024:14:24:54 -0400] Report: stringpool-alloc-bytes=5624
D [11/Jul/2024:14:24:54 -0400] Report: stringpool-total-bytes=6784
D [11/Jul/2024:14:24:54 -0400] PID 655985 (/usr/lib/cups/daemon/cups-driverd) was terminated normally with signal 9.
I see starting ippfind, but no end of it - probably we could see more when debug2 was enabled, but I kind of recall this was an issue in the past - ippfind from driverless backend from cups-filters project took too long, causing listing drivers to timeout. For sure we should not end with "success", but otherwise it is not CUPS issue.
Can you try some latest versions of cups-filters? 2.0.0 or such - based on CUPS version I guess cups-filters there will be pretty old too.
To emphasize - the fix here will be only change of error message, otherwise the issue lies in the other project -> cups-filters, but I would guess the issue is fixed in newer cups-filters releases. Basically, driverless from cups-filters needs to tell ippfind to end within reasonable time.
So, I just need to update CUPS on those two machines?
Simple as that?
Not cups, but cups-filters - two different projects on Github and two different packages. And first - I don't know for sure, but I'm running on latest projects versions in Fedora and I don't see the issue, the second - I speak from the project perspective. Whether the latest upstream versions are in your OS, that's the question for your distro maintainers.