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 445429 - crash in Home Folder: flasch
crash in Home Folder: flasch
Status: RESOLVED DUPLICATE of bug 436071
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 454569 457201 457202 457727 459398 459404 459406 459408 459409 459410 459412 459414 459415 459419 459420 459421 459422 459424 459425 459426 459427 459433 459434 459435 459438 459453 459774 459778 466982 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-08 09:17 UTC by h.boekemans
Modified: 2007-08-22 19:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18

Attachments
crash trace with debug symbols attached (25.79 KB, text/plain)
2007-07-08 01:22 UTC, phil 		Details

Description h.boekemans 2007-06-08 09:17:18 UTC 
What were you doing when the application crashed?
flasch


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 88260608 vsize: 88260608 resident: 33308672 share: 18563072 rss: 33308672 rss_rlim: 4294967295
CPU usage: start_time: 1181292515 rtime: 716 utime: 650 stime: 66 cutime:0 cstime: 1 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 -1208178976 (LWP 3820)]
(no debugging symbols found)
0x0043d402 in __kernel_vsyscall ()

+ Trace 139317

Thread 1 (Thread -1208178976 (LWP 3820))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 nautilus_file_compare_for_sort
  • #6 fm_icon_view_compare_files
  • #7 ??
  • #8 ??
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #22 nautilus_directory_emit_done_loading
  • #23 ??
  • #24 ??
  • #25 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
    from /lib/libglib-2.0.so.0
  • #32 ??
    from /lib/libpthread.so.0
  • #33 ??
  • #34 ??
    from /lib/libpthread.so.0
  • #35 ??
  • #36 ??
  • #37 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 g_slice_alloc
    from /lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall 


----------- .xsession-errors (186 sec old) ---------------------
WARNING: Please enter a valid installation path.
Please enter the installation path of the Mozilla, SeaMonkey,
or Firefox browser (i.e., /usr/lib/mozilla): dir= /root/Bureaublad/install_flash_player_9_linux/
WARNING: Please enter a valid installation path.
Please enter the installation path of the Mozilla, SeaMonkey,
or Firefox browser (i.e., /usr/lib/mozilla): dir= /root/Bureaublad/install_flash_player_9_linux/
WARNING: Please enter a valid installation path.
Please enter the installation path of the Mozilla, SeaMonkey,
or Firefox browser (i.e., /usr/lib/mozilla): 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-09 01:34:23 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 more useful description to this bug.

Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 palfrey 2007-07-07 21:39:51 UTC 
*** Bug 454569 has been marked as a duplicate of this bug. ***
Comment 3 phil 2007-07-08 01:21:51 UTC 
As mentioned in 454569: I scrolled to "gnome-terminal" in the "Run" (Alt+F2) history, and accidentially hit # then RETURN, which executed "#gnome-terminal". Nautilus started with an empty window and immediately crashed.

This is 100% reproducable.

