Printing broken by Updates of 2006 Aug 1

Bug #55205 reported by ScottHerman
12
Affects Status Importance Assigned to Milestone
cupsys (Ubuntu)
Invalid
Medium
Unassigned
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Updates from 2006 Aug 1 broke printing entirely on my machine, an old compaq p3. Printing worked before the updates. I printed something that morning from firefox, before the updates. After the updates, printing broken.

Attempts to obtain print subsytem status via the AlaCarte applications menu (System-->Administration-->Printing) attempted to launch, but failed.

lpstat hangs.

/var/log/cups/error_log is empty.

attmpts to browse to http://localhost:631/ hang.

attempts to print from firefox, or any other printing application, hang.

Updates included gnome updates, firefox updates.

This machine has no printer connected directly to it, but prints through cups using printers on our local network.

Tags: printing
description: updated
Revision history for this message
Maxence DUNNEWIND (maxenced) wrote :

Did you have updated since Aug 1 ?
I doesn't works, please remove (with --purge) printer daemon (cups i think) and reinstall it .

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Assigning to cupsys and rejecting xorg task...

Changed in xorg:
status: Unconfirmed → Rejected
Revision history for this message
Ante Karamatić (ivoks) wrote : Re: [Bug 55205] Printing broken by Updates of 2006 Aug 1

On Mon, 07 Aug 2006 11:17:40 -0000
ScottHerman <email address hidden> wrote:

> This machine has no printer connected directly to it, but prints through
> cups using printers on our local network.

