firefox-bin crashed with SIGSEGV in __kernel_vsyscall()

[Jean Dumont]

Binary package hint: firefox

Crashed during update of Gutsy

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Oct 5 04:02:19 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/firefox/firefox-bin
NonfreeKernelModules: vmnet vmmon nvidia
Package: firefox 2.0.0.6+2-0ubuntu4
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/jean
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_BE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
 ?? ()
 ?? ()
 ?? ()
Title: firefox-bin crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux jeanpc 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video www-data

[Apport retracing service (apport)]

StacktraceTop:nsTextFrame::Paint (this=0x9ef5254, aPresContext=0x9c6bd08, aRenderingContext=@0x8132090,
nsContainerFrame::PaintChild (this=0x9ef51d0, aPresContext=0x9c6bd08, aRenderingContext=@0x8132090,
nsContainerFrame::PaintChildren (this=0x9ef51d0, aPresContext=0x9c6bd08, aRenderingContext=@0x8132090,
nsHTMLContainerFrame::PaintDecorationsAndChildren (this=0x9ef51d0, aPresContext=0x9c6bd08,
nsInlineFrame::Paint (this=0x9ef51d0, aPresContext=0x9c6bd08, aRenderingContext=@0x8132090,

[John Vivirito (gnomefreak)]

Is this still aproblem for you with latest firefox version in your Ubuntu version?

[Jean Dumont (jean-dumont)]

John Vivirito a écrit :
> Is this still aproblem for you with latest firefox version in your
> Ubuntu version?
>
> ** Changed in: firefox (Ubuntu)
> Status: New => Incomplete
>
> ** Visibility changed to: Public
>
Sorry for the delay,

No, Firefox seems to be a lot more stable, but in fact there are so many
problems with Hardy at the moment that even in the case of a crash it seems
impossible to pinpoint the exact cause. Nautilus seems especially prone to
various "glitches" so much so that in fact I switched to enlightenment-0.17.

As of today it seems that the resolver is acting funny and problems seems to
pile up one another, I seriously consider switching back to gutsy or going
to the Fedora camp (which is indicative of my disappointment with ubuntu)

[John Vivirito (gnomefreak)]

Jean Dumont wrote:
> John Vivirito a écrit :
>
>> Is this still aproblem for you with latest firefox version in your
>> Ubuntu version?
>>
>> ** Changed in: firefox (Ubuntu)
>> Status: New => Incomplete
>>
>> ** Visibility changed to: Public
>>
>>
> Sorry for the delay,
>
> No, Firefox seems to be a lot more stable, but in fact there are so many
> problems with Hardy at the moment that even in the case of a crash it seems
> impossible to pinpoint the exact cause. Nautilus seems especially prone to
> various "glitches" so much so that in fact I switched to enlightenment-0.17.
>
> As of today it seems that the resolver is acting funny and problems seems to
> pile up one another, I seriously consider switching back to gutsy or going
> to the Fedora camp (which is indicative of my disappointment with ubuntu)
>
>
Thank you for the reply. Closing bug due to it no longer being ablet o
be reproduced.

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

[Alexander Sack (asac)]

On Tue, May 13, 2008 at 10:40:28AM -0000, Jean Dumont wrote:
>
> As of today it seems that the resolver is acting funny and problems seems to
> pile up one another, I seriously consider switching back to gutsy or going
> to the Fedora camp (which is indicative of my disappointment with ubuntu)
>

Which resolver are you referring to?

 - Alexander

[Alexander Sack (asac)]

On Tue, May 13, 2008 at 08:31:09PM -0000, Jean Dumont wrote:
>
> ** Attachment added: "unnamed"
> http://launchpadlibrarian.net/14502717/unnamed
>

ok, anyway thanks for following up on this.

You mentioned that firefox is more stable now ... closing bug
accordingly

 status fixreleased

 - Alexander