nautilus crashed with SIGSEGV

Bug #871260 reported by Andreas
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

this happens quite frequently and at random time points.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Oct 9 14:04:24 2011
Disassembly: => 0x7fef0d8ca8be: Cannot access memory at address 0x7fef0d8ca8be
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fef0d8ca8be: Cannot access memory at address 0x7fef0d8ca8be
 PC (0x7fef0d8ca8be) ok
 SP (0x7fffe020ac60) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (16 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:2085): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed
 (gnome-settings-daemon:2085): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed
 (nautilus:2134): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (nautilus:2134): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed

Revision history for this message
Andreas (andreas-kotowicz) wrote :
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.