evolution-source-registry crashed with SIGSEGV in g_hash_table_lookup()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution-data-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Raising a new bug after discussions on Bug #1494804 suggested that this was a different issue as the one documented under #1494804 originated in 15.10.
I don't know what I did to stimulate the problem. An error report prompt appeared one day.
I'll answer the same questions from Bug #1494804 here in case they are relevant.
> what accounts he/she has configured, whether any are from Ubuntu Online Accounts or GNOME Online Accounts?
I have a personal GoogleMail imapx account created though the Online Accounts Service and an ews OWA account linked to my work exchange server.
> whether it crashes also when he/she runs the evolution-
It seems to have worked OK when I ran /usr/lib/
$ /usr/lib/
Migrating mail accounts from GConf...
Migrating addressbook sources from GConf...
Migrating calendar sources from GConf...
Migrating task list sources from GConf...
Migrating memo list sources from GConf...
Registering EGoogleBackendF
Registering EOutlookBackend
Registering EYahooBackendFa
Registering EOwncloudBacken
Registering EEwsBackendFactory ('ews')
Registering EMapiBackendFactory ('mapi')
Registering ECollectionBack
Adding 1433155791.
Adding vfolder ('Source_1')
Adding 1433325395.
OWA <email address hidden>: Pairing 1434544712.
Adding 1434544712.
Adding 1434381690.
Adding 1434381690.
Adding 1437989181.
Adding 1434381690.
Adding 1432804779.
Adding 1434381690.
Adding 1432718461.
Adding 1432718462.
Adding 1432718461.
Adding 1432889488.
Adding 1432889488.
Adding 1432889488.
Adding 1432640797.
Adding 1432640797.
Adding 1432640791.
Adding local ('Source_19')
Adding 1432889488.
Adding 1432640791.
Adding 1433155649.
Adding caldav-stub ('Source_23')
Adding contacts-stub ('Source_24')
Adding birthdays ('Source_25')
Adding google-stub ('Source_26')
Adding ldap-stub ('Source_27')
Adding local-stub ('Source_28')
Adding system-calendar ('Source_29')
Adding system-address-book ('Source_30')
Adding weather-stub ('Source_31')
Adding webcal-stub ('Source_32')
Adding webdav-stub ('Source_33')
Adding sendmail ('Source_34')
Adding system-memo-list ('Source_35')
Adding system-task-list ('Source_36')
module-
module-
Server is up and running...
AUTH (1434381690.
Bus name 'org.gnome.
<email address hidden>: Pairing 1432889488.
Adding 1432889488.
<email address hidden>: Pairing 1432889488.
Adding 1432889488.
<email address hidden>: Pairing 1432640844.
Adding 1432640844.
<email address hidden>: Pairing 1432640844.
Adding 1432640844.
AUTH (1432640797.
AUTH (1434381690.
AUTH (1434381690.
AUTH (1432640797.
OWA <email address hidden>: Pairing 1434382914.
Adding 1434382914.
OWA <email address hidden>: Pairing 1434382914.
Adding 1434382914.
OWA <email address hidden>: Pairing 1434382914.
Adding 1434382914.
OWA <email address hidden>: Pairing 1434382914.
Adding 1434382914.
OWA <email address hidden>: Pairing 1434382914.
Adding 1434382914.
OWA <email address hidden>: Pairing 1434382914.
Adding 1434382914.
OWA <email address hidden>: Pairing 1434382914.
Adding 1434382914.
OWA <email address hidden>: Pairing 1434382914.
Adding 1434382914.
OWA <email address hidden>: Pairing 1434382914.
Adding 1434382914.
Adding 1439892977.
Adding 1434382890.
Adding 1439892980.
AUTH (1434381690.
AUTH (1434381690.
AUTH (1434381690.
AUTH (1434381690.
AUTH (1434381690.
AUTH (1434381690.
AUTH (1434381690.
AUTH (1434381690.
AUTH (1434381690.
AUTH (1434381690.
AUTH (1434381690.
> whether running the source registry under valgrind will also reproduce the crash (it can happen that other timing, due to all slowness caused by the memory checking, will not trigger the crash, but also that the valgrind will log about the issue and will keep the application running). The command might look like (I do not know exact location of the executable, thus it can differ in your distribution):
$ G_SLICE=
The only output that looks suspect is:
Adding system-memo-list ('Source_35')
Adding system-task-list ('Source_36')
module-
module-
Server is up and running...
AUTH (1434381690.
==11889== Conditional jump or move depends on uninitialised value(s)
==11889== at 0xC7FF0DD: ag_auth_data_unref (in /usr/lib/
==11889== by 0xC5EC83E: ??? (in /usr/lib/
==11889== by 0xC5ECB72: ??? (in /usr/lib/
==11889== by 0xC5ED31C: ??? (in /usr/lib/
==11889== by 0x5F403B7: g_closure_invoke (in /usr/lib/
==11889== by 0x5F51FD0: ??? (in /usr/lib/
==11889== by 0x5F59A28: g_signal_
==11889== by 0x5F59CE1: g_signal_emit (in /usr/lib/
==11889== by 0x5C8EA63: ??? (in /usr/lib/
==11889== by 0x5C2E3B6: g_simple_
==11889== by 0x5C2E418: ??? (in /usr/lib/
==11889== by 0x61C9CE4: g_main_
==11889==
==11889== Conditional jump or move depends on uninitialised value(s)
As I know jumping to memory based on what could be uninitialised variables is a bad thing. It seems possible that the tool is mistaken about the initialisation though.
---
Possibly related bugs from the old one were #1200934, #1200819 & #1383852. I can see now that Bug #1383852 is already marked as affecting me so perhaps this is a duplicate?
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: evolution-
Uname: Linux 4.1.0-040100rc8
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Oct 19 13:16:20 2015
ExecutablePath: /usr/lib/
ExecutableTimes
InstallationDate: Installed on 2015-03-12 (220 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: /usr/lib/
ProcCwd: /
Signal: 11
SourcePackage: evolution-
StacktraceTop:
g_hash_
ag_auth_
?? () from /usr/lib/
g_simple_
?? () from /usr/lib/
Title: evolution-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1200819, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.