On Sun, 29 Jun 2008 22:34:42 -0400, Ales Hvezda wrote: > Maybe you should try running the new binary suite on that oldish box and > see if xgsch2pcb still crashes or misbehaves?
On my debian/lenny boxens with xgsch2pcb pulled from current git the application still hanges with no errors on stdout after pcb is started. ps aux|grep dbus reveals that a number of dbus instances are running: [EMAIL PROTECTED]:~/IQO/Projekte/Lasertreiber$ ps aux|grep dbus 101 2623 0.0 0.0 2652 1064 ? Ss Jul01 0:00 /usr/bin/dbus-daemon --system root 3320 0.0 0.0 2520 1208 ? S Jul01 0:00 dbus-daemon --session --print-address --nofork kmk 3512 0.0 0.0 4512 544 ? Ss Jul01 0:00 /usr/bin/ssh-agent /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/kmk/.gnupg/gpg-agent-info-kwak /usr/bin/dbus-launch --exit-with-session /usr/bin/seahorse-agent --execute /usr/bin/gnome-session kmk 3513 0.0 0.0 6128 856 ? Ss Jul01 0:00 /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/kmk/.gnupg/gpg-agent-info-kwak /usr/bin/dbus-launch --exit-with-session /usr/bin/seahorse-agent --execute /usr/bin/gnome-session kmk 3516 0.0 0.0 3036 688 ? S Jul01 0:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/seahorse-agent --execute /usr/bin/gnome-session kmk 3517 0.0 0.0 2520 1000 ? Ss Jul01 0:00 /usr/bin/dbus-daemon --fork --print-pid 9 --print-address 11 --session kmk 11610 0.0 0.0 5016 732 pts/1 R+ 01:46 0:00 grep dbus ---<(kaimartin)>--- -- Kai-Martin Knaak http://lilalaser.de/blog _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
