forwarded 709981 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8604
tags 709981 confirmed upstream moreinfo
thanks

Hi Philipp,

Could you please send me the capture file triggering the issue?

Thanks,
Balint

2013/5/27 Ph. Marek <[email protected]>:
> Package: wireshark
> Version: 1.10.0~rc2-1
> Severity: normal
>
> Starting wireshark with a just-saved capture file (taken with debian
"TShark
> 1.8.6") aborts.
>
> $ file capture
> tcpdump capture file (little-endian) - version 2.4 (Linux "cooked",
capture
> length 65535)
>
>
> starting via GDB gives this backtrace:
>
>
Gtk:ERROR:/tmp/buildd/gtk+3.0-3.8.2/./gtk/gtkwidget.c:14133:gtk_widget_unregister_window:
> assertion failed: (user_data == widget)
>
> Program received signal SIGABRT, Aborted.
> 0x00007ffff124c295 in __GI_raise (sig=sig@entry=6) at
> .../nptl/sysdeps/unix/sysv/linux/raise.c:56
> 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht
> gefunden.
> (gdb) bt
> #0 0x00007ffff124c295 in __GI_raise (sig=sig@entry=6) at
> .../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1 0x00007ffff124f438 in __GI_abort () at abort.c:90
> #2 0x00007ffff1d61426 in g_assertion_message () from /lib/x86_64-linux-
> gnu/libglib-2.0.so.0
> #3 0x00007ffff1d61984 in g_assertion_message_expr () from
/lib/x86_64-linux-
> gnu/libglib-2.0.so.0
> #4 0x00007ffff3319ad6 in gtk_widget_unregister_window () from
/usr/lib/x86_64
> -linux-gnu/libgtk-3.so.0
> #5 0x00007ffff3319bbc in ?? () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #6 0x00007ffff220681b in ?? () from /usr/lib/x86_64-linux-
> gnu/libgobject-2.0.so.0
> #7 0x00007ffff221f2b6 in g_signal_emit_valist () from
/usr/lib/x86_64-linux-
> gnu/libgobject-2.0.so.0
> #8 0x00007ffff221ff82 in g_signal_emit () from /usr/lib/x86_64-linux-
> gnu/libgobject-2.0.so.0
> #9 0x00007ffff331ac71 in gtk_widget_unrealize () from
/usr/lib/x86_64-linux-
> gnu/libgtk-3.so.0
> #10 0x00007ffff324df6e in ?? () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #11 0x00007ffff3319be1 in ?? () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #12 0x00007ffff22068e7 in ?? () from /usr/lib/x86_64-linux-
> gnu/libgobject-2.0.so.0
> #13 0x00007ffff221f2b6 in g_signal_emit_valist () from
/usr/lib/x86_64-linux-
> gnu/libgobject-2.0.so.0
> #14 0x00007ffff221ff82 in g_signal_emit () from /usr/lib/x86_64-linux-
> gnu/libgobject-2.0.so.0
> #15 0x00007ffff331ac71 in gtk_widget_unrealize () from
/usr/lib/x86_64-linux-
> gnu/libgtk-3.so.0
> #16 0x00007ffff331efa5 in gtk_widget_unparent () from
/usr/lib/x86_64-linux-
> gnu/libgtk-3.so.0
> #17 0x00007ffff320d639 in ?? () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #18 0x00007ffff2209a94 in g_cclosure_marshal_VOID__OBJECTv () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #19 0x00007ffff22068e7 in ?? () from /usr/lib/x86_64-linux-
> gnu/libgobject-2.0.so.0
> #20 0x00007ffff221f2b6 in g_signal_emit_valist () from
/usr/lib/x86_64-linux-
> gnu/libgobject-2.0.so.0
> #21 0x00007ffff221ff82 in g_signal_emit () from /usr/lib/x86_64-linux-
> gnu/libgobject-2.0.so.0
> #22 0x00005555555e50a5 in _start ()
>
>
> Perhaps related to https://bugs.launchpad.net/ubuntu-gnome/+bug/1176334
> Updating libgtk2.0-0 (and related) to 2.24.18-1 doesn't help.
>
>
>
> -- System Information:
> Debian Release: jessie/sid
> APT prefers testing
> APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages wireshark depends on:
> ii libc6 2.17-3
> ii libcairo2 1.12.14-4
> ii libgdk-pixbuf2.0-0 2.28.1-1
> ii libglib2.0-0 2.36.1-2build1
> ii libgtk-3-0 3.8.2-1
> ii libpango-1.0-0 1.32.5-5
> ii libpangocairo-1.0-0 1.32.5-5
> ii libpcap0.8 1.3.0-1
> ii libportaudio2 19+svn20111121-1
> ii libwireshark3 1.10.0~rc2-1
> ii libwiretap3 1.10.0~rc2-1
> ii libwsutil2 1.10.0~rc2-1
> ii wireshark-common 1.10.0~rc2-1
> ii zlib1g 1:1.2.8.dfsg-1
>
> wireshark recommends no packages.
>
> wireshark suggests no packages.
>
> -- no debconf information

Reply via email to