abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 68976 bytes cmdline: nautilus component: nautilus Attached file: coredump, 66293760 bytes crash_function: gtk_action_group_add_action executable: /usr/bin/nautilus kernel: 2.6.38-1.fc15.x86_64 package: nautilus-2.91.91-1.fc15 rating: 4 reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) release: Fedora release 15 (Lovelock) time: 1300637614 uid: 500 How to reproduce ----- 1. Was just using nautilus in Gnome 3
Created attachment 486481 [details] File: backtrace
Package: nautilus-2.91.91-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1.xchat and thunderbird open and running 2.start file-manager 3.
Package: nautilus-2.91.91-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. Opened nautilus and then hit ctrl+n to open up a second window, only instead of opening another window, it crashed. Comment ----- It was the first time i opened nautilus after resuming from suspend-to-ram
Proposing as a Beta blocker. Nautilus shouldn't keep crashing :-/
Discussed at 2011-03-25 blocker review meeting. Agreed this does not hit any Beta criteria, is a Final blocker per criterion: "All applications listed under the Applications menu must withstand a basic functionality test and not crash after a few minutes of normal use. They must also have working Help and Help -> About menu items " Also accepted as Beta NTH. Mat, can you test with https://admin.fedoraproject.org/updates/nautilus-2.91.92-1.fc15 too?
Discussed at the 2011-04-21 blocker review meeting. Still waiting on retesting, since there are no new reproductions, we will assume that this has been fixed and close next week if there is no new feedback.
I have not seen this crash in a while, I am happy for it to be closed.
cool, let's knock it off then.