2013-08-31, 19:07
Not to be a jerk, but how is that at all useful?
The 2 outcomes on the logic path from that step are "The images work on the VM" or "the images do not work on the VM".
My honest question is "OK and then what?" Either way you don't get a very clear path on what to do to get it working, just confirmation that the actual install is broken, which we already know.
It seems like a more useful way to proceed is to examine the logs to determine what the nature of the failure is.
In the directory where HTPC manager is installed, you should have a userdata folder.
Inside of there you should have the file htpcmanager.log.
This is the log you'll want to look at after you attempt to load images from XBMC.
Like here's a cat from mine just to give you an idea of WTF I am talking about:
The "decoder jpeg not available" is somewhat helpful because it shows the PIL doesn't have JPEG abilities installed or detected for some reason.
Of course actually fixing that issue seems very specific to the operating system and packages and install method being used, but thats a much more straightforward approach then having to set up (and possibly troubleshoot) an entire VM and new OS on said VM, and then basically be back where you started.
The 2 outcomes on the logic path from that step are "The images work on the VM" or "the images do not work on the VM".
My honest question is "OK and then what?" Either way you don't get a very clear path on what to do to get it working, just confirmation that the actual install is broken, which we already know.
It seems like a more useful way to proceed is to examine the logs to determine what the nature of the failure is.
In the directory where HTPC manager is installed, you should have a userdata folder.
Inside of there you should have the file htpcmanager.log.
This is the log you'll want to look at after you attempt to load images from XBMC.
Like here's a cat from mine just to give you an idea of WTF I am talking about:
Code:
2013-08-20 14:29:49 :: cherrypy.error.161445580 :: ERROR :: [20/Aug/2013:14:29:4 9] HTTP Traceback (most recent call last):
File "/usr/share/htpcmanager/libs/cherrypy/_cprequest.py", line 656, in respon d
response.body = self.handler()
File "/usr/share/htpcmanager/libs/cherrypy/lib/encoding.py", line 188, in __ca ll__
self.body = self.oldhandler(*args, **kwargs)
File "/usr/share/htpcmanager/libs/cherrypy/_cpdispatch.py", line 34, in __call __
return self.callable(*self.args, **self.kwargs)
File "/usr/share/htpcmanager/modules/xbmc.py", line 202, in GetThumb
return get_image(url, h, w, o, self.auth())
File "/usr/share/htpcmanager/htpc/proxy.py", line 51, in get_image
resize_image(image, height, width, opacity, resized)
File "/usr/share/htpcmanager/htpc/proxy.py", line 88, in resize_image
im = im.resize(size, Image.ANTIALIAS)
File "/usr/local/lib/python2.7/dist-packages/PIL/Image.py", line 1290, in resi ze
File "/usr/local/lib/python2.7/dist-packages/PIL/ImageFile.py", line 189, in l oad
File "/usr/local/lib/python2.7/dist-packages/PIL/Image.py", line 385, in _getd ecoder
IOError: decoder jpeg not availableThe "decoder jpeg not available" is somewhat helpful because it shows the PIL doesn't have JPEG abilities installed or detected for some reason.
Of course actually fixing that issue seems very specific to the operating system and packages and install method being used, but thats a much more straightforward approach then having to set up (and possibly troubleshoot) an entire VM and new OS on said VM, and then basically be back where you started.
