Wireshark-bugs: [Wireshark-bugs] [Bug 8705] New: "No such preference" warnings are displayed for
Date: Tue, 21 May 2013 19:30:33 +0000
Bug ID 8705
Summary "No such preference" warnings are displayed for 5 obsolete and 1 platform-specific preference
Classification Unclassified
Product Wireshark
Version 1.11.x (Experimental)
Hardware All
OS All
Status UNCONFIRMED
Severity Normal
Priority Medium
Component Wireshark
Assignee bugzilla-admin@wireshark.org
Reporter turney_cal@emc.com
Attachment #10818 Flags review_for_checkin?

Created attachment 10818 [details]
Patch that addresses all these issues

Build Information:
Version 1.11.0-dev (SVN Rev Unknown from unknown)

Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> 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 (32-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built May 20 2013), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Xeon(R) CPU           E5507  @ 2.27GHz, with 4093MB of physical
memory.

Built using Microsoft Visual C++ 10.0 build 40219

----------------------------


--
"No such preference" warnings are displayed for 5 obsolete and 1
platform-specific preference:  In set_pref()of prefs.c (lines 3824-3833)
'stream.client.<fg/bg>' and 'stream.server.<fg/bg>' should be compared with
'dotp' without the 'stream.' prefix. In addition,
'taps.rtp_player_max_visible', 'client.bg' and 'server.bg' should be compared
with 'dotp' rather than 'value'. This warning is also displayed on WIN32/64
platforms for the "print.command" pref because it is not valid on those
platforms (see 'read_prefs_file()' in prefs.c, line 3023).


You are receiving this mail because:
  • You are watching all bug changes.