Attaches is a trace with gtk2, glib2, gnome-vfs2 and nautilus -debuginfo RPMs installed. Let me know if you need more.
Comment 4 phil 2007-07-08 01:22:30 UTC 
Created attachment 91386 [details]
crash trace with debug symbols attached
Comment 5 Damien Durand 2007-07-16 15:58:23 UTC 
*** Bug 457201 has been marked as a duplicate of this bug. ***
Comment 6 Damien Durand 2007-07-16 15:59:10 UTC 
*** Bug 457202 has been marked as a duplicate of this bug. ***
Comment 7 Reinout van Schouwen 2007-07-24 21:27:49 UTC 
*** Bug 459398 has been marked as a duplicate of this bug. ***
Comment 8 Reinout van Schouwen 2007-07-24 21:28:06 UTC 
*** Bug 459404 has been marked as a duplicate of this bug. ***
Comment 9 Reinout van Schouwen 2007-07-24 21:28:16 UTC 
*** Bug 459406 has been marked as a duplicate of this bug. ***
Comment 10 Reinout van Schouwen 2007-07-24 21:28:33 UTC 
*** Bug 459408 has been marked as a duplicate of this bug. ***
Comment 11 Reinout van Schouwen 2007-07-24 21:28:48 UTC 
*** Bug 459409 has been marked as a duplicate of this bug. ***
Comment 12 Reinout van Schouwen 2007-07-24 21:29:08 UTC 
*** Bug 459410 has been marked as a duplicate of this bug. ***
Comment 13 Reinout van Schouwen 2007-07-24 21:29:18 UTC 
*** Bug 459412 has been marked as a duplicate of this bug. ***
Comment 14 Reinout van Schouwen 2007-07-24 21:31:08 UTC 
*** Bug 459434 has been marked as a duplicate of this bug. ***
Comment 15 Reinout van Schouwen 2007-07-24 21:32:55 UTC 
Phil's backtrace is matched to bug 363856 but I'm not sure it's the same bug.
Comment 16 Reinout van Schouwen 2007-07-24 21:34:09 UTC 
*** Bug 459414 has been marked as a duplicate of this bug. ***
Comment 17 Reinout van Schouwen 2007-07-24 21:34:21 UTC 
*** Bug 459415 has been marked as a duplicate of this bug. ***
Comment 18 Reinout van Schouwen 2007-07-24 21:35:50 UTC 
*** Bug 459419 has been marked as a duplicate of this bug. ***
Comment 19 Reinout van Schouwen 2007-07-24 21:36:08 UTC 
*** Bug 459420 has been marked as a duplicate of this bug. ***
Comment 20 Reinout van Schouwen 2007-07-24 21:36:21 UTC 
*** Bug 459421 has been marked as a duplicate of this bug. ***
Comment 21 Reinout van Schouwen 2007-07-24 21:38:01 UTC 
*** Bug 459422 has been marked as a duplicate of this bug. ***
Comment 22 Reinout van Schouwen 2007-07-24 21:38:18 UTC 
*** Bug 459424 has been marked as a duplicate of this bug. ***
Comment 23 Reinout van Schouwen 2007-07-24 21:38:31 UTC 
*** Bug 459425 has been marked as a duplicate of this bug. ***
Comment 24 Reinout van Schouwen 2007-07-24 21:38:46 UTC 
*** Bug 459426 has been marked as a duplicate of this bug. ***
Comment 25 Reinout van Schouwen 2007-07-24 21:39:00 UTC 
*** Bug 459427 has been marked as a duplicate of this bug. ***
Comment 26 Reinout van Schouwen 2007-07-24 21:39:14 UTC 
*** Bug 459433 has been marked as a duplicate of this bug. ***
Comment 27 Reinout van Schouwen 2007-07-24 21:39:42 UTC 
*** Bug 459435 has been marked as a duplicate of this bug. ***
Comment 28 Reinout van Schouwen 2007-07-24 21:39:52 UTC 
*** Bug 459438 has been marked as a duplicate of this bug. ***
Comment 29 Reinout van Schouwen 2007-07-24 21:40:02 UTC 
*** Bug 459453 has been marked as a duplicate of this bug. ***
Comment 30 Reinout van Schouwen 2007-07-24 21:41:50 UTC 
*** Bug 459774 has been marked as a duplicate of this bug. ***
Comment 31 Reinout van Schouwen 2007-07-24 21:43:00 UTC 
*** Bug 459778 has been marked as a duplicate of this bug. ***
Comment 32 André Klapper 2007-07-26 19:14:03 UTC 
we still need a better stacktrace
Comment 33 André Klapper 2007-07-26 19:14:10 UTC 
*** Bug 457727 has been marked as a duplicate of this bug. ***
Comment 34 Reinout van Schouwen 2007-07-26 19:57:44 UTC 
Andre: the trace from comment #4 isn't sufficient?
Comment 35 phil 2007-07-27 10:10:46 UTC 
Tell me how to make a better backtrace than the one I attached (see comments #3/4) and I will.
Comment 36 Susana 2007-08-22 18:41:42 UTC 
*** Bug 466982 has been marked as a duplicate of this bug. ***
Comment 37 André Klapper 2007-08-22 19:11:59 UTC 
from comment 4 of this report:

+ Trace 157194

  • #3 <signal handler called>
  • #4 compare_by_display_name
    at nautilus-file.c line 1828
  • #5 nautilus_file_compare_for_sort
    at nautilus-file.c line 2181
  • #6 fm_icon_view_compare_files
    at fm-icon-view.c line 2044
  • #7 compare_files
    at fm-icon-view.c line 2056
  • #8 compare_files_cover
    at fm-directory-view.c line 2681
  • #9 g_list_sort_real
    at glist.c line 583
  • #10 g_list_sort_real
    at glist.c line 629
  • #11 g_list_sort_real
    at glist.c line 629
  • #12 g_list_sort_real
    at glist.c line 629
  • #13 g_list_sort_real
    at glist.c line 629
  • #14 sort_files
    at fm-directory-view.c line 2688
  • #15 process_new_files
    at fm-directory-view.c line 2766
  • #16 done_loading_callback
    at fm-directory-view.c line 3174
  • #17 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #18 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #21 IA__g_signal_emit
    at gsignal.c line 2243
  • #22 nautilus_directory_emit_done_loading
    at nautilus-directory.c line 802
  • #23 dequeue_pending_idle_callback
    at nautilus-directory-async.c line 914
  • #24 directory_load_callback
    at nautilus-directory-async.c line 1041
  • #25 dispatch_load_directory_callback
    at gnome-vfs-job.c line 237
  • #26 dispatch_job_callback
    at gnome-vfs-job.c line 562
  • #27 g_idle_dispatch
    at gmain.c line 3928
  • #28 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #29 g_main_context_iterate
    at gmain.c line 2677
  • #30 IA__g_main_loop_run
    at gmain.c line 2881
  • #31 IA__gtk_main
    at gtkmain.c line 1154
  • #32 main
    at nautilus-main.c line 548 






Comment 38


André Klapper





          2007-08-22 19:43:20 UTC
        



this is *exactly* the same trace as bug 436071, but i am not sure whether bug 436071 is a duplicate of bug 324365

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