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 106311 - Infinite expose loops in GtkTreeView: gtk-2.2.1
Infinite expose loops in GtkTreeView: gtk-2.2.1
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
2.2.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
Pawel Salek
: 107432 107496 116798 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-02-17 14:33 UTC by Ariel Tankus
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ariel Tankus 2003-02-17 14:33:25 UTC
Version: 2.0.7.
Inbox: IMAP.
Configuration:  No preview pane.

When a new mail arrives at the Inbox IMAP mailbox, a message corretly
pops up the screen.  At the main window, however, I cannot see a new
message.  Untill now (2.0.7), whenever a new message arrived the scroll
bars moved a bit higher (i.e., were not at the lowest part of the bar,
due to the new mail).  Then I could scroll down, and see the line of the
new message.

The current phenomena are:
The scroll bar remains at the bottom of the bar as if I still see the last
message.  When I try and scroll the bar upward, it pulls up and down.
I keep moving the mouse (still pressed) upward, but the location of the bar
flips between the lowest and about half the bar size up, back and forth,
and does not follow the mouse curser.

The only way I found to see the new message is using the arrows.
One press of the Down arrow makes the scroll bars move a bit higher, as
if suddenly they are aware of the new mail.
The marker (blue) line that marked the last line now disappeared
(as if it is indeed on the new mail, but I can't see this, as the scroll
bars are in a position which shows only from the last old file).
Another press on the Down arrow makes the scroll bar go to the buttom of
the bar.  Now I can see the new message with the marker (blue) line on it.
From this point everything seems normal, until a new mail arrives.
Comment 1 Ariel Tankus 2003-02-23 10:40:37 UTC
The bug persist in 2.0.8.
Comment 2 mjotte 2003-02-27 20:39:30 UTC
I see the same problem with version 2.0.9 with a IMAP mailbox.

Balsa seems to go into an infinite loop when I receive new mail until
I hit the down arrow on my keyboard or switch to a different mailbox.
My cpu hits 100%. When I run balsa using strace the following lines
keep looping over and over after I receive mail:

