The bug didn't get activity/new duplicates for some years and the
nautilus code saw quite some changes since which probably deprecated the
issue so closing it. If it's still a problem in recent Ubuntu/nautilus
version please submit a new report

** Changed in: nautilus (Ubuntu)
       Status: New => Invalid

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.

  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:

Bug description:
  $  apt-cache policy nautilus                               
    Installed: 1:3.6.3-0ubuntu17
    Candidate: 1:3.6.3-0ubuntu17
    Version table:
   *** 1:3.6.3-0ubuntu17 0
          500 saucy/main amd64 Packages
          100 /var/lib/dpkg/status

  $  lsb_release -rd
  Description:    Ubuntu Saucy Salamander (development branch)
  Release:        13.10

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.6.3-0ubuntu17
  ProcVersionSignature: Ubuntu 3.9.0-3.8-generic 3.9.4
  Uname: Linux 3.9.0-3-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Jun  6 10:52:34 2013
  Disassembly: => 0x7f220441c789:       Cannot access memory at address 
  ExecutablePath: /usr/bin/nautilus
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+147+24'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2012-09-30 (248 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
  MarkForUpload: True
  ProcCmdline: nautilus -n
   Segfault happened at: 0x7f220441c789:        Cannot access memory at address 
   PC (0x7f220441c789) ok
   SP (0x7ffffebcdca0) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: nautilus
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (30 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to