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

[Doug McMahon]

Test Case:
Have more than 1 additional internal paritions
Open nautilus, mount 1 from sidebar, mounts fine
Try to mount another partition, nautilus window closes without mounting

Error seen in .xsessions-errors
ERROR:nautilus-places-sidebar.c:1885:open_selected_bookmark: assertion failed: (sidebar->go_to_after_mount_slot == NULL)

likely produces an apport but that just goes to whoopsie

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.4.0-2.6-generic 3.4.0-rc7
Uname: Linux 3.4.0-2-generic x86_64
ApportVersion: 2.1-0ubuntu1
Architecture: amd64
CasperVersion: 1.316
Date: Mon May 21 20:40:11 2012
GsettingsChanges:

LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120521)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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

[Doug McMahon (mc3man)]

Just to note - there is an apport .crash generated, but like all other apport .crash's in 12.10 the report will only be uploaded to a db? somewhere. As in whatever.crash > whatever.upload > whatever.uploaded

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Doug McMahon (mc3man)]

It is currently impossible to get apport or ubuntu-bug to open a launchpad bug report.
As I previously mentioned ALL crashes (/var/crash/.crash) go to /var/crash/upload > /var/crash/uploaded & that's that.
Even apport-cli -c /var/crash/whatever.crash does the same thing if choosing the S option

This occurs even in a few cases where I'm sure there are no previous dupes

As far as this bug several users have found very easy to duplicate based on description

[Sebastien Bacher (seb128)]

you might need to edit /etc/apport/crashdb.conf and uncomment the problem_types line for apport to send issues to launchpad

[Doug McMahon (mc3man)]

The crashdb.conf was ok , just wasn't happening. However with the new apport* packages, (2.1.1-0ubuntu2), all seems fine again
So caused the crash & refiled. Will mark this invalid
For reference new bug report, currently private
Bug 1007593