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 469635 - Menu File, Print, crash the print.exe plugin
Menu File, Print, crash the print.exe plugin
Status: RESOLVED DUPLICATE of bug 467643
Product: GIMP
Classification: Other
Component: Plugins
2.4.x
Other All
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2007-08-23 16:00 UTC by Valerio Messina
Modified: 2008-10-30 19:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Valerio Messina 2007-08-23 16:00:12 UTC
Please describe the problem:
Open an image, choose menu File, then Print ..., I got:
GNU Image Manipulation Program: print.exe - Errore di applicazione
L'istruzione a "0x605a536a" ha fatto riferimento alla memoria a "0x0000000c". La memoria non poteva essere "read".
Fare click su OK per terminare l'applicazione.

that is:

GNU Image Manipulation Program: print.exe - Application error
Istruction at "0x605a536a" try to reference memory at "0x0000000c". Memory cannot be "read".
Click OK to terminate the application.



Steps to reproduce:
1. Open an image
2. choose menu File
3. Print ...


Actual results:
I got the error:
GNU Image Manipulation Program: print.exe - Application error
Istruction at "0x605a536a" try to reference memory at "0x0000000c". Memory cannot be "read".
Click OK to terminate the application.

Expected results:
The Print Dialog Box shold open

Does this happen every time?
yes

Other information:
I tried only Win32 precompiled RC1 downloaded at:
http://sourceforge.net/project/showfiles.php?group_id=121075&package_id=240554&release_id=532945
Comment 1 Michael Schumacher 2007-08-23 17:31:19 UTC

*** This bug has been marked as a duplicate of 468407 ***
Comment 2 Michael Natterer 2007-08-23 18:39:40 UTC
Fixing duplicate.

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