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 692882 - GIMP crashes on Windows XP SP3 ( with all Windows Updates applied )
GIMP crashes on Windows XP SP3 ( with all Windows Updates applied )
Status: RESOLVED INCOMPLETE
Product: GIMP
Classification: Other
Component: General
2.8.2
Other Windows
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-01-30 15:40 UTC by enz-coast
Modified: 2013-07-05 08:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
This Screenshot shows the Error Message we receive on all Windows XP SP3 Clients... (50.64 KB, image/jpeg)
2013-01-30 15:40 UTC, enz-coast
Details

Description enz-coast 2013-01-30 15:40:56 UTC
Created attachment 234832 [details]
This Screenshot shows the Error Message we receive on all Windows XP SP3 Clients...

We are deploying GIMP 2.8.2 to about 140 Computers as the default Software for Image Manipulation. About 60 of our computers are running Windows 7 Professional 64BIT - No problem on this computers... The rest of the machines is running Windows XP Professional 32BIT. This Computers install GIMP and the GIMP Help proper, but when you open GIMP it fails after the startup screens and quits with an error message ( included in the screenshot i attached to my report ).

All machines are part of an Windows 2008 R2 Active Directory and are fully up to date including all Windowsupdates available until today.

We are not running any special Software on the XP machines, so the software combination is exactly the same in XP and 7. There are no active Group Policies or Firewall Policies and there is no Virus Protection that could interfer with GIMP...
Comment 1 enz-coast 2013-01-30 15:47:41 UTC
Oh I forgot - for the deployment we use WPKG and the scripts to deploy GIMP silently offered at wpkg.org ( http://wpkg.org/Gimp )

But as I mentioned before - the installation process runs completely smooth on both operating systems and finishes without any error.
Comment 2 Michael Schumacher 2013-01-30 18:00:21 UTC
Does the same happen when you install GIMP 2.8.2 manually on one of the affected systems?

Without any additional clues so far, let me make this one guess: maybe the 16bit display color depth problem...?
Comment 3 enz-coast 2013-02-04 15:51:02 UTC
My systems are based on different hardware Platforms ( Dell, Fujitsu, HP, IBM, ACER ), all of them are using 32BIT color depth and are using NVIDIA Forceware or ATI Catalyst drivers ( The drivers are deployed also via WPKG ) and they are always updated to the latest drivers available. NO BETA DRIVERS are used.

The error does also appear when I install the program using the normal installation/setup process without any kind of deployment. The error also appears when I use the same command line that my WPKG packaged uses by hand, so I am pretty sure it has nothing to do with the "kind" of deployment / installation.

I also tried to start GIMP with normal user accounts, administrator accounts and guest user account - no difference. Even the domain administrator doesn´t change a thing.

At first I thought it could be an issue with some of the Windowsupdates my clients are downloading from our WSUS Server, so i tried the GIMP deployment on a "vanilla" Windows XP SP3 Pro Machine - But the error is still there - so the patchlevel of Windows XP is not or not directly related to the error I am experiencing.

THX in advance
Comment 4 enz-coast 2013-02-04 15:55:24 UTC
The machines do all have a screen resolution of at least 1280x1024 and at most of 1920x1080. Some of them do use multi-monitor setups - some of them are Notebooks / Tablets - but the error appears on all kinds of my devices. The Windows XP we are using is a standard MSDN Windows XP Professional SP3 Corporate Edition CD - without any modification or customization done to it.
Comment 5 Michael Schumacher 2013-02-04 19:22:10 UTC
There are many users who run GIMP 2.8.2 on Windows XP SP3 without this problem, no idea what might be the problem.
Comment 6 enz-coast 2013-02-07 13:03:00 UTC
Is there something like a log file, even log, debug mode? Because I do not really know how to figure out GIMP crashes, without having a clue what collides / crashes / hangs...

Today I took one Model of every Computer we are using here ( 14 different Models )

-I deployed Windows XP SP3 Professional to all of them using RIS / WDS
-I installed all device drivers including GFX Card...
-The first experiment was: installing GIMP by hand - CRASH
-The second experiment was: deploy GIMP via WPKG - CRASH
-The third experiment was: install SP3 without further Updates - CRASH
-The fourth experiment was: install all available Windowsupdates - CRASH

I don´t know what else to try... Windows Vista - flawless, Windows 7 - flawless, Windows 8 - flawless - Windows XP - CRASH
Comment 7 Michael Schumacher 2013-02-07 19:22:58 UTC
BTW, GIMP 2.8.4 has just been released. Not that is is supposed to fix this - it hardly could, because we do not know what's causing the crashes on your systems - but we should at least know if it still exhibits this problem.
Comment 8 enz-coast 2013-02-20 10:10:57 UTC
Today I switched all of my clients from 2.8.2 to 2.8.4 - nothing changed. The error at startup remains unfixed... All XP machines are NOT operational...
Comment 9 Michael Schumacher 2013-02-20 17:07:41 UTC
Can you compare these Windows XP systems to some off-the-shelf XP Professional or Home systems with all updates applied? Maybe this will uncover any differences that might be relevant.

BTW: Can we rule out sabotage? Maybe someone thinks that GIMP MUST. NOT. BE. USED. THERE. or has some other crazy agenda.
Comment 10 enz-coast 2013-02-20 22:01:25 UTC
I´ll recover some of the machines Using the OEM - Recovery Media tomorrow. I hope that´ll show a change or any kind of difference...
Comment 11 Michael Schumacher 2013-03-17 16:33:28 UTC
Any news?
Comment 12 Michael Schumacher 2013-05-10 11:03:40 UTC
Any news?
Comment 13 Max Mustermann 2013-05-10 11:50:58 UTC
Thank you for reporting this. Unfortunately this particular error message is too generic to find a quick answer, so we have to investigate a bit more.
Can you please run gimp with the --verbose parameter and attach the output
here? If you're unsure on how to do it, see [1]. 
For a further analysis it would also be helpful if you could post the events
from the Windows eventlog, which occur at this time. At [2] you see how to get
them and [3] shows an example.
If all that fails and you need help on debugging GIMP to get more useful information, let us know. 
Your answer within the next 6 weeks is appreciated. Thank you in advance.

[1]
http://wiki.gimp.org/index.php/Users:Tips#Getting_and_posting_the_output_of_gimp_--verbose
[2] http://support.microsoft.com/kb/308427
[3] https://mail.gnome.org/archives/gimp-user-list/2012-December/msg00154.html
Comment 14 Max Mustermann 2013-07-05 08:04:37 UTC
Closing this bug report as no further information has been provided after more than 6 weeks. Please feel free to reopen this bug if the error also occurs with the current GIMP 2.8.6. and you can provide the information asked for. Thanks!