** Changed in: firefox (Ubuntu)
Status: Invalid => Fix Released
--
Firefox Segmentation Fault Requires Reboot
https://bugs.launchpad.net/bugs/60236
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
On 01/28/10 06:01, kuntergunt wrote:
> Update:
> What I did yesterday:
> I reistalled firefox and firefox-gnome-support
> I unstalled scim
> I started firefox in safe mode (firefox -safe-mode) with all addd-ons
> disabled.
> Firefox still aborted with segmentation fault afetr some, maybe 5, minute
Update:
What I did yesterday:
I reistalled firefox and firefox-gnome-support
I unstalled scim
I started firefox in safe mode (firefox -safe-mode) with all addd-ons disabled.
Firefox still aborted with segmentation fault afetr some, maybe 5, minutes.
Today I got a couple of Ubuntu updates:
After in
I have the Segmentation fault problem out of a sudden for 1 hour now.
The notebook was running firefox now for two years with no problems. I
have no Updates installed today. I have lot of memory in my notebook (2
GB). All other apps are running with no problems, but firefox crashes
after a short ti
It also happens on Ubuntu 9.04 (jaunty jackalope) - FF 3 / 3.5.3
strace:
...
[pid 10202] 22:15:37.430885 close(51) = 0
[pid 10202] 22:15:37.432163 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
[pid 10202] 22:15:37.432326
unlink("/home/volker/.mozilla/firefox/7hpruwum.default/lock") = 0
[pid 102
BTW, it's also happening in Epiphany - probably a shared library?
--
Firefox Segmentation Fault Requires Reboot
https://bugs.launchpad.net/bugs/60236
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I still do - it may be AMD Athlon XP CPU's.
Didn't have any trouble till I updated 8.10 (Ibex).
--
Firefox Segmentation Fault Requires Reboot
https://bugs.launchpad.net/bugs/60236
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
from my experience i have same problem WHEN:
my SCIM are 2 bite character input mode. then send somewhere comment to
web page, Firefox suddenly crush and doesnt restart again unless SCIM
back to 1 bite character input mode.
--
Firefox Segmentation Fault Requires Reboot
https://bugs.launchpad.ne
If anyone still sees this issue please file a new bug report with the
info you have. closing due to the original reporter no longer sees it
and from what i see they all are not the same bug.
** Changed in: firefox (Ubuntu)
Status: Incomplete => Invalid
--
Firefox Segmentation Fault Requir
Update on my problem: it was due to faulty RAM. I realized that Firefox
was not the only app crashing for no reason. Running memtest86 confirmed
the problem. Problem was solved by replacing the RAM...
--
Firefox Segmentation Fault Requires Reboot
https://bugs.launchpad.net/bugs/60236
You received
This bug came, then it disappeard, and since a few weeks its back on my AMD64
32-bit feisty box.
It seems to get worse after installing packages.
Did the following:
1) reinstalled firefox: sudo aptitude reinstall firefox
2) removed SCIM: sudo aptitude remove scim
3) reboot
Problem solved.
--
F
My Firefox (and Thunderbird) also randomly crashes.
I've been able to get the full backtrace of on of these segfaults
(attached). This one occured while I let FF run overnight (I wasn't
using it). When I unlocked my station this morning, FF had crashed. I
seems to have crashed on a during a mouse
On Sun, Jul 29, 2007 at 10:50:15PM -, teg350z wrote:
> I've fixed and solve the firefox segmentation fault by removing SCIM
> package:
>
> $ sudo aptitude remove scim
> $ firefox
>
> However, it may show the following minor error, but at least my firefox
> is UP AND RUNNING:
>
> XGetSelectio
I've fixed and solve the firefox segmentation fault by removing SCIM
package:
$ sudo aptitude remove scim
$ firefox
However, it may show the following minor error, but at least my firefox
is UP AND RUNNING:
XGetSelectionOwner: old version of gcin or gcin is not running ??
... try to start a new
And then again, maybe I just had to wait more :) Here's the crash
backtrace
#0 0xe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb7e1f628 in send () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#2 0xb7e4e6c3 in pt_Send (fd=0x9c784e8, buf=0xb40803
I installed clearlooks engine. One thing, however, is really odd. I
started firefox and surely enough, clearlooks was working. After some
time I got that segfault that caused firefox to close. Now I ran firefox
in debug mode hoping I could generate a backtrace. I could almost swear
this crash doesn
On Fri, Jul 06, 2007 at 11:53:38PM -, Ashraf Amayreh wrote:
> While trying to create a trace of this problem with firefox -g, I
> encountered another bug where firefox just hangs and stops responding. I
> don't know how related these are but I would guess they may be related,
> I'm using kubunt
While trying to create a trace of this problem with firefox -g, I
encountered another bug where firefox just hangs and stops responding. I
don't know how related these are but I would guess they may be related,
I'm using kubuntu feisty that is fully updated. I'll try to get another
stack trace of t
It's happening to me too with Kubuntu 7.04 (Feisty) 32-bit on an Intel Core 2
Duo, with the nVidia X driver.
I've found running "aptitude reinstall firefox" fixes it most of the time, and
it often breaks right after installing new software, so I'm thinking it's a
library conflict somewhere.
I'
I get this problem too, on Feisty Kubuntu with AMD64 and nVidia X
driver. I have a feeling it is related to that.
However I have found a workaround that works every time and that
suggests to me it is something in the environment. When this starts
happening I get "Segmentation fault (core dumped)"
I get exactly the same problem in a fresh and fully updated version of
feisty. Will reinstall firefox as Rebecca suggested. Perhaps this should
be in the wiki? This is affecting other apps too, such as kontact.
--
Firefox Segmentation Fault Requires Reboot
https://bugs.launchpad.net/bugs/60236
Yo
Hei folks,
Thanks to this Bug-Report So I was able to identify the stated symptomes to the
problem I was just facing!
AMD-64
4GIB RAM
11GIB free Disk (for /home and /tmp)
edgy all updated
Beryl working
Seg-faulted after trying to open a second firefox-window...
(first one was streaming music)
N
Alexander: I reinstalled that machine (Dapper->Feisty) and I have not
seen the bug anymore. Not suprising, because Feisty ships with Firefox
2. Also, I changed hardware configurations.
John Vivirito: I don't have permanent installations of Edgy and don't
know if the bug exists in that. Seems to wo
I've had this on Ubuntu Edgy (https://launchpad.net/bugs/78809) and
Debian 3.1.
Reinstalling Firefox (sudo apt-get install firefox firefox-gnome-support
--reinstall) usually clears the problem faster than rebooting, though it
doesn't always work.
--
Firefox Segmentation Fault Requires Reboot
htt
** Tags added: mt-needsummary
** Tags removed: mt-needreport
--
Firefox Segmentation Fault Requires Reboot
https://bugs.launchpad.net/bugs/60236
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL P
Tero, Gregory,
Are either of you seeing this bug in the latest firefox in edgy?
version 2.0.0.2+0dfsg-0ubuntu0.6.10
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
This seems to go back to my original comment that possibly some
experimental code was released into the Ubuntu dist of Firefox. While
this would be expected with Feisty given it's experimental nature right
now.
"It won't become official till early April"
It shouldn't or rather installations in Ed
Hi. I have same bug in my Feisty.
backtrace output in attachment.
** Attachment added: "backtrace output"
http://librarian.launchpad.net/6821840/bt
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Can you please follow the instructions that Alexander gave
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/60236/comments/17.
The stacvktrace i am getting is not helpful at all.
** Changed in: firefox (Ubuntu)
Assignee: John Vivirito => Mozilla Bugs
--
Firefox Segmentation Fault Requ
Taking for retrace lets see what i can pull out of crash report.
** Changed in: firefox (Ubuntu)
Assignee: Mozilla Bugs => John Vivirito
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
** Changed in: firefox (Ubuntu)
Assignee: Mozilla Team => Mozilla Bugs
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Tags added: mt-needreport
** Tags removed: needreport
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Tero,
can you please install firefox-dbg package and run firefox in debug mode
for a while like this:
# firefox -g
...
(gdb) run
...
-> then the crash
(gdb) bt full
as soon as you can reproduce this bug in debug mode, please
post the here.
Thanks,
Alexander
** Tags added: need
Hi Alex,
Yes I did install it in /usr/lib and that is the only
reason I am posting such a comment to begin with. Not to mention I am posting
it in Firefox. Yes, what I am mentioning can be far fetched. This is why I
suggested john install both in the /opt directory to make an
On Thu, Feb 08, 2007 at 04:18:36AM -, Walter wrote:
> Hi Alex,
>
> Thank you for realizing what I was trying to say. I was actually
> saying that someone used some of the Firefox Alpha upstream code in the
> Ubuntu release. Since when I attempted to install the Alpha as a
> seperate insta
Hi Alex,
Thank you for realizing what I was trying to say. I was actually
saying that someone used some of the Firefox Alpha upstream code in the
Ubuntu release. Since when I attempted to install the Alpha as a
seperate installation it did indeed produce the same error.
To answer Johns comme
I think Walter wanted to say that this does not happen in upstream
release, while it does in our.
He suggests that this is due to a patch that upstream mozilla doesn't
ship, but we do.
However to follow this trail, we would need someone who can reproduce
this AND who can rebuild debian packages (
Ok installing upstream version does not fix anything or overcome
anything, it is avoiding issues. We do not support upstream version of
firefox nor thunderbird.
https://help.ubuntu.com/community/FirefoxNewVersion shows you how to do
it easy and safely.
--
Firefox Segmentation Fault Requires Reboo
Ironically I solved the problem at least in part. At first I installed
the latest testing Firefox 3.0a2 in the /opt directory to see whether it
produced the same error. I thought it would be cool with 3.0a2 to test
how the new firefox would run. When I realized that installing Mozilla
Firefox 3.0a2
Anyone happen to be using beryl or compiz with this issue. Im tempted to
agree with jdong on the mem. issue and if using beryl/compiz or another
effects app try turning ti off than see if you can reproduce this
please.
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
Well I had similiar problems. Too boot now after upgrading my Video
driver (X Display Driver) I can't start Firefox at all. It keeps on
giving me a segmentation fault. Below is an abbreviated copy of the
Gnome/Mozilla app dump report.
ProblemType: Crash
CoreDump:
CrashCounter: 1
Date: Tue Jan 30
** Changed in: firefox (Ubuntu)
Importance: Undecided => High
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: firefox (Ubuntu)
Assignee: David Farning => Mozilla Team
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have seen this in Dapper less than two months ago. As this bug can't
be reproduced at will, I can't check right away if I still have it or
not.
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
Is this still and issue for you? I am trying sort out the older mozilla
issues?
Thanks
David
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => David Farning
Status: Unconfirmed => Needs Info
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
--
Firefox randomly crashed (closed without explanation) every now and then
for about one day before completely refusing to start. It has been
continuously open for days before the problem occurred.
After segfault on start, these did not help:
- Try to start firefox many many times
- killall fire[ta
Might be related to GTK or Gnome, as after the problem, also gnome
screenshooter (PrintScreen) failed to save a file.
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo
Now it segfaults again just like before. 'strace firefox' has this near the end:
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb73b4000
brk(0x8e7) = 0x8e7
brk(0x8ea) = 0x8ea
--- SIGSEGV (Segmentation
I find it unlikely that the machine would have been running out of
memory. The machine showing this behavior has a GiB of memory. Other
software run well after firefox segfault. For example, I could browse
the web with konqueror. I have tried disabling my profile my renaming
~/.mozilla, and that di
mmap2(NULL, 2684358656, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = -1 ENOMEM (Cannot allocate memory)
Hmm, those entries look very suspicious. Are you low on memory or anything like
that? Tried disabling your plugins? (firefox -safe-mode)?
--
Firefox Segmentation Fault Requires
** Attachment added: "Strace of segfaulting firefox"
http://librarian.launchpad.net/4247631/firefox-segmentation-fault-strace-2006-09-13.txt
--
Firefox Segmentation Fault Requires Reboot
https://launchpad.net/bugs/60236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
51 matches
Mail list logo
