Bug 105358 – ethereal 0.10.12 with GTK+ 2.6.7, GLib 2.6.4 doesn't allow to scroll in results sometimes.

• Product: Gentoo Linux
• Status: RESOLVED TEST-REQUEST

[Description Clock 2005-09-09 04:01:59 UTC]

See the attached screenshot. If the list of packets is long, the scrollbar fills
out the whole scrollbar space instead being just tiny. This prevents the user
from scrolling in the results.

When the boundary between packet listing window and it's lower neighbour window
is drageed, the scrollbar resets into correct function.

I don't know if this is not a result of Gentoo compiling Ethereal with
wrong GTK version, or applying unauthorized patches. I already reported one bug
of Linux kernel to LKML and they fucked me off because Gentoo applied
unauthorized console background patch. So I am reporting here and not to
Ethereal people.

If you are sure it's bug of Ethereal and not gentoo, please change the status to
upstream *and* report the bug to Ethereal folks. Thanks.

ethereal 0.10.12

Compiled with GTK+ 2.6.7, with GLib 2.6.4, with libpcap 0.8.3, with libz 1.2.3,
with libpcre 5.0, without UCD-SNMP or Net-SNMP, without ADNS.

Running with libpcap version 0.8.3 on Linux 2.6.13.


Reproducible: Always
Steps to Reproduce:
1. Rin Ethereal
2. Capture large amount of packets I don't know how large
3.

Actual Results:  
Can't scroll in the packets

Expected Results:  
Can scroll in the packets

Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130,
glibc-2.3.5-r1, 2.6.13 i686)
=================================================================
System uname: 2.6.13 i686 Intel(R) Pentium(R) M processor 1.50GHz
Gentoo Base System version 1.6.13
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -mcpu=i686 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS=""
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X aac aalib alsa apm arts avi berkdb bitmap-fonts cdr crypt cups curl
dga divx4linux dri dv dvd dvdread eds emboss encode esd exif fam ffmpeg fftw
flac flash foomatic foomaticdb fortran ftp gd gdbm gif glut gnome gpm gstreamer
gtk gtk2 guile icq imagemagick imap imlib ipv6 jabber jack java javascript jpeg
kde ldap libcaca libg++ libwww live matroska mikmod ming mmap mmx mng motif
mozilla mp3 mpeg mysql nas ncurses nls ogg oggvorbis opengl oss pam pdflib perl
php png python qt quicktime readline real ruby samba sdl sharedmem shorten slang
socks5 speex spell sse ssl svg svga tcltk tcpd tetex theora threads tiff tls
truetype truetype-fonts type1-fonts unicode vorbis wifi win32codecs wmf xine
xinerama xml xml2 xmms xpm xv xvid zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY

[Comment 1 Clock 2005-09-09 04:03:04 UTC]

Created attachment 67999 [details]
Screenshot when the problem manifests

[Comment 2 Aldo "xoen" Giambelluca 2005-11-18 11:32:13 UTC]

Hi, GTK+ 2.6.10 and GLib 2.6.5 are stable (on x86 and amd64), have you installed?

Have you the same problems with these versions of GTK+/Glib? If no this bug can
be closed.

[Comment 3 Jakub Moc (RETIRED) 2005-12-01 08:33:20 UTC]

This bug is awaiting response from reporter, see comment #2.