November 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1216517] Plymouth bootsplash after 20231012 upgrade was lost then appears intermittently or displays three blocks
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216517 https://bugzilla.suse.com/show_bug.cgi?id=1216517#c2 --- Comment #2 from epp(a)mcom.com --- The only Plymouth bootsplash theme that works reliably, is Tribar. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211331] security/nitrokey-app: Feature: Provide nitrokey-app2
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1211331 https://bugzilla.suse.com/show_bug.cgi?id=1211331#c7 Stakanov Schufter <stakanov(a)disroot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jornfranke.dev@po | |steo.eu) CC| |jornfranke.dev(a)posteo.eu --- Comment #7 from Stakanov Schufter <stakanov(a)disroot.org> --- (In reply to Jörn Franke from comment #6) And you are able to start it? I am currently neither finding the app, nor do I see an icon. Is it only CLI? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216778] Unable to read the text of emails in Evolution
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216778 https://bugzilla.suse.com/show_bug.cgi?id=1216778#c5 --- Comment #5 from Michael Gorse <mgorse(a)suse.com> --- I have a test package with the Debian patch applied in home:mgorse:branches:GNOME:STABLE:41. Ie, zypper ar http://download.opensuse.org/repositories/home:/mgorse:/branches:/GNOME:/ST… (I know that it's built against 15.4, but it should also run on 15.5) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216718] New: FreeBSD guest does not shutdown completely
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216718 Bug ID: 1216718 Summary: FreeBSD guest does not shutdown completely Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: David.Boyd49(a)twc.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since Oracle VirtualBox 7.0.2 (7.0.0 was never loaded) on the Tumbleweed server, FreeBSD 13.2-RELEASE does not shutdown completely. FreeBSD doesn't yet have a 7.0.x version of Guest Additions and is "stuck" on 6.1.48 for now. The problem is also observed on the upcoming FreeBSD 14.0-RELEASE. The problem is also observed when the server is running Leap 15.5. The problem is also observed when the server is running Fedora 38. This problem was not observed with version 6.1.x on the Tumbleweed server. The guest shutdown, whether "ACPI Shutdown" (from the Machine drop down menu), "shutdown -p now" (from the guest console) or "poweroff" (from the guest console), proceeds normally until the guest console displays "uhid0: detached" followed by "uhub0: detached" and then just sits (forever). You can use "Power Off" (from the Machine drop down menu) and restart the VM with everything behaving normally. You can use "Reset" (from the Machine drop down menu) and everything also behaves normally. The Guest VM doesn't appear to know anything about the hang. All filesystems have been flushed and unmounted properly. Subsequent boots of the system are clean. Nothing unusual is present in the system logs. The VirtualBox logs do not have anything interesting in them (as far as I can tell). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1211331] security/nitrokey-app: Feature: Provide nitrokey-app2
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1211331 https://bugzilla.suse.com/show_bug.cgi?id=1211331#c6 --- Comment #6 from Jörn Franke <jornfranke.dev(a)posteo.eu> --- 1(In reply to Stakanov Schufter from comment #5) > O.K. it installs right now, but I do not understand if: > a) nitrokey 1 app has to be installed mandatory in order to have nitrokey2 > app working? > No, you do not need to have it installed. The Nitrokey app 1 is for older hardware of Nitrokey, which is still sold. You can install the both in parallel. > b) if not a) there might be a dependency problem because the app1 and app2 > can be installed contemporarily (as this control hardware that should not be > the case, because in my understanding either one OR the other should be > installed). It is fine if they can be installed in parallel - there is no dependency problem. > > c) when trying to search for nitrokey in the index of programs, not icon is > found if the first version is uninstalled. Nothing but the first app (1.4.2) > does open when starting nitrokey app and both are installed. nitrokey-app2 is not a successor of nitrokey-app 1.4.2. It is in essence a different app. I propose to treat them as nitrokey-app and nitrokey-app2. > > With other words, installs, no complains but apparently no icon and no > functionality. When the first version of the app is uninstalled, the voice > "get nitrokey app" when trying to search the index of programs. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1108673] VUL-1: CVE-2018-17076: gpp: segmentation fault via a crafted file
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1108673 https://bugzilla.suse.com/show_bug.cgi?id=1108673#c8 Tristan Miller <psychonaut(a)nothingisreal.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REOPENED |RESOLVED --- Comment #8 from Tristan Miller <psychonaut(a)nothingisreal.com> --- Packages for GPP 2.28 now appear in http://download.opensuse.org/update/leap/15.5/backports/ and http://download.opensuse.org/update/leap/15.4/backports/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216463] Default UEFI firmware choice set up by gnome-boxes Windows 10/11 assistant can't boot into Windows 10 install disk
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216463 https://bugzilla.suse.com/show_bug.cgi?id=1216463#c5 --- Comment #5 from James Fehlig <jfehlig(a)suse.com> --- Are you connected to the system or session libvirtd [1]? Likely the system one if using virt-manager as root. If running virt-manager as root, please attach /root/.cache/virt-manager/*.log and /var/log/libvirt/qemu/<vm-name>.log. [1] https://libvirt.org/daemons.html#operating-modes https://wiki.libvirt.org/FAQ.html#what-is-the-difference-between-qemu-syste… https://blog.wikichoon.com/2016/01/qemusystem-vs-qemusession.html -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216794] New: Delay when switching to normal mode due to suse.vimrc mapping the escape key
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216794 Bug ID: 1216794 Summary: Delay when switching to normal mode due to suse.vimrc mapping the escape key Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: eecdc3.opensuse(a)coders-haven.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- As the title says $VIMRUNTIME/suse.vimrc adds mappings involving the escape key. This causes a delay of 'timeoutlen' when pressing the escape key to return to normal mode, which defaults to one second and makes using vim on openSUSE feel very sluggish. It seems that these mappings were introduced to make vim properly react on escape codes sent by various terminals such as screen and xterm when pressing modifier keys. I am not getting any issues with xterm when removing those mappings manually, so I was wondering if they really are still needed? Removing them manually is not a viable solution since suse.vimrc gets restored whenever I update the package, which I am current obtaining from the editors repository. I find this really weird by the way as I would expected have the rpmconfigcheck mechanism to prevent this. (If there is a way to prevent package updates from reverting my changes to suse.vimrc please let me know so that I at least have a local workaround for the time being.) I am not familiar with the implementation details of *nix terminals but `:help modifyOtherKeys` mentions an improvement available in xterm 377 and later. Maybe that information is of help? (X11:terminals providers xterm 387 so such a dependency can be fulfilled.) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215944] New: SeaMonkey fails to build with binutils >= 2.41
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215944 Bug ID: 1215944 Summary: SeaMonkey fails to build with binutils >= 2.41 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- SeaMonkey was failing to build with binutils >= 2.41 due to upstream bug <https://bugzilla.mozilla.org/show_bug.cgi?id=1856238>. To fix this issue, I have added a patch to the SeaMonkey 2.53.17.1 packages provided by the mozilla/seamonkey package on OBS: <https://build.opensuse.org/package/show/mozilla/seamonkey>. I am requesting that these changes be included in Leap 15.4 and 15.5. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215178] New: qt6-base-6.4.2-150500.3+ leads to qt6-creator hang
by bugzilla_noreply＠suse.com 01 Nov '23

