Uwe Brauer writes:
> (1) Make sure you have dbus running (sorry, I don't know
anything
> about dbus, I just know that GTK3 wants it).
Hm but I am using GTK2.
I don't know that GTK2 doesn't need it; we're shooting in the dark
here.
> (2) Try starting up with your network disabled (ifconfig eth0
down,
> for example; restart with ifconfig eth0 up).
I tried that
ifconfig eth0 down
dbus-launch
ifconfig eth0 up
Indeed xemacs starts faster.
I meant to start xemacs with the network down. If you didn't, then it
is something to do with dbus. At least we have some evidence that
it's not the GTK-related code in XEmacs itself.
- Configurations in my .Xdefault file seems to be ignored.
That's expected. GTK has its own configuration system.
- When I start with my init files, it finally crashes, I can
provide the lisp backtrace.
Lisp backtraces aren't interesting in crashes. We need a C backtrace
to debug a crash.
- when I try to run
gdb
/home/oub/ALLES/Add-Import/xemacs-gtk/jsparkes-xemacs-gtk-7c940534dc1e/src/xemacs
core then nothing is found.
Try "ulimit -c unlimited" before running gdb. You may also have to
look elsewhere for the core files.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta