[feisty] firefox crashed [@~nsCOMPtr_base] [@~nsStyleBackground]

[Olivier]

Binary package hint: firefox

crash at the restart of KDE (kubuntu feisty)

ProblemType: Crash
Architecture: i386
Date: Wed May 16 01:23:19 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/firefox/firefox-bin
Package: firefox 2.0.0.3+1-0ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/olivier
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games:/usr/lib/mercury/jni/linux/jmf
 LANG=fr_CA.UTF-8
 LANGUAGE=fr_CA:fr
Signal: 11
SourcePackage: firefox
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
 ?? ()
 ?? ()
 ?? ()
Uname: Linux ordi01 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner users video

[Apport retracing service (apport)]

StacktraceTop:__kernel_vsyscall ()
raise () from /lib/tls/i686/cmov/libpthread.so.0
nsProfileLock::FatalSignalHandler (signo=11) at nsProfileLock.cpp:206

[Hilario J. Montoliu (hjmf) (hmontoliu)]

Is this still an issue for you? We are trying to sort this issue and would like to know if this still happens.

If it can be reproduced, please describe the steps to do it.

Thanks in advance.

[Olivier (olidel)]

Hi,

     Unfortunately, for now I didn't succeed to reproduce in an easy way
that bug.

Thanks.

OD

2007/6/17, Hilario J. Montoliu (hjmf) <email address hidden>:
>
> Is this still an issue for you? We are trying to sort this issue and
> would like to know if this still happens.
>
> If it can be reproduced, please describe the steps to do it.
>
> Thanks in advance.
>
>
> ** Tags added: mt-confirm mt-needtestcase
>
> --
> [feisty] firefox crashed [@~nsCOMPtr_base] [@~nsStyleBackground]
> https://bugs.launchpad.net/bugs/115025
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Hilario J. Montoliu (hjmf) (hmontoliu)]

We have not received any duplicates for some time. Thus, this crash was likely due to some unique plugin extension combination or has been fixed in the meantime. Please, reopen it at any time if you have more related info.

Thanks for your contribution. Don't hesitate to submit new crashes,

H. Montoliu