February 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1219945] New: gnome terminal server crash on gnome 46
by bugzilla_noreply＠suse.com 07 May '24

07 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219945 Bug ID: 1219945 Summary: gnome terminal server crash on gnome 46 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Latest TW: Mesa 23.3.5 GNOME:Next for the gnome 46 beta. ``` coredumpctl info 21918 | cat Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. PID: 21918 (gnome-terminal-) UID: 1000 (darix) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Thu 2024-02-15 02:04:12 CET (11min ago) Command Line: /usr/libexec/gnome-terminal-server Executable: /usr/libexec/gnome-terminal-server Control Group: /user.slice/user-1000.slice/user(a)1000.service/app.slice/app-org.gnome.Terminal.slice/gnome-terminal-server.service Unit: user(a)1000.service User Unit: gnome-terminal-server.service Slice: user-1000.slice Owner UID: 1000 (darix) Boot ID: 62d8c0f5e0ee48a192c37b6729c4f93e Machine ID: cb7e8828621b42ce840608de3f231bb4 Hostname: fortress.home.nordisch.org Storage: /var/lib/systemd/coredump/core.gnome-terminal-.1000.62d8c0f5e0ee48a192c37b6729c4f93e.21918.1707959052000000.zst (present) Size on Disk: 14.2M Message: Process 21918 (gnome-terminal-) of user 1000 dumped core. Stack trace of thread 21918: #0 0x00007fa419fae199 n/a (iris_dri.so + 0x1ae199) #1 0x00007fa419f68876 n/a (iris_dri.so + 0x168876) #2 0x00007fa419f68bc5 n/a (iris_dri.so + 0x168bc5) #3 0x00007fa419f68dc3 n/a (iris_dri.so + 0x168dc3) #4 0x00007fa43c8e6f25 n/a (libgtk-4.so.1 + 0x4e6f25) #5 0x00007fa43c8e21d9 n/a (libgtk-4.so.1 + 0x4e21d9) #6 0x00007fa43c8cea7f n/a (libgtk-4.so.1 + 0x4cea7f) #7 0x00007fa43c8e6c3b n/a (libgtk-4.so.1 + 0x4e6c3b) #8 0x00007fa43c8863a4 gsk_renderer_render (libgtk-4.so.1 + 0x4863a4) #9 0x00007fa43c692411 n/a (libgtk-4.so.1 + 0x292411) #10 0x00007fa43c6932b5 n/a (libgtk-4.so.1 + 0x2932b5) #11 0x00007fa43c7e1c64 n/a (libgtk-4.so.1 + 0x3e1c64) #12 0x00007fa43d0c7861 n/a (libgobject-2.0.so.0 + 0x17861) #13 0x00007fa43d0dcd06 n/a (libgobject-2.0.so.0 + 0x2cd06) #14 0x00007fa43d0e35c2 g_signal_emit_valist (libgobject-2.0.so.0 + 0x335c2) #15 0x00007fa43d0e366f g_signal_emit (libgobject-2.0.so.0 + 0x3366f) #16 0x00007fa43c867ed2 n/a (libgtk-4.so.1 + 0x467ed2) #17 0x00007fa43d0c7861 n/a (libgobject-2.0.so.0 + 0x17861) #18 0x00007fa43d0dd9c4 n/a (libgobject-2.0.so.0 + 0x2d9c4) #19 0x00007fa43d0e35c2 g_signal_emit_valist (libgobject-2.0.so.0 + 0x335c2) #20 0x00007fa43d0e366f g_signal_emit (libgobject-2.0.so.0 + 0x3366f) #21 0x00007fa43c84d32f n/a (libgtk-4.so.1 + 0x44d32f) #22 0x00007fa43cfc5114 n/a (libglib-2.0.so.0 + 0x60114) #23 0x00007fa43cfc2700 n/a (libglib-2.0.so.0 + 0x5d700) #24 0x00007fa43cfc4348 n/a (libglib-2.0.so.0 + 0x5f348) #25 0x00007fa43cfc49fc g_main_context_iteration (libglib-2.0.so.0 + 0x5f9fc) #26 0x00007fa43d1fd8ed g_application_run (libgio-2.0.so.0 + 0xe98ed) #27 0x0000559e9bfec93d n/a (gnome-terminal-server + 0x1893d) #28 0x00007fa43b82a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #29 0x00007fa43b82a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #30 0x0000559e9bfecbc5 n/a (gnome-terminal-server + 0x18bc5) Stack trace of thread 21921: #0 0x00007fa43b90578f __poll (libc.so.6 + 0x10578f) #1 0x00007fa43cfc42ef n/a (libglib-2.0.so.0 + 0x5f2ef) #2 0x00007fa43cfc49fc g_main_context_iteration (libglib-2.0.so.0 + 0x5f9fc) #3 0x00007fa43cfc4a41 n/a (libglib-2.0.so.0 + 0x5fa41) #4 0x00007fa43cff12de n/a (libglib-2.0.so.0 + 0x8c2de) #5 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #6 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 21919: #0 0x00007fa43b911bcd syscall (libc.so.6 + 0x111bcd) #1 0x00007fa43d01edf0 g_cond_wait (libglib-2.0.so.0 + 0xb9df0) #2 0x00007fa43cf8d0bb n/a (libglib-2.0.so.0 + 0x280bb) #3 0x00007fa43cf8d547 g_async_queue_pop (libglib-2.0.so.0 + 0x28547) #4 0x00007fa43ba4bd93 n/a (libpangoft2-1.0.so.0 + 0xad93) #5 0x00007fa43cff12de n/a (libglib-2.0.so.0 + 0x8c2de) #6 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #7 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 21935: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 21920: #0 0x00007fa43b911bcd syscall (libc.so.6 + 0x111bcd) #1 0x00007fa43d01edf0 g_cond_wait (libglib-2.0.so.0 + 0xb9df0) #2 0x00007fa43cf8d0bb n/a (libglib-2.0.so.0 + 0x280bb) #3 0x00007fa43cff1ad2 n/a (libglib-2.0.so.0 + 0x8cad2) #4 0x00007fa43cff12de n/a (libglib-2.0.so.0 + 0x8c2de) #5 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #6 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 21922: #0 0x00007fa43b90578f __poll (libc.so.6 + 0x10578f) #1 0x00007fa43cfc42ef n/a (libglib-2.0.so.0 + 0x5f2ef) #2 0x00007fa43cfc49fc g_main_context_iteration (libglib-2.0.so.0 + 0x5f9fc) #3 0x00007fa43929e99d n/a (libdconfsettings.so + 0x699d) #4 0x00007fa43cff12de n/a (libglib-2.0.so.0 + 0x8c2de) #5 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #6 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 22395: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 21934: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 21936: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 21923: #0 0x00007fa43b90578f __poll (libc.so.6 + 0x10578f) #1 0x00007fa43cfc42ef n/a (libglib-2.0.so.0 + 0x5f2ef) #2 0x00007fa43cfc4c1f g_main_loop_run (libglib-2.0.so.0 + 0x5fc1f) #3 0x00007fa43d23a276 n/a (libgio-2.0.so.0 + 0x126276) #4 0x00007fa43cff12de n/a (libglib-2.0.so.0 + 0x8c2de) #5 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #6 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 21937: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 859: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 22396: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 860: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 6653: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 10460: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 10461: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 6654: #0 0x00007fa43b88effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007fa43b891d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007fa419f0f42b n/a (iris_dri.so + 0x10f42b) #3 0x00007fa419f04697 n/a (iris_dri.so + 0x104697) #4 0x00007fa43b892bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007fa43b91400c __clone3 (libc.so.6 + 0x11400c) ELF object binary architecture: AMD x86-64 ``` ``` (gdb) bt #0 list_addtail (list=0x559ea1709098, item=0x559ea0ebfbb8) at ../src/util/list.h:83 #1 st_save_zombie_sampler_view (view=<optimized out>, st=0x559ea1707690) at ../src/mesa/state_tracker/st_context.c:214 #2 st_texture_release_all_sampler_views (st=0x559ea17e85b0, stObj=<optimized out>) at ../src/mesa/state_tracker/st_sampler_view.c:272 #3 0x00007fa419f68876 in st_texture_release_all_sampler_views (stObj=0x559ea25f3590, st=<optimized out>) at ../src/mesa/state_tracker/st_sampler_view.c:258 #4 st_delete_texture_sampler_views (stObj=0x559ea25f3590, st=<optimized out>) at ../src/mesa/state_tracker/st_sampler_view.c:292 #5 _mesa_delete_texture_object (ctx=0x559ea17a0f40, texObj=0x559ea25f3590) at ../src/mesa/main/texobj.c:523 #6 0x00007fa419f68bc5 in _mesa_reference_texobj_ (ptr=ptr@entry=0x559ea17b7760, tex=tex@entry=0x559ea0c219f0) at ../src/mesa/main/texobj.c:637 #7 0x00007fa419f68dc3 in _mesa_reference_texobj (tex=<optimized out>, ptr=<optimized out>) at ../src/mesa/main/texobj.h:92 #8 bind_texture_object (ctx=0x559ea17a0f40, unit=2, texObj=0x559ea0c219f0) at ../src/mesa/main/texobj.c:1714 #9 0x00007fa43c8e6f25 in gsk_gl_descriptors_use (self=0x559ea0fe0710) at ../gsk/gpu/gskgldescriptors.c:132 #10 gsk_gpu_shader_op_gl_command_n (op=<optimized out>, frame=0x559ea181b470, state=0x7ffeb2318d70, instance_scale=1) at ../gsk/gpu/gskgpushaderop.c:133 #11 0x00007fa43c8e21d9 in gsk_gpu_op_gl_command (state=0x7ffeb2318d70, frame=0x559ea181b470, op=<optimized out>) at ../gsk/gpu/gskgpuop.c:49 #12 gsk_gpu_render_pass_op_gl_command (op=<optimized out>, frame=0x559ea181b470, state=0x7ffeb2318d70) at ../gsk/gpu/gskgpurenderpassop.c:189 #13 0x00007fa43c8cea7f in gsk_gpu_op_gl_command (state=0x7ffeb2318d70, frame=0x559ea181b470, op=0x7fa421aff010) at ../gsk/gpu/gskgpuop.c:49 #14 gsk_gl_frame_submit (frame=0x559ea181b470, vertex_buffer=<optimized out>, op=0x7fa421aff010) at ../gsk/gpu/gskglframe.c:162 #15 0x00007fa43c8e6c3b in gsk_gpu_frame_render (texture=0x0, viewport=0x7ffeb2318e10, node=0x559ea0d7ae10, region=0x559ea0279200, target=0x559ea1819920, timestamp=90730367859, self=0x559ea181b470) at ../gsk/gpu/gskgpuframe.c:624 #16 gsk_gpu_renderer_render (renderer=<optimized out>, root=0x559ea0d7ae10, region=<optimized out>) at ../gsk/gpu/gskgpurenderer.c:416 #17 0x00007fa43c8863a4 in gsk_renderer_render (renderer=<optimized out>, root=<optimized out>, region=<optimized out>) at ../gsk/gskrenderer.c:509 #18 0x00007fa43c692411 in gtk_widget_render (widget=0x559ea0fb80f0, surface=<optimized out>, region=0x559e9dd7c130) at ../gtk/gtkwidget.c:11971 #19 0x00007fa43c6932b5 in surface_render () at ../gtk/gtkwindow.c:4752 #20 0x00007fa43c7e1c64 in _gdk_marshal_BOOLEAN__BOXEDv (closure=0x559ea17f0da0, return_value=0x7ffeb23191f0, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x559e9e4fec30) at gdk/gdkmarshalers.c:130 #21 0x00007fa43d0c7861 in _g_closure_invoke_va (closure=0x559ea17f0da0, return_value=0x7ffeb23191f0, instance=0x559ea1754830, args=0x7ffeb23192f0, n_params=1, param_types=0x559e9e4fec30) at ../gobject/gclosure.c:897 #22 0x00007fa43d0dcd06 in signal_emit_valist_unlocked (instance=instance@entry=0x559ea1754830, signal_id=signal_id@entry=280, detail=detail@entry=0, var_args=var_args@entry=0x7ffeb23192f0) at ../gobject/gsignal.c:3415 #23 0x00007fa43d0e35c2 in g_signal_emit_valist (instance=0x559ea1754830, signal_id=280, detail=0, var_args=0x7ffeb23192f0) at ../gobject/gsignal.c:3254 #24 0x00007fa43d0e366f in g_signal_emit (instance=instance@entry=0x559ea1754830, signal_id=<optimized out>, detail=detail@entry=0) at ../gobject/gsignal.c:3574 #25 0x00007fa43c867ed2 in gdk_surface_paint_on_clock (clock=<optimized out>, data=0x559ea1754830) at ../gdk/gdksurface.c:1370 #26 gdk_surface_paint_on_clock (clock=<optimized out>, data=0x559ea1754830) at ../gdk/gdksurface.c:1346 #27 0x00007fa43d0c7861 in _g_closure_invoke_va (closure=0x559ea1755330, return_value=0x0, instance=0x559ea1755130, args=0x7ffeb2319680, n_params=0, param_types=0x0) at ../gobject/gclosure.c:897 #28 0x00007fa43d0dd9c4 in signal_emit_valist_unlocked (instance=instance@entry=0x559ea1755130, signal_id=signal_id@entry=289, detail=detail@entry=0, var_args=var_args@entry=0x7ffeb2319680) at ../gobject/gsignal.c:3415 #29 0x00007fa43d0e35c2 in g_signal_emit_valist (instance=0x559ea1755130, signal_id=289, detail=0, var_args=0x7ffeb2319680) at ../gobject/gsignal.c:3254 #30 0x00007fa43d0e366f in g_signal_emit (instance=instance@entry=0x559ea1755130, signal_id=<optimized out>, detail=detail@entry=0) at ../gobject/gsignal.c:3574 #31 0x00007fa43c84d32f in _gdk_frame_clock_emit_paint (frame_clock=0x559ea1755130) at ../gdk/gdkframeclock.c:712 #32 gdk_frame_clock_paint_idle (data=data@entry=0x559ea1755130) at ../gdk/gdkframeclockidle.c:634 #33 0x00007fa43cfc5114 in g_timeout_dispatch (source=0x559ea2373ae0, callback=0x7fa43c84ce10 <gdk_frame_clock_paint_idle>, user_data=0x559ea1755130) at ../glib/gmain.c:4989 #34 0x00007fa43cfc2700 in g_main_dispatch (context=0x559e9d9f60c0) at ../glib/gmain.c:3344 #35 g_main_context_dispatch_unlocked (context=context@entry=0x559e9d9f60c0) at ../glib/gmain.c:4152 #36 0x00007fa43cfc4348 in g_main_context_iterate_unlocked (context=context@entry=0x559e9d9f60c0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4217 #37 0x00007fa43cfc49fc in g_main_context_iteration (context=context@entry=0x559e9d9f60c0, may_block=may_block@entry=1) at ../glib/gmain.c:4282 #38 0x00007fa43d1fd8ed in g_application_run (application=0x559e9da3a210, argc=0, argv=<optimized out>) at ../gio/gapplication.c:2712 #39 0x0000559e9bfec93d in main (argc=<optimized out>, argv=<optimized out>) at ../src/server.cc:232 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1217299] New: zypp:plugins/zypper-changelog-plugin: Bug repodata is now using zstd compression
by bugzilla_noreply＠suse.com 06 May '24

06 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217299 Bug ID: 1217299 Summary: zypp:plugins/zypper-changelog-plugin: Bug repodata is now using zstd compression Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: zbalogh(a)suse.com Reporter: ianmepham(a)gmail.com QA Contact: screening-team-bugs(a)suse.de CC: nadvornik(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I'm running Tumbleweed x86_64, all up-to-date as of 18 Nov 2023 with snapshot 20231116. The package zypper-changelog-plugin I'm using is version 0.3-1.2. Recently zypper-changelog has stopped working with no error messages nor any other output given. I've tested both trying to download the changelog for a single package, such as with zypper-changelog --package vim, as well as the changelogs for any upcoming system updates with zypper-changelog ‐‐update I understand that the repodata is now compressed with zstd rather than gz as mentioned in the Factory mailing list here https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… I tested modifying zypper-changelog to accept both gz and zstd compressed repodata so it would work with both the official repos and any other repos which still use gz compression. Please keep in mind that I've only tested this in Tumbleweed. It also requires using zstdcat in place of zcat. Fortunately zstdcat also supports gz compression. The version of zstdcat I tested this with is 1.5.5-3.5. Here's a diff of the changes I've tested to give you an idea of what I mean comparing the current version 0.3-1.2 zypper-changelog and a modified test version: 147c147 < if file.endswith("primary.xml.gz"): --- > if file.endswith(("primary.xml.zst", "primary.xml.gz")): 172c172 < zcat_process = subprocess.Popen(["zcat", --- > zstdcat_process = subprocess.Popen(["zstdcat", 176c176 < stdout_value, stderr_value = zcat_process.communicate() --- > stdout_value, stderr_value = zstdcat_process.communicate() I understand that using a tuple is considered to be more pythonic, but I'm not sure if some may find it more legible to do something like this: if file.endswith("primary.xml.zst") or if file.endswith("primary.xml.gz"): I've not really done stuff like this before so my sincere apologies if I've picked the wrong option or made a mistake in this bug report. I'm also just an amateur with Python too so I may have easily overlooked something. Please ask if you need any more information. Thank you for your time and for such a useful tool. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217828] New: podman not using netavark as default
by bugzilla_noreply＠suse.com 06 May '24

06 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217828 Bug ID: 1217828 Summary: podman not using netavark as default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On Tumbleweed, despite being on podman 4.8.0 we are still using CNI instead of netavark as the default network backend https://openqa.opensuse.org/tests/3781263#step/podman/48 This issue was detected while extending the podman tests on Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213297] New: No clang-tools package needed by clang >=13 from PackageHub repo
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213297 Bug ID: 1213297 Summary: No clang-tools package needed by clang >=13 from PackageHub repo Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: oleksandr.shchirskyi(a)intel.com QA Contact: packagehub-bugs(a)suse.com Target Milestone: --- Found By: --- Blocker: No There is an issues with LLVM versions >=13 on SLES15 SP5. None of the Package Hub versions can be installed because the Clang-tool dependency is missing. For example, LLVM for SLES15 SP4 includes Clang-tool, but for SP5 it doesn't: https://packagehub.suse.com/packages/llvm13/ The same issue applies to LLVM 14. Here's a brief log example: # grep PRETTY /etc/os-release PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5" # zypper install clang14-devel Refreshing service 'Basesystem_Module_15_SP5_x86_64'. Refreshing service 'Desktop_Applications_Module_15_SP5_x86_64'. Refreshing service 'Development_Tools_Module_15_SP5_x86_64'. Refreshing service 'Legacy_Module_15_SP5_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Server_15_SP5_x86_64'. Refreshing service 'SUSE_Package_Hub_15_SP5_x86_64'. Refreshing service 'Server_Applications_Module_15_SP5_x86_64'. Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'clang-tools >= 14.0.6' needed by the to be installed clang14-devel-14.0.6-bp155.4.10.x86_64 Solution 1: do not install clang14-devel-14.0.6-bp155.4.10.x86_64 Solution 2: break clang14-devel-14.0.6-bp155.4.10.x86_64 by ignoring some of its dependencies # zypper info clang14-devel Refreshing service 'Basesystem_Module_15_SP5_x86_64'. Refreshing service 'Desktop_Applications_Module_15_SP5_x86_64'. Refreshing service 'Development_Tools_Module_15_SP5_x86_64'. Refreshing service 'Legacy_Module_15_SP5_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Server_15_SP5_x86_64'. Refreshing service 'SUSE_Package_Hub_15_SP5_x86_64'. Refreshing service 'Server_Applications_Module_15_SP5_x86_64'. Loading repository data... Reading installed packages... Information for package clang14-devel: -------------------------------------- Repository : SUSE-PackageHub-15-SP5-Backports-Pool Name : clang14-devel Version : 14.0.6-bp155.4.10 Arch : x86_64 Vendor : openSUSE Support Level : unknown Installed Size : 17.3 MiB Installed : No Status : not installed Source package : llvm14-14.0.6-bp155.4.10.src Upstream URL : https://www.llvm.org/ Summary : CLANG frontend for LLVM (devel package) Description : This package contains the clang (C language) frontend for LLVM. (development files) # zypper search clang | grep tools # At the same moment it's possible to install LLVM >=13 from OpenSUSE repos, for example, adding this to repos config "http://download.opensuse.org/distribution/leap/15.5/repo/oss/" -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217716] New: No bass, nonfunctional brightness keys on Lenovo Slim 7 16" AMD
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217716 Bug ID: 1217716 Summary: No bass, nonfunctional brightness keys on Lenovo Slim 7 16" AMD Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: variable_valuables761(a)simplelogin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- It seems the bass speakers do not work in the latest Tumbleweed KDE snapshot on the Lenovo Slim 7 16" AMD, 16ARH7, 82UX0001US (and this same model is called Yoga outside the United States). This issue appears to be similar to that of the wide range of recently released laptops that have the CS35L41 and TAS2781 amps, however I cannot find that hardware listed in any of my logs or online spec sheets for this laptop. The closest I can find is that is has a Realtek ALC3287 codec. Also, the keyboard brightness keys do not work. It seems the internal display's brightness value is bugged and shows up as a huge number in brightnessctl (and other tools) rather than something within the expected range. I can provide any logs that would be helpful. I hope this is an appropriate place to report these issues. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1217051] New: Enable ptrace_scope=1 by default on openSUSE Tumbleweed
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217051 Bug ID: 1217051 Summary: Enable ptrace_scope=1 by default on openSUSE Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: 95kreaninw95(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently, on openSUSE Tumbleweed, ptrace_scope is disabled by default (ptrace_scope=0). This makes Chromium sandboxing status showing as no and red colored for both Ptrace Protection with Yama LSM entries. Enabling ptrace_scope=1 this fixed the issue. And I think it's a security hardening for the system. There's a request to enable this feature on SUSE 15 SP4: https://bugzilla.suse.com/show_bug.cgi?id=1198601 I am requesting this on openSUSE Tumbleweed. For reference, ptrace_scope is enabled on Ubuntu since 10.10. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1213574] New: Thunderbird OAUTH2 broken
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213574 Bug ID: 1213574 Summary: Thunderbird OAUTH2 broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent Thunderbird updates broke OAUTH2 and this seems to be a common problem with Thunderbird 102. With this update it no longer presents an OAUTH2 dialog for IMAP. My employer uses Microsoft Office365 and OAUTH2 is essential. This used to work. Even with a clean install and nuking the previous configuration it will never prompt for OAUTH2 authentication like it used to. Note that the OAUTH2 dialog DOES work with SMTP, but not IMAP. Searching the Internet reveals that this is a common problem with this release. Please upgrade Thunderbird to a newer release for 15.4. I'm not quite ready to upgrade to 15.5 just yet since I use this machine for heavy development work. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1220190] New: AUDIT: drkonqi6
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1220190 Bug ID: 1220190 Summary: AUDIT: drkonqi6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- drkonqi is the crash handler for KDE applications. drkonqi6 will coexist in openSUSE for a while and needs to be reviewed: [ 93s] drkonqi6.x86_64: E: dbus-file-unauthorized (Badness: 10000) /usr/share/dbus-1/system.d/org.kde.drkonqi.conf (sha256 file digest default filter:233b3b98de2fc6b780c1eb9c3ab9b9f99b1949dfab951cababd7c5a717b8ee16 shell filter:233b3b98de2fc6b780c1eb9c3ab9b9f99b1949dfab951cababd7c5a717b8ee16 xml filter:3326c5271c6321c5b3a703d187443eef260d54aa7347bc8f05d9090a153a04bd) [ 93s] drkonqi6.x86_64: E: dbus-file-unauthorized (Badness: 10000) /usr/share/dbus-1/system-services/org.kde.drkonqi.service (sha256 file digest default filter:b99a6dc5943df0e641616dc4be3122fdd1d1b1c418df298c56008b50c5fb2b08 shell filter:b6f2a505903e2d8874d7da96a197944ab4a11f351f3db80ffeeec86d9eefd79a xml filter:<failed-to-calculate>) Package sources: https://build.opensuse.org/package/show/KDE:Frameworks/drkonqi6 -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1217260] New: slib build failed in %post
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217260 Bug ID: 1217260 Summary: slib build failed in %post Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello slib does not build on Leap 15.6. This should be fixed before Beta (Feb 2023). https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6 Build log from Leap 15.6 https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… [ 26s] ERROR: In procedure open-file: [ 26s] In procedure open-file: No such file or directory: "/usr/share/guile/site/2.2/slibcat" [ 26s] ... running 50-check-binary-kernel-log [ 26s] ... running 50-check-core-files [ 26s] ... checking for core files [ 26s] ... running 50-check-debuginfo [ 26s] ... testing for empty debuginfo packages [ 26s] ... running 50-check-filelist [ 26s] ... checking filelist [ 26s] ... running 50-check-gconf-scriptlets [ 26s] ... testing GConf scriptlet presence [ 26s] ... running 50-check-installtest [ 26s] ... testing for pre/postinstall scripts that are not idempotent [ 27s] Backtrace: [ 27s] 12 (apply-smob/1 #<catch-closure 5638290ba180>) [ 27s] In ice-9/boot-9.scm: [ 27s] 705:2 11 (call-with-prompt ("prompt") #<procedure 5638290d38c0 ?> ?) [ 27s] In ice-9/eval.scm: [ 27s] 619:8 10 (_ #(#(#<directory (guile-user) 563829187140>))) [ 27s] In ice-9/command-line.scm: [ 27s] 181:18 9 (_ #<input: string 563829192a80>) [ 27s] In unknown file: [ 27s] 8 (eval (require (quote new-catalog)) #<directory (guile-?>) [ 27s] In /usr/share/slib/require.scm: [ 27s] 145:16 7 (slib:require new-catalog) [ 27s] 79:15 6 (catalog:get new-catalog) [ 27s] In /usr/share/slib/guile-2.init: [ 27s] 257:4 5 (with-load-pathname _ _) [ 27s] In ice-9/boot-9.scm: [ 27s] 2312:4 4 (save-module-excursion #<procedure 563829261990 at ice-?>) [ 27s] 3832:12 3 (_) [ 27s] In /usr/share/slib/mklibcat.scm: [ 27s] 22:2 2 (_) [ 27s] In ice-9/ports.scm: [ 27s] 461:11 1 (call-with-output-file "/usr/share/guile/site/2.2/slib?" ?) [ 27s] In unknown file: [ 27s] 0 (open-file "/usr/share/guile/site/2.2/slibcat" "w" # #f) [ 27s] [ 27s] ERROR: In procedure open-file: [ 27s] In procedure open-file: No such file or directory: "/usr/share/guile/site/2.2/slibcat" [ 27s] postinstall script of slib-3b7-bp156.2.2.noarch.rpm failed -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213148] New: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213148 Bug ID: 1213148 Summary: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: catice567(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since kernel 6.2, my Tumbleweed refuses to boot because of intel isp. Ubuntu had this problem but they fixed it by disabling atomisp. I have a request to the openSUSE kernel maintainers: Can you please disable atomisp in your kernel, especially since this will affect Leap later on next year? -- You are receiving this mail because: You are on the CC list for the bug.

1 6