Bug 19785 - TB doesn't run properly after upgrade from the usual repo. (ABORT: JS_SetICUMemoryFunctions failed.: file /home/iurt/rpmbuild/BUILD/thunderbird-45.4.0/thunderbird-45.4.0/mozilla/xpcom/build/XPCOMInit.cpp, line 816)
Summary: TB doesn't run properly after upgrade from the usual repo. (ABORT: JS_SetICUM...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Florian Hubold
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-14 22:03 CET by René Lagoni Neukirch
Modified: 2016-11-16 20:13 CET (History)
3 users (show)

See Also:
Source RPM: Thunderbird 45.4.0-1.mga5
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description René Lagoni Neukirch 2016-11-14 22:03:26 CET 
Description of problem:
Upgraded TB til 45.4 from the usual repo.

"Dump":
bash-4.3$ thunderbird
[5774] ###!!! ABORT: JS_SetICUMemoryFunctions failed.: file /home/iurt/rpmbuild/BUILD/thunderbird-45.4.0/thunderbird-45.4.0/mozilla/xpcom/build/XPCOMInit.cpp, line 816
[5774] ###!!! ABORT: JS_SetICUMemoryFunctions failed.: file /home/iurt/rpmbuild/BUILD/thunderbird-45.4.0/thunderbird-45.4.0/mozilla/xpcom/build/XPCOMInit.cpp, line 816
Segmentfejl [segmentation error]
bash-4.3$ 

Version-Release number of selected component (if applicable):
        Version: 45.4.0-1.mga5
        Nuværende installeret version: 0:45.4.0-1.mga5
        Gruppe: Netværk/Post
        Arkitektur: x86_64
        Størrelse: 112948 KB
        Medie: Ingen (installeret)

How reproducible:
Always, when trying to start TB (even as root).

Steps to Reproduce:
1. Just click the icon or issue "thunderbird" from a prompt.
2.
3.
René Lagoni Neukirch 2016-11-14 22:03:41 CET

CC: (none) => rene

Marja Van Waes 2016-11-15 12:03:33 CET

CC: (none) => marja11
Assignee: bugsquad => doktor5000
Summary: TB doesn't run properly after upgrade from the usual repo. => TB doesn't run properly after upgrade from the usual repo. (ABORT: JS_SetICUMemoryFunctions failed.: file /home/iurt/rpmbuild/BUILD/thunderbird-45.4.0/thunderbird-45.4.0/mozilla/xpcom/build/XPCOMInit.cpp, line 816)

Comment 1 René Lagoni Neukirch 2016-11-15 17:10:14 CET 
Hi again,

I tried some "end user" investigation by comparing my java environment/installation on my MGA5 - which fail severely - and my MGA6 which works.

The only difference to my knowledge is the ...python3-java...

Don't know if this helps ...

/René
Comment 2 René Lagoni Neukirch 2016-11-16 16:53:32 CET 
Hello one more time.
Is there a workaround, maybe?
I would prefer NOT to move "my product" to the mga6 staged development platform.
Comment 3 Marja Van Waes 2016-11-16 17:21:50 CET 
(In reply to René Lagoni Neukirch from comment #2)
> Hello one more time.
> Is there a workaround, maybe?
> I would prefer NOT to move "my product" to the mga6 staged development
> platform.

I don't think that's needed.

Do you use KDE?

I found a similar error, here:

https://forums.mageia.org/en/viewtopic.php?f=7&t=9900#p57206

IIUC, that happened after having chosen 'Use my KDE style in GTK applications', and was it solved after selecting another style

CC'ing KDE maintainers

CC: (none) => kde

Comment 4 René Lagoni Neukirch 2016-11-16 20:13:32 CET 
Hello Marja,

PROBLEM SOLVED !

THX for your clever advise on changing the KDE style.
TB is now working properly again.

Take care/René
--------------------------------------------
(In reply to Marja van Waes from comment #3)
> (In reply to René Lagoni Neukirch from comment #2)
> > Hello one more time.
> > Is there a workaround, maybe?
> > I would prefer NOT to move "my product" to the mga6 staged development
> > platform.
> 
> I don't think that's needed.
> 
> Do you use KDE?
> 
> I found a similar error, here:
> 
> https://forums.mageia.org/en/viewtopic.php?f=7&t=9900#p57206
> 
> IIUC, that happened after having chosen 'Use my KDE style in GTK
> applications', and was it solved after selecting another style
> 
> CC'ing KDE maintainers

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.