On 2016-09-14 11:40:41 +0900, Yasushi SHOJI wrote: > On Thu, 08 Sep 2016 10:38:09 +0900, > Leon Meier wrote: > > > > By the way, I don't know who is the culprit: libgtk-3-0, emacs, or > > someone else. So please consider my found / nofound tags just as > > additional information on my configuration rather as a bug source > > hint. Sorry about that. > > https://mail.gnome.org/archives/commits-list/2016-May/msg06553.html > > I found this commit on Gtk+. So I assume this is an intended change > for Gtk+ 3.22, no?
According to the bug report it refers: https://bugzilla.gnome.org/show_bug.cgi?id=765410 there was already an issue since Gtk+ 3.20 at least. The warning was added recently to signal that this was the fault of the application, which did something wrong. IMHO, a warning in this case is bad. This is just debugging information, which annoys the end user. If the goal was to make the cause of the problem visible enough to that the user could report a bug, then fine, but there should be an *easy* way to silence this warning (e.g. once the bug has been reported), without other side effects. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
