Closed GoogleCodeExporter closed 9 years ago
could you provide me a full XBMC DEBUG log? It should hold more info. Please
note
that it should be a DEBUG log, not a normal log.
Original comment by basrie...@gmail.com
on 2 Apr 2008 at 9:32
hmmm where to find debug log.. i guess this the normal log attached...
however i tried another xbmc version (XBMC SVN 2008-03-23 (23rd of March 2008)
rev12263) but with the same problem
Original comment by davez...@gmail.com
on 2 Apr 2008 at 10:24
Attachments:
No, that is not a debug log. See here on more info on debug logging:
http://xbmc.org/wiki/?title=HOW-TO_Submit_a_Proper_Bug_Report#Logs_and_debug-log
_files
Original comment by basrie...@gmail.com
on 3 Apr 2008 at 6:47
ok i ill check when i get back home
Original comment by davez...@gmail.com
on 3 Apr 2008 at 7:52
this is the relevant part i guess... a global that is not defined:
19:09:30 M: 37183488 DEBUG: ParentPath = [Q:\scripts]
19:09:30 M: 37183488 INFO: Loading skin file: DialogProgress.xml
19:09:30 M: 37183488 DEBUG: Load DialogProgress.xml: 65.35ms (60.19 ms xml
load)
19:09:31 M: 35614720 DEBUG: Alloc resources: 4.38ms (0.01 ms skin load, 0.36
ms
preload)
19:09:31 M: 35225600 INFO: Traceback (most recent call last):
19:09:31 M: 35225600 INFO: File "Q:\scripts\XOT-Uzg.v3\default.py", line
111, in ?
19:09:31 M: 35225600 INFO:
19:09:31 M: 35225600 INFO: globalLogFile.critical("Error initializing ¸AQC
script", config.appName, exc_info=True)
19:09:31 M: 35225600 INFO: NameError
19:09:31 M: 35225600 INFO: :
19:09:31 M: 35225600 INFO: name 'globalLogFile' is not defined
19:09:31 M: 35225600 INFO:
19:09:31 M: 35225600 ERROR: Scriptresult: Error
19:09:31 M: 35225600 INFO: Python script stopped
19:09:31 M: 37298176 DEBUG: CGUIMediaWindow::GetDirectory (Q:\scripts)
19:09:31 M: 37298176 DEBUG: ParentPath = [Q:\scripts]
Original comment by davez...@gmail.com
on 3 Apr 2008 at 6:19
Attachments:
Looks like something went wrong uploading the script to your xbox (Binary vs
ASCII).
The "Error initializing ¸AQC script" has some strange characters as it should
read
"Error Initializing XOT-Uzg (XOT-Uzg.v3) script".
Could you try to first completely remove your XOT folder and then upload it
again?
Original comment by basrie...@gmail.com
on 3 Apr 2008 at 8:05
i used filezilla for upload: i tried auto/bin/ascii still the exact same effect,
i downloaded smartfxp, same effect... I changed my language setting from dutch
to
english, and changed the character set from standard to western-european (maybe
it is
some strange utf stuff)...
downloaded de.7z instead of the .zip
but unfortunately it didn't work...
Original comment by davez...@gmail.com
on 3 Apr 2008 at 9:51
But did you delete the complete XOT folder before uploading?
Original comment by basrie...@gmail.com
on 4 Apr 2008 at 1:56
yep each time...
(i assume the only folder resides in the scripts subdir)
Original comment by davez...@gmail.com
on 4 Apr 2008 at 4:13
well, if you put it in the scriptfolder it is! XOT does not store data at other
locations. But I must say it is a very weird problem. I have never seen or
heard it
before.
I assume you first extract the files to you PC HD and then upload the complete
XOT
folder, so all files without editing them, from your pc to a empty folder on
your Xbox?
Original comment by basrie...@gmail.com
on 4 Apr 2008 at 6:56
:-( yeah, i do it exact as you say... i ll give some more info:
xbox 1.6, duo2 GX, 200Gb disk, slayer 2.7, Bigfoot 87 xbmc (latest) / T3ch,
Project
Mayhem III
my neighbour has also a modded box, i'll try the script there too,
i ll let you know
Original comment by davez...@gmail.com
on 4 Apr 2008 at 8:44
by the way i googled a bit and it seems i am not alone:
http://www.xboxforum.nl/xbox-games/928-op-de-xbox-tv-kijken-3.html
Original comment by davez...@gmail.com
on 4 Apr 2008 at 8:47
Hallo, was hir inmiddels al een oplossing voor gevonden ? ik loop namelijk
tegen
hetzelfde probleem aan...
Original comment by rbrtv...@gmail.com
on 8 Apr 2008 at 6:18
Please post in english here!
As far as I know the problem this guy has is already solved, because he did not
reply
anymore. As for you: what version of XBMC and XOT are you using? And could you
attach
a DEBUG logfile of XBMC (and if present an uzg.log) for me?
Original comment by basrie...@gmail.com
on 8 Apr 2008 at 8:18
Actually it is not solved :-)
I am still having the same problem, I got some an idea by the way:
remember in the debug log the part about "AQT"; it seems there is actually an
AQT
script in my scripts folder... I am now trying to find some time to empty my
box and
setup everything again without the aqt script and then try again.
Rob? what version of xbmc are you running (on slayers 2.7 by any chance?)
Bas i am sorry for my late reply but my children want some xbox time too :-)
Original comment by davez...@gmail.com
on 10 Apr 2008 at 5:14
Well oke, than. We need to figure out how to solve the problem. To get the info
straight:
- you both run XBMC on an XBOX
- you both have a latest SVN build of XBMC
- you both run XOT as a script, not a plugin
- XOT is located in the XBMC\scripts folder
- You use the PMIII skin
- You do not run on HD resolutions
If the above is NOT correct, let me know.
Original comment by basrie...@gmail.com
on 10 Apr 2008 at 7:12
- you both run XBMC on an XBOX
> yes
- you both have a latest SVN build of XBMC
> 22nd of march t3ch (also tried bigfoot)
- you both run XOT as a script, not a plugin
>yes
- XOT is located in the XBMC\scripts folder
>yes
- You use the PMIII skin
>yes (also tried other skins)
- You do not run on HD resolutions
>correct
Original comment by davez...@gmail.com
on 10 Apr 2008 at 7:41
Oke, I changed something in the script. It won't fix your problem, but it will
put
additional data in the XBMC.log file and it should prevent your xbox to lockup.
Could you both replace the 'default.py' in the XOT folder with the one I
attached
here. Run XBMC and XOT again and post your XBMC.log here?
Original comment by basrie...@gmail.com
on 10 Apr 2008 at 9:28
Attachments:
Ok i will right after i get home...
upload binary or ascii?
Original comment by davez...@gmail.com
on 11 Apr 2008 at 7:40
GBW: I replaced the .py, I hope you can figure out what the problem is now. :)
Fire69
Original comment by jeremy.d...@gmail.com
on 11 Apr 2008 at 7:52
Attachments:
You can upload it as ascii and make sure you run XOT as a script, not plugin. I
only
added a quick debug option for the script functionality.
Original comment by basrie...@gmail.com
on 11 Apr 2008 at 8:03
Upload as ascii? :?
I ran it as script this time.
Original comment by jeremy.d...@gmail.com
on 11 Apr 2008 at 11:30
Attachments:
ok here it is
Original comment by davez...@gmail.com
on 11 Apr 2008 at 4:33
Attachments:
Jeremy de Backer, I am very sorry to tell you, but you did not run the
customized
default.py that I posted. I can see from the line number of the error that it
is the
old one.
To Dave: I am interested in the content of your libs folder. Could you post me
all
the files that are listed in your XOT\Libs folder?
Original comment by basrie...@gmail.com
on 11 Apr 2008 at 7:54
Oke, I made an extra change to get more exact data on your error and added some
debugging for the plugin version. Could you try this file (upload ascii or
auto) and
run XOT and post the XBMC.log and (if available) an uzg.log.
Original comment by basrie...@gmail.com
on 11 Apr 2008 at 8:33
Attachments:
ok here s my libs
Original comment by davez...@gmail.com
on 12 Apr 2008 at 8:28
Attachments:
i guess no uzg.log... This the extract from the xbmc.log:
20:39:17 M: 37191680 DEBUG: CGUIMediaWindow::GetDirectory (Q:\scripts)
20:39:17 M: 37167104 DEBUG: ParentPath = [Q:\scripts]
20:39:17 M: 37163008 INFO: Loading skin file: DialogProgress.xml
20:39:17 M: 37163008 DEBUG: Load DialogProgress.xml: 57.11ms (52.57 ms xml
load)
20:39:17 M: 35594240 DEBUG: Alloc resources: 5.54ms (0.01 ms skin load, 0.35
ms
preload)
20:39:18 M: 35205120 INFO: Exception during the initialisation of the
script. No
logging information was present because the logger was not loaded.
20:39:18 M: 35205120 INFO:
20:39:18 M: 35205120 INFO: Traceback (most recent call last):
20:39:18 M: 35205120 INFO: File "Q:\scripts\XOT-Uzg.v3\default.py", line
69, in ?
20:39:18 M: 35205120 INFO: globalLogFile =
logger.Customlogger(os.path.join(config.rootDir, config.logFileName),
config.logLevel, config.logDual)
20:39:18 M: 35205120 INFO: AttributeError: 'module' object has no attribute
'Customlogger'
20:39:18 M: 35205120 INFO: Scriptresult: Succes
20:39:18 M: 35205120 INFO: Python script stopped
Original comment by davez...@gmail.com
on 12 Apr 2008 at 8:43
now this is strange. The errors says that it cannot find the Class Customlogger
in
the logger module. But it sure is there! Could you post your logger.py here (it
is in
the libs folder of XOT)?
Original comment by basrie...@gmail.com
on 12 Apr 2008 at 5:22
[deleted comment]
[deleted comment]
Oke, I modified the default.py again. Could you try again?
Original comment by basrie...@gmail.com
on 12 Apr 2008 at 9:11
Attachments:
Yep i ll check it today as i get home,
Original comment by davez...@gmail.com
on 14 Apr 2008 at 11:59
it looks quite similair:
06:15:01 M: 35188736 INFO: Exception during the initialisation of the
script. No
logging information was present because the logger was not loaded.
06:15:01 M: 35188736 INFO:
06:15:01 M: 35188736 INFO: Traceback (most recent call last):
06:15:01 M: 35188736 INFO: File "Q:\scripts\XOT-Uzg.v3\default.py", line
69, in ?
06:15:01 M: 35188736 INFO: globalLogFile =
logger.Customlogger(os.path.join(config.rootDir, config.logFileName),
config.logLevel, config.logDual)
06:15:01 M: 35188736 INFO: AttributeError: 'module' object has no attribute
'Customlogger'
06:15:01 M: 35188736 INFO: Scriptresult: Succes
06:15:01 M: 35188736 INFO: Python script stopped
Original comment by davez...@gmail.com
on 14 Apr 2008 at 6:19
In that case I am lost? I updated the library search order to first search the
XOT
lib folder, so, in theory, it should always find the logger.py file! I will try
to
read some more on the problem.
Original comment by basrie...@gmail.com
on 14 Apr 2008 at 7:45
You don't happen to have a file logger.py in any of your other scripts? Could
you check?
Original comment by basrie...@gmail.com
on 14 Apr 2008 at 7:49
Oke, for the sake of coding. Run this default.py and please post the complete
XBMC.log. It should hold info on what Logger module is imported.
Original comment by basrie...@gmail.com
on 14 Apr 2008 at 7:54
Attachments:
hmmm let's try deduction here :-)
could you try hardcode it?
btw there is a logger.py in Pathe.nl\libs (sounds familiair :))
Original comment by davez...@gmail.com
on 14 Apr 2008 at 7:55
Hardcoding is not possible, you need to import a module before you can use it.
The
importing fails.
Original comment by basrie...@gmail.com
on 14 Apr 2008 at 8:03
and skip logging?
Original comment by davez...@gmail.com
on 15 Apr 2008 at 7:16
[deleted comment]
Skipping is not possible because the
logger thst fails to initialise is needed
throughout the complete script.
Original comment by basrie...@gmail.com
on 15 Apr 2008 at 9:45
Ok it is solved: In installed the new xbmc world release and it now works
flawlessly... I am very impressed with your program... thanks for putting all
the
effort in
Dave
Original comment by davez...@gmail.com
on 16 Apr 2008 at 2:48
Good to hear that.
XBMC World release of XBMC I assume?
Original comment by basrie...@gmail.com
on 16 Apr 2008 at 6:41
Can Jeremy confirm this?
Original comment by basrie...@gmail.com
on 16 Apr 2008 at 7:32
yep xbmc world release.. so thanks Bas and Bigfoot :-)
Original comment by davez...@gmail.com
on 17 Apr 2008 at 6:09
Problem solved with new version....closing issue.
Original comment by basrie...@gmail.com
on 21 Apr 2008 at 7:23
Original issue reported on code.google.com by
davez...@gmail.com
on 2 Apr 2008 at 8:44