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 666940 - In mypaint, the color picker doesn't work on a secondary screen
In mypaint, the color picker doesn't work on a secondary screen
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.24.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2011-12-28 09:42 UTC by Philippe Nicloux
Modified: 2018-02-10 04:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Philippe Nicloux 2011-12-28 09:42:37 UTC 
Well,In mypaint, the color picker doesn't work on a secondary screen. 
It only catch black color.

This bug exist only since version 0.9 and doesn't exist under linux.
Comment 1 André Klapper 2011-12-28 16:18:13 UTC 
Which exact gtk version is this about?
Comment 2 Martin Renold 2011-12-28 16:34:52 UTC 
I assume he is using MyPaint 1.0.0, so that should be GTK+ 2.24.8.
Comment 3 Philippe Nicloux 2011-12-28 16:36:10 UTC 
Excuse such a silly question, but where can I see the version of gtk Mypaint is using ?
Comment 4 Martin Renold 2011-12-28 16:47:44 UTC 
Locate a file named libgtk-win32-2.0-0.dll or similar in the MyPaint installation, and hover your cursor over it.
Comment 5 Philippe Nicloux 2011-12-28 17:11:50 UTC 
Thanks !
So , yes, you were right, it was the gtk+ 2.24.8
Comment 6 Michael Schumacher 2012-07-12 15:23:36 UTC 
Is bug #676708 a duplicate of this? I'm unsure, because this one explicitly states that this happens on a secondary screen, but does not specify what happens on the primary screen.
Comment 7 Philippe Nicloux 2012-07-13 07:52:30 UTC 
Hi, to be more explicite : the color picker works fine on a primary screen, and not on the secondary screen.
Comment 8 Matthias Clasen 2018-02-10 04:35:07 UTC 
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.