Custom Query (1145 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (13 - 15 of 1145)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#1109 fixed XDG_CACHE_HOME should be pointed to a local directory davidben

Reported by davidben, 11 years ago.

Description

The  XDG base directory spec defines several variables including XDG_CACHE_HOME where applications are supposed to stuff cache data. There aren't all that many that create cache data of any significance, but browsers do. Google Chrome (and unbranded Chromium builds) uses it. Firefox does not, but they already split their profile into local/remote halves for Windows. I intend to shepherd a  patch in Firefox to put the local half into XDG_CACHE_HOME.

Debathena should consider pointing XDG_CACHE_HOME to something local. That would get local cache in Chrome for free, and same with Firefox once the patch goes through. This would also fix issue #329 as urlclassifier3.{sqlite,pset} are also part of the local profile. So are the offline cache and startup cache. (This would not fix #1107 as Thunderbird does not treat ImapMail? as local data.) This isn't explicitly stated as the intention in the spec (not that rigorous reading of a spec is remotely meaningful for desktop APIs), but random searches on Google do suggest that NFS homedir and local XDG_CACHE_HOME are common.

It's conceivable that bad things will happen with an app running in two concurrent logins but each sees different caches, so it's probably worth testing a few things. (Then again, I suspect they all already break on concurrent logins anyway.)

#1161 fixed Xauthority shouldn't be in ~ quentin

Reported by quentin, 10 years ago.

Description

Precise puts Xauthority in ~/.Xauthority, which means you can't launch any apps when AFS is sad.

#128 fixed Write cron job to e-mail about packages in -proposed broder

Reported by broder, 14 years ago.

Description

We should write something to e-mail us when a package has been in -proposed for more than a day or so so that we don't forget to migrate functional packages to production.

In a perfect world, I think such a script should track which package/version combinations it's already notified us about so we only get notified for a given pair once.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.