|Summary:||[abrt] crash in seamonkey-2.0.6-1.fc13: Process /usr/lib/seamonkey-2.0.6/seamonkey-bin was killed by signal 6 (SIGABRT)|
|Product:||[Fedora] Fedora||Reporter:||Andrey V. Henneberg <safir>|
|Component:||seamonkey||Assignee:||Gecko Maintainer <gecko-bugs-nobody>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||13||CC:||caillon, gecko-bugs-nobody, kengert, lam, newmedea, skeeter1029, tenstrip, wayland|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2011-06-29 13:05:15 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Andrey V. Henneberg 2010-07-23 17:51:36 UTC
abrt 1.1.1 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/seamonkey-2.0.6/seamonkey-bin -mail comment: The problem is reproduced for version 2.0.6. component: seamonkey crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib/seamonkey-2.0.6/seamonkey-bin global_uuid: 6e4bcafe01ea4996abdc18cba711d07826f6e561 kernel: 220.127.116.11-147.fc13.i686.PAE package: seamonkey-2.0.6-1.fc13 rating: 4 reason: Process /usr/lib/seamonkey-2.0.6/seamonkey-bin was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) How to reproduce: Steps are the same as for versions 2.0.4 and 2.0.5
Comment 1 Andrey V. Henneberg 2010-07-23 17:51:42 UTC
Created attachment 434021 [details] File: backtrace
Comment 2 Andrey V. Henneberg 2010-07-23 17:58:05 UTC
seamonkey-2.0.6 crashes the same way as described in bug https://bugzilla.redhat.com/show_bug.cgi?id=583300
Comment 3 Leszek Matok 2010-07-24 07:15:22 UTC
Package: seamonkey-2.0.6-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Same as in every SM with F13's libcairo.
Comment 4 tenstrip 2010-07-24 07:49:18 UTC
Package: seamonkey-2.0.6-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- crashes *after* closing program via [X]
Comment 5 Andrey V. Henneberg 2010-07-24 11:32:22 UTC
Open several heavy pages and quickly close them one by one.
Comment 6 Martin 2010-07-30 09:19:19 UTC
Package: seamonkey-2.0.6-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Just close Seamonkey, seems to happen every time 2. 3.
Comment 7 dedanna 2010-08-08 00:02:19 UTC
Package: seamonkey-2.0.6-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open Seamonkey 2. Cruise the web 3. Close Seamonkey Comment ----- Same as always...
Comment 8 dedanna 2010-08-08 09:32:38 UTC
Package: seamonkey-2.0.6-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I was just surfing the web with Seamonkey, and it crashed out of the clear blue sky. 2. 3. Comment ----- This is getting ridiculous.
Comment 9 dedanna 2010-08-08 09:36:53 UTC
I'm seriously beginning to think it's the upstream bug. It does this in my Arch Linux, too, and did it in Mandriva as well when I was on it.
Comment 10 Leszek Matok 2010-08-08 10:42:47 UTC
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=522635 Bug was fixed long time ago in the trunk, but Fedora ships old SeaMonkey with new Cairo version. I can't understand why nothing is done about it in Fedora. SeaMonkey is absolutely unusable, crashing every 10th tab close, there are two patches in the bug + there's always possibility to use 2.1 alpha. Actually, I'm using 2.1a2 and 2.1a3 for the last month and it's rock stable in absolute terms, while the "stable" release you're using isn't at all. The only problem it has is combo buttons not expanding, you have to use keyboard to operate them. Probably something to do with being compiled by some robot on an ancient system, but I CBA to recompile SeaMonkey on Fedora :) AGAIN: Maintainters, why oh why can't we get one of the patches applied to SM and put to updates-testing? Or Koji? Or wherever? We're waiting MONTHS (bug was first reported in F13 RCs as bug 583300) for you to release a fix to make SM remotely usable, when patches seem available. Upstream is clearly not interested in supporting 2.0 on newer distros, so it really needs to be fixed downstream for now...
Comment 11 dedanna 2010-08-21 05:29:03 UTC
*** Bug 625971 has been marked as a duplicate of this bug. ***
Comment 12 dedanna 2010-08-21 05:30:43 UTC
This is getting way too ridiculous. Seamonkey, no matter what I do, crashes at least six times a day now with this. Fedora, please fix. Thank you.
Comment 13 dedanna 2010-08-21 05:33:12 UTC
@Leszek Matok, 2.x.x is no more stable for me than this is, and is so much more even like Firefox, it makes me want to scream. It's no solution here. Thanks anyway.
Comment 14 dedanna 2010-08-21 05:35:00 UTC
Sorry, meant the alpha.
Comment 15 dedanna 2010-08-26 17:23:18 UTC
I have added the option for --disable-system-cairo to Seamonkey 2.0.6's execution, I have 8 tabs open (have opened and closed a whole lot more than that), and Seamonkey hasn't crashed in a couple of hours at least. I've also closed it using the X with no crash. Just a heads up.
Comment 16 Leszek Matok 2010-08-26 23:46:06 UTC
Adding it to execution arguments won't help (I actually tested just in case, but it crashed as usual after 20 or tabs closed), but rebuilding RPM with it should! :) Anyone able to provide a scratch build in Koji? I'm not going to install a million devel packages since for me, binary 2.1a from mozilla.org nightlies works 100% stable (unless Flash crashes it, but that's easy to work around, and that's only if you use Flash at all)
Comment 17 Leszek Matok 2010-08-28 09:21:47 UTC
I forced myself to actually rebuild SeaMonkey with --disable-system-cairo. Wasn't that bad, took little over an hour to yum-builddep seamonkey, yum-downloader --source seamonkey, correct seamonkey-mozconfig with above option and rpm -bb seamonkey.spec. I'm writing this from SM 2.0.6 with 15 hours of uptime, so the work-around is working. As usual, I have to ask maintainers: why can't you put such build in updates-testing at least? That's a third known work-around now and nothing is being done...
Comment 18 dedanna 2010-08-29 00:18:04 UTC
I'm wondering how that worked for me then? I ran up to 25 tabs, closed them, opened them, the works. I stayed up for some 5 hours for the very first time with it.
Comment 19 dedanna 2010-08-31 00:34:35 UTC
*** Bug 628760 has been marked as a duplicate of this bug. ***
Comment 20 dedanna 2010-08-31 00:35:24 UTC
*** Bug 628757 has been marked as a duplicate of this bug. ***
Comment 21 dedanna 2010-08-31 00:36:07 UTC
Looks like it's not working any more. :P
Comment 22 Tim Nelson 2010-12-17 01:01:42 UTC
I've removed the NEEDSINFO tag -- if it should still be here, can someone state what info is needed?
Comment 23 Tim Nelson 2010-12-17 01:02:33 UTC
Also, why is this marked low importance?
Comment 24 dedanna 2010-12-17 16:07:06 UTC
I've noticed this here and at the Arch bugzilla both. When we file a bug, it doesn't give us the option of importance. Also, check to see if it was filed via ABRT - if it was, it was filed as auto-low importance and priority...
Comment 25 Bug Zapper 2011-06-01 13:07:31 UTC
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 26 Bug Zapper 2011-06-29 13:05:15 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.