> > This has been reported by others too. Its a fatal crash in > > evolution-sharp. I believe you can disable/uninstall > > evolution-data-server backend to avoid the crash. > > Thank you very much for the investigation. > > So beagle crashes caused by the evolution-sharp binding problem. But > should that make other GTK+ applications that use the GTK+ file sector > for example hang? During a strace I noticed other applications try to > read ~/.beagle/socket which seems to block. > > IMHO this seems to be a beagle problem as it affects other software, > triggered by the beagle crash.
(1) Its a really really fatal crash in that I doubt beagle is even running after that crash. The unix socket ~/.beagle/socket it created was therefore not removed after the crash causing other apps to hang. (2) WIth libbeagle-0.3.4+, there should not be any hang when using gtk file selector. libbeagle now tries to open the socket in a non-blocking mode. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
