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 537223 - crash in File Browser: Trying to access a windo...
crash in File Browser: Trying to access a windo...
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 09:45 UTC by fgparedes
Modified: 2008-06-08 12:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description fgparedes 2008-06-08 09:45:59 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Trying to access a windows share


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 548540416 vsize: 548540416 resident: 53174272 share: 18403328 rss: 53174272 rss_rlim: 18446744073709551615
CPU usage: start_time: 1212916401 rtime: 589 utime: 549 stime: 40 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 0x2b12baf75240 (LWP 4023)]
[New Thread 0x40800950 (LWP 4641)]
(no debugging symbols found)
0x00002b12b446bedf in waitpid () from /lib/libpthread.so.0

+ Trace 199851

Thread 1 (Thread 0x2b12baf75240 (LWP 4023))

  • #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 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (38 sec old) ---------------------
** (gnome-settings-daemon:3528): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Non hai tal ficheiro ou directorio
** (gnome-settings-daemon:3528): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Non hai tal ficheiro ou directorio
** (gnome-settings-daemon:3528): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Non hai tal ficheiro ou directorio
** (gnome-settings-daemon:3528): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Non hai tal ficheiro ou directorio
** (gnome-settings-daemon:3528): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Non hai tal ficheiro ou directorio
** (gnome-settings-daemon:3528): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Non hai tal ficheiro ou directorio
** (gnome-settings-daemon:3528): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Non hai tal ficheiro ou directorio
** (gnome-settings-daemon:3528): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Non hai tal ficheiro ou directorio
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-08 12:24:52 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 ***