Always asking to accept incoming network connections

Free flexible open source todo manager featuring hierarchical tasks

Brought to you by: fraca7, wolftune

This project can now be found here.

#1506 Always asking to accept incoming network connections

Status: closed

Owner: Jérome Laheurte

Labels: None

Operating system: macosx

Updated: 2026-01-20

Created: 2014-03-29

Creator: Tobi

Private: No

(Actually I’m unsung the news version which is 1.3.37, but there’s no milestone for it yet)

It seems to be a bug of TaskCoach, that at every launch the question about accepting incoming network connections. As far as I can tell it’s a problem with TaskCoach’s signature (see https://community.activestate.com/node/9804 or http://stackoverflow.com/q/17527700/1018250 for example). The output of codesign -vv /applications/taskcoach.app is

/applications/taskcoach.app: a sealed resource is missing or invalid
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/__init__.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/_parseaddr.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/base64mime.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/charset.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/encoders.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/errors.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/generator.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/header.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/iterators.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/message.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/mime/__init__.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/quoprimime.pyo
file modified: /Applications/TaskCoach.app/Contents/Resources/lib/python2.7/email/utils.pyo

I hope you can fix this :-)

Discussion

Jérome Laheurte - 2014-03-30

assigned_to: Jérome Laheurte

First version affected: Release_1.3.36 --> Release_1.3.37
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jérome Laheurte - 2014-03-30

A fix was made and checked into the source code repository of Task Coach. The fix will be part of the next release. You will get another notification when that release is available with the request to install the new release and confirm that your issue has indeed been fixed.

If you like, you can download a recent build from http://www.fraca7.net/TaskCoach-packages/latest_bugfixes.py to test the fix.

Because a fix has been made for this bug report, the priority of this report has been lowered to 1 and its resolution has been set to 'Fixed'.
Thanks, Task Coach development team

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tobi - 2014-03-30

Thanks, it seems to work fine :-) is ist “save” to use the experimental build or is it better to wait for the next official release?

I got another question, which is not really a bug: TaskCoach ist very slow, it takes a few seconds to start/stop the timer. I’m not sure if it is possible to improve on this, but think this problem was not so bad with older versions. And is there a reason that TaskCoach doesn’t support click-through anymore?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jérome Laheurte - 2014-03-30

It's pretty safe, we don't do much dangerous things in this branch.

Performance highly depends on your setup. For instance, the calendar view is a huge resource hog...

What do you mean by click-through ?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tobi - 2014-03-30

Performance highly depends on your setup. For instance, the calendar view is a huge resource hog…

In my view I have only the taks tree and the category window. My MacBook uses a SSD drive an 16 GB RAM, so I can’t imagine performance issues caused by my setup …

What do you mean by click-through?

I mean that the icons are click-able even when the window is inactive. At the moment the first click activates the window and the second click triggers the button. On OSX there are some apps that support that and other that don’t. E.g. Safari does while Mail doesn’t

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jérome Laheurte - 2014-03-30

I tackle performance issues from time to time but it's not easy :)

As for click-through, I don't think we have this level of control through the toolkit we use for windowing (wx). It probably disappeared after an upgrade of said toolkit.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tobi - 2014-03-30

I tackle performance issues from time to time but it's not easy :)

Great :-)

As for click-through, I don't think we have this level of control through the toolkit we use for windowing (wx). It probably disappeared after an upgrade of said toolkit.

Ok, thats possible. I can live without click-trouhg but is sometime click to often because the delays feedback of the app …

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jérome Laheurte - 2014-04-21

This bug should be fixed in the latest release of Task Coach. Can you please install the latest release of Task Coach and confirm that this bug has indeed been fixed?

Thanks, Task Coach development team

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tobi - 2014-04-22

Seems to work. Thanks!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jérome Laheurte - 2014-04-23

status: fixed-and-released --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tobi - 2016-11-30

Hi, this bug seems to reappear in the current version (1.4.3 – January 31, 2016). Could you pleas take a look at it.

My Setup:

MacBook Pro, SSD, 16 GB Ram

OS X 10.11.6
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.