March 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1209656] New: gthumb displays thumbnails only on first 50 images
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209656 Bug ID: 1209656 Summary: gthumb displays thumbnails only on first 50 images Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: heiko.rommel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865774 --> https://bugzilla.suse.com/attachment.cgi?id=865774&action=edit screenshot of gthumb not rendering all thumbnails I am using gthumb-3.12.0-bp154.1.118 from Main Repository. When using gthumb on large folders, only the first 50 images are rendered. See attached screenshot. How to reproduce: gthumb /usr/share/icons/gnome/32x32/apps/ -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1209655] New: gthumb crashes when accessing sub folders
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209655 Bug ID: 1209655 Summary: gthumb crashes when accessing sub folders Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: heiko.rommel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865772 --> https://bugzilla.suse.com/attachment.cgi?id=865772&action=edit backtrace with all debuginfos installed I tried to paste selected images into a sub folder I had previously created with gthumb. As soon as I select that folder, gthumb crashes with SIGSEGV in function _gth_file_list_thumbnailer_iterate. version is gthumb-3.12.0-bp154.1.118.x86_64 from Main Repository backtrace when run from gdb is attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1209895] New: Several patterns cannot be installed on microos - nothing provides 'libmutter-11.so.0
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209895 Bug ID: 1209895 Summary: Several patterns cannot be installed on microos - nothing provides 'libmutter-11.so.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3197822/modules/patt erns/steps/28 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: mloviska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-ContainerHost-x86_64-container-host@mloviska/os-autoinst-distri-opensuse#slem_install_all_patterns@64bit fails in [patterns](https://openqa.opensuse.org/tests/3197822/modules/patterns/steps/… ## Test suite description New test case tries to install all available patterns for Microos. Tested image: openSUSE-MicroOS.x86_64-16.0.0-ContainerHost-kvm-and-xen-Snapshot20230327.qcow2 Problem: nothing provides 'libmutter-11.so.0()(64bit)' needed by the to be installed budgie-desktop-10.7+0-1.2.x86_64 Problem: nothing provides 'libmutter-11.so.0()(64bit)' needed by the to be installed budgie-desktop-10.7+0-1.2.x86_64 Problem: the to be installed pattern:microos_kde_desktop-5.0-64.1.x86_64 requires 'patterns-microos-desktop-kde', but this requirement cannot be provided Problem: the to be installed pattern:microos_ra_verifier-5.0-64.1.x86_64 requires 'patterns-microos-ra_verifier', but this requirement cannot be provided Problem: the to be installed pattern:xen_server-20210330-4.1.x86_64 requires 'patterns-server-xen_server', but this requirement cannot be provided Problem: the to be installed pattern:devel_rpm_build-20170319-11.2.x86_64 requires 'patterns-devel-base-devel_rpm_build', but this requirement cannot be provided Problem: nothing provides 'libmutter-11.so.0()(64bit)' needed by the to be installed budgie-desktop-10.7+0-1.2.x86_64 Solution 1: do not install pattern:budgie-20220527-2.2.x86_64 Solution 2: break budgie-desktop-10.7+0-1.2.x86_64 by ignoring some of its dependencies ## Reproducible Fails since (at least) Build [mloviska/os-autoinst-distri-opensuse#16735](https://openqa.opensuse.org/tes… ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1209923] New: YaST Partitioner produces invalid GPT (on USB drive) after removing two partitions
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209923 Bug ID: 1209923 Summary: YaST Partitioner produces invalid GPT (on USB drive) after removing two partitions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: opensuse.k1akb(a)slmail.me QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I started up YaST2 Partitioner. I insert a USB drive (that contained the OpenSUSE Tumbleweed installation image, but probably irrelevant) and use the partitioner to remove the 2 existing partitions. I let the partitioner apply the modifications and close it. What happens: - in KDE, the storage/removable device mount notifications show the medium is refreshed/reloaded and shows as if the partitions still exist. (Reports on OpenSUSE Tumbleweed partition) - `sudo gdisk -l /dev/sda` reports a corrupt GPT partition. What I expected: - KDE to detect a drive without partitions, therefore nothing to mount. - YaST2 Partitioner to make the modifications such that there are no corruptions, i.e. `gdisk` reports no errors and changes are applied without surprises :-) NOTE: (obviously) I lost no valuable data (except for the OpenSUSE Tumbleweed image, of course), but I would think twice to trust YaST2 for making changes to drivers purposed for backup/long-term storage. ``` user@host ~> sudo gdisk -l /dev/sda [sudo] password for user: GPT fdisk (gdisk) version 1.0.9.1 Caution: invalid main GPT header, but valid backup; regenerating main header from backup! Warning: Invalid CRC on main header data; loaded backup partition table. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table! Warning! One or more CRCs don't match. You should repair the disk! Main header: ERROR Backup header: OK Main partition table: ERROR Backup partition table: OK Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: damaged Found valid MBR and corrupt GPT. Which do you want to use? (Using the GPT MAY permit recovery of GPT data.) 1 - MBR 2 - GPT 3 - Create blank GPT Your answer: ^C�� user@host ~ [SIGINT]> ``` Not sure which packages belong to YaST2 Partitioner: rpm -qa | grep yast2 ``` yast2-bootloader-4.6.0-1.1.x86_64 yast2-metapackage-handler-4.6.0-1.1.noarch yast2-online-update-frontend-4.6.1-1.1.noarch yast2-packager-4.6.0-1.1.x86_64 patterns-yast-yast2_basis-20220411-1.4.x86_64 yast2-journal-4.6.0-1.1.noarch yast2-python3-bindings-4.6.0-1.2.x86_64 yast2-sysconfig-4.6.0-1.1.noarch yast2-alternatives-4.6.0-1.1.x86_64 patterns-yast-yast2_desktop-20220411-1.4.x86_64 yast2-country-data-4.6.0-1.1.x86_64 yast2-security-4.6.0-1.1.noarch yast2-xml-4.6.0-1.2.x86_64 yast2-core-4.6.0-1.2.x86_64 yast2-printer-4.6.0-1.1.x86_64 yast2-perl-bindings-4.6.0-1.2.x86_64 yast2-users-4.6.0-1.2.x86_64 yast2-network-4.6.0-1.1.noarch yast2-update-4.6.0-1.1.x86_64 yast2-qt-branding-openSUSE-84.87.20230227-1.1.noarch yast2-apparmor-4.6.0-1.1.noarch patterns-yast-x11_yast-20220411-1.4.x86_64 yast2-ruby-bindings-4.6.1-1.2.x86_64 yast2-pkg-bindings-4.6.0-1.2.x86_64 yast2-x11-4.6.0-1.1.x86_64 yast2-theme-4.6.0-1.1.noarch yast2-control-center-qt-4.6.0-1.2.x86_64 yast2-storage-ng-4.6.2-1.1.x86_64 patterns-kde-kde_yast-20221001-2.1.noarch yast2-ycp-ui-bindings-4.6.0-1.2.x86_64 yast2-online-update-4.6.1-1.1.noarch yast2-ntp-client-4.6.0-1.1.noarch yast2-theme-breeze-4.6.0-1.1.noarch yast2-logs-4.6.1-1.1.x86_64 yast2-pam-4.6.0-1.1.noarch yast2-services-manager-4.6.0-1.1.noarch yast2-proxy-4.6.0-1.1.noarch yast2-country-4.6.0-1.1.x86_64 yast2-firewall-4.6.0-1.1.noarch yast2-trans-stats-2.19.0-17.26.noarch yast2-hardware-detection-4.6.0-1.2.x86_64 yast2-control-center-4.6.0-1.2.x86_64 yast2-vm-4.6.0-1.1.x86_64 yast2-installation-4.6.1-1.1.noarch yast2-ldap-4.6.0-1.2.x86_64 yast2-4.6.1-1.1.x86_64 yast2-snapper-4.6.0-1.1.x86_64 yast2-transfer-4.6.0-1.2.x86_64 ``` rpm -qa | grep openSUSE-release ``` openSUSE-release-appliance-custom-20230326-2183.1.x86_64 openSUSE-release-20230326-2183.1.x86_64 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1210023] New: windows:mingw:win{32|64}/mingw{32|64}-kde4-filesystem: broken support for -d option in %_mingwxx_cmake_kde4
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210023 Bug ID: 1210023 Summary: windows:mingw:win{32|64}/mingw{32|64}-kde4-filesystem: broken support for -d option in %_mingwxx_cmake_kde4 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Found By: --- Blocker: --- The %_mingwxx_cmake_kde4 macro provides a -d option to specify a custom build directory, which currently does not work. The aforementioned macro uses %_mingwxx_cmake_qt4, which in turn uses %_mingwxx_cmake. In the former and latter macros, a change to the build directory occurs, which leads to the current build problems with KDE4 packages on mingw32, and can be fixed by making adjustments in both macros. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1209611] New: windows:mingw:win{32|64}/mingw{32|64}-filesystem: Move out cmake related support to mingw{32|64}-cross-cmake
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209611 Bug ID: 1209611 Summary: windows:mingw:win{32|64}/mingw{32|64}-filesystem: Move out cmake related support to mingw{32|64}-cross-cmake Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Found By: --- Blocker: --- CMake support files and macros for native packages are provided by the cmake package and not by the basic filesystem. To have a better separation and less updates of the mingw{32|64}-filesystem package when improving cmake support, it would be helpful to have a separate mingw32-cross-cmake package that provides the relevant rpm macros. The condition for this is that packages that use cmake use mingw32-cross-cmake as a build dependency. This could also be set centrally via the project configuration. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[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 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 1208943] New: intel compute driver aka intel-opencl
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208943 Bug ID: 1208943 Summary: intel compute driver aka intel-opencl Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: dani.mackiol(a)web.de QA Contact: sndirsch(a)suse.com Found By: --- Blocker: --- Hallo, is it possible to update the intel driver to the latest version? So that the new Intel Arc cards are supported with kernel 6.2. igc ( intel-graphic-compiler) is necessary. I try to compile it myself in OBS, but fail with error messages. Even Blender refuses to work with reference to the old module: linux driver version xx.xx.23904 or newer. currently is version 23.05.25593. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 19