Ubuntu
mozilla-firefox package

Cannot print from eVince when started in Firefox

Asked by Danny Staple

On Dapper 6.06 LTS, In Firefox 1.5.0.7, when I follow a PDF link, which therefore starts eVince, trying to print leads to eVince hanging.

This is 100% reproducable. It may or may not be a bug. I have to kill off eVince by closing the window, and waiting for the "force quit" dialog, or with a kill -9 from the command line.

I can save the file to my filesystem, open it there, and print fine.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu mozilla-firefox Edit question
Assignee:
No assignee Edit question
Solved by:
Luca Falavigna
Solved:
Last query:
Last reply:
Revision history for this message
Luca Falavigna (dktrkranz) said : 		#1

If you can reproduce it, you may want to file a new bug.

Revision history for this message
Óscar Rodríguez Ríos (ingorr01) said : 		#2

Do you have an configured printer? If not could be the problem.

Revision history for this message
Danny Staple (danny-orionrobots) said : 		#3

I definately have a configured printer.

As I stated, I can print fine from eVince when it is not started in firefox, eg by saving a PDF file to my desktop, double clicking it, and then clicking print, where I am taken to a print dialog, and can print.

When starting form firefox, eVince hangs when I click file->print, but before I see the print dialog. eVince is also fine when started from the command line.

I wander if it has something to do with the environment that Firefox passes to eVince when starting it. Has anyone got any bright ideas for debugging that?

It would maybe evolve doing an env dump in a script right before running eVince and tieing its standard out and standard error to a log file. Now writing such a script is trivial, but how to get firefox to run that instead?

Revision history for this message
Danny Staple (danny-orionrobots) said : 		#4

Luca, I suspected it would lead to a bug report, but jsut wanted to try here to see if I had missed soemthing obvious. The bug has been files as Bug #62934.

Revision history for this message
Luca Falavigna (dktrkranz) said : 		#5

I linked your bug to this ticket, which you may consider to close.

Revision history for this message
Danny Staple (danny-orionrobots) said : 		#6

Okay. Closing.