June 2023 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1212203] fails to boot to the new system after manual transational update
by bugzilla_noreply＠suse.com 12 Jun '23

12 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212203 https://bugzilla.suse.com/show_bug.cgi?id=1212203#c2 Ignaz Forster <iforster(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FEATURE CC| |iforster(a)suse.com --- Comment #2 from Ignaz Forster <iforster(a)suse.com> --- As Thorsten already pointed out this is intentional behavior: Ignoring unavailable repositories may even lead to system downgrades, so this is treated as an error. Please remove, disable or fix the repository in question. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212203] fails to boot to the new system after manual transational update
by bugzilla_noreply＠suse.com 12 Jun '23

12 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212203 https://bugzilla.suse.com/show_bug.cgi?id=1212203#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kukuk(a)suse.com --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Vishal Goswami from comment #0) > 2.there will not be any errors except "zypper --no-cd dup on > /.snapshots/5/snapshot failed with exit code 106! > Use '--interactive' for manual problem resolution." after the update from zypper manual page: " 106 - ZYPPER_EXIT_INF_REPOS_SKIPPED Some repository had to be disabled temporarily because it failed to refresh. You should check your repository configuration (e.g. zypper ref -f)." Please fix your repositories. It's not the fault of transactional-update or zypper, if your repository setup creates errors. > 3.sudo reboot > Actual Results: > you will boot in the original snapshot without the update. Ok, so everything is working: transactional-update could not apply the updates without errors and thus does not boot into a possible broken system. > Expected Results: > you should boot in the updated system NO! transactional-update should never ever boot into a possible broken system! If you want that, you don't need transactional-update but you can stay with a traditional system. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212203] New: fails to boot to the new system after manual transational update
by bugzilla_noreply＠suse.com 11 Jun '23

11 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212203 Bug ID: 1212203 Summary: fails to boot to the new system after manual transational update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: techvish81(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36 Build Identifier: i tried many times but it doesnt work , i disabled the automatic transactional update timer and tried to manually update several times but it only works if ignore-unknown is added to the command. (which i found from an old related bug , but cannot find now as it was closed.) so, i can do "sudo transactional-update run zypper --ignore-unknown dup" and it magically works but if i use the normal "sudo transactional-update dup" and "sudo reboot" it just boots to the snapshot before update. Reproducible: Always Steps to Reproduce: 1.try manually updating with "sudo transactional-update dup" 2.there will not be any errors except "zypper --no-cd dup on /.snapshots/5/snapshot failed with exit code 106! Use '--interactive' for manual problem resolution." after the update 3.sudo reboot Actual Results: you will boot in the original snapshot without the update. Expected Results: you should boot in the updated system right now on kernel 6.3.6 snapshot 20230608 my system is i5 6300u (dell e5470 laptop) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208652] (MicroOS) no video thumbnails on Dolphin or videoplayback on mpv (rpm)
by bugzilla_noreply＠suse.com 10 Jun '23

10 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1208652 https://bugzilla.suse.com/show_bug.cgi?id=1208652#c10 Joed L <jlopez777+opensuse(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM CC| |jlopez777+opensuse(a)gmail.co | |m Status|REOPENED |RESOLVED --- Comment #10 from Joed L <jlopez777+opensuse(a)gmail.com> --- So this should go to flatpak devs for enhancing dolphin. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211841] New: cp: cannot create regular file (Emacs distrobox-export)
by bugzilla_noreply＠suse.com 10 Jun '23

10 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211841 Bug ID: 1211841 Summary: cp: cannot create regular file (Emacs distrobox-export) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: sjaniska(a)atmarama.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, attempt to distro-export Emacs from Tumbleweed container on MicroOS (Aeon) yields very strange error: $ distrobox-export --app emacs cp: cannot create regular file '/run/host/home/gour/.local/share/icons/emacs/private/org-roam-ui/.git/objects/pack/pack-b37f39824f3b0034f42e7324cb2296562bbcd2fc.idx': Permission denied cp: cannot create regular file '/run/host/home/gour/.local/share/icons/emacs/private/org-roam-ui/.git/objects/pack/pack-b37f39824f3b0034f42e7324cb2296562bbcd2fc.pack': Permission denied Any hint? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1212190] New: Cockpit Software Updates screen has no scrollbars
by bugzilla_noreply＠suse.com 09 Jun '23

09 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212190 Bug ID: 1212190 Summary: Cockpit Software Updates screen has no scrollbars Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: robert.koktan(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867490 --> https://bugzilla.suse.com/attachment.cgi?id=867490&action=edit Cockpit Software Updates screen # cat /etc/os-release NAME="openSUSE MicroOS" # VERSION="20230604" The Cockpit Software Updates screen has no scrollbars, so one cannot scroll down to see all available snapshots. Not that one ought to rollback to any snapshots that may be down there at the bottom of the list, but they ought to at least be visible. See attached screencap. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1211840] New: "permission denied" for Viber (flatpak)
by bugzilla_noreply＠suse.com 08 Jun '23

08 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211840 Bug ID: 1211840 Summary: "permission denied" for Viber (flatpak) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: sjaniska(a)atmarama.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, when I try to launch Viber on Aeon (MicroOS) installed from the Flatpak I get: "$ flatpak run com.viber.Viber /app/extra/viber/Viber: error while loading shared libraries: libQt6WebEngineCore.so.6: cannot enable executable stack as shared object requires: Permission denied" Any hint? -- You are receiving this mail because: You are the assignee for the bug.

1 1