GNOME Bugzilla – Bug 680665
Crash after editing bookmarks
Last modified: 2012-08-23 10:37:58 UTC
I have gathered nautilus bugs of the type nautilus crashed with SIGABRT in g_assertion_message() all together in launchpad bug: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1017232 Interestingly the crash occures the first time on Ubuntu11.10 with nautilus versionn3.2.1-0ubuntu4.2, then it is in Ubuntu12.04 with version3.4.2-0ubuntu3 and occures last on Ubuntu12.10 with version3.5.4-0ubuntu1. The descriptions of the users are different how to hit the crasher. I have copied the most usefull ones in the launchpad bug(link above), in the comments, so you can have a read on them on one ticket. I could not decide which one is the usefullest. Please have a look at the ticket. Greetings melchiaros Member of Ubuntu Bugsquad ---------Header of the launchpad reportreported by Doug McMahon :------------- 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 . . .
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Hello Andre, on launchpad there are files attached to the report. Also stacktraces as much as you want. I in general do not copy the whole bunch upstream(to much). Bugzilla would be unhappy about. The files can be found on launchpad comment #1 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1017232/comments/1 Please get there what you need. Keep in mind that the dubs may have more actual stacktraces, like: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1029534/comments/1 for 3.5.4 version. Also older stacktraces are available ofer the dubs listed on the right side of the launchpad ticket.
Dough has also checked some minutes ago for reproducability and has pointed out a simple repoducing method. I am not so familiar with Bugzilla. Can you remove the NEEDINFO please.
Oh, sorry I have just recognized that I have point you to the wrong stacktraces.
Created attachment 219708 [details] the stacktrace
I haved attached one manually. The tread stacktraces are still on the launchpad report. Apport do store them not in comment #1. They are some comments later.
(In reply to comment #2) > on launchpad there are files attached to the report. Also stacktraces as much > as you want. I in general do not copy the whole bunch upstream(to much). We just need the stacktrace here (pasted), so the stacktrace parser can pick it up. Thanks for comment 5!
Aha, have not known this. Is then all here what you need? And Unconfiremd is quite not correct. There are 9 people that are affected by this crasher. They have all produced independend of each stacktraces. -> So, I do not know your workflow, but this seems to be enough confirmation.
There isn't any difference between NEW and UNCONFIRMED in this bugtracker. (Plus if 9 people all face it with the same distribution it does not neessarily prove that it's an upstream issue, though unlikely in this case that it isn't.)
Can't reproduce given the instructions in the original comment. Is this still an issue? If so, can you provide updated instructions to reproduce it?
Doug MacMahon, the original reportert, has the same result of nautilus git master 15h ago. He will do a recheck in a week. I have ask him to comment here about the result. Please let the ticket as long as he needs open. Thank you.
As I said, we need a detailed way to reproduce this and a recent detailed backtrace.
There is no need, this is no longer an issue in the current 3.5.90 I had commented in the LP bug about 2 weeks ago that this crash didn't occur in the git source so would not be an issue once Ubuntu upgraded The reporter of this bug bug wanted me to note that here - sorry, I forgot to do so.
In regards to the last comment I close this here as fixed.