When using the add printer wizard through the control panel on my 64-bit install, I can get only so far then come to this error
Printer is on the network, not connected through a cable.
I have already added it using the cups localhost method through a browser, so this is more of a notification to see if others can reproduce the result than a call for help
topic title: Adding printer error - cups authorization cancelled
4 posts
• Page 1 of 1
-
pcpavnzPosts: 19
- Joined: 09 Nov 2012
-
DavePosts: 1,062
- Joined: 20 Jan 2010
#2
Yes I have gotten this error recently, but I cannot comment on it being a problem with any of the recent releases.
I bought a new printer recently (samsung ML-2165) and installed the drivers and configured the printer for a few computers.
All of the computers worked fine, except for one. The one that gave the above error.
This was an 8.5 install that when installing the printer driver apt updated cups..... As said above in the 8.5 install I could configure the printer via localhost:631. It is using a newer version of cups than the other computers due to the apt upgrade. So Maybe this is a confict between system-config-printer and the latest cups version.
I bought a new printer recently (samsung ML-2165) and installed the drivers and configured the printer for a few computers.
All of the computers worked fine, except for one. The one that gave the above error.
This was an 8.5 install that when installing the printer driver apt updated cups..... As said above in the 8.5 install I could configure the printer via localhost:631. It is using a newer version of cups than the other computers due to the apt upgrade. So Maybe this is a confict between system-config-printer and the latest cups version.
-
dolphin_oraclePosts: 2,238
- Joined: 16 Dec 2007
#3
I don't know if its related, but when installing my brother printer drives, I have to add my user name to the lpadmin group in order to configure the driver with system-config-printer. I get an authorization error as well.
-
SamKPosts: 1,028
- Joined: 21 Aug 2011
#4
I have not yet had an opportunity to do more than a superficial look at 13.2 but it looks as though the bug fix reported for 13.1 is not included in 13.2.
The symptoms and Debian fix are here
post30877.html?hilit=printer#p30877
Might it be possible to have the fix issued as part of the usual upgrade mechanism and applied to existing accounts? It might be worthwhile in view of Photoprint being added in 13.2.
The symptoms and Debian fix are here
post30877.html?hilit=printer#p30877
Might it be possible to have the fix issued as part of the usual upgrade mechanism and applied to existing accounts? It might be worthwhile in view of Photoprint being added in 13.2.