Setting a default network cups printer
T o n g
I'm having difficulties setting a default network cups printer.
I've set the default printer on the server, and verified via the web
interface. Also, I did
lpadmin -d new_printer
on my client host, either as root and as myself.
However, the printing still goes to the old printer that I set
previously.
Anyone can help?
Thanks
--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/ie0fm5$qgg$1...@dough.gmane.org
Camaleón
> I'm having difficulties setting a default network cups printer.
>
> I've set the default printer on the server, and verified via the web
> interface. Also, I did
>
> lpadmin -d new_printer
>
> on my client host, either as root and as myself.
>
> However, the printing still goes to the old printer that I set
> previously.
>
> Anyone can help?
What does "lpstat -t | grep default" say?
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
T o n g
>> I've set the default printer on the server, and verified via the web
>> interface. Also, I did
>>
>> lpadmin -d new_printer
>>
>> on my client host, either as root and as myself.
>>
>> However, the printing still goes to the old printer that I set
>> previously.
> What does "lpstat -t | grep default" say?
Oh, that's how you find default printers --
$ lpstat -t | grep default
system default destination: epson_cx1500
Still pointing to my old printer on the client. On the server it reports
correctly.
--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/ie0gh0$qgg$2...@dough.gmane.org
David Jardine
> On Sat, 11 Dec 2010 18:34:04 +0000, Camaleón wrote:
>
> >> I've set the default printer on the server, and verified via the web
> >> interface. Also, I did
> >>
> >> lpadmin -d new_printer
> >>
> >> on my client host, either as root and as myself.
> >>
> >> However, the printing still goes to the old printer that I set
> >> previously.
>
> > What does "lpstat -t | grep default" say?
>
> Oh, that's how you find default printers --
>
> $ lpstat -t | grep default
> system default destination: epson_cx1500
>
> Still pointing to my old printer on the client. On the server it reports
> correctly.
Have you perhaps set the PRINTER environment variable? Try
printenv PRINTER
Cheers,
David
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2010121119...@gennes.augarten
Camaleón
> On Sat, 11 Dec 2010 18:34:04 +0000, Camaleón wrote:
>
>> What does "lpstat -t | grep default" say?
>
> Oh, that's how you find default printers --
>
> $ lpstat -t | grep default
> system default destination: epson_cx1500
>
> Still pointing to my old printer on the client. On the server it reports
> correctly.
Besides David's advice, have you tried by restarting cups daemon ("/etc/
init.d/cups restart") on the client side? :-?
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Rob Owens
> Hi,
>
> I'm having difficulties setting a default network cups printer.
>
> I've set the default printer on the server, and verified via the web
> interface. Also, I did
>
> lpadmin -d new_printer
>
> on my client host, either as root and as myself.
>
> However, the printing still goes to the old printer that I set
> previously.
>
sure how to do it, except for using Gnome's printer tools.
-Rob
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20101211221...@aurora.owens.net
T o n g
On Sat, 11 Dec 2010 20:00:23 +0000, Camaleón wrote:
>>> What does "lpstat -t | grep default" say?
>>
>> Oh, that's how you find default printers --
>>
>> $ lpstat -t | grep default
>> system default destination: epson_cx1500
>>
>> Still pointing to my old printer on the client. On the server it
>> reports correctly.
>
> Besides David's advice, have you tried by restarting cups daemon ("/etc/
> init.d/cups restart") on the client side? :-?
Hmm... super strange. I restarted the cups daemon on the client side, then
$ lpadmin -d hp_4l
$ lpstat -t | grep default
system default destination: epson_cx1500
$ env | grep epson || echo no found
no found
Moreover,
$ lpadmin -x epson_cx1500
$ lpc status | grep epson -A1
epson_cx1500:
printer is on device '///dev/null' speed -1
-- still there, do it again,
$ lpadmin -x epson_cx1500
$ lpc status | grep epson -A1
-- gone. however,
$ lpstat -t | grep default
system default destination: epson_cx1500
Super strange! Anyone has more ideas?
Ahh...!
$ lpoptions
auth-info-required=none copies=1 device-uri=file:///dev/null job-hold-
until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0
number-up=1 printer-info=epson_cx1500 printer-is-accepting-jobs=true
printer-is-shared=false printer-location printer-make-and-model='Epson
Stylus CX1500 - CUPS+Gutenprint v5.2.6 on 192.168.0.100' printer-state=3
printer-state-change-time=1292159331 printer-state-reasons=none printer-
type=2162692 printer-uri-supported=ipp://localhost:631/printers/
epson_cx1500
How can I change that lpoptions? Hold on... Yes,
$ lpoptions -d hp_4l
Did the trick. Now:
$ lpstat -t | grep default
system default destination: hp_4l
Thanks every one who responded.
--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/ie2ht4$qgg$3...@dough.gmane.org
Camaleón
> On Sat, 11 Dec 2010 20:00:23 +0000, Camaleón wrote:
>
>> Besides David's advice, have you tried by restarting cups daemon
>> ("/etc/ init.d/cups restart") on the client side? :-?
>
> Hmm... super strange. I restarted the cups daemon on the client side,
> then
>
> $ lpadmin -d hp_4l
(...)
> Ahh...!
>
> $ lpoptions
(...)
> How can I change that lpoptions? Hold on... Yes,
>
> $ lpoptions -d hp_4l
>
> Did the trick. Now:
>
> $ lpstat -t | grep default
> system default destination: hp_4l
>
> Thanks every one who responded.
Hum, indeed, that is the command suggested by CUPS for setting the
default printer:
***
http://www.cups.org/documentation.php/options.html
Setting the Default Printer
If you normally use a particular printer, you can tell CUPS to use it by
default using the lpoptions(1) command:
lpoptions -d printer
***
But using CUPS web interface and set the default printer from there
should have the same effect. Didn't that work for you? :-?
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
T o n g
> Hum, indeed, that is the command suggested by CUPS for setting the
> default printer:
>
> ***
> http://www.cups.org/documentation.php/options.html
>
> Setting the Default Printer
>
> If you normally use a particular printer, you can tell CUPS to use it by
> default using the lpoptions(1) command:
>
> lpoptions -d printer
Anyone know how I can get rid of this lpoptions default printer and use
system default?
> But using CUPS web interface and set the default printer from there
> should have the same effect. Didn't that work for you? :-?
That's the first thing that I tried. but I got a 404 forbidden. Tried
twice then gave up.
--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/ie3est$qgg$4...@dough.gmane.org
David Jardine
> On Sun, 12 Dec 2010 14:59:10 +0000, Camaleón wrote:
>
> > But using CUPS web interface and set the default printer from there
> > should have the same effect. Didn't that work for you? :-?
>
> That's the first thing that I tried. but I got a 404 forbidden. Tried
> twice then gave up.
404 is "Not found". 403 is "Forbidden".
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2010121301...@gennes.augarten
Camaleón
> On Sun, 12 Dec 2010 14:59:10 +0000, Camaleón wrote:
>
>> Hum, indeed, that is the command suggested by CUPS for setting the
>> default printer:
>>
>> ***
>> http://www.cups.org/documentation.php/options.html
>>
>> Setting the Default Printer
>>
>> If you normally use a particular printer, you can tell CUPS to use it
>> by default using the lpoptions(1) command:
>>
>> lpoptions -d printer
>
> Anyone know how I can get rid of this lpoptions default printer and use
> system default?
Hum... I'm not sure what do you mean here by "system default" :-)
I always set the default printer from CUPS web interface and IIRC, you
need the root password for "delicate" tasks (like adding a new printer or
setting the default one). So, I guess these actions are kept as the
"default" (system wide settings) :-?
>> But using CUPS web interface and set the default printer from there
>> should have the same effect. Didn't that work for you? :-?
>
> That's the first thing that I tried. but I got a 404 forbidden. Tried
> twice then gave up.
You should investigate that point further, it is important to have a
working CUPS web interface as most of the common task rely on it.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Joel Roth
> On Sun, 12 Dec 2010 21:30:06 +0000, T o n g wrote:
>
> > On Sun, 12 Dec 2010 14:59:10 +0000, Camaleón wrote:
> >
> >> Hum, indeed, that is the command suggested by CUPS for setting the
> >> default printer:
> >>
> >> ***
> >> http://www.cups.org/documentation.php/options.html
> >>
> >> Setting the Default Printer
> >>
> >> If you normally use a particular printer, you can tell CUPS to use it
> >> by default using the lpoptions(1) command:
> >>
> >> lpoptions -d printer
> >
> > Anyone know how I can get rid of this lpoptions default printer and use
> > system default?
> Hum... I'm not sure what do you mean here by "system default" :-)
> I always set the default printer from CUPS web interface and IIRC, you
> need the root password for "delicate" tasks (like adding a new printer or
> setting the default one). So, I guess these actions are kept as the
> "default" (system wide settings) :-?
Does anyone know how to handle this _without_ root
permissions?
I see there is an 'lp' group and user.
> >> But using CUPS web interface and set the default printer from there
> >> should have the same effect. Didn't that work for you? :-?
> >
> > That's the first thing that I tried. but I got a 404 forbidden. Tried
> > twice then gave up.
>
> You should investigate that point further, it is important to have a
> working CUPS web interface as most of the common task rely on it.
>
> Greetings,
>
> --
> Camaleón
>
>
> --
> To UNSUBSCRIBE, email to debian-us...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
> Archive: http://lists.debian.org/pan.2010.12...@gmail.com
>
--
Joel Roth
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20101213181258.GA31021@sprite
Camaleón
> On Mon, Dec 13, 2010 at 02:22:39PM +0000, Camale??n wrote:
(...)
>> I always set the default printer from CUPS web interface and IIRC, you
>> need the root password for "delicate" tasks (like adding a new printer
>> or setting the default one). So, I guess these actions are kept as the
>> "default" (system wide settings) :-?
>
> Does anyone know how to handle this _without_ root permissions?
>
> I see there is an 'lp' group and user.
As per "man lpoptions":
***
FILES
~/.cups/lpoptions - user defaults and instances created by non-root
users.
/etc/cups/lpoptions - system-wide defaults and instances created by the
root user.
***
Maybe you can try by tweaking things in each "~/.cups/lpoptions" user
file :-?
Gilbert Sullivan
> Does anyone know how to handle this _without_ root
> permissions?
>
> I see there is an 'lp' group and user.
Within the narrow context of this question I believe you can add any
regular user to the lpadmin group to give that user permissions to
configure printers through the CUPS Web interface. Having done this on
my systems allows me to use that interface for adding / removing /
configuring printers through that interface using only my normal user
name and password.
Is that what you were asking about?
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
T o n g
>> Anyone know how I can get rid of this lpoptions default printer and use
>> system default?
>
> Hum... I'm not sure what do you mean here by "system default" :-)
Hi Camaleón, thanks for your reply in other message. I did
rm ~/.cups/lpoptions
and am able to use whatever default system printer lpadmin designated.
>>> But using CUPS web interface and set the default printer from there
>>> should have the same effect. Didn't that work for you? :-?
>>
>> That's the first thing that I tried. but I got a 404 forbidden. Tried
>> twice then gave up.
>
> You should investigate that point further, it is important to have a
> working CUPS web interface as most of the common task rely on it.
I guess I got, as David pointed out, 403 "Forbidden". But that's only for
setting the default printer via the CUPS web interface. Other things, eg,
adding a printer, work fine.
Since everything is working fine for me now. I'll move onto other things
from now.
Thanks everybody who helped!
--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/ie5sha$317$2...@dough.gmane.org
Joel Roth
> On 12/13/2010 01:12 PM, Joel Roth wrote:
> >Does anyone know how to handle this _without_ root
> >permissions?
> >
> >I see there is an 'lp' group and user.
>
> Within the narrow context of this question I believe you can add any
> regular user to the lpadmin group to give that user permissions to
> configure printers through the CUPS Web interface. Having done this
> on my systems allows me to use that interface for adding / removing
> / configuring printers through that interface using only my normal
> user name and password.
> Is that what you were asking about?
Yes, and I've verified that belonging to lpadmin group
enables administration via CUPS web interface using
regular user credentials.
Thanks.
--
Joel Roth
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20101213205732.GA699@sprite
Wayne Topa
> On Mon, 13 Dec 2010 08:12:58 -1000, Joel Roth wrote:
>
>> On Mon, Dec 13, 2010 at 02:22:39PM +0000, Camale??n wrote:
>
> (...)
>
>>> I always set the default printer from CUPS web interface and IIRC, you
>>> need the root password for "delicate" tasks (like adding a new printer
>>> or setting the default one). So, I guess these actions are kept as the
>>> "default" (system wide settings) :-?
>>
>> Does anyone know how to handle this _without_ root permissions?
>>
>> I see there is an 'lp' group and user.
>
> As per "man lpoptions":
>
> ***
> FILES
> ~/.cups/lpoptions - user defaults and instances created by non-root
> users.
> /etc/cups/lpoptions - system-wide defaults and instances created by the
> root user.
> ***
>
It seems from the lpoptions man page that the files you cite above are
created by the lpoptions command. That is not so on my amd64 box. I
have partitions for stable/testing/sid and new-testing. None of them
have an /etc/cups/lpoptions file or any ~/.cups directories. I have
looked through the docs and I have yet to find any mention on what
should be in the .cups/lpoptions files. I made .cups dirs for root and
myself put the output of lpoptions in a lpoptions file. That does not
help with my problem. I believe it will help the OP with his though.
I hoped that this thread might help in getting cups to work on the
stable/testing and sid partitions. Sadly it didn't. I have, however,
cups working on a lenny (from CD) to Testing partition which is better
then nothing.
As a possible side note that may be of help to others having a similar
problem with cups. The 3 partitions that cups is not working on were
installed on the HD by a company that advertizes Debian / RedHat systems
installs. It turned out RedHat is what they know and I believe
they have something installed incorrectly for Debian. The only
partition that works correctly is the one I installed from Debian CD's.
This drive came with a system purchased 3-4 years ago.
Hope this might be of use to others.
Wayne
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
> On 12/13/2010 02:06 PM, Camaleón wrote:
>> On Mon, 13 Dec 2010 08:12:58 -1000, Joel Roth wrote:
>>
>>> Does anyone know how to handle this _without_ root permissions?
>>>
>>> I see there is an 'lp' group and user.
>>
>> As per "man lpoptions":
>>
>> ***
>> FILES
>> ~/.cups/lpoptions - user defaults and instances created by non-root
>> users.
>> /etc/cups/lpoptions - system-wide defaults and instances created by the
>> root user.
>> ***
>>
>>
> It seems from the lpoptions man page that the files you cite above are
> created by the lpoptions command.
Mmm, no, I don't think so. Or at least I didn't get in that way.
What I understand from the man page is that those files need to be
manually created by the user or by root, not just by running the
command. I can be wrong, though.
> That is not so on my amd64 box. I
> have partitions for stable/testing/sid and new-testing. None of them
> have an /etc/cups/lpoptions file or any ~/.cups directories.
Mine neither :-). I think when someone sets the printer settings using
CUPS web interface, those values are stored somewhere, in another place.
> I have looked through the docs and I have yet to find any mention on
> what should be in the .cups/lpoptions files. I made .cups dirs for
> root and myself put the output of lpoptions in a lpoptions file. That
> does not help with my problem. I believe it will help the OP with his
> though.
What was your problem? This is the first post I see from you in this
thread :-?
OTOH, it is not very clear for me what is exact role of those files. If
we read this doc:
http://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/cupsdocumentation
It says:
***
(...) Page-specific option settings cannot be set as default in the PPD
files, but they can be set by editing the ~/.cups/lpoptions or /etc/cups/
lpoptions files.
***
But does not say what to put in there or in what format.
> I hoped that this thread might help in getting cups to work on the
> stable/testing and sid partitions. Sadly it didn't. I have, however,
> cups working on a lenny (from CD) to Testing partition which is better
> then nothing.
Maybe if you explain what's wrong in your side, someone can help :-)
> As a possible side note that may be of help to others having a similar
> problem with cups. The 3 partitions that cups is not working on were
> installed on the HD by a company that advertizes Debian / RedHat systems
> installs. It turned out RedHat is what they know and I believe they
> have something installed incorrectly for Debian. The only partition
> that works correctly is the one I installed from Debian CD's. This drive
> came with a system purchased 3-4 years ago.
>
> Hope this might be of use to others.
I've never had any problem with CUPS, but true is that all the printers we
have at the office are very well supported by Linux (all are PostScript
or PCL6 based and using network adapters, just one of them is shared via
windows an using a samba backend), and still had not to play with
printers shared over a big network with VPN's or firewalls in between ;-)
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Wayne Topa
> On Mon, 13 Dec 2010 16:14:34 -0500, Wayne Topa wrote:
>
>> On 12/13/2010 02:06 PM, Camaleón wrote:
>>> On Mon, 13 Dec 2010 08:12:58 -1000, Joel Roth wrote:
>>>
>>>> Does anyone know how to handle this _without_ root permissions?
>>>>
>>>> I see there is an 'lp' group and user.
>>>
>>> As per "man lpoptions":
>>>
>>> ***
>>> FILES
>>> ~/.cups/lpoptions - user defaults and instances created by non-root
>>> users.
>>> /etc/cups/lpoptions - system-wide defaults and instances created by the
>>> root user.
>>> ***
>>>
>>>
>> It seems from the lpoptions man page that the files you cite above are
>> created by the lpoptions command.
>
> Mmm, no, I don't think so. Or at least I didn't get in that way.
>
> What I understand from the man page is that those files need to be
> manually created by the user or by root, not just by running the
> command. I can be wrong, though.
{Quote}
>
> ROOT ACCOUNT OPTIONS
> When run by the root user, lpoptions gets and sets default options and instances for all users in the /etc/cups/lpoptions
> file.
{\Quote}
>
>> That is not so on my amd64 box. I
>> have partitions for stable/testing/sid and new-testing. None of them
>> have an /etc/cups/lpoptions file or any ~/.cups directories.
>
> Mine neither :-). I think when someone sets the printer settings using
> CUPS web interface, those values are stored somewhere, in another place.
>
>> I have looked through the docs and I have yet to find any mention on
>> what should be in the .cups/lpoptions files. I made .cups dirs for
>> root and myself put the output of lpoptions in a lpoptions file. That
>> does not help with my problem. I believe it will help the OP with his
>> though.
>
> What was your problem? This is the first post I see from you in this
> thread :-?
Cups interface at localhost:631 will not connect to any of the tabs
except Home and Online Help. All others say "500 Internal Server Error".
As this thread was about, yet another cups problem, and I had not
remembered running lpoptions before I decided to see if it would/could
assist me in solving problem.
I have only had a problem with cups on this AMD64 system. It was
working fine on an 586 box, which I have used for years, until it (the
586 system) died. The Printer is an HP6P which I have used on all my
Debian systems since 1994.
Wayne
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
> On 12/13/2010 05:13 PM, Camaleón wrote:
>>> It seems from the lpoptions man page that the files you cite above are
>>> created by the lpoptions command.
>>
>> Mmm, no, I don't think so. Or at least I didn't get in that way.
>>
>> What I understand from the man page is that those files need to be
>> manually created by the user or by root, not just by running the
>> command. I can be wrong, though.
>
> {Quote}
>>
>> ROOT ACCOUNT OPTIONS
>> When run by the root user, lpoptions gets and sets default
>> options and instances for all users in the
>> /etc/cups/lpoptions file.
> {\Quote}
Okay, let me check it in my squeeze:
root@debian:~# lpoptions -d ricoh
auth-info-required=none copies=1 device-uri=socket://172.16.0.108
finishings=3 job-hold-until=no-hold job-priority=50 job-sheets=none,none
marker-change-time=1282231350 marker-colors=#000000,#000000 marker-
levels=-1,-1 marker-names='Toner,Tóner\ residual' marker-
types=toner,wasteToner number-up=1 printer-commands=none printer-
info=ricoh printer-is-accepting-jobs=true printer-is-shared=false printer-
location printer-make-and-model='Ricoh Aficio 3030 - CUPS+Gutenprint
v5.2.6' printer-state=3 printer-state-change-time=1282231350 printer-
state-reasons=none printer-type=2109460 printer-uri-supported=ipp://
localhost:631/printers/ricoh
root@debian:~# ls -l /etc/cups
total 52
-rw-r--r-- 1 root root 1281 jun 29 19:43 acroread.conf
-rw-r--r-- 1 root root 4058 jun 29 19:46 cupsd.conf
-rw-r--r-- 1 root root 4178 jun 29 19:46 cupsd.conf.default
-rw-r--r-- 1 root root 14 dic 14 10:12 lpoptions
-rw-r--r-- 1 root root 1573 jun 29 19:43 pdftops.conf
drwxr-xr-x 2 root lp 112 ago 31 17:47 ppd
-rw------- 1 root lp 1352 nov 26 21:40 printers.conf
-rw------- 1 root lp 1352 nov 17 17:25 printers.conf.O
-rw-r--r-- 1 root root 240 jul 24 12:37 raw.convs
-rw-r--r-- 1 root root 211 jul 24 12:37 raw.types
-rw-r--r-- 1 root root 186 jun 29 19:46 snmp.conf
drwx------ 2 root lp 112 jul 24 12:37 ssl
-rw-r----- 1 root lp 90 ago 21 18:05 subscriptions.conf
-rw-r----- 1 root lp 386 ago 19 17:22 subscriptions.conf.O
File "loptions" has been created there.
And now for the user:
test@debian:~$ lpoptions -d hp4250
auth-info-required=none copies=1 device-uri=socket://172.16.0.105
finishings=3 job-hold-until=no-hold job-priority=50 job-sheets=none,none
marker-change-time=1280496487 marker-colors=none,none marker-
levels=100,99 marker-names='Black\ Cartridge\ HP\ Q5942A,Maintenance\ Kit
\ HP\ 110V-Q5421A,\ 220V-Q5422A' marker-types=tonerCartridge,fuser number-
up=1 printer-commands=AutoConfigure,Clean,PrintSelfTestPage printer-
info=hp4250 printer-is-accepting-jobs=true printer-is-shared=false
printer-location printer-make-and-model='HP LaserJet 4250 Postscript
(recommended)' printer-state=3 printer-state-change-time=1280496487
printer-state-reasons=none printer-type=10522820 printer-uri-
supported=ipp://localhost:631/printers/hp4250
test@debian:~$ ls -l .cups
total 4
-rw-r--r-- 1 test test 15 dic 14 10:14 lpoptions
File is also there, so everything is working as expected and manual is
completely right. Why it fails at your side, dunno :-?
>> What was your problem? This is the first post I see from you in this
>> thread :-?
>
> Cups interface at localhost:631 will not connect to any of the tabs
> except Home and Online Help. All others say "500 Internal Server
> Error".
>
> As this thread was about, yet another cups problem, and I had not
> remembered running lpoptions before I decided to see if it would/could
> assist me in solving problem.
Ah, I remember that thread:
http://lists.debian.org/debian-user/2010/11/msg01405.html
If you are still facing the same problem and provided you removed/
reinstalled the package and nothing changed, I would open a bug report.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Wayne Topa
The working Test-squeeze has the same as yours, but, The lpoptions
file is empty. All users can use the printer. Did you edit the
lpoptions file to add users to it? I don't remember ever doing that
even when cups was working.
The Non-working squeeze is missing the lpoptions file. I have
purge/reinstalled cups* more times than I can remember.
~$ ls /media/testing/etc/cups/
classes.conf cupsd.conf cupsd.conf.dpkg-old cups-pdf.conf
printers.conf printers-old.conf raw.types ssl/
classes.conf.O cupsd.conf.default cupsd.conf.O ppd/
printers.conf.O raw.convs snmp.conf
> And now for the user:
>
> test@debian:~$ lpoptions -d hp4250
> auth-info-required=none copies=1 device-uri=socket://172.16.0.105
> finishings=3 job-hold-until=no-hold job-priority=50 job-sheets=none,none
> marker-change-time=1280496487 marker-colors=none,none marker-
> levels=100,99 marker-names='Black\ Cartridge\ HP\ Q5942A,Maintenance\ Kit
> \ HP\ 110V-Q5421A,\ 220V-Q5422A' marker-types=tonerCartridge,fuser number-
> up=1 printer-commands=AutoConfigure,Clean,PrintSelfTestPage printer-
> info=hp4250 printer-is-accepting-jobs=true printer-is-shared=false
> printer-location printer-make-and-model='HP LaserJet 4250 Postscript
> (recommended)' printer-state=3 printer-state-change-time=1280496487
> printer-state-reasons=none printer-type=10522820 printer-uri-
> supported=ipp://localhost:631/printers/hp4250
> test@debian:~$ ls -l .cups
> total 4
This works on the testing squeeze but not on the other.
>> As this thread was about, yet another cups problem, and I had not
>> remembered running lpoptions before I decided to see if it would/could
>> assist me in solving problem.
>
> Ah, I remember that thread:
>
> http://lists.debian.org/debian-user/2010/11/msg01405.html
>
> If you are still facing the same problem and provided you removed/
> reinstalled the package and nothing changed, I would open a bug report.
I don't believe it is a Debian bug. Something on the 3 partitions
installed by the system installers is affecting those partitions. Each
of them have this cups problem as well as:
2.Root login on startup comes up with a flag set that causes the root
passwd and ssh passwd to be shown on the screen. If after logging in
Ctrl C is entered, a relogin restores normal root behavior.
3. Kernel package (make-kpkg) does not run on any of those partitions.
I plan on deleting the offending partitions and installing, from CD,
the new stable on two partitions then upgrade one to Sid.
As mentioned before the installers were used to installing RedHat. I
think they left something, which I have not been able to find, somewhere
on each partition that caused these problems. Something that is normal
for RH but not Debian.
Thanks for the reply Camaleón
Wayne
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
> On 12/14/2010 04:36 AM, Camaleón wrote:
>> Okay, let me check it in my squeeze:
>>
>> root@debian:~# lpoptions -d ricoh
(...)
>> File "loptions" has been created there.
>
> The working Test-squeeze has the same as yours, but, The lpoptions file
> is empty. All users can use the printer. Did you edit the lpoptions
> file to add users to it? I don't remember ever doing that even when
> cups was working.
"/etc/cups/lpoptions" only has one line ("Default ricoh"), which was
automatically added after running the command. It doesn't have to have
nothing more as I only run the command to set the default printer.
OTOH, this command should not be needed to run at all, all the operations
can be done using CUPS web interface (when it works, of course). Take
this command as an alternative or when you need to automate the task.
> The Non-working squeeze is missing the lpoptions file. I have
> purge/reinstalled cups* more times than I can remember.
>
> ~$ ls /media/testing/etc/cups/
> classes.conf cupsd.conf cupsd.conf.dpkg-old cups-pdf.conf
> printers.conf printers-old.conf raw.types ssl/ classes.conf.O
> cupsd.conf.default cupsd.conf.O ppd/
> printers.conf.O raw.convs snmp.conf
The file should not be there unless you run the command... hum, what kind
of path is that ("/media/testing/etc/cups/")? a chrooted one? :-?
>> And now for the user:
>>
>> test@debian:~$ lpoptions -d hp4250
(...)
>> test@debian:~$ ls -l
>> .cups
>> total 4
>
> This works on the testing squeeze but not on the other.
But what error are you getting when you run it? No errors and no file? :-?
>>> As this thread was about, yet another cups problem, and I had not
>>> remembered running lpoptions before I decided to see if it would/could
>>> assist me in solving problem.
>>
>> Ah, I remember that thread:
>>
>> http://lists.debian.org/debian-user/2010/11/msg01405.html
>>
>> If you are still facing the same problem and provided you removed/
>> reinstalled the package and nothing changed, I would open a bug report.
>
> I don't believe it is a Debian bug. Something on the 3 partitions
> installed by the system installers is affecting those partitions. Each
> of them have this cups problem as well as:
>
> 2.Root login on startup comes up with a flag set that causes the root
> passwd and ssh passwd to be shown on the screen. If after logging in
> Ctrl C is entered, a relogin restores normal root behavior.
>
> 3. Kernel package (make-kpkg) does not run on any of those partitions.
>
> I plan on deleting the offending partitions and installing, from CD, the
> new stable on two partitions then upgrade one to Sid.
The cleaner install, the better. I usually have several virtual machines
for that precise purpose, one VM for lenny, other with squeeze... just
for testing software programs and different setups.
> As mentioned before the installers were used to installing RedHat. I
> think they left something, which I have not been able to find, somewhere
> on each partition that caused these problems. Something that is normal
> for RH but not Debian.
Starting form scratch in a clean environment would be desiderable, yes.
If you are still facing the problem, then yes, report it. Reporting bugs
that are not really bugs happens all the time (we are users, not devels
nor experts, we can fail), so do not worry if the error is just on your
side, the origin of the error will be shown when dealing with it in the
BTS :-)
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Wayne Topa
> On Tue, 14 Dec 2010 12:31:37 -0500, Wayne Topa wrote:
>
>> On 12/14/2010 04:36 AM, Camaleón wrote:
>
>> ~$ ls /media/testing/etc/cups/
>> classes.conf cupsd.conf cupsd.conf.dpkg-old cups-pdf.conf
>> printers.conf printers-old.conf raw.types ssl/ classes.conf.O
>> cupsd.conf.default cupsd.conf.O ppd/
>> printers.conf.O raw.convs snmp.conf
>
> The file should not be there unless you run the command... hum, what kind
> of path is that ("/media/testing/etc/cups/")? a chrooted one? :-?
It is the Testing partition on the same disk that has the problems I
mentioned.
>>> And now for the user:
>>>
>>> test@debian:~$ lpoptions -d hp4250
>
> (...)
>
>>> test@debian:~$ ls -l
>>> .cups
>>> total 4
>>
>> This works on the testing squeeze but not on the other.
>
> But what error are you getting when you run it? No errors and no file? :-?
>
As I am not booted into that partition, I can't answer that yet. I will
reboot in a while and answer that question later.
>
> Starting form scratch in a clean environment would be desiderable, yes.
> If you are still facing the problem, then yes, report it. Reporting bugs
> that are not really bugs happens all the time (we are users, not devels
> nor experts, we can fail), so do not worry if the error is just on your
> side, the origin of the error will be shown when dealing with it in the
> BTS :-)
That is another reason I got into this thread. To inform others of the
'possible' problems from Non Debian installs.
If, when I install from a new Debian CD, I have the same problem, I will
submit a bug report.
Thanks again
Wayne
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Wayne Topa
>
>> On 12/14/2010 04:36 AM, Camaleón wrote:
>
>>> Okay, let me check it in my squeeze:
>>>
>>> root@debian:~# lpoptions -d ricoh
>
> (...)
>
>>> File "loptions" has been created there.
>>
>> The working Test-squeeze has the same as yours, but, The lpoptions file
>> is empty. All users can use the printer. Did you edit the lpoptions
>> file to add users to it? I don't remember ever doing that even when
>> cups was working.
>
> "/etc/cups/lpoptions" only has one line ("Default ricoh"), which was
> automatically added after running the command. It doesn't have to have
> nothing more as I only run the command to set the default printer.
>
>>
>> This works on the testing squeeze but not on the other.
>
> But what error are you getting when you run it? No errors and no file? :-?
When lpoptions is run on the Squeeze partition (the one with cups
problem) lpoptions returns nothing. Which is how it should be because
the cups interface is not working.
On the Test-Squeeze partition with the working Cups interface, lpoptions
returns data about the default printer, as you would expect.
Note the /etc/cups/lpoptions file is empty. So cups did not enter the
printer name into that file and the printer is working OK anyway.
I am about to reformat the old lenny partition and install from a new
install CD. If that succeeds, which I believe it will, I will tnem do
to same for the Sid partition.
Thanks for an interesting thread and your replies.
Happy Holidays
Wayne
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org