nautilus crashed with SIGABRT in g_assertion_message()

Bug #1017232 reported by Doug McMahon
96
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Nautilus
Fix Released
Critical
nautilus (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Small issue -

If you have added a bookmark(s) to nautilus -
Open a nautilus window > Bookmarks > Edit
Change the name of an added bookmark, the change is imediatly relflected in the sidebar under "Bookmarks"
Click on the edited bookmark, nautilus crashes

If you close ^ or open a new nautilus window this doesn't happen, only from the window where edit was made

From xsession-errors
**
ERROR:nautilus-bookmarks-window.c:272:repopulate: assertion failed: (GTK_IS_TREE_VIEW (bookmark_list_widget))

There was further but seems an apport issue unrelated

**
ERROR:nautilus-bookmarks-window.c:272:repopulate: assertion failed: (GTK_IS_TREE_VIEW (bookmark_list_widget))
ERROR: hook /usr/share/apport/package-hooks//source_nautilus.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 799, in add_hooks_info
    symb['add_info'](self, ui)
TypeError: add_info() takes exactly 1 positional argument (2 given)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 804, in add_hooks_info
    symb['add_info'](self)
  File "/usr/share/apport/package-hooks//source_nautilus.py", line 6, in add_info
    if report.has_key("Stacktrace") and "/usr/lib/nautilus" in report["Stacktrace"]:
AttributeError: 'Report' object has no attribute 'has_key'

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
Uname: Linux 3.5.0-1-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.2.5-0ubuntu1
Architecture: amd64
Date: Sun Jun 24 15:10:10 2012
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120623)
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: nautilus crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (gnome-settings-daemon:21155): color-plugin-WARNING **: failed to get edid: unable to get EDID for output
 (gnome-settings-daemon:21155): color-plugin-WARNING **: unable to get EDID for xrandr-default: unable to get EDID for output
 (gnome-settings-daemon:21155): color-plugin-WARNING **: failed to reset xrandr-default gamma tables: gamma size is zero
 (compiz:21169): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed

Revision history for this message
Doug McMahon (mc3man) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.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-amd64-retrace
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
Sasa Paporovic (melchiaros) wrote :

Justin wrote in bug 978809 which refere to oneiric:

"
There might be multiple issues here, but I don't recall exactly the chain of events. I started by opening a folder via the Dropbox indicator and then opened a nautilus tab by clicking on one of my bookmarks on the left. At this point, copy/paste, etc. were disabled in the folder I originally opened and the properties window for any object in the Dropbox folder indicated that I was supposedly clicking on the folder I had opened in the second tab. Very strange. Then, I reloaded the Dropbox folder/tab a few times (crtl+r) with no change in the context menu (copy/paste still disabled). Finally I changed folders in the first tab, the Dropbox folder tab, by clicking on a different bookmark or something higher in the hierarchy from the bar at the top. Nautilus then crashed.

"

tags: added: i386 oneiric
tags: added: precise
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Dmitry Shachnev wrote in bug 1015012 on precise:
"
Nautilus crashed when I pressed Ctrl+Z trying to revert renaming of a file.

"

Revision history for this message
Doug McMahon (mc3man) wrote :

This is continuing in nautilus-1:3.5.4-0ubuntu2 in 12.10
Now the crash can occur by simply just renaming an added bookmark, same error

ERROR:nautilus-bookmarks-window.c:272:repopulate: assertion failed: (GTK_IS_TREE_VIEW (bookmark_list_widget))

Changed in nautilus:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Doug McMahon (mc3man) wrote :

Don't know if additionally help, will attach anyway

Changed in nautilus:
importance: Medium → Critical
C de-Avillez (hggdh2)
tags: added: qa-manual-testing
Revision history for this message
Doug McMahon (mc3man) wrote :

As of the current master git this crash doesn't occur on 12.10 as previously described & or as in comment #9
The latest version has moved Bookmarks (edit), to the app menu, checked in both unity & gs

I gather in a week or so there should be another Ubuntu package release, can be rechecked then

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Hi Doug,

the nautilus maintainers on the GNOME project have the same result, they could not hit the crasher with the latest development of nautilus.

When you do the rechek can you comment on upstream bugtracker what the result is? In the case when it is gone, please tell them to close their ticket, but please let the launchpad one open, because oneiric and precise will be still affected.

Thank you

melchiaros

Changed in nautilus:
status: New → Incomplete
Changed in nautilus (Ubuntu):
status: Confirmed → Fix Released
Changed in nautilus:
status: Incomplete → Fix Released
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.