desktop-packages team mailing list archive

[Justin Force <711429@xxxxxxxxxxxxxxxxxx>]

This bug definitely still exists in Natty. The GNOME bug also indicates
that the fix is a hack, so I think this is still a problem.

To EASILY reproduce this:

1. Create a folder in Nautilus for testing. Press Ctrl-Shift-N 30 times or so to get a lot of folders to play with then press Enter to create them.
2. Select the top folder and start rapidly pressing the Delete key.
3. Where'd Nautilus go? 


See my previous apport-collect submission above for details.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/711429

Title:
  nautilus crashed with SIGSEGV in g_closure_invoke()

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: nautilus

  Happened when deleting a file.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  NonfreeKernelModules: nvidia wl
  Architecture: amd64
  Date: Tue Feb  1 20:08:51 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: nautilus
  ProcEnviron:
   LANG=es_ES.utf8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4cfbee:	mov    0x18(%rdi),%rdx
   PC (0x004cfbee) ok
   source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
   ?? () from /usr/lib/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin nopasswdlogin plugdev sambashare tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/711429/+subscriptions