A quick follow-up. The warning is triggered simply by selecting Options under 
Settings. No additional action is required to generate the warning. 


Louis 

----- Original Message ----- 
From: "Louis P Zulli" <[email protected]> 
To: "Christian Anthon" <[email protected]> 
Cc: [email protected] 
Sent: Sunday, January 11, 2009 11:24:51 AM GMT -05:00 US/Canada Eastern 
Subject: [Bug-gnubg] Re: GTK warning 


Thanks. Gave that a try. Does this help? 



Gtk-WARNING **: Unable to find default local directory monitor type 
aborting... 


Program received signal SIGABRT, Aborted. 
0x93585e42 in __kill () 
(gdb) bt 
#0  0x93585e42 in __kill () 
#1  0x93585e34 in kill$UNIX2003 () 
#2  0x935f823a in raise () 
#3  0x93604679 in abort () 
#4  0x04ef733f in g_logv () 
#5  0x04ef7369 in g_log () 
#6  0x0452afa4 in gtk_folder_constructed () 
#7  0x04e74e3c in g_object_newv () 
#8  0x04e7565c in g_object_new_valist () 
#9  0x04e757ab in g_object_new () 
#10 0x0452a87f in enumerate_children_callback () 
#11 0x04a9977e in g_simple_async_result_complete () 
#12 0x04a997d1 in complete_in_idle_cb () 
#13 0x04eecf5b in g_main_context_dispatch () 
#14 0x04ef0c3e in g_main_context_iterate () 
#15 0x04ef0fa7 in g_main_loop_run () 
#16 0x04573a01 in gtk_main () 
#17 0x000eda6c in GTKRunDialog (dialog=0x1b3fe008) at gtkwindows.c:463 
#18 0x000e3599 in GTKSetOptions () at gtkoptions.c:1774 
#19 0x046e4fb6 in gtk_item_factory_callback_marshal () 
#20 0x04e6e7a9 in g_closure_invoke () 
#21 0x04e7f022 in signal_emit_unlocked_R () 
#22 0x04e806db in g_signal_emit_valist () 
#23 0x04e80ab9 in g_signal_emit () 
#24 0x0468f574 in gtk_widget_activate () 
#25 0x04588743 in gtk_menu_shell_activate_item () 
#26 0x04588ae8 in gtk_menu_shell_button_release () 
#27 0x0457619b in _gtk_marshal_BOOLEAN__BOXED () 
#28 0x04e6e7a9 in g_closure_invoke () 
#29 0x04e7f1cb in signal_emit_unlocked_R () 
#30 0x04e801da in g_signal_emit_valist () 
#31 0x04e80ab9 in g_signal_emit () 
#32 0x0468f806 in gtk_widget_event_internal () 
#33 0x04574385 in gtk_propagate_event () 
#34 0x0457491f in gtk_main_do_event () 
#35 0x049ae9a5 in gdk_event_dispatch () 
#36 0x04eecf5b in g_main_context_dispatch () 
#37 0x04ef0c3e in g_main_context_iterate () 
#38 0x04ef0fa7 in g_main_loop_run () 
#39 0x04573a01 in gtk_main () 
#40 0x000b3d9b in RunGTK (pwSplash=0x0, commands=0x0, python_script=0x0, 
match=0x0) at gtkgame.c:3820 
#41 0x0002e379 in main (argc=1, argv=0xbffff754) at gnubg.c:5078 

(gdb) quit 
The program is running.  Exit anyway? (y or n) y 
Procyon: ~]  

----- Original Message ----- 
From: "Christian Anthon" <[email protected]> 
To: "Louis P Zulli" <[email protected]> 
Cc: [email protected] 
Sent: Sunday, January 11, 2009 9:22:40 AM GMT -05:00 US/Canada Eastern 
Subject: Re: GTK warning 

I cannot reproduce this, but you can try to obtain a backtrace by 
running under gdb: 

anthon-desktop% gdb ./gnubg 
(gdb) run --g-fatal-warnings 

and type bt when gnubg exits on the first warning. 

Christian. 

On Sat, Jan 10, 2009 at 12:17 PM, Zulli, Louis P <[email protected]> wrote: 
> I invoke from a terminal with gnubg -w and then do Settings-->Options 
> followed by Cancel and Quit. After quitting, I have the following in my 
> terminal window: 
> (gnubg:13719): Gtk-WARNING **: Unable to find default local directory 
> monitor type 
> (gnubg:13719): Gtk-WARNING **: Unable to find default local directory 
> monitor type 
> (gnubg:13719): Gtk-WARNING **: Unable to find default local directory 
> monitor type 
> (gnubg:13719): Gtk-WARNING **: Unable to find default local directory 
> monitor type 
> (gnubg:13719): Gtk-WARNING **: Unable to find default local directory 
> monitor type 
> (gnubg:13719): Gtk-WARNING **: Unable to find default local directory 
> monitor type 
> (gnubg:13719): Gtk-WARNING **: Unable to find default local directory 
> monitor type 
> (gnubg:13719): Gtk-WARNING **: Unable to find default local directory 
> monitor type 
> (gnubg:13719): Gtk-WARNING **: Unable to find default local directory 
> monitor type 
> There are always nine of these warnings. I have no apparent problems using 
> gnubg, so I suppose these are harmless. 
> My gnubg was just built from the very latest snapshot, and I'm using 
> GTK+-2.14.6. I believe these warnings have been present for quite some time; 
> I finally decided to isolate and report them. 
> Louis 

_______________________________________________ Bug-gnubg mailing list 
[email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
_______________________________________________
Bug-gnubg mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnubg

Reply via email to