rsesek@: what can cause this?
avi@: you have a 10.11.6 machine, right? can you try to repro?

That dialog is controlled by the system. Maybe there's a daemon that is wedged? I'd probably try restarting the machine.

Thanks for filing the issue!

Unable to reproduce the issue on reported chromium version 67.0.3396.87 using Mac 10.13.1. Attaching the screen shots for reference.

@Reporter: Could you please check as per comment#3 and let us know if the issue still persists. Hence adding label "Needs-Feedback".

Deleted: Verifying.png 28.1 KB

	Verifying.png 28.1 KB View Download

Deleted: Copying.png 28.2 KB

	Copying.png 28.2 KB View Download

I rebooted as per Comment #3, and still got stuck "Verifying." Left it to grind and came back 10m later to the Gatekeeper dialog (unidentified developer, etc. etc.). So launched it again from contextual menu (as you do to bypass Gatekeeper), and still got stuck for several minutes before finally getting the Gatekeeper dialog with the choice to open anyway. I did so, and can now use 67.0.3396.87 — HOWEVER, my Mac is treating it like a brand new app — asking for permission to use the Keychain, etc. The verifying delay, and the security stops for Gatekeeper and Keychain have never happened before with a Chromium update. So while I'm "in," something is still amiss, FYI.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As we are unable to reproduce the issue from our end (...in comment#4) and in comment#5 it's mentioned that reporter is able to launch chromium yet it seems, he has few issues relating to it as it's "treating the browser like a brand new app — asking for permission to use the Keychain ..." hence adding label "TE-NeedsTriageHelp" and requesting someone from Dev team to have a look at this and help in further triaging it.

Thanks!

Adding rsesek for the response in #5.

This sounds like something machine-specific. I'm not sure there's anything Chrome can do to alleviate this. Do other apps have this problem?

Agreed — this sounds like either something wrong with the machine, or something wrong with the copy of Chrome you have, unfortunately. Chrome is signed so it should never show up as from an "unidentified developer", and you shouldn't have to go through the context menu to launch it.

Well, I didn't have the same problem updating to 67.0.3396.99, so I guess I'm cured.

Thanks for digging into this, folks.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Good to hear. Thanks for the update, regardless!

FYI, I had this problem again with v70 today. "Verifying" dialog stayed onscreen for 5-8 minutes, then (finally) told me the app was from an unidentified developer. Tried again, launching with right-click > Open. Still got the "Verifying" dialog for 5-8 minutes, then Chromium stopped bouncing in the Dock, and the dot indicating it was running disappeared, but it was still running. Had to force quit and try again. Took three times around before it would launch properly.