nautilus crashed with SIGSEGV in g_type_check_is_value_type()

Bug #638463 reported by ubername
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nautilus

I had a problem with the contents displaying on my desktop

see http://ubuntuforums.org/showthread.php?t=1574604

I was playing with the 'desktop-is-home-dir' setting. At some point I noticed that Nautilus was no longer displaying 'Home' in the side panel, and when I set the desktop is home dir to true, Nautilus crashed

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.31.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4
Uname: Linux 2.6.35-21-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Sep 14 22:11:59 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: nautilus --sm-client-id 10d9fb22f712501281127417629690618400000185900031 --sm-client-state-file /home/username/.config/session-state/nautilus-1284498394.desktop
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff91afd615f <g_type_check_is_value_type+271>: cmpq $0x0,(%rax)
 PC (0x7ff91afd615f) ok
 source "$0x0" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_is_value_type () from /usr/lib/libgobject-2.0.so.0
 g_value_type_compatible () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_is_value_type()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
ubername (ubername) wrote :
ubername (ubername)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_is_value_type (
 g_value_type_compatible (src_type=37016896,
 g_value_object_collect_value (value=0x1e68888,
 g_signal_emit_valist (
 g_signal_emit (instance=0x234d540, signal_id=0,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

is this reproducible with latest package on Maverick?

Changed in nautilus (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in nautilus (Ubuntu):
status: Incomplete → Invalid
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.