01 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1215178 Bug ID: 1215178 Summary: qt6-base-6.4.2-150500.3+ leads to qt6-creator hang Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: andrey.v.novikoff(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With the current revision of libQt6Gui6-6.4.2-150500.3.7.4 from the official openSUSE repos, the qt6-creator-9.0.2 hangs when showing the Issues pane and consumes all memory in an infinite loop. The bug is the same as described on https://bugreports.qt.io/browse/QTCREATORBUG-28593 and connected with https://bugreports.qt.io/browse/QTBUG-109474 This is a regression in Qt6Gui cased by patch https://codereview.qt-project.org/c/qt/qtbase/+/435080 for Qt-6.5 branch. As per changelog, this patch was also applied to the qt6-base-6.4.2 from the "Updates from SUSE Linux Enterprise 15" repository (source file `0002-QTextLayout-fix-maximumWidth-for-a-text-containing-line.patch`). Thus, the problem appears now in Qt-6.4 branch including qt6-creator hang. Downgrading libQt6Gui6-6.4.2 to the original revision of libQt6Gui6-6.4.2-150500.1.14 from the Main OpenSUSE repository do resolves the issue with Qt6-creator. The problematic qt6base patch 435080 was superseded in the upstream via https://codereview.qt-project.org/c/qt/qtbase/+/453906 . Hope, this can be backported to the 6.4.2 as well. Or, the bad 435080 patch can be just removed altogether. -- You are receiving this mail because: You are on the CC list for the bug.

1 3