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 393467 - crash in gtk_file_info_get_is_folder
crash in gtk_file_info_get_is_folder
Status: RESOLVED DUPLICATE of bug 363472
Product: gtk+
Classification: Platform
Component: Widget: Other
2.10.x
Other All
: High critical
: ---
Assigned To: gtk-bugs
gtk-bugs
: 395938 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-01-06 11:16 UTC by victorhantelmann
Modified: 2007-01-31 10:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description victorhantelmann 2007-01-06 11:16:10 UTC
What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:31:29 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors (8925 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------

Memory status: size: 125300736 vsize: 0 resident: 125300736 share: 0 rss: 26099712 rss_rlim: 0
CPU usage: start_time: 1168081310 rtime: 0 utime: 3455 stime: 0 cutime:3185 cstime: 0 timeout: 270 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/glade-2'

(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 -1208600880 (LWP 28922)]
(no debugging symbols found)
0x005da402 in __kernel_vsyscall ()

Thread 1 (Thread -1208600880 (LWP 28922))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_file_info_get_is_folder
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_file_chooser_button_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_tree_model_filter_convert_child_iter_to_iter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_tree_model_sort_convert_iter_to_child_iter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #10 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #13 gtk_tree_model_row_inserted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_file_info_render_icon
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__POINTER
    from /lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_by_name
    from /lib/libgobject-2.0.so.0
  • #20 fs_module_create
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #21 gnome_vfs_stat_to_file_info
    from /usr/lib/libgnomevfs-2.so.0
  • #22 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #23 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #24 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #26 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #27 g_cclosure_marshal_VOID__OBJECT
  • #28 __libc_start_main
    from /lib/libc.so.6
  • #29 g_cclosure_marshal_VOID__OBJECT
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2007-01-18 20:52:47 UTC
*** Bug 395938 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2007-01-18 20:53:16 UTC
looks like a gtk+ issue
Comment 3 Sebastien Bacher 2007-01-31 10:28:35 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 363472 ***