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 753746 - Failure to load in New Windows 10 Download
Failure to load in New Windows 10 Download
Status: RESOLVED DUPLICATE of bug 449848
Product: GIMP
Classification: Other
Component: General
2.8.0
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2015-08-18 09:42 UTC by Nick
Modified: 2016-09-24 21:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nick 2015-08-18 09:42:33 UTC
Post downloading Windows 10 I experienced that GIMP 2.8 would not open.  I uninstalled the program and re-installed it experiencing the same problem.  GIMP will not load in Windows 10.
Comment 1 Michael Schumacher 2015-08-18 13:40:10 UTC
Seems to work fine for other people, so it might be up to you to figure this out.
Comment 2 André Klapper 2015-08-18 18:45:13 UTC
Please provide exact steps to reproduce that someone else could follow, and any error messages when starting from a terminal window.
Comment 3 Nick 2015-08-19 00:27:39 UTC
Andre Klapper:  I uploaded and installed Windows 10.  When I attempted to open GIMP 2.8 it froze.  The only way to terminate the program was to utilize Task Manager. There was no message.  Many attempts produced the same result.  I uninstalled GIMP 2.8 and re-installed GIMP 2.8 and experienced the same results. . . . freeze; Task Manger to terminate.  Predicated on Expert Michael Schumacher, I have uninstalled Windows 10, reverted to Windows 7 and GIMP 2.8 works perfectly.
Comment 4 Michael Schumacher 2015-08-19 12:30:00 UTC
Is this the "recreate font cache on first start" issue? Seems likely after an upgrade of the operating system, which probably updated a lot of font files as well.

Use a file access monitor (maybe the Windows 10 task manager has learned to do this) to see what the gimp process is doing.
Comment 5 André Klapper 2015-08-19 12:45:11 UTC
(In reply to Nick from comment #3)
> Andre Klapper:  I uploaded and installed Windows 10.  When I attempted to
> open GIMP 2.8 it froze.  

Which exact GIMP version? "2.8" can be many different subversions...
Comment 6 Emma 2015-08-21 21:23:43 UTC
Same for me here. Re-installed many times but no success.
Comment 7 Nick 2015-08-21 23:42:57 UTC
Emma,
I uninstalled and re-installed W10.  GIMP works on 2nd re-install.
Comment 8 Emma 2015-08-22 15:05:09 UTC
Yes, after 6 re installation, it finally works.
Thanks.
Comment 9 Simone 2015-09-03 21:18:13 UTC
Same issue here. I was running GIMP 2.8.6 and installed Windows 10. Since it didn't load, I tried downloading and installing 2.8.14. Still nothing. Please note that there are no error messages, no prompts, nothing - you click on the program icon or any .xcf file, and absolutely nothing happens. GIMP doesn't even show up in task manager.

I tried un-installing and re-installing it (the latest version) at least 7 times, rebooting in between installations, and still no success. Any ideas on what might be happening?
Comment 10 Nick 2015-09-04 11:04:43 UTC
Hi Simone,

I have experienced success loading Gimp one time on one PC on the 1st try.  The other took successfully after #2.  I am aware of up to 6 tries before success.  There are many problems with drivers in many areas of Windows 10 as I understand it.  I would suggest you document your effort and submit it to the MS Windows 10 team.  If enough folks do the same, the priority to resolve the issue may be upgraded.
Comment 11 Simone 2015-09-08 13:23:58 UTC
Eh, I ended up reporting the error and then going back to Windows 7 even though I quite liked Win 10 - can't do without Gimp :)

I hope they fix the driver issues quickly.
Comment 12 Michael Schumacher 2016-05-09 08:51:06 UTC
Some of the freezes encountered here could be bug 449848 - the initial font cache creation. A tool like Process Monitor can tell you what a process is actually doing when it appears to be non-responsive: https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
Comment 13 Michael Schumacher 2016-09-24 21:20:54 UTC
Let's assume this to be a duplicate of bug 449848.

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