Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#2367 - Thunderbird crashes very often

Attached to Project: Arch Linux
Opened by Iamandi Florin (Florin) - Sunday, 13 March 2005, 21:21 GMT
Last edited by Judd Vinet (judd) - Monday, 14 March 2005, 23:41 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Dale Blount (dale)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Thunderbird is crushing very often. On crash it outputs different errors on line #159 of run-mozilla.sh. Here are the last 3 errors, the crash #3 was at 5 minutes from the crash #1.

/opt/mozilla/lib/thunderbird-1.0/run-mozilla.sh: line 159: 3828 Illegal Instruction "$prog" ${1+"$@"}

/opt/mozilla/lib/thunderbird-1.0/run-mozilla.sh: line 159: 4996 Segmentation Fault "$prog" ${1+"$@"}

/opt/mozilla/lib/thunderbird-1.0/run-mozilla.sh: line 159: 5198 Segmentation Fault "$prog" ${1+"$@"}
This task depends upon

Closed by  Dale Blount (dale)
Tuesday, 31 May 2005, 15:50 GMT
Reason for closing:  Works for me
Additional comments about closing:  user removed settings and crashes stopped
Comment by Jan de Groot (JGC) - Sunday, 13 March 2005, 22:58 GMT
What CPU do you have and is your memory okay? Try running memtest86 for a while.

The "illegal instruction" error you supply is usually caused by unsupported CFLAGS for your hardware. I hit it once with FreeBSD when I switched from a P3 500 to a Duron 750, where the duron didn't have SSE...
Comment by Iamandi Florin (Florin) - Monday, 14 March 2005, 17:52 GMT
It's a Duron 800.

[florin ~]$ dmesg|grep CPU
Initializing CPU#0
CPU: After generic identify, caps: 0183f9ff c1c7f9ff 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0183f9ff c1c7f9ff 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 64K (64 bytes/line)
CPU: After all inits, caps: 0183f9ff c1c7f9ff 00000000 00000020 00000000 00000000
Intel machine check reporting enabled on CPU#0.
CPU0: AMD Duron(tm) Processor stepping 01
per-CPU timeslice cutoff: 182.83 usecs.
Brought up 1 CPUs
CPU0:
ACPI: CPU0 (power states: C1[C1] C2[C2])
ACPI: Processor [CPU0] (supports 16 throttling states)
Comment by Iamandi Florin (Florin) - Monday, 14 March 2005, 19:40 GMT
I have been running memtest86 for an hour now, no errors.
I don't know much about the CFLAGS. Where and what should I look for in order to provide more details?
Comment by Jan de Groot (JGC) - Monday, 14 March 2005, 22:57 GMT
CPU couldn't be the problem, neither the memory. Are you using xorg or xfree86? I've heard some things on the mailinglist, could be GTK locking itself into xorg in an incompatible way so it crashes with XFree86.
Comment by Iamandi Florin (Florin) - Monday, 14 March 2005, 23:18 GMT
I am using xorg:
[florin ~]$ pacman -Qi xorg
Name : xorg
Version : 11R6.8.2-2

Here's the gtk too:
[florin ~]$ pacman -Qi gtk
Name : gtk
Version : 1.2.10-4

HTH. Thank you.
Comment by Paul Mattal (paul) - Tuesday, 05 April 2005, 20:06 GMT
What motherboard are you using? I think I may have seen things like this with the Asus A7N8X fairly long ago. I think mine were nonfatal errors, though. Weird stuff.
Comment by Iamandi Florin (Florin) - Wednesday, 06 April 2005, 21:46 GMT
I have an Asus A7VI-VM, VIA VT8365 (VIA Prosavage KM133) chipset.
Comment by Paul Mattal (paul) - Thursday, 07 April 2005, 02:06 GMT
Well that's not the connecting link then, as the A7N8X is the NVidia NForce2. Good luck finding the solution!
Comment by pete (drg006) - Sunday, 24 April 2005, 05:27 GMT
Have you tried reloading your settings? I was also having problems (more often hangs than seg faults), but I just cleared out my settings in ~/.thunderbird, and then re-imported my mail and I haven't had any problems since.
Comment by Iamandi Florin (Florin) - Sunday, 24 April 2005, 08:11 GMT
OK. I'll try this. Let's see if it helps in any way.
However I have noticed that the behaviour is not constant, as in sometimes it can crash so often that I can't work properly but there are other days when I am expecting it to crash any second... yet it doesn't.
Comment by Paul Mattal (paul) - Sunday, 01 May 2005, 20:24 GMT
Did this have any effect?
Comment by Iamandi Florin (Florin) - Sunday, 01 May 2005, 21:21 GMT
So far so good. No crash in the last days.
I haven't had a crash the whole week. Normal usage, I've been keeping up with -Syu...
*shrug*
Comment by Paul Mattal (paul) - Sunday, 01 May 2005, 21:26 GMT
Let's let this sit until 6/1 and then close it if you've got no more problems. Sound fair?
Comment by Iamandi Florin (Florin) - Monday, 02 May 2005, 17:30 GMT
Fair enough for me.

Loading...