nautilus crashed with SIGSEGV in g_closure_invoke()

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

Bug Description

Opening new as all the previous bugs were different version.
This is a new bug on 12.04

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.2.1-2ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CheckboxSubmission: 436b39225e95524b1259e913c38499a0
CheckboxSystem: 3e53d3ea5811723345f19eff5070f9ab
Date: Wed Dec 28 07:36:41 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: nautilus /home/username/Pictures
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f538a8bf34c: mov 0x8(%rbp),%eax
 PC (0x7f538a8bf34c) ok
 source "0x8(%rbp)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/libsyncdaemon-1.0.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
siucdude (siucdude) wrote :
visibility: private → public
Revision history for this message
Aaron Haviland (aaron-haviland) wrote :

This appears to be a duplicate of bug #908261. Do you have any indication that it is a different issue?

Revision history for this message
siucdude (siucdude) wrote :

Yes looks to be duplicate... when i submitted this bug. the 908261 did not show up in the list.
Thanks
TJ

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.