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 795727 - gimp color-dialog is storing or restoring position incorrectly
gimp color-dialog is storing or restoring position incorrectly
Status: RESOLVED DUPLICATE of bug 782194
Product: GIMP
Classification: Other
Component: User Interface
2.10.0
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2018-05-01 20:35 UTC by Jason Cole
Modified: 2018-05-02 17:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jason Cole 2018-05-01 20:35:28 UTC 
Reproduction steps (Windows 10):

* configure screens such that the top left-hand corner of the desktop space is not visible on any monitor (a 22"@1080p screen on the left, and a 43" 4k screen on the right).
* start up gimp
* move GIMP to fullscreen on the smaller display
* attempt to change the foreground or background color (the header is offscreen, but the rest of the dialog can be seen).
* close the dialog
* reopen the dialog, by attempting to change the background color again (the dialog is now hiding in the top left. This can be verified by making the dialog ~2500px wide the first time it is opened)

Proposed fix:
* check to make sure that dialogs appear on a screen, possibly by changing their window type?
Comment 1 Michael Natterer 2018-05-01 21:05:49 UTC 
You say dialog*s*, doey this happen with any other dialog?
Comment 2 Michael Natterer 2018-05-01 21:06:00 UTC 
*does*
Comment 3 Jason Cole 2018-05-02 15:07:31 UTC 
It does not appear to affect either the "New..." dialog or the "Gaussian Blur" dialog. It might just be the color picker.
Comment 4 Jason Cole 2018-05-02 15:11:21 UTC 
Are there other specific dialogs you'd like tested, in order to narrow down the bug?
Comment 5 Michael Natterer 2018-05-02 17:05:20 UTC 
Thanks for checking, this is a duplicate.

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