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 336919 - nautilus crashed after creating a folder
nautilus crashed after creating a folder
Status: RESOLVED DUPLICATE of bug 320267
Product: nautilus
Classification: Core
Component: general
2.12.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-02 13:08 UTC by zvobug
Modified: 2006-04-02 15:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description zvobug 2006-04-02 13:08:14 UTC
Distribution: Debian testing/unstable
Package: nautilus
Severity: Normal
Version: GNOME2.12.3 2.12.2
Gnome-Distributor: Debian
Synopsis: nautilus crashed after creating a folder
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.12.2
BugBuddy-GnomeVersion: 2.0 (2.12.1)
Description:
Description of the crash:
created folder with shift-ctrl-n
renamed it k750i (name of my digital camera)
then tried to find it in the list
bingo

Steps to reproduce the crash:
1. created folder with shift-ctrl-n
2. renamed it k750i (name of my digital camera)
3. then tried to find it in the list


Expected Results:
should be obvious

How often does this happen?
well, only once, but I had the phone plugged in the USB...

Additional Information:
I had the phone connected to my computer through USB cable...


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227917632 (LWP 5470)]
[New Thread -1245844560 (LWP 11281)]
[New Thread -1243632720 (LWP 5492)]
[New Thread -1243370576 (LWP 5491)]
[New Thread -1243108432 (LWP 5490)]
[New Thread -1238328400 (LWP 5478)]
(no debugging symbols found)
0xb74c7221 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread -1227917632 (LWP 5470))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_tree_model_get_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 gtk_tree_model_get
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 fm_list_view_get_type
  • #6 gtk_tree_view_column_cell_set_cell_data
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 _gtk_tree_view_queue_draw_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gdk_window_clear_area_e
    from /usr/lib/libgdk-x11-2.0.so.0
  • #17 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #18 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #19 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug created by bug-buddy at 2006-04-02 13:08 -------


Unknown version 2.12.2 in product nautilus.  Setting version to "2.12.x".

Comment 1 Christian Kirbach 2006-04-02 15:00:30 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 320267 ***