abrt 1.0.2 detected a crash. 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.9-174.fc12.i686 package: thunderbird-3.0-4.fc12 rating: 4 reason: Process was terminated by signal 6 (Aborted)
Created attachment 381324 [details] File: backtrace
#3 <signal handler called> No symbol table info available. #4 0x00a84416 in __kernel_vsyscall () No symbol table info available. #5 0x004efa91 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 resultvar = <value optimized out> resultvar = <value optimized out> pid = 6512628 selftid = 2259 #6 0x004f135a in abort () at abort.c:92 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0xffffffff, sa_sigaction = 0xffffffff}, sa_mask = {__val = {4294967280, 2966440864, 3220658416, 3220658656, 134540279, 134558588, 79, 78, 3220658416, 134545246, 6512628, 79, 3220658616, 5423362, 2967450960, 79, 3220658656, 2967450960, 0, 4222451712, 2967450960, 2967450960, 2967450960, 2967450960, 2967451038, 2967451060, 2967450960, 2967451060, 0, 0, 0, 0}}, sa_flags = 0, sa_restorer = 0x68} sigs = {__val = {32, 0 <repeats 31 times>}} #7 0x004e8be8 in __assert_fail (assertion=<value optimized out>, file=<value optimized out>, line=<value optimized out>, function=<value optimized out>) at assert.c:81 buf = 0xb0d04ba0 "thunderbird-bin: xcb_io.c:378: _XAllocID: Assertion `ret != inval_id' failed.\n" #8 0x00818c0a in _XAllocID (dpy=0xb744b000) at xcb_io.c:378 ret = 4294967295 __PRETTY_FUNCTION__ = "_XAllocID" #9 0x00af0c48 in XRenderCreatePicture (dpy=<value optimized out>, drawable=<value optimized out>, format=<value optimized out>, valuemask=<value optimized out>, attributes=<value optimized out>) at Picture.c:90 info = 0xb7450f10 pid = <value optimized out> #10 0x0023fc7a in _cairo_xlib_surface_ensure_src_picture ( surface=<value optimized out>) at cairo-xlib-surface.c:844 pa = {repeat = 2357422, alpha_map = 3220659160, alpha_x_origin = 0, alpha_y_origin = 0, clip_x_origin = 2343800, clip_y_origin = -1343408312, clip_mask = 3022438112, graphics_exposures = 1792, subwindow_mode = 1, poly_edge = -1272529184, poly_mode = 2, dither = 1, component_alpha = -1343408383} #11 _cairo_xlib_surface_set_attributes (surface=<value optimized out>) at cairo-xlib-surface.c:1414 status = <value optimized out> -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Reporter, this does not look like a duplicate that I can see, so let's get the information that we'll need to pass on to the developers, if you are willing. Could you perform the following commands and attach their output as files added to this bug? Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. First of all, could we get output of the command rpm -qa *thunderbird* *xulrun* *firefox* *mozilla* *flash* *plugin* Please also install thunderbird-debuginfo (debuginfo-install is from yum-utils package). # debuginfo-install thunderbird Then run thunderbird inside the gdb debugger. Please do the following: $ thunderbird -g stuff will appear. ignore this until you get the gdb command prompt, then do: (gdb) run Now, thunderbird should start up. Use it and reproduce the crash. When thunderbird crashes, you should be back to the gdb prompt. Now do: (gdb) thread apply all backtrace More screens of stuff will occur. Copy all of this part to your editor of choice, such as gedit, and save it as an uncompressed file and attach it to this bug report. We will review this issue again once you've had a chance to attach this information. Thanks in advance. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 381660 [details] Reply to, needinfo requested: [Bug 551892] [abrt] crash in thunderbird-3.0-4.fc12 Ok, here is the info you requested. In attachment... Don
This bug has been triaged Reporter, thank you for your extra efforts. I will turn this over to a dev and he may or may not ask for more information. jhorak, I am assigning this to you, to start. If you are not the correct dev, please reassign as needed. I believe we have all the info you would require, and was unable to immediately identify this as a duplicate. Setting keyword Triaged and status ASSIGNED (Fedora 12) per new policy. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 559676 has been marked as a duplicate of this bug. ***
*** Bug 576967 has been marked as a duplicate of this bug. ***
can't reproduce it in Thunderbird/3.1.6
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.