Starting with emacs 26 I get thses GTK warnings when I start emacs: # > emacs-26 (emacs-26:10892): Gtk-CRITICAL **: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed (emacs-26:10892): Gtk-CRITICAL **: gtk_widget_override_background_color: assertion 'GTK_IS_WIDGET (widget)' failed (emacs-26:10892): Gtk-CRITICAL **: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed (emacs-26:10892): Gtk-CRITICAL **: gtk_widget_override_background_color: assertion 'GTK_IS_WIDGET (widget)' failed (emacs-26:10892): Gtk-CRITICAL **: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed (emacs-26:10892): Gtk-CRITICAL **: gtk_widget_override_background_color: assertion 'GTK_IS_WIDGET (widget)' failed (emacs-26:10892): Gtk-CRITICAL **: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed (emacs-26:10892): Gtk-CRITICAL **: gtk_widget_override_background_color: assertion 'GTK_IS_WIDGET (widget)' failed
Just noted that is is these lines in my .emacs files that causes the warnings: ;; Color settings. (setq default-frame-alist '((background-color . "#333333") (foreground-color . "White") (cursor-color . "White"))) (setq initial-frame-alist default-frame-alist) In particular it is the (background-color . "#333333") item that is causing the warnings
Can you please report this upstream, too?
(In reply to Ulrich Müller from comment #2) > Can you please report this upstream, too? Here: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32975 I will report back if I hear back from upstream.
Seems like app-emacs/ecb-2.41_pre20140215-r1 is causing this. Look at the upstrem bug. The current ecb points to https://github.com/alexott/ecb.git and that is old. New how seems to be https://github.com/ecb-home/ecb/commits/master. A new snapshot from there seems in order.
BTW, ECB seems dormant and I suspect emacs-ycmd(https://github.com/abingham/emacs-ycmd) would be better.
(In reply to Joakim Tjernlund from comment #4) > Seems like app-emacs/ecb-2.41_pre20140215-r1 is causing this. Look at the > upstrem bug. Still, lisp code shouldn't be able to cause any GTK+ warnings? > The current ecb points to https://github.com/alexott/ecb.git and that is old. > New how seems to be https://github.com/ecb-home/ecb/commits/master. > A new snapshot from there seems in order. Ah, looks like I've missed that. I am going to make a new snapshot from there then. (And how much nicer it would be if they did actual releases...) (In reply to Joakim Tjernlund from comment #5) > BTW, ECB seems dormant and I suspect > emacs-ycmd(https://github.com/abingham/emacs-ycmd) would be better. Looks like that would need ycmd (https://github.com/Valloric/ycmd) as a dependency, which is not in the tree?
(In reply to Ulrich Müller from comment #6) > (In reply to Joakim Tjernlund from comment #4) > > Seems like app-emacs/ecb-2.41_pre20140215-r1 is causing this. Look at the > > upstrem bug. > > Still, lisp code shouldn't be able to cause any GTK+ warnings? I guess so. > > > The current ecb points to https://github.com/alexott/ecb.git and that is old. > > New how seems to be https://github.com/ecb-home/ecb/commits/master. > > A new snapshot from there seems in order. > > Ah, looks like I've missed that. I am going to make a new snapshot from > there then. (And how much nicer it would be if they did actual releases...) Don't think there is much new in there though. > > > (In reply to Joakim Tjernlund from comment #5) > > BTW, ECB seems dormant and I suspect > > emacs-ycmd(https://github.com/abingham/emacs-ycmd) would be better. > > Looks like that would need ycmd (https://github.com/Valloric/ycmd) as a > dependency, which is not in the tree? Correct, there seem to be a build.py script to build it all and I don't speak python :( emacs-ymcd is in melpa though, one can get the ebuilds needed via app-portage/gs-elpa
Created attachment 550602 [details, diff] Don't call GTK functions on non-GTK scrollbars (Bug#32975) This patch, from upstream, fixes the problem.
Thank you. It looks like emacs-26.2 isn't very far away: https://lists.gnu.org/archive/html/emacs-devel/2018-10/msg00060.html So I wonder if this merits a revision bump of 26.1 (IIUC, it is only a warning but doesn't affect functionality) or if we should wait for the release of 26.2?
(In reply to Ulrich Müller from comment #9) > Thank you. It looks like emacs-26.2 isn't very far away: > https://lists.gnu.org/archive/html/emacs-devel/2018-10/msg00060.html > > So I wonder if this merits a revision bump of 26.1 (IIUC, it is only a > warning but doesn't affect functionality) or if we should wait for the > release of 26.2? I can wait, I got it here anyway. Thanks. I rather like if you had a look at packaging ycmd server :)
BTW, upstream was a bit surprised over the use of --without-toolkit-scroll-bars Something to look into?
Closing as RESOLVED UPSTREAM. (In reply to Joakim Tjernlund from comment #11) > BTW, upstream was a bit surprised over the use of > --without-toolkit-scroll-bars > Something to look into? It can be controlled with the toolkit-scroll-bars USE flag. I don't see a compelling reason to flip the default of that flag, when all other toolkit related flags are off by default.
