HP Laserjet 3380 via samba: Test page OK, printing from applications hangs printer

[vicent]

Binary package hint: openoffice.org

openoffice and other aplications can't print on a HP Laserjet 3380 via samba (the printer crashes). Maybe is a cups problem?

I print from a Ubuntu 9.04 to the printer via samba (in a Windows XP box). No problem in 8.04/8.10. The document arrives to the printer, cause I see in the display the printing message, but the printer hangs and I need to reset it. No problem when printing a test page from printer's properties.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: openoffice.org-core 1:3.0.1-9ubuntu3
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: openoffice.org
Uname: Linux 2.6.28-11-generic i686

[Scott Howard (showard314)]

Thanks for reporting and helping make Ubuntu better. We'll need a little more information to work on this.

Please run:

"apport-collect 368504" from a terminal

And follow the steps at:
https://wiki.ubuntu.com/DebuggingPrintingProblems#CUPS%20error_log

to produce and post an error log.

I'm also adding the samba package association.

[vicent (vicente-hackett-pc)]

I have a problem, I set the level security of launchpad to "read non-personal data only", but apport-collect need "change anything" level. I tried to change it, but now I have this error message:

Logging into Launchpad...
Traceback (most recent call last):
  File "/usr/bin/apport-collect", line 131, in <module>
    lp = login()
  File "/usr/bin/apport-collect", line 48, in login
    launchpad = Launchpad(credentials, launchpad_instance, cache_dir)
  File "/usr/lib/python2.6/dist-packages/launchpadlib/launchpad.py", line 60, in __init__
    self._wadl = self._browser.get_wadl_application(self._root_uri)
  File "/usr/lib/python2.6/dist-packages/launchpadlib/_browser.py", line 230, in get_wadl_application
    url, media_type='application/vd.sun.wadl+xml')
  File "/usr/lib/python2.6/dist-packages/launchpadlib/_browser.py", line 212, in _request
    raise HTTPError(response, content)
launchpadlib.errors.HTTPError: HTTP Error 401: Unauthorized

How to continue?

[vicent (vicente-hackett-pc)]

this is the cups error_log

[Thierry Carrez (ttx)]

If something arrives to the printer then samba probably did its part... Please reopen the samba task if you can point to an issue in samba.

[Scott Howard (showard314)]

Thanks for the error log.

Please check out:
http://ubuntuforums.org/showthread.php?t=987189

Unfortunately, I don't believe you have the same problem.
Marking as Confirmed, to be looked at by the developers.

[Till Kamppeter (till-kamppeter)]

It is not yet clear whether the problem is caused by Samba or if it is somewhere in the filter chain. The error_log does not show any problems with the smb CUPS backend (the Samba client), but there are some warnings coming from the filters.

To give me the possibility to be able to reproduce the bug, please do the following:

Disable the print queue by entering

cupsdisable HP-LaserJet-3380

Clear the queue from stuck jobs with

cancel -a

and then send a job from an application with which your printer crashed.

Now the job will wait in the disabled queue. Copy the job data file:

sudo cp /var/spool/cups/d* ~/jobdata
chmod 777 ~/jobdata

Re-enable the print queue with

cupsenable HP-LaserJet-3380

Check whether your printer really crashes. If the job gets printed normally, repeat the previous steps with another file/application, so that you get a job captured which causes the problem.

Attach the file ~/jobdata to this bug report. Tell which file you have printed with which application. Attach also the file.

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
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".