nautilus crashed with SIGSEGV in icon_rename_ended_cb()

Bug #985848 reported by Bálint Magyar
56
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Nautilus
Invalid
Critical
nautilus (Fedora)
Won't Fix
Undecided
nautilus (Ubuntu)
Invalid
High
Unassigned

Bug Description

Crash happened just as I pressed Return after entering a name for a newly created directory. There was a several seconds long freeze before the window closed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
CheckboxSubmission: eed034d02b91fdd992cb6cca72fa5744
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Thu Apr 19 21:29:33 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 org.gnome.nautilus.window-state geometry '1069x624+295+115'
 org.gnome.nautilus.window-state sidebar-width 187
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120407)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x4398ce: cmp %rax,(%rdx)
 PC (0x004398ce) ok
 source "%rax" ok
 destination "(%rdx)" (0x275d0078) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
In , kotofos (kotofos-redhat-bugs) wrote :

libreport version: 2.0.7
abrt_version: 2.0.6
backtrace_rating: 3
cmdline: nautilus -n
comment: open new window, by clicking middle button on side panel, while no nautilus windows open and "nautilus handle desktop" is on
crash_function: icon_rename_ended_cb
executable: /usr/bin/nautilus
kernel: 3.1.4-1.fc16.x86_64
pid: 1482
pwd: /home/kotofos
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
time: Вт. 13 дек. 2011 19:10:54
uid: 1000
username: kotofos

backtrace: Text file, 38487 bytes
dso_list: Text file, 16442 bytes
maps: Text file, 77207 bytes
smolt_data: Text file, 2991 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=1
:HOSTNAME=kotofos-laptop
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=1ae78454aedfe02bdcbc0f4b00000011-1323669018.425340-735808942
:QTDIR=/usr/lib64/qt-3.3
:QTINC=/usr/lib64/qt-3.3/include
:IMSETTINGS_MODULE=none
:USER=kotofos
:USERNAME=kotofos
:MAIL=/var/spool/mail/kotofos
:PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/kotofos/.local/bin:/home/kotofos/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/kotofos
:XMODIFIERS=@im=none
:LANG=en_GB.utf8
:GDM_LANG=en_GB.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/kotofos
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=kotofos
:QTLIB=/usr/lib64/qt-3.3/lib
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-lvSN8ivVxT,guid=bcaf33b2f0a44a31627725bf0000003e
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/kotofos
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-kotofos-1lg2UE/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1186,unix/unix:/tmp/.ICE-unix/1186
:GNOME_KEYRING_CONTROL=/tmp/keyring-Q31oJo
:SSH_AUTH_SOCK=/tmp/keyring-Q31oJo/ssh
:GPG_AGENT_INFO=/tmp/keyring-Q31oJo/gpg:0:1
:LC_TIME=ru_RU.utf8
:LC_NUMERIC=ru_RU.utf8
:LC_MONETARY=ru_RU.utf8
:LC_MEASUREMENT=ru_RU.utf8
:DESKTOP_AUTOSTART_ID=10c46320ee63203918132366902013747200000011860028

var_log_messages:
:Dec 13 19:10:53 kotofos-laptop kernel: [109297.109042] nautilus[1482]: segfault at 30 ip 000000000043862e sp 00007fffcc141730 error 4 in nautilus[400000+159000]
:Dec 13 19:11:17 kotofos-laptop abrt[3397]: Saved core dump of pid 1482 (/usr/bin/nautilus) to /var/spool/abrt/ccpp-2011-12-13-19:10:54-1482 (132722688 bytes)

xsession_errors:
:Initializing nautilus-dropbox 0.7.1
:Initializing nautilus-gdu extension
:(nautilus:1482): Gtk-CRITICAL **: _gtk_timeline_rewind: assertion `GTK_IS_TIMELINE (timeline)' failed
:(nautilus:1482): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
:(nautilus:1482): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
:Initializing nautilus-dropbox 0.7.1
:Initializing nautilus-gdu extension

Revision history for this message
In , kotofos (kotofos-redhat-bugs) wrote :

Created attachment 546222
File: dso_list

Revision history for this message
In , kotofos (kotofos-redhat-bugs) wrote :

Created attachment 546223
File: maps

Revision history for this message
In , kotofos (kotofos-redhat-bugs) wrote :

Created attachment 546224
File: smolt_data

Revision history for this message
In , kotofos (kotofos-redhat-bugs) wrote :

Created attachment 546225
File: backtrace

Revision history for this message
Bálint Magyar (balintm) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 icon_rename_ended_cb (container=<optimized out>, file=0x167a990, new_name=0x1743d70 "Cseh Tam\303\241s - Antoine \303\251s Desir\303\251e (1978)", icon_view=0x11ce300) at nautilus-icon-view.c:1917
 ffi_call_unix64 () at ../src/x86/unix64.S:75
 ffi_call (cif=0x7fff12cf9470, fn=0x4398a0 <icon_rename_ended_cb>, rvalue=<optimized out>, avalue=<optimized out>) at ../src/x86/ffi64.c:486
 g_cclosure_marshal_generic (closure=0x112bd00, return_gvalue=0x0, n_param_values=3, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=0x4398a0) at /build/buildd/glib2.0-2.32.1/./gobject/gclosure.c:1454
 g_closure_invoke (closure=0x112bd00, return_value=0x0, n_param_values=3, param_values=0x7fff12cf96c0, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.32.1/./gobject/gclosure.c:777

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
summary: - nautilus crashed with SIGSEGV in ffi_call_unix64()
+ nautilus crashed with SIGSEGV in icon_rename_ended_cb()
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, that bug is ranked high enough on errors.ubuntu.com, we should try to get it fixed and to roll the fix in a stable update

Changed in nautilus (Ubuntu):
importance: Medium → High
Changed in nautilus (Ubuntu Precise):
importance: Undecided → High
status: New → Triaged
Changed in nautilus:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
In , efreeti (efreeti-redhat-bugs) wrote :

Create a new folder, crash when I tried to name it as "Radio-Em-DR" (without double quotes)

backtrace_rating: 4
Package: nautilus-3.4.2-5.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Revision history for this message
In , efreeti (efreeti-redhat-bugs) wrote :

Created attachment 595452
File: backtrace

Changed in nautilus:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug didn't get any activity for 6 months and no recent duplicate, is that still an issue?

Changed in nautilus (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Stéphane Démurget (stephane-demurget-free) wrote :

My brother just hit this bug many times since yesterday on a folder with ~6000 pictures (I do not know if that can be helpful) with an Ubuntu 12.10 fully updated as of yesterday (12/29/2012).

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

tags: added: saucy
tags: added: utopic
Changed in nautilus (Ubuntu):
status: Incomplete → Invalid
no longer affects: nautilus (Ubuntu Precise)
Changed in nautilus (Fedora):
importance: Unknown → Undecided
status: Unknown → Won't Fix
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.