Phatch

Phatch should not always start a fonts subprocess when it boots

Bug #529533 reported by Stani
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Phatch
Invalid
Low
Stani
Phatch 0.2.7 "Bug Fix"

Bug Description

ATM Phatch starts a subprocess at boot time to check or create the font cache. If the font cache is present it should not be started.

Revision history for this message
Stani (stani) wrote :

This is how it gets called: config.py > fonts.py > system.call

It should be prevented with some 'if os.path.exists'.

Changed in phatch:
importance: Undecided → Low
milestone: none → 0.2.7
status: New → Confirmed
Revision history for this message
Stani (stani) wrote :

After studying the issue more close, it would be better to implement a caching system for system.find_exe. This is not really a bug so I filed this blueprint for it:
https://blueprints.launchpad.net/phatch/+spec/cache-exe

Changed in phatch:
assignee: nobody → stani (stani)
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.