> Yes the socket exist but is dead because of a crashed beagle (forgot the > evolution# issue?). > > [EMAIL PROTECTED]:~$ stat .beagle/socket > File: `.beagle/socket' > Size: 0 Blocks: 0 IO Block: 4096 socket > Device: 806h/2054d Inode: 328351 Links: 1 > Access: (0755/srwxr-xr-x) Uid: ( 1000/ meebey) Gid: ( 1000/ meebey) > Access: 2008-04-20 16:28:33.000000000 +0200 > Modify: 2008-04-20 16:28:33.000000000 +0200 > Change: 2008-04-20 16:28:33.000000000 +0200 > [EMAIL PROTECTED]:~$ > > Beagle doesn't crash completly btw, the process is still there but not > even responding to kill, only kill -9 works in that stage, see #475640 > for the crash trigger / cause.
Ahh... that explains it. And now I have to figure out why does not beagle completely crash. So basically the only chance of reproducing this is to trigger the evolution# crash :) > After I killed beagled using kill -9, gnome-color-chooser and other GTK+ > apps "work" again (not hanging with EAGAIN). > > Beagle or libbeagle should handle this case gracefully though (when > beagle crashes / hangs for some reason) The problem is - this is a crash in a native library and beagle has _no_ control over it. Maybe Mono has some control but I am not sure. I need a favour if it is possible to reproduce the evolution-sharp crash. In that case, start beagled from the terminal, let it crash and hang and then send a SIGQUIT to the beagled process. Hopefully mono will print a stacktrace in the beagled terminal which may contain some more information. TIA. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
