Bridge: Cmd-Q won't quit application

  • 2
  • Problem
  • Updated 4 months ago
  • (Edited)
When i hit cmd-Q on any of my computers, with Bridge Cs6, there will be many times where i won't be able to quit the app (of course i can't reproduce right now, cmd-Q works, when it didn't 3 minutes ago).

This often happens just before I leave and shut down my mac, I cycle through the apps, to check if i didn't leave anything opened, and just press cmd-Q, which works everywhere but on Bridge. Any idea ?
Photo of Franck Payen

Franck Payen

  • 80 Posts
  • 7 Reply Likes
  • frustrated

Posted 6 years ago

  • 2
Photo of Franck Payen

Franck Payen

  • 80 Posts
  • 7 Reply Likes
7 months later same shortcut problem...
Photo of Tom Van Damme

Tom Van Damme

  • 2 Posts
  • 1 Reply Like
Same here. All programs quit when using cmd+q except Bridge. Only works through the menu.
Photo of Tom Van Damme

Tom Van Damme

  • 2 Posts
  • 1 Reply Like
Hi there,

This bug has happening for some time now apparently.

Situation: the shortcut Cmd+Q to quit Bridge works fine, up until the moment I've hidden the app. After that Cmd+Q (Quit) won't work to quit.

  • So I start Bridge - Cmd+Q works fine to quit again.
  • I start Bridge, hide it (using Cmd+H), bring it back to foreground, and Cmd+Q doesn't do anything anymore. I have to go to the menu and select Bridge>Quit Bridge. After I quit and restart the app, Cmd+Q will work again until the app has been hidden.

I've checked my system shortcuts, but nothing interferes with this shortcut. Cmd+Q works fine on other apps (Illustrator, Photoshop, Indesign,... all quit when using the shortcut). Also all other shortcuts do seem to work in Bridge, it's just the Cmd+Q that doesn't do anything.

Like I said, it might not be related to Bridge since trashing preferences or reinstalling doesn't change anything. Also the same bug has been present over a few versions now.

Would be nice to finally get some feedback on a possible cause (and solution) for this.

 Thank you!

Photo of Kukurykus

Kukurykus

  • 256 Posts
  • 37 Reply Likes
It's good you found reason of this bug, however that should be task of Bridge team. Anyway that's typical for them - 6 years of waiting to fix so small bug and all shows they do not care at all to do it.
(Edited)