nautilus crashed with SIGSEGV in g_object_ref()

Bug #453290 reported by MichaelPalin
90
This bug affects 14 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

1) Ubuntu karmic (development branch) 9.10
2)nautilus:
  Instalados: 1:2.28.0-0ubuntu7
  Candidato: 1:2.28.0-0ubuntu7
  Tabla de versión:
 *** 1:2.28.0-0ubuntu7 0
        500 http://es.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
3) Nothing (wasn't with the PC)
4) Just found the PC like that

ProblemType: Crash
Architecture: amd64
Date: Fri Oct 16 08:30:36 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.28.0-0ubuntu7
ProcCmdline: nautilus
ProcEnviron:
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SegvAnalysis:
 Segfault happened at: 0x7f094dc9c651 <g_object_ref+17>: cmpq $0x50,(%rax)
 PC (0x7f094dc9c651) ok
 source "$0x50" ok
 destination "(%rax)" (0x700000008) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_object_ref () from /usr/lib/libgobject-2.0.so.0
 g_datalist_clear () from /lib/libglib-2.0.so.0
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 g_closure_unref () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_object_ref()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1670): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1670): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1702): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1695): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

Revision history for this message
MichaelPalin (michaelpalin) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:g_object_ref () from /usr/lib/libgobject-2.0.so.0
g_datalist_clear () from /lib/libglib-2.0.so.0
g_object_unref () from /usr/lib/libgobject-2.0.so.0
extension_action_callback_data_free (data=0x1f837c0)
g_closure_unref () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

visibility: private → public
Changed in nautilus (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
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.