This bug has been fixed upstream, and the fix should be available in the
latest available, Oneiric release. Can anyone confirm that this bug has
been fixed in Oneiric?

** Changed in: nautilus (Ubuntu)
       Status: Triaged => Incomplete

-- 
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/518891

Title:
  nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

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

Bug description:
  Binary package hint: nautilus

  When I tried to delete a *.jpg-file, Nautilus crashed.

  ProblemType: Crash
  Architecture: i386
  Date: Mon Feb  8 17:09:05 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: nvidia
  Package: nautilus 1:2.29.2-0ubuntu4
  ProcCmdline: nautilus
  ProcEnviron:
   LANGUAGE=en_GB.utf8
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-12.17-generic-pae
  SegvAnalysis:
   Segfault happened at: 0x811e901:     mov    0xc(%eax),%edx
   PC (0x0811e901) ok
   source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__VOID ()
   g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
  Uname: Linux 2.6.32-12-generic-pae i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to