do you happen to be using fedora or something? there's a bugzilla entry in bugzilla.redhat.com about this (it seems several programs are getting hit by this bug)
Jeff
On Fri, 2004-04-16 at 11:13 -0400, Patrick O'Callaghan wrote:
You asked for it :-) I attach 2 traces. I may be out of line sending these to the list. If so, sorry, but I did report the first of them via Bugzilla a couple of days ago and never got the usual ACK. Remember that these are against 1.5.5 (despite the Subject line), anon CVS as of 3 days ago. poc On Sun, 2004-04-04 at 09:00, Not Zed wrote: > Make sure its the absolute latest cvs. Note that anoncvs hasn't been > updating for a few days and doesn't include some fixes for this exact > issue. > > And we need a call backtrace, which you get from gdb, not a system call > trace, in order to debug the problem. > > I doubt switching desktops has anything to do with it other than it > being a coincidence. > > > On Fri, 2004-04-02 at 14:55 -0400, Patrick O'Callaghan wrote: > > I just submitted a similar report against 1.5.5 (compiled > > from anon CVS). It also freezes a lot if I switch desktops > > under KDE 3.2. Seems to correlate with Evo doing something > > slow and network-related, like fetching mail, while not > > on the current desktop. I did an "strace -p <pid>" on the > > Evo shell and got > > > > futex(0x85f7984, FUTEX_WAIT, 15, NULL <unfinished ...> > > > > if that means anything to anybody. > > > > Only a --force-shutdown and bonobo-slay will fix it. > > > > Fedora RC1, KDE 3.2 > > > > poc > > > > On Fri, 2004-04-02 at 13:35 -0500, Jeffrey Stedfast wrote: > > > Don't bother submitting a bug report unless it is eproducable on 1.5 > > > (it is extremely unlikely that we will be touching the 1.4 codebase > > > ever again) > > > > > > Jeff > > > > > > On Fri, 2004-04-02 at 12:01 -0600, Thomas F. O'Connell wrote: > > > > I've got two situations that frequently cause Evo 1.4.6 to hang: > > > > > > > > 1. When viewing a folder in which I have not yet disabled the preview > > > > pane, if I try to disable it using Alt-V P (I.e., View->Preview Pane), > > > > Evolution locks up. Once I force shutdown, I can enter the same folder > > > > and accomplish this successfully, but on the first try, it locks up. > > > > > > > > 2. If I leave Evolution running for long periods of time (say, the > > > > duration of a business day), when I quit, Evolution will lock up. > > > > > > > > One interesting point about this was that when I was still using > > > > Slackware 9.0, I didn't have this problem. I've had it with both > > > > Evolution 1.4.5 and 1.4.6 since upgrading. > > > > > > > > I've tried running with CAMEL_VERBOSE_DEBUG=1, and I don't see anything > > > > indicative of a problem. > > > > > > > > I'm running Slackware 9.1 for ix86. I have one account which accesses an > > > > Exchange server and one that accesses Courier-IMAP. > > > > > > > > If the developers have any suggestions for providing more output, I'd be > > > > happy to oblige. > > > > > > > > Should I file a bug report for each case? I didn't see any that matched > > > > my scenarios. > > > > > > > > -tfo > > > > > > > > _______________________________________________ > > > > evolution maillist - [EMAIL PROTECTED] > > > > http://lists.ximian.com/mailman/listinfo/evolution > > > > > > > > _______________________________________________ > > evolution maillist - [EMAIL PROTECTED] > > http://lists.ximian.com/mailman/listinfo/evolution > > _______________________________________________ > evolution maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/evolution
