Description of problem: Seems to have occurred on boot. Dunno what nautilus was doing. Version-Release number of selected component: nautilus-3.30.0-2.fc29 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_realloc executable: /usr/bin/nautilus journald_cursor: s=ad1754bd272b4cdab96f03ea3cb7e872;i=318c7;b=bda2afaab0844240a5f4cf9276c11363;m=3fa6746;t=5767add7870bf;x=a16d47fee07aad89 kernel: 4.18.9-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001
Created attachment 1486024 [details] File: backtrace
Created attachment 1486025 [details] File: cgroup
Created attachment 1486026 [details] File: core_backtrace
Created attachment 1486027 [details] File: cpuinfo
Created attachment 1486028 [details] File: dso_list
Created attachment 1486029 [details] File: environ
Created attachment 1486030 [details] File: exploitable
Created attachment 1486031 [details] File: limits
Created attachment 1486032 [details] File: maps
Created attachment 1486033 [details] File: mountinfo
Created attachment 1486034 [details] File: open_fds
Created attachment 1486035 [details] File: proc_pid_status
*** Bug 1645892 has been marked as a duplicate of this bug. ***
Similar problem has been detected: After leaving a Nautilus window open for a long time (hours), it crashed for seemingly no reason. The Nautilus-related packages I have installed are the following: evince-nautilus-3.30.2-1.fc29.x86_64 totem-nautilus-3.26.2-1.fc29.x86_64 gnome-terminal-nautilus-3.30.2-1.fc29.x86_64 file-roller-nautilus-3.30.1-1.fc29.x86_64 nautilus-python-1.2.2-2.fc29.x86_64 deja-dup-nautilus-38.0-3.fc29.x86_64 nautilus-extensions-3.30.3-1.fc29.x86_64 nautilus-sendto-3.8.6-3.fc29.x86_64 reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_realloc executable: /usr/bin/nautilus journald_cursor: s=b9c19a5dc68e4561a83de27a145b8ca3;i=32dc3;b=7bf99d9eac7d4c1fb393b555fca7e711;m=78e2f8277;t=57a5d8d965ffb;x=168c2716044a291b kernel: 4.18.17-300.fc29.x86_64 package: nautilus-3.30.3-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Booted computer, then searched for a file by entering the Overview and typing. No result was found after a few seconds, even though the file I was looking for does exist, so I assumed the search provider needed more startup time & I pressed Escape to try again later. Then, this crash report appeared. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_realloc executable: /usr/bin/nautilus journald_cursor: s=b9c19a5dc68e4561a83de27a145b8ca3;i=5e498;b=c1cb39b8bf434d66a121f90ae2409bdb;m=c3f62f6;t=57adfaa67a4d3;x=9f07a247aa266e06 kernel: 4.18.17-300.fc29.x86_64 package: nautilus-3.30.3-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Happened just after startup (turned on the PC, logged in and got the crash). I started the System Monitor, but I am not sure whether that was before or after the crash. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_realloc executable: /usr/bin/nautilus journald_cursor: s=ff944e9c0cf045879833dd994fdff1b3;i=b3edd;b=755a740fe676474abe563c60def980e7;m=bd1f708;t=57c34a013ad82;x=ee58d5847051c8e7 kernel: 4.19.5-300.fc29.x86_64 package: nautilus-3.30.4-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1664211 has been marked as a duplicate of this bug. ***
Similar problem has been detected: This is the second times Files has crashed on startup. It seems to happen the first time I try to start Files when I log in. When I try to start Files a second time, it does not crash and I can use it as expected. reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_realloc executable: /usr/bin/nautilus journald_cursor: s=2f5b94152c164c79befcdbd35bfed382;i=939daf;b=59c7b8793660466c8ff818c389c17d3a;m=fb4cb1a;t=57f2cc73f6662;x=9c787a02022fd7da kernel: 4.19.13-300.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1665787 has been marked as a duplicate of this bug. ***
*** Bug 1668015 has been marked as a duplicate of this bug. ***
Similar problem has been detected: This happened when logging in (after boot). reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_realloc executable: /usr/bin/nautilus journald_cursor: s=2dfd4bfd0b9c49e7bf8baeec3ec3ffc7;i=983c0c;b=0f90698b292c49a4937a0cf4c765ec43;m=836ff17;t=5819c960bb3f7;x=691ee04b11cda264 kernel: 4.18.16-200.fc28.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1001
*** Bug 1676444 has been marked as a duplicate of this bug. ***
*** Bug 1676641 has been marked as a duplicate of this bug. ***
*** Bug 1679828 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I opened LibreOffice Writter and received several error notifications (LibreOffice Write is working as expected though) reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_realloc executable: /usr/bin/nautilus journald_cursor: s=2da36e7925a34964bed4b4d94ec64675;i=4ac9f3;b=90c2db1a4a754dd8b34f9d32d861d250;m=3480aed5d;t=5830cb074228d;x=bbd54baaee0fff60 kernel: 4.20.11-200.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1689556 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Occured on startup reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_realloc executable: /usr/bin/nautilus journald_cursor: s=daa1ed7ec5164a679321c9faef960082;i=132889;b=0f93afb0aa6949fcaf658466db1ee3e5;m=c877250;t=584633b81f5a5;x=cfe7d6c366c88c3d kernel: 4.20.14-200.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1690887 has been marked as a duplicate of this bug. ***
*** Bug 1696125 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Nautilus broke after I started my system reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_realloc executable: /usr/bin/nautilus journald_cursor: s=5637a6dcc6f04c48826206a28e32fa9f;i=38338;b=69a6db8146f74326abd6d0116cb1b19c;m=23017313;t=58618cd319cc4;x=f4d2a744a51d8218 kernel: 5.0.6-200.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1965243530
*** Bug 1700635 has been marked as a duplicate of this bug. ***
*** Bug 1702794 has been marked as a duplicate of this bug. ***
Similar problem has been detected: This crash typically happens after typing a search term into the shell's Overview. It happens several times a day, and has been occuring for months now. Reinstalling Nautilus didn't get rid of the problem. reporter: libreport-2.10.0 backtrace_rating: 3 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_realloc executable: /usr/bin/nautilus journald_cursor: s=c228e1adbf734ffb85d748f6f7e66196;i=10958a;b=a1eae13395244b0a8c9a6e7d376539c8;m=4a0a100dd;t=58792b789f15e;x=d6170dd8105b7511 kernel: 5.0.9-200.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It happens on a regular basis (approx. once every 2 weeks) and the computer completely freeze. The only way to recover control is to swhich the computer down. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_realloc executable: /usr/bin/nautilus journald_cursor: s=4f0ba24abfc6449dac1bfa5669068318;i=b373;b=45a2766968f34c339bfdb4e71a0fd286;m=6605f0487;t=5853db7294d90;x=2fd023642039670 kernel: 5.0.3-200.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1570160 [details] valgrind errors Hi Since realloc() is crashing, I arranged for nautilus to run under valgrind. I found a couple of different valgrind errors. I don't know how to reproduce them, I'm not even sure they are related, but I guess they might be worth a look. I suppose it's interesting to consider the negative result as well. I.e. I've been having these realloc() crashes, other people have still been having them recently - but valgrind is not finding an invalid value passed to realloc() specifically. Maybe it points towards nautilus corrupting the heap with some invalid writes. (Also, when running nautilus under valgrind, it seems like it is not crashing :-). e.g. May 15 14:43:56 alan-laptop dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.gnome.Nautilus' May 15 14:44:08 alan-laptop org.gnome.Nautilus[1748]: ==3457== Thread 8: May 15 14:44:08 alan-laptop org.gnome.Nautilus[1748]: ==3457== Invalid write of size 4 May 15 14:44:08 alan-laptop org.gnome.Nautilus[1748]: ==3457== at 0x1A7AEC: search_add_hits_idle.part.5 (nautilus-search-engine-recent.c:134) May 15 14:44:08 alan-laptop org.gnome.Nautilus[1748]: ==3457== by 0x1A8214: search_add_hits_idle (glib-autocleanups.h:45) May 15 14:44:08 alan-laptop org.gnome.Nautilus[1748]: ==3457== by 0x1A8214: recent_thread_func (nautilus-search-engine-recent.c:317) May 15 14:44:08 alan-laptop org.gnome.Nautilus[1748]: ==3457== by 0x48FE2A9: g_thread_proxy (gthread.c:784) May 15 14:44:08 alan-laptop org.gnome.Nautilus[1748]: ==3457== by 0x585158D: start_thread (pthread_create.c:486) May 15 14:44:08 alan-laptop org.gnome.Nautilus[1748]: ==3457== by 0x5968682: clone (clone.S:95) May 15 14:44:08 alan-laptop org.gnome.Nautilus[1748]: ==3457== Address 0xd3931b0 is 48 bytes inside a block of size 56 free'd ...
*** Bug 1715912 has been marked as a duplicate of this bug. ***
*** Bug 1727252 has been marked as a duplicate of this bug. ***
*** Bug 1749080 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.