This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 1 and 32 (spanning 31 versions)
Revision 1 as of 2005-01-21 21:13:06
Size: 3361
Editor: UlfLamping
Comment: this page isn't developer specific
Revision 32 as of 2007-09-06 19:00:24
Size: 3518
Editor: UlfLamping
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
The following is a list of known and confirmed bugs. == On bug reporting ==
Line 5: Line 5:
As people often consider intended behaviour to be a bug, '''please do not put anything on this list if you haven't already asked the developer mailing list about it. If you ask the developer list, they'll see it immediately, and: /!\ '''Please don't add new bugs here, ask the developer/user mailing lists or use our [http://bugs.wireshark.org/bugzilla/ bugzilla] for this purpose.'''
Line 7: Line 7:
 * if it's a bug, they might be able to fix it soon; For several reasons, a Wiki isn't a good way to handle bugs, e.g. how to ask questions to a new bug if no mail address was left.
Line 9: Line 9:
 * if it's not a bug, they can indicate so and say why it's not a bug.

If you don't ask the developer list, they won't see it until they look at this page, and they can't point out that it's not a bug if it isn't, and they can't discuss it as easily in order to come up with the correct fix if it is a bug.'''
New bugs added to this page will be deleted without further notice!
Line 17: Line 15:
 1. The horizontal scrollbar in the packet list pane wasn't completely removed. It does automatically appear if the content doesn't fit into the window. If you widen your columns to be larger than the pane, a scrollbar will appear.  1. The horizontal scrollbar in the packet list pane wasn't removed. It does automatically appear if the content doesn't fit into the window. If you widen your columns to be larger than the pane, a scrollbar will appear. You can also use View/Resize All Columns for this.
Line 19: Line 17:
== General/Unsorted bugs ==  1. Plugins are not portable between versions. Ever wondered why Wireshark keeps its plugins in a directory named after its version? That is because the plugin interface is considered an internal interface to Wireshark. Therefore it is not stable (as API and ABI) and can change with every version. So when moving from one version to the next you get a fresh install of plugins for this version. When using a 3rd party plugin, request a fresh build from the supplier.
Line 21: Line 19:
 * Ethereal will terminate if it runs out of memory (due to glib's g_malloc/g_free implementation). Currently no solution to this; note that many of the GLib facilities that Ethereal uses, such as G!HashTables, use g_malloc, so even if Ethereal were to use a different memory allocator, that wouldn't help if it continued to use those facilities.  1. The Wireshark Windows version (as well as some other windows software) won't work well with desktop theme software, e.g. making the windows desktop look like Mac OS X. Known problems are with Alienware's Windows theme (!AlienMorph(TM)?) not showing the packet list well.
Line 23: Line 21:
 1. Restore correct behavior of Save feature for followed TCP streams. This functionality has been broken since v10.5 when streams started being saved as ASCII only, preventing recovery of binary data from TCP streams (FTP data streams for example). - ''Chris Eagle''  1. ICMP packets appearing when filtering for other ip based protocols. Some ICMP packets sometimes contain the packet that "caused the error" and this is going to be dissected. if you dont want to have the frames that are icmp but contain udp use "{{{udp && ! icmp}}}" instead of "{{{udp}}}" as filter.
Line 25: Line 23:
== Capture file reading == == Running Out Of Memory -> Terminate ==
Line 27: Line 25:
  1. Time stamps in capture files from the Windows version of Sniffer are not always interpreted correctly. 0.10.9 should do a much better job of this, but it won't necessarily do a perfect job. If you have a problem with time stamps in Sniffer files in a release prior to 0.10.9, try it with 0.10.9. If you have a problem in 0.10.9, please give us a copy of a capture file with the problem, and a listing of what the time stamps on the packets '''should''' be, if possible. Wireshark will terminate if it runs out of memory. There's currently no solution to this, for details and workarounds see the /OutOfMemory page.
Line 29: Line 27:
== Fixed == == Packet List Vertical Scrollbar ==
Line 31: Line 29:
 * 0.10.7: Win32: Occasional GTK/GLib warnings, popping up a console window (e.g. if you put a Notebook in Standby). The GLib 2.4.7 seems to fix this problem, as the release notes state to not pop up a console window for GLib warnings. However, this is somewhat bogus, as the warnings should be fixed, instead of simply not showing them. The new lib is included since Ethereal 0.10.7. The vertical scrollbar of the packet list sometimes doesn't show up or is otherwise strange, due to a probable bug in the GTK+ toolkit. Simply resizing the Packet List (by moving the seperator bar) usually solves this problem.
Line 33: Line 31:
 * 0.10.7: Win32: ADNS warnings, if no DNS server is available. The release notes of ADNS release adns-1.0-win32-04.zip (at http://adns.jgaa.com/) state to fix this bug. The new lib is included since Ethereal 0.10.7. == Sniffer Time Stamps ==
Line 35: Line 33:
 * 0.10.9: Win32: Crashes on Windows 95/98/Me. This should now be fixed in 0.10.9. Time stamps in capture files from the Windows version of Sniffer are not always interpreted correctly.
Line 37: Line 35:
 * 0.10.9: The dissector for the DNP-3 protocol used in control systems often crashed. - ''Dan !McDonald (dan.mcdonald@austinenergy.com)'' This is fixed in 0.10.9. If you have a problem with time stamps in Sniffer files, try it with the latest Wireshark release. If you still have a problem with it, please add a new [http://bugs.wireshark.org/bugzilla/ bugzilla] bug and give us a copy of a capture file with the problem, and a listing of what the time stamps on the packets '''should''' be, if possible.

== Win32 only: white text color hard to read ==

If you use a 256 color display (e.g. for terminal services), the text color can be white on grey background which is hard to read.
Workaround: Use GTK1 variant while installation.

== Win32 only: Wireshark crashes at startup without any error message ==

This crash is due to a problem in the newly used libgcrypt in 0.99.3, a workaround is described in:

http://www.wireshark.org/lists/wireshark-users/200609/msg00105.html

== Win32 only: Saving to an already existing filename shows strange behaviour ==

Wireshark will ask you if you want to save to that file anyway, then asking a second time about it.

Workaround: Save to a different filename.
Line 40: Line 55:

 * As bugs are relevant for all users, not only developers, rename it to simply "KnownBugs" and put a link from the FrontPage to it might be a good idea. - ''Ulf Lamping'' (That's what I was thinking yesterday as well. I think we should move it to the top level. - ''Guy Harris'')

Known Bugs

On bug reporting

/!\ Please don't add new bugs here, ask the developer/user mailing lists or use our [http://bugs.wireshark.org/bugzilla/ bugzilla] for this purpose.

For several reasons, a Wiki isn't a good way to handle bugs, e.g. how to ask questions to a new bug if no mail address was left.

New bugs added to this page will be deleted without further notice!

Not a Bug

Things our users frequently notify as bugs, but which are intended behaviour.

  1. The horizontal scrollbar in the packet list pane wasn't removed. It does automatically appear if the content doesn't fit into the window. If you widen your columns to be larger than the pane, a scrollbar will appear. You can also use View/Resize All Columns for this.
  2. Plugins are not portable between versions. Ever wondered why Wireshark keeps its plugins in a directory named after its version? That is because the plugin interface is considered an internal interface to Wireshark. Therefore it is not stable (as API and ABI) and can change with every version. So when moving from one version to the next you get a fresh install of plugins for this version. When using a 3rd party plugin, request a fresh build from the supplier.
  3. The Wireshark Windows version (as well as some other windows software) won't work well with desktop theme software, e.g. making the windows desktop look like Mac OS X. Known problems are with Alienware's Windows theme (AlienMorph(TM)?) not showing the packet list well.

  4. ICMP packets appearing when filtering for other ip based protocols. Some ICMP packets sometimes contain the packet that "caused the error" and this is going to be dissected. if you dont want to have the frames that are icmp but contain udp use "udp && ! icmp" instead of "udp" as filter.

Running Out Of Memory -> Terminate

Wireshark will terminate if it runs out of memory. There's currently no solution to this, for details and workarounds see the /OutOfMemory page.

Packet List Vertical Scrollbar

The vertical scrollbar of the packet list sometimes doesn't show up or is otherwise strange, due to a probable bug in the GTK+ toolkit. Simply resizing the Packet List (by moving the seperator bar) usually solves this problem.

Sniffer Time Stamps

Time stamps in capture files from the Windows version of Sniffer are not always interpreted correctly.

If you have a problem with time stamps in Sniffer files, try it with the latest Wireshark release. If you still have a problem with it, please add a new [http://bugs.wireshark.org/bugzilla/ bugzilla] bug and give us a copy of a capture file with the problem, and a listing of what the time stamps on the packets should be, if possible.

Win32 only: white text color hard to read

If you use a 256 color display (e.g. for terminal services), the text color can be white on grey background which is hard to read. Workaround: Use GTK1 variant while installation.

Win32 only: Wireshark crashes at startup without any error message

This crash is due to a problem in the newly used libgcrypt in 0.99.3, a workaround is described in:

http://www.wireshark.org/lists/wireshark-users/200609/msg00105.html

Win32 only: Saving to an already existing filename shows strange behaviour

Wireshark will ask you if you want to save to that file anyway, then asking a second time about it.

Workaround: Save to a different filename.

Discussion

KnownBugs (last edited 2013-12-20 15:23:31 by ChristopherMaynard)