Bug 594482

Summary: [abrt] crash in telepathy-butterfly-0.5.9-1.fc12: transport.py:471:__extract_command:ValueError: need more than 1 value to unpack
Product: [Fedora] Fedora Reporter: Theophanis Kontogiannis <theophanis_kontogiannis>
Component: telepathy-butterflyAssignee: Brian Pepple <bdpepple>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: afarrag, bdpepple, b.hardill, bobkaiser1, felibank, hackob, mkhakheria, sander, simon.marillet
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:b1e0e269
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 14:31:06 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 Flags
File: backtrace none

Description Theophanis Kontogiannis 2010-05-20 19:37:48 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
cmdline: /usr/bin/python /usr/libexec/telepathy-butterfly
component: telepathy-butterfly
executable: /usr/libexec/telepathy-butterfly
kernel: 2.6.32.12-115.fc12.x86_64
package: telepathy-butterfly-0.5.9-1.fc12
reason: transport.py:471:__extract_command:ValueError: need more than 1 value to unpack
release: Fedora release 12 (Constantine)

backtrace
-----
transport.py:471:__extract_command:ValueError: need more than 1 value to unpack

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/papyon/transport.py", line 457, in __on_received
    commands = self.__extract_command(commands)
  File "/usr/lib/python2.6/site-packages/papyon/transport.py", line 471, in __extract_command
    first, rest = data.split('\r\n', 1)
ValueError: need more than 1 value to unpack

Local variables in innermost frame:
self: <HTTPPollConnection object at 0x1b3a050 (papyon+transport+BaseTransport at 0x1b7ea60)>
data: '<html>\n<head><title>Error 303: Hotspot login required</title></head>\n<body>\n<h1>Error 303: Hotspot login required</h1>\n</body>\n</html>\n'

How to reproduce
-----
1. it just crashed... 
2.
3.

Comment 1 Theophanis Kontogiannis 2010-05-20 19:37:51 UTC
Created attachment 415496 [details]
File: backtrace

Comment 2 Bob 2010-06-10 04:15:42 UTC
Package: telepathy-butterfly-0.5.10-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
As you can see from the data, Hughesnet satellite ISP had a connection problem.  We are having heavy rain storms currently.  The Preferences have the Network Proxy set to a direct connection.  The proxy was not using the web accelerator.

From Hughesnet: <TITLE>Web Acceleration Client Error (504) - Suspected Satellite Link Outage</TITLE><B><font face=arial color=#3642a2>Web Acceleration Client Error (504) - Suspected Satellite Link Outage</font></B><font style=normal face=arial size=2px><P>The satellite link was not operational when the last web page request was made. Possible causes for this include recent changes in weather conditions or equipment problems in the Network Operations Center. Trying again at a later time may result in restored service due to either improvements in the weather conditions causing the service outage or rectification of a network problem in the Network Operations Center. If this problem persists, please contact your service provider for additional assistance.</P> </font>'

Comment 3 Bob 2010-06-11 14:29:24 UTC
Package: telepathy-butterfly-0.5.10-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
Another example of Hughesnet satellite trouble.  It was unable to keep up with the load and returned an error message.

Comment 4 Bob 2010-06-28 07:44:58 UTC
Package: telepathy-butterfly-0.5.11-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.probably received error message from Hughesnet satellite ISP.
2.
3.


Comment
-----
Was on Hughesnet satellite connection with very slow response and intermittent connectivity.

Comment 5 simon.marillet 2010-07-01 19:16:36 UTC
Package: telepathy-butterfly-0.5.11-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.open telepathy
2.hibernate the computer
3.wake-up the computer


Comment
-----
I tried a second time and it crashed too.

Comment 6 Benjamin Hardill 2010-10-25 08:43:49 UTC
Package: telepathy-butterfly-0.5.9-1.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1. Just running Empathy
2.
3.

Comment 7 Bug Zapper 2010-11-03 14:30:53 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2010-12-03 14:31:06 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.