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 777944 - GdkMonitor is not implemented for Quartz
GdkMonitor is not implemented for Quartz
Status: RESOLVED DUPLICATE of bug 779184
Product: gtk+
Classification: Platform
Component: Backend: Quartz
3.22.x
Other Mac OS
: Normal normal
: ---
Assigned To: gtk-quartz maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2017-01-30 15:41 UTC by draymond
Modified: 2017-03-08 12:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
stack trace (2.21 KB, text/plain)
2017-01-30 15:41 UTC, draymond 		Details

Description draymond 2017-01-30 15:41:53 UTC 
Created attachment 344562 [details]
stack trace

After upgrading from 3.20 to 3.22 I am now seeing the following error in the console while running my application under OSX:

(my_app:68224): Gdk-WARNING **: GdkQuartzDisplay does not implement the monitor vfuncs
Comment 1 Daniel Boles 2017-01-30 15:47:35 UTC 
That's not an error. It's a warning. The monitor API is quite new, and no one has yet implemented support for Quartz, so it has to create a fallback monitor, and it warns that it had to do this. I presume your application continues to work after this warning. Would you like to try writing a patch to implement the monitor API?
Comment 2 draymond 2017-01-31 01:10:55 UTC 
Hi, Daniel.  I don't really know anything about the monitor API.  I am reporting this as an application developer.  When GTK emits errors or warnings to the console that generally indicates the application developer needs to fix something in their code.  I have tried to do that but my debugging indicates there is nothing I can do from the application side.  So I am left to ignore the warning and let my users see it and continually report it to me?  That's not an ideal scenario.  IMHO, this warning should be removed or perhaps triggered only when the application invokes the monitor API.
Comment 3 Daniel Boles 2017-01-31 09:30:05 UTC 
That's a sensible request. I believe it also precedents in other warnings being 'downgraded' to only appear in debug modes. Let's see what the maintainers think.

Hopefully someone will get a chance to implement the monitor API in Quartz before too long.


(FWIW, I continue to get one "How does the application know what size to allocate?" message for each run of my program. I guess I could have my program print the bit of code that precisely answers that question, around the same time.)
Comment 4 Matthias Clasen 2017-03-08 11:55:26 UTC 
Looks like there is an implementation of it here:

https://github.com/tschoonj/gtk/commits/gtk4-quartz
Comment 5 Emmanuele Bassi (:ebassi) 2017-03-08 12:08:38 UTC 
Tom already filed bug 779184 with a link to his branch, and I've asked him to attach his patches there, so we can track the issue in the other bug.

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