https://bugzilla.suse.com/show_bug.cgi?id=1219970 https://bugzilla.suse.com/show_bug.cgi?id=1219970#c5 Vasilis Liaskovitis <vliaskovitis@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vliaskovitis@suse.com --- Comment #5 from Vasilis Liaskovitis <vliaskovitis@suse.com> --- Created attachment 873039 --> https://bugzilla.suse.com/attachment.cgi?id=873039&action=edit coredump from gnome-shell-45.3-2.2.x86_64 I am attaching a compressed gnome-shell coredump from my Tumbleweed (out-of-date) with gnome-shell-45.3-2.2. The coredump was produced a few weeks ago with the original steps to reproduce in comment#0. According to comment#0 the steps are not longer valid. I have not reproduced another way yet. From the backtrace it looks like an issue with sqlite3 memory allocation. gdb /usr/bin/gnome-shell core.gnome-shell.1000.12b034247d384e09b0b3637d9224839e.21523.1708076809000000 (gdb) bt #0 0x0000000000000000 in () #1 0x00007f8aa802f674 in mallocWithAlarm (pp=<synthetic pointer>, n=824) at /usr/src/debug/sqlite-src-3440200/sqlite3.c:30055 #2 sqlite3Malloc (n=824) at /usr/src/debug/sqlite-src-3440200/sqlite3.c:30120 #3 sqlite3Malloc (n=824) at /usr/src/debug/sqlite-src-3440200/sqlite3.c:30114 #4 0x00007f8aa80e334b in sqlite3MallocZero (n=824) at /usr/src/debug/sqlite-src-3440200/sqlite3.c:30399 #5 openDatabase (zFilename=0x7f8ae8001d70 "/home/vliaskovitis/.local/share/gnome-shell/extensions/emoji-copy@felipeftn/data/emojis.db", ppDb=0x7f8ae8001030, flags=<optimized out>, zVfs=0x0) at /usr/src/debug/sqlite-src-3440200/sqlite3.c:49832 #6 0x00007f8a52a41b7d in gda_sqlite_provider_open_connection (provider=0x5604a75609d0 [GdaSqliteProvider], cnc=0x5604a71f6f20 [GdaConnection], params=<optimized out>, auth=<optimized out>) at ../libgda/sqlite/gda-sqlite-provider.c:1216 #7 0x00007f8a52a0c975 in worker_open_connection (data=0x5604a73ac2d0, error=0x5604a70a6ca8) at ../libgda/gda-server-provider.c:2097 #8 0x00007f8a52a6ab85 in worker_thread_main (worker=0x5604aa579050) at ../libgda/thread-wrapper/gda-worker.c:213 #9 0x00007f8b092f148e in g_thread_proxy (data=0x5604a8165680) at ../glib/gthread.c:831 #10 0x00007f8b0888ff44 in start_thread () at /lib64/libc.so.6 #11 0x00007f8b089184cc in clone3 () at /lib64/libc.so.6 In any case libgda should be able to handle the error, without crashing the whole desktop. I think this is likely the same bug as GNOME/libgda upstream issue: https://gitlab.gnome.org/GNOME/libgda/-/issues/267 Discussion and core analysis should probably be continued there, as it looks like this is an unsolved upstream issue, not only affecting downstream. -- You are receiving this mail because: You are on the CC list for the bug.