Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#12082 closed Bug Report - General (Invalid)

cache_file.py:243:_init_cache:TMDBCacheDirectoryError

Reported by: cube_00@… Owned by:
Priority: minor Milestone:
Component: MythTV - General Version: 0.27-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description

cache_file.py:243:_init_cache:TMDBCacheDirectoryError: Directory containing cache file does not exist: /var/lib/mythtv/.mythtv/pytmdb3.cache.

Unsure why it's looking for a .mythtv directory here, should I just add one for it or is a bug?

Attachments (1)

backtrace (2.0 KB) - added by cube_00@… 11 years ago.

Download all attachments as: .zip

Change History (4)

Changed 11 years ago by cube_00@…

Attachment: backtrace added

comment:1 Changed 11 years ago by Raymond Wagner

Resolution: Invalid
Status: newclosed

tmdb3.py assumes that you will have read/write access to your own home directory, and your home directory is apparently set to /var/lib/mythtv/. If it cannot open a cache file there, this is a user configuration error. Please take this up on the mailing list, IRC channel, or forum.

comment:2 Changed 11 years ago by cube_00@…

Thanks for the reply.

Given the trend to moving services such as mythbackend to user IDs of their own, is there a configuration option to change this location to somewhere more suitable? Seems a waste to create .mythtv folder here for this one python script.

comment:3 Changed 11 years ago by Raymond Wagner

Many different parts of MythTV use ${HOME}/.mythtv/ as scratch space. The file that identifies the database location is there. The theme cache is there. If /var/lib/mythtv/ is your home directory, and you are running MythTV, /var/lib/mythtv/.mythtv/ should already exist. That is, unless you have defined both ${MYTHCONFDIR} and ${HOME} to the same /var/lib/mythtv/, which means MythTV is now dirtying up your home directory, in which case a recent patch committed to tmdb3.py will make it use the ${MYTHCONFDIR} variable in the same manner.

Note: See TracTickets for help on using tickets.