August 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201995] Intel Tigerlake: Mostly black screen with X.Org without nomodeset
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201995 https://bugzilla.suse.com/show_bug.cgi?id=1201995#c29 --- Comment #29 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. The enable_psr=0 option seems to be a common workaround for this kind of oft-seen flickering problem. Ideally speaking, the driver should work as is, but Intel didn't catch up all things yet, unfortunately... I keep this bug opened to see what's the reaction of the upstream. Please give the URL of the upstream report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195030] /usr/lib/rpm/rpmdb_stat -CA: pmdb_stat: DB_ENV->open: No such file or directory
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1195030 https://bugzilla.suse.com/show_bug.cgi?id=1195030#c4 Michael Schr�der <mls(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Michael Schr�der <mls(a)suse.com> --- The environment options won't work as SUSE's rpm runs the databases in DB_PRIVATE mode, thus with no shared environment. This also means there can be no stale locks. Try something like: /usr/lib/rpm/rpmdb_stat -d Basenames -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202111] New: supportconfig: Allow limiting the timeframe of option "-l"
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202111 Bug ID: 1202111 Summary: supportconfig: Allow limiting the timeframe of option "-l" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: All OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a system with 2GB out of 4GB available in /var, a "supportconfig -l" caused "No space left on device" errors. As it seems the total amount of log files is simply too much. The sum of all compressed files is about 1GB (compression rate may be as high as 95%). The problem was that problem had been reported to support that happened in mid of last month, so older logs are desired. However just adding *all* logs is a poor idea. In contrast hb_report allows to set a start and an end point-in-time where logs are examined. Obviously such an option would be quite helpful for supportconfig, too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200747] New: permissions package contains invalid entries for bind
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1200747 Bug ID: 1200747 Summary: permissions package contains invalid entries for bind Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: lars.vogdt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I currently get the following error reported when running chkstat --system --set on a 15.4 system (upgraded from 15.3): > /var/lib/named/dev/null: on an insecure path - /var/lib/named has different non-root owner who could tamper with the file. > /var/lib/named/dev/random: on an insecure path - /var/lib/named has different non-root owner who could tamper with the file. The 'permissions' package has Version: 20201225 (Factory: 20220309). Both mentioned device nodes do not exist any longer, as bind in 15.4 is running non-chroot'ed (encapsulated via systemd instead see #1196990). The corresponding entry has been removed from the permissions package a few weeks prior in Oct 2020: https://github.com/openSUSE/permissions/commit/ece8520ae271152d88ad24968c38… Quoting the relevant parts of the above submission from file /etc/permissions (that part, that need to be removed in the current 15.4 RPM) below: -------------------------------[/etc/permissions] # named chroot (#438045) # # These currently conflict with a systemd-tmpfiles configuration file. # The entries in parallel serve the purpose of a whitelisting for # world-writable files, therefore they need to stay in place until we have a # better whitelisting concept. /var/lib/named/dev/null root:root 0666 /var/lib/named/dev/random root:root 0666 ------------------------------- I suggest to review the file for 15.4 completely, to avoid other incidents. But at least for my problem, removing the two lines from the file fixed it. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1178332] zypper: symbol lookup error: /usr/lib64/libzypp.so.1722: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarB5cxx11E
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1178332 https://bugzilla.suse.com/show_bug.cgi?id=1178332#c30 --- Comment #30 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2022:2640-1: An update that has four recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1160171,1178331,1178332,1200624 CVE References: JIRA References: Sources used: openSUSE Leap 15.4 (src): yaml-cpp-0.6.3-150400.4.3.1 SUSE Linux Enterprise Module for Desktop Applications 15-SP4 (src): yaml-cpp-0.6.3-150400.4.3.1 SUSE Linux Enterprise Module for Basesystem 15-SP4 (src): yaml-cpp-0.6.3-150400.4.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178331] M17N/yaml-cpp: Bug Wrong version of libyaml-cpp from M17N would crash libzypp and zypper
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1178331 https://bugzilla.suse.com/show_bug.cgi?id=1178331#c19 --- Comment #19 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2022:2640-1: An update that has four recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1160171,1178331,1178332,1200624 CVE References: JIRA References: Sources used: openSUSE Leap 15.4 (src): yaml-cpp-0.6.3-150400.4.3.1 SUSE Linux Enterprise Module for Desktop Applications 15-SP4 (src): yaml-cpp-0.6.3-150400.4.3.1 SUSE Linux Enterprise Module for Basesystem 15-SP4 (src): yaml-cpp-0.6.3-150400.4.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1160171] Failed to launch (symbol lookup error: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarB5cxx11E)
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1160171 https://bugzilla.suse.com/show_bug.cgi?id=1160171#c16 --- Comment #16 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2022:2640-1: An update that has four recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1160171,1178331,1178332,1200624 CVE References: JIRA References: Sources used: openSUSE Leap 15.4 (src): yaml-cpp-0.6.3-150400.4.3.1 SUSE Linux Enterprise Module for Desktop Applications 15-SP4 (src): yaml-cpp-0.6.3-150400.4.3.1 SUSE Linux Enterprise Module for Basesystem 15-SP4 (src): yaml-cpp-0.6.3-150400.4.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202066] New: Several instances of FileZilla were INVISIBLY run at startup after reboot
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202066 Bug ID: 1202066 Summary: Several instances of FileZilla were INVISIBLY run at startup after reboot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: php4fan(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- OpenSUSE has this "feature" that I absolutely hate that when you restart, it automatically starts whatever applications you had running when you restarted. I'm sure I can disable it somewhere but that's not the point: as long as this feature exists, it has to work decently. Actually, it has to work perfectly, but decently would be a start. So, here's what happened. I had one (ONE) instance of FileZilla open and I restarted the system. After restart, FileZilla didn't seem to be running. There was no FileZilla window anywhere, and is pinned icon in the task manager was not highlighted. This was not a problem, because as I said, I don't even like applications that I left open to be automatically started after reboot, so the less there are the better, and I didn't even notice. I didn't remember that I had left it open. SPOILER: in reality it _was_ running but as I said, I had no way of knowing. So, I rebooted several times because I was trying installing and uninstalling stuff repeatedly, so I rebooted half a dozen times. Never did I ever notice that filezilla was running. Now, it doesn't matter what made me think of it, but I ran this in a terminal: $ ps aux | grep filezilla and it turned out there were half a dozen processes of it running. One for every time that I had rebooted. So I hit Alt+Tab and found out that there were a bunch of FileZilla windows, but it was not the main window, but rather a popup with an error message that said that there were some issues with utf8 characters in filenames or whatnot. So there are several things that went wrong here: 1. The feature that, at startup, automatically launches the applications that were left open prior to reboot, is completely broken. Most of these applications have issues when run this way. FileZilla always shows this error related to utf-8 or unicode or whatever when launched automatically at startup (it does not show the error when launched manually normally). Thunderbird is forever unable to connect to the network when it is launched this way. While probably each of those applications have their own bugs, you are clearly launching them "too soon" or in some wrong way. So, this is one issue, leading to FileZilla showing (or wanting to show) that error popup 2. The popup with the error message didn't actually popup. It was somehow buried behind other windows, or completely invisible. Only when I used Alt+Tab was I ever able to discover its existence. That's wrong on its own 3. FileZilla's icon in the task manager should have been highlighted, so that I should have been able to see that there was, in fact, a filezilla window open (the error message popup), and I should have been able to access it by clicking on the task-manager icon (which instead would open a brand new FileZilla window). But no, the popup apparently doesn't count as window for the task manager. Only after I close the error popup, does the icon in the task manager become highlighted. 4. When I rebooted again, with the filezilla process running, with the invisible error-message popup waiting to be discovered and closed, after reboot, somehow TWO FileZilla processes were launched; and at the next reboot they were 3, and so on. Actually, I can't be sure of that. All I know for sure is that after like 6 or 7 reboots I had like 6 or 7 filezilla processes running, all of them with the error popup waiting to be closed (which I found and closed one by one with Alt+Tab). The whole thing is ridiculous. -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1202067] New: MicroOS Desktop: unacceptable TLS certificate
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202067 Bug ID: 1202067 Summary: MicroOS Desktop: unacceptable TLS certificate Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: axel.braun(a)gmx.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Installation of MOS on Raspi4 from openSUSE-MicroOS-DVD-aarch64-Snapshot20220729-Media.iso After first boot, adding flatpak repo fails with the above error message. As Raspi does not have a RTC, Date/time is wrong, as chronyd is installed, but not activated After manually installation, adding installing firefox from flathub still fails -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1202070] nautilus (gvfsd) fails to open admin:/// URL due to missing pkexec
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202070 https://bugzilla.suse.com/show_bug.cgi?id=1202070#c2 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Marcus Meissner <meissner(a)suse.com> --- and also split provides for pkexec package. -- You are receiving this mail because: You are on the CC list for the bug.

1 0