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 399130 - crash in CD/DVD Creator: I was doing a search in ...
crash in CD/DVD Creator: I was doing a search in ...
Status: RESOLVED DUPLICATE of bug 363856
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-21 20:13 UTC by paretoj
Modified: 2007-01-22 17:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description paretoj 2007-01-21 20:13:34 UTC
What were you doing when the application crashed?
I was doing a search in my home directory for '17', without quotes.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 103632896 vsize: 0 resident: 103632896 share: 0 rss: 31375360 rss_rlim: 0
CPU usage: start_time: 1169410241 rtime: 0 utime: 275 stime: 0 cutime:251 cstime: 0 timeout: 24 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227082064 (LWP 6657)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227082064 (LWP 6657))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 nautilus_file_get_uri
  • #5 nautilus_file_get_parent_uri
  • #6 nautilus_file_get_parent_uri
  • #7 fm_directory_view_bump_zoom_level
  • #8 fm_directory_view_bump_zoom_level
  • #9 fm_directory_view_bump_zoom_level
  • #10 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #11 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #12 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #13 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #14 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #15 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #16 POA_Nautilus_MetafileMonitor__init
  • #17 fm_directory_view_bump_zoom_level
  • #18 fm_directory_view_bump_zoom_level
  • #19 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #24 nautilus_directory_async_state_changed
  • #25 nautilus_marshal_BOOLEAN__POINTER
  • #26 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #31 nautilus_marshal_BOOLEAN__POINTER
  • #32 nautilus_marshal_BOOLEAN__POINTER
  • #33 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #34 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #35 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #36 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #37 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 POA_Nautilus_MetafileMonitor__init
  • #39 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #40 ??
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2007-01-22 17:40:12 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 363856 ***