After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 107496 - balsa loops after IMAP ping finds new message
balsa loops after IMAP ping finds new message
Status: RESOLVED DUPLICATE of bug 106311
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
2.2.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Pawel Salek
Depends on:
Blocks:
 
 
Reported: 2003-03-03 21:21 UTC by Lynn Kerby
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Lynn Kerby 2003-03-03 21:21:23 UTC 
I have seen balsa 2.0.9 loop twice today after it finds new message(s) in
my IMAP mailbox as a result of an IMAP "ping".  The new message count is
updated on screen, but the mailbox index window (which was left at the
bottom of the mailbox) doesn't scroll to see the new message. When the
"next unread" button is clicked, the message is displayed, but still no
scrolling of the mailbox index.  The scrollbar buttons can be used to scroll
the mailbox index.  Attempts to delete the newly received message(s) have
resulted in hangs.

I don't have a stack traceback to attach at the moment, but I'm pretty sure
I can reproduce this and add one if necesary.  The only balsa function I saw
on the stack was main(), everything else was related to gdk/gtk.  Many of the
functions on the stack seemed to be related to visibility updates.
Comment 1 Pawel Salek 2003-03-03 21:32:30 UTC 
Again, which gtk2 have you got? 2.2.1? It all looks like a set of
duplicate reports.
Comment 2 Lynn Kerby 2003-03-03 22:03:08 UTC 
Yes, my gtk+ is 2.2.1.  I did some searching through the bug list
prior to reporting, but didn't find anything that looked related
using loop or hang.  Sorry if this is/was a known problem.
Comment 3 Pawel Salek 2003-03-03 22:07:26 UTC 
Do not worry: it took me some digging and help from other people to
find out it truly was gtk2 problem.
Comment 4 Pawel Salek 2003-03-03 22:08:27 UTC 

*** This bug has been marked as a duplicate of 106311 ***
Comment 5 Lynn Kerby 2003-03-03 22:39:16 UTC 
I can confirm that the patch in the redhat bug report fixes the
problem as well.