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 541521 - crash in Computer: J'essayais d'accéder à u...
crash in Computer: J'essayais d'accéder à u...
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-07-04 09:26 UTC by Cyp
Modified: 2008-07-04 16:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Cyp 2008-07-04 09:26:54 UTC
Version: 2.20.0

What were you doing when the application crashed?
J'essayais d'accéder à un dossier partagé sur un ordinateur sous Vista, via Samba. À savoir que ce bug se reproduit à chaque fois que j'essaye d'y accéder, systématiquement.


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

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome-human

Memory status: size: 81768448 vsize: 81768448 resident: 31469568 share: 17948672 rss: 31469568 rss_rlim: 4294967295
CPU usage: start_time: 1215161387 rtime: 2289 utime: 2046 stime: 243 cutime:205 cstime: 8 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 0xb6be7940 (LWP 2985)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6be7940 (LWP 2985))

  • #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 (9 sec old) ---------------------
not trans
781
m| 438932
not rec
 wlan0: 9029496    9992    0    0    0     0          0         0  1317658    8866    0    0    0     0       0          0
not trans
781
m| 438932
not rec
:images/idle-good-signal-lock.png
|idle-good-signal-lock.png
 wlan0: 9029496    9992    0    0    0     0          0         0  1317658    8866    connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 Pedro Villavicencio 2008-07-04 15:17:02 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!
Comment 2 Cyp 2008-07-04 15:54:35 UTC
Thanks for your answer. Sorry for my bad english.

I can reproduce the crash :

1. Open Nautilus
2. Browse Windows Network
3. Double-clic on the name of Windows workgroup
4. Double-clic on the name of a computer (which is under Vista)
5. Double-clic on one shared folder
6. Crash

Trace with nautilus-dbg package installed :

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

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome-human

Memory status: size: 80130048 vsize: 80130048 resident: 29118464 share: 17539072 rss: 29118464 rss_rlim: 4294967295
CPU usage: start_time: 1215182248 rtime: 515 utime: 485 stime: 30 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b4b940 (LWP 2974)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b4b940 (LWP 2974))

  • #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 istr_hash
    at nautilus-directory-async.c line 170
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (2231 sec old) ---------------------
(firefox-bin:7728): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox-bin:7728): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox-bin:7728): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox-bin:7728): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox-bin:7728): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox-bin:7728): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox-bin:7728): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 3 A. Walton 2008-07-04 16:01:30 UTC
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 ***