May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1224404] New: Missing framebuffer during boot on aarch64
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224404 Bug ID: 1224404 Summary: Missing framebuffer during boot on aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3891664/modules/ansi ble/steps/31 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: dracut-maintainers(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Depends on: 1219180 Target Milestone: --- Found By: openQA Blocker: --- +++ This bug was initially created as a clone of Bug #1219180 +++ Unless the initrd is built with the platform native DRM driver (e.g. virtio_gpu), there is no graphical output during boot. This also means that entering a passphrase for unlocking the root fs is not possible. On x86 it uses the EFI framebuffer successfully, but on aarch64 dmesg has no trace of efifb/simplefb/simpledrm. The original bug report has some more details, but the summary is that efifb or other builtin drivers don't work with virtio-gpu-pci. To get any display output at all, the virtio-gpu module is needed. From a dracut PoV, the crypt module should probably pull in drm if virtio-gpu is detected? ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-sdboot-aarch64-microos-wizard@aarch64 fails in [ansible](https://openqa.opensuse.org/tests/3891664/modules/ansible/steps/31) ## Test suite description Like MicroOS, but use neither combustion nor ignition for the intial configuration, so jeos-firstboot runs. ## Reproducible Fails since (at least) Build [20231129](https://openqa.opensuse.org/tests/3771195) ## Expected result Last good: [20231127](https://openqa.opensuse.org/tests/3763820) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=microo… -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1223587] New: windows:mingw:win{32|64}: not present email address hib@hiberis.nl in bug tracker
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223587 Bug ID: 1223587 Summary: windows:mingw:win{32|64}: not present email address hib(a)hiberis.nl in bug tracker 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, mkbosmans(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- When opening new bugs for the mingw32|64 project, the mentioned email address is entered in the CC field. Submitting the bug then fails with the error message that this email address does not exist. This email address should be removed from the ticket system. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1223405] New: Bluetooth disabled at each login since upgrade to Plasma 6
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223405 Bug ID: 1223405 Summary: Bluetooth disabled at each login since upgrade to Plasma 6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: epp(a)mcom.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since the upgrade to Plasma 6, Bluetooth becomes disabled at each login. Must manually re-enable it each time. Once enabled, it should remain enabled between sessions. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1224215] New: Krunner randomly forces you to backspace-remove text to clear out text
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224215 Bug ID: 1224215 Summary: Krunner randomly forces you to backspace-remove text to clear out text Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: jlopez777+opensuse(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Krunner randomly forces you to backspace-remove text to clear out text Submitted here too: https://bugs.kde.org/show_bug.cgi?id=485375 SUMMARY I have to manually hit backspace to remove text from krunner. expected behavior: it should just clear out text or have it highlighted to allow for "write over" so that the new text I enter wipes out old text. Hard to reproduce, not sure what triggers it because it doesn't happen all the time...but I think its when I highlight text. 1. Highlight some random text from web browser 2. Call krunner 3. Observe behavior 4. esc and call krunner again, and NOW it highlights all the text for overwrite....which should be intended behavior initially. DEMO of the problem: Hard to explain, so here is a vid: https://youtu.be/0WtkuhZGlEs -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1220476] New: GCC 14: freeipmi package fails
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1220476 Bug ID: 1220476 Summary: GCC 14: freeipmi package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kkaempf(a)suse.com, mjambor(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Building freeipmi with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: sel/ipmi-sel-string-supermicro-x10dimm-common.c: In function ‘sel_string_output_supermicro_x10dimm_event_data2_event_data3’: sel/ipmi-sel-string-supermicro-x10dimm-common.c:87:14: error: implicit declaration of function ‘sel_string_output_supermicro_dimm_event_data2_event_data3’; did you mean ‘sel_string_output_supermicro_x10dimm_event_data2_event_data3’? [-Wimplicit-function-declaration] 87 | if ((ret = sel_string_output_supermicro_dimm_event_data2_event_data3 (ctx, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | sel_string_output_supermicro_x10dimm_event_data2_event_data3 ipmi-sensors-oem-intel.c: In function ‘ipmi_sensors_oem_intel_output_oem_record’: ipmi-sensors-oem-intel.c:98:18: error: implicit declaration of function ‘ipmi_sensors_oem_intel_s2600wp_output_oem_record’; did you mean ‘ipmi_sensors_oem_intel_s2600jf_output_oem_record’? [-Wimplicit-function-declaration] 98 | if ((ret = ipmi_sensors_oem_intel_s2600wp_output_oem_record (state_data, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ipmi_sensors_oem_intel_s2600jf_output_oem_record Builds with: Index: freeipmi.spec_dir/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h =================================================================== --- freeipmi.spec_dir.orig/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h +++ freeipmi.spec_dir/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h @@ -38,5 +38,14 @@ int sel_string_output_supermicro_overhea unsigned int flags, unsigned int *wlen, struct ipmi_sel_system_event_record_data *system_event_record_data); +int sel_string_output_supermicro_dimm_event_data2_event_data3 (ipmi_sel_ctx_t ctx, + struct ipmi_sel_entry *sel_entry, + uint8_t sel_record_type, + char *buf, + unsigned int buflen, + unsigned int flags, + unsigned int *wlen, + struct ipmi_sel_system_event_record_data *system_event_record_data, + int *oem_rv); #endif /* IPMI_SEL_STRING_SUPERMICRO_COMMON_H */ Index: freeipmi.spec_dir/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c =================================================================== --- freeipmi.spec_dir.orig/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c +++ freeipmi.spec_dir/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c @@ -34,6 +34,7 @@ #include "ipmi-sensors-oem-intel.h" #include "ipmi-sensors-oem-intel-s5500wb.h" #include "ipmi-sensors-oem-intel-s2600jf.h" +#include "ipmi-sensors-oem-intel-s2600wp.h" #include "ipmi-sensors-oem-intel-quanta-qssc-s4r.h" #include "ipmi-sensors-oem-intel-node-manager.h" -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1221340] New: qemu: fails to build with osc
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221340 Bug ID: 1221340 Summary: qemu: fails to build with osc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: adrian.schroeter(a)suse.com, dfaggioli(a)suse.com Target Milestone: --- Found By: Development Blocker: --- Steps to reproduce: osc co openSUSE:Factory/qemu && cd $_ osc build --noservice --clean standard Actual results: using SOURCE_DATE_EPOCH with value 1709510400 as build time error: Failed build dependencies: canokey-qemu-devel is needed by qemu-8.2.1-0.x86_64 libxdp-devel is needed by qemu-8.2.1-0.x86_64 pkgconfig(spice-protocol) >= 0.12.3 is needed by qemu-8.2.1-0.x86_64 pkgconfig(spice-server) >= 0.12.5 is needed by qemu-8.2.1-0.x86_64 xen-devel >= 4.2 is needed by qemu-8.2.1-0.x86_64 Powering off. [ 94.494179][ T3445] reboot: Power down This likely has to do with these macros %if 0%{with canokey} BuildRequires: canokey-qemu-devel %endif that are not properly parsed to provide the BuildRequires # rpm -q osc build osc-1.6.1-150500.403.1.noarch build-20240221-150500.444.1.noarch (both from openSUSE:Tools / 15.5) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1218513] New: wayland, scale settings not recorded
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1218513 Bug ID: 1218513 Summary: wayland, scale settings not recorded Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- If I set the scale to 105 % then it works well. When I log out then log in, the scale is at 100 %. The scale is not recorded. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221682] New: GCC 14: autofs package fails
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221682 Bug ID: 1221682 Summary: GCC 14: autofs package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Filesystems Assignee: kernel-fs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ddiss(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building autofs with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to (exhaustive list of errors): cyrus-sasl.c:112:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 112 | { SASL_CB_USER, &getuser_func, NULL }, | ^ cyrus-sasl.c:112:25: note: (near initialization for ‘callbacks[0].proc’) cyrus-sasl.c:113:29: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 113 | { SASL_CB_AUTHNAME, &getuser_func, NULL }, | ^ cyrus-sasl.c:113:29: note: (near initialization for ‘callbacks[1].proc’) cyrus-sasl.c:114:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(sasl_conn_t *, void *, int, sasl_secret_t **)’ {aka ‘int (*)(struct sasl_conn *, void *, int, struct sasl_secret **)’} [-Wincompatible-pointer-types] 114 | { SASL_CB_PASS, &getpass_func, NULL }, | ^ cyrus-sasl.c:114:25: note: (near initialization for ‘callbacks[2].proc’) cyrus-sasl.c:119:24: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char *)’ [-Wincompatible-pointer-types] 119 | { SASL_CB_LOG, &sasl_log_func, NULL }, | ^ cyrus-sasl.c:119:24: note: (near initialization for ‘debug_callbacks[0].proc’) cyrus-sasl.c:120:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 120 | { SASL_CB_USER, &getuser_func, NULL }, | ^ cyrus-sasl.c:120:25: note: (near initialization for ‘debug_callbacks[1].proc’) cyrus-sasl.c:121:29: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 121 | { SASL_CB_AUTHNAME, &getuser_func, NULL }, | ^ cyrus-sasl.c:121:29: note: (near initialization for ‘debug_callbacks[2].proc’) cyrus-sasl.c:122:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(sasl_conn_t *, void *, int, sasl_secret_t **)’ {aka ‘int (*)(struct sasl_conn *, void *, int, struct sasl_secret **)’} [-Wincompatible-pointer-types] 122 | { SASL_CB_PASS, &getpass_func, NULL }, | ^ cyrus-sasl.c:122:25: note: (near initialization for ‘debug_callbacks[3].proc’) ./autofs-5.1.9/config.log: conftest.c: In function 'main': ./autofs-5.1.9/config.log: conftest.c:58:47: error: passing argument 4 of 'ldap_parse_page_control' from incompatible pointer type [-Wincompatible-pointer-types] ./autofs-5.1.9/config.log: 58 | ret = ldap_parse_page_control(ld,clp,ct,c); ./autofs-5.1.9/config.log: | ^ ./autofs-5.1.9/config.log: | | ./autofs-5.1.9/config.log: | struct berval * ./autofs-5.1.9/config.log: In file included from /usr/include/lber_types.h:24, ./autofs-5.1.9/config.log: from /usr/include/lber.h:29, ./autofs-5.1.9/config.log: from /usr/include/ldap.h:30, ./autofs-5.1.9/config.log: from conftest.c:49: ./autofs-5.1.9/config.log: /usr/include/ldap.h:2155:25: note: expected 'struct berval **' but argument is of type 'struct berval *' ./autofs-5.1.9/config.log: 2155 | ldap_parse_page_control LDAP_P(( ./autofs-5.1.9/config.log: | ^~~~~~ Fixing configure may not be necessary to build the package, but it might be an indication that the package will be misconfigured. See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1221507] New: sddm fails to start with DisplayServer=wayland - always attempts to use tty1
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221507 Bug ID: 1221507 Summary: sddm fails to start with DisplayServer=wayland - always attempts to use tty1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- VERSION_ID="20240314" S | Name | Summary | Type ---+-----------------------------+-----------------------------------+------ i+ | kcm_sddm | A sddm control module for KDE | пакет i+ | kcm_sddm-lang | Translations for package kcm_sddm | пакет i+ | plasma6-sddm-theme-openSUSE | SDDM theme for openSUSE | пакет i+ | sddm | QML-based display manager (Qt5) | пакет i | sddm-branding-openSUSE | openSUSE branding for SDDM (Qt5) | пакет i | sddm-greeter-qt5 | SDDM Greeter for Qt5 themes | пакет i | sddm-greeter-qt6 | SDDM Greeter for Qt6 themes | пакет i | sddm-qt6-branding-openSUSE | Plasma 6 branding for SDDM | пакет bor@uefi:~> cat /etc/sddm.conf.d/wayland.conf [General] DisplayServer=wayland bor@uefi:~> loginctl SESSION UID USER SEAT TTY STATE IDLE SINCE 10 1000 bor - pts/0 active no - 1 sessions listed. bor@uefi:~> мар 16 21:30:47 uefi sddm[1192]: Initializing... мар 16 21:30:47 uefi sddm[1192]: Starting... мар 16 21:30:47 uefi sddm[1192]: Logind interface found мар 16 21:30:47 uefi sddm[1192]: Adding new display... мар 16 21:30:47 uefi sddm[1192]: Loaded empty theme configuration мар 16 21:30:47 uefi sddm[1192]: Using VT 1 мар 16 21:30:47 uefi sddm[1192]: Display server started. мар 16 21:30:48 uefi sddm[1192]: Reading from "/usr/local/share/wayland-sessions/plasmawayland.desktop" мар 16 21:30:48 uefi sddm[1192]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" мар 16 21:30:48 uefi sddm[1192]: Session "/usr/share/wayland-sessions/plasmawayland.desktop" selected, command: "/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" for VT 1 мар 16 21:30:49 uefi sddm-helper[1245]: [PAM] Starting... мар 16 21:30:49 uefi sddm-helper[1245]: [PAM] Authenticating... мар 16 21:30:49 uefi sddm-helper[1245]: [PAM] returning. мар 16 21:30:49 uefi sddm[1192]: Authentication for user "bor" successful мар 16 21:30:54 uefi sddm-helper[1245]: pam_unix(sddm-autologin:session): session opened for user bor(uid=1000) by bor(uid=0) мар 16 21:30:54 uefi sddm-helper[1245]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_open_session мар 16 21:30:54 uefi sddm-helper[1245]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: open_session called without kwallet5_key мар 16 21:30:55 uefi sddm-helper[1245]: [PAM] Preparing to converse... мар 16 21:30:55 uefi sddm-helper[1245]: [PAM] Conversation with 1 messages мар 16 21:30:55 uefi sddm[1192]: Authentication information: SDDM::Auth::INFO_UNKNOWN "Last login: Sat Mar 16 21:24:37 MSK 2024 on tty1" мар 16 21:30:57 uefi sddm-helper[1245]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" мар 16 21:30:57 uefi sddm-helper[1318]: Failed to take control of "/dev/tty1" ("root"): Operation not permitted Well, tty1 of course belongs to agetty. In X11 mode SDDM is using setUpNewVt() which calls IOCTL VT_OPENQRY while in Wayland mode it starts with vt1 and checks whether there is logind session using it. Of course there is no logind session so it always assumes vt1 is available. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1216969] New: Recent Applications and Recent Files are no longer updated
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1216969 Bug ID: 1216969 Summary: Recent Applications and Recent Files are no longer updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent Applications and Recent Files are no longer updated in KDE's Application menu. The links are existing in .local/share/RecentDocuments, though. Didn't find any directory for Recent Apps. Operating System: openSUSE Tumbleweed 20231106 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 13