latest wireshark core dumps

[Daniel Braniss]

just a wild guess, but wireshark is also complaining about:

** (wireshark:79448): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-H8OvE4zmWb: No such file or directory


after many tries, there is a /var/tmp/dbus-xxxx but not the one requested,
does any one know how does this dbus-xxx appear? I ran dbus-launch, and
that seems to be reading correctly /var/db/dbus/machine-id
I am mentioning dbus, because last time there were issues, i did some magics with
dbus and wireshark stooped core-dumping… [the magic no longer works :-(

danny


> On Dec 16, 2014, at 8:56 AM, Daniel Braniss <danny at cs.huji.ac.il> wrote:
> 
> good to know it’s not a local issue!
> thanks!
> if it’s of any help:
> (gdb) bt
> #0  0x0000000809cff6d2 in g_type_check_instance_is_fundamentally_a (
>    type_instance=0x109e1860, fundamental_type=80) at gtype.c:3979
> #1  0x0000000809cdb43a in g_object_ref (_object=0x109e1860) at gobject.c:3041
> #2  0x0000000809f8523f in g_list_foreach (list=0x810aa3b80, 
>    func=0x809cdb410 <g_object_ref>, user_data=0x0) at glist.c:993
> #3  0x00000008082cd60d in gtk_window_set_icon_list (window=0x810946230, 
>    list=0x810aa3b80) at gtkwindow.c:4456
> #4  0x00000000004445b6 in _start ()
> #5  0x0000000809cd548c in g_cclosure_marshal_VOID__VOID (closure=0x810962300, 
>    return_value=0x0, n_param_values=1, param_values=0x7fffffffdcd0, 
>    invocation_hint=0x7fffffffdc70, marshal_data=0x0) at gmarshal.c:85
> #6  0x0000000809cd107a in g_closure_invoke (closure=0x810962300, 
>    return_value=0x0, n_param_values=1, param_values=0x7fffffffdcd0, 
>    invocation_hint=0x7fffffffdc70) at gclosure.c:768
> #7  0x0000000809cf4a3c in signal_emit_unlocked_R (node=0x81084ea60, detail=0, 
>    instance=0x810946230, emission_return=0x0, 
>    instance_and_params=0x7fffffffdcd0) at gsignal.c:3553
> #8  0x0000000809cf66b9 in g_signal_emit_valist (instance=0x810946230, 
>    signal_id=8, detail=0, var_args=0x7fffffffe410) at gsignal.c:3309
> #9  0x0000000809cf700f in g_signal_emit (instance=0x810946230, signal_id=8, 
>    detail=0) at gsignal.c:3365
> #10 0x00000008082a2b86 in gtk_widget_realize (widget=0x810946230)
>    at gtkwidget.c:5508
> ---Type <return> to continue, or q <return> to quit---
> #11 0x00000000004c1e55 in _start ()
> #12 0x00000000004478e2 in _start ()
> #13 0x000000000042463f in _start ()
> #14 0x0000000800811000 in ?? ()
> #15 0x0000000000000000 in ?? ()
> 
>> On Dec 16, 2014, at 1:54 AM, Dutch Ingraham <stoa at gmx.us> wrote:
>> 
>> On 12/13/14 06:11, Daniel Braniss wrote:
>>> hi all,
>>> I just compiled from ports wireshark et.all on a virgin 10.1-stable,
>>> and it’c coredumping on startup, any hints?
>>> 
>>> thanks,
>>> 	danny
>>> 
>>> _______________________________________________
>>> freebsd-hackers at freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
>>> 
>> A few of us are having the same problem.[1],[2],[3]  Working on it.
>> 
>> [1]https://forums.freebsd.org/threads/wireshark-install.49487/
>> [2]http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+current/freebsd-questions
>> [3]bug #195980
>> _______________________________________________
>> freebsd-hackers at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
> 
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"