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 533312 - crash in Open Folder: accesing to a folder on ...
crash in Open Folder: accesing to a folder on ...
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-05-15 16:43 UTC by jmrxto
Modified: 2008-05-15 19:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description jmrxto 2008-05-15 16:43:08 UTC
Version: 2.20.0

What were you doing when the application crashed?
accesing to a folder on a windows machine using samba "smb://192.168.2.156"


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

System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: default.kde

Memory status: size: 85848064 vsize: 85848064 resident: 31887360 share: 16105472 rss: 31887360 rss_rlim: 4294967295
CPU usage: start_time: 1210869714 rtime: 131 utime: 125 stime: 6 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bec720 (LWP 32150)]
[New Thread 0xb6b30b90 (LWP 32185)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6bec720 (LWP 32150))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (30827 sec old) ---------------------
|idle-signal.png
 wlan0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
:images/idle-signal.png
|idle-signal.png
 wlan0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
:images/idle-signal.png
|idle-signal.png
 wlan0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
:images/idle-signal.png
|idle-signal.png
 wlan0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
:images/idle-signal.png
|idle-signal.png
 wlan0:       0       0    0    0    0     0          0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Paweł Paprota 2008-05-15 19:31:00 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 ***