• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
31

P: Email not working-External error has occurred: ?:0 Attempt to index field 'font'( a nil value )

Participant ,
Oct 25, 2020 Oct 25, 2020

Copy link to clipboard

Copied

Ever since the V10 update my email out of LR Classic has quit working, but instead returns the above error message.  I have reset the preferences, deleted and readded my email client to no avail.  Still does not work and from the forum, it looks like there are lots of nil value errors happening.

System specs:

OS Name Microsoft Windows 10 Home
Version 10.0.19041 Build 19041
Other OS Description  Not Available
OS Manufacturer Microsoft Corporation
System Name JOESALIENPC
System Manufacturer Alienware
System Model Alienware Aurora R7
System Type x64-based PC
System SKU 0858
Processor Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 3192 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date Alienware 1.0.22, 6/9/2020
SMBIOS Version 3.1
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Alienware
BaseBoard Product 0VDT73
BaseBoard Version A00
Platform Role Desktop
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume3
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.488"
User Name JOESALIENPC\Jhud2
Time Zone Pacific Daylight Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.8 GB
Available Physical Memory 21.4 GB
Total Virtual Memory 40.9 GB
Available Virtual Memory 25.4 GB
Page File Space 9.12 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

Bug Fixed
TOPICS
macOS , Windows

Views

493

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Dec 08, 2020 Dec 08, 2020

Updates to the Adobe Photography Products were released yesterday and include a fix for this issue. Please install the December update, restart your system and verify you are no longer experiencing the issue. Thank you for your assistance in reporting, providing additional information and, most of all, for your patience.

Votes

Translate

Translate
replies 166 Replies 166
166 Comments
New Here ,
Nov 04, 2020 Nov 04, 2020

Copy link to clipboard

Copied

This has been driving me crazy all night trying to fix. I cannot believe Adobe did not catch this enormous bug/issue. Unbelievable.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Nov 04, 2020 Nov 04, 2020

Copy link to clipboard

Copied

So do I, disappointing.

Votes

Translate

Translate

Report

Report
Participant ,
Nov 04, 2020 Nov 04, 2020

Copy link to clipboard

Copied

Funny.  They knew about this early on after the release, but never communicated with their help department--and thus the people there were trying everything to fix it.  There is no fix but debugging the program and its sure taking too long to do. 

Votes

Translate

Translate

Report

Report
New Here ,
Nov 04, 2020 Nov 04, 2020

Copy link to clipboard

Copied

Adobe’s negligence cost me hours of anxiety and worry, thinking there was problem with my system. I’m pretty pissed.

Votes

Translate

Translate

Report

Report
New Here ,
Nov 04, 2020 Nov 04, 2020

Copy link to clipboard

Copied

With over 22,000 employees at Adobe you would think may have 1-2  of them on this forum  trying to help people might be a good strategy to help protect their brand.  What upsets me as well is that of all of their famous  independent  'photoshop Surrogates '  on their  own  blogs, videos, and newsletters touting all of the new  10.0 features  with  walkthroughs  and 'ten top  things in  10.0  ' videos  even today  not one of them  anywhere is writing about these bugs. 

Votes

Translate

Translate

Report

Report
Community Expert ,
Nov 04, 2020 Nov 04, 2020

Copy link to clipboard

Copied

@MrLiveProducer I hate to disagree, but check the red section at the top of my blog post... I always update if there are notable issues. https://www.lightroomqueen.com/whats-new-in-lightroom-classic-10-0/

And the official answer right at the top of the first page of this thread is from a staff member. 

That's not an excuse for bugs, but unfortunately bugs do happen. 

______________________
The Lightroom Queen - Author of the Lightroom Missing FAQ & Edit Like a Pro books.

Votes

Translate

Translate

Report

Report
New Here ,
Nov 04, 2020 Nov 04, 2020

Copy link to clipboard

Copied

Victoria hi,

I stand corrected  I was not aware of your great blog I will be sure to access it from now on. Good on ya as you are in minority right now and standing tall. 🙂

Votes

Translate

Translate

Report

Report
Participant ,
Nov 04, 2020 Nov 04, 2020

Copy link to clipboard

Copied

Victoria is one of the real good people who happens to also be an expert on all things LR.   Unfortunately, it has been 15 days since upgrade and all we know at this point is that they are aware of the bug(s).  

Votes

Translate

Translate

Report

Report
Community Beginner ,
Nov 06, 2020 Nov 06, 2020

Copy link to clipboard

Copied

Any idea when this bug is going to be fixed?

Votes

Translate

Translate

Report

Report
Participant ,
Nov 06, 2020 Nov 06, 2020

Copy link to clipboard

Copied

So its day 16 and nothing--nothing from Adobe, nothing from their "moderators".  Just--we are aware of the problem. How about telling us what the strategy is to solve it and when you expect it to be solved?

Votes

Translate

Translate

Report

Report
New Here ,
Nov 06, 2020 Nov 06, 2020

Copy link to clipboard

Copied

I have had to change my entire workflow to work around this huge bug - that they don’t seem to be adressing. It really makes me lose confidence in Adobe.

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 06, 2020 Nov 06, 2020

