After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 537298 - Nautilus freezes when trying to open Trash on the sidebar
Nautilus freezes when trying to open Trash on the sidebar
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: [obsolete] Sidebar
2.22.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on: 528600
Blocks:
 
 
Reported: 2008-06-08 19:54 UTC by Serkan
Modified: 2009-03-21 18:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Serkan 2008-06-08 19:54:50 UTC 
Please describe the problem:
If you open Nautilus with root account, and click the Trash on the sidebar, it freezes.

Steps to reproduce:
1. Get root rights
2. Open Nautilus
3. Click Trash on the sidebar


Actual results:
Nautilus freezes.

Expected results:
Open the Trash dir. 

Does this happen every time?
Yes.

Other information:
Comment 1 Baptiste Mille-Mathias 2008-06-08 19:57:16 UTC 
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!
Comment 2 Münir Ekinci 2008-06-08 20:06:05 UTC 
I can produce this bug, too
Comment 3 Serkan 2008-06-08 20:41:57 UTC 
Ok, I'll add the requested backtrace as quick as possible.
Comment 4 Serkan 2008-06-08 21:49:33 UTC 
I am so sorry but i can't get a stack trace with gdb. gdb does not give any information about this. I tried it as multithreaded and non-multithreded way.  Additionally if it takes a little bit long whole system freezes. 

By the way, I am trying to get the trace as "root". So special circumstances is not working in here. I logged in root and tried it, there is no problem with that. If you open nautilus with sudo or with root rights it is happening. 

Is there any other way i can get stack trace?
Comment 5 Emrah Ergin 2008-06-08 23:22:50 UTC 
One more unhappy user... In addition to experiencing the same bug, I can confirm that the free memory and swap space starts filling until the computer becomes unresponsive. So, I assume there is "memory leakage", too.
Comment 6 Sebastien Bacher 2008-06-10 13:42:03 UTC 
using "sudo dbus-launch nautilus" workaround the issue, in the buggy case gvfs is not started and nautilus seems to loop somewhere around nautilus_path_bar_update_path nautilus-pathbar.c
Comment 7 A. Walton 2008-06-10 13:50:23 UTC 
Marking dependency on bug 528600 per the last comment (the infinite loop in this case is happening as Nautilus spins forever trying to get to root on a GDummyFile). That might actually be the only necessary fix.
Comment 8 A. Walton 2008-06-11 18:11:45 UTC 
Verifying that the GLib fix solves this issue, however, I still think that the loop that's causing this is silly. We should stop after some sane number of iterations (a good guess would be MAX_PATH).
Comment 9 Cosimo Cecchi 2009-03-21 18:52:57 UTC 
The loop looks legal to me, as walking up the tree until we get NULL is part of the GFile API contract. I'll close this as OBSOLETE.