Tvheadend

Check permissions on /usr/share/tvheadend/source/webui/static/extjs/resources/images/default/*.gif and below - should be root/root, 644 on files, 755 on directories.

While you're there, also check /usr/share/tvheadend/src/webui/static/icons. They should be as above.

Permissions look as expected, however /usr/share/tvheadend/source/ doesn't exist, but /usr/share/tvheadend/src/ does. Should there be both or is that a mistype?

Fat fingers, sorry - src is correct, not source.

With 3.4.27 on Arch we have also this issue. But trigger.gif is shown, if you enter the url of the image directly. I have no idea why the black boxes are shown.

I had a thought here... are we looking in the right place? Permissions are all very well, but what if it isn't hts that's trying to access the files.

tvheadend includes its own web server. That loads up the extjs pages (config.js and friends). I am assuming that none of this necessarily runs as hts... it may run as root, maybe something else. So...

1. If there's some quirk of different distros that changes how this process is spawned, the rights it inherits, or similar then maybe what works on, say, 'buntu 12.x doesn't work on Arch.

2. If something else has happened during installation that does the same - maybe some global umask, maybe a top-level inherited file system permission - then perhaps a process that runs as UID:GID on box 1 can access the files while the equivalent on box 2 can't.

We'd need to figure out where the processes run... are they simply threads of tvheadend (in which case they're indistinguishable and should be hts:video) or are they genuinely separately-spawned processes in their own right.

Just a thought... maybe judicious use of ps -eaf, grep, pstree, fuser and similar would tell us more?

lsof suggests that the web server runs under hts:

tvheadend 21927  hts   11u  IPv4            4372076      0t0     TCP *:9981 (LISTEN)

... so I'm not sure whether that shoots my theory down or not.

Okay, I've been posting to the wrong thread - I was looking at config.js/FAILED issues related to imagecache - but the webserver bit is perhaps relevant to the dodgy graphics, so I'll leave these here in case someone wants to follow it through.

If I try to access /static/extjs/resources/images/default/form/trigger.gif directly, the icon is shown. So it is readable by the webserver. So I would assume it's an css-error or so.