Bug 574096 - [abrt] crash in thunderbird-3.0.3-1.fc12: Process /usr/lib/thunderbird-3.0/thunderbird-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in thunderbird-3.0.3-1.fc12: Process /usr/lib/thunderbird-3.0/th...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Horak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3610f9a80642de44588bc786dfb...
: 586444 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-16 15:48 UTC by Ivan Pravdin
Modified: 2010-12-03 17:14 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 17:14:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (36.62 KB, text/plain)
2010-03-16 15:48 UTC, Ivan Pravdin
no flags Details
Backtrace (38.30 KB, application/octet-stream)
2010-03-29 13:06 UTC, Andrea Gazzaniga
no flags Details

Description Ivan Pravdin 2010-03-16 15:48:11 UTC
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.32.9-70.fc12.i686
package: thunderbird-3.0.3-1.fc12
rating: 4
reason: Process /usr/lib/thunderbird-3.0/thunderbird-bin was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 Ivan Pravdin 2010-03-16 15:48:14 UTC
Created attachment 400485 [details]
File: backtrace

Comment 2 Simen 2010-03-21 13:22:32 UTC

How to reproduce
-----



Comment
-----
Closed Thunderbird.

Comment 3 Chris Campbell 2010-03-25 15:10:19 UTC
#3  <signal handler called>
No symbol table info available.
#4  0x00bb4416 in __kernel_vsyscall ()
No symbol table info available.
#5  0x00818a91 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
        resultvar = <value optimized out>
        resultvar = <value optimized out>
        pid = 9826292
        selftid = 2434
#6  0x0081a35a in abort () at abort.c:92
        save_stage = 2
        act = {__sigaction_handler = {sa_handler = 0xbfb03b70, sa_sigaction = 
    0xbfb03b70}, sa_mask = {__val = {3079501600, 3215997764, 8215848, 
    3215997748, 10315788, 3215997736, 8305212, 0, 3079467152, 5, 0, 1, 
    3079501160, 2659532800, 3215997704, 8259120, 2, 2659532800, 10091495, 
    10112132, 2434, 0, 3215997808, 3215997736, 3215997748, 134524081, 
    3079501160, 0, 10349488, 11256228, 134524065, 134551024}}, sa_flags = 
    -1078969480, sa_restorer = 0x804d19b <idalloc+440>}
        sigs = {__val = {32, 0 <repeats 31 times>}}
#7  0x00a152e6 in IA__g_logv (log_domain=<value optimized out>, 
    log_level=<value optimized out>, format=<value optimized out>, 
    args1=<value optimized out>) at gmessages.c:549
        domain = <value optimized out>
        data = <value optimized out>
        masquerade_fatal = <value optimized out>
        test_level = <value optimized out>
        i = <value optimized out>
#8  0x00a15317 in IA__g_log (log_domain=<value optimized out>, 
    log_level=<value optimized out>, format=<value optimized out>)
    at gmessages.c:569
No locals.
#9  0x06b93703 in gdk_x_error (display=0xb7650000, error=0xbfb0414c)
    at gdkmain-x11.c:466
        buf = 
    "XI_BadDevice (invalid Device parameter)", '\000' <repeats 24 times>"\277, "
        msg = <value optimized out>
#10 0x00e1e946 in bonobo_x_error_handler (display=<value optimized out>,



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Andrea Gazzaniga 2010-03-26 05:22:53 UTC

Comment
-----
1. Back from suspend to RAM
2. Get mail in thunderbird, sayd can't connect (network was ok)
3. Close thunderbird, got crash report

Comment 5 Chris Campbell 2010-03-26 19:35:37 UTC
Andrea, could you attach a back-trace so we can confirm your crash is the same as the reporters? If it is, then you've given us steps to reproduce.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Andrea Gazzaniga 2010-03-29 13:06:10 UTC
Created attachment 403286 [details]
Backtrace

Here is the requested backtrace.

Comment 7 Chris Campbell 2010-03-30 13:15:24 UTC
OK, back-trace is the same, and in fact looks good, with reproducer steps, such as they are. Not setting this as a dupe. Setting keyword and status.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 8 Karel Klíč 2010-05-25 09:46:29 UTC
*** Bug 586444 has been marked as a duplicate of this bug. ***

Comment 9 Bug Zapper 2010-11-03 19:30:52 UTC
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

Comment 10 Bug Zapper 2010-12-03 17:14:35 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.