Firefox and SeaMonkey crashes on Opensuse 12.3 after upgrade

English Applications
#1

I Upgraded Firefox and SeaMonkey to the latest version in my Open Suse 12.3. After upgrade they crash all the time and I cannot use them since they crash during the startup of application.
Please advise

veki

#2

start them from a terminal and see the error messages, as firefox and sm use diferent profiles I don’t think it’s your profile folder, what graphic card do you have mozilla has had a lot of problems with some intel cards, try running firefox in safe mode and disable hardware acceleration.
there could be some package mismatches see if all updates have been applied there could be a shared object that hasn’t been updated.

#3

When I started Firefox from Konsole it started up, but when I entered Gmail it crashed and I noticed message in terminal:
Floating point exception.
When I started Seamonkey it immediately crashed and I found in terminal the following message:
[2198] ###!!! ABORT: Aborting on channel error.: file /home/abuild/rpmbuild/BUILD/seamonkey/mozilla/ipc/glue/MessageChannel.cpp, line 1618
[2198] ###!!! ABORT: Aborting on channel error.: file /home/abuild/rpmbuild/BUILD/seamonkey/mozilla/ipc/glue/MessageChannel.cpp, line 1618
/usr/bin/seamonkey: line 140: 2170 Segmentation fault $MOZ_PROGRAM “$@”

Please advise,

veki

#4

Hi, openSUSE 12.3 reaches its end of life on jan 4th, 2015. Perhaps now is the time to upgrade? HTH Lenwolf

#5

Please do not use vague expressions like this:
. what you think being the latest version at the moment in time you wrote this may not be seen as the latest version for others. E.g. you may look at the Mozilla web site, where others may look at the openSUSE Update repo;
. in due time (some weeks) there may be one or more newer versions and nobody will know any more which version this thread is about, making this thread useless;
. it is shorter and easier to type the version number then the words “the latest version” and certainly easier to read and evaluate.

#6

Hello,

When I said the latest version I thought the latest version installed by zypper. I assumed that I follow what is default by methods without using my interventions. If otherwise, I would say that I Installed version different from available using zypper. Consequently, Firefox is version 34.0.5-1.94.3 adn Seamonkey is version: 2.31-1.65.2

Thanks,

Veki

#7

Thanks, aboslute values are always more easy then relative ones that are relative to some unknown start point (assuming what others might understand/think).

#8

I think you should start software updater from yast and see if there are any new updates I believe you might have an old mozilla shared rpm and that’s where the segmentation fault comes from.

#9

what’s your graphic card and video driver some intel cards can cause similar segmentation faults.

#10

I installed that Firefox and SeaMonkey by regular use of commands:
zypper refresh
and
zypper update.

Consequently, I have not improvised anything and all installations are done by deafult values by the system itself.

Thanks,

veki

#11

Hello,

I do have Nvidia card on Toshiba Satellite laptop. Everything worked perfectly up to the upgrade I committed a couple of days ago with deafulst values from pacakage manager and commands:
zypper refresh
and
zypper update

Thanks,

Veki

#12

Maybe this helps:
**
“Problem:** Seamonkey 2.31 on Linux fails to start up after upgrading from 2.30, only showing the “clear private data” dialog and reporting “###!!! ABORT: Aborting on channel error.: file …]/comm-release/mozilla/ipc/glue/MessageChannel.cpp, line 1618” to the console.
Workaround: Attaching to the process with gdb when the dialog was shown and then detaching allowed the program to start up normally on future runs.”

I found this workaround here: http://achurch.org/notes.html

#13

Thanks. But, how to do that attaching as mentioned in workaround.
Thanks,

Veki

#14

Never did this myself, but I try to explain:

  • Start seamonkey
  • Start gdb in a console
  • Get the process-id for seamonkey e.g. with ps
**ps -x | grep seamonkey**
28068 ?        Sl     0:18 ...
  • Attach seamonkey process-id to gdb
(gdb) **attach 28068**
  • Then detach seamonkey from gdb
(gdb) **detach**
Detaching from program: ...

Bold: what to type
Hope this helps.

#15

I tried what you mentioned and it helped. I am writing this from Seamonkey that works. :slight_smile:
However, still looking for the solution for Firefox floating point exception.

Thanks,

veki