Description of problem: Starting Thunderbird with xmpp accounts to autojoin at start causes Thunderbird to segfault. Version-Release number of selected component (if applicable): 52.4.0 When started from konsole: $ thunderbird [calBackendLoader] Using Thunderbird's builtin libical backend GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. 10:53:22.313 ERROR firetray.StatusIcon Missing libappindicator for gtk3 (thunderbird:3753): Gtk-CRITICAL **: gtk_icon_theme_append_search_path: assertion 'path != NULL' failed prpl-jabber: Error during SRV lookup: Error: Could not find libresolv in any of libresolv.9.so,libresolv.so Exception: Error: couldn't open library libresolv.so: libresolv.so: cannot open shared object file: No such file or directory prpl-jabber: Error during SRV lookup: Error: Could not find libresolv in any of libresolv.9.so,libresolv.so Exception: Error: couldn't open library libresolv.so: libresolv.so: cannot open shared object file: No such file or directory Segmentation fault (core dumped) Next thunderbird start is successfull as the xmpp accounts did get disabled, but the segfault results as soon as you try to connect them.
Assigning to the registered maintainer. @ doktor5000 Note that bug reports from most users (except from packagers, packager-committers and most other special ldap groups) are now by default set to "UNCONFIRMED" I haven't tried to reproduce the issue, xmpp accounts mean nothing to me.
Assignee: bugsquad => doktor5000CC: (none) => marja11
Had a time to test with "stock" Thunderbird downloaded from mozilla.org/thunderbird. That one gives the same error messages, but does not crash and seems to work OK. So it seems to be specific to Mageia...
Also in Mageia6, Thunderbird 52.4.0 (32bit), installed from /updates/testing does not crash when jabber/xmpp accounts are connected.
Summary: thunderbird & jabber results segfault - missing libresolv => thunderbird & jabber results segfault
(In reply to Marja van Waes from comment #1) > Note that bug reports from most users (except from packagers, > packager-committers and most other special ldap groups) are now by default > set to "UNCONFIRMED" That's not good. That means those bugs won't be seen in most searches, since UNCONFIRMED is not selected by default. This change was never discussed and should be reverted.
(In reply to David Walser from comment #4) > (In reply to Marja van Waes from comment #1) > > Note that bug reports from most users (except from packagers, > > packager-committers and most other special ldap groups) are now by default > > set to "UNCONFIRMED" > > That's not good. That means those bugs won't be seen in most searches, > since UNCONFIRMED is not selected by default. This change was never > discussed and should be reverted. CC'ing LpSolit who made the change and stormi.
Status: UNCONFIRMED => NEWEver confirmed: 0 => 1CC: (none) => LpSolit, stormi
(In reply to David Walser from comment #4) > That's not good. That means those bugs won't be seen in most searches, > since UNCONFIRMED is not selected by default. This change was never > discussed and should be reverted. Not true. By default, no bug status is pre-selected. We already had this discussion in bug 21219. So I won't change my mind on this. Moreover, default queries on the home page do not care what the bug status is, and so UNCONFIRMED bugs are listed as well.
CC: LpSolit => (none)
Bug still valid in Cauldron's thunderbird-52.5.0-1.mga7 In Mageia6, Thunderbird 52.5.0 (32bit), installed from /updates/testing does not crash when jabber/xmpp accounts are connected. So it seems to be something specific to Mageia & Cauldron...
Source RPM: thunderbird-52.4.0-1.mga7.src.rpm => thunderbird-52.5.0-1.mga7.src.rpm
Can't reproduce this inside M7, Cauldron and even a M7 32 bits on a VM. Closing this. We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there. As a result we are setting this bug to RESOLVED:OLD
Status: NEW => RESOLVEDResolution: (none) => OLDCC: (none) => ouaurelien