Attached printer not working in openSuse 13.1
Tags:
None
Registered Member 
|
As I have never looked at logs other than boot logs previously, I am uncertain about the correct procedure, although I did some research when you first asked about the tail of the error_log.
To this point, I have executed the command after the print attempts, but there may have been a delay. Should I start it before hitting the print command? If not, I can have the tail command ready in a terminal and start that almost immediately. Thanks for your patience. |
Administrator
|
Ideally, the command should be run beforehand.
You can use the following invocation to monitor each file for changes continuously. Press Control + C to exit the tail once you've finished gathering the log.
In particular, the error_log file is likely the most relevant.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Thanks for the correction. I will do that and report back.
|
|
Registered Member
|
I now ran the tail just before and then attempted to print from KATE:
From Konsole:
|
|
Administrator
|
Interesting. Did either of those print jobs succeed? If they didn't, could you try printing a document from Libreoffice so I can compare the differences between the two logs? It certainly looks like CUPS believes the print job was successful - so my guess would be a driver problem, which would explain why printing via Samba worked.
Also, it may help if you set a default printer through the CUPS interface - there seems to be quite a bit of complaint in the log about that. Finally, what is the model of printer, and what driver is the remote computer (which prints via Samba) using?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
From LibreOffice (which does print; KATE and the Konsole did not):
This log looks somewhat similar to the one previously from the attempt to print from Konsole. The printer is an HP LaserJet 4050, and the remote driver is the HP LaserJet 4050 Series Postscript (recommended) proprietary driver (same on both machines). I set the printer to default (maintenance > set as server default) and attempted (without success) to print again from KATE:
|
|
Administrator
|
Can you check the paper type in Libreoffice and Kate please? Based on some of the output, they seem to be using different types (Kate, etc use Letter - while Libreoffice uses A4). As a default, this should be correctable through the CUPS settings for your printer.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Thanks. Paper size configuration needs to corrected. Unless I'm wrong, I don't see that as causing the problem here.
What may be a contributing factor is something I mentioned at the outset - the printer is attached to the pc through a parallel port (parallel:/dev/lpt1), and here the port is on a SIIG pci card that provides the physical parallel port (the ASUS motherboard of course doesn't have one). Because of the parallel port connection, I've run into another complication. The ultimate goal for the pc is to run Windows XP in a VirtualBox vm as a guest on SuSE Linux 13.1. Much to my amazement, the vm is up and running, and I've figured how to load programs. The snag arose when I went to print - the port lp1 is not directly accessible. While there are hints and suggestions on the virtualbox forum, I'm not confident they will resolve the issue. One suggestion using command line configuration disabled the vm. Given the fact that the remote pc can print via Samba, I may be able to resolve both the local and the VirtualBox issues by placing the printer on the network (e.g., JetDirect). Of course, if I had a newer printer with a USB connection, this might well be a non-issue. The printer is a workhorse - purchased in 2000 and except for a replacement fusing roller assembly, is still going strong and I'm the only user. While some might argue that it is more printer that I need, 14 years of service more than justifies the original cost and size. |
Global Moderator
|
I've only read the last couple of posts and not really checked the logs so apologies if this has been asked before..
You got hplip installed? With it come a number of very useful subprogrammes such as hp-check! Always helped me...
Debian testing
|
|
Registered Member
|
PS. From a quick check of prices of cards that plug into the printer, it may be less expensive to buy a new printer!
|
|
Registered Member
|
hplip is referenced in several posts.
|
|
Global Moderator
|
Right, now I've had the time to read through the whole thread and while you have hplip installed you apparently haven't run hp-check yet - that output would be interesting. Also, have you run systemsettings as root and installed the printer system wide?
Debian testing
|
|
Registered Member
|
Yes, thank you. I believe I have done all of that. For details, please see: http://forums.opensuse.org/showthread.php/497358-Attached-printer-not-working-in-openSuse-13-1.
I started this thread because my printing difficulties seem to occur only with KDE applications and I thought that the folks here would have a greater insight into how those applications function. And indeed, bcooksley has me looking at logs, about which no one else previously inquired. |
|
Registered Member
|
One slight correction. I'm just fetching the logs and bcooksley is examining them. As I have not previously looked at CUPS error logs, I've just started attempting to decipher them.
|
|
Administrator
|
I've seen incorrect paper sizes causing issues like this before - that was one of the few differences I picked up between the Libreoffice log and the KDE application logs.
In terms of getting the printer passed through to Virtualbox - you can do this using IPP once it prints using CUPS on your local system (which appears to be the case as it works with Libreoffice). You will need to enable remote printing in the CUPS settings on your computer first though, otherwise it won't permit the "remote" virtual machine to send it jobs to process. In the Windows VM, add a network printer, specifying ipp://<IP address of your computer>/printers/<Printer name in CUPS> as the address. If that doesn't work then specify http://<IP address>:631/printers/<Printer name in CUPS>. Then configure it in Windows to use any Postscript print driver (search under Generic - "PS" in the name is a good indicator). Please note that this technique works well for any printer which CUPS can handle - you don't need to install drivers on the other systems either, as long as they can produce Postscript then CUPS will handle the rest of the process.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Bookmarks
Who is online
Registered users: Bing [Bot], daret, Google [Bot], Sogou [Bot]
