I guess I just wasn't patient enough; the bug reports I said had hung for like an hour actually completed. But, now they want me to make a new bug report rather than be able to attach it to an existing one. Whoops. Here's the URLs:
https://bugs.launchpad.net/ubuntu/+source/firefox/+filebug/437c2c30-c604-11e5-9da3-68b5996a96c8? https://bugs.launchpad.net/ubuntu/+source/firefox/+filebug/95b06742-c608-11e5-b400-0025b3df357a? https://bugs.launchpad.net/ubuntu/+source/firefox/+filebug/12a84d08-c60b-11e5-8930-68b5996a96c8? Maybe you won't need them; here's the "apport.bug" report from when I collected a report then used "ubuntu-bug -c (existing file)" to submit it. I never got a crash dump so these 3 reports probably had the same data anyway (other than time stamps). In summary, it looks like a lot of the file is the alsa config (which is huge since for some reason the audio chip on here has like 150 switches and volume controls), the other hardware info is almost empty (since there's no PCI bus). Enjoy! Thanks for the help! ** Attachment added: "apport.bug" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1539284/+attachment/4558675/+files/bug.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539284 Title: Firefox 44.0 repeatedly crashes on ARMHF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1539284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
