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 100521 - Gimp-1.2.4 will not print
Gimp-1.2.4 will not print
Status: RESOLVED INVALID
Product: GIMP
Classification: Other
Component: Plugins
1.x
Other Windows
: Normal normal
: 1.2
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2002-12-06 15:20 UTC by Warren Norwood
Modified: 2003-11-25 18:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Warren Norwood 2002-12-06 15:20:44 UTC 
Choosing Print draws no response from GIMP except the hourglass for a few 
seconds.  No print dialog appears.  Thhe printer is not active.

I uninstalled and reinstalled GIMP successfully using gimp-1.2.4-
20020907setup.exe, but got the same results.
Comment 1 Raphaël Quinet 2002-12-06 15:41:57 UTC 
Thanks for creating a new bug report for this (this was previously
reported in bug #96916).  I hope that some Windows NT 4.0 users will
be able to confirm this bug and find a solution...
Comment 2 Wade Hampton 2003-03-21 18:07:21 UTC 
On Windows 98 release 1, GIMP 1.2.4 printed fine the first day I used
it.  The next day
(when my son's report was due), I could not print and I kept getting
errors about too many
dialogs open.  Solution:  save to png and then import into OpenOffice
Draw.
-- daswadester@netscape.net
Comment 3 Tor Lillqvist 2003-03-22 17:17:54 UTC 
As I never seem to have time or motivation to improve the winprint 
plug-in, and nobody else seems to volunteer, dare I suggest dropping 
the winprint plug-in from GIMP altogether?
Comment 4 Dave Neary 2003-07-23 16:28:04 UTC 
Assigning 1.2 bugs to milestone 1.2.6.

Dave.
Comment 5 Warren Norwood 2003-07-23 20:24:31 UTC 
Works for me.  I'm restricted from using GIMP at work anymore, and it 
works just fine at home on 98/ME/Linux, so the issue is dead as far 
as I'm concerned.
--Warren
Comment 6 Sven Neumann 2003-11-25 18:09:56 UTC 
Since the bug doesn't seem to be reproducable and the bug reporter
indicated that it isn't a problem for him any longer, I am closing it
as invalid.