Bug 832391
| Summary: | [abrt] synapse-0.2.10-2.fc17: Process /usr/bin/synapse was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vilhjálmur Magnússon <villimagg> | ||||||||
| Component: | synapse | Assignee: | Renich Bon Ciric <renich> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | dkaylor, joe, michel, mtasaka, renich, tante, valent.turkovic | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:741c2598a0ef82fc53b008c3703e13dbe4e1bc64 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-08-01 18:48:55 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Vilhjálmur Magnússon
2012-06-15 09:59:32 UTC
Created attachment 592094 [details]
File: backtrace
Created attachment 592095 [details]
File: maps
Created attachment 592096 [details]
File: dso_list
I can just say me too, on Fedora 17. What broke synapse? Can you please revert to last working version ASAP? I have the same problem, it seems to be connected to the Synapse Zeitgeist plugin which crashes. You can as a workaround disable the plugin in synapse until it is fixed. If it helps, it is stable on 64bit systems, but crashes on 32bit. This is just my personal observation so maybe it is not same for everybody but maybe it helps track down this bug... Cannot confirm Valent's observation: With the Zeitgeist plugin enabled it crashes on my 64Bit box. I have the 64-bit version installed. With the Zeitgeist plugin enabled, it crashes. With the plugin disabled, it is stable. (In reply to comment #8) > I have the 64-bit version installed. With the Zeitgeist plugin enabled, it > crashes. With the plugin disabled, it is stable. Same here. Thanks for all the report -- I'll try and disable the Zeitgeist plugin by default for the next build. Crashes the moment I start typing something in Synapse. backtrace_rating: 4 Package: synapse-0.2.10-2.fc17 OS Release: Fedora release 17 (Beefy Miracle) What about troubleshooting the Zeitgeist plugin? No idea why it's causing the crash? This is because the libzeitgeist update that is needed to build synapse has not been marked as stable: https://admin.fedoraproject.org/updates/search/libzeitgeist and somehow libzeitgeist's upstream didn't do a soname bump, so synapse happily installs against an outdated version of a dependency. We're pushing the update now, so hopefully synapse should just work once that package makes it to the mirrors (In reply to comment #13) > This is because the libzeitgeist update that is needed to build synapse has > not been marked as stable: > > https://admin.fedoraproject.org/updates/search/libzeitgeist > > and somehow libzeitgeist's upstream didn't do a soname bump, so synapse > happily installs against an outdated version of a dependency. > > We're pushing the update now, so hopefully synapse should just work once > that package makes it to the mirrors Yes, this is the reason. Backtrace says: #0 0x0000000000000000 in ?? () <======================== No symbol table info available. #1 0x00000000004a5a3a in synapse_zeitgeist_plugin_process_results_co (_data_=0x18e27e0) at zeitgeist-plugin.c:1079 This suggests that functions to be called here could not be found. And actually with libzeitgeist-0.3.18 (used for building synapse 0.2.10), zeitgeist-plugin.c says: 1079 _data_->_tmp20_ = zeitgeist_subject_get_current_uri (_data_->_tmp19_); And rpmsodiff of libzeitgeist rpm says: $ rpmsodiff libzeitgeist-0.3.12-1.fc17.i686.rpm libzeitgeist-0.3.18-1.fc17.i686.rpm common sonames: libzeitgeist-1.0.so.1 /usr/lib/libzeitgeist-1.0.so.1.0.4 /usr/lib/libzeitgeist-1.0.so.1.1.4 --- libzeitgeist-0.3.12-1.fc17/libzeitgeist-1.0.so.1 2012-01-16 14:36:29.000000000 +0900 +++ libzeitgeist-0.3.18-1.fc17/libzeitgeist-1.0.so.1 2012-05-05 20:33:35.000000000 +0900 @@ -35,2 +35,3 @@ zeitgeist_event_get_manifestation T +zeitgeist_event_get_origin T zeitgeist_event_get_payload T @@ -49,2 +50,3 @@ zeitgeist_event_set_manifestation T +zeitgeist_event_set_origin T zeitgeist_event_set_payload T @@ -59,2 +61,4 @@ zeitgeist_index_search_finish T +zeitgeist_index_search_with_relevancies T +zeitgeist_index_search_with_relevancies_finish T zeitgeist_interpretation_for_mimetype T @@ -70,2 +74,3 @@ zeitgeist_log_find_related_uris_finish T +zeitgeist_log_get_default T zeitgeist_log_get_events T @@ -73,2 +78,3 @@ zeitgeist_log_get_type T +zeitgeist_log_get_version T zeitgeist_log_insert_events T @@ -104,2 +110,3 @@ zeitgeist_storage_state_get_type T +zeitgeist_subject_get_current_uri T <====================== zeitgeist_subject_get_interpretation T @@ -114,2 +121,3 @@ zeitgeist_subject_new_full T +zeitgeist_subject_set_current_uri T zeitgeist_subject_set_interpretation T Note that technically soname bump on libzeitgeist is _not_ needed, because just new symbols are added (this handling happens so common, e.g. on gtk2). However once you build synapse against new libzeitgeist, you must ensure that synapse gets installed with new libzeitgeist. Yeah, sorry to everybody. I forgot to push the updated libzeitgeist to stable. ;=s I'll pay more attention in the future. Sorry and thanks to Michel Alexandre Salim and all of you for helping so much. I will set the bug to "MODIFIED" until somebody confirms the fix. libzeitgeist-0.3.18-1 has been pushed to stable now. Expect it in the next repo sync. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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. so, any fix confirmations? Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |