file browser directs to home directory only

[crashbird]

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.04
DISTRIB_CODENAME=feisty
DISTRIB_DESCRIPTION="Ubuntu 7.04"

When i open the file browser it shows the contents of home directory which is fine. But when i click on some other directory or try to open another folder, the screen blanks for a moment and then again the contents of the home directory is only shown back.

[Basilio Kublik (sourcercito)]

Hi there
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible under a new user account?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[Bipul Islam (bipul-mib)]

I run a ububtu 7.04 fiesty fawn system. It was working fine.
Today i was trying out some upgrades on artwork usplashes etc.
once done i wanted to browse to the directories like /bin or /bin or /usr ,etc
but whenever i click the "<" beside the tab showing my user name , Desk top shows for a few seonds & return to the home folder.
I also get a nautilus-debug-log.txt on my home folder whic goes as thus....

===== BEGIN MILESTONES =====
0x8182d30 2008/04/04 21:10:15.8338 (GLog): file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
0x8182d30 2008/04/04 21:10:15.8339 (USER): debug log dumped due to signal 6
===== END MILESTONES =====
===== BEGIN RING BUFFER =====
0x8182d30 2008/04/04 21:10:10.9988 (USER): window 0x81f8048 open location: old="(none)", new="x-nautilus-desktop:"
0x8182d30 2008/04/04 21:10:11.0881 (USER): create new navigation window=0x81de928
0x8182d30 2008/04/04 21:10:11.0881 (USER): window 0x81de928 open location: old="(none)", new="file:///home/bipul"
0x8182d30 2008/04/04 21:10:11.7062 (USER): change view of window 0x81de928: "file:///home/bipul" to "OAFIID:Nautilus_File_Manager_Icon_View"
0x8182d30 2008/04/04 21:10:11.9244 (USER): finished loading window 0x81f8048: x-nautilus-desktop:
0x8182d30 2008/04/04 21:10:11.9699 (USER): finished loading window 0x81de928: file:///home/bipul
0x8182d30 2008/04/04 21:10:15.5423 (USER): selection changed in window 0x81de928
file:///home/bipul/OFFICE
0x8182d30 2008/04/04 21:10:15.7747 (USER): fm_directory_view_activate_files window=0x81de928
file:///home/bipul/OFFICE
0x8182d30 2008/04/04 21:10:15.7752 (USER): directory view open_location window=0x81de928: file:///home/bipul/OFFICE
0x8182d30 2008/04/04 21:10:15.7752 (USER): window 0x81de928 open location: old="file:///home/bipul", new="file:///home/bipul/OFFICE"
0x8182d30 2008/04/04 21:10:15.7752 (USER): finished loading window 0x81de928: file:///home/bipul
0x8182d30 2008/04/04 21:10:15.8338 (GLog): file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
0x8182d30 2008/04/04 21:10:15.8339 (USER): debug log dumped due to signal 6
===== END RING BUFFER =====

This configuration for the debug log can be re-created
by putting the following in ~/nautilus-debug-log.conf
(use ';' to separate domain names):

[debug log]
max lines=1000

Yester day i also enabled root account login in my system by editing a gdm.conf file
'Allowroot=true'

Guys for some more info:
i can view other folders using $ nautilus <foldername>
but when i try to open even my directories inside my user folder the problem repeats.

[Bipul Islam (bipul-mib)]

I have found some extra info on the bug please look into this....

[Sebastien Bacher (seb128)]

could you try if that's still an issue using hardy?

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.