firefox crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: firefox 23.0~b4+
ProcVersionSign
Uname: Linux 3.10.0-4-generic x86_64
AddonCompatChec
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
BuildID: 20130709093527
Channel: Unavailable
Date: Sun Jul 21 16:35:03 2013
ExecutablePath: /usr/lib/
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-07-06 (14 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130704)
IpRoute:
default via 10.0.0.1 dev ppp0 proto static
10.0.0.1 dev ppp0 proto kernel scope link src 217.203.141.232
MarkForUpload: True
PrefSources: prefs.js
ProcCmdline: /usr/lib/
Profiles: Profile0 (Default) - LastVersion=
RelatedPackageV
totem-mozilla 3.8.2-0ubuntu1
rhythmbox-mozilla 2.99.1-0ubuntu1
RunningIncompat
Signal: 11
SourcePackage: firefox
StacktraceTop:
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
g_main_
?? () from /usr/lib/
Title: firefox crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/25/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K52JT.206
dmi.board.
dmi.board.name: K52JT
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K52JT
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1196700, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.