*** This bug is a duplicate of bug 1971242 ***
https://bugs.launchpad.net/bugs/1971242
I suspect this problem is caused by this issue
(https://github.com/OpenPrinting/cups/pull/500) that is fixed in cups
where the option print-color-mode is set to monochrome when the printer
PPD file has Color
I suspect this problem is caused by this issue
(https://github.com/OpenPrinting/cups/pull/500) that is fixed in cups
where the option print-color-mode is set to monochrome when the printer
PPD file has ColorModel: CMYK and not ColorModel: RGB (Our Ricoh C4500
uses CMYK as its ColorModel: CMYK)
We
@sil2100 it works for me as long as I set AuthType Default for / (which
I didn't have to set before but I'm happy to set it now)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1783298
Titl
If I also set "AuthType Default" for "/" then the cups 2.2.7-1ubuntu2.4 works.
I did not have this set in 14.04 or 16.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1783298
Title:
[S
cups 2.2.7-1ubuntu2.4 from proposed has exactly the same symptoms for me
- prompts for password when printing. So the original issue seems to be
different from Esko's.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https:
Unfortunately my possible workaround in comments 3 & 4 only partially
work - cups stops prompting for a password but its smb backend
(/usr/lib/x86_64-linux-gnu/samba/smbspool_krb5_wrapper) does not receive
the AUTH_UID is not set and therefore cannot spool the job the a Windows
print server.
I'm a
Here is my proposed solution (attached) to the problem - I do not claim
to fully understand cups' authentication system but it seems to me from
looking at the old code to cups/auth.c and the new broken code that this
patch would make the unix domain socket authentication work the same as
it did bef
My suggested work around above does not fix the issue (completely)
because systemd is in charge of the socket - so as well as commenting
out "Listen /run/cups/cups.sock" in /etc/cups/cupsd.conf you have to
also do the following:
systemctl stop cups.service
systemctl stop cups.socket
rm /run/cups/c
It appears that it first stops working in cups version 2.2.7 when there
is a major change in cups/auth.c.
It is still broken in the current cups github repo master branch.
I have noticed it works correctly if you disable the unix domain socket,
e.g. comment out
Listen /run/cups/cups.sock
in /et
The above setup work fine in Ubuntu 17.10 as well which uses cups 2.2.4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1783298
Title:
AuthInfoRequired negotiate in cups 2.2.7 in Bionic d
Public bug reported:
Hi,
We have our printers configured to print to a Windows print server. In
Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems
to be acting more like AuthInfoRequired username,password i.e. it
prompts for a password when printing rather than using the av
Public bug reported:
In Ubuntu 16.04 using cups version 2.1.3-4 the cups daemon leaves tcp sockets
in CLOSE_WAIT state if a client uses kerberos authentication with encryption
(the default for authenticated connections). cupds will then also consume 100%
of a CPU.
The impact of this bug is th
12 matches
Mail list logo
