https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3640
--- Comment #8 from Jim Young <jyoung@xxxxxxx> 2009-10-12 21:39:01 PDT ---
Hello Stig,
With SVN 30553 I think things have changed for the better but there are still
some issues.
I'm currently unable to crash on Linux, but I can reliably trigger a
Gtk-CRITICAL error (see detailed steps to replicate below).
I also occasionally trigger a crash on Windows but I haven't determined the
steps necessary to replicate the crashes.
I think the the Gtk-CRITICAL messages is related to having different numbers of
columns in the various profiles and/or perhaps that the column.width is not
fetched (or stored) from/to the proper "recent" file when switching between
profiles.
I have this hunch about "column.width" having an issue because when I start
Wireshark with a profile with only only two columns (Num and Time) the Time
column assumes a very wide value (the remainder of the width of the window).
If I then select the Default profile (with 6 columns), exit and then restart
Wireshark (now using the Default profile), and then open up a capture the Time
column will still have the extremely wide width it had assumed from the
previous two column profile.
On Linux I can reliably trigger this Gtk-CRITICAL message:
> (lt-wireshark:9803): Gtk-CRITICAL **: gtk_tree_view_column_get_width: assertion `GTK_IS_TREE_VIEW_COLUMN (tree_column)' failed
I use the following steps to trigger the message above:
1) On Linux, Startup Wireshark
2) Open up "Edit | Configuration Profiles..." dialog.
3) Click on "New"
4) Click on "Ok"
5) Open up "Edit | Preferences..." dialog.
6) Confirm that the title bar indicates that you are editing "New profile".
7) Click on "Columns" to open the Columns edit page
8) Click on the "Info" Column entry
9) Click "Remove" to delete the "Info" column entry
10) Click "Remove" to delete the "Protocol" column entry
11) Click "Remove" to delete the "Destination" column entry
12) Click "Remove" to delete the "Source" column entry
13) Click "Ok" to accept, save and close the Preferences dialog.
14) Exit Wireshark
15) Restart Wireshark
16) Click on the Profile Selector located on the bottom right hand corner of
the Wireshark Window (where its says "Profile: New profile").
17) Click on "Default" to switch the current profile from "New profile".
18) Click on the Profile Selector a second time.
17) Click on "New profile" to switch the current profile from "Default".
This second profile change (Step 17) from the Default profile (with six
columns) back to the "New profile" (with only two columns) will trigger four of
the "Gtk-CRITICAL" messages reported above.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.