gettimeofday({1046377990, 373190}, NULL) = 0
poll([{fd=5, events=POLLIN}, {fd=3, events=POLLIN}, {fd=7,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=12, events=POLLIN}, {fd=14,
events=POLLIN|POLLPRI}, {fd=15, events=POLLIN|POLLPRI}, {fd=16,
events=POLLIN|POLLPRI}, {fd=17, events=POLLIN|POLLPRI}], 9, 0) = 0
gettimeofday({1046377990, 373425}, NULL) = 0
write(9, "5\30\4\0{5 \1\354\0 \1X\3u\0017\1\6\0|5 \1{5 \1\4\0\1\0"...,
2040) = 2040
write(9, "\234\6\5\0}5
\1\0\0\0\0\2\0\21\0\31\0\23\0\234\27\n\0\003"..., 2032) = 2032
writev(9, [{"F\6\5\0{5 \1\10\0 \1\0\0%\0\35\0\25\0008\27\4\0\10\0
\1"..., 2044}, {"G\0P\0\337\0\23\0", 8}], 2) = 2052
write(9, "\234\27\20\0\0035 \1U\0 \1}5 \0016\0\0\0\3\0 \1\0\0\0\0"...,
2040) = 2040
write(9, "8\27\4\0\10\0 \1\0\0\10\0\0\0\0\0\234\6\5\0}5 \1\0\0\0"...,
2044) = 2044
writev(9, [{"8\27\4\0\2215 \1\4\0\0\0\356\356\356\0F\6\5\0{5
\1\221"..., 1484},
{"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024}],
2) = 2508
write(9, "\234\10\t\0\0035 \1\2245 \1\2255 \1}5 \1\0\0\0\0\0\0\0"...,
2044) = 2044
writev(9, [{"8\10\4\0\10\0 \1\0\0\10\0\0\0\0\0\234\6\5\0}5
\1\0\0\0"..., 2048}, {"\0\0\0\0X\3u\1", 8}], 2) = 2056
writev(9, [{"F\10\5\0{5 \1\10\0 \1/\3\f\1)\0\25\00085\4\0\10\0
\1\0"..., 1312},
{"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024}],
2) = 2336
write(9, "\234\10\t\0\0035 \1\2365 \1\2375 \1}5 \1\0\0\0\0\0\0\0"...,
2044) = 2044
write(9, "8\10\4\0\21\0 \1\0\0\10\0\0\0\0\0\234\6\5\0}5 \1\0\0\0"...,
472) = 472
read(9, "\1\2\215\203\0\0\0\0\2\0\340\1\0\0\0\0\4\0\0\0\0\0\0\0"...,
32) = 32
ioctl(9, 0x541b, [0])                   = 0
Comment 3 Pawel Salek 2003-02-27 20:47:25 UTC
I have seen that too but only with gtk-2.2. It looks like one of
idle/timeout functions keeps generating all the time update events, or
something. Which gtk have you got?
Comment 4 mjotte 2003-02-27 20:51:33 UTC
Yes, I'm using gtk-2.2 from the redhat "phoebe" beta:

> rpm -q gtk2 balsa
gtk2-2.2.1-1
balsa-2.0.9-1
Comment 5 Pawel Salek 2003-02-27 21:40:46 UTC
When I interrupt balsa, the stacktrace is:
  • #0 ??
  • #1 _XRead
    from /usr/X11R6/lib/libX11.so.6
  • #2 _XReply
    from /usr/X11R6/lib/libX11.so.6
  • #3 XQueryPointer
    from /usr/X11R6/lib/libX11.so.6
  • #4 _gdk_windowing_window_get_pointer
    from /usr/lib/libgdk-x11-2.0.so.0
  • #5 gdk_window_get_pointer
    from /usr/lib/libgdk-x11-2.0.so.0
  • #6 gtk_tree_view_get_type
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 gtk_widget_send_expose
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gdk_window_clear_area_e
    from /usr/lib/libgdk-x11-2.0.so.0
  • #16 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #17 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #18 g_timeout_add
    from /usr/lib/libglib-2.0.so.0
  • #19 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 main
    at main.c line 433
  • #25 __libc_start_main
    from /lib/tls/libc.so.6

1. Somebody knows a gtk expert to explain that?
2. Ariel, which gtk do you use?
Comment 6 Pawel Salek 2003-02-27 21:58:34 UTC
Cross-reported to redhat as
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=85317
Comment 7 Ariel Tankus 2003-02-28 07:59:56 UTC
I work with gtk version 2.2.1.
The Debian package I use is:

-----------------------
lap-humor /home/arielt/readings 7> dpkg --status libgtk2.0-0
Package: libgtk2.0-0
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 3544
Maintainer: Akira TAGOH <tagoh@debian.org>
Source: gtk+2.0
Version: 2.2.1-1
Replaces: libgtk2.0-0png3
Depends: libgtk2.0-common (>= 2.2.1-1), libatk1.0-0 (>= 1.2.2), libc6
(>= 2.3.1-1), libfontconfig1 (>= 2.1), libfreetype6 (>= 2.1.3-5),
libglib2.0-0 (>= 2.2.1), libjpeg62, libpango1.0-0 (>= 1.2.1),
libpng12-0, libtiff3g, libxft2 (>= 2.1), xlibs (>> 4.1.0), xlibs (>>
4.2.0), zlib1g (>= 1:1.1.4)
Conflicts: libgtk2.0-0png3 (<< 2.0.6-2), eog2 (<< 1.0.1-4),
gnome-panel2 (<< 2.0.4-1), celestia (<< 1.2.4-4), gimp1.3 (<<
1.3.7-1.1), metatheme (<< 0.9.7-3), libgnomeui-0 (<< 2.0.6-2),
gtk2.0-examples (<< 2.2.0), libgdkxft0
Description: The GTK+ graphical user interface library
 The GTK+ is a multi-platform toolkit for creating graphical user
 interfaces. Offering a complete set of widgets, the GTK+ is suitable
 for projects ranging from small one-off tools to complete application
 suites.
 .
 This package contains the shared libraries.
-----------------------
Comment 8 Pawel Salek 2003-02-28 08:26:30 UTC
FWIW, Jonathan Blandford's patch fixes that for me. Still, I reassign
the report to gtk+ module so the maintainer can close it when the
patch is in.
Comment 9 Pawel Salek 2003-03-03 22:08:25 UTC
*** Bug 107496 has been marked as a duplicate of this bug. ***
Comment 10 Elijah Newren 2003-03-05 17:28:08 UTC
*** Bug 107432 has been marked as a duplicate of this bug. ***
Comment 11 Frederic Crozat 2003-04-17 15:58:29 UTC
Committed on CVS on both gtk-2-2 and HEAD branch by jrb.

I'm not sure we should close this bug or not... Jonathan ?
Comment 12 Kristian Rietveld 2003-05-22 22:15:45 UTC
Looks like it was committed on Apr 17 2003.

Closing.
Comment 13 Pawel Salek 2003-07-22 22:28:28 UTC
*** Bug 116798 has been marked as a duplicate of this bug. ***