On Saturday 18 April 2009 01:49:56 Tim Kientzle wrote: > Igor R wrote: >>> "unexpected character `{', expected keyword - e.g. `style' >> Looks like GTK? GTK is certainly involved, it appears. From ktrace, I know that it invokes open() on the raw directory and reads it just before generating the warning. From inside GDB, I can breakpoint open() and see this backtrace just before the warning gets printed: Breakpoint 2, 0x28ca9f5c in open () from /lib/libc.so.7 #0 0x28ca9f5c in open () from /lib/libc.so.7 #1 0x28a97cb2 in open () from /lib/libthr.so.3 #2 0x2836c227 in gtk_rc_get_im_module_path () from /usr/local/lib/libgtk-x11-2.0.so.0 #3 0x2836c7a4 in gtk_rc_reparse_all_for_settings () from /usr/local/lib/libgtk-x11-2.0.so.0 #4 0x28388b64 in gtk_settings_get_for_screen () from /usr/local/lib/libgtk-x11-2.0.so.0 #5 0x28388cf5 in gtk_settings_get_default () from /usr/local/lib/libgtk-x11-2.0.so.0 So gtk is reading the raw directory and trying to interpret it as a settings file. Still don't know where it's getting the screwed-up settings file name from, but this is progress. TimReceived on Sat Apr 18 2009 - 15:22:46 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:46 UTC