Lightroom always switches desktop space to the initial

  • 1
  • Problem
  • Updated 2 days ago
  • In Progress
1. Create 2 desktop spaces on macOS.
2. Open Lightroom in the first space.
3. Open Mission Control (press F3).
4. Drag Lightroom window to the second space.
5. Switch to the Lightroom on the second space.

Should be: Lightroom must remain on the screen.

Actual result: Lightroom changes desktop space automatically to the first one without Lightroom in it. Can't use Lightroom anymore.

Photo of Dmitry


  • 157 Posts
  • 52 Reply Likes

Posted 3 weeks ago

  • 1
Photo of Dave Roberts

Dave Roberts

  • 147 Posts
  • 25 Reply Likes
After creating second desktop. Right click on LR in dock, select ‘Assign to’ and it will stay put!
Photo of Dmitry


  • 157 Posts
  • 52 Reply Likes
But it doesn't fix the issue and only offer a workaround.
Photo of Alan Harper

Alan Harper

  • 428 Posts
  • 84 Reply Likes
Actually, as far as I can tell, Dave's work-around only makes it worse. I assigned LR to "Desktop on Display 1" (I have 2 displays) and after that, on seemingly a random basis, the "Window : Secondary Display : Survey ⇧N" would display only on Display 1. It was very confusing to figure this out.

Bottom line: Lightroom and Spaces just don't cooperate. And since every other program I have seems to work fine, I suspect the problem is Adobe's. Perhaps this is from Adobe trying to suss out how many monitors you have, and not understanding how the spaces and monitors interact.
Photo of Alan Harper

Alan Harper

  • 429 Posts
  • 85 Reply Likes
I just saw this today too -- I moved LR from Space 1 (where it had opened) to space 2. After that I would without warning be booted back to Space 1. Especially strange was when I used Lights Out in LR, and I got these dark window frames placed on top of another app's windows. Obviously, Lightroom Classic is not very compatible with Apple's Spaces, even after all these years.
Photo of Ruby k

Ruby k, Employee

  • 9 Posts
  • 4 Reply Likes
Hi Dmitry, Alan ,

We are also seeing this issue at our end. We have added this issue to our list.Thanks for bringing this out.