Description of problem: I was copying files to an usb disk by drag and dropping between 2 tabs within Nautilus. Version-Release number of selected component: nautilus-3.30.1-1.fc29 Additional info: reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: stop_cache_selection_list executable: /usr/bin/nautilus journald_cursor: s=c1628fbed72546a0a3b3aa5219ff0229;i=270b0;b=dc4ccbc208ad4b4da3072a75b185bf22;m=c997063b;t=5780670bc115a;x=35ab836a647c64aa kernel: 4.18.13-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 stop_cache_selection_list at ../src/nautilus-canvas-dnd.c:375 #1 nautilus_canvas_container_receive_dropped_icons at ../src/nautilus-canvas-dnd.c:1064 #2 drag_data_received_callback at ../src/nautilus-canvas-dnd.c:1673 #3 _gtk_marshal_VOID__OBJECT_INT_INT_BOXED_UINT_UINT at gtkmarshalers.c:5470 #7 g_signal_emit_by_name at gsignal.c:3487 #8 gtk_drag_selection_received at gtkdnd.c:1180 #12 g_signal_emit_by_name at gsignal.c:3487 #13 gtk_selection_retrieval_report at gtkselection.c:3049 #14 gtk_selection_convert at gtkselection.c:1161 #15 gtk_drag_get_data at gtkdnd.c:900 Potential duplicate: bug 1529864
Created attachment 1493262 [details] File: backtrace
Created attachment 1493263 [details] File: cgroup
Created attachment 1493264 [details] File: core_backtrace
Created attachment 1493265 [details] File: cpuinfo
Created attachment 1493266 [details] File: dso_list
Created attachment 1493267 [details] File: environ
Created attachment 1493268 [details] File: exploitable
Created attachment 1493269 [details] File: limits
Created attachment 1493270 [details] File: maps
Created attachment 1493271 [details] File: mountinfo
Created attachment 1493272 [details] File: open_fds
Created attachment 1493273 [details] File: proc_pid_status
Created attachment 1493274 [details] File: var_log_messages
Similar problem has been detected: Happened when trying to move a folder into another folder. The sidebar "New bookmark" option was visible the whole time reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: stop_cache_selection_list executable: /usr/bin/nautilus journald_cursor: s=ff8abb134ecb4a92b26a4fe502eccb9e;i=756c4;b=3aa3161b6c224143be8d2c70b8a90bdc;m=1234795b4;t=579ed6d5eeb6f;x=5fb374dc54dec809 kernel: 4.18.16-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: 1. Select files in Nautilus (icon list). 2. Drag them to a folder. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: stop_cache_selection_list executable: /usr/bin/nautilus journald_cursor: s=385496cccf0b45c296eb63cce09e6d50;i=866e;b=e7b5fd3558c8490582187b857375bfdd;m=8c3eaf5c8;t=57a5185c904ce;x=363a3fe6de4383f kernel: 4.18.16-300.fc29.x86_64 package: nautilus-3.30.3-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1649953 has been marked as a duplicate of this bug. ***
Similar problem has been detected: 1. I had nautilus open 2. from the terminal I disabled the experimental views via gsettings: gsettings set org.gnome.nautilus.preferences use-experimental-views false 3. nautilus briefly restarted the open windows and then crashed reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: stop_cache_selection_list executable: /usr/bin/nautilus journald_cursor: s=22303bb7202a4f00b83b4376aa891207;i=558281;b=fbe15c933d79460090c30a53151967b9;m=69b79a3c;t=57c4e599d8a8a;x=1c8b7c33976501b4 kernel: 4.19.4-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 1657456 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Booted, logged in, got this abrt notice reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: stop_cache_selection_list executable: /usr/bin/nautilus journald_cursor: s=315c3364607a48b2a9be42104b21ba42;i=48dafb;b=68adb0c6c5eb4a229bbb6811e46bee40;m=4d7bf0c2d;t=57cb32c0f0aa3;x=7ee34f9bef1e0090 kernel: 4.19.6-300.fc29.x86_64 package: nautilus-3.30.4-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1001
*** Bug 1661789 has been marked as a duplicate of this bug. ***
*** Bug 1670130 has been marked as a duplicate of this bug. ***
*** Bug 1670219 has been marked as a duplicate of this bug. ***
*** Bug 1671021 has been marked as a duplicate of this bug. ***
*** Bug 1672463 has been marked as a duplicate of this bug. ***
Similar problem has been detected: While extracting a .tar.bz2 archive and performing other normal actions, (e.g. copying, renaming) Nautilus crashed. reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: stop_cache_selection_list executable: /usr/bin/nautilus journald_cursor: s=0cb130c94d6845a0b3923241b7864449;i=1d9ef;b=064b7aefb7694fb0a252c85de48a72e1;m=56db49eb;t=5814fac6484df;x=a02f08d0faa4edf kernel: 4.20.6-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 1673709 has been marked as a duplicate of this bug. ***
*** Bug 1674098 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Trying to install yabasic-2.81.4-1.x86_64.rpm (source: http://www.yabasic.de/download/yabasic-2.81.4-1.x86_64.rpm) reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: stop_cache_selection_list executable: /usr/bin/nautilus journald_cursor: s=b6140f88b3f347c09b98774f0f7b37fe;i=4815;b=30c9a61eac5a41bea955d1ee07c82d6d;m=36e73510;t=5822c12d4abf6;x=32b4f40678a5c1eb kernel: 4.20.8-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 1683924 has been marked as a duplicate of this bug. ***
*** Bug 1684989 has been marked as a duplicate of this bug. ***
*** Bug 1685284 has been marked as a duplicate of this bug. ***
*** Bug 1688990 has been marked as a duplicate of this bug. ***
Similar problem has been detected: The followig steps are: 1. I created a folder using nautilus and was arranging my files. 2. It was hung for a while, when I cut and trying to paste a file(txt) from one directory to another using keyboard. 3. Then I tried to open the file using "Text Editor" which was also hung for few seconds. 4. Finally I closed "Text editor" and "Nautilus" normally and opend again to move my file, it worked after which "Problem Reporting" showed me the problem raised by saying "nautilus killed by SIGSEGV" under Application crash. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: stop_cache_selection_list executable: /usr/bin/nautilus journald_cursor: s=1a23edcf49f542c09def98035c8b52d3;i=147fa;b=0791e27c2fd542b0aa0e04705d4021a5;m=aec9a6fc;t=5845c8f2cd59f;x=4c4aa60d4146a348 kernel: 4.20.15-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 1691262 has been marked as a duplicate of this bug. ***
Similar problem has been detected: navigating in folder with pictures, also possibly caused by a drag- & drop action reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: stop_cache_selection_list executable: /usr/bin/nautilus journald_cursor: s=15a9e5ea69ee4b398d22ff30826e1b89;i=3e56f9;b=fa5a9a19d13943f480a8e85305a9f972;m=3b361f34d;t=58529e5d9611d;x=d5a74b5b07792720 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
Similar problem has been detected: Nautilus started to display undefined behaviour after (unsuccessfully) trying to drag and drop a directory into another directory. I killed it using Ctrl-q and restarted it (twice), and it quickly segfaulted. I was not doing anything special when the segfault happened. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: stop_cache_selection_list executable: /usr/bin/nautilus journald_cursor: s=e0727d9a8a414c4f8f45be933af8b75a;i=99c62;b=3a3c67876dd34f48b3eaa1cc7a33a93b;m=2e44e2032;t=5858b7e601b7a;x=d7c0a8ac24b750d4 kernel: 5.0.4-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 1701661 has been marked as a duplicate of this bug. ***
*** Bug 1705241 has been marked as a duplicate of this bug. ***
*** Bug 1705654 has been marked as a duplicate of this bug. ***
*** Bug 1705958 has been marked as a duplicate of this bug. ***
*** Bug 1706496 has been marked as a duplicate of this bug. ***
*** Bug 1720414 has been marked as a duplicate of this bug. ***
*** Bug 1732865 has been marked as a duplicate of this bug. ***
Similar problem has been detected: The crash happened while I was selecting multiple image files (.dng) by holding Ctrl and clicking them one by one. Before that, Nautilus showed strange behaviour (Ctrl being stuck) and had to be restarted after doing the following: - Hold Ctrl and select multiple (dozens of) files. - Mistakenly "slip", hence initiating a drag-and-drop. - Ctrl is now "stuck": clicking on a file adds it to the selection, clicking on a shortcut in the left panel opens it in a new tab, etc... reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: stop_cache_selection_list executable: /usr/bin/nautilus journald_cursor: s=e0727d9a8a414c4f8f45be933af8b75a;i=257648;b=ff98829e87fc404bb31f272f8dcf42a2;m=58a40ee;t=59209aedb08a8;x=4ffb2b115d3e50a9 kernel: 5.2.11-100.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
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.