Ubuntu
nautilus package

nautilus crashed with SIGSEGV in gtk_main_do_event()

Bug #417060 reported by GPXRacer on 2009-08-21

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nautilus (Ubuntu)	Invalid	Medium	Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

I was reading this (bug-reporting) homepage when it crashed, therefore I did nothing special

ProblemType: Crash
Architecture: i386
Date: Fri Aug 21 19:31:15 2009
Disassembly: 0x27db390:
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.4-0ubuntu6
ProcCmdline: nautilus
ProcEnviron:
LANGUAGE=de_DE.UTF-8
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
SegvAnalysis:
Segfault happened at: 0x27db390:
PC (0x027db390) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgdk-x11-2.0.so.0
g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
?? () from /usr/lib/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in gtk_main_do_event()
Uname: Linux 2.6.31-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Tags:

Revision history for this message

GPXRacer (bikedevil) wrote on 2009-08-21:

#1

Dependencies.txt Edit (4.3 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (45.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (766 bytes, text/plain; charset="utf-8")
Registers.txt Edit (496 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (538 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.1 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (313 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-24: Stacktrace.txt (retraced)

#2

Stacktrace.txt (retraced) Edit (3.5 KiB, text/plain)

StacktraceTop:?? ()
gdk_event_dispatch (source=0x8853408, callback=0,
IA__g_main_context_dispatch (context=0x8853450)
g_main_context_iterate (context=0x8853450,
IA__g_main_loop_run (loop=0x8b67e28)

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-24: ThreadStacktrace.txt (retraced)

#3

ThreadStacktrace.txt (retraced) Edit (5.0 KiB, text/plain)

Changed in nautilus (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2009-09-04:

#4

Thanks for the report, do you still have this crash? may you tell us a few easy steps in order to recreate it? Thanks.

Changed in nautilus (Ubuntu):
assignee:	nobody → Ubuntu Desktop Bugs (desktop-bugs)
status:	New → Incomplete
visibility:	private → public

Revision history for this message

Sebastien Bacher (seb128) wrote on 2009-09-29:

#5

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in nautilus (Ubuntu):
status:	Incomplete → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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