Hi Peter, 2016-01-13 1:11 GMT+01:00 Peter Wu <pe...@lekensteyn.nl>: > On Sun, Jan 10, 2016 at 11:52:39AM +0100, Bálint Réczey wrote: >> Hi, >> >> 2016-01-09 16:40 GMT+01:00 Peter Wu <pe...@lekensteyn.nl>: >> > Hi Bernard, >> > >> > On Thu, Jan 07, 2016 at 12:31:12PM -0500, bernard ck Wong wrote: >> >> I have installed wireshark2.01 from the wireshark stable ppa on Wily (64 >> >> bit) and wireshark-gtk crashes immediately. The errors are in attachment. >> >> The package for vivid 64 bit works without issue though. >> >> >> >> I just compiled 2.01 from source and it didn't crash. >> > >> > Can you please post the outptu of: >> > >> > tshark -G currentprefs | grep gui.layout_type >> > >> > If it is "#gui.layout_type: 1" (or something in the range 1-6) and still >> > crashes, then maybe some memory is scribbled. Can you try to reproduce >> > the issue with a clean configuration? Example: >> > >> > HOME=/tmp/wshome wireshark >> I have reproduced the issue in a clean Wily VM. >> And did short triaging: >> >> #4 0x00005653770ef3e3 in main_widgets_rearrange () at >> /home/vagrant/wireshark-2.0.1+g59ea380/ui/gtk/main.c:3491 >> 3491 g_assert_not_reached(); >> (gdb) p prefs.gui_layout_type >> $1 = layout_unused >> >> Recompilation does not help and the preferences file is not created. >> >> The Qt version and tshark start fine. > > Can you try this fix (for master, but should be backported too): > https://code.wireshark.org/review/13154 > > It also means that somehow the gui.layout_type field was set to 0... But > the default on master-2.0 is: > > epan/prefs.c:3032: prefs.gui_layout_type = layout_type_5; > > Does Ubuntu include a default prefs file having gui.layout_type:0? Sorry for not posting here earlier, but the crash is fixed or at least shadowed by this commit: https://code.wireshark.org/review/#/c/13178/
You may want to revert it before testing other possible fixes. Cheers, Balint ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
