Nautilus randomly slow and finally crashes

Bug #1378424 reported by Free Rage
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Low
Unassigned

Bug Description

I migrated my laptop in 14.04.1 LTS (from a 12.04 partially upgraded in 13.10 for hardware support). Since then I have randomly very slow nautilus windows opening. When that happen, if a nautilus window is opened it become grey and the icons on the desktop are frozen the time for the new nautilus window to show up.

I thought problem solve by editing .gtk-bookmarks in home directory witch contained some old reference to unavailable samba shares [edit : that file (.gtk-bookmarks) is no longer used, so that was why it was refering to old shares. The new one ~/.config/gtk-3.0/bookmarks has no reference to unavailable shares]. But the problem arise again and I get some random crashes.

I tried to launch nautilus from command line but no message.

Note that I had to upgrade samba due to the bug https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186

Date: Tue Oct 7 17:48:20 2014
DistroRelease: Ubuntu 14.04
ExecutablePath: /usr/bin/nautilus
ExecutableTimestamp: 1405434801
ProcCmdline: nautilus -n
ProcCwd: /home/pro
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcMaps:
[description is too long see file attached]
ProcStatus:
 Name: nautilus
 State: S (sleeping)
 Tgid: 2927
 Ngid: 0
 Pid: 2927
 PPid: 2631
 TracerPid: 0
 Uid: 1000 1000 1000 1000
 Gid: 1000 1000 1000 1000
 FDSize: 64
 Groups: 4 24 27 30 46 109 124 125 1000
 VmPeak: 1465996 kB
 VmSize: 1421672 kB
 VmLck: 0 kB
 VmPin: 0 kB
 VmHWM: 92616 kB
 VmRSS: 50124 kB
 VmData: 929688 kB
 VmStk: 136 kB
 VmExe: 1352 kB
 VmLib: 63360 kB
 VmPTE: 960 kB
 VmSwap: 1592 kB
 Threads: 4
 SigQ: 0/26789
 SigPnd: 0000000000000000
 ShdPnd: 0000000000000000
 SigBlk: 0000000000000000
 SigIgn: 0000000000001000
 SigCgt: 0000000180000000
 CapInh: 0000000000000000
 CapPrm: 0000000000000000
 CapEff: 0000000000000000
 CapBnd: 0000001fffffffff
 Seccomp: 0
 Cpus_allowed: f
 Cpus_allowed_list: 0-3
 Mems_allowed: 00000000,00000001
 Mems_allowed_list: 0
 voluntary_ctxt_switches: 23120
 nonvoluntary_ctxt_switches: 6415
Signal: 11
Uname: Linux 3.13.0-36-generic x86_64
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_LogindSession: /user/1000.user/c2.session

Revision history for this message
Free Rage (free-rage) wrote :
description: updated
Revision history for this message
Free Rage (free-rage) wrote :

The same problem can happen even when I try to open the printers window.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.