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 757717 - HELP: I cannot save files on Windows 10!
HELP: I cannot save files on Windows 10!
Status: RESOLVED INCOMPLETE
Product: GIMP
Classification: Other
Component: General
2.8.14
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2015-11-07 04:19 UTC by Jeb Eldridge
Modified: 2017-01-04 22:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
System Information (1.40 MB, text/plain)
2015-11-07 04:19 UTC, Jeb Eldridge
Details
GIMP-2.8.EXE WINDOWS DUMP FILE - Google Drive Location (151 bytes, text/plain)
2015-11-11 02:16 UTC, Jeb Eldridge
Details

Description Jeb Eldridge 2015-11-07 04:19:05 UTC
Created attachment 315021 [details]
System Information

The Save dialogue freezes GIMP each and every time I go to save, export, save as, etc. on Gimp 2.8.14 on Windows 10 - And there's no way around it from the looks of it, which brings my productivity to a screeching halt and with that, my PC performance.
Please fix :-(

Please see below for system details about my PC. Also, please see attached for a full .TXT file dump from MSINFO32.exe containing all information needed.



--------------

System Information report written at: 11/06/15 23:13:04
System Name: DESKTOP-04RV02T
[System Summary]

Item	Value	
OS Name	Microsoft Windows 10 Pro Insider Preview	
Version	10.0.10576 Build 10576	
Other OS Description 	Not Available	
OS Manufacturer	Microsoft Corporation	
System Name	DESKTOP-04RV02T	
System Manufacturer	BIOSTAR Group	
System Model	A880G+	
System Type	x64-based PC	
System SKU	To Be Filled By O.E.M.	
Processor	AMD Phenom(tm) II X4 850 Processor, 3300 Mhz, 4 Core(s), 4 Logical Processor(s)	
BIOS Version/Date	American Megatrends Inc. 080016, 9/21/2011	
SMBIOS Version	2.6	
Embedded Controller Version	255.255	
BIOS Mode	Legacy	
BaseBoard Manufacturer	BIOSTAR Group	
BaseBoard Model	Not Available	
BaseBoard Name	Base Board	
Platform Role	Desktop	
Secure Boot State	Unsupported	
PCR7 Configuration	Binding Not Possible	
Windows Directory	C:\WINDOWS	
System Directory	C:\WINDOWS\system32	
Boot Device	\Device\HarddiskVolume1	
Locale	United States	
Hardware Abstraction Layer	Version = "10.0.10576.0"	
User Name	DESKTOP-04RV02T\Jeb	
Time Zone	Eastern Standard Time	
Installed Physical Memory (RAM)	8.00 GB	
Total Physical Memory	7.94 GB	
Available Physical Memory	3.23 GB	
Total Virtual Memory	9.19 GB	
Available Virtual Memory	3.67 GB	
Page File Space	1.25 GB	
Page File	C:\pagefile.sys	
Hyper-V - VM Monitor Mode Extensions	Yes	
Hyper-V - Second Level Address Translation Extensions	Yes	
Hyper-V - Virtualization Enabled in Firmware	Yes	
Hyper-V - Data Execution Protection	Yes
Comment 1 Michael Schumacher 2015-11-07 11:09:20 UTC
Someone on https://superuser.com/questions/979504/load-dialog-disk-access-slowdown-on-windows-10 has traced a similar behavior - for all programs - back to a floppy controller setting in BIOS. You might want to check this.
Comment 2 Jeb Eldridge 2015-11-10 12:19:35 UTC
Hi again! :-)
I am happy this bug wasn't abandoned and has been similarly reported... my bug slightly differs though.
-----
UPDATE! 11/10/2015
The virtual floppy driver in my BIOS Settings (BioStar A880G+ for AMD AM3) is disabled, but I still get the exact same "Not Responding" dialogue from GIMP and Windows as I go to save - albeit it seems an update to Windows or GIMP has *slightly* fixed the issue, because now I finally get a classic Windows Explorer window open to save the file, but only after an unreasonable amount of time (sometimes 5 minutes or more) while Windows thinks the program is not responding.
I have created a Microsoft Windows Dump (.DMP) file for Gimp-2.8.exe to help out with debugging and development on a more reliable GIMP application.
I am uploading the file now.
Comment 3 Jeb Eldridge 2015-11-11 02:15:07 UTC
IUnfortunately, the Windows Crash Dump file has been too large to attach onto the bug report itself even after several attempts of compressing the file. The crash dump file is located on Google Drive at https://drive.google.com/open?id=0B6ihhZN41GENX3ZvRnR2Nk5iOW8
Comment 4 Jeb Eldridge 2015-11-11 02:16:30 UTC
Created attachment 315222 [details]
GIMP-2.8.EXE WINDOWS DUMP FILE - Google Drive Location
Comment 5 Michael Schumacher 2015-11-12 13:04:41 UTC
That file is not really shared, I doubt many people are going to request access.

Also, about the "not abandoned": for bugs on the Windows platforms, we pretty much rely on affected users to do the research - few of the developers use Windows at all, and it seems to be an odd feature of this platform to never let such problems happen to the few who do.
Comment 6 Michael Z Freeman 2016-05-04 13:32:51 UTC
I also get this bug. At first nothing happens when going to save a file either from "export as" or other save attempts from, for example "save for web". There is then a delay of sometimes ~5-10 minutes and eventually a file save dialogue window appears. I can provide more info / logs on request. I have successfully built Gimp git from source for Linux and am looking into building for Windows so I could test fixes sometime in the near future.
Comment 7 nm 2016-05-29 17:44:25 UTC
Can't reproduce this on win 10 at the moment. Tested with both 2.8 and with git master version but can save it in a blink of an eye.

Tested to only save on the desktop and still can't reproduce it.
Comment 8 Michael Schumacher 2016-06-04 20:15:55 UTC
Barney, you have checked the link I added in comment 1?
Comment 9 Michael Schumacher 2016-07-22 07:56:05 UTC
Be advised that without someone who is affected figuring this out, there will likely not be any change - for the majority of Windows 10 users, there seems to be no problem.
Comment 10 Michael Schumacher 2016-10-09 18:57:42 UTC
Network shares - or anything else hat refers to a (preferably non-accessible) network location can cause this, too.
Comment 11 Michael Schumacher 2016-12-02 10:09:07 UTC
Jeb, Michael: have you found anything that might cause this, per chance?
Comment 12 Michael Schumacher 2017-01-04 22:57:43 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!