nautilus crashes on opening folder containing broken symlinks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nautilus |
Fix Released
|
Critical
|
|||
nautilus (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: nautilus
whenever i open the '/usr/bin' folder of my lucid partiton, nautilus crashes.This happens every time i open the folder. when i run it in the terminal this is the output i get
-------
arjun@arjun-
(nautilus:5034): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported
Initializing nautilus-gdu extension
Nautilus-
Please ask your system administrator to enable user sharing.
Segmentation fault
-------
Description: Ubuntu maverick (development branch)
Release: 10.10
nautilus:
Installed: 1:2.30.1-0ubuntu3
Candidate: 1:2.30.1-1ubuntu1
Version table:
1:
500 http://
*** 1:2.30.1-0ubuntu3 0
100 /var/lib/
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.30.1-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.34-5-generic x86_64
Architecture: amd64
Date: Wed Jun 23 15:42:13 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100602.2)
ProcEnviron:
LANG=en_IN
SHELL=/bin/bash
SourcePackage: nautilus
tags: | added: lucid |
summary: |
- nautrilus crashes on opening /usr/bin + nautilus crashes on opening folder containing broken symlinks |
Changed in nautilus: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in nautilus: | |
importance: | Medium → Critical |
status: | New → Incomplete |
Changed in nautilus: | |
status: | Incomplete → New |
Changed in nautilus (Ubuntu): | |
status: | New → Triaged |
Changed in nautilus: | |
status: | New → Confirmed |
Changed in nautilus: | |
status: | Confirmed → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http:// wiki.ubuntu. com/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.