Ubuntu
gutenprint package

Epson Stylus Photo R380 doesn't eject after printing

Bug #125977 reported by marcw
2
Affects Status Importance Assigned to Milestone
gutenprint (Ubuntu)
Fix Released
Undecided
Pascal De Vuyst

Bug Description

Using the new Gutsy gutenprint 5.0.1 source, diff, and dsc I created a new deb for my Feisty installation because I noticed that it included a driver for my new Epson Stylus Photo R380 where the stock Feisty gutenprint doesn't.

The build and installation went fine with no errors or unmet dependencies. The included drivers work fine for my other 2 printers. Indeed, it even works fine for my new R380 except that it doesn't eject the printed material after finishing the job. This just happens on the R380. It doesn't matter if the job was a printed page, a photo, or even a DVD, it simply doesn't eject it. The workaround is to power off the printer which then does eject the job.

One odd thing I noticed is that if I perform a test print from within the CUPS admin page (http://localhost:631) the page *does* eject normally. But that's the only time it performs as it should. At all other times - including from within both gimp and the gnome-cups-manager - it does not eject the completed job.

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

Do you have the same problem with Ubuntu Gutsy?
Can you try with the tribe 2 live CD (http://cdimage.ubuntu.com/releases/gutsy/tribe-2/).

Changed in gutenprint:
assignee: nobody → pascal-devuyst
status: New → Incomplete
Revision history for this message
marcw (marcw) wrote :

I didn't get a chance to look at this until today and since I received a notice that Tribe3 was released, I used that one instead of Tribe2.

First off, Booting the LiveCD gives me a warning:
Internal Error
failed to initialize HAL

Not sure if this error is to be expected or not.

The gnome-cups-manager recognized my USB attached R380 without any problems and I was able to successfully install my R380. Unfortunately, I was not able to print. Performing a test print e.g. resulted in the printer queue window seeing the job but it was in a stopped state. No amount of coaxing could un-stop it. So I can't really say if Tribe3 fixes things or not.

Revision history for this message
marcw (marcw) wrote :

Once I got past the app armor bug that makes printing not work in the Tribe5 LiveCD, this bug seems to not exist. Everything I tried printing on my R380 from Tribe5 seemed to print fine with none of the eject problems I reported. I suppose I'll just have to live with this bug in Feisty even though I'm using the same Gutenprint as the one in Tribe5.

Till Kamppeter (till-kamppeter)
Changed in gutenprint:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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