After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 401138 - printed page has text upside down and almost out of cell
printed page has text upside down and almost out of cell
Status: RESOLVED DUPLICATE of bug 301779
Product: Gnumeric
Classification: Applications
Component: Printing
1.6.x
Other All
: Normal normal
: ---
Assigned To: Andreas J. Guelzow
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2007-01-26 21:11 UTC by Marc Miller
Modified: 2007-01-27 16:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Marc Miller 2007-01-26 21:11:30 UTC 
Please describe the problem:
I just started using gnumeric today, and copied sample pages from ms excel and ms works.

All looks good on screen and functions work good as far as I can tell so far.

When attempting to print a sample page to my HP deskjet 3650, the text in the cells looks like it is upside down and almost out of the cell.  I can only get the very bottom of the data to print in the cell, and it appears to be upside down.

The 'print preview' screen looks correct.

Hope you can help!  Thanks!
Marc Miller
mwmiller@tctwest.net

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?
Yes, it happens every time.  I tried it on two different sample pages from two different workbooks.

Other information:
Comment 1 Andreas J. Guelzow 2007-01-27 16:30:08 UTC 
I am sure that this is a duplicate bug report but I can't find the original. If I recall correctly, This was a printer-specific issue related to one HP printer )possibly the same model you are using.) If you print to an pdf file and then have a look at the pdf file, does it look right. What if you then send the pdf file to the printer?
Comment 2 Andreas J. Guelzow 2007-01-27 16:37:43 UTC 

*** This bug has been marked as a duplicate of 301779 ***