June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225787] New: openSUSE Leap 15.5 hangs during boot with recent kernels on Raspberry Pi 3b
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225787 Bug ID: 1225787 Summary: openSUSE Leap 15.5 hangs during boot with recent kernels on Raspberry Pi 3b Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: adrian.glaubitz(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- One of the recent updates broke openSUSE Leap 15.5 on the Raspberry Pi 3B. The systems no longer boots beyond "Reached target Basic System." The last working version for me was: - 5.14.21-150500.55.52-default The following two versions don't work: - 5.14.21-150500.55.59-default - 5.14.21-150500.55.65-default The last kernel messages before the system hangs are: [ OK ] Started Forward Password R…s to Plymouth Directory Watch. [ OK ] Reached target Path Units. [ OK ] Reached target Basic System. [ 7.538503][ T311] mmc1: new high speed SDIO card at address 0001 [ 7.562530][ T300] mmcblk0: mmc0:e624 SC32G 29.7 GiB [ 7.575747][ T300] mmcblk0: p1 p2 p3 [ 7.592670][ T296] dwc2 3f980000.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [ 7.600936][ T296] dwc2 3f980000.usb: DWC OTG Controller [ 7.606531][ T296] dwc2 3f980000.usb: new USB bus registered, assigned bus number 1 [ 7.614486][ T296] dwc2 3f980000.usb: irq 51, io mem 0x3f980000 [ 7.620891][ T296] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14 [ 7.630098][ T296] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 7.638174][ T296] usb usb1: Product: DWC OTG Controller [ 7.638178][ T301] fb0: switching to vc4 from EFI VGA [ 7.638188][ T296] usb usb1: Manufacturer: Linux 5.14.21-150500.55.59-default dwc2_hsotg [ 7.657225][ T296] usb usb1: SerialNumber: 3f980000.usb [ 7.657301][ T301] Console: switching to colour dummy device 80x25 [ 7.657891][ T296] hub 1-0:1.0: USB hub found [ 7.673797][ T296] hub 1-0:1.0: 1 port detected [ 7.689828][ T301] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4]) This issue has been independently reported by another user in [1]. > [1] https://lists.opensuse.org/archives/list/arm@lists.opensuse.org/thread/L3WQ… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225644] [Build 20240527] openQA test fails in apptainer
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225644 https://bugzilla.suse.com/show_bug.cgi?id=1225644#c3 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|guillaume.gardet(a)arm.com |containers-bugowner(a)suse.de --- Comment #3 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Egbert Eich from comment #2) > Created attachment 875252 [details] > Screenshot from test > > This is a problem with the test suite. The screen shot shows the error > message: > "While performing build: while creating squashfs: create command failed: > exit status 1: Write failed because no space left on device". > Assigning back to reporter as he may know who would be able to address this. I do not think this is a problem with the test suite since the same test code used to work and was not updated recently https://github.com/os-autoinst/os-autoinst-distri-opensuse/commits/master/t… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222715] segmentation fault with vdr-plugin-xineliboutput and libvdpau
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222715 https://bugzilla.suse.com/show_bug.cgi?id=1222715#c11 --- Comment #11 from Peter Münster <pmlists(a)free.fr> --- > "RESOLVED WORKSFORME" Does this mean, that you cannot reproduce it? And that it won’t be fixed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225777] Package hplip does not build with gcc14 because of new errors
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225777 Johannes Meixner <jsmeix(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.wilck(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225799] windows:mingw:win64/mingw64-kmymoney5: crashes on startup
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225799 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fstrba(a)suse.com |ralf.habacker(a)freenet.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225798] windows:mingw:win32/mingw32-python: Incomplete dependencies when building mingw32-ktoblzcheck
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225798 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fstrba(a)suse.com |ralf.habacker(a)freenet.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221116] Enable qt6 VCL plugin building
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221116 Martin Schreiner <martin.schreiner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.schreiner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221116] Enable qt6 VCL plugin building
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221116 https://bugzilla.suse.com/show_bug.cgi?id=1221116#c6 --- Comment #6 from Martin Schreiner <martin.schreiner(a)suse.com> --- Ok folks, I got a Qt6 build kind of working. I'll post an update here tomorrow with an OBS repository we can test from. Also, any fixes I'll submit there, then we can submit to LibreOffice:Factory, and that will eventually land on openSUSE:Factory, and then on to Tumbleweed. But we might be able to do all of this during this week. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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