June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[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 1225801] New: Package libgee does not build with gcc14 because of new errors
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225801 Bug ID: 1225801 Summary: Package libgee does not build with gcc14 because of new errors 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: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- GCC 14 newly by default treats as errors a number of situations which before were only warnings. For more information see https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571. Because of this, package libgee fails to compile. This can be seen online at: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… It can be reproduced locally with command: osc build --clean --alternative-project home:rguenther:nextgcc See also https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/l/libgee.md?re… and https://bugs.gentoo.org/920315 and https://bugs.gentoo.org/894376 The (first) error (that halts the build) is: [ 11s] concurrentlist.c: In function 'gee_concurrent_list_construct': [ 11s] concurrentlist.c:469:168: error: passing argument 4 of 'gee_hazard_pointer_set_pointer' from incompatible pointer type [-Wincompatible-pointer-types] [ 11s] 469 | gee_hazard_pointer_set_pointer (GEE_CONCURRENT_LIST_TYPE_NODE, (GBoxedCopyFunc) gee_concurrent_list_node_ref, (GDestroyNotify) gee_concurrent_list_node_unref, &self->priv->_tail, _tmp7_, (gsize) 0, (gsize) 0); [ 11s] | ^~~~~~~~~~~~~~~~~~ [ 11s] | | [ 11s] | GeeConcurrentListNode ** {aka struct _GeeConcurrentListNode **} [ 11s] In file included from concurrentlist.c:26: [ 11s] gee.h:2076:54: note: expected 'const void ***' but argument is of type 'GeeConcurrentListNode **' {aka 'struct _GeeConcurrentListNode **'} [ 11s] 2076 | gconstpointer** aptr, [ 11s] | ~~~~~~~~~~~~~~~~^~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225800] New: Package libesmtp does not build with gcc14 because of new errors
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225800 Bug ID: 1225800 Summary: Package libesmtp does not build with gcc14 because of new errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- GCC 14 newly by default treats as errors a number of situations which before were only warnings. For more information see https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571. Because of this, package libesmtp fails to compile. This can be seen online at: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… It can be reproduced locally with command: osc build --clean --alternative-project home:rguenther:nextgcc Notes from fedora-modernc project however suggest that "removing autotools" is necessary: https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/l/libesmtp.md?… The (first) error (that halts the build) is: [ 24s] ../smtp-api.c: In function ‘smtp_version’: [ 24s] ../smtp-api.c:1183:7: error: implicit declaration of function ‘strlcpy’; did you mean ‘strncpy’? [-Wimplicit-function-declaration] [ 24s] 1183 | if (strlcpy (buf, v, len) > len) [ 24s] | ^~~~~~~ [ 24s] | strncpy -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 1225791] New: Packman Mesa update cause KDE Plamsa Wayland failed to launch from SDDM
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225791 Bug ID: 1225791 Summary: Packman Mesa update cause KDE Plamsa Wayland failed to launch from SDDM 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: i(a)guoyunhe.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Yesterday, I run zypper dup and updated a few Mesa packages from Packman. Today when I boot system, I cannot launch KDE Plasma Wayland from SDDM. (X11 works though) I tried to removed Packman repo and install Mesa from openSUSE repos, and now KDE Plasma Wayland works properly. I check journalctl and found all kde services core dumped when using Packman Mesa packages: 6月 02 10:35:31 amd-desktop systemd-coredump[9555]: [🡕] Process 9537 (org_kde_powerde) of user 1000 dumped core. Stack trace of thread 9537: #0 0x00007f12fda949dc __pthread_kill_implementation (libc.so.6 + 0x949dc) #1 0x00007f12fda41176 raise (libc.so.6 + 0x41176) #2 0x00007f12fda28917 abort (libc.so.6 + 0x28917) #3 0x00007f12fe2e072d _Z6qAbortv (libQt6Core.so.6 + 0xe072d) #4 0x00007f12fe3309fe n/a (libQt6Core.so.6 + 0x1309fe) #5 0x00007f12fe2e1de3 _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0xe1de3) #6 0x00007f12feb584c9 n/a (libQt6Gui.so.6 + 0x1584c9) #7 0x00007f12febe8500 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x1e8500) #8 0x00007f12fe392d3d _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x192d3d) #9 0x00007f12febe858c _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x1e858c) #10 0x00007f12febe9800 _ZN15QGuiApplicationC1ERiPPci (libQt6Gui.so.6 + 0x1e9800) #11 0x000055ad20c01d82 n/a (org_kde_powerdevil + 0x9d82) #12 0x00007f12fda2a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #13 0x00007f12fda2a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #14 0x000055ad20c02ca5 n/a (org_kde_powerdevil + 0xaca5) Stack trace of thread 9551: #0 0x00007f12fdb0578f __poll (libc.so.6 + 0x10578f) #1 0x00007f12fc91432f n/a (libglib-2.0.so.0 + 0x5f32f) #2 0x00007f12fc914a3c g_main_context_iteration (libglib-2.0.so.0 + 0x5fa3c) #3 0x00007f12fe5c0a0c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3c0a0c) #4 0x00007f12fe39979b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x19979b) #5 0x00007f12fe474c84 _ZN7QThread4execEv (libQt6Core.so.6 + 0x274c84) #6 0x00007f12fe97b6fa n/a (libQt6DBus.so.6 + 0x386fa) #7 0x00007f12fe4ece59 n/a (libQt6Core.so.6 + 0x2ece59) #8 0x00007f12fda92ba2 start_thread (libc.so.6 + 0x92ba2) #9 0x00007f12fdb1400c __clone3 (libc.so.6 + 0x11400c) ELF object binary architecture: AMD x86-64 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1216444] segfault in akonadi_html_to
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1216444 https://bugzilla.suse.com/show_bug.cgi?id=1216444#c2 Michael Hirmke <opensuse(a)mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #2 from Michael Hirmke <opensuse(a)mike.franken.de> --- Seems to have been solved in the meantime, probably by KDE6. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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