Bug#885859: libglib-2.0: cinnamon crash libglib-2.0.so.0.5400.2

[Simon McVittie]

Control: reassign -1 cinnamon
Control: tags -1 + moreinfo

On Sat, 30 Dec 2017 at 14:25:34 +0000, bumaw at wp.pl wrote:
> [  962.017447] traps: cinnamon[30326] trap int3 ip:7fbb868b5951 sp:7ffdb1a697a0 error:0 in libglib-2.0.so.0.5400.2[7fbb86865000+111000]

Sorry, there is not enough information here to solve a crash, or even to
know which package is responsible for the crash. It might be a bug in
libglib-2.0.so.0, or it might be application code or another library
in the cinnamon process passing bad data into libglib-2.0.so.0; we
can't tell.

If you can get more information, and you are not sure which package has
the bug, it is usually best to report crashes as a bug in whatever
program crashed (in this case cinnamon). That way, the bug report will
include all applicable package versions, and the maintainer of the
crashing program can reassign the bug report to a library if there is
evidence that the crash is a bug in that library.

Because you're using systemd, one very convenient way to get more
information is to install the systemd-coredump and gdb packages, and
make the crash happen again. Also install the -dbgsym packages
for libglib2.0, cinnamon, and any other libraries that seem relevant
(please see <https://wiki.debian.org/HowToGetABacktrace> for more
details).

Then you'll be able to use the command "coredumpctl" to list crash dumps,
and "coredumpctl gdb" to load the most recent crash dump into gdb, or
a command like "coredumpctl gdb 12345" to load an older crash dump with
process ID 12345.

To get a backtrace in gdb, use the commands "set pagination
off" and "thread apply all bt" at the (gdb) prompt: see
<https://wiki.debian.org/HowToGetABacktrace> for more details.The cinnamon
maintainers will need this information to be able to do anything about
this bug.

The output of "reportbug --template cinnamon" would also be very useful:
that will include a lot more version numbers than were in this bug report.

Cinnamon maintainers: please could you take over triaging this, and
reassign back to GLib if it turns out to be our bug? Thanks!

Regards,
    smcv