Problem with [ X ] keyboard shortcut in Lightroom CC 2015.8 / 6.8 update

  • 1
  • Problem
  • Updated 3 years ago
  • (Edited)
Merged

This conversation has been merged. Please reference the main conversation: Lightroom CC 2015.8: Shortcut X to reject an image in Library not available (French)

Working in the develop module, when I refuse a photo by pressing the X key and want to remove the photo LR crashes. This is in the develop module. In the library module it does works fine. A Bug???
Photo of Thijs

Thijs

  • 5 Posts
  • 0 Reply Likes
  • could be better

Posted 3 years ago

  • 1
Photo of Ronald Byram

Ronald Byram

  • 144 Posts
  • 15 Reply Likes
Are you running windows or IOS? I just tested this I flagged picture and then did a Cntrl-Backspace nad was prompted to delete picture. no crash. (I am windows 10 and CC LR 2015.8
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5882 Posts
  • 1290 Reply Likes
@Thijs, are you using the French Language version of LIghtroom? If so, there is bug in this release regarding the X key. We are looking into it. 
Photo of Thijs

Thijs

  • 5 Posts
  • 0 Reply Likes
No I'm using the Dutch version on a iMac MacOS Siera. So it is also in the Dutch Version.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5851 Posts
  • 1282 Reply Likes
Thank you for the information I will pass it along to the team. 
Photo of Steve Hurrell

Steve Hurrell

  • 2 Posts
  • 0 Reply Likes
I am having the same issue with LR 6.8 crashing. 

After selecting images to delete in the  'Develop' module, and then deleting them, I cannot then change to any further image in that module. 

Trying to swap modules prompts an Error message saying 'cannot change to the new module'.

I am using LR 6.8 (in UK) on a 15" Macbook Pro Retina running OSX 10.11.6.

When then quitting the LR 6.8 application there is no option to back-up, as I normally require in Preferences.

Sometimes (but not always) after re-opening the software the problem remains necessitating an OSX restart. On next opening the software, it appears to be working normally.

Does anyone have any suggestions, please? Thanks in advance.

Steve Hurrell
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5088 Posts
  • 1989 Reply Likes
Have you been through the steps in this document? https://helpx.adobe.com/lightroom/kb/error-changing-modules-lightroom.html 
Photo of Trent Archer

Trent Archer

  • 2 Posts
  • 0 Reply Likes
I'm having a similar issue; when I delete an image from disk and want to edit another, I have to exit and go back in. It's extremely frustrating. Especially given the general issues with running LR in a virtual machine.

Glad to know I'm not the only one, though.

I'm in the UK too and using LR in a Windows 10 VM.
(Edited)
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5088 Posts
  • 1989 Reply Likes
Odd question Trent - why a VM rather than using LR natively?
Photo of Trent Archer

Trent Archer

  • 2 Posts
  • 0 Reply Likes
I simply don't like using Windows and prefer Ubuntu, so I just use LR in a VM.
I appreciate that I'd get better performance using Windows all the time, but it's not a huge deal to me. Especially as I'm not a professional photographer.
(Edited)
Photo of Andreas Hüttner

Andreas Hüttner

  • 3 Posts
  • 1 Reply Like
Same issue here!
I'm running the german Version under Mac OS X.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5088 Posts
  • 1989 Reply Likes
That makes sense, thanks Trent.
Photo of Steve Hurrell

Steve Hurrell

  • 2 Posts
  • 0 Reply Likes
Replying to Victoria's suggestion concerning this document – 
 https://helpx.adobe.com/lightroom/kb/error-changing-modules-lightroom.html 

No, I haven't tried any of these methods.  I really don't want to start uninstalling the software unless absolutely essential. It seems to be quite an old document, relating to old versions of LR. I feel the current errors occur because of the deleting issue, not the other way round. 

Steve Hurrell

This conversation is no longer open for comments or replies.