Bug 577752 - [abrt] crash in thunderbird-3.0.3-1.fc12: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in thunderbird-3.0.3-1.fc12: Process /usr/lib64/thunderbird-3.0/...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7d0e255e5517c1bcc15f03e7192...
: 582705 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-29 07:48 UTC by collura
Modified: 2010-11-03 18:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-03 18:38:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (71.27 KB, text/plain)
2010-03-29 07:48 UTC, collura
no flags Details

Description collura 2010-03-29 07:48:21 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/thunderbird-3.0/thunderbird-bin
comment: i am guessing that the left-click menu 'copy-again' function didnt get an updated location after i changed the name of the original destination folder.  guess i got spoiled by how well the message filters update when i rename things,  lol.
component: thunderbird
executable: /usr/lib64/thunderbird-3.0/thunderbird-bin
kernel: 2.6.32.9-70.fc12.x86_64
package: thunderbird-3.0.3-1.fc12
rating: 4
reason: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. copy multiple selected letters to a folder
2. rename the folder ( moved to be subfolder of another folder )
3. use the left-click option of 'copy again to xxxxxxx location'
4. watch it crash

Comment 1 collura 2010-03-29 07:48:24 UTC
Created attachment 403210 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 09:48:34 UTC
*** Bug 582705 has been marked as a duplicate of this bug. ***

Comment 3 collura 2010-09-25 03:01:21 UTC
possibly duplicate of bug#538568 ?

Comment 4 Bug Zapper 2010-11-03 18:22:38 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 5 collura 2010-11-03 18:38:15 UTC
havent noticed this in fc13/fc14 so closing as nextrelease.

if anyone has problems let me know and we reopen as fc13 or fc14 as needed


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