abrt 1.0.8 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/thunderbird-3.0/thunderbird-bin component: thunderbird executable: /usr/lib/thunderbird-3.0/thunderbird-bin kernel: 2.6.31.6-166_1.cubbi_tuxonice.fc12.i686 package: thunderbird-3.0.1-1.fc12 rating: 4 reason: Process /usr/lib/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1. start thunderbird 2. 3.
Created attachment 400959 [details] File: backtrace
How to reproduce ----- 1. start thunderbird 2. 3.
#3 <signal handler called> No symbol table info available. #4 0x00b95ba6 in IA__g_type_check_instance_cast (type_instance=0xb4e68b70, iface_type=3076181376) at gtype.c:3731 node = 0xb8000054 iface = <value optimized out> check = <value optimized out> #5 0x05ca0058 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #6 0x0598e698 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 No symbol table info available. #7 0x00a6a172 in g_idle_dispatch (source=<value optimized out>, callback=<value optimized out>, user_data=<value optimized out>) at gmain.c:4065 No locals. #8 0x00a6bf88 in g_main_dispatch (context=<value optimized out>) at gmain.c:1960 user_data = 0xb42c3f70 callback = 0x598e630 cb_data = <value optimized out> current_source_link = {data = 0xb42e0b40, next = 0x0} source = 0xb42e0b40 current = <value optimized out> i = <value optimized out> #9 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513 No locals. #10 0x00a6f8b8 in g_main_context_iterate (context=<value optimized out>, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591 max_priority = 115 timeout = 0 some_ready = 1 nfds = <value optimized out> allocated_nfds = <value optimized out> fds = <value optimized out> __PRETTY_FUNCTION__ = "g_main_context_iterate" -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 574680 has been marked as a duplicate of this bug. ***
Thank you for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 574369 ***