[bugzilla-daemon@xxxxxxxxxxxxx]

Comment # 4 on bug 11400 from jean-christophe manciot

Yes, the behavior is a little different in both situations:
- the crash happens right away when dumpcap owner & group are NOT modified
(root:root)
- the Glib & GTK critical messages disappear when dumpcap owner & group ARE
modified (username:wireshark) and wireshark is launched with
"LIBOVERLAY_SCROLLBAR=0 wireshark". The crash happens when trying to start a
capture on an interface that is not denied to the user.

-----------------------------------------
When dumpcap owner & group are root:root:
-----------------------------------------
actionmystique@msi-ge60:~$ gdb wireshark
GNU gdb (Ubuntu 7.9-1ubuntu1) 7.9
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from wireshark...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/local/bin/wireshark 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe677f700 (LWP 8197)]
[New Thread 0x7fffe6f80700 (LWP 8196)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff138a425 in g_type_check_instance_is_fundamentally_a () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

(gdb) bt full
#0  0x00007ffff138a425 in g_type_check_instance_is_fundamentally_a ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#1  0x00007ffff136beae in g_object_ref () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#2  0x00007ffff108e07d in g_list_foreach () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3  0x00007ffff253ee01 in gtk_window_set_icon_list () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
No symbol table info available.
#4  0x00000000004416b0 in ?? ()
No symbol table info available.
#5  0x00007ffff13672d5 in g_closure_invoke () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#6  0x00007ffff137903c in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.                                                 
#7  0x00007ffff1381698 in g_signal_emit_valist () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0                 
No symbol table info available.                                                 
#8  0x00007ffff13818ff in g_signal_emit () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#9  0x00007ffff252f4ac in gtk_widget_realize () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
No symbol table info available.
#10 0x00000000004b9e6b in ?? ()
No symbol table info available.
#11 0x000000000042291a in ?? ()
No symbol table info available.
#12 0x00007ffff01eea40 in __libc_start_main (main=0x422510, argc=1,
argv=0x7fffffffde68, init=<optimized out>, 
    fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffde58)
at libc-start.c:289
        result = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 3430723780462007694,
4340544, 140737488346720, 0, 0, 
                -3430724486959442546, -3430756087587121778}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 
              0x521da0 <__libc_csu_init>, 0x7fffffffde68}, data = "" = 0x0,
cleanup = 0x0, 
              canceltype = 5381536}}}
        not_first_call = <optimized out>
#13 0x0000000000423b69 in _start ()
No symbol table info available.

---

      You are receiving this mail because:

• You are watching all bug changes.