there has been no such issue reported in years, assuming it doesn't
exist in the current version of the code and closing

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

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

Title:
  [lucid] nautilus crashed with SIGSEGV in g_closure_invoke()

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  I'm aware of the many similar bugs, but they seem to concern older
  versions. I'm reporting this one separately because I'm on Lucid.

  ProblemType: Crash
  Architecture: amd64
  Date: Tue Jan 19 09:38:02 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/nautilus
  Package: nautilus 1:2.29.1-0ubuntu2
  ProcCmdline: nautilus --sm-client-id 
1080a661343d896341126078375934851900000043280032 --sm-client-state-file 
/home/User Name/.config/session-state/nautilus-1263890127.desktop
  ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
  SegvAnalysis:
   Segfault happened at: 0x7fbc7b64d5cc:        mov    0x8(%rsi),%rdx
   PC (0x7fbc7b64d5cc) ok
   source "0x8(%rsi)" (0x00000008) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/libgtk-x11-2.0.so.0
   g_closure_invoke ()
   ?? () from /usr/lib/libgobject-2.0.so.0
   ?? () from /usr/lib/libgtk-x11-2.0.so.0
  Tags: lucid
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  Uname: Linux 2.6.32-10-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XsessionErrors:
   (gnome-settings-daemon:2017): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:2017): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:2086): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (trackerd:2085): Tracker-CRITICAL **: Could not initialize the HAL context, 
no error, is hald running?

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to