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 481542 - crash in Computer:
crash in Computer:
Status: RESOLVED DUPLICATE of bug 478212
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-29 09:29 UTC by arktong
Modified: 2007-10-20 04:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description arktong 2007-09-29 09:29:48 UTC
Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 110190592 vsize: 110190592 resident: 27377664 share: 19443712 rss: 27377664 rss_rlim: 4294967295
CPU usage: start_time: 1191055623 rtime: 599 utime: 533 stime: 66 cutime:5 cstime: 3 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 -1209035040 (LWP 2859)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209035040 (LWP 2859))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 nautilus_connect_background_to_file_metadata
  • #11 ??
  • #12 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #18 fm_directory_view_begin_loading
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
    from /lib/libglib-2.0.so.0
  • #23 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #24 ??
    from /lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #26 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (7 sec old) ---------------------
(process:3828): GStreamer-WARNING **: The GStreamer function gst_init_get_option_group() was
	called, but the GLib threading system has not been initialised
	yet, something that must happen before any other GLib function
	is called. The application needs to be fixed so that it calls
	   if (!g_thread_supported ()) g_thread_init(NULL);
	as very first thing in its main() function. Please file a bug
	against this application.
** (nautilus:2859): WARNING **: destroyed file still being monitored
** ERROR **: file nautilus-directory-background.c: line 621 (nautilus_connect_background_to_file_metadata): assertion failed: (NAUTILUS_IS_FILE (old_file))
aborting...
(bug-buddy:3916): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: 第 1 行第 40 個字發生錯誤:元素‘b’已關閉,但開啟中的元素是‘span’
--------------------------------------------------
Comment 1 Christian Kirbach 2007-10-19 22:28:13 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 478212 ***
Comment 2 arktong 2007-10-20 04:40:15 UTC
(In reply to comment #1)
> Thanks for taking the time to report this bug.
> This particular bug has already been reported into our bug tracking system, but
> the maintainers need more information to fix the bug. Could you please answer
> the questions in the other report in order to help the developers?
> 
> 
> *** This bug has been marked as a duplicate of 478212 ***
> 
Hi, do you now still need additional information?
I tried to install the debug packages by following 
http://live.gnome.org/GettingTraces/DistroSpecificInstructions

But then in the web-page of http://live.gnome.org/GettingTraces it was written that 
"After installing the relevant debugging information packages, just make the program crash again. If you cannot do so, please leave a comment and tell us.".
So I would like to ask how to make the program crash again????????? ~~~~~
Thank you for your attention.~