Copy link to clipboard

Copied

Get an error message on my MacBook Pro running version 10.15.7 when attempting to email photos from Lightroom Classic 10.0. I am wondering when this bug may be fixed or should I revert to an earlier version of Lightroom?

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 07, 2020 Nov 07, 2020

Copy link to clipboard

Copied

Known and Reported bug. Will be Fixed in a future update of LrC.

In the mean time Export to your HDD and then Email that exported image to whomever using your email program on your computer or the Web interface from your email provider.

Votes

Translate

Translate

Report

Report
Participant ,
Nov 07, 2020 Nov 07, 2020

Copy link to clipboard

Copied

Day 17---Nothing!  Trying to figure out what's taking so long.  I assure you if the subscription pay plan collapsed they would have it fixed in a day. 

Votes

Translate

Translate

Report

Report
Engaged ,
Nov 07, 2020 Nov 07, 2020

Copy link to clipboard

Copied

Same issue for the past 2 releases. They know about it but Tech Support told me it is way low on the priority list. I fail to see how they can mess things up more with every release. I can't import images into LR from an LG G7 phone either (started 2 releases ago). Any attempt not only crashes LR it also crashes Windows Explorer. Meanwhile Windows sees and reads the phone just fine and images can be dragged in with no problem ...other than having to create new folders manually for each month and day that aren't already in LR eco system. 

Photoshop's Select and Mask doesn't work at all for several releases now. Oh I suppose it would if I spent $4000 or so on a new system. My laptop just doesn't cut it with PS anymore ...even though it is an i7 with 16gigs of ram running at 2.4 off a 1TB SSD. The drive and all the memory were upgraded at considerable expense to be able to use Photoshop but alas ...one has to buy other software now in order to do photo editing. 

I use Fundy Designer, which runs like a deer on my system and clearly illustrates that Adobe needs to dragged into the 21st century, insofar as having responsible people in charge of product development and testing. It's just not making sense any more. I and many others I'm aware of are spending more time fighting bugs than on productive workflow.

They just keep releasing unproven "UPDATES" with the full intention of letting the user community discover the programming errors and report them. The trouble is there are so many of them now they are never going to catch up and the next release will pile on even more. As they say ...the light at the end of the tunnel ...is a train!

Votes

Translate

Translate

Report

Report
Participant ,
Nov 08, 2020 Nov 08, 2020

Copy link to clipboard

Copied

As I said earlier, it would be very helpful if Adobe would communicate by giving an estimate on when a patch for his bug (and others) would be available. I agree, as troubles mount--where to start!

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 09, 2020 Nov 09, 2020

Copy link to clipboard

Copied

@Rikk J'ai le même problème  ave le message: ?0: attempt to index field 'font' ( a nil value)

merci d'apporter une solution et de nous en informer .

NB: Cette erreur s'est produite ce 09/11/2020

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 10, 2020 Nov 10, 2020

Copy link to clipboard

Copied

same issue on my side

Votes

Translate

Translate

Report

Report
New Here ,
Nov 10, 2020 Nov 10, 2020

Copy link to clipboard

Copied

Downgrading LR version to work around this has somehow corrupted my win 10 system and now it won’t boot or do a startup repair. Thanks, Adobe.

Votes

Translate

Translate

Report

Report
Participant ,
Nov 10, 2020 Nov 10, 2020

Copy link to clipboard

Copied

Wow--I feel for you.  Just ridiculous.  Still no news from Adobe. 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Nov 10, 2020 Nov 10, 2020

Copy link to clipboard

Copied

After upgrading Lightroom classic to ver 10.0, I get the following error message every time I try to email a photo from within the program:

20201012_EmailExport-cee1bb3b-0897-4250-ba7b-e0e7df8b60c1-11067264.jpg

Here is my system configuration:

20201110_Speccy-d5ae75ca-9747-4793-9569-0e988cf3da59-221002120.jpg

Is there a fix for this BUG?

Votes

Translate

Translate

Report

Report
Contributor ,
Nov 10, 2020 Nov 10, 2020

Copy link to clipboard

Copied

Fixes are generally delivered in next release so you will have to wait 10.1.

.
Sheepdog trying to help Lightroom and Photoshop beginners

Votes

Translate

Translate

Report

Report
Engaged ,
Nov 10, 2020 Nov 10, 2020

Copy link to clipboard

Copied

Adobe has known about this for months. It hasn't been resolved in the past two releases, including with 10.0. I've virtually given up on this Lightroom feature and various Photoshop features that haven't worked for years.

Adobe's Tech supports folks work like rented mules to try and help but they can't resolve programming issues.

Votes

Translate

Translate

Report

Report
Participant ,
Nov 10, 2020 Nov 10, 2020

Copy link to clipboard

Copied

Wow---if this thing isn't fixed soon--I'm out of the entire Adobe universe.  Really this is nuts. 

Votes

Translate

Translate

Report

Report
New Here ,
Nov 10, 2020 Nov 10, 2020

Copy link to clipboard

Copied

an identical problem. but FTP-server export also not ok!!!!

Votes

Translate

Translate

Report

Report