Lightroom: How to Better Understand When LR Bugs Bite? (Can we somehow activate error logging?)

  • 2
  • Question
  • Updated 9 years ago
  • Answered
Is there a way in which I could help to address some of the remaining bugs?

I relatively frequently get an "An unknown error occurred." message. Is there a way, e.g., by activating a logging mechanism, in which I could help the team to find out about the source of this error / these errors?

I recently could not reorganise a folder structure because LR told me "You cannot move a folder into one of its subfolders" (or very similar). The target folder was not a subfolder. I subsequently moved the folder I wanted to move into the target folder using Windows Explorer and then let LR "find" the folder at the new location. This appears to have worked but LR should have supported the move in the first place.

Sometimes, when I want to move a folder within LR, LR tells me that the operation didn't succeed and when I try again immediately the move works.

Obviously all the above normally works so I'm not sure whether there would be a point in filing bug reports for these.

Maybe being able to activate some logging and/or sending data to the team would help to make the above scenarios repeatable?

After recently having lost all photo orientation data, having had folder synchronisation problems (because one file somehow had its "rootFolder" become "nil" problem that caused LR to be unable to synchronise a folder was not picked up by a catalogue check / optimisation.

It seems that there are a number of bugs but without being able to gain a deeper understanding what situations in particular cause LR to choke, I doubt regular bug reports will help to track down those bugs.
Photo of TK


  • 531 Posts
  • 120 Reply Likes
  • no longer confident in LR keeping catalogues sound and would like to be able to help in the detective work.

Posted 9 years ago

  • 2
Photo of Dan Tull

Dan Tull, Employee

  • 172 Posts
  • 39 Reply Likes
Official Response
The "unknown error occurred." message is typically something that can be diagnosed with a logging switch I added in 3.0 for just this purpose. Another example issue that tracebacks is good at diagnosing is the dreaded error switching modules message.

You need to pass -tracebacks to the executable as a command line argument. On windows, you can tweak the shortcut to pass this parameter. On the Mac, you could either make a .command which passes the extra parameter or run LR from directly.

On Windows, these messages can be viewed if you attach WinDbg or run DebugView (note these need to be running _before_ you elicit the error to capture the messages). On the Mac, can be used to view the traceback output.

Note that not all output from this command corresponds to a bug. It logs each time a Lua "throw". Some of these are errors, but some are throws used to cancel an operation and unroll the call stack.

I've used it enough at this point that I'm thinking I may try to make it easier to use this mode in some future version.

There's additional logging that can be enabled, but it's noisier and more subsystem specific in terms of its use.