February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1198621] New: systemd-boot: mach bunt
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1198621 Bug ID: 1198621 Summary: systemd-boot: mach bunt Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: snwint(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1198583 Found By: --- Blocker: --- If we go for systemd-boot we need it to look nice. How about gfxboot for it? :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1146936] New: nmcli-examples: add examples of bonding + vlan + bridge
by bugzilla_noreply＠novell.com 04 Apr '23

04 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1146936 Bug ID: 1146936 Summary: nmcli-examples: add examples of bonding + vlan + bridge Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: william.brown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Configuring a bond + vlan + bridge is not completely straightforward or clear with nmcli. An example should be added such as: nmcli conn add type bond con-name bond0 ifname bond0 mode 802.3ad ipv4.method disabled ipv6.method ignore nmcli connection add type ethernet con-name bond0-eth1 ifname eth1 master bond0 slave-type bond nmcli connection add type ethernet con-name bond0-eth2 ifname eth2 master bond0 slave-type bond nmcli connection add type bridge con-name net_18 ifname net_18 ipv4.method disabled ipv6.method ignore nmcli connection add type vlan con-name bond0.18 ifname bond0.18 dev bond0 id 18 master net_18 slave-type bridge This is suitable for libvirt/vms to use the bridges. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1176818] New: Wrong public keys in openSUSE-build-key for verifying container image signatures
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1176818 Bug ID: 1176818 Summary: Wrong public keys in openSUSE-build-key for verifying container image signatures Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: meissner(a)suse.com Reporter: rhafer(a)suse.com QA Contact: qa-bugs(a)suse.de CC: sgrunert(a)suse.com Found By: --- Blocker: --- The openSUSE-build-keys package contains /usr/lib/rpm/gnupg/keys/opensuse-container-key.asc and /usr/lib/rpm/gnupg/keys/suse-container-key.asc which symlink to the "openSUSE Project Signing Key <opensuse(a)opensuse.org>" and "SuSE Package Signing Key <build(a)suse.de>" but apparently the images we provide on registry.opensuse.org are signed by some other key. When enabling signature verification for "registry.opensuse.org" using the key "/usr/lib/rpm/gnupg/keys/opensuse-container-key.asc" all images fail to verify because the images are signed with a different key. Looking into the signatures, which are fetched from "https://registry.opensuse.org/sigstore/" it seem the images are signed by a key with the ID "D754694F9AB48CE9". The key in /usr/lib/rpm/gnupg/keys/opensuse-container-key.asc however AFAICS is: "B88B2FD43DBDC284". So something is wrong here. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1205802] New: VUL-0: CVE-2022-39346: nextcloud: Missing length validation of user displayname allows to generate an SQL error
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1205802 Bug ID: 1205802 Summary: VUL-0: CVE-2022-39346: nextcloud: Missing length validation of user displayname allows to generate an SQL error Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/348950/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: ecsos(a)schirra.net Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- rh#2148815 Nextcloud server is an open source personal cloud server. Affected versions of nextcloud server did not properly limit user display names which could allow a malicious users to overload the backing database and cause a denial of service. It is recommended that the Nextcloud Server is upgraded to 22.2.10, 23.0.7 or 24.0.3. There are no known workarounds for this issue. https://github.com/nextcloud/security-advisories/security/advisories/GHSA-6… https://github.com/nextcloud/server/pull/33052 https://hackerone.com/reports/1588562 References: https://bugzilla.redhat.com/show_bug.cgi?id=2148815 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39346 https://github.com/nextcloud/security-advisories/security/advisories/GHSA-6… http://www.cvedetails.com/cve/CVE-2022-39346/ https://github.com/nextcloud/server/pull/33052 https://www.cve.org/CVERecord?id=CVE-2022-39346 https://hackerone.com/reports/1588562 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1208756] New: Goodix GDIX1003/GT9110P i2c device is Unsupported
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208756 Bug ID: 1208756 Summary: Goodix GDIX1003/GT9110P i2c device is Unsupported Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: need2burn(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865155 --> http://bugzilla.opensuse.org/attachment.cgi?id=865155&action=edit dmesg output I have a new version of a POS-X Ion 8 tablet that seems to have some hardware not yet supported by openSUSE. This doesn't work on any version of openSUSE. The manufacturer tells me it's a Goodix T080642-01D-GTC, with a GT9110P IC. The OS (openSUSE Tumbleweed 20230226 running 6.1.12-1-default) reports it under /sys/bus/i2c/devices as i2c-GDIX1003:00. No dmesg logs mention goodix, the driver does not load, and it does not pick up the touchscreen when loaded. Evtest does not show the device either. From what I can tell looking at the Goodix driver, it only refers to GDIX1001 and GDIX1002, and no mention of GDIX1003. Attaching dmesg and can provide any other information. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1202792] New: OpenVPN in Leap 15.4 seems to be built without --enable-iproute2
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1202792 Bug ID: 1202792 Summary: OpenVPN in Leap 15.4 seems to be built without --enable-iproute2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: georg.jansing(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using OpenVPN for several years on openSUSE (42.2 or so?) and always used a setup with a non-root user as advertized in https://openvpn.net/community-resources/how-to/#security (Unprivileged mode) This requires "--enable-iproute2" to be passed to configure at build time (at least as per current documentation). Either this was not the case in the Leap 15.3 version (2.4.x) or it was disabled in the 15.4 version for some reason. Could this flag be enabled (again) for the 15.4 package or is there a strong reason against it? From a -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1172949] New: iphone not recognized when plugged into usb port
by bugzilla_noreply＠suse.com 02 Apr '23

02 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1172949 Bug ID: 1172949 Summary: iphone not recognized when plugged into usb port Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: 1chip(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838816 --> http://bugzilla.opensuse.org/attachment.cgi?id=838816&action=edit dmesg output when Iphone x is plugged into usb port it only charges.Can't import any photos and does not show up in dolphin. Using opensuse leap 15.2 with KDe plasma 5.18.5 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1208543] New: Leap 15.5 beta Network Image points to 15.4 repos
by bugzilla_noreply＠suse.com 02 Apr '23

02 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208543 Bug ID: 1208543 Summary: Leap 15.5 beta Network Image points to 15.4 repos Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: kwizzz(a)googlemail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Used Network Image openSUSE-Leap-15.5-NET-x86_64-Build408.2-Media.iso Downloaded from http://get.opensuse.org/leap/15.5/ Issue: After downloading the repo data, the installer warns ��To use the selected repository a matching boot image is needed. Download it now and restart?�� If I click on Yes, it looks like the system is restarted with a Leap 15.4 boot image. Reason: The repo location used by the 15.5 Network Image is set to http://download.opensuse.org/distribution/leap/15.4/repo/oss, as confirmed by looking into installer details (Expert �� Show Config) and by checking debug output on tty3 (which contains only .../leap/15.4/... paths. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1202078] New: Plasma wayland cannot be set as default with autologin
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202078 Bug ID: 1202078 Summary: Plasma wayland cannot be set as default with autologin Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Leap 15.4 with Plasma KDE 5.24.4 and all updates installed with autologin enabled. It works fine on X11. I tried to set Plasma Wayland as default via "System Settings-->Startup and Shutdown-->Login Screen (SDDM)-->Behavior-->choose Plasma Wayland", but then I will end in console instead in Plasma. Plasma Wayland itself works, if I keep old settings with autologin into X11 and then I just unlog to SDDM, change session and log with Wayland, it is ok. Just autologin will not boot. I can reproduce it both on my freshly installed Laptop with i5-11400H cpu with integrated graphics and in VirtualBox. I tested behavior in Fedora 36 without updates (similar components, Plasma 5.24.3, etc) and there autologin settings works fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1200983] New: mouse & keyboard not available in X/plasma
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 Bug ID: 1200983 Summary: mouse & keyboard not available in X/plasma Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: opensuse(a)mike.franken.de QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Starting with a few Tumbleweed snapshots ago I always have the problem, that mouse and keyboard are not working in my X/plasma desktop. I always have to unplug und plug them in again. After that they work as expected. There are no obvious error messages, that could help me to solve this problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 24