dcpomatic/src/tools, branch macos108 DCP-o-matic DCP tools https://git.carlh.net/cgit/dcpomatic/atom?h=macos108 2021-05-10T21:35:53Z Open a dialogue if pinging the back-end fails on macOS. 2021-05-10T21:35:53Z Carl Hetherington cth@carlh.net 2021-05-10T13:12:23Z urn:sha1:1484f4e3642e3ddcb10515eb0f32b00370968da3 At least this means the user will get another go without losing their setup. My only theory at this point is that sometimes the backend takes a crazy amount of time to start up because of some SIP / gatekeeper type nonsense (#1990). Attempt ping from front- to back-end several times (#1990). 2021-05-09T21:15:05Z Carl Hetherington cth@carlh.net 2021-05-09T14:43:24Z urn:sha1:472959c1357f43e2eb33366c58bed0466474c2b7 On macOS it seems that the backend sometimes is not started very quickly. Adding a long timeout to ping does not work, perhaps because the backend is not listening. Trying a few times seems to fix it. With this fix I saw this log: Sun May 9 23:02:51 2021: dcpomatic_disk_writer e63a485e23 started Sun May 9 23:02:51 2021: Entering main loop Sun May 9 23:02:51 2021: Writer receives command: P from the backend and Sun May 9 23:02:45 2021: Could not send ping to writer (attempt 1) Sun May 9 23:02:47 2021: Could not send ping to writer (attempt 2) Sun May 9 23:02:49 2021: Could not send ping to writer (attempt 3) from the front-end, suggesting that the first 3 pings went to /dev/null and the 4th was heard. Add more logging to disk writer. 2021-05-09T21:15:05Z Carl Hetherington cth@carlh.net 2021-05-09T08:08:39Z urn:sha1:767238a8abebbb2a2f8d1e91806131754b9c67fd Add some more logging to disk_writer. 2021-05-08T15:35:12Z Carl Hetherington cth@carlh.net 2021-05-08T15:35:12Z urn:sha1:1ac807fa50ea6e20e821d59bb00a397a4812c3e4 Updated cs_CZ translation from Tomáš Begeni. 2021-05-07T15:16:33Z Carl Hetherington cth@carlh.net 2021-05-07T15:16:33Z urn:sha1:62b6c99b034f592563a0f6a16ddbeca8039842df pot/merge. 2021-05-06T22:32:45Z Carl Hetherington cth@carlh.net 2021-05-06T22:32:45Z urn:sha1:8a68631f7095cd716aae3f7053d819668555f557 C++11 tidying. 2021-05-03T18:18:04Z Carl Hetherington cth@carlh.net 2021-05-03T09:17:34Z urn:sha1:689fa55d1529ad88449ca464e9107c4dcc54d1cb C++11 tidying. 2021-04-30T23:31:35Z Carl Hetherington cth@carlh.net 2021-04-30T23:31:35Z urn:sha1:8963f0007af1a312017b9627c18b82ec2a577591 Close down the FilmViewer before its GUI elements get destroyed (#1982). 2021-04-22T23:08:17Z Carl Hetherington cth@carlh.net 2021-04-22T23:08:17Z urn:sha1:cde59064499abaf8f30d0979747041af363cbef4 Otherwise this happens when we're already in the middle of destroying the UI. Do the polkit dance for unmounting drives as well as writing them. 2021-04-22T13:42:11Z Carl Hetherington cth@carlh.net 2021-04-21T23:40:39Z urn:sha1:3b63427fd27ea6bebb6dbe6ac463b30fd84d152c If we ask for permission to unmount that should carry over to give permission to format/write as well.