robert 1f4053bbd9 Add a temporary workaround to the chrome wrapper script that checks ... if the SingletonLock file is available and valid. The problem is that when chrome crashes one of the destructors fail to remove the lockfile and then when you start chrome again, it will try to communicate with the old PID of the chromium main process, because the SingletonLock file will point to `hostname`-PID_of_old_chromium and since that process is not running anymore, startup will fail.		2012-05-17 08:52:59 +00:00
..
chrome	Add a temporary workaround to the chrome wrapper script that checks	2012-05-17 08:52:59 +00:00
chrome.desktop	Add missing RUN_DEPENDS.	2011-05-19 11:57:37 +00:00