Wireshark crashes with segmentation fault after trying to do any functionality with it

This issue was migrated from bug 7280 in our old bug tracker.

Original bug information:

Reporter: Prafulla
Status: RESOLVED NOTABUG
Product: Wireshark
Component: GTK+ UI
OS: Fedora
Platform: x86
Version: 1.6.7

Prafulla said:

Build Information:

1.6.7 - built on fedora 4 ( 2.6.11-1.1369_FC4smp) with gtk+ 3.4 glib 2.32.3

Wireshark crashes with segmentation fault after trying to do any functionality with it like open a file, clicking on About in help , any operation for that matter. It crashes with segmentation fault:

Here is the gdb output:

[root@fw9500CP_lin01 wireshark-1.6.7]# libtool --mode=execute gdb wireshark
./wireshark: line 61: Xwireshark: command not found
GNU gdb Red Hat Linux (6.3.0.0-1.21rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /home/ppalwe/wireshark-1.6.7/.libs/lt-wireshark
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0xbbe000
[Thread debugging using libthread_db enabled]
[New Thread -1208908096 (LWP 16400)]
Detaching after fork from child process 16593.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208908096 (LWP 16400)]
0x0041cd83 in gtk_range_get_adjustment () from /usr/lib/libgtk-x11-2.0.so.0
(gdb) where
#0  0x0041cd83 in gtk_range_get_adjustment () from /usr/lib/libgtk-x11-2.0.so.0
#1  0x0041cf5d in gtk_range_get_adjustment () from /usr/lib/libgtk-x11-2.0.so.0
#2  0x0041f025 in gtk_range_get_adjustment () from /usr/lib/libgtk-x11-2.0.so.0
#3  0x004abc44 in gtk_tree_view_set_fixed_height_mode ()
   from /usr/lib/libgtk-x11-2.0.so.0
#4  0x003ef567 in gtk_marshal_VOID__UINT_STRING ()
   from /usr/lib/libgtk-x11-2.0.so.0
#5  0x00139ed8 in g_closure_invoke (closure=0x9687248, return_value=0x0,
    n_param_values=3, param_values=0xbfe323d0, invocation_hint=0xbfe3236c)
    at gclosure.c:777
#6  0x00148c6d in signal_emit_unlocked_R (node=0x954d398, detail=0,
    instance=0x964a950, emission_return=0x0, instance_and_params=0xbfe323d0)
    at gsignal.c:3547
#7  0x00149ef8 in g_signal_emit_valist (instance=0x964a950, signal_id=134,
    detail=0, var_args=Variable "var_args" is not available.
) at gsignal.c:3296
#8  0x0014a1d8 in g_signal_emit (instance=0x964a950, signal_id=134, detail=0)
    at gsignal.c:3352
#9  0x004941f0 in gtk_tree_model_row_inserted ()
   from /usr/lib/libgtk-x11-2.0.so.0
#10 0x003e870f in gtk_list_store_insert () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x003e89e1 in gtk_list_store_append () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x08086c15 in simple_list_append (list=0x8c4b2b8) at gui_utils.c:1072
#13 0x080f9059 in about_folders_row (table=Variable "table" is not available.
) at about_dlg.c:376

added crash osfedora uigtk version1.6 labels

Jeff Morriss said:

(In reply to comment #‍0)
> Build Information:
> 1.6.7 - built on fedora 4 ( 2.6.11-1.1369_FC4smp) with gtk+ 3.4 glib 2.32.3

Do you really mean Fedora 4? Fedora 4 is ancient (current is 16 IIRC), but the above says you've got a modern GTK+ and glib. I suppose your kernel version could really be FC4.

Note that GTK+ 3 support in 1.6 is probably experimental at best--you should probably be using GTK+ 2. (I think GTK+ 3 is stable in trunk, but it took a bunch of development to get it there; should we disable it in trunk-1.6?)

Prafulla said:

(In reply to comment #1)  
> (In reply to comment #0)  
> > Build Information:  
> > 1.6.7 - built on fedora 4 ( 2.6.11-1.1369_FC4smp) with gtk+ 3.4 glib 2.32.3  
>  
> Do you really mean Fedora 4?  Fedora 4 is ancient (current is 16 IIRC), but the  
> above says you've got a modern GTK+ and glib.  I suppose your kernel version  
> could really be FC4.  
>  
> Note that GTK+ 3 support in 1.6 is probably experimental at best--you should  
> probably be using GTK+ 2.  (I think GTK+ 3 is stable in trunk, but it took a  
> bunch of development to get it there; should we disable it in trunk-1.6?)  



Which GTK+ 2 version looks OK to try?
I will try gtk+ 2.24.0 and check.

Thanks

Jeff Morriss said:

(In reply to comment #2)  
> (In reply to comment #1)  
> > (In reply to comment #0)  
> > > Build Information:  
> > > 1.6.7 - built on fedora 4 ( 2.6.11-1.1369_FC4smp) with gtk+ 3.4 glib 2.32.3  
> >  
> > Do you really mean Fedora 4?  Fedora 4 is ancient (current is 16 IIRC), but the  
> > above says you've got a modern GTK+ and glib.  I suppose your kernel version  
> > could really be FC4.  
> >  
> > Note that GTK+ 3 support in 1.6 is probably experimental at best--you should  
> > probably be using GTK+ 2.  (I think GTK+ 3 is stable in trunk, but it took a  
> > bunch of development to get it there; should we disable it in trunk-1.6?)  
>  
>  
>  
> Which GTK+ 2 version looks OK to try?  
> I will try gtk+ 2.24.0 and check.  

1.6.x requires GTK+ 2.4 or later.  2.24.0 should be fine.

Prafulla said:

(In reply to comment #3)  
> (In reply to comment #2)  
> > (In reply to comment #1)  
> > > (In reply to comment #0)  
> > > > Build Information:  
> > > > 1.6.7 - built on fedora 4 ( 2.6.11-1.1369_FC4smp) with gtk+ 3.4 glib 2.32.3  
> > >  
> > > Do you really mean Fedora 4?  Fedora 4 is ancient (current is 16 IIRC), but the  
> > > above says you've got a modern GTK+ and glib.  I suppose your kernel version  
> > > could really be FC4.  
> > >  
> > > Note that GTK+ 3 support in 1.6 is probably experimental at best--you should  
> > > probably be using GTK+ 2.  (I think GTK+ 3 is stable in trunk, but it took a  
> > > bunch of development to get it there; should we disable it in trunk-1.6?)  
> >  
> >  
> >  
> > Which GTK+ 2 version looks OK to try?  
> > I will try gtk+ 2.24.0 and check.  
>  
> 1.6.x requires GTK+ 2.4 or later.  2.24.0 should be fine.  


Thanks,
I tried with gtk+ 2.24.0 and it seems to be working and fixed this issue of crashing.
But it induced another issue.

Now I do not see any text on GUI when I launch wireshark, only the boxes are displayed and there is no text associated with these boxes and its hard to navigate.


What could have caused this missing texts?

Jeff Morriss said:

(In reply to comment #4)  
> Now I do not see any text on GUI when I launch wireshark, only the boxes are  
> displayed and there is no text associated with these boxes and its hard to  
> navigate.  
>  
> What could have caused this missing texts?  

I think usually this indicates a font installation problem.

Anyway, it looks like Wireshark is OK here, so closing this.

Jeff Morriss said:

Also: I disabled GTK3 support in the 1.6 trunk in r42852 so others don't run into the same trouble you did.

closed