Bug 890818

Summary: [abrt] streamtuner-2.0.8-9.fc17: streamtuner2:289:rowno:TypeError: iter should be a GtkTreeIter
Product: [Fedora] Fedora Reporter: Alexander <asd_wte>
Component: streamtunerAssignee: Matthias Haase <matthias_haase>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: matthias_haase
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5d64a6763776ef165720fdbd853d3360243a82f4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 03:37:47 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: executable
none
File: environ
none
File: smolt_data
none
File: core_backtrace none

Description Alexander 2012-12-30 13:01:08 UTC 
Description of problem:
Occured in streamturner2. The problem occured upon starting it and trying to play an online radio.

Version-Release number of selected component:
streamtuner-2.0.8-9.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
cmdline:        python /usr/bin/streamtuner2
kernel:         3.6.9-2.fc17.x86_64

backtrace:
:streamtuner2:289:rowno:TypeError: iter should be a GtkTreeIter
:
:Traceback (most recent call last):
:  File "/usr/bin/streamtuner2", line 308, in on_play_clicked
:    row = self.row()
:  File "/usr/bin/streamtuner2", line 293, in row
:    return self.channel().stations() [self.rowno()]
:  File "/usr/bin/streamtuner2", line 289, in rowno
:    return model.get_path(iter)[0]
:TypeError: iter should be a GtkTreeIter
:
:Local variables in innermost frame:
:model: <gtk.ListStore object at 0x10a9c050 (GtkListStore at 0x10b6bb20)>
:self: <StreamTunerTwo object at 0x2535320 (PyGladeXML at 0x2580d90)>
:iter: None

Potential duplicate bug: 768767
Comment 1 Alexander 2012-12-30 13:01:11 UTC 
Created attachment 670398 [details]
File: executable
Comment 2 Alexander 2012-12-30 13:01:14 UTC 
Created attachment 670399 [details]
File: environ
Comment 3 Alexander 2012-12-30 13:01:16 UTC 
Created attachment 670400 [details]
File: smolt_data
Comment 4 Alexander 2012-12-30 13:01:18 UTC 
Created attachment 670401 [details]
File: core_backtrace
Comment 5 Fedora End Of Life 2013-07-04 00:11:00 UTC 
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.
Comment 6 Fedora End Of Life 2013-08-01 03:37:51 UTC 
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.