November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1204998] New: kde3-kommander and kde3-kommander-runtime not working
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204998 Bug ID: 1204998 Summary: kde3-kommander and kde3-kommander-runtime not working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: bugs(a)clearingstelle-eeg-kwkg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We have OpenSUSE Leap 15.4 x86_64 installed (inside a virtual machine). We added the KDE3-Repository (https://download.opensuse.org/repositories/KDE:/KDE3/15.4/) and installed kde3-kommander and kde3-kommander-runtime to run a KDE3-kmdr-file as a wrapper for a bash-script. Installed is kde3-kommander-3.5.10-lp154.105.1.x86_64. When starting only kmdr-editor or kmdr-executor, the KDE Plasma 5 Desktop freezes after seconds and only a reboot helps, killing processes not. The rare warnings when opening the programs in a console could help: konsole: kmdr-editor kbuildsycoca running reusing existing ksycoca libpng warning: iCCP: known incorrect sRGB profile -> KDE Plasma 5 Desktop freezes konsole: kmdr-executor ~/some_kmdr_file.kmdr DCOPClient::AttachInternal. Attach failed. Could not open network socket kbuildsycoca running -> Sometimes it even opens, but it freezes after a few seconds. We also tried to delete the users's cache (rm -rf ~/.cache), but this did not help. In Leap 15.4 in August 2022 kmdr-programs worked with the previous kde3-kommander rpm package. P.S.: In Leap 15.3 with kde3-kommander-3.5.10-lp153.105.1.x86_64 our KDE3-kmdr-file opens and works fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1203765] New: Unable to log into a gnome session because libcms2.so.2.0.13 crashes
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203765 Bug ID: 1203765 Summary: Unable to log into a gnome session because libcms2.so.2.0.13 crashes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 861749 --> http://bugzilla.opensuse.org/attachment.cgi?id=861749&action=edit dmesg - error This bug is also problematic for the openSUSE-Tumbleweed-DVD-x86_64-Snapshot20220921-Media image because you can install opensuse but you cannot login into the GUI because liblcms2 crashes. lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20220925 Codename: n/a zypper info liblcms2-2 Loading repository data... Reading installed packages... Information for package liblcms2-2: ----------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : liblcms2-2 Version : 2.13.1-1.4 Arch : x86_64 Vendor : openSUSE Installed Size : 389.0 KiB Installed : Yes (automatically) Status : up-to-date Source package : lcms2-2.13.1-1.4.src Upstream URL : https://www.littlecms.com/ Summary : Libraries for the Little CMS Engine Description : Little CMS Engine - A color managment library and tools. gnome-shell --version GNOME Shell 43.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1205151] New: Impossible take snapshots of home partition
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205151 Bug ID: 1205151 Summary: Impossible take snapshots of home partition Classification: openSUSE Product: openSUSE Leap Micro Version: 5.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: screening-team-bugs(a)suse.de Reporter: levi(a)levi-jacobs.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This problem happened to me in MicroOS, but will likely affect Leap Micro as well. If this bug is miscategorized, feel free to move it. Creating a new snapper config on MicroOS to gain automatic snapshots of the home partition works properly: ```bash snapper -c home create-config /home ``` But then snapper-timeline.service fails with following error: ``` systemd[1]: Started Timeline of Snapper Snapshots. systemd-helper[1765]: running timeline for 'home'. systemd-helper[1765]: IO Error (mktemp failed). systemd-helper[1765]: timeline for 'home' failed. systemd[1]: snapper-timeline.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: snapper-timeline.service: Failed with result 'exit-code'. ``` Same error appears when taking a snapshot manually. Snapshots of the root filesystem works as normal. Maybe it's a problem of SELinux? -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1205258] New: Multi-step transactions for transactional updates
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205258 Bug ID: 1205258 Summary: Multi-step transactions for transactional updates Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: All OS: openSUSE Leap 15.5 Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: contact(a)ericlevy.name QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Transactional updates, available as an installation option in Leap, ensures that each change to the system is captured and recorded within a transaction. However, the limitation, compared to normal systems, is that system changes cannot be tested for their practical effect until after a system reboot. Afterward, if any problems are found, the transaction must rolled back, and the change must be attempted again, after another reboot. Such a process is particularly cumbersome if the outcome of a change would not be determined until it would be tested in practice. Proposed is a mechanism for opening a transaction, which would remain open after the completion of the command opening it. Further commands would then allow entry into the open transaction, either in read-only or read-write mode, until the transaction is finally closed. For example, one might consider consider the following command sequence: 1. sudo transactional-update begin 2. sudo transcational-update enter -w a. sudo zypper ins somepackage b. exit 3. sudo transactional-update enter a. cd ~/project b. make c. exit 4. sudo transactional-update commit In the sequence, the user has requested that a new transaction be opened. It will remain open even after the command completes. The user has then entered the environment of the transaction, with the ability to modify the system. The tool creates a shell in the isolated environment, in which the user has selected a package for installation, and then has exited. The transaction remains open even after the shell closes. To test whether the system modifications carry the desired effect, the user has entered again into the transaction environment, but without the ability to modify the system. The user has then attempted a build process, in the modified system environment, to determine whether the system changes have had the desired effect. In this environment, the installed package is available, though not on main system. The user has finally exited the environment, and then committed the system changes. (Alternatively, the user may have destroyed the transaction, if needed.) After the transaction is committed, it represents the system state for the next boot session. In a normal system, a user may install packages or make other system changes, and test the effects immediately. The user may then make further changes, or reverse earlier ones, again, with immediate effect. The proposed enhancement allows the same capability in an isolated environment, which is optionally committed for the next boot cycle. It is possible to achieve a comparable effect by simply adding a read-only option to the tranactional-update command. This option could be combined with the continue switch. However, explicit semantics for the use case is likely to reduce the incidence of human error and ensure best practices. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204983] New: Unable to create distrobox with tumbleweed image
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204983 Bug ID: 1204983 Summary: Unable to create distrobox with tumbleweed image Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: logan.clarke(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862623 --> http://bugzilla.opensuse.org/attachment.cgi?id=862623&action=edit Output of "docker logs tumbleweed" Distrobox fails on the Installing basic packages... step when using the Tumbleweed image. Operating System: openSUSE Tumbleweed 20221030 Kernel Version: 6.0.5-1-default (64-bit) Graphics Platform: X11 Processors: 12 � AMD Ryzen 5 5600G with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: RENOIR Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B550M DS3H AC Distrobox version: 1.4.1 Docker version: 20.10.17-ce, build a89b84221c85 --- $ distrobox create -n tumbleweed Creating 'tumbleweed' using image registry.opensuse.org/opensuse/tumbleweed:latest [ OK ] Distrobox 'tumbleweed' successfully created. To enter, run: distrobox enter tumbleweed --- --- $ distrobox list ID | NAME | STATUS | IMAGE 907e89fe5168 | tumbleweed | exited | registry.opensuse.org/opensuse/tumbleweed:latest --- --- $ distrobox enter tumbleweed Container tumbleweed is not running. Starting container tumbleweed run this command to follow along: docker logs -f tumbleweed Starting container... [ OK ] Installing basic packages... Warning: program compiled against libxml 210 using older 209 Warning: program compiled against libxml 210 using older 209 Warning: program compiled against libxml 210 using older 209 Warning: program compiled against libxml 210 using older 209 Error: An error occurred --- Last entry in docker logs -f tumbleweed (full logs attached) --- + zypper install -y Mesa-dri libvulkan1 libvulkan_intel libvulkan_radeon zypper: symbol lookup error: /lib64/libcurl.so.4: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation + '[' 127 -ne 0 ']' + printf 'Error: An error occurred\n' Error: An error occurred --- -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1098360] New: aide --init gives the error DBG: md_enable: algorithm 7 not available
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1098360 Bug ID: 1098360 Summary: aide --init gives the error DBG: md_enable: algorithm 7 not available Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: chevy.stroker(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- virt:~ # aide --init DBG: md_enable: algorithm 7 not available gcry_md_enable 7 failedAIDE initialized database at /var/lib/aide/aide.db.new Number of entries: 218651virt:~ # -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1028824] New: aide looking for a removed algorithm
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1028824 Bug ID: 1028824 Summary: aide looking for a removed algorithm Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tschaefer(a)t-online.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After starting: aide -i comes the following notice: DBG: md_enable: algorithm 7 not available -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1139017] New: aide gcry_md_enable 7 failure
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1139017 Bug ID: 1139017 Summary: aide gcry_md_enable 7 failure Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP1 Hardware: x86-64 OS: SLES 15 Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: woe.2018(a)wizonet.ch QA Contact: packagehub-bugs(a)suse.com Found By: --- Blocker: --- This error occurs in openSuSE Leap 15 and openSuSE Leap 15.1 (which is not available ub in OS: and Version: selector above). The output of aide shows no longer the differ files - only the summary is available: aide_2019-06-23 gcry_md_enable 7 failedAIDE found differences between database and filesystem!! Summary: Total number of entries: 103548 Added entries: 18 Removed entries: 0 Changed entries: 17 Therefore it is no longer possible to identify the files that has changed. I think the error is based on this message: In output: gcry_md_enable 7 failed When started: DBG: md_enable: algorithm 7 not available -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1204604] New: [Build 20221022] wicked: openQA test fails in t08_setup_second_card
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204604 Bug ID: 1204604 Summary: [Build 20221022] wicked: openQA test fails in t08_setup_second_card Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2828836/modules/t08_ setup_second_card/steps/12 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation # Test died: Unexpected IP 10.0.2.15 on ens4 at opensuse/tests/wicked/basic/sut/t08_setup_second_card.pm line 39. openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-wicked_basic_sut@64bit fails in [t08_setup_second_card](https://openqa.opensuse.org/tests/2828836/modules/t0… ## Test suite description Include basic sanity checks of wicked network framework Maintainer: qa-c(a)suse.de ## Reproducible Fails since (at least) Build [20221022](https://openqa.opensuse.org/tests/2828571) ## Expected result Last good: [20221021](https://openqa.opensuse.org/tests/2826895) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1205243] New: VUL-0: CVE-2022-45059: varnish: HTTP request smuggling via hop-by-hop headers
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205243 Bug ID: 1205243 Summary: VUL-0: CVE-2022-45059: varnish: HTTP request smuggling via hop-by-hop headers Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/347488/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: jengelh(a)inai.de Reporter: carlos.lopez(a)suse.com QA Contact: security-team(a)suse.de CC: mrueckert(a)suse.com Found By: Security Response Team Blocker: --- CVE-2022-45059 An issue was discovered in Varnish Cache 7.x before 7.1.2 and 7.2.x before 7.2.1. A request smuggling attack can be performed on Varnish Cache servers by requesting that certain headers are made hop-by-hop, preventing the Varnish Cache servers from forwarding critical headers to the backend. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45059 https://www.cve.org/CVERecord?id=CVE-2022-45059 https://varnish-cache.org/security/VSV00010.html -- You are receiving this mail because: You are on the CC list for the bug.

1 1