| Bug ID |
10162
|
| Summary |
Gtk complaints when packet comments contain XML-like markup
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
wireshark 1.99.0 (v1.99.0-rc1-144-g90af86e from master)
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 GTK+ 2.24.22, with Cairo 1.13.1, with Pango 1.36.1, with
GLib 2.38.2, with libpcap, with libz 1.2.8, without POSIX capabilities, without
libnl, without SMI, with c-ares 1.10.0, with Lua 5.2, without Python, with
GnuTLS 3.1.24, with Gcrypt 1.5.3, without Kerberos, without GeoIP, without
PortAudio, with AirPcap.
Running on Linux 3.14.4-200.fc20.x86_64, with locale en_US.UTF-8, with libpcap
version 1.5.3, with libz 1.2.8, GnuTLS 3.1.24, Gcrypt 1.5.3, without AirPcap.
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
Built using gcc 4.8.2 20131212 (Red Hat 4.8.2-7).
--
I noticed Gtk-warnings coming out of my Wireshark:
~~~
Gtk-WARNING **: Failed to set text from markup due to error parsing markup:
Error on line 1 char 40: Element 'markup' was closed, but the currently open
element is 'none'
~~~
A little debugging indicates that the problem came from a packet comment which
had text like "hi there <bye>" in it. The stuff that looks vaguely like an XML
tag is what causes the warnings to pop out: removing it made the warnings go
away.
wireshark-qt does not exhibit the problem.
Not sure if this is worth fixing (and I don't have time to dig into it now) but
I wanted to document the problem nontheless.
How-to-repeat:
0) Start Wireshark from the command line
1) Open a file and select a packet
2) Right-click and add a Packet comment which includes "<something>" (including
the brackets but not the quotes)
3) observe the warning. Click around some other packets and come back to the
one with the comment and you'll see the warning some more.
You are receiving this mail because:
- You are watching all bug changes.