[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#934105: xfdesktop4: xfdesktop crashes and coredump when upgrading

Hello Jiang Jun,
I just tried to reproduce the crash. Unfortunately it
did not happen in a minimal VM.

This package google-chrome-stable is from a third-party repository?

Therefore you might be able to have a look at the
output of "coredumpctl list".
There should be a line for the crash with pid 5159.
Then you could just use "coredumpctl gdb 5159" to
enter gdb with the recorded core and issue these commands

If you could install the following dbgsym packages before
like described in [1] could be very helpful.
    apt install xfdesktop4-dbgsym libglib2.0-0-dbgsym libgtk2.0-0-dbgsym libwnck22-dbgsym

With such packages installed the output in journalctl
should also offer some more information already.

If you have rebooted since then coredumpctl might not
show cores from the previous boots.
But you can have a look into /var/lib/systemd/coredump.

    unlz4 -k /var/lib/systemd/coredump/core.xfdesktop.0.00000000000000000000000000000000.5159.0000000000000000.lz4 /tmp/core.xfdesktop
    gdb -q /usr/bin/xfdesktop --core /tmp/core.xfdesktop

And then forward that output to this bug.
And maybe copy the core....lz4 to a safe place or it will
get deleted automatically soon, if the maintainer have
some more questions about it.

Nevertheless, I expect that the top frames
should look something like this:

    (gdb) bt
    #0  0x00007f053483a75a in magazine_chain_pop_head () at ../../../glib/gslice.c:538
    #1  thread_memory_magazine1_alloc () at ../../../glib/gslice.c:841
    #2  g_slice_alloc () at ../../../glib/gslice.c:1015
    #3  0x00007f0534818316 in g_list_prepend () at ../../../glib/glist.c:314
    #4  0x00007f05356e2b87 in update_client_list () at screen.c:1637
    #5  do_update_now () at screen.c:2332
    #6  0x00007f05356e3b44 in update_idle () at screen.c:2355
    #7  0x00007f053481c898 in g_main_dispatch () at ../../../glib/gmain.c:3189

These frames can be reached when changing display resolution.
Does the crash appear also if you manually the resolution?

Kind regards,

[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

Reply to: