Normally, installing openSUSE would add a boot entry to the UEFI firmware.
My wild guess: ACER has decided to control the boot process itself, instead of allowing the UEFI firmware to control it. However, in this case it found that it did not have a suitable boot entry. So it created one from the firmware boot entry that openSUSE had installed.
In any case, if it is booting properly and if your root file system is using the partition that you assigned, then it is likely that it is working as you intended.
Hi
Wow, lot’s of duplicate entries… your last boot was from 000D, you could clean them all out, you really only need the one, I would set the default to 0000 via;
efibootmgr -n 0000
That sets it to boot from the 0000 nvram entry temporarily, once set reboot the system and check the output again, if all ok, we can set that and remove all the other ones with another efibootmgr command.