Bug 107288 – nautilus crash after editing mime info

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 107288 - nautilus crash after editing mime info


Summary:	nautilus crash after editing mime info


Status:	RESOLVED DUPLICATE of bug 97257

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-02-28 20:16 UTC by Steve Przepiora
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Steve Przepiora 2003-02-28 20:08:39 UTC

Package: nautilus
Severity: normal
Version: 2.0.6
Synopsis: nautilus crash after editing mime info
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
I was editing mime-types located in /usr/share/mime-info. I opened
nautilus on my home directory where a file of the mime type in question
is located and nautilu crashed.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?
every time I did this

Additional Information:




Debugging Information:

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

(no debugging symbols found)...[New Thread 8192 (LWP 13906)]
[New Thread 16385 (LWP 13909)]
[New Thread 8194 (LWP 13910)]
[New Thread 16387 (LWP 13911)]
[New Thread 24580 (LWP 13912)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 34399

Thread 1 (Thread 8192 (LWP 13906))

#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 waitpid
from /lib/i686/libpthread.so.0
#3 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#4 __pthread_sighandler
from /lib/i686/libpthread.so.0
#5 <signal handler called>
#6 kill
from /lib/i686/libc.so.6
#7 raise
from /lib/i686/libpthread.so.0
#8 abort
from /lib/i686/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 get_bonobo_window
#12 create_popup_menu
#13 fm_directory_view_pop_up_selection_context_menu
#14 icon_container_context_click_selection_callback
#15 g_cclosure_marshal_VOID__POINTER
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 button_release_event
at nautilus-icon-container.c line 2834
#21 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_widget_event_internal
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 gdk_event_dispatch
from /usr/lib/libgdk-x11-2.0.so.0
#31 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#34 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#35 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#36 main
#37 __libc_start_main
from /lib/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-28 15:08 -------

Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 John Fleck 2003-03-01 03:39:42 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 97257 ***