Mythfrontend rescales themes every startup.

[anonymous]

Although there is caching I see the rescaling progress bar every time I (re)start mythfrontend. This takes time.

[Janne Grunau]

please attach the output of mythfrontend -v most

[anonymous]

mythfrontend log

[Isaac Richards]

It's just checking to see if there's anything to rescale.

[anonymous]

It is generating cache images as well.

[Isaac Richards]

2 very small images, which looks like it's taking about 0.2 seconds. Make sure the timestamp on them isn't in the future, and the "problem" will go away.

[anonymous]

Timestamp is not in the future:

# ls -l /usr/share/mythtv/themes/default/blank.png -rw-r--r-- 1 root root 151 Feb 23 08:24 /usr/share/mythtv/themes/default/blank.png # ls -l /usr/share/mythtv/themes/Retro/blank.png -rwxr--r-- 1 1000 1000 151 Mar 13 2006 /usr/share/mythtv/themes/Retro/blank.png

[Isaac Richards]

I still don't consider taking an extra 2 tenths of a second on startup to be a bug.

[anonymous]

The progess bar is longer on the screen than 2 tenths of a second. And if the images are processed, why at all if the cache allows for 2 cached copies? If not a bug may I at least understand?

[cpinkham]

When the lead developer of a project closes your ticket THREE times, it's a sign that the issue you are seeing is not an issue and probably won't be investigated. Trac is not a discussion forum. If you want to talk about this and get some help, try asking on the mythtv-users mailing list or in the #mythtv-users IRC channel. Constantly reopening this ticket will just tick the developers off and get you ignored.

[anonymous]

Nice to know that a developer does not want to pay attention to a problem I observe and support with a logfile. The fact that a logfile does not cohere with what is on teh screen is their issue as well.

[someone else]

I see this everytime I startup mythtv as well.

[anonymous]

This started happening to me only once I changed from the default theme. I'm using blue, but I didn't test any other. I can't find the mythfrontend.log file even using find, and the files in the blue theme directory are all dated 12/20/2006.

By any chance, could the code that's checking the timestamp be looking in a third directory or even failing in the check?

[anonymous]

For me this does not take 2/10 of a second. It does the prescaling theme images 3 times and several minutes in total, maybe slower because i have a humble 32mb graphics card on my VIA EPIA MII motherboard. So for me this is a real issue.

[anonymous]

KnoppMyth? user (R5E50) here, using blootube wide. My timestamps are ok, and I see this too. Takes about 5-8 seconds, every time, even when aborting from the "do you want to quit" screen. I'm just offering another data point.

[sphery <mtdean@…>]

KnoppMyth? user: you are (like many of the people here probably are) seeing Myth checking to verify it already has pre-scaled images (and it does, or it would take much more than 10 seconds). To prove this, shut down mythfrontend and remove the cache directories ("rm -r $HOME/.mythtv/{theme,osd}cache"), then restart mythfrontend. You'll notice a /large/ difference in the time required to scale the images.

anonymous who's seeing prescaling "3 times and several minutes in total": the graphics card has no effect on scaling speed, only the CPU, RAM, and I/O subsystem does (so, your Via processor is why it takes 3 minutes). The reason it's scaling every time is a configuration issue, probably like below.

anonymous who's using bluetube: the user running mythfrontend doesn't have write permissions on $HOME/.mythtv/ or $HOME/.mythtv/{theme,osd}cache or some subdirectory. You can probably fix it by a) verifying you've specified the proper "export HOME=/whatever" in the script that starts mythfrontend and b) "rm -r $HOME/.mythtv/{theme,osd}cache"

anonymous who uploaded a log file (and who feel slighted because he doesn't get the support to which he's entitled): you are starting mythfrontend in an environment in which the HOME environment variable resolves to "/root", so mythfrontend is using /root/.mythtv for its image cache. There is no possible way that any user (other than root) would have access to this directory on a properly-configured system. You are running as root, so it works. (But for others reading this ticket's comments, please keep in mind what I mentioned about HOME resolving to /root). You'll also notice that your log only shows the generation of 2 images and attempts to generate 4 (for files missing from the theme) and it only takes seconds. Therefore, you're seeing the same as KnoppMyth? user, above.

All: this is not a discussion forum. Please post questions to the -users mailing list or ask on #mythtv-users on freenode to verify that you're seeing a bug before creating tickets or adding comments to tickets. Oh, and we don't need more "me too's." Thanks.

[stuartm]

Although most images are loaded from the cache each time, a handful are loaded before themecachedir is defined so they are rescaled every time.

I've attached a one-line fix which seems to work fine but as I'm not sure whether there are undesirable consequences that I haven't had the time to spot, so please test.

[devel@…]

Wow! Mythfrontend starts almost instantaneously for me now, the image scaling dialog barely flashes on the screen. Thanks for this, certainly works for me

[stuartm]

(In [13506]) Closes #3189

Initialise the theme cache earlier to avoid rescaling images loaded in the creation of MythThemeBase?. Should decrease the startup time of mythfrontend.

[stuartm]

(In [13557]) Backports [13506] to -fixes.

Refs #3189. Initialise the theme cache earlier to avoid rescaling images loaded in the creation of MythThemeBase?. Should decrease the startup time of mythfrontend.