Bug 701548

Summary: [abrt] taskcoach-1.0.3-2.fc14: _core.py:3917:Bind:AssertionError
Product: [Fedora] Fedora Reporter: David Kovalsky <dkovalsk>
Component: taskcoachAssignee: Rakesh Pandit <rakesh.pandit>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: benl, martin.nyhus, oleg, waltsaw
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:42c37ae4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:09: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:
Attachments:
Description Flags
File: backtrace none

Description David Kovalsky 2011-05-03 08:05:20 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 2938 bytes
cmdline: /usr/bin/python /usr/bin/taskcoach
component: taskcoach
executable: /usr/bin/taskcoach
kernel: 2.6.35.12-88.fc14.x86_64
package: taskcoach-1.0.3-2.fc14
reason: _core.py:3917:Bind:AssertionError
release: Fedora release 14 (Laughlin)
time: 1304409846
uid: 10625

How to reproduce
-----
1. Double-click on on a task with one subtask, just as about a gazilion times in the past
2. Notice that Abrt comes up. But Task Coach is up and seems functioning
3. At this point and time, the issue is 100% reproducible.

Comment 1 David Kovalsky 2011-05-03 08:05:23 UTC
Created attachment 496444 [details]
File: backtrace

Comment 2 David Kovalsky 2011-05-04 21:15:25 UTC
Looking into this further, clicking any task which has subtasks triggers this. This makes parent tasks uneditable. 

FYI - I've tried updating to taskcoach-1.2.6-2.fc15.noarch from F15 and that work like charm. Any chance giving Fedora 14 latest upstream version?

Comment 3 Martin Nyhus 2011-05-24 18:32:49 UTC
Package: taskcoach-1.0.3-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Crash happened when I double clicked on a task that had sub tasks

Comment 4 David Kovalsky 2011-05-24 21:11:46 UTC
Just a quick report back - I have a fairly large task setup and with the F15 version I mentioned in comment #2 everything still works like charm. 

I haven't seen any regressions, and on the plus side - 1.2 has many new nice features like dependencies.

Comment 5 Walt 2011-05-29 03:25:40 UTC
Package: taskcoach-1.0.3-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Normal operation
2.edit task
3.crash

Comment 6 Oleg Tsarev 2011-08-02 16:17:27 UTC
Package: taskcoach-1.0.3-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I just edit my tasks and get crash
2.
3.

Comment 7 Fedora End Of Life 2012-08-16 15:09:36 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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