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 527912 - crash in File Browser: i was exploring a window...
crash in File Browser: i was exploring a window...
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-04-13 19:17 UTC by gomnaz
Modified: 2008-04-13 23:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description gomnaz 2008-04-13 19:17:54 UTC 
Version: 2.20.0

What were you doing when the application crashed?
i was exploring a windows shared directory using smb protocol


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

System: Linux 2.6.24.4-apollo #1 SMP Wed Apr 2 12:21:18 CEST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaElegant
Icon Theme: gTangish-2.0

Memory status: size: 104890368 vsize: 104890368 resident: 47091712 share: 16621568 rss: 47091712 rss_rlim: 4294967295
CPU usage: start_time: 1208107141 rtime: 1464 utime: 1399 stime: 65 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bc1720 (LWP 3587)]
(no debugging symbols found)
0xb75d7f91 in waitpid () from /lib/libpthread.so.0

+ Trace 195133

Thread 1 (Thread 0xb6bc1720 (LWP 3587))

  • #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 ??
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (3983 sec old) ---------------------
 wlan0: 1626460    3416    0    0    0     0          0         0    83455     702    0    0    0     0       0          0
not trans
628
m| 173931
:images/idle-good-signal-lock.png
|receiving-good-signal-lock.png
 wlan0: 1626460    3416    0    0    0     0          0         0    83455     702    0    0    0     0       0          0
not trans
628
m| 173931
not rec
:images/receiving-good-signal-lock.png
|idle-good-signal-lock.png
 wlan0: 1626580    3418    0    0    0     0          0         0    83455     702    0    0    0     0       0  
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Gianluca Borello 2008-04-13 23:20:43 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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