nautilus crashes when browsing /var/log at nautilus_icon_container_search_preedit_changed

Bug #630886 reported by Johan Kiviniemi
This bug report is a duplicate of:  Bug #625696: Nautilus crash when IM preedit. Edit Remove
42
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Nautilus
New
Critical
nautilus (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: nautilus

Nautilus crashes consistently when browsing /var/log and finding files by typing their names.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.31.90-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-19.26-generic-pae 2.6.35.3
Uname: Linux 2.6.35-19-generic-pae i686
NonfreeKernelModules: fglrx wl
Architecture: i386
Date: Sun Sep 5 16:17:27 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=fi_FI.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/zsh
 LC_NUMERIC=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x8132373: movl $0x1,0x224(%eax)
 PC (0x08132373) ok
 source "$0x1" ok
 destination "0x224(%eax)" (0x6e617697) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__STRING ()
 g_closure_invoke () 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
Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__STRING()
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Johan Kiviniemi (ion) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 nautilus_icon_container_search_preedit_changed (
 g_cclosure_marshal_VOID__STRING ()
 g_closure_invoke () 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

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-i386-retrace
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=629159 .

Is there any chance to get a more complete backtrace in case the nautilus developers ask for it? please read https://wiki.ubuntu.com/DebuggingProgramCrash to known how to do it and make sure you have libgtk2, libglib2 and nautilus dbgsym packages installed, thanks a lot.

summary: - nautilus crashes when browsing /var/log
+ nautilus crashes when browsing /var/log at
+ nautilus_icon_container_search_preedit_changed
Changed in nautilus (Ubuntu):
status: New → Triaged
Changed in nautilus:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
Jesse (sbjesse) wrote :

I am affected too. Am I discovered that this doesn't happen on a freshly installed machine, only from my box that upgraded from Lucid to Alpha

Revision history for this message
Jesse (sbjesse) wrote :

I have tried obtaining a more detailed backtrace attached here:?field.comment=I have tried obtaining a more detailed backtrace attached as gdb-nautilus.txt
The command I ran to get the backtrace:
gdb -x ~/junk/nautilus.gdbrc -p `pidof nautilus` nautilus
The content of nautilus.gdbrc is as follows: (between the bars)
====
set logging file gdb-nautilus.txt
set logging overwrite on
set logging on
handle SIG33 pass nostop noprint
set pagination 0
continue
backtrace full
info registers
x/16i $pc
thread apply all backtrace full
quit
====
What I did the reproduce the bug:
1. run gdb to attach to nautilus (damn it is reborn every time ...)
2. visit Places / Bookmarks / Downloads, which gives me a Nautilus window
3. type "ooo". Nautilus behaved as expected. Close this window
4. invoke "nautilus ~/Downloads" from terminal, which gives me a Nautilus window
5. type "ooo". Bug reproduced:
  preedit box pops up, the first "o" is entered, and SIGSEGV was caught ...

Revision history for this message
Fumihito YOSHIDA (hito) wrote :

@Jesse

I check this backtrace file, it seems same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/625696 , and, bt18 are ibus's procedure(maybe).

Could you please check your environment that {had / had not} ibus-enablement?

Revision history for this message
Jesse (sbjesse) wrote :

@fumihito thank you! i've tried running nautilus without ibus and you are right! it didn't crash!

Revision history for this message
Fumihito YOSHIDA (hito) wrote :

@Jesse

Thank you for your responce! I'll set dup of 625696.
And, your backtrace-file seems very good case, it will be there for bug squash!

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.