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 752729 - Gimp Crashing While Using Color Picker
Gimp Crashing While Using Color Picker
Status: RESOLVED DUPLICATE of bug 740634
Product: GIMP
Classification: Other
Component: Tools
2.8.14
Other Windows
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2015-07-22 14:59 UTC by Wallace
Modified: 2016-03-28 12:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of the error that Windows had logged in the Event Viewer. (140.11 KB, image/png)
2015-07-22 14:59 UTC, Wallace
Details

Description Wallace 2015-07-22 14:59:14 UTC
Created attachment 307914 [details]
Screenshot of the error that Windows had logged in the Event Viewer.

ERROR messages I received:
GNU Image Manipulation Program has stopped working
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

I was using the color picker to change the color of the font I was using. I clicked with the color picker on the foreground color that's displayed in the tool dialog box.
Gimp then stopped working. This is the second time this has occurred, while doing this same operation.

Below is the full text associated with the attached event error screenshot.

Log Name: Application
Source: Application Error
Date: 7/21/2015 6:31:05 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Wallace-Machine
Description:
Faulting application name: gimp-2.8.exe, version: 2.8.14.0, time stamp: 0x00000000
Faulting module name: libpixman-1-0.dll, version: 0.0.0.0, time stamp: 0xa338a330
Exception code: 0xc0000005
Fault offset: 0x000000000008ce00
Faulting process id: 0x1a8
Faulting application start time: 0x01d0c41726ae0bd8
Faulting application path: D:\Programs\Gimp\GIMP 2\bin\gimp-2.8.exe
Faulting module path: D:\Programs\Gimp\GIMP 2\bin\libpixman-1-0.dll
Report Id: 514acf95-3011-11e5-82d0-001aa0c7ebdb
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-07-22T01:31:05.000000000Z" />
<EventRecordID>23352</EventRecordID>
<Channel>Application</Channel>
<Computer>Wallace-Machine</Computer>
<Security />
</System>
<EventData>
<Data>gimp-2.8.exe</Data>
<Data>2.8.14.0</Data>
<Data>00000000</Data>
<Data>libpixman-1-0.dll</Data>
<Data>0.0.0.0</Data>
<Data>a338a330</Data>
<Data>c0000005</Data>
<Data>000000000008ce00</Data>
<Data>1a8</Data>
<Data>01d0c41726ae0bd8</Data>
<Data>D:\Programs\Gimp\GIMP 2\bin\gimp-2.8.exe</Data>
<Data>D:\Programs\Gimp\GIMP 2\bin\libpixman-1-0.dll</Data>
<Data>514acf95-3011-11e5-82d0-001aa0c7ebdb</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

The below link is to a YouTube video demo of showing the crash event/error.

https://www.youtube.com/watch?v=SARIpRoMVVM
Comment 1 Michael Schumacher 2015-07-23 23:00:51 UTC
Duplicate of bug 740634?
Comment 2 Wallace 2015-07-23 23:32:43 UTC
(In reply to Michael Schumacher from comment #1)
> Duplicate of bug 740634?

Okay, if you say so.
Comment 3 Michael Natterer 2016-03-28 00:26:20 UTC
Wallace, is it really the same bug? Do you use multiple monitors?
Comment 4 Wallace 2016-03-28 00:35:04 UTC
(In reply to Michael Natterer from comment #3)
> Wallace, is it really the same bug? Do you use multiple monitors?

I no longer use Gimp 2.8.14 and this bug doesn't appear in the latest Gimp release of 2.8.16, so I guess this issue was solved in 2.8.16.

However, I was using multiple monitors when I had 2.8.14 installed.
I'm also no longer using a multiple monitor setup.
Comment 5 Michael Natterer 2016-03-28 12:30:53 UTC
Thanks, I think it's safe to assume you were suffering from the
multi-monitor issue in bug 740634.

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