https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3483
Summary: Wireshark start-up very slow when X forwarding over ssh
Product: Wireshark
Version: 1.0.6
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Medium
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: spoyarek@xxxxxxxxxx
Created an attachment (id=3029)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3029)
Reduce splash update frequency if wireshark is invoked remotely
Build Information:
wireshark 1.0.6
Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled with GTK+ 2.10.4, with GLib 2.12.3, with libpcap 0.9.4, with libz
1.2.3, with POSIX capabilities (Linux), with libpcre 6.6, with SMI 0.4.5,
without ADNS, without Lua, with GnuTLS 1.4.1, with Gcrypt 1.2.4, with MIT
Kerberos, without PortAudio, without AirPcap.
Running on Linux 2.6.18-128.1.6.el5xen, with libpcap version 0.9.4.
Built using gcc 4.1.2 20080704 (Red Hat 4.1.2-44).
--
The wireshark splash screen update seems to be taking a lot of time when it is
invoked over an ssh forwarded X connection. I've included two patches to remedy
this since I felt it could be done on one of these two ways:
1) wireshark-conditionally-reduce-splash-update.patch: To set update interval
depending upon whether we're on a local X server or a remote one. I've
considered ":x.y" as local and everything else as remote. It seemed like the
best way since checking $SSH_CONNECTION limited the patch only to secure remote
connections over slower internet tubes and XShmQueryExtension() is not really
reliable for this. I got the latter hint from here:
http://www.mail-archive.com/wireshark-dev@xxxxxxxxxxxxx/msg13153.html
2) wireshark-reduce-splash-update.patch: Increase the update interval to 1
second
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
