August 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1135095] New: LTO: xtrabackup build fails
by bugzilla_noreply＠novell.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1135095 Bug ID: 1135095 Summary: LTO: xtrabackup build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails here: https://build.opensuse.org/build/openSUSE:Factory:Staging:N/standard/x86_64… due to: [ 313s] /home/abuild/rpmbuild/BUILD/percona-xtrabackup-2.4.12/build/libmysql/libmysql_exports_file.cc:106:15: error: function 'mysql_load_plugin' redeclared as variable [ 313s] 106 | extern void* mysql_load_plugin; [ 313s] | ^ [ 313s] /home/abuild/rpmbuild/BUILD/percona-xtrabackup-2.4.12/sql-common/client_plugin.c:541:1: note: previously declared here [ 313s] 541 | mysql_load_plugin(MYSQL *mysql, const char *name, int type, int argc, ...) [ 313s] | ^ [ 313s] /home/abuild/rpmbuild/BUILD/percona-xtrabackup-2.4.12/build/libmysql/libmysql_exports_file.cc:105:15: error: function 'mysql_client_register_plugin' redeclared as variable [ 313s] 105 | extern void* mysql_client_register_plugin; [ 313s] | ^ [ 313s] /home/abuild/rpmbuild/BUILD/percona-xtrabackup-2.4.12/sql-common/client_plugin.c:395:1: note: previously declared here [ 313s] 395 | mysql_client_register_plugin(MYSQL *mysql, [ 313s] | ^ [ 313s] /home/abuild/rpmbuild/BUILD/percona-xtrabackup-2.4.12/build/libmysql/libmysql_exports_file.cc:104:15: error: function 'mysql_client_find_plugin' redeclared as variable [ 313s] 104 | extern void* mysql_client_find_plugin; [ 313s] | ^ [ 313s] /home/abuild/rpmbuild/BUILD/percona-xtrabackup-2.4.12/sql-common/client_plugin.c:553:1: note: previously declared here -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1175424] New: gnome-shell: random crashes
by bugzilla_noreply＠suse.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1175424 Bug ID: 1175424 Summary: gnome-shell: random crashes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using latest TW I see occasional random gnome-shell crashes: Aug 18 09:49:15 marxinbox.suse.cz systemd-coredump[21092]: Process 1423 (gnome-shell) of user 1000 dumped core. Stack trace of thread 1423: #0 0x00007ffff6c154b1 __GI_raise (libc.so.6 + 0x3c4b1) #1 0x0000555555556ed2 n/a (gnome-shell + 0x2ed2) #2 0x00007ffff6c15530 __restore_rt (libc.so.6 + 0x3c530) #3 0x00007ffff7a0f2b7 g_log_structured_array (libglib-2.0.so.0 + 0x5b2b7) #4 0x00007ffff7a0f6c5 g_log_default_handler (libglib-2.0.so.0 + 0x5b6c5) #5 0x0000555555556cda n/a (gnome-shell + 0x2cda) #6 0x00007ffff7a0f919 g_logv (libglib-2.0.so.0 + 0x5b919) #7 0x00007ffff7a0fbaf g_log (libglib-2.0.so.0 + 0x5bbaf) #8 0x00007ffff710b457 n/a (libgjs.so.0 + 0x48457) #9 0x00007ffff7116b70 n/a (libgjs.so.0 + 0x53b70) #10 0x00007ffff7116bf7 n/a (libgjs.so.0 + 0x53bf7) #11 0x00007ffff7a04057 n/a (libglib-2.0.so.0 + 0x50057) #12 0x00007ffff7a082b7 g_main_context_dispatch (libglib-2.0.so.0 + 0x542b7) #13 0x00007ffff7a08638 n/a (libglib-2.0.so.0 + 0x54638) #14 0x00007ffff7a0892b g_main_loop_run (libglib-2.0.so.0 + 0x5492b) #15 0x00007ffff6e5cca4 meta_run (libmutter-6.so.0 + 0xbaca4) #16 0x0000555555556838 n/a (gnome-shell + 0x2838) #17 0x00007ffff6bffcca __libc_start_main (libc.so.6 + 0x26cca) #18 0x0000555555556a1a n/a (gnome-shell + 0x2a1a) Stack trace of thread 1427: #0 0x00007ffff6ccdfcf __GI___poll (libc.so.6 + 0xf4fcf) #1 0x00007ffff7a085ce n/a (libglib-2.0.so.0 + 0x545ce) #2 0x00007ffff7a086ef g_main_context_iteration (libglib-2.0.so.0 + 0x546ef) #3 0x00007ffff7a08741 n/a (libglib-2.0.so.0 + 0x54741) #4 0x00007ffff7a319de n/a (libglib-2.0.so.0 + 0x7d9de) #5 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #6 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1461: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1453: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1430: #0 0x00007ffff6ccdfcf __GI___poll (libc.so.6 + 0xf4fcf) #1 0x00007ffff7a085ce n/a (libglib-2.0.so.0 + 0x545ce) #2 0x00007ffff7a086ef g_main_context_iteration (libglib-2.0.so.0 + 0x546ef) #3 0x00007ffff7d4456d dconf_gdbus_worker_thread (libdconfsettings.so + 0x656d) #4 0x00007ffff7a319de n/a (libglib-2.0.so.0 + 0x7d9de) #5 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #6 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1429: #0 0x00007ffff6ccdfcf __GI___poll (libc.so.6 + 0xf4fcf) #1 0x00007ffff7a085ce n/a (libglib-2.0.so.0 + 0x545ce) #2 0x00007ffff7a0892b g_main_loop_run (libglib-2.0.so.0 + 0x5492b) #3 0x00007ffff7c57786 n/a (libgio-2.0.so.0 + 0x11f786) #4 0x00007ffff7a319de n/a (libglib-2.0.so.0 + 0x7d9de) #5 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #6 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1454: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1460: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1468: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1465: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1458: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1459: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1467: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1464: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1502: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007ffff58a3fb9 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so + 0x7dffb9) #2 0x00007ffff58a5cdd _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-68.so + 0x7e1cdd) #3 0x00007ffff52ec7da n/a (libmozjs-68.so + 0x2287da) #4 0x00007ffff52ed68b n/a (libmozjs-68.so + 0x22968b) #5 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #6 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1500: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007ffff58a3fb9 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so + 0x7dffb9) #2 0x00007ffff58a5cdd _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-68.so + 0x7e1cdd) #3 0x00007ffff52ec7da n/a (libmozjs-68.so + 0x2287da) #4 0x00007ffff52ed68b n/a (libmozjs-68.so + 0x22968b) #5 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #6 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1462: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1503: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007ffff58a3fb9 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so + 0x7dffb9) #2 0x00007ffff58a5cdd _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-68.so + 0x7e1cdd) #3 0x00007ffff52ec7da n/a (libmozjs-68.so + 0x2287da) #4 0x00007ffff52ed68b n/a (libmozjs-68.so + 0x22968b) #5 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #6 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1469: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1457: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1455: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1471: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1466: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1463: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1499: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007ffff58a3fb9 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so + 0x7dffb9) #2 0x00007ffff58a5cdd _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-68.so + 0x7e1cdd) #3 0x00007ffff52ec7da n/a (libmozjs-68.so + 0x2287da) #4 0x00007ffff52ed68b n/a (libmozjs-68.so + 0x22968b) #5 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #6 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1497: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007ffff58a3fb9 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so + 0x7dffb9) #2 0x00007ffff58a5cdd _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-68.so + 0x7e1cdd) #3 0x00007ffff52ec7da n/a (libmozjs-68.so + 0x2287da) #4 0x00007ffff52ed68b n/a (libmozjs-68.so + 0x22968b) #5 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #6 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1501: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007ffff58a3fb9 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so + 0x7dffb9) #2 0x00007ffff58a5cdd _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-68.so + 0x7e1cdd) #3 0x00007ffff52ec7da n/a (libmozjs-68.so + 0x2287da) #4 0x00007ffff52ed68b n/a (libmozjs-68.so + 0x22968b) #5 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #6 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1472: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1498: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007ffff58a3fb9 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so + 0x7dffb9) #2 0x00007ffff58a5cdd _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-68.so + 0x7e1cdd) #3 0x00007ffff52ec7da n/a (libmozjs-68.so + 0x2287da) #4 0x00007ffff52ed68b n/a (libmozjs-68.so + 0x22968b) #5 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #6 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 11935: #0 0x00007ffff6cd3629 syscall (libc.so.6 + 0xfa629) #1 0x00007ffff7a560c2 g_cond_wait_until (libglib-2.0.so.0 + 0xa20c2) #2 0x00007ffff79d8521 n/a (libglib-2.0.so.0 + 0x24521) #3 0x00007ffff79d8b42 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x24b42) #4 0x00007ffff7a32369 n/a (libglib-2.0.so.0 + 0x7e369) #5 0x00007ffff7a319de n/a (libglib-2.0.so.0 + 0x7d9de) #6 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #7 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1504: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007ffff58a3fb9 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so + 0x7dffb9) #2 0x00007ffff58a5cdd _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-68.so + 0x7e1cdd) #3 0x00007ffff52ec7da n/a (libmozjs-68.so + 0x2287da) #4 0x00007ffff52ed68b n/a (libmozjs-68.so + 0x22968b) #5 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #6 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1477: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1475: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1470: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1474: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1456: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) Stack trace of thread 1473: #0 0x00007ffff61467e2 futex_wait_cancelable (libpthread.so.0 + 0xf7e2) #1 0x00007fffe9e2598b n/a (radeonsi_dri.so + 0x4bf98b) #2 0x00007fffe9e258b7 n/a (radeonsi_dri.so + 0x4bf8b7) #3 0x00007ffff613feaa start_thread (libpthread.so.0 + 0x8eaa) #4 0x00007ffff6cd8aff __clone (libc.so.6 + 0xffaff) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1133305] New: LTO: multipath-tools build fails
by bugzilla_noreply＠novell.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1133305 Bug ID: 1133305 Summary: LTO: multipath-tools build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- in the LTO staging project (openSUSE:Factory:Staging:N), libaio doesn't export all symbols it used to export. In particular, io_cancel() and io_getevents() are undefined: apollon:/mnt/img/lib64 # nm -D libaio.so.1 0000000000000000 A LIBAIO_0.1 0000000000000000 A LIBAIO_0.4 U __stack_chk_fail U io_cancel 0000000000001050 T io_destroy U io_getevents 0000000000001110 T io_queue_init 0000000000001100 T io_queue_release 0000000000001080 T io_queue_run 0000000000001060 T io_setup 0000000000001070 T io_submit This causes the multipath-tools build to fail. The failure is independent on whether -flto=X is active while building multipath-tools itself. > [ 50s] gcc -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -flto=4 -g -DBIN_DIR=\"/sbin\" -DLIB_STRING=\"lib64\" -DRUN_DIR=\"run\" -MMD -MP -fPIE -I../libmultipath -I../libmpathcmd main.o -o multipath -Wl,-z,relro -Wl,-z,now -pie -L../libmultipath -lmultipath -L../libmpathcmd -lmpathcmd -lpthread -ldevmapper -ldl -ludev -laio > [ 50s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../libmultipath/libmultipath.so: undefined reference to `io_getevents' > [ 50s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../libmultipath/libmultipath.so: undefined reference to `io_cancel'' > [ 50s] collect2: error: ld returned 1 exit status > [ 50s] make[1]: *** [Makefile:18: multipath] Error 1 -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1133233] New: LTO: libaio build fails
by bugzilla_noreply＠novell.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1133233 Bug ID: 1133233 Summary: LTO: libaio build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package delivers a static library and should use fat LTO objects: https://en.opensuse.org/openSUSE:LTO#Static_libraries -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1133277] New: LTO: protobuf abuild fails
by bugzilla_noreply＠novell.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1133277 Bug ID: 1133277 Summary: LTO: protobuf abuild fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails due to: [ 233s] + ../src/protoc --java_out=core/src/main/java -I../src ../src/google/protobuf/descriptor.proto [ 233s] terminate called after throwing an instance of 'std::system_error' [ 233s] what(): Unknown error -1 [ 233s] /var/tmp/rpm-tmp.IcJGkF: line 61: 9707 Aborted ../src/protoc --java_out=core/src/main/java -I../src ../src/google/protobuf/descriptor.proto #0 0x00007ffff7e3fd8b in raise () from /lib64/libc.so.6 #1 0x00007ffff7e29549 in abort () from /lib64/libc.so.6 #2 0x00007ffff7aad63f in ?? () from /usr/lib64/libstdc++.so.6 #3 0x00007ffff7ab8f38 in ?? () from /usr/lib64/libstdc++.so.6 #4 0x00007ffff7ab8f83 in std::terminate() () from /usr/lib64/libstdc++.so.6 #5 0x00007ffff7ab91b4 in __cxa_throw () from /usr/lib64/libstdc++.so.6 #6 0x00007ffff7ab0156 in std::__throw_system_error(int) () from /usr/lib64/libstdc++.so.6 #7 0x00007ffff792741b in std::call_once<void (&)()> (__once=..., __f=<optimized out>) at /usr/include/c++/9/x86_64-suse-linux/bits/gthr-default.h:700 #8 0x00007ffff77fbb83 in global constructors keyed to 65535_0_bytestream.o.132584 () at ./google/protobuf/repeated_field.h:428 #9 0x00007ffff7fe276a in call_init.part () from /lib64/ld-linux-x86-64.so.2 #10 0x00007ffff7fe2866 in _dl_init () from /lib64/ld-linux-x86-64.so.2 #11 0x00007ffff7fd40ca in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #12 0x0000000000000004 in ?? () #13 0x00007fffffffeb14 in ?? () #14 0x00007fffffffeb50 in ?? () #15 0x00007fffffffeb6e in ?? () #16 0x00007fffffffeb77 in ?? () #17 0x0000000000000000 in ?? () https://github.com/protocolbuffers/protobuf/issues/5923 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1194809] New: Possible password leak by windows stealing focus
by bugzilla_noreply＠suse.com 23 Mar '23

23 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1194809 Bug ID: 1194809 Summary: Possible password leak by windows stealing focus Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Yesterday I lost (luckily only part of) an important password as follows: I was running pidgin as IRC client. pidgin was configured to autoconnect to some channels on irc.suse.de. I activated the SUSE VPN via the GNOME VPN panel. I continued working in the terminal. I ran a command in the terminal that required typing a password (as usual in terminal applications, typing passwords provides no visual feedback like "***"). I pressed "enter" and nothing happened. At this point I realized that the 2nd half of the password had ended up in the pidgin window. What happened? If an IRC server is unreachable, pidgin polls in the background in a certain interval (a few minutes I think). When the server becomes reachable, it connects to it, which causes the typical startup dialog & messages ("You are connected to irc1.suse.de ....") to be displayed. At this moment, the pidgin window pops up and grabs the keyboard focus. As the window is relatively small and my screen is large, and I was looking at the keyboard while typing (because I usually do when typing passwords), I didn't notice this immediately, and typed part of the password to the pidgin window. This is particularly nasty, because after establishing the VPN connection, the window pops up after a non-deterministic time interval which is between a few seconds and ~5 minutes. You can't "wait" for this to happen, and if you don't, you're likely to forget that the connection process is going on in the background. Also, making matters worse, when the pidgin window pops up because of a message in some chat, the focus isn't necessarily in the chat (tab in the pidgin window) that caused the pop-up, but in some currently selected chat. In the case at hand, I'd typed my password at to libera.chat's "NickServ" bot (which didn't recongnize it as command, but might have logged what I typed). For the time being, I've disabled the "auto-join" feature for all pidgin channels on irc.suse.de. But I'm unsure if that actually helps, because I believe that pidgin would try to connect to IRC accounts nonetheless, and if it does, the typical login / connect dialogs might cause the window to pop up even if no chats are configured to connect automatically. See also https://askubuntu.com/questions/1084032/how-to-prevent-new-windows-from-ste… There someone suggests using > gsettings set org.gnome.desktop.wm.preferences focus-new-windows 'strict' I've tried that setting on TW (GNOME 41.3) and saw no change in behavior. A simple test is typing something like this in the terminal: > $ gedit & > $ abcdefg.... # continue typing At some point, gedit will pop up and the text will end up in the gedit window. Note that this happens with gedit but not e.g. with emacs or libreoffice writer. So it depends on the application. Also, some applications (e.g. the ssh and gpg askpass tools) use a different API that does this much better - the entire screen gets locked and changes color, so that typing something at the wrong window is practically impossible. This behavior would be inapparopriate for an application like gedit, though. The behavior of gedit and pidgin under GNOME is highly dangerous. I've reason to believe that other Window Managers (or X in general) behave similarly. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1194332] New: kernel lsm boot parameter needs lsm=integrity to use IMA
by bugzilla_noreply＠suse.com 23 Mar '23

23 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1194332 Bug ID: 1194332 Summary: kernel lsm boot parameter needs lsm=integrity to use IMA Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Build 20211229 added 'lsm=apparmor' as a kernel parameter into GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. Please change it to 'lsm=integrity,apparmor' to allow using IMA (e.g. 'ima_policy=tcb' kernel parameter). That avoids kernel oops breaking boot [1]: [ 1.210321][ T1] Kernel panic - not syncing: integrity_inode_get: lsm=integrity required. [ 1.212119][ T1] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.15.12-1-default #1 openSUSE Tumbleweed dacaf19d133e8023737b25567dc90a32d973f26e [ 1.215246][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014 [ 1.218496][ T1] Call Trace: [ 1.219715][ T1] <TASK> [ 1.220844][ T1] dump_stack_lvl+0x46/0x5a [ 1.222144][ T1] panic+0xf3/0x2cb [ 1.223326][ T1] integrity_inode_get.cold+0x13/0x13 [ 1.224710][ T1] process_measurement+0x86e/0x960 [ 1.226069][ T1] ? aa_file_perm+0x112/0x480 [ 1.227359][ T1] ? select_task_rq_fair+0x15a/0x1350 [ 1.228744][ T1] ? __kernel_read+0x14a/0x2d0 [ 1.230068][ T1] ? profile_signal_perm.part.0+0x91/0xb0 [ 1.231516][ T1] ima_bprm_check+0x55/0xb0 [ 1.232810][ T1] bprm_execve+0x22a/0x660 [ 1.234104][ T1] ? rest_init+0xc0/0xc0 [ 1.235372][ T1] kernel_execve+0x12e/0x1b0 [ 1.236689][ T1] kernel_init+0x76/0x120 [ 1.237982][ T1] ret_from_fork+0x22/0x30 [ 1.239278][ T1] </TASK> [ 1.240462][ T1] Kernel Offset: 0x7600000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 1.243605][ T1] Rebooting in 90 seconds.. [1] https://openqa.opensuse.org/tests/2122167#step/boot_ltp/13 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1201962] New: Bootloader password leaked into_YaST logs
by bugzilla_noreply＠suse.com 23 Mar '23

23 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1201962 Bug ID: 1201962 Summary: Bootloader password leaked into_YaST logs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: ancor(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In yast2-bootloader (even during system installation) if the option "Protect Boot Loader with Password" is used, YaST executes the command grub2-mkpasswd-pbkdf2 to generate the hashed password. Doing so, it leaks the typed password to the YaST logs. https://github.com/yast/yast-bootloader/blob/master/src/lib/bootloader/grub… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1201248] New: VUL-0: CVE-2022-31014: nextcloud: Nextcloud is vulnerable to SMTP command injection
by bugzilla_noreply＠suse.com 23 Mar '23

23 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1201248 Bug ID: 1201248 Summary: VUL-0: CVE-2022-31014: nextcloud: Nextcloud is vulnerable to SMTP command injection Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/336309/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: ecsos(a)schirra.net Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2022-31014 Nextcloud server is an open source personal cloud server. Affected versions were found to be vulnerable to SMTP command injection. The impact varies based on which commands are supported by the backend SMTP server. However, the main risk here is that the attacker can then hijack an already-authenticated SMTP session and run arbitrary SMTP commands as the email user, such as sending emails to other users, changing the FROM user, and so on. As before, this depends on the configuration of the server itself, but newlines should be sanitized to mitigate such arbitrary SMTP command injection. It is recommended that the Nextcloud Server is upgraded to 22.2.8 , 23.0.5 or 24.0.1. There are no known workarounds for this issue. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-31014 https://github.com/nextcloud/security-advisories/security/advisories/GHSA-2… https://github.com/nextcloud/server/pull/32428 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31014 https://hackerone.com/reports/1516377 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1185529] New: libgccjit does not find libgcc/crtbegin.o
by bugzilla_noreply＠suse.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1185529 Bug ID: 1185529 Summary: libgccjit does not find libgcc/crtbegin.o Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: opensusebz(a)halobates.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to compile current emacs with libgccjit11, but the test of libgccjit at configure time fails: (t.c is below) gcc t.c -lgccjit ./a.out ld: cannot find crtbeginS.o: No such file or directory ld: cannot find -lgcc ld: cannot find -lgcc_s libgccjit.so: error: error invoking gcc driver strace shows that the paths seem to be incorrect: strace -e execve -f ./a.out ... [pid 23720] execve("/usr/bin/ld", ["ld", "--build-id", "--eh-frame-hdr", "-m", "elf_x86_64", "-shared", "-o", "/tmp/libgccjit-X37gMf/fake.so", "/usr/lib/../lib64/crti.o", "crtbeginS.o", "-L/lib/../lib64", "-L/usr/lib/../lib64", "/tmp/ccgGNXSP.o", "-lgcc", "--push-state", "--as-needed", "-lgcc_s", "--pop-state", "-lc", "-lgcc", "--push-state", "--as-needed", "-lgcc_s", "--pop-state", "crtendS.o", "/usr/lib/../lib64/crtn.o"], 0x14203a0 /* 105 vars */) = 0 crtbegin etc. are in /usr/lib64/gcc/x86_64-suse-linux/ but the driver is not telling the linker that. t.c: #include <libgccjit.h> #include <stdlib.h> #include <stdio.h> int main (int argc, char **argv) { gcc_jit_context *ctxt; gcc_jit_result *result; ctxt = gcc_jit_context_acquire (); if (!ctxt) exit (1); gcc_jit_type *int_type = gcc_jit_context_get_type (ctxt, GCC_JIT_TYPE_INT); gcc_jit_function *func = gcc_jit_context_new_function (ctxt, NULL, GCC_JIT_FUNCTION_EXPORTED, int_type, "foo", 0, NULL, 0); gcc_jit_block *block = gcc_jit_function_new_block (func, "foo"); gcc_jit_block_end_with_return ( block, NULL, gcc_jit_context_new_rvalue_from_int (ctxt, int_type, 1)); result = gcc_jit_context_compile (ctxt); if (!result) exit (1); typedef int (*fn_type) (void); fn_type foo = (fn_type)gcc_jit_result_get_code (result, "foo"); if (!foo) exit (1); if (foo () != 1) exit (1); gcc_jit_context_release (ctxt); gcc_jit_result_release (result); return 0; } -- You are receiving this mail because: You are on the CC list for the bug.

1 3