I tested on Debian Sid, but I didn't get a similar segfault there. It
looks like this might somehow be an Ubuntu-specific issue.

I've attached a stacktrace from gdb (on Ubuntu 16.10):
Thread 1 "gmrun" received signal SIGSEGV, Segmentation fault.
0x00007ffff72b67f9 in g_type_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
(gdb) bt
#0  0x00007ffff72b67f9 in g_type_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#1  0x00007ffff79ccaa4 in gtk_type_new () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#2  0x000055555555a425 in ?? ()
#3  0x0000555555558b03 in ?? ()
#4  0x00007ffff641f3f1 in __libc_start_main (main=0x555555558890, argc=1, 
argv=0x7fffffffdfa8, init=<optimized out>, fini=<optimized out>, 
    rtld_fini=<optimized out>, stack_end=0x7fffffffdf98) at 
../csu/libc-start.c:291
#5  0x0000555555559289 in ?? ()

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633505

Title:
  gmrun gets a segment fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gmrun/+bug/1633505/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to