Description of problem: I started up an instance. Version-Release number of selected component: emacs-1:28.2-4.fc38 Additional info: reporter: libreport-2.17.9 cmdline: emacs tools/rockboxdev.sh type: CCpp cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-kitty-63506.scope runlevel: N 5 package: emacs-1:28.2-4.fc38 journald_cursor: s=4b4e9570774c43efacdbf61ff62ab96f;i=2d8a5;b=ec984f5e1d294734bc4a03d3d6404fa3;m=b54a1e903;t=5f9cf0b61f88e;x=7d14087f828579d9 executable: /usr/bin/emacs-28.2 rootdir: / kernel: 6.2.11-300.fc38.x86_64 reason: emacs-28.2 killed by SIGSEGV backtrace_rating: 4 comment: I started up an instance. crash_function: handle_fatal_signal uid: 1000 Truncated backtrace: Thread no. 1 (2 frames) #4 handle_fatal_signal at ../../src/sysdep.c:1762 #5 deliver_thread_signal.constprop.0 at ../../src/sysdep.c:1754
Created attachment 1958865 [details] File: maps
Created attachment 1958866 [details] File: open_fds
Created attachment 1958867 [details] File: environ
Created attachment 1958868 [details] File: dso_list
Created attachment 1958869 [details] File: cpuinfo
Created attachment 1958870 [details] File: limits
Created attachment 1958871 [details] File: os_info
Created attachment 1958872 [details] File: proc_pid_status
Created attachment 1958873 [details] File: backtrace
Created attachment 1958874 [details] File: core_backtrace
Created attachment 1958875 [details] File: mountinfo
After upgrading to Fedora 38, with emacs 28.2-4, on x86_64, emacs seg faults for me on startup. I doesn't happen every time. I moved my .emacs and .emacs.d/ out of the way, that didn't solve the problem. A stack trace is below. Is this related to this bug? $ emacs Fatal error 11: Segmentation fault Backtrace: emacs(emacs_backtrace+0x5c)[0x5889dc] emacs(terminate_due_to_signal+0xa1)[0x46533c] emacs[0x465cc6] emacs[0x6ae2b4] /lib64/libc.so.6(+0x3dba0)[0x7fe8c665eba0] /lib64/libcairo.so.2(+0x59c8c)[0x7fe8cee80c8c] /lib64/libcairo.so.2(+0xa8144)[0x7fe8ceecf144] /lib64/libcairo.so.2(+0x64127)[0x7fe8cee8b127] /lib64/libcairo.so.2(+0x70099)[0x7fe8cee97099] /lib64/libcairo.so.2(+0x720e9)[0x7fe8cee990e9] /lib64/libcairo.so.2(+0x2be9a)[0x7fe8cee52e9a] /lib64/libcairo.so.2(cairo_show_glyphs+0x2e)[0x7fe8ceea745e] emacs[0x68c1cd] emacs[0x539ac2] emacs[0x53c0b4] emacs[0x4c0f14] emacs(gui_write_glyphs+0x9c)[0x4ccc9c] emacs[0x4757a6] emacs[0x47caac] emacs[0x47d824] emacs(update_frame+0x1ed)[0x47e4cd] emacs[0x4aca1f] emacs(message3_nolog+0xf6)[0x4a2a86] emacs(message3+0x308)[0x4a2f18] emacs(Fmessage+0x46)[0x5fa976] /usr/bin/../lib64/emacs/28.2/native-lisp/28.2-a66ed3a6/preloaded/mule-3352613d-82b9a969.eln(F6c6f61642d776974682d636f64652d636f6e76657273696f6e_load_with_code_conversion_0+0x31b)[0x7fe8bf7cb51b] emacs(Ffuncall+0x221)[0x603971] emacs(Fload+0x3f9)[0x6305c9] emacs(Ffuncall+0x221)[0x603971] emacs[0x609b15] emacs(Fmapc+0x55)[0x609db5] emacs(eval_sub+0x5c8)[0x602d78] emacs[0x63001b] emacs(Feval_buffer+0x17a)[0x63143a] /usr/bin/../lib64/emacs/28.2/native-lisp/28.2-a66ed3a6/preloaded/mule-3352613d-82b9a969.eln(F6c6f61642d776974682d636f64652d636f6e76657273696f6e_load_with_code_conversion_0+0x27b)[0x7fe8bf7cb47b] emacs(Ffuncall+0x221)[0x603971] emacs(Fload+0x3f9)[0x6305c9] emacs(Ffuncall+0x221)[0x603971] /usr/bin/../lib64/emacs/28.2/native-lisp/28.2-a66ed3a6/preloaded/startup-bbc6ea72-9c04c94d.eln(F636f6d6d616e642d6c696e65_command_line_0+0x1436)[0x7fe8bf75fca6] emacs(Ffuncall+0x221)[0x603971] /usr/bin/../lib64/emacs/28.2/native-lisp/28.2-a66ed3a6/preloaded/startup-bbc6ea72-9c04c94d.eln(F6e6f726d616c2d746f702d6c6576656c_normal_top_level_0+0xf6d)[0x7fe8bf75c38d] ... Segmentation fault (core dumped)
That scenario matches mine; I've had it crash twice on me now at startup, in a system that I'd recently upgraded from F37. I've also had gnome-shell crash on me multiple times so presumably not all is quite well in the house of F38?
Fired up emacs from commandline and also tried via desktop launch in KDE. I think this is the first time I've used emacs since upgrading to Fedora 38 last week. It works ok in the terminal (i.e. emacs -nw). reporter: libreport-2.17.9 type: CCpp reason: emacs-28.2 killed by SIGSEGV journald_cursor: s=55a1de8d268a4c3c96a8ea826b2fafe2;i=13da47;b=4d99a8d8f44a48649ca1754a1e46510c;m=2ea17ce7d;t=5fa12ff4c91a3;x=3c3405c3f47d97cb executable: /usr/bin/emacs-28.2 cmdline: emacs build/partitioned.trig cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.konsole-37617251a4cf48fcb51cf6ddf3827dd1.scope rootdir: / uid: 1000 kernel: 6.2.11-300.fc38.x86_64 package: emacs-1:28.2-4.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: handle_fatal_signal
Same with both Wayland and Xorg. If I try "emacs --no-site-lisp" then it works. Also the next time I run "emacs", it works. The following time it crashes again.
I started emacs from the terminal. Here's the first few lines of the output: Backtrace: emacs(emacs_backtrace+0x5c)[0x5889dc] emacs(terminate_due_to_signal+0xa1)[0x46533c] emacs[0x465cc6] emacs[0x6ae2b4] /lib64/libc.so.6(+0x3db70)[0x7fd3cec5fb70] /lib64/libcairo.so.2(+0x59c8c)[0x7fd3d74c5c8c] /lib64/libcairo.so.2(+0xa8144)[0x7fd3d7514144] /lib64/libcairo.so.2(+0x64127)[0x7fd3d74d0127] /lib64/libcairo.so.2(+0x70099)[0x7fd3d74dc099] /lib64/libcairo.so.2(+0x720e9)[0x7fd3d74de0e9] /lib64/libcairo.so.2(+0x2be9a)[0x7fd3d7497e9a] /lib64/libcairo.so.2(cairo_show_glyphs+0x2e)[0x7fd3d74ec45e] emacs[0x68c1cd] Note that emacs started correctly a few minutes later while this bug report was being generated. This did not happen in F37. I've only seen this with the new upgrade to F38. reporter: libreport-2.17.9 type: CCpp reason: emacs-28.2 killed by SIGSEGV journald_cursor: s=717dc1674d7240edb922523c198e0044;i=17b4bf;b=7032d2758142486f8a3b5aa461a4ea86;m=11fc8e3229;t=5facf43a11a8f;x=89c80c51d1ab1882 executable: /usr/bin/emacs-28.2 cmdline: emacs /home/mbass/dat/brewery/run230426/journal.txt cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-22fcaf16-aaee-4611-aa8d-a48b39074412.scope rootdir: / uid: 1000 kernel: 6.2.13-300.fc38.x86_64 package: emacs-1:28.2-4.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: handle_fatal_signal
Not sure, I was using emacs to read a sizable text log file (with "-nw", occasionally), and stopping and starting again, may have tried clicking on 'disable showing native compile log warnings' too in the alternate window, and emacs crashed in one of the middle sessions. relaunch afterward is fine. reporter: libreport-2.17.9 executable: /usr/bin/emacs-28.2 rootdir: / kernel: 6.2.14-300.fc38.x86_64 journald_cursor: s=4dd5b893754a48a396c4413e625573fc;i=2c558;b=f0ed22e081024d6f991ed6a668791908;m=3662206414;t=5fb22f799a79e;x=266a50ce1d3033cb cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-bbd179d0-e4f2-4753-aa15-434c3e99e179.scope runlevel: N 5 uid: 0 dso_list: /usr/bin/emacs-28.2 emacs-1:28.2-4.fc38.x86_64 (Fedora Project) 1682916293 backtrace_rating: 4 cmdline: emacs f35-f36-upgrade-try1 type: CCpp reason: emacs-28.2 killed by SIGSEGV package: emacs-1:28.2-4.fc38 crash_function: handle_fatal_signal
emacs launched by "git cherry-pick --continue" (I have "git config core.editor emacs"). reporter: libreport-2.17.9 executable: /usr/bin/emacs-28.2 rootdir: / kernel: 6.2.14-300.fc38.x86_64 journald_cursor: s=15e22ab40381453db1322b6a626f8d6b;i=2db90;b=f0ed22e081024d6f991ed6a668791908;m=5de1403c9b;t=5fb4a76b98026;x=47efa2a70d16baf4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-4fc446a8-7fdf-401d-a0c5-2422791673fb.scope runlevel: N 5 uid: 1000 backtrace_rating: 4 cmdline: /usr/bin/emacs /home/Hin-Tak/git-others/ghostpdl-trunk/.git/COMMIT_EDITMSG type: CCpp reason: emacs-28.2 killed by SIGSEGV package: emacs-1:28.2-4.fc38 comment: emacs launched by "git cherry-pick --continue" (I have "git config core.editor emacs"). crash_function: handle_fatal_signal
I have reported this issue in Cairo. https://gitlab.freedesktop.org/cairo/cairo/-/issues/778
This could be a possible duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2182529. In case anyone in here can reproduce the crash, can you please try using a different font, more specifically one that is neither SVG nor COLRv1?
Another kind of backtrace from plain `emacs -q`. MATE Desktop(xorg) On my machine, `emacs -q` dies once every 7~10 times. reporter: libreport-2.17.9 type: CCpp reason: emacs-28.2 killed by SIGSEGV journald_cursor: s=f3e386bc22bf4d268ef4a28553da8d9a;i=447be8;b=90f52628ac434c099bfd255dd4ee31f3;m=13e306c6e;t=5fb80089e5761;x=48d707fd477b8008 executable: /usr/bin/emacs-28.2 cmdline: emacs -q cgroup: 0::/user.slice/user-1002.slice/session-8.scope rootdir: / uid: 1002 kernel: 6.2.14-300.fc38.x86_64 package: emacs-1:28.2-4.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: handle_fatal_signal
Emacs crashed on start-up. reporter: libreport-2.17.9 type: CCpp reason: emacs-28.2 killed by SIGSEGV journald_cursor: s=567ea76ef93a4791a07ec13e3ab4d49b;i=82dfd;b=eab1465ddf2f4132b4dc452458eea166;m=467a2c417;t=5fb82c701d42c;x=9139035c57ecc649 executable: /usr/bin/emacs-28.2 cmdline: /usr/bin/emacs cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-emacs-6ae35d30552b48a38fcbe02f4603e8b7.scope rootdir: / uid: 1000 kernel: 6.2.14-300.fc38.x86_64 package: emacs-1:28.2-4.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: handle_fatal_signal comment: Emacs crashed on start-up.
Hi! The patch from Cairo https://gitlab.freedesktop.org/cairo/cairo/-/commit/10cc34f521cf272f881bbad9a6fc4e794cca8687 solved this random startup death completely! (I rebuilt cairo-1.17.8-3 rpm with the above patch only). I ran `emacs -q` 5350 times with patched cairo successfully. No segv occurred. ``` while true; do; emacs -q --eval '(server-start)' &; sleep 3; emacsclient --eval '(save-buffers-kill-emacs)' || echo "FAILED"; sleep 0.5; done ``` (In reply to hkoba from comment #21) > Another kind of backtrace from plain `emacs -q`. MATE Desktop(xorg) > On my machine, `emacs -q` dies once every 7~10 times. >
Emacs sometimes crashes on start-up. reporter: libreport-2.17.10 type: CCpp reason: emacs-28.2 killed by SIGSEGV journald_cursor: s=567ea76ef93a4791a07ec13e3ab4d49b;i=8cc57;b=2b7d8097acb04deebdc9184040703d84;m=589763725;t=5fbc32e540df0;x=e8d8ec2fbf820a57 executable: /usr/bin/emacs-28.2 cmdline: /usr/bin/emacs cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-emacs-b1f611a1a1fc4a52be49d4b1b9bd6b4d.scope rootdir: / uid: 1000 kernel: 6.2.15-300.fc38.x86_64 package: emacs-1:28.2-4.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: handle_fatal_signal comment: Emacs sometimes crashes on start-up.
*** This bug has been marked as a duplicate of bug 2189228 ***