Is printing supposed to be working in rev.16673, or is it a known work-in-progress?
It simply sends the CPU to 100% until inkscape is killed from the command line on my Linux machine; closing Inkscape using the normal Quit menu item is not enough.
Thomas
I had the same problem in WinXP. I installed a newer version of SVN and it now prints but it is nothing like the screen image, it is all over the place. I compiled and installed 16705 and there is no difference. I then noticed the render tab on the print dialog. Set to Cairo, the effects are as above but set to bitmap I get a good print - just drastically smaller so I have to mess with the dpi setting.
Hope this helps,
Tony
Thomas Worthington-3 wrote:
Is printing supposed to be working in rev.16673, or is it a known work-in-progress?
It simply sends the CPU to 100% until inkscape is killed from the command line on my Linux machine; closing Inkscape using the normal Quit menu item is not enough.
Thomas
SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Fri, 14 Dec 2007 15:17:54 -0000, Docsonic <docsonic@...58...> wrote:
I had the same problem in WinXP. I installed a newer version of SVN and it now prints but it is nothing like the screen image, it is all over the place. I compiled and installed 16705 and there is no difference. I then noticed the render tab on the print dialog. Set to Cairo, the effects are as above but set to bitmap I get a good print - just drastically smaller so I have to mess with the dpi setting.
Hope this helps,
It helps in the sense that misery loves company :) But printing to 300dpi A3 via bitmap gives my computer a headache, so hopefully it'll be sorted soon or I'll have to stop using the SVN version.
Thomas
Ouch. I use an earlier version just for printing now as printing is critical to my Inkscape use - I use it mainly to design and create decals! This is easy in Windows but I don't know if it works in Linux to have 2 versions side-by-side.
Thanks,
Tony
Thomas Worthington-3 wrote:
On Fri, 14 Dec 2007 15:17:54 -0000, Docsonic <docsonic@...58...> wrote:
I had the same problem in WinXP. I installed a newer version of SVN and it now prints but it is nothing like the screen image, it is all over the place. I compiled and installed 16705 and there is no difference. I then noticed the render tab on the print dialog. Set to Cairo, the effects are as above but set to bitmap I get a good print - just drastically smaller so I have to mess with the dpi setting.
Hope this helps,
It helps in the sense that misery loves company :) But printing to 300dpi A3 via bitmap gives my computer a headache, so hopefully it'll be sorted soon or I'll have to stop using the SVN version.
Thomas
SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Fri, 2007-12-14 at 16:24 +0000, Thomas Worthington wrote:
It helps in the sense that misery loves company :) But printing to 300dpi A3 via bitmap gives my computer a headache, so hopefully it'll be sorted soon or I'll have to stop using the SVN version.
Do you have the "Cairo PDF" and "Cairo PS" as save formats in your build? If so, do they do the same thing?
--Ted
On Fri, 14 Dec 2007 17:18:20 -0000, Ted Gould <ted@...11...> wrote:
On Fri, 2007-12-14 at 16:24 +0000, Thomas Worthington wrote:
It helps in the sense that misery loves company :) But printing to 300dpi A3 via bitmap gives my computer a headache, so hopefully it'll be sorted soon or I'll have to stop using the SVN version.
Do you have the "Cairo PDF" and "Cairo PS" as save formats in your build? If so, do they do the same thing?
I have both; both work, printing goes into some sort of infinate loop which survives closing Inkscape.
TW
On Fri, 2007-12-14 at 18:28 +0000, Thomas Worthington wrote:
On Fri, 14 Dec 2007 17:18:20 -0000, Ted Gould <ted@...11...> wrote:
On Fri, 2007-12-14 at 16:24 +0000, Thomas Worthington wrote:
It helps in the sense that misery loves company :) But printing to 300dpi A3 via bitmap gives my computer a headache, so hopefully it'll be sorted soon or I'll have to stop using the SVN version.
Do you have the "Cairo PDF" and "Cairo PS" as save formats in your build? If so, do they do the same thing?
I have both; both work, printing goes into some sort of infinate loop which survives closing Inkscape.
Hmm, that's odd. They both generate the Cairo canvas the same way, so this must be something in the actual printer output.
Kees, are there any other processing loops in dealing with the printer?
--Ted
-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of Diederik van Lierop Sent: zaterdag 22 december 2007 20:01
BTW, what happened to the windows debugging symbols? Apparently they're not included in the nightly builds, or did I overlook them?
Just tested, they are definitely there. You have to load them in gdb. gdb
file inkscape.exe inkscape.dbg
Cheers, Johan
-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of J.B.C.Engelen@...1578... Sent: zaterdag 22 december 2007 20:16 To: mail@...1689...; inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] Printing
-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of Diederik van Lierop Sent: zaterdag 22 december 2007 20:01
BTW, what happened to the windows debugging symbols? Apparently they're not included in the nightly builds, or did I overlook them?
Just tested, they are definitely there.
Sorry, I was too quick. Indeed I cannot find them in the packages from inkscape.modevia.com.
- Johan
Kees is on vacation for a while, but I asked them about this yesterday. He does not have a Windows system so cannot address the issue himself, but would welcome patches from those with access to Windows.
Bryce
On Sat, Dec 22, 2007 at 08:01:10PM +0100, Diederik van Lierop wrote:
Hi guys,
There are some serious issues with printing on windows: Inkscape dies immediately :-(
[1]https://bugs.launchpad.net/inkscape/+bug/176018I do hope that Kees will find some time to look into this soon, because this will be a blocker! Could someone please bump the importance of this bug to high (I don't have sufficient rights for that)
BTW, what happened to the windows debugging symbols? Apparently they're not included in the nightly builds, or did I overlook them?
Diederik
Ted Gould wrote:
On Fri, 2007-12-14 at 18:28 +0000, Thomas Worthington wrote:
On Fri, 14 Dec 2007 17:18:20 -0000, Ted Gould [2]<ted@...11...> wrote:
On Fri, 2007-12-14 at 16:24 +0000, Thomas Worthington wrote:
It helps in the sense that misery loves company :) But printing to 300dpi A3 via bitmap gives my computer a headache, so hopefully it'll be sorted soon or I'll have to stop using the SVN version.
Do you have the "Cairo PDF" and "Cairo PS" as save formats in your build? If so, do they do the same thing?
I have both; both work, printing goes into some sort of infinate loop which survives closing Inkscape.
Hmm, that's odd. They both generate the Cairo canvas the same way, so this must be something in the actual printer output.
Kees, are there any other processing loops in dealing with the printer?
--Ted ------------------------------------------------------------------References
Visible links
- https://bugs.launchpad.net/inkscape/+bug/176018
- mailto:ted@...11...
Hi,
On Wed, Dec 12, 2007 at 11:08:25AM -0000, Thomas Worthington wrote:
Is printing supposed to be working in rev.16673, or is it a known work-in-progress?
It simply sends the CPU to 100% until inkscape is killed from the command line on my Linux machine; closing Inkscape using the normal Quit menu item is not enough.
This appears to be a gtk bug: http://bugzilla.gnome.org/show_bug.cgi?id=482089
I think the best course of action is to require gtkmm 2.12.1. (It was fixed there.) I don't see a way to require "2.10.0 or higher, but not 2.12.0 exactly".
-Kees
On Dec 29, 2007 8:47 AM, Kees Cook <kees@...62...> wrote:
I think the best course of action is to require gtkmm 2.12.1. (It was fixed there.) I don't see a way to require "2.10.0 or higher, but not 2.12.0 exactly".
Thanks! I confirm that with gtk 2.12.3 (not gtkmm - I have gtkmm 2.10.10 and that I didn't upgrade) printing works again on Linux.
So, now we need to:
- change the configure scripts
- add a note to Release Notes
- build a new lib bundle for windows with latest gtk (also needed for another bugfix, as I reported recently)
Thanks!
On Sat, Dec 29, 2007 at 09:03:22PM -0400, bulia byak wrote:
On Dec 29, 2007 8:47 AM, Kees Cook <kees@...62...> wrote:
I think the best course of action is to require gtkmm 2.12.1. (It was fixed there.) I don't see a way to require "2.10.0 or higher, but not 2.12.0 exactly".
Thanks! I confirm that with gtk 2.12.3 (not gtkmm - I have gtkmm 2.10.10 and that I didn't upgrade) printing works again on Linux.
So, now we need to:
- change the configure scripts
I posted a patch to fix the configure script for this at https://bugs.launchpad.net/inkscape/+bug/176018 however, Kees says he's working on a hack that will solve the problem without requiring hardcoding the gtk version.
Bryce
Bryce Harrington wrote:
On Sat, Dec 29, 2007 at 09:03:22PM -0400, bulia byak wrote:
On Dec 29, 2007 8:47 AM, Kees Cook <kees@...62...> wrote:
I think the best course of action is to require gtkmm 2.12.1. (It was fixed there.) I don't see a way to require "2.10.0 or higher, but not 2.12.0 exactly".
Thanks! I confirm that with gtk 2.12.3 (not gtkmm - I have gtkmm 2.10.10 and that I didn't upgrade) printing works again on Linux.
So, now we need to:
- change the configure scripts
I posted a patch to fix the configure script for this at https://bugs.launchpad.net/inkscape/+bug/176018 however, Kees says he's working on a hack that will solve the problem without requiring hardcoding the gtk version.
Did we just agree to require GTK 2.12.1 or greater? What does this mean for GLIB versions? I've got a bug laying around for which the easy fix involves requiring GLIB 2.11.4.
http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/exten...
Aaron Spike
On Sun, Dec 30, 2007 at 06:44:43AM -0600, Aaron Spike wrote:
Bryce Harrington wrote:
On Sat, Dec 29, 2007 at 09:03:22PM -0400, bulia byak wrote:
On Dec 29, 2007 8:47 AM, Kees Cook <kees@...62...> wrote:
I think the best course of action is to require gtkmm 2.12.1. (It was fixed there.) I don't see a way to require "2.10.0 or higher, but not 2.12.0 exactly".
Thanks! I confirm that with gtk 2.12.3 (not gtkmm - I have gtkmm 2.10.10 and that I didn't upgrade) printing works again on Linux.
So, now we need to:
- change the configure scripts
I posted a patch to fix the configure script for this at https://bugs.launchpad.net/inkscape/+bug/176018 however, Kees says he's working on a hack that will solve the problem without requiring hardcoding the gtk version.
Did we just agree to require GTK 2.12.1 or greater? What does this mean for GLIB versions? I've got a bug laying around for which the easy fix involves requiring GLIB 2.11.4.
Nope. The above patch would allow any version of GTK except exactly 2.12.0. So 2.10.* would still work. However, Kees committed a patch that gets around the issue entirely (but we'll want to revisit it when we increase the requirements to 2.12.2+)
Tell me more about the seriousness of the bug you're looking at. What's the bug ID for it?
http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/exten...
Aaron Spike
Bryce
On Dec 30, 2007 4:03 AM, bulia byak wrote:
So, now we need to:
change the configure scripts
add a note to Release Notes
build a new lib bundle for windows with latest gtk (also needed for
another bugfix, as I reported recently)
Could somebody please also change alignment of printing options? It's right aligned now, whereas left aligned would be preferable.
Alexandre
On Sun, 30 Dec 2007 01:03:22 -0000, bulia byak <buliabyak@...400...> wrote:
On Dec 29, 2007 8:47 AM, Kees Cook <kees@...62...> wrote:
I think the best course of action is to require gtkmm 2.12.1. (It was fixed there.) I don't see a way to require "2.10.0 or higher, but not 2.12.0 exactly".
Thanks! I confirm that with gtk 2.12.3 (not gtkmm - I have gtkmm 2.10.10 and that I didn't upgrade) printing works again on Linux.
Hold on!
I now have gtk 2.12.2-r2, gtkmm 2.12.1, cairo 1.4.12 and Inkscape rev.16862 on Gentoo Linux.
When I try to print the document at
http://www.tww.cx/downloads/boxtest.svg
(basically a rectangle on an A4 page) the output is the postscript file at
http://www.tww.cx/downloads/boxtest.ps
This does not seem to set the bounding box quite right (or at least, it does not identify the page size as "A4") and includes an extra blank page and in fact produces no output of any sort apart from two blank pages on my printers. Ghostscript also does not produce any output other than
GPL Ghostscript 8.60 (2007-08-01) Copyright (C) 2007 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. %%BoundingBox: 83 232 417 710 %%HiResBoundingBox: 83.588622 232.160055 416.982854 709.554283
showpage, press <return> to continue<<
%%BoundingBox: 0 0 0 0 %%HiResBoundingBox: 0.000000 0.000000 0.000000 0.000000
showpage, press <return> to continue<<
Ghostview does display it, albeit in a custom bounding box rather than an A4 one.
Both printers are happily printing other Postscript output as we speak.
Any ideas?
Thomas
On Mon, Dec 31, 2007 at 12:23:42AM -0000, Thomas Worthington wrote:
On Sun, 30 Dec 2007 01:03:22 -0000, bulia byak <buliabyak@...400...> wrote:
On Dec 29, 2007 8:47 AM, Kees Cook <kees@...62...> wrote:
I think the best course of action is to require gtkmm 2.12.1. (It was fixed there.) I don't see a way to require "2.10.0 or higher, but not 2.12.0 exactly".
Thanks! I confirm that with gtk 2.12.3 (not gtkmm - I have gtkmm 2.10.10 and that I didn't upgrade) printing works again on Linux.
Hold on!
Your issue appears unrelated to the one under discussion - please file a new bug about it.
Bryce
I now have gtk 2.12.2-r2, gtkmm 2.12.1, cairo 1.4.12 and Inkscape rev.16862 on Gentoo Linux.
When I try to print the document at
http://www.tww.cx/downloads/boxtest.svg
(basically a rectangle on an A4 page) the output is the postscript file at
http://www.tww.cx/downloads/boxtest.ps
This does not seem to set the bounding box quite right (or at least, it does not identify the page size as "A4") and includes an extra blank page and in fact produces no output of any sort apart from two blank pages on my printers. Ghostscript also does not produce any output other than
GPL Ghostscript 8.60 (2007-08-01) Copyright (C) 2007 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. %%BoundingBox: 83 232 417 710 %%HiResBoundingBox: 83.588622 232.160055 416.982854 709.554283
showpage, press <return> to continue<<
%%BoundingBox: 0 0 0 0 %%HiResBoundingBox: 0.000000 0.000000 0.000000 0.000000
showpage, press <return> to continue<<
Ghostview does display it, albeit in a custom bounding box rather than an A4 one.
Both printers are happily printing other Postscript output as we speak.
Any ideas?
Thomas
participants (10)
-
unknown＠example.com -
Aaron Spike -
Alexandre Prokoudine -
Bryce Harrington -
bulia byak -
Diederik van Lierop -
Docsonic -
Kees Cook -
Ted Gould -
Thomas Worthington