gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"]

This crash has the same stack trace characteristics as bug #1748450. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

StacktraceTop:
 _g_log_abort () from /tmp/apport_sandbox_ymge7ahu/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_default_handler () from /tmp/apport_sandbox_ymge7ahu/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 default_log_handler ()
 g_logv () from /tmp/apport_sandbox_ymge7ahu/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log () from /tmp/apport_sandbox_ymge7ahu/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0

Status changed to 'Confirmed' because the bug affects multiple users.

Also tracking in:
https://errors.ubuntu.com/problem/10051642bda6e2a9a27fe0b0d5f84f8b1f29438f

Disabling auto-hide of the dock seems to prevent this from happening.

This bug was fixed in the package mutter - 3.34.0-3ubuntu1

---------------
mutter (3.34.0-3ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
    + debian/control:
      - Update VCS flags to point to launchpad
      - Update maintainer to ubuntu
    + debian/gbp.conf: update branch to point to ubuntu/master
    + debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
      - X11: Add support for fractional scaling using Randr

mutter (3.34.0-3) experimental; urgency=medium

  * d/p/clutter-*: Cherry-pick from upstream to fix a crash. During
    animations, which was particularly bad when using Dash-to-Dock in
    auto-hide mode. (LP: #1841794)

 -- Iain Lane <email address hidden> Fri, 20 Sep 2019 16:32:18 +0100

The latest version of mutter in eoan is presently 3.34.0-1ubuntu1, so do we declare this unfixed?...

Weird. Now the page is correctly showing 3.34.0-3ubuntu1 is the latest.

https://launchpad.net/ubuntu/+source/mutter

I have a crash report which was uploaded with apport on 2019-12-22 08:38 EST. The UUID for the crash report is: 59c38b68-24c0-11ea-b1ac-fa163e983629

I am no expert, but it looks pretty similar to this report. Can someone glance at it to confirm if it is the same problem or another?

gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 is crashing on me every two days and one looses everything very often. Gnome becomes unstable and I need to reboot. Sometimes, I am thrown back to gdm but then cannot login anymore; only a reboot will fix this.

Hans,

Your crash report is not retraceable because "The following packages are missing debug symbols: libjpeg-turbo8 libnvidia-gl-435.". I see no evidence it is related to this bug.

Still, please keep submitting new crash reports, new bugs, as soon as you experience them.

Thanks Daniel. I installed the following packages:

libjpeg-turbo8-dbg/eoan,now 2.0.3-0ubuntu1 amd64 [installed]
libjpeg8-dbg/eoan,now 8c-2ubuntu8 amd64 [installed]

libnvidia-gl-435 does not have any debugging symbols package available. Next time it crashes, I will transmit a better report.

That said, I fail to understand how you determined that the libjpeg symbols are required. Searching through the crash report, I only see the following below. How, as a casual user, can I figure out which package I should install to provide a better debugging experience?

Thanks again.

$ fgrep libjpeg _usr_bin_gnome-shell.1000.crash
 libjpeg-turbo8 2.0.3-0ubuntu1
 libjpeg8 8c-2ubuntu8
 7f33dc2b5000-7f33dc2b9000 r--p 00000000 fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2
 7f33dc2b9000-7f33dc2fd000 r-xp 00004000 fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2
 7f33dc2fd000-7f33dc337000 r--p 00048000 fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2
 7f33dc337000-7f33dc338000 ---p 00082000 fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2
 7f33dc338000-7f33dc339000 r--p 00082000 fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2
 7f33dc339000-7f33dc33a000 rw-p 00083000 fd:01 58076797 /usr/lib/x86_64-linux-gnu/libjpeg.so.8.2.2

Hans,

This is again off-topic for this bug so shouldn't really be discussed here. But to answer your question your crash report is linked to a page where I got that info:

https://errors.ubuntu.com/bucket/?id=failed%3A/usr/bin/gnome-shell%3A5%3A/usr/lib/x86_64-linux-gnu/libc-2.30.so%2B213eb%3A/usr/bin/gnome-shell%2B152a%3A/usr/lib/x86_64-linux-gnu/libc-2.30.so%2B21470%3A/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1%2B3b8e5%3A/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1%2B3c969%3A/usr/bin/gnome-shell%2B15ee%3A/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1%2B3cb9c%3A/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1%2B3cd83%3A/usr/lib/libgjs.so.0.0.0%2B339e9%3A/usr/lib/libgjs.so.0.0.0%2B30d28%3A/usr/lib/libgjs.so.0.0.0%2B30e09%3A/usr/lib/x86_64-linux-gnu/libmozjs-60.so.0.0.0%2B7b41ef%3A/usr/lib/x86_64-linux-gnu/libmozjs-60.so.0.0.0%2B786974%3A/usr/lib/x86_64-linux-gnu/libmozjs-60.so.0.0.0%2B793dab%3A/usr/lib/x86_64-linux-gnu/libmozjs-60.so.0.0.0%2B7948fd

See LP: #1858414