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 537314 - crash in Open Folder: I was accessing a folder...
crash in Open Folder: I was accessing a folder...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-08 21:50 UTC by zpkayak
Modified: 2008-06-09 09:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description zpkayak 2008-06-08 21:50:00 UTC 
Version: 2.20.0

What were you doing when the application crashed?
I was accessing a folder on a windows XP computer on my home network. I just installed Debian on this computer yesterday,	


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 83542016 vsize: 83542016 resident: 21336064 share: 15147008 rss: 21336064 rss_rlim: 4294967295
CPU usage: start_time: 1212961001 rtime: 362 utime: 331 stime: 31 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c17720 (LWP 2631)]
(no debugging symbols found)
0xb7361f91 in waitpid () from /lib/libpthread.so.0

+ Trace 199894

Thread 1 (Thread 0xb6c17720 (LWP 2631))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (8 sec old) ---------------------
** Message: another SSH agent is running at: /tmp/ssh-zZsWxu2553/agent.2553
Window manager warning: Failed to read saved session file /home/gus/.metacity/sessions/default0.ms: Failed to open file '/home/gus/.metacity/sessions/default0.ms': No such file or directory
Initializing gnome-mount extension
seahorse nautilus module initialized
** (gnome-system-monitor:2747): WARNING **: SELinux was found but is not enabled.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2401525 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2401525 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-09 09:35:22 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 522534 ***