| Bug ID |
10272
|
| Summary |
Propose enhancing how Wireshark reads preferences/recent files to be linefeed/CR agnostic
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.8
|
| Hardware |
x86
|
| OS |
Mac OS X 10.4
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
TShark 1.10.8 (v1.10.8-2-g52a5244 from master-1.10)
Copyright 1998-2014 Gerald Combs <[email protected]> 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 (64-bit) with GLib 2.36.0, with libpcap, with libz 1.2.3, without
POSIX
capabilities, without libnl, with SMI 0.4.8, without c-ares, without ADNS, with
Lua 5.1, without Python, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT
Kerberos, with GeoIP.
Running on Mac OS X 10.9.4, build 13E28 (Darwin 13.3.0), with locale
en_US.UTF-8, with libpcap version 1.3.0 - Apple version 41, with libz 1.2.5.
Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
OBSERVED BEHAVIOR
When I zip up .wireshark from my Windows box and deploy it under Linux,
Wireshark works fine.
But when I do the same to an OS X box, Wireshark runs into trouble with
profiles. Examples:
* It resets the gui.* preferences files from TRUE to FALSE
gui.toolbar_main_show: FALSE
gui.filter_toolbar_show: FALSE
gui.wireless_toolbar_show: FALSE
gui.airpcap_driver_check_show: FALSE
gui.packet_list_show: FALSE
gui.tree_view_show: FALSE
gui.byte_view_show: FALSE
gui.statusbar_show: FALSE
gui.packet_list_colorize: FALSE
* It doesn't display customized columns (and will even comment them out
automagically, under circumstances which I haven't quite nailed down).
* It doesn't display custom Filters, even though they exist in preferences
WORKAROUND
If I convert the newly arrived ./wireshark/* files using dos2unix, everything
works fine.
DESIRED BEHAVIOR
Wireshark under OS X would be agnostic to line termination characters in
preferences & recent files, just as Wireshark under Linux is.
You are receiving this mail because:
- You are watching all bug changes.
