You are not logged in.
Pages: 1
Earlier today, I filed a bug - my thunderbird crashed a few seconds after launch, and gave me this message:
[oscar@pirate ~]$ mozilla-thunderbird
/opt/mozilla-thunderbird/lib/thunderbird-1.0/run-mozilla.sh: line 159: 12239 Segmentation fault "$prog" ${1+"$@"}When I filed the bug, I was using an non official thunderbird-build, and the bugreport was closed.
I removed my thunderbird, and reinstalled using the official package.
This is what I get after a few seconds in thunderbird:
[oscar@pirate ~]$ thunderbird
/opt/mozilla/lib/thunderbird-1.0/run-mozilla.sh: line 159: 13356 Segmentation fault "$prog" ${1+"$@"}Since my bug got closed, I can't even add an comment about this, and filing another bug about this won't make me popular ![]()
To err is human... to really foul up requires the root password.
Offline
you have a segmentation fault, that's not good, :cry:
arch + gentoo + initng + python = enlisy
Offline
Did you try to move your TB profile somewhere and then relaunch it?
Microshaft delenda est
Offline
2 things:
you should be able to run thunderbird in the same way you can with firefox...
try "thunderbird --debug" it should pop into gdb... type run (if it pauses keep typing run)... when it crashes type "info stack" and post the output here.
this may be related to the same firefox problem I was having. Some of my issues came from freetype2, but not all - the others came from gnome-vfs... i have since removed gnome-cfs and am using the stock freetype2... everything is happy.
Offline
If you need a bug re-opened, I'd suggest emailing the developer that closed it and request it be looked at again.
Offline
I thought, as the submitter, that you could re-open bugs.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
I thought, as the submitter, that you could re-open bugs.
I tried, but I couldn't find the proper button to make it happen ![]()
To err is human... to really foul up requires the root password.
Offline
did you look to see why the bug was closed? The maintainer may not have beenable to reproduce the issue and it is very hard to fix what cannot be duplicated. If the maintainer is not having issues you may want to contact them to find out what could be causing the problem for your system.
AKA uknowme
I am not your friend
Offline
Pages: 1