search

bruno1505 / pyetv

Automatically exported from code.google.com/p/pyetv
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Pye TV won't work on Mac OS Leopard 10.5.7 #26

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. update to 10.5.7
2. run front row

What is the expected output? What do you see instead?

Front row will not start with the pyetv frappliance installed, as soon as I
remove it front row starts and works perfectly but of course without the
pyetv plugin.
I tried every version since 3.0.1 and can safely rule out eyetv is causing
this problem, it did work before on 10.5.5

What version of the product are you using? On what operating system?

Mac Mini 2009 better
OS X Leopard 10.5.7
EyeTV 3.1.0 (3.1.1 is broken even on 10.5.5)
Pyetv 1.2

Please provide any additional information below.

Boxee and understudy do work so it's not a python problem, it must be in
the script itself.

Original issue reported on code.google.com by ilja.spierings@gmail.com on 20 May 2009 at 12:42

GoogleCodeExporter commented 8 years ago 
That's odd...it works for me.  I'll look into it.

Original comment by jon.chri...@gmail.com on 20 May 2009 at 3:40

GoogleCodeExporter commented 8 years ago 
I installed the python package for mac and this is prove python actually runs:

Last login: Wed May 20 17:03:54 on ttys000
iSPs-Mac-Mini:~ iSP$ python
Python 2.5.1 (r251:54863, Feb  6 2009, 19:02:12) 
[GCC 4.0.1 (Apple Inc. build 5465)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> 2+2
4
>>> 

not sure if it's any help but it's the last thing I could think of.

Original comment by ilja.spierings@gmail.com on 20 May 2009 at 5:02

GoogleCodeExporter commented 8 years ago 
I have OSX 10.5.7 and EyeTV 3.1.1 (4916) and PyeTV 1.2 ... and they "work" with 
the
same "faults" described in the other thread 

(waiting for Applescript fix ...)

Original comment by edward.g...@gmail.com on 27 May 2009 at 4:23

GoogleCodeExporter commented 8 years ago 
[ other thread = http://code.google.com/p/pyetv/issues/detail?id=22 ]

Original comment by edward.g...@gmail.com on 27 May 2009 at 4:24

GoogleCodeExporter commented 8 years ago 
What messages are in the console.log or the system.log when you try to start 
Front Row?

Original comment by jon.chri...@gmail.com on 29 May 2009 at 11:31

GoogleCodeExporter commented 8 years ago 
These are the errors I get:

May 30 15:58:43 iSPs-Mac-Mini com.apple.launchd[145] (com.apple.quicklook):
Throttling respawn: Will start in 4 seconds
May 30 15:59:00 iSPs-Mac-Mini authexec[4645]: executing
/System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
May 30 15:59:00 iSPs-Mac-Mini authexec[4647]: executing
/System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
May 30 15:59:01 iSPs-Mac-Mini authexec[4649]: executing
/System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
May 30 15:59:59 iSPs-Mac-Mini FrontRow[4665]: ******** Application Startup 
********
May 30 16:00:04 iSPs-Mac-Mini ReportCrash[4667]: Formulating crash report for 
process
Front Row[4665]
May 30 16:00:04 iSPs-Mac-Mini ReportCrash[4667]: Saved crashreport to
/Users/iSP/Library/Logs/CrashReporter/Front 
Row_2009-05-30-160003_iSPs-Mac-Mini.crash
using uid: 501 gid: 20, euid: 501 egid: 20
May 30 16:00:04 iSPs-Mac-Mini com.apple.launchd[145] (com.apple.RemoteUI[4665]):
Exited abnormally: Segmentation fault
May 30 16:00:04 iSPs-Mac-Mini com.apple.launchd[145] (com.apple.RemoteUI): 
Throttling
respawn: Will start in 5 seconds
May 30 16:00:09 iSPs-Mac-Mini FrontRow[4669]: ******** Application Startup 
********
May 30 16:00:11 iSPs-Mac-Mini ReportCrash[4667]: Formulating crash report for 
process
Front Row[4669]
May 30 16:00:11 iSPs-Mac-Mini ReportCrash[4667]: Saved crashreport to
/Users/iSP/Library/Logs/CrashReporter/Front 
Row_2009-05-30-160010_iSPs-Mac-Mini.crash
using uid: 501 gid: 20, euid: 501 egid: 20
May 30 16:00:11 iSPs-Mac-Mini com.apple.launchd[145] (com.apple.RemoteUI[4669]):
Exited abnormally: Segmentation fault
May 30 16:00:11 iSPs-Mac-Mini com.apple.launchd[145] (com.apple.RemoteUI): 
Throttling
respawn: Will start in 8 seconds
May 30 16:00:19 iSPs-Mac-Mini FrontRow[4670]: ******** Application Startup 
********

This repeats itself until I remove pyetv

Original comment by ilja.spierings@gmail.com on 30 May 2009 at 2:03

GoogleCodeExporter commented 8 years ago 
> May 30 16:00:04 iSPs-Mac-Mini ReportCrash[4667]: Formulating crash report for 
process
Front Row[4665]

What's in that crash report?

Original comment by jon.chri...@gmail.com on 30 May 2009 at 2:44

GoogleCodeExporter commented 8 years ago 
Where can I find this crash report? it's not in system profiler.

Original comment by ilja.spierings@gmail.com on 30 May 2009 at 6:38

GoogleCodeExporter commented 8 years ago 
nvm, this should be it:

Process:         Front Row [4681]
Path:            /System/Library/CoreServices/Front 
Row.app/Contents/MacOS/Front Row
Identifier:      com.apple.frontrow
Version:         2.1.7 (2.1.7)
Build Info:      FrontRow-3090000~2
Code Type:       X86 (Native)
Parent Process:  launchd [145]

Date/Time:       2009-05-30 16:01:01.968 +0200
OS Version:      Mac OS X 10.5.7 (9J61)
Report Version:  6
Anonymous UUID:  25B93280-14D1-4318-95F0-C1D883EE1EDC

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000009d14fee0
Crashed Thread:  0

Thread 0 Crashed:
0   ???                             0x06cd10cc 0 + 114102476
1   ???                             0x06cc44d3 0 + 114050259
2   ???                             0x06cc41c9 0 + 114049481
3   ???                             0x06cd7c6e 0 + 114130030
4   ???                             0x06cd7e6a 0 + 114130538
5   ???                             0x06cd7ec6 0 + 114130630
6   ???                             0x06ce5e6e 0 + 114187886
7   ???                             0x06ce6174 0 + 114188660
8   ???                             0x02479725 0 + 38246181
9   ???                             0x02479996 0 + 38246806
10  ???                             0x1a98b855 0 + 446216277
11  ???                             0x1a98bd6c 0 + 446217580
12  ???                             0x1a9a2825 0 + 446310437
13  ???                             0x1a9b9b63 0 + 446405475
14  ???                             0x191ccd3d 0 + 421317949
15  ???                             0x1923ab1a 0 + 421767962
16  ???                             0x1923c45b 0 + 421774427
17  ???                             0x191e6c27 0 + 421424167
18  ???                             0x191ccd3d 0 + 421317949
19  ???                             0x1a99c6d5 0 + 446285525
20  ???                             0x1a98ba92 0 + 446216850
21  ???                             0x024280d4 0 + 37912788
22  ???                             0x02427f5c 0 + 37912412
23  ???                             0x02427df6 0 + 37912054
24  ???                             0x000030da 0 + 12506
25  ???                             0x00003017 0 + 12311
26  ???                             0x00002b1f 0 + 11039
27  ???                             0x0009e94e 0 + 649550

Thread 1:
0   ???                             0x030ef286 0 + 51311238
1   ???                             0x030f6a7c 0 + 51341948
2   ???                             0x034b104e 0 + 55251022
3   ???                             0x034b1cd4 0 + 55254228
4   ???                             0x1a7e5a60 0 + 444488288
5   ???                             0x03120155 0 + 51511637
6   ???                             0x03120012 0 + 51511314

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x9d14fee0  ebx: 0x06cd0fea  ecx: 0x00000000  edx: 0x1b5029a0
  edi: 0xbfffe5f0  esi: 0x8fe310a8  ebp: 0xbfffe528  esp: 0xbfffe4d0
   ss: 0x0000001f  efl: 0x00010292  eip: 0x06cd10cc   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0x9d14fee0

Binary Images:
0x8fe00000 - 0x8fe298a3  dyld 0.0 (???) <d1092af4e89e77aa121dd5fb0c855cd9> 
/usr/lib/dyld

Original comment by ilja.spierings@gmail.com on 30 May 2009 at 6:40

GoogleCodeExporter commented 8 years ago 
I never could reproduce this issue and 10.5.8 is now out anyway.

Original comment by jon.chri...@gmail.com on 18 Aug 2009 at 5:16