Hello, thanks for the bug report.

We need more info please install firefox-debug and the use gdb
https://wiki.mageia.org/en/Debugging_software_crashes

Keywords: (none) => NEEDINFO

please do the following:
1) enable the "core release debug"
2) install the following packages: gdb glibc-debug firefox-debug
3) run the following command from a terminal:
   gdb -q firefox
4) then type "run"
5) when it segfaults, type "bt" and copy back the stack trace in a file you'll attach (not paste) to this bug report
Thanks

CC: (none) => thierry.vignaud

Created attachment 1128 [details]
Firefox 8 debug output

(In reply to comment #3)
> Created attachment 1128 [details]
> Firefox 8 debug output

Hi Ken,

I know there is a ton of them... but can you install the indicated packages from your output and run this again?

Missing debug package(s), you should install: GConf2-debug-2.32.3-2.mga1.i586 ORBit2-debug-2.14.19-1.mga1.i586 atk1.0-debug-1.32.0-2.mga1.i586 avahi-debug-0.6.30-1.mga1.i586 cairo-debug-1.10.2-3.mga1.i586 dbus-debug-1.4.1-3.mga1.i586 dbus-glib-debug-0.88-2.mga1.i586 fontconfig-debug-2.8.0-5.mga1.i586 freetype2-debug-2.4.4-5.3.mga1.i586 gcc-debug-4.5.2-4.mga1.i586 gdk-pixbuf2.0-debug-2.22.1-3.1.mga1.i586 glib2.0-debug-2.28.6-3.mga1.i586 gnome-vfs2-debug-2.24.4-1.mga1.i586 gtk+2.0-debug-2.24.4-1.mga1.i586 libalsa2-debug-1.0.24.1-3.mga1.i586 libart_lgpl-debug-2.3.21-3.mga1.i586 libbonobo-debug-2.32.1-2.mga1.i586 libbonoboui-debug-2.24.5-1.mga1.i586 libcanberra-debug-0.27-2.mga1.i586 libgcrypt-debug-1.4.6-4.mga1.i586 libgnome-keyring-debug-2.32.0-1.mga1.i586 libgnome2-debug-2.32.1-7.mga1.i586 libgnomecanvas-debug-2.30.3-1.mga1.i586 libgnomeui2-debug-2.24.5-1.mga1.i586 libgpg-error-debug-1.10-1.mga1.i586 libice-debug-1.0.7-2.mga1.i586 libjpeg-debug-8b-5.mga1.i586 libnotify-debug-0.5.2-2.mga1.i586 libogg-debug-1.2.2-1.mga1.i586 libpng-debug-1.2.46-1.mga1.i586 libproxy-debug-0.4.6-8.mga1.i586 libsm-debug-1.2.0-2.mga1.i586 libtool-debug-2.4-3.mga1.i586 libvorbis-debug-1.3.2-1.mga1.i586 libvpx-debug-0.9.6-4.mga1.i586 libx11-debug-1.4.3-1.mga1.i586 libxau-debug-1.0.6-1.mga1.i586 libxcb-debug-1.7-1.mga1.i586 libxcomposite-debug-0.4.3-1.mga1.i586 libxcursor-debug-1.1.11-1.mga1.i586 libxdamage-debug-1.1.3-1.mga1.i586 libxdmcp-debug-1.1.0-1.mga1.i586 libxext-debug-1.2.0-2.mga1.i586 libxfixes-debug-5.0-1.mga1.i586 libxi-debug-1.4.2-1.mga1.i586 libxinerama-debug-1.1.1-2.mga1.i586 libxml2-debug-2.7.8-9.2.mga1.i586 libxrandr-debug-1.3.1-2.mga1.i586 libxrender-debug-0.9.6-1.mga1.i586 libxt-debug-1.1.1-2.mga1.i586 nspr-debug-4.8.9-1.1.mga1.i586 nss-debug-3.13.1-0.2.mga1.i586 nss_mdns-debug-0.10-9.mga1.i586 openssl-debug-1.0.0d-2.mga1.i586 pango-debug-1.28.4-1.mga1.i586 pcre-debug-8.12-3.mga1.i586 pixman-debug-0.20.2-1.mga1.i586 popt-debug-1.16-1.mga1.i586 sqlite3-debug-3.7.6.2-3.mga1.i586 startup-notification-debug-0.10-6.mga1.i586 xcb-util-debug-0.3.6-3.mga1.i586 zlib-debug-1.2.5-3.mga1.i586


Thanks!

Created attachment 1129 [details]
Firefox 8 debug output

After installing all DEBUG packages...

Attachment 1128 is obsolete: 0 => 1

Created attachment 1130 [details]
Latest results of "gdb -q firefox"

Previous debug txt was obtained while using FF7 run from /home.  After FF7 updates itself to FF8 this is the debug output.

@ Ken

Thanks for the backtraces.

Sorry that no one responded, probably everyone was just too busy (we're short on volunteers who help)

There have been a lot of updates, we even have FF 9 now. Do you still have this bug?

CC: (none) => marja11, remco

Those are useless.
You need to:
1) enable Core Release Debug medium,
2) install firefox-debug, glibc-debug
3) type "thread apply all bt full" rather than "bt"

(In reply to comment #8)
> Those are useless.
> You need to:
> 1) enable Core Release Debug medium,
> 2) install firefox-debug, glibc-debug
> 3) type "thread apply all bt full" rather than "bt"

I've moved on to different hardware and the bug is not present in the new configuration.  The old system still has the same problem.  It must be hardware related as no one in the forums seems to have the issue.  Anyway, looks like we can close the book on this one.  Thank you for the response.  I'm enjoying Mageia and glad that I moved from Mandrive when I did.

(In reply to comment #9)
> 
> I've moved on to different hardware and the bug is not present in the new
> configuration.  The old system still has the same problem.  It must be hardware
> related as no one in the forums seems to have the issue.  Anyway, looks like we
> can close the book on this one.  Thank you for the response.  I'm enjoying
> Mageia and glad that I moved from Mandrive when I did.


Thanks for replying :)

Closing as OLD, then, feel free to reopen when needed (sorry we gave you so much work while the instructions in comment 8 would have been better :( )

Status: NEW => RESOLVED
Resolution: (none) => OLD