April 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1209197] New: Kernel 6.2.2 with older NVIDIA graphics won't boot (freeze after 4.5 sec into boot process)
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209197 Bug ID: 1209197 Summary: Kernel 6.2.2 with older NVIDIA graphics won't boot (freeze after 4.5 sec into boot process) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sddrossy(a)aol.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi! On Tumbleweed, updated this morning (20230311 with kernel 6.2.2) and since kernel 6.2.1 won't boot without "nomodeset", freezing when switching graphics after about 4.5 sec into boot: https://paste.opensuse.org/pastes/22f64611e02d Here is dmesg of successful boot with kernel 6.1.12 https://paste.opensuse.org/pastes/194765a7e091 output of lspci and inxi can be found in this thread https://forums.opensuse.org/t/no-boot-with-kernel-6-2/164791 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1209970] Trimmed "Leap" logo on the default wallpaper
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209970 https://bugzilla.suse.com/show_bug.cgi?id=1209970#c1 Maurizio Galli <maurizio.galli(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maurizio.galli(a)suse.com --- Comment #1 from Maurizio Galli <maurizio.galli(a)suse.com> --- I think it's better to open an issue here: https://github.com/openSUSE/artwork -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210031] On login, xfce session is corrupted some times
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210031 https://bugzilla.suse.com/show_bug.cgi?id=1210031#c2 Maurizio Galli <maurizio.galli(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maurizio.galli(a)suse.com --- Comment #2 from Maurizio Galli <maurizio.galli(a)suse.com> --- To me this sounds like a configuration conflict introduced by your backup copy. Logout of Xfce and log into a tty console and move the following file in your home dir to backup location or delete it: ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml Log into Xfce again and see if everything works. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 1203190] VUL-1: CVE-2022-35931: nextcloud: Password Policy app could generate passwords that would be block
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1203190 https://bugzilla.suse.com/show_bug.cgi?id=1203190#c3 --- Comment #3 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2023:0083-1: An update that fixes three vulnerabilities is now available. Category: security (important) Bug References: 1203190,1205802,1208591 CVE References: CVE-2022-35931,CVE-2022-39346,CVE-2023-25579 JIRA References: Sources used: openSUSE Backports SLE-15-SP4 (src): nextcloud-23.0.12-bp154.2.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209985] Secure boot violation
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209985 https://bugzilla.suse.com/show_bug.cgi?id=1209985#c19 --- Comment #19 from Andrei Borzenkov <arvidjaar(a)gmail.com> --- (In reply to Fabian Vogt from comment #17) > (In reply to Andrei Borzenkov from comment #16) > > Oh, and what is the actual error in the first place? We may be facing > > entirely different issue here. > > I made a screenshot of the initial error with verbose shim boot enabled. The > main messages were: Attaching this screenshot would be better. Note that BootCurrent is 0019 which means firmware used "boot from NVMe" entry. In which case it loaded /boot/efi/EFI/boot/bootx64.efi. While this file itself looks OK, it loads fallback.efi and it looks old. objcopy -O binary -j .sbat /boot/efi/EFI/boot/bootx64.efi objcopy -O binary -j .sbat /boot/efi/EFI/boot/fallback.efi Still even if loading fallback.efi fails (it does for me) it should then try to load MokManager.efi. objcopy -O binary -j .sbat /boot/efi/EFI/boot/MokManager.efi Any chance that bootx64.efi and MolManager.efi were updated after the error was captured? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192388] Certain UI elements in some applications stop responding to clicks
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1192388 https://bugzilla.suse.com/show_bug.cgi?id=1192388#c14 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #14 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. Thanks. So let's close it as fixed. :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192388] Certain UI elements in some applications stop responding to clicks
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1192388 https://bugzilla.suse.com/show_bug.cgi?id=1192388#c13 Linus Kardell <linus.kardell(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(linus.kardell@gma | |il.com) | --- Comment #13 from Linus Kardell <linus.kardell(a)gmail.com> --- I didn't see this issue now when trying it with VSCode and Meld in IceWM -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209985] Secure boot violation
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209985 https://bugzilla.suse.com/show_bug.cgi?id=1209985#c18 --- Comment #18 from Tseng <dennis.tseng(a)suse.com> --- Would you please also check the .sbat section of grub.efi ? For example, in the following case, because grub.efi(grub,1) < vars(grub,3), it will be revoked finally. > cat /sys/firmware/efi/vars/SbatLevelRT-605dab50-e046-4300-abb6-3dd810dd8b23/data sbat,1,2022111500 shim,2 grub,3 /boot/efi/EFI/opensuse> objdump -j .sbat -s grub.efi|more .sbat section�� 127000 73626174 2c312c53 42415420 56657273 sbat,1,SBAT Vers 127010 696f6e2c 73626174 2c312c68 74747073 ion,sbat,1,https 127020 3a2f2f67 69746875 622e636f 6d2f7268 ://github.com/rh 127030 626f6f74 2f736869 6d2f626c 6f622f6d boot/shim/blob/m 127040 61696e2f 53424154 2e6d640a 67727562 ain/SBAT.md.grub 127050 2c312c46 72656520 536f6674 77617265 ,1,Free Software .......... finished verifying SBAT data: Security Policy Violation �� ERROR �� Verification failed: (0x1A) Security Violation �� -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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