January 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1234942] New: Maybe there are some incorrect configurations related to compiling Vim.
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234942 Bug ID: 1234942 Summary: Maybe there are some incorrect configurations related to compiling Vim. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: hxliang666(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 879361 --> https://bugzilla.suse.com/attachment.cgi?id=879361&action=edit Comparison of Results **My system information, wsl2:** NAME="openSUSE Tumbleweed" # VERSION="20241226" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20241226" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" # CPE 2.3 format, boo#1217921 CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20241226:*:*:*:*:*:*:*" #CPE 2.2 format #CPE_NAME="cpe:/o:opensuse:tumbleweed:20241226" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" **Problem description:** 1. After opening CPP files with gVim and exiting insert mode, the gVim cursor reacts with a delay when changing from the vertical bar to the block, even though I have removed many of my Vim configurations. 2. To address this, I manually compiled gVim and observed a different result: everything works correctly, and no delay occurs. **gVim provided by the system** VIM - Vi IMproved 9.1 (2024 Jan 02) Included patches: 1-908 Compiled by 'http://www.opensuse.org/' Huge version with GTK3 GUI. Features included (+) or not (-): +acl +file_in_path +mouse_urxvt -tag_any_white +arabic +find_in_path +mouse_xterm -tcl +autocmd +float +multi_byte +termguicolors +autochdir +folding +multi_lang +terminal -autoservername -footer -mzscheme +terminfo +balloon_eval +fork() +netbeans_intg +termresponse +balloon_eval_term +gettext +num64 +textobjects +browse -hangul_input +packages +textprop ++builtin_terms +iconv +path_extra +timers +byte_offset +insert_expand +perl +title +channel +ipv6 +persistent_undo +toolbar +cindent +job +popupwin +user_commands +clientserver +jumplist +postscript +vartabs +clipboard +keymap +printer +vertsplit +cmdline_compl +lambda +profile +vim9script +cmdline_hist +langmap -python +viminfo +cmdline_info +libcall +python3/dyn +virtualedit +comments +linebreak +quickfix +visual +conceal +lispindent +reltime +visualextra +cryptv +listcmds +rightleft +vreplace +cscope +localmap +ruby/dyn +wildignore +cursorbind +lua/dyn +scrollbind +wildmenu +cursorshape +menu +signs +windows +dialog_con_gui +mksession +smartindent +writebackup +diff +modify_fname -sodium +X11 +digraphs +mouse -sound +xattr +dnd +mouseshape +spell -xfontset -ebcdic +mouse_dec +startuptime +xim +emacs_tags +mouse_gpm +statusline -xpm +eval -mouse_jsbterm -sun_workshop +xsmp_interact +ex_extra +mouse_netterm +syntax +xterm_clipboard +extra_search +mouse_sgr +tag_binary -xterm_save -farsi -mouse_sysmouse -tag_old_static system vimrc file: "/etc/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" 3rd user vimrc file: "~/.config/vim/vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "/etc/gvimrc" user gvimrc file: "$HOME/.gvimrc" 2nd user gvimrc file: "~/.vim/gvimrc" 3rd user gvimrc file: "~/.config/vim/gvimrc" defaults file: "$VIMRUNTIME/defaults.vim" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/atk-1.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/libxkbcommon -I/usr/include/wayland -I/usr/include/fribidi -I/usr/include/libpng16 -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/gio-unix-2.0 -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -O2 -Wall -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -g -Wall -pipe -fno-strict-aliasing -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -flto=auto -L/usr/local/lib -Wl,--as-needed -o vim -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXt -lX11 -lSM -lICE -lm -lselinux -ltinfo -lrt -lacl -lgpm -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -L/usr/local/lib64 -fstack-protector-strong -L/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -lperl -lm -ldl -lcrypt -lpthread **gVim Compiled by me** VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Dec 31 2024 08:58:55) Included patches: 1-981 Compiled by banana@Banana Huge version with GTK3 GUI. Features included (+) or not (-): +acl +file_in_path +mouse_urxvt -tag_any_white +arabic +find_in_path +mouse_xterm -tcl +autocmd +float +multi_byte +termguicolors +autochdir +folding +multi_lang +terminal -autoservername -footer -mzscheme +terminfo +balloon_eval +fork() +netbeans_intg +termresponse +balloon_eval_term +gettext +num64 +textobjects +browse -hangul_input +packages +textprop ++builtin_terms +iconv +path_extra +timers +byte_offset +insert_expand +perl +title +channel +ipv6 +persistent_undo +toolbar +cindent +job +popupwin +user_commands +clientserver +jumplist +postscript +vartabs +clipboard +keymap +printer +vertsplit +cmdline_compl +lambda +profile +vim9script +cmdline_hist +langmap -python +viminfo +cmdline_info +libcall +python3 +virtualedit +comments +linebreak +quickfix +visual +conceal +lispindent +reltime +visualextra +cryptv +listcmds +rightleft +vreplace +cscope +localmap +ruby +wildignore +cursorbind +lua +scrollbind +wildmenu +cursorshape +menu +signs +windows +dialog_con_gui +mksession +smartindent +writebackup +diff +modify_fname -sodium +X11 +digraphs +mouse -sound +xattr +dnd +mouseshape +spell -xfontset -ebcdic +mouse_dec +startuptime +xim +emacs_tags -mouse_gpm +statusline -xpm +eval -mouse_jsbterm -sun_workshop -xsmp +ex_extra +mouse_netterm +syntax +xterm_clipboard +extra_search +mouse_sgr +tag_binary -xterm_save -farsi -mouse_sysmouse -tag_old_static system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" 3rd user vimrc file: "~/.config/vim/vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "$VIM/gvimrc" user gvimrc file: "$HOME/.gvimrc" 2nd user gvimrc file: "~/.vim/gvimrc" 3rd user gvimrc file: "~/.config/vim/gvimrc" defaults file: "$VIMRUNTIME/defaults.vim" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/usr/local/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/atk-1.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/libxkbcommon -I/usr/include/wayland -I/usr/include/fribidi -I/usr/include/libpng16 -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/gio-unix-2.0 -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DWITH_GZFILEOP -I/usr/include/libmount -I/usr/include/blkid -g -O2 -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -Wl,--as-needed -o vim -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lXt -lX11 -lSM -lICE -lm -ltinfo -lselinux -L/usr/lib -llua5.4 -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -L/usr/local/lib64 -fstack-protector-strong -L/usr/lib/perl5/5.40.0/x86_64-linux-thread-multi/CORE -lperl -lm -ldl -lcrypt -lpthread -L/usr/lib64/python3.11/config-3.11-x86_64-linux-gnu -lpython3.11 -ldl -lm -lruby3.3 -lm -lpthread -L/usr/lib64 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c24 --- Comment #24 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi (In reply to Jiri Slaby from comment #21) > (In reply to Michal Kubeček from comment #20) > > Are you really sure that this time it is for real and we are not going to > > repeat the same dance again? Couldn't we at least wait until after 6.13 > > final to have a bit more time for testing before it hits Tumbleweed and > > its users? > > And perhaps ask users to test TW with Kernel:HEAD once it contains this > change. I can do that, but I feel like it wouldn't make much of a difference. As this change has been discussed on factory; only those participants would likely test anyway. > > Note I won't take this config change with the big master->stable merge. The > merge usually has enough its own bugs to solve. That's OK. I can prepare a separate change for stable. > > So either I take this into stable either before 5.13 merge (i.e. cherry-pick > it) or after (a revert during the big merge and > cherry-pick/revert-the-revert later) ;). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c23 Thomas Zimmermann <tzimmermann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tzimmermann@suse. | |com) | --- Comment #23 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi (In reply to Michal Kubeček from comment #20) > This has been going on for months and it is getting more and more > ridiculous. Please keep it professional. > The option has been disabled multiple times, each time with the > same reasoning ("nobody needs this any more") and each time with the same > result: getting reenabled within a week or two because it turns out it does > actually break something. What are you talking about? This kernel option has been disabled exactly once, which resulted in bsc#1232727. We reverted the kernel change to get the fix done. But bsc#1232727 has been trivial to resolve. The whole fallout that happened afterwards entirely goes back to the dire state that our Plymouth package is in. It is unrelated to the kernel's fbdev interface. > > Are you really sure that this time it is for real and we are not going to > repeat the same dance again? Couldn't we at least wait until after 6.13 > final to have a bit more time for testing before it hits Tumbleweed and > its users? I sent out a message to the factory list to collect possible use cases in Oct 2023. And then again a reminder in Oct 2024. [1] The two actionable use cases I heard about were fbiterm and the links web browser in 'graphics mode' (mentioned by a single person). We've removed the fbiterm in boo#1224053 in May 2024. The maintainer of links has been working on converting the program to DRM interface AFAIK. Meanwhile links continues to work in pure text mode. [1] https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223838] Nonfunctional brightness keys on Apple Macbook 5.1 (mcp79,nouveau)
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1223838 https://bugzilla.suse.com/show_bug.cgi?id=1223838#c64 --- Comment #64 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Jiri Slaby from comment #63) > (In reply to Takashi Iwai from comment #19) > > The upstream submission: > > https://lore.kernel.org/all/20240517110853.8481-1-tiwai@suse.de/ > > It somehow fell through the cracks. Care to ping them/resend? Done: https://lore.kernel.org/all/20250102114944.11499-1-tiwai@suse.de/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234871] systemdboot_widgets shows undefined method >= for nil
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234871 https://bugzilla.suse.com/show_bug.cgi?id=1234871#c2 --- Comment #2 from Stefan Schubert <schubi(a)suse.com> --- >When converting my system from Legacy to sdboot /boot/efi is empty Hm, empty efi directory is strange. Have have you converted your system ? Is it an EFI system ? >I installed yast2-bootloader as https://microos.opensuse.org/blog/2023-12-20-sdboot-fde/ says yast2 has sdboot support It says: "Soon after the announcement, yast-bootloader gained support for it for new installations." So, the important word is "new installation" and not "migration" :-) Anyway, currently I cannot reproduce the error but perhaps we find a solution for it ..... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c22 --- Comment #22 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #21) > (In reply to Michal Kubeček from comment #20) > > Are you really sure that this time it is for real and we are not going to > > repeat the same dance again? Couldn't we at least wait until after 6.13 > > final to have a bit more time for testing before it hits Tumbleweed and > > its users? > > And perhaps ask users to test TW with Kernel:HEAD once it contains this > change. Or even build Kernel:stable + config.addon in your home and let users test that at first (I would once you post a link to the factory list). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234692] Moval of dbus-launch to dbus-daemon prevents start of Dolphin super user mode
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234692 https://bugzilla.suse.com/show_bug.cgi?id=1234692#c6 --- Comment #6 from Christophe Marin <christophe(a)krop.fr> --- (In reply to John Smith from comment #4) > The below update broke Dolphin's right click context menu functionality. > > https://build.opensuse.org/request/show/1231914 > > Right click> Open Folder With> File Manager - Super User Mode. > Fixed with https://build.opensuse.org/request/show/1233825 it just needs a new snapshot to be released. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c21 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #21 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Michal Kubeček from comment #20) > Are you really sure that this time it is for real and we are not going to > repeat the same dance again? Couldn't we at least wait until after 6.13 > final to have a bit more time for testing before it hits Tumbleweed and > its users? And perhaps ask users to test TW with Kernel:HEAD once it contains this change. Note I won't take this config change with the big master->stable merge. The merge usually has enough its own bugs to solve. So either I take this into stable either before 5.13 merge (i.e. cherry-pick it) or after (a revert during the big merge and cherry-pick/revert-the-revert later) ;). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222902] Monitor detection fails after hard reset
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222902 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mrmazda(a)earthlink.net | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234500] New: VUL-0: : singularity-ce: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234500 Bug ID: 1234500 Summary: VUL-0: : singularity-ce: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/432234/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: eich(a)suse.com Reporter: gianluca.gabrielli(a)suse.com QA Contact: security-team(a)suse.de Blocks: 1234482 Target Milestone: --- Found By: --- Blocker: --- Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/cry...@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 https://github.com/golang/crypto/commit/b4f1988a35dee11ec3e05d6bf3e90b695fb… https://go.dev/cl/635315 https://go.dev/issue/70779 https://groups.google.com/g/golang-announce/c/-nPEi39gI4Q/m/cGVPJCqdAQAJ https://pkg.go.dev/vuln/GO-2024-3321 http://www.openwall.com/lists/oss-security/2024/12/11/2 https://bugzilla.redhat.com/show_bug.cgi?id=2331720 https://github.com/CVEProject/cvelistV5/blob/main//cves/2024/45xxx/CVE-2024… -- You are receiving this mail because: You are on the CC list for the bug.

1 4