# Where can we reports bugs?

**URL:** <https://forums.suse.com/t/where-can-we-reports-bugs/44044>\
**Category:** SUSE Liberty Linux\
**Created:** [September 12, 2024, 10:03am UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044 "2024-09-12T10:03:28Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![sp-de-nrw](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@sp-de-nrw](https://forums.suse.com/u/sp-de-nrw)\
**Post date:** [September 12, 2024, 10:03am UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/1 "2024-09-12T10:03:28Z")

</div>

We have currently a bug with SuSE Liberty Linux and EFI boot, but only a lite subscription. That has no support, which is fine but is there still a way to report the bug? Other users would also benefit.

---

<div class="post-metadata">

**Author:** ![sp-de-nrw](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@sp-de-nrw](https://forums.suse.com/u/sp-de-nrw)\
**Post date:** [September 12, 2024, 10:06am UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/2 "2024-09-12T10:06:43Z")

</div>

Some of the EFi systems will fail to boot after the first `yum update` because the provided `shim-x64` package removes the `shim*.efi` files from `EFI/centos/` inside the EFI partition. Copying those files from `EFI/redhat` to `EFI/centos` makes the system bootable again.

---

<div class="post-metadata">

**Author:** ![JKWMoore](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jkwmoore/32/11609_2.png) [@JKWMoore](https://forums.suse.com/u/JKWMoore)\
**Post date:** [October 7, 2024, 10:11am UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/3 "2024-10-07T10:11:43Z")

</div>

I too would like to know an answer to this. Same situation, have a lite subscription and I am seeing checksum errors on mirror sync which I suspect are due to metadata on the repo being incorrect.

```auto
W, [2024-10-07T11:11:21.367585 #11672] WARN -- : × bind-lite-devel-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.374102 #11672] WARN -- : × bind-libs-lite-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.377064 #11672] WARN -- : × bind-pkcs11-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.378400 #11672] WARN -- : × bind-pkcs11-utils-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.384181 #11672] WARN -- : × bind-sdb-chroot-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.390344 #11672] WARN -- : × bind-sdb-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.391426 #11672] WARN -- : × bind-utils-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.400482 #11672] WARN -- : × bind-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match
W, [2024-10-07T11:11:21.479580 #11672] WARN -- : × bind-pkcs11-libs-9.11.4-26.P2.el7_9.16.x86_64.rpm - Checksum doesn't match

```

Edit:

I attempted to clear and resync the mirrors to see if this would clear things up. It has not:

```bash
rmt-cli repos disable 6747 6748 6986 6987
rmt-cli repos clean
rmt-cli repos enable 6747 6748 6986 6987
rmt-cli sync
rmt-cli mirror

```

---

<div class="post-metadata">

**Author:** ![Zulu](https://avatars.discourse-cdn.com/v4/letter/z/a9adbd/32.png) [@Zulu](https://forums.suse.com/u/Zulu)\
**Post date:** [October 9, 2024, 4:54pm UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/4 "2024-10-09T16:54:07Z")

</div>

Exaclt the same error as @JKWMoore reported. Unfortunately, in the same boat being a lite user with no support.  
Slightly frustrated as what is the point of paying for the repository if you can use it due to checksum issues. Hope someone from Suse sees this and fixes the issue.

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [October 10, 2024, 2:34am UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/5 "2024-10-10T02:34:43Z")

</div>

@JKWMoore @sp-de-nrw @sp-de-nrw Hi, have you logged into SUSE Customer Center and opened a Support Request there?

---

<div class="post-metadata">

**Author:** ![Zulu](https://avatars.discourse-cdn.com/v4/letter/z/a9adbd/32.png) [@Zulu](https://forums.suse.com/u/Zulu)\
**Post date:** [October 10, 2024, 8:37am UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/6 "2024-10-10T08:37:29Z")

</div>

While I’ve purchased extended CentOS support, I’m unable to submit a support ticket due to the lack of paid support. This is frustrating, especially since the issue is related to SUSE. It seems that the only solution is to either buy additional support or deal with the problem.

---

<div class="post-metadata">

**Author:** ![JKWMoore](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jkwmoore/32/11609_2.png) [@JKWMoore](https://forums.suse.com/u/JKWMoore)\
**Post date:** [October 10, 2024, 12:24pm UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/7 "2024-10-10T12:24:59Z")

</div>

Same situation as Zulu says above. I’m unable to submit a support ticket due to having a Lite subscription.

i.e

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/1/19b7841b66b2dcdbec96b58e3a4ce921115fa8f9.png)

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [October 10, 2024, 1:03pm UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/8 "2024-10-10T13:03:21Z")

</div>

@JKWMoore @Zulu @sp-de-nrw I guess you could try Bugzilla then… [https://bugzilla.suse.com/](https://bugzilla.suse.com/)

---

<div class="post-metadata">

**Author:** ![Zulu](https://avatars.discourse-cdn.com/v4/letter/z/a9adbd/32.png) [@Zulu](https://forums.suse.com/u/Zulu)\
**Post date:** [October 10, 2024, 1:29pm UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/9 "2024-10-10T13:29:06Z")

</div>

[1231501 – rmt-cli mirror failing](https://bugzilla.suse.com/show_bug.cgi?id=1231501) raised.  
I’m hoping for the best, but I’m not expecting much.

---

<div class="post-metadata">

**Author:** ![JKWMoore](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jkwmoore/32/11609_2.png) [@JKWMoore](https://forums.suse.com/u/JKWMoore)\
**Post date:** [October 14, 2024, 9:10am UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/10 "2024-10-14T09:10:46Z")

</div>

N.b. I now see the mirror working correctly.

---

<div class="post-metadata">

**Author:** ![rodferrior](https://avatars.discourse-cdn.com/v4/letter/r/ec9cab/32.png) [@rodferrior](https://forums.suse.com/u/rodferrior)\
**Post date:** [October 25, 2024, 5:57pm UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/11 "2024-10-25T17:57:00Z")

</div>

> [@sp-de-nrw](#):
>
> We have currently a bug with SuSE Liberty Linux and EFI boot, but only a lite subscription. That has no suppo[r](https://trueflowmedia.com/jeffrey-cappo-net-worth/)t, which is fine but is there still a way to report the bug? Other users would also benefit.

SuSE maintains community support channels, such as the openSUSE Forums and the openSUSE Bugzilla. While openSUSE is the community branch and distinct from SuSE Liberty Linux, SuSE engineers monitor these forums, and related issues are sometimes resolved in both community and enterprise versions.

---

<div class="post-metadata">

**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\
**Post date:** [October 28, 2024, 6:44pm UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/12 "2024-10-28T18:44:01Z")

</div>

> [@rodferrior](#):
>
> SuSE maintains community support channels, such as the openSUSE Forums and the openSUSE Bugzilla. While openSUSE is the community branch and distinct from SuSE Liberty Linux, SuSE engineers monitor these forums, and related issues are sometimes resolved in both community and enterprise versions.

Whilst the openSUSE project is sponsored by SUSE openSUSE is independent from SUSE - SUSE are not responsible for openSUSE resources such as their Forums or Bugzilla. I’ll also note that these SUSE Forums are not the official route to SUSE support - instead you should open a support case via the SUSE Customer Center.

---

<div class="post-metadata">

**Author:** ![sp-de-nrw](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@sp-de-nrw](https://forums.suse.com/u/sp-de-nrw)\
**Post date:** [October 30, 2024, 8:56am UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/13 "2024-10-30T08:56:48Z")

</div>

> [@smflood](#):
>
> (…)instead you should open a support case via the SUSE Customer Center.

I would if I could.

The lite subscription causes this tiny detail in the customer portal and hence the question in this thread: “You are not currently entitled to use the support system.”

---

<div class="post-metadata">

**Author:** ![sp-de-nrw](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@sp-de-nrw](https://forums.suse.com/u/sp-de-nrw)\
**Post date:** [October 30, 2024, 8:58am UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/14 "2024-10-30T08:58:33Z")

</div>

It is disabled caused by the lite subscription (in our case).

---

<div class="post-metadata">

**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\
**Post date:** [November 7, 2024, 6:20pm UTC](https://forums.suse.com/t/where-can-we-reports-bugs/44044/15 "2024-11-07T18:20:07Z")

</div>

> [@sp-de-nrw](#):
>
> I would if I could.
> 
> The lite subscription causes this tiny detail in the customer portal and hence the question in this thread: “You are not currently entitled to use the support system.”

Yes I saw your earlier post but wanted to provide the correct information and general procedure. I did previously flag this thread to a SUSE contact and will ask the question about support for Liberty Lite.
