I have been having problems with Evolution grabbing my mouse related to clicking on mails, I think. I wouldn't call it a freeze, though... Eventually I usually could get it to go back (by clicking aimlessly on things that change the mouse coursor) but occasionally I'd have to do a killev.
--Ben On Sun, 2002-04-28 at 16:20, Not Zed wrote: > > Its pretty unlikely multiple threads are accessing gtk/etc, we know its > not thread safe, so are very careful about using it (as much a mess as > it makes of the code). > > Is anyone else experiencing this? I'm definetly not getting it (yet) - > I very infrequently update gtk/etc though. > > gdb seems to be playing up too, perhaps try cvs gdb? Not really sure > ... > > > On Mon, 2002-04-29 at 00:58, Xavier Bestel wrote: > > Le dim 28/04/2002 � 17:09, Owen Taylor a �crit : > > > > > > Xavier Bestel <[EMAIL PROTECTED]> writes: > > > > > > > Le dim 28/04/2002 � 16:23, Xavier Bestel a �crit : > > > > > Hi, > > > > > > > > > > since a few days, Evo freezes very very often. This happens when I click > > > > > (or select with keyboard) a mail in the list. Not always, not always the > > > > > same. > > > > > > > > > > I tried running gdb evolution-mail in a terminal, but it exited at the > > > > > freeze (Program exited). There were still evolution-mail threads > > > > > present, apparently all stuck in select() or so. > > > > > > > > Ok, galeon seems to have the same problem, less frequent. > > > > The common pattern is, when I attach gdb to the main (frozen) thread: > > > > they both freeze in a X function, like this: > > > > > > > > #0 0x4097a7ce in select () from /lib/libc.so.6 > > > > #1 0x40273fdc in _XlcPublicMethods () from /usr/X11R6/lib/libX11.so.6 > > > > #2 0x401cf3ba in _XRead () from /usr/X11R6/lib/libX11.so.6 > > > > #3 0x401cfdc3 in _XReply () from /usr/X11R6/lib/libX11.so.6 > > > > #4 0x401cba77 in XSync () from /usr/X11R6/lib/libX11.so.6 > > > > #5 0x40041150 in gdk_superwin_scroll () from /usr/lib/libgtksuperwin.so > > > > > > > > Not always the same function, but top 2 are always select() and > > > > _XlcPublicMethods() ... > > > > > > the _XlcPublicMethods thing is just an artifact of not having > > > symbols for Xlib. > > > > > > > now I'm a bit lost, who should I address that report to ? > > > > > > I'd have to guess it's an evolution bug; it's trying to use GDK from > > > multiple threads without locking, and thats' corrupting X lib > > > internals. (Probably the user from multiple threads is accidental) > > > > I don't think so, because it happened suddenly both for galeon and > > evolution. I suspect an underlying common package (e.g. gtk+, gdk or X) > > to be the cause. Unfortunately I don't know which ones have been updated > > lately. > > > > Xav > > > > > > > > _______________________________________________ > > evolution maillist - [EMAIL PROTECTED] > > http://lists.ximian.com/mailman/listinfo/evolution > > > _______________________________________________ > evolution maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/evolution >
signature.asc
Description: This is a digitally signed message part