Please attach your /etc/cups/cupsd.conf and /etc/cups/cups.d/*.

Revision history for this message
Jan Ekholm (chakie) wrote :

We have two Kubuntu Dapper systems at home that also have printing broken. We print to a Debian CUPS system over our local network and printing worked perfectly fine until som update in early August (can't specify exactly which).

When printing anything at all now we only get three lines of text output that read:

-12345@PJL ENTER LANGUAGE=PCL3GUI
17H1-1M126o0M1-2Hg20WXX XX
u600Dr4812Sr1Ap224Yb0Vb122W

Nothing else is printed. Both systems do the same. Printing from a Mac that also prints to the same system works as it should, so the two Dappers are somehow broken.

Attached is my cupsd.conf

In /etc/cups/cups.d/ there are the files browse.conf and ports.conf, which contain the lines:

browse.conf:
Browsing off

ports.conf:
Listen 127.0.0.1:631

Revision history for this message
Jan Ekholm (chakie) wrote :

As a comment to my above comment, the Debian CUPS server is untouched, no updates have been applied to it for weeks, so some Dapper update has touched something that affects our system.

The printer is a HP PSC 1510 and we also use the "hplip" package for the printing process.

Revision history for this message
Rob Steele (rob-steele) wrote :

CUPS printing was also broken for me by the updates of Aug 1. Previous to this, printing to a Fedora server running CUPS 1.2.2 worked. Now, the Dapper machine prints this to my HP LaserJet 4L:
-12345X@PJL
@PJL SET MANUALFEED=OFF
@PJL SET ECONOMODE=OFF
@PJL SET COPIES=1
@PJL SET RET=MEDIUM
@PJL SET DENSITY=3

Results are similar printing to a HP DeskJet 930c attached to the same Fedora server.

Other machines continue to print correctly to the print server.

I decided to reinstall with the recently-released Dapper 6.06.1. Same results.

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

@Jan & Rob
More information and a workaround for your problem can be found in bug #55828.

Revision history for this message
Edmund Laugasson (ed-lau) wrote :

I have the same problem.

I can't access to CUPS at all. This is critical problem to me :(

Revision history for this message
Maxence DUNNEWIND (maxenced) wrote :

> I can't access to CUPS at all. This is critical problem to me

what cups worte when you try http://localhost:631 ?

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

> I have the same problem.
> I can't access to CUPS at all.

Saying "it doesn't work" is not very descriptive, please provide more information. It would be nice if you could describe what you have already tried to investigate the problem.

Is cups running? Run the following command to find out:
$ ps -A | grep cups
$ /etc/init.d/cupsys status

What does the following command give:
$ lpinfo -v

Please attach your /etc/cups/cupsd.conf and /etc/cups/cups.d/*

Are you able to access the webinterface (http://localhost:631), if not do a ping localhost.

Revision history for this message
Rob Steele (rob-steele) wrote :

> More information and a workaround for your problem can be found in bug #55828

Thanks Pascal! That was a big help. The raw queue works great for me.

I also discovered that if I enable browsing on my Dapper client, I can use the printer that was found by browsing and it also works fine, no problems. The "browsed-to" printer must also use server-side drivers, since I cannot set any driver information on the client this way (it is disabled in the UI).

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

@Rob
Please do not add unrelated information in this bug report. This bug is about CUPS not working at all.
The problem you have is bug #55828, please add further comments about your problem there.
I have added your comment to bug #55828.

Revision history for this message
Edmund Laugasson (ed-lau) wrote :
Download full text (3.7 KiB)

> Saying "it doesn't work" is not very descriptive, please provide more information.

Well, I added the file http://librarian.launchpad.net/3900492/printingbuginfo.txt made with the script available at https://wiki.ubuntu.com/PrintingBugInfoScript

> It would be nice if you could describe what you have already tried to investigate the problem.

I installed KDE 3.5.4 from http://kubuntu.org/packages/kde-354/ and did not afraid any problem due to its stable state. It promised eliminate a lot of problems, including several CUPS problems - at http://kubuntuforums.net/ we may read:

* Updated cupsys to upstream bugfix release 1.2.2, fixing many bugs
  (including #42513, #42802, #44931, #47387, #48116, #51432, and part
  of #42802).

This Kubuntu 6.06.1 include KDE 3.5.4 and CUPS 1.2.2, I suppose.

I did not mention the CUPS problem until I needed to install network printer. Then I could not access over web interface even CUPS is working. I made restart using usual command

sudo /etc/init.d/cupsys restart

... and it started normally. I included my error_log also and it shows no errors. I changed log level to debug in CUPS config file to get more output into this log file but it did not give errors.

I use the kernel 2.6.15-23-386, because 2.6.15-26-386 seems to be buggy, because sound server ALSA crashed and whatever I tried to play (Amarok, Kaffeine, XMMS, MPlayer) looped endlessly and only killing the program stopped it. I don't know, is it KDE 3.5.4 and 2.6.15-26-386 (26.46) incompatibility issue or is this new kernel really so buggy. Anyway - I use the original kernel, what came from Kubuntu 6.06 LTS Alternative installation CD.

> Is cups running? Run the following command to find out:
> $ ps -A | grep cups

4030 ? 00:00:00 cupsd

> $ /etc/init.d/cupsys status

Status of Common Unix Printing System: cupsd is running.

Well, it seems like running. This is the most strange thing - everything seems to be fine but no access to CUPS daemon...

>What does the following command give:
> $ lpinfo -v

Nothing - it just start waiting something and no output. I should use CTRL+C to cancel it.

> Please attach your /etc/cups/cupsd.conf and /etc/cups/cups.d/*

 Please see attached cups_config_files.tar.gz file.

> Are you able to access the webinterface (http://localhost:631)

No, I'm not able to access.

> if not do a ping localhost.

I read this problem and my localhost exist:
$ ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.092 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.085 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.084 ms

--- localhost ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.084/0.087/0.092/0.003 ms

> More information and a workaround for your problem can be found in bug #55828

Unfortunately I were not able to change any format to raw due to no access of CUPS

Another thing - I made Kubuntu 6.06 Alternate install onto another machine and there I did not install KDE 3.5.4 and left this KDE, what it updated - KDE 3.5.2. And result is, that I can access to ...

Read more...

Revision history for this message
Edmund Laugasson (ed-lau) wrote :

I also tried to run command:

kcmshell printers

as root and as regular user and both times I received error message, which is in Estonian language as you may see in attached *.png picture. This error message in this picture says (free translation made by me):

Its impossible to get list of printers. Manager error message is:
Connection to CUPS server failed. Check that CUPS server is correctly installed and started. Error: Connection to CUPS server failed. Check that CUPS server is correctly installed and started.

Revision history for this message
Edmund Laugasson (ed-lau) wrote :

When I run kcmshell printers at command prompt, it gave me a lot of output. I saved it into file and now I post it also here.

Revision history for this message
Edmund Laugasson (ed-lau) wrote :

I also would like to say, that in this laptop, where all this KDE 3.5.4 and CUPS 1.2.2 rendez-vous happens - there I have no printers installed.

So I keep in some time this KDE 3.5.4 to see this bug solve process. If it will not be solved during one week, I problably will install clean Kubuntu again with official KDE 3.5.2 to get my printers work. I have at work network printer (HP LJ 6P with TrendNet printserver) and also I plan buy to home printserver, because this laptop (Fujitsu-Siemens Amilo L7300G2) does not have parallel port (LPT) and therefore I need to use printserver to be able to print at all.
Reason is simple - I need to work and schoolyear begins and I work at school.
But thanks in advance for all of help! I hope in one beautiful day it will be solved.
But this case teached me one thing - don't think, that new stable version of KDE will work - there may be bugs, that you don't even expect and these bugs may be critical for you (like current is)...

Revision history for this message
Edmund Laugasson (ed-lau) wrote :

Sorry, I forgot to add my CUPS error log. Here it is.

Revision history for this message
Edmund Laugasson (ed-lau) wrote :

I also had in /etc/environments the following row (added myself to accelerate Konqueror web browsing):

KDE_NO_IPV6=1

I commented it out, made restart to CUPS and even to PC but it did not help - CUPS still not accessible...

I also have in Firefox some tweaks (http://easylinux.info/wiki/Ubuntu_dapper#How_to_load_Web_site_faster_in_Mozilla_Firefox) to get better perfomance but also these tweaks were not the reason, why I cannot access over web.
Certainly I added user cupsys to group shadow:
sudo adduser cupsys shadow

... and also checked, that regular user were already in group lpadmin. So I should have everything ready to access CUPS over web interface.

I also tried to install old CUPS 1.20 by using command:

sudo apt-get install cupsys=1.2.0-0ubuntu5 cupsys-client=1.2.0-0ubuntu5 cupsys-bsd=1.2.0-0ubuntu5

... but it did not help. Certainly, I removed CUPS and all other components before I installed old ones.

As you probably mention - I read launchpad and searched Google before I reported this bug.

I also tried to reconfigure it:
sudo dpkg-reconfigure cupsys

I choosed instead of:
localhost:631 /var/run/cups/cups.sock
... and put there only:
localhost:631

It did not help...

So, I gave up and reported my bug...

Revision history for this message
Edmund Laugasson (ed-lau) wrote :

It seems like it's not actually CUPS problem but just KDE 3.5.4, which is not able to communicate with CUPS 1.2.2

This is my humble opinion :)

But how to trace the reason of this bug - I don't unfortunately know... If somebody does - please let me know. Perhaps I can so help to resolve this bug...

Revision history for this message
Edmund Laugasson (ed-lau) wrote :

I installed at 16th of August 2006 to another (desktop) PC also Kubuntu 6.06 LTS and there I installed at first network printer in the beginning. I did not make any updates before - just clean Kubuntu. Then I enabled universe, multiverse repositories and made dist-upgrade as always. After restart I still could access to the CUPS. Then I enabled also KDE 3.5.4 repository and also KOffice and Amarok repositories from kubuntu.org/packages, made again dist-upgrade and after restart I still could access to CUPS! Amazing! I could also print to this network printer (HP LaserJet 6P with TrendNet printserver using ipp protocol and 9100 port as always).

But KDE started already at version 3.5.2 to announce me, that it could not create mcop folder (artsmessage). It's quite boring to see at each login this error message...
I checked at ~/.mcop and everything seemed to fine. Also sound worked. Even with 2.6.15-26-386 (26.46) kernel! I just don't understand...

Revision history for this message
Edmund Laugasson (ed-lau) wrote :

.... but this laptop.... There I still cannot access to CUPS :( It seems like I have to reinstall it. It seems like no solution is not yet known for this CUPS problem.

What could be different with this two situation... At laptop I made after install available KDE 3.5.4 repositories and after that I made first update and dist-upgrade. I did not update and dist-upgrade before.

Revision history for this message
Vassilis Pandis (pandisv) wrote :

many people have confirmed this, setting status to confirmed

Changed in cupsys:
importance: Untriaged → High
status: Unconfirmed → Confirmed
Revision history for this message
Ante Karamatić (ivoks) wrote :

@Edmund
Do you have some kind of firewall?

@Scott
Any changes?

@Vassilis
Actually, only one person confirmed this bug :)

Revision history for this message
Ante Karamatić (ivoks) wrote :

Reducing to medium.

Changed in cupsys:
importance: High → Medium
Revision history for this message
ScottHerman (scott-herman) wrote : Re: [Bug 55205] Re: Printing broken by Updates of 2006 Aug 1

Since I needed printing, as this was my office machine, I backed up all my data, reloaded the OS from the ubuntu CD. I then applied all of the updates to bring it up to date and printing works now.

Ante Karamatić <email address hidden> wrote: @Edmund
Do you have some kind of firewall?

@Scott
Any changes?

@Vassilis
Actually, only one person confirmed this bug :)

--
Printing broken by Updates of 2006 Aug 1
https://launchpad.net/bugs/55205

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Sorry, you're right - I'll try to be more careful next time. Thanks for reverting my changes.

Revision history for this message
Edmund Laugasson (ed-lau) wrote :

I don't have any firewall.

Revision history for this message
Ante Karamatić (ivoks) wrote :

First of all, you can downgrade KDE to the official one, but we'll see if KDE is the problem.

What's the output of 'telnet localhost 631' and 'sudo netstat -atp | grep cupsd'?

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 alpha?

Changed in cupsys:
status: Confirmed → Incomplete
Revision history for this message
Javier Jardón (jjardon) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in cupsys:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.