Closed GoogleCodeExporter closed 9 years ago
Sounds like cancelling the download didn't kill off all the helper applications
(and
if those are currently running, it's impossible to successfully run more).
Oddly enough, hitting cancel OR quitting iTiVo is supposed to kill them all.
Start the 'activity monitor' (Applications/Utilities), and look for instances of
'curl', 'tivodecode', 'mencoder', and 'comskip'
If those are running, you should kill them, and I'll need to figure out why iTiVo
is failing to kill them itself. If none of those were running, then my guess is
wrong, and I have to figure out why it's failing anyways....
Original comment by yoav.yer...@gmail.com
on 7 Nov 2008 at 6:43
Hmm.. I just noticed that the code assumes that usernames are all-lowercase.
If you
open up a terminal and type
whoami
What username does it get (are there any uppercase letters in it or spaces?).
Changing the code to accept anything that is non-whitespace. I wonder if that
was
the bug
Original comment by yoav.yer...@gmail.com
on 7 Nov 2008 at 6:46
When I type whoami in the terminal it gives me my username which contains no
uppercase letters or spaces. So
that must not be the issue, at least in my case.
Original comment by smacdiarmid
on 7 Nov 2008 at 3:03
I may have figured it out. I was running the new version 1.3 off of my desktop
for testing purposes. Since I
moved it to my applications folder I have not had this issue yet. Could that
have been causing the problem?
Original comment by smacdiarmid
on 7 Nov 2008 at 3:35
I don't *think* it should cause problems, but at least I'm glad to see you got
it
fixed (I run temporary new version out of different locations without issue).
So
clearly something is up, but at least installing it fixes it.
I unfortunately can't reproduce this problem here. If it happens again, can you
open up a terminal.app and run
ps -jAww -o command | grep -e 'iTiVo.app'
and include the output? I want to try and figure out why it's not finding your
applications to kill..
Moving it to Priority-low for now since we have a 'workaround' and I can't work on
the bug until I can reproduce it.
Original comment by yoav.yer...@gmail.com
on 7 Nov 2008 at 4:42
assuming this hasn't happened since you 'installed' the app?
Marking it as 'fixed' I guess. if more people report this as an issue I'll just
add it to the faq.
Original comment by yoav.yer...@gmail.com
on 9 Nov 2008 at 6:02
Original issue reported on code.google.com by
smacdiarmid
on 7 Nov 2008 at 6:16