Bug 531464
| Summary: | [abrt] crash detected in telepathy-butterfly-0.5.1-1.fc12 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ailton Jr <ailtonjr.ce> | ||||||
| Component: | telepathy-butterfly | Assignee: | Brian Pepple <bdpepple> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 12 | CC: | aaron.j.brown, address.celeste, alejo2q, alessandromachado.vip, alexander.l.hansen, alex.brooks-2ofy9ljg, amontandon, anders_juel, andreas.tunek, antenna-5, artemio.silva, asiminski, asterix314, ataliba, bdpepple, benjavalero, bionikiu, bjmeany, blemidon, bobpoljakov, brian, bugzilla, camelmovie, carlg, caverslug, chipi_vk, chris, chris, claudiorodrigo, coutinho.sanches, crozes.kevin, crzand, dalinhuang, darwall, dexapier, diogofcaseca, donkishoot, doom_ii, dreamervocal, duka34, dwmw2, eduard0.ec0, engle_mars, excranium, fade, fanzorro, felip_assis, felipeeg10, flama.es, francesco.carrozzo, fraph24, freddylefloch, fredladeroute, futhark77, gaperez64, giancarlogiesa, gileadeg, g_mignacio, h3xstream.0, hackob, halon.by, hawks.junior, hdl645, itvend, jackonweb, jefftaylor42, jhonny.oliveira, jhwhbd, jimmyb, jmenendez, john.mccalpin, joostvandorp, kanelxake, kchoi, lacintra.michael, linuxnow, lnx.tomas, loki1984, luzemail, malfax, mangelp, manuelrrojas, marc166, marcusdean.adams, markos30, matteopacini.informatica, matteo.pasotti, mbuschman, metaska, mhyp666, micheleqa, miguelmorimoreira, MisRegistros001, mkapos, mkhakheria, nabof, nicholasp83, noah.swint, oswaldo, pantelis.fedora, ph.autom, privat, putramuzhafar.biz, qmin77, quetzalcoatl_99, rafepren, redhat, renich, richard, rippeltippel, r.michael.bleam, robbieb3, rudd-o, sanabria.d, sander, shining_burning_gundum, snicore, statik_g, stephane.maniaci, steven.will, sweester, tcfxfzoi, teoblues, teoman.onay, thomas, thunderbirdtr, tncarrolls, toofdetreg, tsinik.subscriptions, volans2000, wan_jinxue, webmaster, wengole, wesley.massuda, wilson.an, wizzardx6, wjstarrsiii, xoxxyy, yaniv4345, yaozhanp, ymainguy, yn.abid, zaterio | ||||||
| Target Milestone: | --- | Keywords: | Reopened, Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | abrt_hash:4ab1453d | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-12-04 03:38:33 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
Ailton Jr
2009-10-28 13:44:28 UTC
Created attachment 366436 [details]
File: backtrace
Can you recreate this bug using the new version of tp-butterfly in bodhi? You can install with the following command: yum --enablerepo=updates-testing update telepathy-butterfly This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Haven't heard back in 3 weeks whether this bug is present in the latest tp-butterfly (0.5.3-1). Closing as NOTABUG. Please re-open if this is not true. Just got this bug through ABRT, and reported it, got directed to this bug entry. I am not sure what caused this - possibly someone trying to send me an offline message on MSN. Name : telepathy-butterfly Arch : noarch Version : 0.5.3 Release : 2.fc12 I am running Fedora 12, all current updates applied. And x86_64 arch. This happens here often when connection problems occur. I'm on mobile broadband and the quality could definitely be better here. Yeah, but a program shouldn't crash, just because the internet connection went down. Not normal... I see the bug solved as "notabug".... How to reproduce ----- 1. launch empathy 2. wait for an msn account to connect 3. Comment ----- Launch empathy, connect with a msn account. The bug seems to unaffect the execution at all How to reproduce ----- 1. Start empathy 2. Follow wizard for adding my MSN account 3. Wait a little.... connected... wait a moment... this error How to reproduce ----- 1. Happens on Startup 2. 3. Comment ----- I have no idea how this happened... How to reproduce ----- 1. Open Empathy. 2. Login with MSN account. Comment ----- Bug occurred as Empathy started up at Gnome login and started to log into the various IM services. How to reproduce ----- a contact started a conversation with me How to reproduce ----- 1. Launch 2. 3. How to reproduce ----- 1. Open Empathy 2. The bug message appears Comment ----- I opened Empathy and suddenly the automatic bugreport message appears. Nothing else happened. How to reproduce ----- 1. Start Empathy. 2. 3. How to reproduce ----- How to reproduce ----- 1. Wait 2. 3. How to reproduce ----- 1. try to login to msn 2. 3. I'm getting this from the debug window of telephaty : stderr-ERREUR: 1,269843e+09: /usr/lib/python2.6/site-packages/butterfly/handle.py:56: DeprecationWarning: object.__new__() takes no parameters stderr-ERREUR: 1,269843e+09: instance = object.__new__(cls, connection, *args) stderr-ERREUR: 1,269843e+09: Traceback (most recent call last): stderr-ERREUR: 1,269843e+09: File "/usr/lib/python2.6/site-packages/papyon/switchboard_manager.py", line 81, in <lambda> stderr-ERREUR: 1,269843e+09: lambda sb, command: self.__on_message_undelivered(command)) stderr-ERREUR: 1,269843e+09: File "/usr/lib/python2.6/site-packages/papyon/switchboard_manager.py", line 154, in __on_message_undelivered stderr-ERREUR: 1,269843e+09: MessageError.DELIVERY_FAILED) stderr-ERREUR: 1,269843e+09: File "/usr/lib/python2.6/site-packages/papyon/switchboard_manager.py", line 125, in _on_error stderr-ERREUR: 1,269843e+09: raise NotImplementedError stderr-ERREUR: 1,269843e+09: NotImplementedError Changed the component back to telepathy.. my bad. Package: telepathy-butterfly-0.5.9-1.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. It happned while my status set to away 2. Does not happen while I am using pidgin 3. Comment ----- I am tired of this same bug over and over, I have switched to Pidgin for IM In FC13 always crash !!! Just got the same crash here by having Empathy running in the background, have no clue what happened. What is required for this bug to be reopened as it seems like people can reproduce and are redirected here by ABRT to a bug I in Fedora13 cannot get ABRT to add comments to because it is closed? This also blocks ABRT from adding which versions that crashes to the bugreport. Still occurs with latest updates in Fedora 13. Why is this bug marked WONTFIX? (In reply to comment #25) > Just got the same crash here by having Empathy running in the background, have > no clue what happened. What is required for this bug to be reopened as it seems > like people can reproduce and are redirected here by ABRT to a bug > This also blocks ABRT from adding which versions that crashes to the bugreport. Fill a bug upstream since i believe Brian Pepple is only in charge of packaging Empathy for Fedora. rpm -q telepathy-butterfly > I in Fedora13 cannot get ABRT to add comments to because it is closed? That's the point. (In reply to comment #27) > > Fill a bug upstream since i believe Brian Pepple is only in charge of packaging > Empathy for Fedora. > > rpm -q telepathy-butterfly > I have currently not the time, but I still cannot see why this bug is closed as wontfix as the issue still is there, an no motivation whatsoever to why it will not be fixed is done. > > I in Fedora13 cannot get ABRT to add comments to because it is closed? > > That's the point. So the point of a bugreport is to _NOT_ follow a issue and see if it still exists? Maybe someone got tired of all the bugspam ABRT makes, but closing the bug as wontfix just because the maintainer do not have the time or will to go upstream himself/herself does feel a bit wrong. > So the point of a bugreport is to _NOT_ follow a issue and see if it still
> exists? Maybe someone got tired of all the bugspam ABRT makes, but closing the
> bug as wontfix just because the maintainer do not have the time or will to go
> upstream himself/herself does feel a bit wrong.
The point of a bug report is to give and receive feedback to / from the developer(s) concerning a particular issue (bug, feature request etc..). Since this bug report have been opened on the 2009-10-28, and the only reply by Brian Pepple was on the 2009-11-14, i think it was appropriate to close it.
This bug report *should* have been reported a while ago upstream but unfortunately it wasn't.
We currently have 104 users CC'ed on this bug report and leaving it open, when the backtrace is complete and it's marked as "triaged" only generate more unnecessary traffic. Feel free to manually add the version of telepathy-butterfly.
The status is currently CLOSED - WONTFIX. Closing it was intended for ABRT to avoid adding CCs. Yes, I agree CLOSED WONTFIX isn't the proper solution to such a problem, but Bugzilla fails to provide a solution that is less inappropriate than that for closing issues that maintainers cannot seem to keep up with.
I'm *not* going to re-open this bug report unless it's filled upstream. Furthermore, if the maintainer does not have time to maintain a relationship with upstream, they should be looking for a co-maintainer who is willing to handle such issues.
Package: telepathy-butterfly-0.5.11-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)
How to reproduce
-----
1. start Empathy 2.30.2
2. crash is immediate
3.
Comment
-----
Messages in /var/log/messages don't seem to add any useful info:
Jul 14 10:09:37 mccalpin-d630 python: abrt: detected unhandled Python exception in /usr/libexec/telepathy-butterfly
Jul 14 10:09:37 mccalpin-d630 abrtd: Directory 'pyhook-1279120177-2664' creation detected
Jul 14 10:09:37 mccalpin-d630 abrt[2676]: saved python crash dump of pid 2664 to /var/cache/abrt/pyhook-1279120177-2664.new
Jul 14 10:09:38 mccalpin-d630 abrtd: New crash /var/cache/abrt/pyhook-1279120177-2664, processing
Jul 14 10:09:38 mccalpin-d630 abrtd: Registered Action plugin 'RunApp'
Jul 14 10:09:38 mccalpin-d630 abrtd: RunApp('/var/cache/abrt/pyhook-1279120177-2664','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
Jul 14 10:09:42 mccalpin-d630 abrtd: Getting crash infos...
Package: telepathy-butterfly-0.5.11-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Start Empathy 2. 3. Package: telepathy-butterfly-0.5.9-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. 2. 3. Comment ----- using Empathy with MSN, happens periodically Package: telepathy-butterfly-0.5.11-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- started program Package: telepathy-butterfly-0.5.11-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open Empathy 2. Crash of this module occurrs 3. Package: telepathy-butterfly-0.5.7-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Start the system for the first time. 2.Click the red siren icon in the tray. 3.Be informed of error by ABRT tool. Comment ----- Default configuration. In my experience this no longer happens in 0.5.11-1.fc13. Update your systems. Package: telepathy-butterfly-0.5.11-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Just use telepathy with MSN account 2.When open Telephaty bugs appears...changing to pidgin 3.Telepathy really Sucks Package: telepathy-butterfly-0.5.11-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start Application, I've configured 3 account: MSN, ICQ and gtalk 2. waiting few seconds Package: telepathy-butterfly-0.5.11-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open Telepathy and connect with some msn account 2. Wait 3. Abrt shows up with a report, eventually. Comment ----- Simply use telepathy with an msn account and wait. Continues happening to me in F13. (In reply to comment #1) > Created an attachment (id=366436) [details] > File: backtrace Looking into the backtrace, it seems that the problem is in "papyon". -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Package: telepathy-butterfly-0.5.11-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- The message appeared in the notification window Package: telepathy-butterfly-0.5.7-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- i don't know what happens. Created attachment 439910 [details]
Doesn't raise NotImplementedError
The program couldn't manage the custom error "NotImplementedError". So, I've simply replaced "raise NotImplementedError" with "pass". So, every error that cannot be handled by the switchboard manager, is ignored :D
You can apply the patch with: su -c "patch -p1 /usr/lib/python2.6/site-packages/papyon/switchboard_manager.py ~/switchboard_manager.py.diff -R" Yes, it's really a simple and stupid patch, but I don't want to see everytime abrt warning me about it :D Package: telepathy-butterfly-0.5.9-1.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- doing nothing. Package: telepathy-butterfly-0.5.9-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Launch empathy 2. Send a message containg link to a contact 3. Wait some sec 4. Close the chat dialog Comment ----- I've just launched empathy and sent a link to a contact, waited some sec and then closed the window This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. |