To troubleshoot networked printing problems there are a sequence of
steps.
1. ping (ipofprinter)
nmap (ipofprinter)
The first command checks whether you can access the printer through the
network, the second shows which port numbers are used by the printer and
through this which protocols are active (80: Has web interface, 139: SMB, 443:
encrypted IPP or encrypted web interface, 515: LPD, 631: IPP, 9100: Install
nmap if needed.
2. Run the commands:
$ /usr/lib/cups/backend/snmp
$ sudo /usr/lib/cups/backend/dnssd
These will give whether the printer is found by CUPS or system-config-printer
and with what device protocols they are found with.
3. Run the command
$ /usr/lib/cups/backend/snmp <IP of the printer>
If and only if a printer does not get found by the simple
"/usr/lib/cups/backend/snmp" call.
4. Find out if your printer gets detected by CUPS:
$ lpinfo -v
5. Run the commands:
$ avahi-browse -a -v -t -r
$ avahi-browse -a -v -c -r
These commands show whether your printer is visible via DNS-SD/mDNS/BonJour.
Attach the outputs of each of these to this bug report.
Also CUPS has a web interface that gives troubleshooting tools and
helpful information http://127.0.0.1:631/
Please also enable CUPS debugging by following these instructions:
Navigate to system - administration - printing, click the gear icon and select
printer, select server in the main menu (top bar) and then settings Then check
the checkbox "Save debugging information for troubleshooting" and click "Apply".
In all Ubuntu flavors (also Kubuntu and server editions) you can run
$ cupsctl LogLevel=debug
to activate debug logging.
In Karmic and later (CUPS 1.4.x) there is an automatic debug logging only for
failed print jobs. So if you problem was a failed print job, the error_log can
already contain the desired information. Unfortunately, only 200 debug message
lines get logged per failed job. Run the command
$ cupsctl LogDebugHistory=999999
for practically unlimited logging of failed jobs.
In older versions of all flavors, where there is not yet a "cupsctl" command,
edit the file /etc/cups/cupsd.conf, find the line LogLevel ... and change it to
LogLevel debug, save the file. Then restart CUPS:
$ sudo /etc/init.d/cupsys restart
Clear the queue from any stuck jobs by deleting the jobs in the job
viewer or running the "cancel -a" command.
Try to print something. Wait until the job disappears from the queue or turns
into "Stopped" state, independent whether something gets out of the printer. If
the job never reaches "Stopped" state after the printer not showing any
reaction for a longer time you also can go on to the next step.
Scan or photograph the printout if it is not correct and attach the images to
the bug report.
Add /var/log/cups/error_log as an attachment to the bug report. Note that the
file is not accessible for normal users. From Jaunty on you can access it from
the account of the first user set up (in general users in the "adm" group).
Otherwise you need to access it as root. To view the file run
$ sudo less /var/log/cups/error_log
and to copy it for attaching to a bug report run
$ sudo cp /var/log/cups/error_log ~
$ sudo chmod 777 ~/error_log
Quinn Balazs
--
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/1213876
Title:
printer not seen by CUPS
Status in “cups” package in Ubuntu:
Incomplete
Bug description:
Hi
I am trying to report a bug with Ubuntu 13.04. From the looks of the forum I
am not the only one with this problem.
I use a Dell 1720 level display Vostro with a P8700 64 bit processor @
2.5GHz. The laptop also has 4GB. Ram & 300Gb. of hard drive. The OS as
bought is Win7 pro. I use a Canon multifunctional, an MPS560 which has
a wifi card. Access to the web is via virginmedia fibre link and
router.
I upgraded from 12.04-1 to 12.04-2 and then to 13.04, in the hope that
I would be able to use the multifn. with the upgraded CUPS.
All three parts work fine on Win7, including ink level display, both
via USB and the wifi link; so all hardware is OK.
Using Ubu13.04 and an USB cable all is fine, prints A4 text and DL
envelopes ok.
Ink level display does not work but I expected that. XSane also finds
the scanner without difficulty.
With the USB cable removed it is a disaster.
Xsane cannot see the scanner; Cups thinks the printer is available and sends
the data, which shows as either 'completed' or 'held' on the 'view print queue'
app.
I went to 192.168.0.1 via Firefox found that the MPS is 192.168.0.2
and the Dell is 192.168.03. I checked MAC and IP for the printer and
printed them. I then went to the printer and printed the LAN settings,
all matched the data from 192.168.02.report
I then pinged both the router and the printer; both returned send
times of about 2.0 mS. with a max./dev. of about 0.7mS. and returned
no data losses.
I have also been to CUPS Host:631 via Firefox, this was very interesting but
unfortunately offered no solution.
On two occasions whilst attempting to resolve the problem I got auto
bug reports with a request to send to Ubuntu, which I did.
Please help!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1213876/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
