Stacktrace: #0 0x00007f51cbc07d02 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 No symbol table info available. #1 0x00007f51cbc0b588 in ?? () from /lib/libglib-2.0.so.0 No symbol table info available. #2 0x00007f51cbc0b9e5 in g_main_loop_run () from /lib/libglib-2.0.so.0 No symbol table info available. #3 0x00007f51ccba90e7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #4 0x00000000004522bf in main (argc=2, argv=0x7fffc6cec838) at main.c:1334 lw = <value optimized out> path = <value optimized out> cmd_path = 0x0 cmd_file = 0x0 cmd_list = 0x0 collection_list = 0x0 first_collection = <value optimized out> bufl = <value optimized out>
In Karmic (uname: Linux 2.6.31-12-generic x86_64) the bug is triggered by setting gqview as the default image viewer and clicking an image, or using command-line like this: gqview -r image.jpg. The -r option forces any new image to load in an already existing gqview window. This worked fine in Jaunty, but fails in Karmic. (Note that -r is the default option for the menu-launcher.) As far as I can tell, the packages for Jaunty and Karmic are identical. I compiled from source (gcc 4.4.1-4ubuntu6, gqview_2.0.4.orig.tar.gz + gqview_2.0.4-5.diff.gz) and the crash went away. -- gqview crashed with SIGSEGV in g_main_context_dispatch() https://bugs.launchpad.net/bugs/424300 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs