nautilus crashed with SIGSEGV in g_closure_invoke()

Bug #186235 reported by josegd
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

Gnome 2.21

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Jan 26 22:29:52 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: cdrom
Package: nautilus 1:2.21.6-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: nautilus /media/sda4/jose
ProcCwd: /home/jose
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
Uname: Linux jose-desktop 2.6.24-5-generic #1 SMP Thu Jan 24 19:29:14 UTC 2008 x86_64 GNU/Linux
UserGroups:

Tags: apport-crash
Revision history for this message
josegd (josegd-telefonica) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_closure_invoke (closure=0x1494ca0, return_value=0x0, n_param_values=1,
signal_emit_unlocked_R (node=0xb38110, detail=0, instance=0x119b2a0, emission_return=0x0,
IA__g_signal_emit_valist (instance=0x119b2a0, signal_id=<value optimized out>, detail=0,
IA__g_signal_emit (instance=0x2, signal_id=0, detail=32)
gtk_combo_box_model_row_deleted (model=0x1498130, path=0x16ca980, user_data=0x119b2a0)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in nautilus:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, can you tell us a few easy steps in order to reproduce the crash? thanks.

Changed in nautilus:
assignee: nobody → 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:
status: Incomplete → Invalid
Revision history for this message
Bryan (bhalter-launchpad) wrote :

Seem to be hitting this again in Ibbid

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.