Created attachment 453986 [details] emerge --info launching some gtk+ applications (e.g., zathura) from xterm causes a flood of useless gtk debug messages to spam the terminal, making it unusable for anything else. This seems to be caused by the configure option "--enable-debug", which is set to "yes" by default (for gtk+-3*) Please add "--enable-debug=minimum" to the ebuild, or else add a USE variable. (Note that "--enable-debug=no" could lead to crashes, according to upstream)
gtk+:3 does not pass any --enable-debug flag and as such it ends up with minimum debug already. At the start of gtk+ building at the end of configure, you can also see the configure summary where it says: Debugging: minimum So the premise here is false on the "spam". I can't say anything further, as that "spam" is not provided. Also, why look at the terminal for a GUI program?
(In reply to Mart Raudsepp from comment #1) > gtk+:3 does not pass any --enable-debug flag and as such it ends up with > minimum debug already. At the start of gtk+ building at the end of > configure, you can also see the configure summary where it says: > > Debugging: minimum You're right. It seems upstream has a peculiar notion of "minimum". Nothing to be done... > > So the premise here is false on the "spam". > I can't say anything further, as that "spam" is not provided. (zathura:961): Gtk-WARNING **: Theme parsing error: <data>:9:26: The style property GtkRange:slider-width is deprecated and shouldn't be used anymore. It will be removed in a future version (repeat ad infinitum) Unsolicited bulk disruptive crap. > Also, why look at the terminal for a GUI program? Because a GUI program doesn't have to be launched by mouse clicking. An xterm is used for many things besides seeing debug messages when something goes wrong (in the current case, when it doesn't). Some of us use xterm to cd to a dir and do related stuff( e.g., gvim foo.tex, pdflatex foo.tex, zathura foo.pdf, etc), recalling bash history when needed, etc.
The theme you use should be updated to be more compatible with gtk+-3.20, as the theme stuff should be stable now since then; I guess they didn't break everything, but some of it goes through deprecation, so things might visually break on 3.22 (unless that's what you use already) or 3.89+. Not sure what theme that is, so maybe this bug should be converted to fixing that, or I guess we can just close it for now and you can reopen a new one about the theme warnings if you feel so inclined. I'll leave open for now and probably close in a future run through bugmail/open bugs unless you can some other ideas or want to convert this one to the theme bug :)
(In reply to Mart Raudsepp from comment #3) > The theme you use should be updated to be more compatible with gtk+-3.20, as > the theme stuff should be stable now since then; I guess they didn't break > everything, but some of it goes through deprecation, so things might > visually break on 3.22 (unless that's what you use already) or 3.89+. > > Not sure what theme that is Just yesterday I manually fixed my theme to avoid these warnings in emacs. The error messages I was receiving referred me to "gtk.css", and a search of my whole /usr/share tree turned up /usr/share/themes/Xfce-kolors/gtk-3.0/gtk.css Jorge's error messages don't provide a filename, (zathura:961): Gtk-WARNING **: Theme parsing error: <data>:9:26 and instead they mention "<data>", so I'm not sure where the correction needs to take place. Maybe zathura is loading the theme styles itself, and feeding them to GTK+ as a string or something? I guess the first thing I would try is to figure out which GTK+ theme you're using; for example, I'm using Xfce-kolors. See if you can fix the errors in the associated CSS file and test if the zathura errors go away. If they do, then at least we know that fixing the theme will fix the warnings.
(In reply to Mart Raudsepp from comment #3) > > I'll leave open for now and probably close in a future run through > bugmail/open bugs unless you can some other ideas or want to convert this > one to the theme bug :) Agreed, I think this is not a Gentoo bug but rather an upstream misfeature.
(In reply to Michael Orlitzky from comment #4) > (In reply to Mart Raudsepp from comment #3) > > (zathura:961): Gtk-WARNING **: Theme parsing error: <data>:9:26 > > and instead they mention "<data>", so I'm not sure where the correction > needs to take place. Maybe zathura is loading the theme styles itself, and > feeding them to GTK+ as a string or something? > > I guess the first thing I would try is to figure out which GTK+ theme you're > using; for example, I'm using Xfce-kolors. See if you can fix the errors in > the associated CSS file and test if the zathura errors go away. If they do, > then at least we know that fixing the theme will fix the warnings. I didn't install any general gtk themes, so whatever it is is just a default. I installed themes for the WM (openbox): $ ls -1 /usr/share/themes/ Artwiz-boxed Bear2 Clearlooks Clearlooks-3.4 Clearlooks-Olive Default Emacs Mikachu Natura Onyx Onyx-Citrus Orang Raleigh Surreal_Gentoo Syscrash I have Artwiz-boxed selected. zathura is minimalistic, its window has the Artwiz-boxed decorations as expected.
Try upgrading to dev-libs/girara-0.2.6. That's the library that provides the user interface for Zathura. Afterwards, you *must* re-emerge app-text/zathura itself. I was able to make the warnings go away by doing so.
(In reply to Michael Orlitzky from comment #7) > Try upgrading to dev-libs/girara-0.2.6. That's the library that provides the > user interface for Zathura. Afterwards, you *must* re-emerge > app-text/zathura itself. I was able to make the warnings go away by doing so. Thanks, it works for me too.
Marking as duplicate of newer girara stabilization then. I've asked there to consider going with 0.2.6 instead of 0.2.5 *** This bug has been marked as a duplicate of bug 571330 ***
