Red Hat Bugzilla – Bug 1316783
sqlite3Malloc() null crash come from libtracker-sparql
Last modified: 2017-11-16 22:39:52 EST
Description of problem:
thunderbird 38.6.0-3 or newer crashes on startup, per haps due to the recent sqlite fix
Version-Release number of selected component (if applicable):
Flawless startup of thunderbird
Please attach a backtrace of the crash, how to is here:
The info at the url needs correction: `debuginfo-install thunderbird` needs to be `dnf debuginfo-install thunderbird` on my system.
Also, for the debuginfo:
Total download size: 788 M
Installed size: 3.3 G
I do not think this is normal.
Yes, that's okay because the debuginfo pakages are huge.
Also, please try new profile (thunderbird -ProfileManager -no-remote) and safe mode (thunderbird -safe-mode).
Created attachment 1135159 [details]
crash bt as it is on my system
bt without installation of GB's of debuginfos
Created attachment 1135166 [details]
bt with sqlite debuginfos installed
(In reply to Martin Stransky from comment #3)
> Also, please try new profile (thunderbird -ProfileManager -no-remote) and
> safe mode (thunderbird -safe-mode).
safe-mode makes thunderbird start OK.
Now I need to find out which addon is the cause.
when I enabled trackerbird addon thunderbird crashed again.
Hm, that looks weird. Thread 0x7fffbf43b700 does not look ok to me, ends in sqlite3Malloc() and null. But that seems to come from libtracker-sparql/tracker not thunderbird.
Can you please attach a troubleshooting info? It's in Help -> Troubleshooting info and please attach the plain text version.
Created attachment 1135192 [details]
Help -> Troubleshooting
(In reply to Martin Stransky from comment #8)
> Hm, that looks weird. Thread 0x7fffbf43b700 does not look ok to me, ends in
> sqlite3Malloc() and null. But that seems to come from
> libtracker-sparql/tracker not thunderbird.
Indeed, disabling tracker addon in thunderbird enables me to run 36.6.0-3 or newer.
*38*.6.0-3 or newer that is
The tracker uses system sqlite which causes the problem.
F22 is getting EOLed in 2 weeks, so not going to fix this, sorry.
Comment 12 makes me think that this is still relevant.
*** Bug 1312868 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
(In reply to Debarshi Ray from comment #14)
> Comment 12 makes me think that this is still relevant.
Reproduceable for me with thunderbird-45.8.0-1.fc25.x86_64
(In reply to Igor Gnatenko from comment #17)
> (In reply to Debarshi Ray from comment #14)
> > Comment 12 makes me think that this is still relevant.
> any news?
The only news in this case is going to be getting rid of tracker's thunderbird subpackage from Fedora. I dropped the firefox subpackage recently. Haven't gotten around to thunderbird, yet. Feel free to do it. :)
It is there purely as a proof-of-concept. Nothing was designed to actually use it, nobody tests it or cares about it otherwise. It might even get dropped from upstream tracker. See the GNOME bug.
> The only news in this case is going to be getting rid of tracker's thunderbird subpackage from Fedora. I dropped the firefox subpackage recently. Haven't gotten around to thunderbird, yet. Feel free to do it. :)
Glad to hear of this.
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.