nautilus hits SIGABRT: sidebar->go_to_after_mount_slot == NULL

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

Bug Description

This crash occurs when trying to open, (mount) more than 1 internal partition from the same nautilus window

Test case: have 2 or more available partitions to mount
Open nautilus, click on one in sidebar - it mounts/opens fine
Click on a 2nd one, nautilus hangs, then crashes

from xsession-errors
ERROR:nautilus-places-sidebar.c:1885:open_selected_bookmark: assertion failed: (sidebar->go_to_after_mount_slot == NULL)

attached small vid
This is on todays iso, upsated, in a live session. See the same thing on a real install & have for some time now in 12.10

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.4.0-3.8-generic 3.4.0
Uname: Linux 3.4.0-3-generic x86_64
ApportVersion: 2.1.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.317
Date: Fri Jun 1 20:29:04 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+24'
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120601)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no 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: (compiz:7826): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed

Related branches

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
Doug McMahon (mc3man)
visibility: private → public
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
summary: - nautilus crashed with SIGABRT in g_assertion_message()
+ nautilus hits SIGABRT: sidebar->go_to_after_mount_slot == NULL
Changed in nautilus (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Changed in nautilus:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in nautilus (Ubuntu):
status: Triaged → Fix Committed
Changed in nautilus:
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nautilus - 1:3.5.1-0ubuntu6

---------------
nautilus (1:3.5.1-0ubuntu6) quantal; urgency=low

  * debian/patches/git_no_assert_on_double_mount.patch: lp: #1007593
    "sidebar: don't forget to NULL slot pointer after volume is mounted"
  * debian/patches/git_bookmark_place_dnd.patch: lp: #874386, #920691
    "places-sidebar: allow dropping of files to bookmarks"
  * debian/patches/git_no_menubars_segfault.patch: lp: #1003771
    "window-menus: disconnect from GtkSettings notifications on finalize"
 -- Sebastien Bacher <email address hidden> Tue, 12 Jun 2012 21:28:08 +0200

Changed in nautilus (Ubuntu):
status: Fix Committed → 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.