gtk warning

[François Patte]

Bonjour,

Every time I launch evince, I get this gtk warning:

(evince:3823): Gtk-WARNING **: Allocating size to EvSidebar
0x562ac0fa7520 without calling gtk_widget_get_preferred_width/height().
How does the code know the size to allocate?

and for emacs, this one:

(emacs:4011): Gtk-WARNING **: gtk_window_parse_geometry() called on a
window with no visible children; the window should be set up before
gtk_window_parse_geometry() is called.

What do they mean and how to get rid of them?

Thank you.

-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. [phone]
http://www.math-info.univ-paris5.fr/~patt

[Tom Horsley]

On Wed, 21 Jun 2017 12:26:50 +0200
François Patte wrote:

>  What do they mean and how to get rid of them? 
Every time I launch any GTK based tool I get near unlimited warnings
like that. GTK just loves to spew meaningless messages. If the tool
is working for you, just ignore them. If it breaks somehow and you want
to submit a bug report, then they might provide extra info to be
included in the bug report.

As far as I know, the only way to get rid of them is to redirect
stderr to /dev/null.

[Mike Wright]

On 06/21/2017 05:19 AM, Tom Horsley wrote:
>  On Wed, 21 Jun 2017 12:26:50 +0200
>  François Patte wrote:
>  
> > What do they mean and how to get rid of them?
>  
>  Every time I launch any GTK based tool I get near unlimited warnings
>  like that. GTK just loves to spew meaningless messages. If the tool
>  is working for you, just ignore them. If it breaks somehow and you want
>  to submit a bug report, then they might provide extra info to be
>  included in the bug report.
>  
>  As far as I know, the only way to get rid of them is to redirect
>  stderr to /dev/null. 
Redirecting to /dev/null doesn't shut them up for me.

Speculating here, but it seems unlikely that GTK is designed for 
unsilenceable spewage and is more likely an unwanted gift from the 
programmer.

I ended up creating a script, "run", that "exec"s another script, one

that actually invokes the desired GTK loudmouth via another exec. e.g. 
"run gimp or run rhythmbox", where gimp and rhythmbox are scripts that 
call the executables of the same name.  Both scripts redirect 3,2,1 
> /dev/null.  (Not sure why but a lot of programmers seem to like to 
open fd3 while others are partial to 5 & 6.) Mysteriously, the second 
script must be executed from its resident directory to get the desired 
results (and it's not a case of executing the executable instead of the 
script).  I have callers for each of the GTK programs I use on a regular 
basis.

I similarly do the same for programs that also spew to terminals when 
they are invoked directly or automatically.  Both firefox and chrome 
fall into that category.

Using two scripts invoking "exec" with redirected outputs is the only 
way I've been able to use a term while running anything that touches 
GTK. A kludge with a capital K but it works for me and leaves me with an 
unmolested term.

mw

[Samuel Sieb]

On 06/21/2017 10:53 AM, Mike Wright wrote:
>  Redirecting to /dev/null doesn't shut them up for me.
>  
>  Speculating here, but it seems unlikely that GTK is designed for 
>  unsilenceable spewage and is more likely an unwanted gift from the 
>  programmer.
>  
>  I ended up creating a script, "run", that "exec"s another script, one
>
>  that actually invokes the desired GTK loudmouth via another exec. e.g. 
>  "run gimp or run rhythmbox", where gimp and rhythmbox are scripts that 
>  call the executables of the same name.  Both scripts redirect 3,2,1 
>   >/dev/null.  (Not sure why but a lot of programmers seem to like to 
>  open fd3 while others are partial to 5 & 6.) Mysteriously, the second 
>  script must be executed from its resident directory to get the desired 
>  results (and it's not a case of executing the executable instead of the 
>  script).  I have callers for each of the GTK programs I use on a regular 
>  basis. 
You're running a graphical application, why do you care what it writes 
to the terminal?  If you really don't like the warnings, then file a bug 
on the application to fix their code.

[Mike Wright]

On 06/21/2017 01:05 PM, Samuel Sieb wrote:
>  On 06/21/2017 10:53 AM, Mike Wright wrote:
> > Redirecting to /dev/null doesn't shut them up for me.
> >
> > Speculating here, but it seems unlikely that GTK is designed for 
> > unsilenceable spewage and is more likely an unwanted gift from the 
> > programmer.
> >
> > I ended up creating a script, "run", that "exec"s another script,
> one 
> > that actually invokes the desired GTK loudmouth via another exec. e.g. 
> > "run gimp or run rhythmbox", where gimp and rhythmbox are scripts that 
> > call the executables of the same name.  Both scripts redirect 3,2,1 
> >  >/dev/null.  (Not sure why but a lot of programmers seem to like to 
> > open fd3 while others are partial to 5 & 6.) Mysteriously, the second 
> > script must be executed from its resident directory to get the desired 
> > results (and it's not a case of executing the executable instead of 
> > the script).  I have callers for each of the GTK programs I use on a 
> > regular basis.
>  
>  You're running a graphical application, why do you care what it writes 
>  to the terminal?  
Because 90% of my work is CLI.  Sometimes I like music, sometimes I have 
to do some image manipulation, sometimes I like the news, sometimes I 
have to google for things.  Not that difficult to imagine.

[Samuel Sieb]

On 06/21/2017 01:14 PM, Mike Wright wrote:
>  On 06/21/2017 01:05 PM, Samuel Sieb wrote:
> > You're running a graphical application, why do you care what it writes 
> > to the terminal? 
>  
>  Because 90% of my work is CLI.  Sometimes I like music, sometimes I have 
>  to do some image manipulation, sometimes I like the news, sometimes I 
>  have to google for things.  Not that difficult to imagine. 
That doesn't explain why you care about the output.  Run it in its own 
terminal or run it from the GUI.  Are you trying to background it and 
still use the same terminal for other things?