Re: CUPS problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Wade,
this is what happes:

[root@localhost par]# /sbin/service cups restart
Stopping cups:                                             [  OK  ]
Starting cups:                                             [  OK  ]

No clue - it seems.

Brgds
PAR

Wade Hampton wrote:
Do you get an error when you run /sbin/service cups restart?  Check
/var/log/messages.  On one of my computers, I am getting an error
about can't read cupsd.conf and the printer daemon is not starting
(see my other posting).  I can start cupsd manually, however.
--
Wade Hampton

On 8/22/07, PerAntonRønning <pa-ronn@xxxxxxxxx> wrote:
Karl,
thank you. The problem is that I did remove the printer, then I added it
again, but it still could not get in contact with CUPS.
No printing takes effect, not only the testpage.
I also have trouble starting system-config-printer, and any efforts to
do printer management is rejected. So I wonder if there is something
wrong with my CUPS, but I have never done any installation or
configuration of CUPS before, so there I am a novice.

Brgds
PAR


Karl Larsen wrote:
PerAntonRønning wrote:
After a long period of smooth sailing I suddenly encountered a CUPS
problem.
Why I have got it is uncertain, maybe as a result of a yum upgrade
run. I had to reinstall FC 5 due to some disk trouble (possibly
because a blown fuse cut the electricity supply to my desk)
so I imagined that I would be interested in upgraded programs since I
burned the FC5 distro.

I remove and reinstall the printer (which btw. is online, lights are
up :-) ) and when sending a testpage to the printer i get the
following message:

"There was a problem sending CUPS test page to laser1 queue (my
chosen printer name)

/usr/bin/lpr  connection refused

The following daemons are running:
cupsd
cups-config-daemon

I would be grateful to receive some help on this one.

Brgds
PAR




   I had a problem like that. I had to delete the printer from the
printer setup program and then re-load it with the same name and so
forth. It fixed the problem.



--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux