Bug? "Segmentation fault" and core dumps for multiple applications

Hi everyone, since today, I obtain multiple core dumps on a regular base from multiple applications. (the last software upgrade has been done a couple of days ago).

Running coredumpctl debug makes gdb display these information:

Core was generated by `/usr/lib/xfce4/panel/wrapper-2.0 /usr/lib/xfce4/panel/plugins/libwhiskermenu.so 8 14680071 whiskermenu Whisker\ Menu Show\ a\ menu\ to\ easily\ access\ installed\ applications'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  gtk_im_multicontext_set_slave (multicontext=0x640b8cf4ea00, slave=0x0, finalizing=0) at ../gtk/gtk/gtkimmulticontext.c:177

The stack trace is (the top lines are the same for every affected application, so I may safely assume the same root cause :wink: ):

#0  gtk_im_multicontext_set_slave (multicontext=0x640b8cf4ea00, slave=0x0, finalizing=0) at ../gtk/gtk/gtkimmulticontext.c:177
#1  0x00007d762882e82a in g_closure_invoke (closure=0x640b8d170600, return_value=0x0, n_param_values=2, param_values=0x7ffe92926120, invocation_hint=0x7ffe92926070)
    at ../glib/gobject/gclosure.c:833
#2  0x00007d762885f565 in signal_emit_unlocked_R.isra.0 (node=node@entry=0x7ffe92926230, detail=detail@entry=650, instance=instance@entry=0x640b8cf34ea0, 
    emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffe92926120) at ../glib/gobject/gsignal.c:3887
#3  0x00007d762884fca9 in signal_emit_valist_unlocked (instance=instance@entry=0x640b8cf34ea0, signal_id=signal_id@entry=1, detail=detail@entry=650, var_args=var_args@entry=0x7ffe929263a0)
    at ../glib/gobject/gsignal.c:3519
#4  0x00007d762884ff32 in g_signal_emit_valist (instance=0x640b8cf34ea0, signal_id=1, detail=650, var_args=var_args@entry=0x7ffe929263a0) at ../glib/gobject/gsignal.c:3262
#5  0x00007d762884fff4 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at ../glib/gobject/gsignal.c:3582
#6  0x00007d762883ad16 in g_object_dispatch_properties_changed (object=0x640b8cf34ea0, n_pspecs=<optimized out>, pspecs=<optimized out>) at ../glib/gobject/gobject.c:1819
#7  0x00007d762883e544 in g_object_notify_by_spec_internal (object=0x640b8cf34ea0, pspec=0x640b8cf4ea00) at ../glib/gobject/gobject.c:1924
#8  g_object_notify_by_pspec (object=0x640b8cf34ea0, pspec=0x640b8cf4ea00) at ../glib/gobject/gobject.c:2030
#9  0x00007d7627f3a457 in _gdk_event_emit (event=0x640b8d210750) at ../gtk/gdk/gdkevents.c:73
#10 _gdk_event_emit (event=0x640b8d210750) at ../gtk/gdk/gdkevents.c:67
#11 0x00007d7627f96b40 in gdk_event_source_dispatch.lto_priv () at ../gtk/gdk/x11/gdkeventsource.c:354
#12 0x00007d7627c51559 in g_main_dispatch (context=0x640b8cf05e90) at ../glib/glib/gmain.c:3357
#13 0x00007d7627cb4257 in g_main_context_dispatch_unlocked (context=0x640b8cf05e90) at ../glib/glib/gmain.c:4208
#14 g_main_context_iterate_unlocked.isra.0 (context=0x640b8cf05e90, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4273
#15 0x00007d7627c52287 in g_main_loop_run (loop=0x640b8d20fba0) at ../glib/glib/gmain.c:4475
#16 0x00007d76281e4d7f in gtk_main () at ../gtk/gtk/gtkmain.c:1329
#17 0x0000640b5580e2b1 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/xfce4-panel/xfce4-panel/wrapper/main.c:362

Am I the only one to face this issue? What may I try to get out of this situation?

Thanks!

Matthias

Hi, the first thing I’d check is disk integrity. I’d do a full fsck on at least the / partition, booted from a Live USB. I’d suspect an issue with e.g. bad sectors, especially if the disk has some “vintage”.

Also worth looking at the SMART test results. You might need to install smartmontools for this.

It might also be worth taking a look at:

Hope this helps!

1 Like

Or the RAM might be defective.

Can you try to remove and reinstall the RAM modules ?

2 Likes

There was similar issues reported on testing branch. After we downgraded the packages to 26th of January it was fine again. Most likely the gtk3 update in unstable branch might be the reason.

3 Likes

Maybe remove, check and reinstall the CPU.

Memory dump is always related to memory.

A direct link to the Testing branch post by @philm:

Regards.

1 Like

Apparently, downgrading the packages solved the issue. Thank you for your support! I should have opened the Testing Update thread first :wink:

1 Like