Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 590611 - [abrt] crash in telepathy-butterfly-0.5.7-1.fc12: list index out of range
Summary: [abrt] crash in telepathy-butterfly-0.5.7-1.fc12:
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-butterfly
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:51b29afd
: 599577 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-10 10:19 UTC by tk01
Modified: 2010-12-03 14:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-03 14:52:02 UTC

Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-10 10:19 UTC, tk01
no flags Details

Description tk01 2010-05-10 10:19:03 UTC
abrt 1.0.9 detected a crash.

architecture: i686
cmdline: /usr/bin/python /usr/libexec/telepathy-butterfly
component: telepathy-butterfly
executable: /usr/libexec/telepathy-butterfly
package: telepathy-butterfly-0.5.7-1.fc12
reason: list index out of range
release: Fedora release 12 (Constantine)

----- list index out of range

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/papyon/msnp/", line 107, in _dispatch_command
  File "/usr/lib/python2.6/site-packages/papyon/msnp/", line 500, in _handle_UBX
    cm = (parts[4].encode("utf-8"), parts[5].encode("utf-8"))
IndexError: list index out of range

Local variables in innermost frame:
account: ''
cm: <Element 'CurrentMedia' at 0x8767cc8>
idx: 2
network_id: 1
self: <NotificationProtocol object at 0x868baa4 (papyon+msnp+notification+NotificationProtocol at 0x86ba910)>
tree: <Element 'Data' at 0x86a0c50>
parts: [u'Winamp', u'Music', u'1', u'\u591c\u660e\u3051\u306e\u5c11\u5973\u305f\u3061 (??? ???) / lubinn', u'']
command: <papyon.msnp.command.Command object at 0x86a42cc>

Comment 1 tk01 2010-05-10 10:19:05 UTC
Created attachment 412784 [details]
File: backtrace

Comment 2 Brian Pepple 2010-06-03 14:40:02 UTC
*** Bug 599577 has been marked as a duplicate of this bug. ***

Comment 3 Bug Zapper 2010-11-03 15:12:30 UTC
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:

Comment 4 Bug Zapper 2010-12-03 14:52:02 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.