Bug 836499
| Summary: | [abrt] telepathy-gabble-0.16.1-1.fc17: tp_base_channel_close: Process /usr/libexec/telepathy-gabble was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Torsten Ebbecke <TEbbecke> | ||||||||
| Component: | telepathy-gabble | Assignee: | Brian Pepple <bdpepple> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | abhaykadam88, bdpepple, sander | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:e99589c776abe76b1cda97ab3c7dcc443464a546 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-07-31 18:52:19 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
Torsten Ebbecke
2012-06-29 09:51:05 UTC
Created attachment 595242 [details]
File: backtrace
Created attachment 595243 [details]
File: maps
Created attachment 595244 [details]
File: dso_list
Since adding my Google account, Gnome has crashed twice - the first time when attempting to access my calendar, the second when attempting to log in to chat. I wonder if it is to do with my account using 2-step authentication? Empathy asked for a password even though I had already signed in using the online accounts method, that doesn't seem like the desired behaviour. backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) XMPP fails to connect backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) software tried to reconnect after resume from ram or something like that backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) I connected my iphone and unlocked my screen backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) i happen again and again after suspending backtrace_rating: 3 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) This bug occurred when trying to login into MSN, gmail and facebook chat accounts, via Empathy messenger. backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) $ while [ 1 ]; do mc-tool enable salut/local_xmpp/account1; sleep 1; mc-tool disable salut/local_xmpp/account1; done yes, I was disabling a non-related account in a loop trying to trigger other error ;) (namely, bug #827083 ) backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) quickly disabling/enabling a google chat account, i think. backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Happened just after I logged in backtrace_rating: 3 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Tried to sign into GTalk. backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Connection los, i clicked on reconnect backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) There was a network problem, then when empathy tried to reconnect it crashed. I get these errors most of the time backtrace_rating: 3 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Click on "Reconnect" button on a Connection error pop-up for a GMail account backtrace_rating: 3 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) 1. executed 'mc-tool request gabble/jabber/(username obscured) available' 2. launched empathy. backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) I'll assume it was something to do with mDNS cht. backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) I have configured three Online Accounts; one facebook and two gmail accounts (one @gmail.com and one private domain) On opening Empathy, it requests me to provide a password, I provide the correct password for both accounts Empathy tried to connect several times, not succeeding on any of the attempts. backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) A network disconnect happened (Wi-Fi hiccup). All accounts disconnected and reconnected. backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Resumed from suspend. backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) waking up from standy backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) I resumed my machine from suspend and then used the gnome-shell to set my status to "available". I got the crash soon afterwards. backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Restarted wireless network connection. backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) auto generated by os backtrace_rating: 4 Package: telepathy-gabble-0.16.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) 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. 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. |