Bug#476610: [pkg-cli-apps-team] Bug#476610: Processed: reassign bug #476610 to package beagle

2008-04-20 Thread Mirco Bauer
tags 476610 + confirmed retitle 476610 beagle: stalling other GTK+ applications ($HOME/.beagle/socket returns EAGAIN) found 476610 0.3.5-1 thanks On Sun, 2008-04-20 at 08:29 -0400, D Bera wrote: Which version of beagle and libbeagle do you have ? Thanks, - dBera I can reproduce this bug

Bug#476610: [pkg-cli-apps-team] Bug#476610: Processed: reassign bug #476610 to package beagle

2008-04-20 Thread D Bera
I can reproduce this bug with the following versions: [EMAIL PROTECTED]:~$ dpkg -l beagle | grep ii ii beagle 0.3.5-1 indexing and search tool for your personal data [EMAIL PROTECTED]:~$ dpkg -l libbeagle1 | grep ii ii

Bug#476610: [pkg-cli-apps-team] Bug#476610: Processed: reassign bug #476610 to package beagle

2008-04-20 Thread Mirco Bauer
On Sun, 2008-04-20 at 11:50 -0400, D Bera wrote: connect(15, {sa_family=AF_FILE, path=/home/meebey/.beagle/socket}, 110) = -1 EAGAIN (Resource temporarily unavailable) It is strange that connect() is returning EAGAIN. Does the socket physically exist ? Yes the socket exist but is dead

Bug#476610: [pkg-cli-apps-team] Bug#476610: Processed: reassign bug #476610 to package beagle

2008-04-20 Thread D Bera
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: