nautilus hits SIGABRT eel_canvas_item_send_behind "item_position != -1

Bug #946671 reported by Sarrvesh
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Nautilus
Confirmed
Critical
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I found that a lot of related bugs have either become invalid or expired. I am not sure whether I will be able to recreate this crash scenario but nautilus crashed when I moved from a directory to its parent directory.

Description: Ubuntu precise (development branch)
Release: 12.04

nautilus:
  Installed: 1:3.3.90-0ubuntu6
  Candidate: 1:3.3.90-0ubuntu6
  Version table:
 *** 1:3.3.90-0ubuntu6 0
        500 http://se.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.90-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.94-0ubuntu1
Architecture: i386
CheckboxSubmission: a15aeb06833f0b0e12fcaa521b827126
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Sun Mar 4 23:02:56 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+564+189'
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: nautilus crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-03-02 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Sarrvesh (sarrfriend) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=0x817d59f "Eel", file=0x817d80c "eel-canvas.c", line=753, func=0x817e100 "eel_canvas_item_send_behind", message=<optimized out>) at /build/buildd/glib2.0-2.31.18/./glib/gtestutils.c:1860
 g_assertion_message_expr (domain=0x817d59f "Eel", file=0x817d80c "eel-canvas.c", line=753, func=0x817e100 "eel_canvas_item_send_behind", expr=0x817daf2 "item_position != -1") at /build/buildd/glib2.0-2.31.18/./glib/gtestutils.c:1871
 eel_canvas_item_send_behind (item=0x93add70, behind_item=0x8de2820) at eel-canvas.c:755
 nautilus_icon_container_add (container=0x8c4b408, data=0x92a1008) at nautilus-icon-container.c:7181
 nautilus_icon_view_add_file (view=0x8ed0028, file=0x92a1008, directory=0x8f25148) at nautilus-icon-view.c:527

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 SIGABRT in raise()
+ nautilus crashed with SIGABRT in g_assertion_message()
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: nautilus crashed with SIGABRT in g_assertion_message()

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
visibility: private → public
summary: - nautilus crashed with SIGABRT in g_assertion_message()
+ nautilus crashed with SIGABRT eel_canvas_item_send_behind"
+ "item_position != -1
summary: - nautilus crashed with SIGABRT eel_canvas_item_send_behind"
- "item_position != -1
+ nautilus crashed with SIGABRT eel_canvas_item_send_behind "item_position
+ != -1
summary: - nautilus crashed with SIGABRT eel_canvas_item_send_behind "item_position
- != -1
+ nautilus hits SIGABRT eel_canvas_item_send_behind "item_position != -1
Changed in nautilus (Ubuntu):
status: Confirmed → Triaged
Changed in nautilus:
importance: Unknown → Medium
status: Unknown → New
Changed in nautilus:
importance: Medium → Critical
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug is quite old and the code changed since, also there has been no new report of that specific problem nor activity for some years so assuming it has been resolved and closing the ticket. If you still get issues in newer versions feel free to open a new report though.

Changed in nautilus (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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