Version-Release number of selected component: nautilus-3.10.1-3.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/nautilus --no-default-window crash_function: nautilus_window_sync_location_widgets executable: /usr/bin/nautilus kernel: 3.13.3-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 nautilus_window_sync_location_widgets at nautilus-window.c:1022 #1 real_active at nautilus-window-slot.c:475 #5 g_signal_emit_by_name at gsignal.c:3426 #6 nautilus_window_set_active_slot at nautilus-window.c:1780 #7 notebook_switch_page_cb at nautilus-window.c:272 #12 gtk_notebook_switch_page at gtknotebook.c:6597 #13 gtk_notebook_real_remove at gtknotebook.c:4939 #14 gtk_notebook_remove at gtknotebook.c:4109 #15 nautilus_notebook_remove at nautilus-notebook.c:461 #20 g_list_foreach at glist.c:949
Created attachment 865834 [details] File: backtrace
Created attachment 865835 [details] File: cgroup
Created attachment 865836 [details] File: core_backtrace
Created attachment 865837 [details] File: dso_list
Created attachment 865838 [details] File: environ
Created attachment 865839 [details] File: exploitable
Created attachment 865840 [details] File: limits
Created attachment 865841 [details] File: maps
Created attachment 865842 [details] File: open_fds
Created attachment 865843 [details] File: proc_pid_status
Created attachment 865844 [details] File: var_log_messages
Another user experienced a similar problem: logged using root with a portable hard drive connected through usb reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/nautilus --new-window crash_function: nautilus_window_sync_location_widgets executable: /usr/lib64/sampler/wrapped/usr/bin/nautilus kernel: 3.13.5-202.fc20.x86_64 package: nautilus-3.10.1-3.fc20.sam.1 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
abrtd just reported this same issue on my laptop, as I closed nautilus. So I thought I'd provides some background on what lead up to it, since it might be reproducible on my laptop. (At least, the performance issues leading up to the segfault are very reproducible). Prior to closing nautilus, I was transferring about 3GB of data to my HTC One Android phone. Data transfers like that have regularly caused my entire desktop GUI (Gnome 3) to lock up. Sometimes to the point where I can't move my mouse. Eventually that will pass after the file transfer is done. During the file transfer, an additional 1GB of swap was used on my system. The majority of memory was being used by 'gvfsd-gphoto2'. This swap remained in use, with gvfsd-gphoto2 using 66% of memory in top. (Even after the transfer was done). Here's what happened when I closed nautilus after the file transfer had been completed for at least 10 minutes. May 22 10:07:36 nibbana dbus-daemon: dbus[1522]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' May 22 10:07:36 nibbana dbus[1522]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' May 22 10:07:36 nibbana systemd: Starting Fingerprint Authentication Daemon... May 22 10:07:36 nibbana dbus-daemon: dbus[1522]: [system] Successfully activated service 'net.reactivated.Fprint' May 22 10:07:36 nibbana dbus[1522]: [system] Successfully activated service 'net.reactivated.Fprint' May 22 10:07:36 nibbana systemd: Started Fingerprint Authentication Daemon. May 22 10:07:36 nibbana fprintd: Launching FprintObject May 22 10:07:36 nibbana fprintd: ** Message: D-Bus service launched with name: net.reactivated.Fprint May 22 10:07:36 nibbana fprintd: ** Message: entering main loop May 22 10:07:48 nibbana kernel: nautilus[22951]: segfault at 20 ip 0000000000478c39 sp 00007fff9154e890 error 4 in nautilus[400000+14b000] May 22 10:07:48 nibbana kernel: [71735.791038] nautilus[22951]: segfault at 20 ip 0000000000478c39 sp 00007fff9154e890 error 4 in nautilus[400000+14b000] May 22 10:07:52 nibbana abrt-hook-ccpp: Saved core dump of pid 22951 (/usr/bin/nautilus) to /var/tmp/abrt/ccpp-2014-05-22-10:07:50-22951 (77434880 bytes) May 22 10:07:59 nibbana abrt-server: Generating core_backtrace May 22 10:07:59 nibbana abrt-server: Generating backtrace May 22 10:08:07 nibbana fprintd: ** Message: No devices in use, exit May 22 10:08:17 nibbana dbus-daemon: dbus[1522]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) May 22 10:08:17 nibbana dbus[1522]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) May 22 10:08:17 nibbana dbus-daemon: dbus[1522]: [system] Successfully activated service 'org.freedesktop.problems' May 22 10:08:17 nibbana dbus[1522]: [system] Successfully activated service 'org.freedesktop.problems' May 22 10:08:31 nibbana gnome-session: Window manager warning: last_focus_time (71760630) is greater than comparison timestamp (71755948). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... May 22 10:08:40 nibbana gnome-session: abrt-applet: Problem connecting to dbus, or applet is already running I can provide that core dump, if needed. After removing my phone, swap usage dropped by 1GB. May 22 10:11:04 nibbana kernel: [71932.273714] usb 1-1.2: USB disconnect, device number 14 May 22 10:11:04 nibbana kernel: usb 1-1.2: USB disconnect, device number 14 May 22 10:11:06 nibbana colord: device removed: sysfs-HTC-Android_Phone
Another user experienced a similar problem: The cinnamon session was running overnight. The session was locked. It was unlocked & some windows were closed like like DejaDup, Nemo, gnome-terminal etc. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: nautilus --new-window /run/media/vikram/VIKRAM crash_function: nautilus_window_sync_location_widgets executable: /usr/bin/nautilus kernel: 3.14.7-200.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Aession in cinnamon. Two tabs were open. One was a dir in HOME & another was a pen drive. A file was copied to pen drive. When the file dialog stated 100 % the window was closed after which it crashed. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: nautilus --new-window /run/media/vikram/VIKRAM crash_function: nautilus_window_sync_location_widgets executable: /usr/bin/nautilus kernel: 3.14.7-200.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGSEGV runlevel: 1 5 type: CCpp uid: 1000
Another user experienced a similar problem: Start copying something to an USB stick and then close the copy window and Nautilus. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/nautilus --no-default-window crash_function: nautilus_window_sync_location_widgets executable: /usr/bin/nautilus kernel: 3.14.8-200.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: when i run the program the cpu use is 100%, then i close the window. i think there is a memory leak bug. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: nautilus_window_sync_location_widgets executable: /usr/bin/nautilus kernel: 3.14.9-200.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.