GNOME Bugzilla – Bug 137519
nautilus crash when UIM gtk input method is available
Last modified: 2004-12-22 21:47:04 UTC
-install uim input method on your system http://www.freedesktop.org/Software/uim -make sure uim server is not running (killall uim-helper-serv) -start nautilus => crash. nautiluys doesn't crash if uim server is already running. Stacktrace using GDB : Starting program: /mnt/gnome/prefix24/bin/nautilus --no-desktop [Thread debugging using libthread_db enabled] [New Thread 1089443168 (LWP 25277)] [New Thread 1091189680 (LWP 25281)] [New Thread 1091455920 (LWP 25282)] [New Thread 1091722160 (LWP 25283)] [New Thread 1091988400 (LWP 25284)] [New Thread 1092254640 (LWP 25285)] [New Thread 1092520880 (LWP 25286)] [New Thread 1092787120 (LWP 25287)] Detaching after fork from child process 25290. ** (nautilus:25277): WARNING **: Throbber activation exception 'Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'' ** (nautilus:25277): WARNING **: A view failed. The UI will handle this with a dialog but this should be debugged. Program received signal SIGSEGV, Segmentation fault.
+ Trace 45226
Thread 1089443168 (LWP 25277)
(gdb) print *view $2 = {parent = {parent_slot = {container = {widget = {object = { parent_instance = {g_type_instance = {g_class = 0x83d72b8}, ref_count = 1088614920, qdata = 0x0}, flags = 2098720}, private_flags = 15360, state = 0 '\0', saved_state = 0 '\0', name = 0x0, style = 0x0, requisition = {width = 0, height = 0}, allocation = {x = -1, y = -1, width = 1, height = 1}, window = 0x0, parent = 0x0}, focus_child = 0x0, border_width = 0, need_resize = 0, resize_mode = 0, reallocate_redraws = 0, has_focus_chain = 0}, child = 0x0}}, details = 0x50}
It was a bug in uim which is using exit instead of _exit, causing ORBit exit handler to be called.. I've reported it to uim authors.