Bug 14704 - Cannot launch Thunderbird because of a bus error
Summary: Cannot launch Thunderbird because of a bus error
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Florian Hubold
QA Contact:
URL:
Whiteboard: NEEDINFO
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-01 19:37 CET by Carolyn Rowse
Modified: 2014-12-05 10:18 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Carolyn Rowse 2014-12-01 19:37:40 CET
Description of problem:

I'm no longer able to open Thunderbird.  When I try from the CLI I get the words "Bus error".  This has been happening during the last few days, but I haven't been checking my e-mails very frequently lately so I can't pinpoint when the problem would have started.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2014-12-03 17:13:42 CET
Which desktop environment and display manager do you use?

what is the output of:

rpm -qa | grep thunderbird

What happens if you first rename 
/home/<you>/.thunderbird to: 
/home/<you>/.thunderbirdOLD and then start thunderbird (yeah, your mailboxes won't be there), or when you log in as a different user and start thunderbird?

CC: (none) => doktor5000, marja11
Whiteboard: (none) => NEEDINFO

Comment 2 Marja Van Waes 2014-12-03 17:14:23 CET
s/or/and/
Comment 3 Florian Hubold 2014-12-04 01:41:42 CET
In addition to the rpm -qa | grep thunderbird output, please first run thunderbird from a terminal and post the complete output here (before trying to rename your ~/.thunderbird profile folder).

Status: NEW => ASSIGNED
Assignee: bugsquad => doktor5000

Comment 4 Carolyn Rowse 2014-12-05 10:18:17 CET
It seems fine now since I installed the latest update.  Thanks anyway.

Carolyn

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.