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 526420 - crash in Computer: j'ouvrais un dossier sur...
crash in Computer: j'ouvrais un dossier sur...
Status: RESOLVED DUPLICATE of bug 425157
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-05 23:34 UTC by corbeille.a.pub
Modified: 2008-04-06 10:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description corbeille.a.pub 2008-04-05 23:34:31 UTC 
Version: 2.20.0

What were you doing when the application crashed?
j'ouvrais un dossier sur mon serveur dédié, en passant par l'option "se connecter à un serveur distant" de gnome. Je suis sous Debian SID - mon serveur est sous Debian ETCH


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-486 #1 Thu Mar 27 17:00:17 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Elegant Brit
Icon Theme: ALLBLACK

Memory status: size: 91738112 vsize: 91738112 resident: 31100928 share: 17993728 rss: 31100928 rss_rlim: 4294967295
CPU usage: start_time: 1207427788 rtime: 1235 utime: 1178 stime: 57 cutime:0 cstime: 3 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 0xb6c08720 (LWP 3480)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 194335

Thread 1 (Thread 0xb6c08720 (LWP 3480))

  • #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 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #10 g_log
    from /usr/lib/libglib-2.0.so.0
  • #11 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #12 ??
  • #13 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(nautilus:3480): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(nautilus:3480): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
** (nautilus:3480): CRITICAL **: nautilus_file_monitor_remove: assertion `NAUTILUS_IS_FILE (file)' failed
** (nautilus:3480): CRITICAL **: nautilus_file_cancel_call_when_ready: assertion `NAUTILUS_IS_FILE (file)' failed
** (nautilus:3480): CRITICAL **: nautilus_file_monitor_remove: assertion `NAUTILUS_IS_FILE (file)' failed
** (nautilus:3480): CRITICAL **: nautilus_file_unref: assertion `NAUTILUS_IS_FILE (file)' failed
** ERROR **: file nautilus-directory-background.c: line 616 (nautilus_connect_background_to_file_metadata): assertion failed: (NAUTILUS_IS_FILE (old_file))
aborting...
--------------------------------------------------
Comment 1 Gianluca Borello 2008-04-06 10:20:07 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 425157 ***