Bug 437437 - "Open in terminal" crashes Nautilus
Summary: "Open in terminal" crashes Nautilus
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus-open-terminal
Version: 8
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Paul W. Frields
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-14 06:32 UTC by Stephen So
Modified: 2008-03-21 17:39 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2008-03-21 17:39:53 UTC


Attachments (Terms of Use)
trace from nautilus-debuginfo (11.37 KB, application/octet-stream)
2008-03-14 07:14 UTC, Stephen So
no flags Details

Description Stephen So 2008-03-14 06:32:30 UTC
Description of problem:

When I open up nautilus and select "open in terminal", nautilus crashes and bug
buddy comes up


Version-Release number of selected component (if applicable):  nautilus-2.20.0-9.fc8


How reproducible: Always


Steps to Reproduce:
1.  Open up nautilous (eg. click on home folder icon on desktop)
2.  Go to file menu
3.  Select "open in terminal"
  
Actual results:

Bug buddy comes up and nautilus restarts

Expected results:

The gnome-terminal should come up.

Additional info:

Comment 1 petrosyan 2008-03-14 06:56:39 UTC
Can you install nautilus-debuginfo and attach stacktrace?

Comment 2 Stephen So 2008-03-14 07:14:58 UTC
Created attachment 298019 [details]
trace from nautilus-debuginfo

I haven't done this before so I hope I've attached the right information.

Comment 3 Stephen So 2008-03-21 06:33:21 UTC
I had a crash recently and all my gnome settings went awry, so I deleted all my
config files related to gnome and started afresh.  To my amazement, this bug has
disappeared (i.e. I can now start a terminal without nautilus crashing).  So
maybe this isn't a bug after all but just a corrupted config?

Comment 4 Paul W. Frields 2008-03-21 17:39:53 UTC
I've tried to reproduce the behavior on four different systems here, with no
luck, so I'm guessing you're right.  I'm going to close WORKSFORME right now,
but if you notice the problem recurring, you can reopen the bug.


Note You need to log in before you can comment on or make changes to this bug.