Bug 453038 – crash in File Browser: Eclipse에서 c/c++ 프로젝트 속성을...

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 453038 - crash in File Browser: Eclipse에서 c/c++ 프로젝트 속성을...


Summary:	crash in File Browser: Eclipse에서 c/c++ 프로젝트 속성을...


Status:	RESOLVED DUPLICATE of bug 433983

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-02 08:35 UTC by kbs93
Modified:	2007-07-02 20:23 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description kbs93 2007-07-02 08:35:44 UTC

Version: 2.18.1

What were you doing when the application crashed?
Eclipse에서 c/c++ 프로젝트 속성을 변경하고 있어습니다.
 - c/c++ 폴더 속성을 테스트 하였습니다.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 99168256 vsize: 99168256 resident: 33009664 share: 20627456 rss: 33009664 rss_rlim: 4294967295
CPU usage: start_time: 1183360204 rtime: 453 utime: 154 stime: 299 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 -1208535328 (LWP 2472)]
[New Thread -1273746544 (LWP 3199)]
(no debugging symbols found)
0x00fc2402 in __kernel_vsyscall ()

+ Trace 145201

Thread 1 (Thread -1208535328 (LWP 2472))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 ??
#11 gtk_tree_model_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_tree_model_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_tree_row_reference_free
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_tree_view_set_cursor_on_cell
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_tree_view_set_cursor
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
#23 ??
from /lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#25 ??
from /lib/libglib-2.0.so.0
#26 g_main_loop_run
from /lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
The imcontext has not been registered yet
Failed to deregister an IMContext
The imcontext has not been registered yet
Failed to deregister an IMContext
The imcontext has not been registered yet
Failed to deregister an IMContext
The imcontext has not been registered yet
Failed to deregister an IMContext
The imcontext has not been registered yet
Failed to deregister an IMContext
The imcontext has not been registered yet
Failed to deregister an IMContext
** ERROR **: file fm-tree-model.c: line 1527 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0)
aborting...
--------------------------------------------------

Comment 1 Christian Kirbach 2007-07-02 20:23:10 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 433983 ***