Comment 3 for bug 1650666

Revision history for this message
Ivo Wever (ivo-wever) wrote :

Just upgraded to Zesty. Experiencing what seems to be this exact problem.

$ gdb -silent --args gvim -f -u /dev/null -U /dev/null --noplugin
Reading symbols from gvim...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/gvim -f -u /dev/null -U /dev/null --noplugin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe94cd700 (LWP 22840)]
[New Thread 0x7fffe8ccc700 (LWP 22841)]
[New Thread 0x7fffe3fff700 (LWP 22842)]
[New Thread 0x7fffe0f29700 (LWP 22843)]
[New Thread 0x7fffd6582700 (LWP 22844)]
[New Thread 0x7fffd5d81700 (LWP 22845)]
[New Thread 0x7fffd5580700 (LWP 22847)]
[Thread 0x7fffd5580700 (LWP 22847) exited]
[Thread 0x7fffe0f29700 (LWP 22843) exited]
[Thread 0x7fffd6582700 (LWP 22844) exited]
[Thread 0x7fffd5d81700 (LWP 22845) exited]

(gvim:22836): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <= (gint)rarray->len' failed

** (gvim:22836): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed

** (gvim:22836): CRITICAL **: unity_gtk_menu_item_get_child_shell: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed

** (gvim:22836): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed

** (gvim:22836): CRITICAL **: unity_gtk_menu_item_get_label: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed

** (gvim:22836): CRITICAL **: unity_gtk_menu_item_get_icon: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed

Thread 1 "gvim" received signal SIGSEGV, Segmentation fault.
0x00007fffe96e2083 in ?? () from /usr/lib/x86_64-linux-gnu/libunity-gtk3-parser.so.0