Error when load Lora

[ChowMein47]

Lora already installed but i can't use it. plz help me!

locon load lora method
loading Lora /content/cagliostro-colab-ui/models/Lora/koreanDollLikeness_v20.safetensors: AttributeError
Traceback (most recent call last):
File "/content/cagliostro-colab-ui/extensions/a1111-sd-webui-locon/scripts/../../../extensions-builtin/Lora/lora.py", line 222, in load_loras
lora = load_lora(name, lora_on_disk.filename)
File "/content/cagliostro-colab-ui/extensions/a1111-sd-webui-locon/scripts/main.py", line 370, in load_lora
is_sd2 = 'model_transformer_resblocks' in shared.sd_model.lora_layer_mapping
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1614, in getattr
raise AttributeError("'{}' object has no attribute '{}'".format(
AttributeError: 'LatentDiffusion' object has no attribute 'lora_layer_mapping'

[Linaqruf]

what model name and what lora link?

[ChowMein47]

@Linaqruf this is the link. I tried to use other Lora from Naonaovn & Luxluna but i still facing the same issue

https://huggingface.co/Kanbara/doll-likeness-series/resolve/main/koreanDollLikeness_v20.safetensors

[Linaqruf]

the lora is loaded successfully with chilloutmix-ni as a model
I think the problem is

• Your model isn't SDv1.x model because KoreanDollLikeness was based on that
• The LoRA is corrupted after downloaded
• This probably happens in repo_type = AUTOMATIC1111, and AUTOMATIC1111-Dev

[PhoenixEugene]

@Linaqruf Hello there. Since apparently I'm now facing a similar (or the same?) issue @YellowStar11 faced a few days ago, I chose to write this here instead of creating a new issue. (Whatever this is, it's definitely weird, because I used the Colab with the A1111 repo just yesterday and the day before and had no problems loading LoRAs on either occasion)

You can see in the screenshot that something isn't right. After I got that error the first time, I hit the "Disconnect and delete runtime" button and tried everything again from scratch, and still the problem persisted. As for your possible explanations above:

1. I only use SDv1.5 models, I've never tried or even wanted to use SDv2 models before. In this instance, I believe the model was Galena DEDUX (NSFW)
2. The LoRA "add_detail" wasn't the only LoRA that didn't want to load. All of them didn't. All 16 of them. So I'm not so sure about the chances of ALL LoRA files getting corrupted after being downloaded, TWICE.
3. Yes, as I mentioned before, it was the A1111 repo.

This leads me to believe that it's something with the A1111 repo, right? Then again, it worked fine just yesterday, what could've possibly changed? And if it is a problem with the repo, is there a fix?

[Linaqruf]

Hi, now I understand the problem. The problem is as follows:

• Your LoRA is trained with the LyCORIS module, and you're using the a1111-sd-webui-locon extension to load it.
• However, the a1111-sd-webui-locon extension is deprecated. I still use it for backward compatibility.
• Automatic1111 now supports LoRA with expanded Conv2d, also known as LoCon, and it has a code conflict with LoCon extensions since May 15th.
• And current commit break the extensions, makes it more not usable because it throw filename error. Compatibility with recent a1111 dev KohakuBlueleaf/a1111-sd-webui-locon#39

That's why the LoRA can't be loaded. This is also mentioned in the LoCon extension repository

• [CRITICAL]All LoRAs not working anymore KohakuBlueleaf/a1111-sd-webui-locon#40 <-- similar with your issue
• 'LatentDiffusion' object has no attribute 'lora_layer_mapping' after today git pull stable-diffusion-webui KohakuBlueleaf/a1111-sd-webui-locon#38 <-- similar with @YellowStar11

For a temporary fix, don't set update extensions to True. I pushed a commit last night to set it to False by default. Also, avoid using AUTOMATIC1111-Dev as it's a temporary fix. If you're looking for a long-term solution, here are some options:

1. If it's LoCon without cp_decomposition, try loading it in sd-webui-additional-networks.
2. I have also installed a1111-sd-webui-lycoris, which is a continuation of a1111-sd-webui-locon. If the same error occurs again:
   • You can change the prefix for your LoRA from <lora:... to <lyco:.....
   • Or load your LoCon from the Lycoris tab in the extra network. I centralized all LoRA paths to the folder /models/LoRA, so you can load LoRA implementations from Kohya, Lycoris, or Automatic1111 from there.

I also plan to delete a1111-sd-webui-locon after all the problems are resolved. I know it's complicated, but because there are no universal rules to implement LoRA, people now make their own implementations, resulting in the same LoRA being different due to different algorithms.

Thank you.

[PhoenixEugene]

Thank you so much for the thorough explanation! I'll be trying today with "update extensions" set to false as you suggested. Again, thanks!