April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222184] New: SDDM fails after upgrade to Plasma 6
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222184 Bug ID: 1222184 Summary: SDDM fails after upgrade to Plasma 6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: o.g.m.belleux(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873946 --> https://bugzilla.suse.com/attachment.cgi?id=873946&action=edit History of sudo zypper -v dup --allow-vendor-change Hello, After unsuccessful attempts to upgrade to Plasma 6 (see bug 1221515), I've finally been able to give it a go. The upgrade went well until the reboot. First of all, SDDM didn't display the theme and an error message in red indicating that it couldn't find a file. I logged into TTY and searched for and installed the missing RPMs, which are not installed by default: - libQt6QuickLayouts6 - libQt6Xml6 - libQt6Svg6 From there SDDM displays the theme. By entering login + password, there is a connection attempt then back to Greeter with Wayland as X11. In TTY , I found that libQt6Core5Compat6 was missing for wayland. I was able to launch a plasma 6 session under wayland with an ugly display that didn't respect the theme colours, among other oddities. However, with X11 I get a black screen for SDDM. So I can't connect. So reboot + snapper rollback to plasma 5 for now. I attach the upgrade history for information. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221515] New: unsatisfied dependency problems for Plasma 6 / Gear 24.02
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221515 Bug ID: 1221515 Summary: unsatisfied dependency problems for Plasma 6 / Gear 24.02 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: o.g.m.belleux(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873571 --> https://bugzilla.suse.com/attachment.cgi?id=873571&action=edit result of ```sudo zypper -v dup -D --allow-vendor-change|tee zypper_dup.txt``` I added kde repositories as described in https://en.opensuse.org/SDB:KDE_repositories and try ```sudo zypper -v dup -D --allow-vendor-change``` which give me 2 Problems: – Problem: the to be installed libKPim6Mime6-24.02.0-kf.276.1.x86_64 requires 'kmime >= 24.02.0', but this requirement cannot be provided – Problem: the to be installed kdepim-runtime-24.02.0-kf.347.1.x86_64 requires 'akonadi', but this requirement cannot be provided I checked with zypper se and at the openbuildservice; kmime and akonadi are availables. I've tried to solve these problems, but it just keeps producing more and more of them. I did ```sudo zypper -v dup -D --allow-vendor-change|tee zypper_dup.txt``` choosing the uninstall solution with the smallest number for info. I attach the file zypper_dup.txt. I think these are simple problems of dependencies and "conflict" or "obsolete" in specs due to changes between "KDE 5" and "KDE 6". In doubt, I'd rather wait for them to be resolved than break everything before upgrading to Plasma 6. Thanks to all the KDE Team for the great work you do voluntarily. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1222211] New: "Forget file" in "Recent Files" of the "Application Menu" starter seems to do nothing (KDE Plasma 6, Tumbleweed 20240329)
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222211 Bug ID: 1222211 Summary: "Forget file" in "Recent Files" of the "Application Menu" starter seems to do nothing (KDE Plasma 6, Tumbleweed 20240329) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ingo.strauch(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I've recently updated to version 20240329 of Tumbleweed which for me was the upgrade of KDE Plasma 5 to 6. Since then, forgetting files via the start menu does not work as expected anymore. Steps to reproduce * open the "Application Menu" starter * click "Recent Files" at the top to show the list of recent files * right-click on one of the files and select "Forget File" from the context menu Expected behavior * the file gets removed from the list immediately (just like it did with KDE Plasma 5) Actual behavior * the file is still shown in the list As it turns out the file does get forgotten because it is removed from the list in a fresh login session, so it seems to me it's just a UI refresh problem. I still find it quite annoying because my use case often is to open files from the "Recent Files" list where I first have to remove several (to me) irrelevant entries before the document I'm looking for is shown. I've also tested this with a fresh user account and the problem exists there as well. Forgetting files does work as expected in "Application Starter" but not with "Application Menu". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221840] podman with pasta (passt) fails with apparmor
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221840 https://bugzilla.suse.com/show_bug.cgi?id=1221840#c14 --- Comment #14 from Danish Prakash <danish.prakash(a)suse.com> --- Thanks for the patch, even though I can invoke `pasta` without any errors, I'm still getting the same permission denied error on the netns: > Couldn't open network namespace /proc/9080/ns/net: Permission denied Adding the following rule to usr.bin.passt doesn't help either: > /proc/@{pid}/ns/ r, On the contrary, setting the two usr.bin.pas* profiles to complain mode, things are back to normal so perhaps the rules are still not right? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|virt-bugs(a)suse.de |llrainey15(a)gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133158] VUL-1: CVE-2019-0223: qpid-proton: Apache Qpid Proton TLS Man in the Middle Vulnerability
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1133158 https://bugzilla.suse.com/show_bug.cgi?id=1133158#c9 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |security-team(a)suse.de --- Comment #9 from Fridrich Strba <fstrba(a)suse.com> --- . -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133158] VUL-1: CVE-2019-0223: qpid-proton: Apache Qpid Proton TLS Man in the Middle Vulnerability
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1133158 https://bugzilla.suse.com/show_bug.cgi?id=1133158#c8 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fstrba(a)suse.com |screening-team-bugs(a)suse.de --- Comment #8 from Fridrich Strba <fstrba(a)suse.com> --- Released, so assigning to security for closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 https://bugzilla.suse.com/show_bug.cgi?id=1222186#c8 Claudio Marcial Peon <claudio(a)datacor.net.ar> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |claudio(a)datacor.net.ar --- Comment #8 from Claudio Marcial Peon <claudio(a)datacor.net.ar> --- Thanks Robert. I can confirm that making those changes you suggest on https://bugzilla.suse.com/show_bug.cgi?id=1222186#c3 everything works again. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c30 --- Comment #30 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- installed kernel-default-6.8.2-2.1.gb88b81e.x86_64.rpm and restarted about 20 times. Can not trigger the kernel panic. Is it possible the issue is fixed recently? I assume we should look at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/driv…. This commit seems suspicious because it seems a timing issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/d… Not sure if that would even result in a kernel panic. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221803] plasma6 - several processes dumping core
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221803 https://bugzilla.suse.com/show_bug.cgi?id=1221803#c2 Reinhard Mutz <Reinhard.Mutz(a)frei-leipzig.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Reinhard.Mutz@frei-leipzig. | |de --- Comment #2 from Reinhard Mutz <Reinhard.Mutz(a)frei-leipzig.de> --- I suffered from the same bug and at least I found a workaround. First to say I installed a new fresh version of tumblewee, dated 2024-03-24, on my laptop and it work perfect. My working machine has an Intel(R) Core(TM) i7-3770K CPU and 16 GB of RAM. I use TW from the very beginning and I am happy with that. After an update in the last days of February plasma coulnd be started. I did a lot of work and ended up with a workaround. I fount that my current installed plama uses a direct in /home/user/... but the new intalled plasma uses a directory /usr/local/share/plasma/.... My workaround: scp -p -r /usr/share/plasma $HOME/.local/share/ After a relogin it worked and showed my saved sessions as it did before. more details: I started plasma "strace plasmashell" > plasmash.log 2>&1". You can see all commands before the crash "tail -50 plasmash.log". The log tells You that the directories /usr/share/plasma $HOME/.local/share/ are in some way mismatched. proposal for solution: the maintainers of plasma may please decide which directory to use and give hints for any updates. I did not expect such a behaviour because I used KDE3 and saw all updates up to version KDE5 worked correctly. From my point of view (experience) I would never expect such an error but nobody is perfect. -- You are receiving this mail because: You are on the CC list for the bug.

1 0