Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 244368 - gecko crashes using Mozilla Firefox
Summary: gecko crashes using Mozilla Firefox
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
Depends on:
Reported: 2008-10-25 19:24 UTC by Algirdas
Modified: 2008-10-25 21:35 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Bugzilla report included (gecko-klaida.txt,664.42 KB, text/plain)
2008-10-25 19:25 UTC, Algirdas

Note You need to log in before you can comment on or make changes to this bug.
Description Algirdas 2008-10-25 19:24:59 UTC
Bugzilla reports, that gecko crashed and firefox quits when I use session manager.

Reproducible: Always
Comment 1 Algirdas 2008-10-25 19:25:52 UTC
Created attachment 169864 [details]
Bugzilla report included
Comment 2 Mike Auty (RETIRED) gentoo-dev 2008-10-25 21:35:29 UTC
Algirdas, your bug report is a little vague.  Firstly, please always include the output from running "emerge --info".

You mentioned bugzilla, but bugzilla is a web application for reporting bugs to after they've happened, not a program that reports bugs to users when they happen.  Did you mean bug-buddy, a gnome program that's used when a program crashes?

Also, you mention that gecko crashed.  Gecko is a rendering engine used inside of firefox.  What makes you mention gecko specifically, rather than just saying that firefox crashed?  Did bug-buddy mention gecko in particular?

Finally, you said that this happens whilst you're using session manager.  What do you mean by session manager?  Is that System -> Preferences -> Sessions, or something else?

Please be aware that bug-buddy can automatically submit these reports to gnome, who are far more likely to be able to help you with this problem, given that they understand the type of output produced in the report you attached.  Please consider submitting this issue to them, rather than reopening this bug...