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 480960 - crash in Open Folder: Trying to get info (righ...
crash in Open Folder: Trying to get info (righ...
Status: RESOLVED DUPLICATE of bug 479483
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-27 14:04 UTC by r33kk0
Modified: 2007-10-03 11:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description r33kk0 2007-09-27 14:04:48 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Trying to get info (right-click in nautilus) about a plain text file. Info window didn't have the time to appear before crash. Same crash happens also (at least) with jpegs and tiffs (but not while getting info about a directory, a tarball or a directory).


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21070821-rq #1 SMP Tue Aug 21 21:27:44 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tangerine

Memory status: size: 71614464 vsize: 71614464 resident: 23064576 share: 13893632 rss: 23064576 rss_rlim: 4294967295
CPU usage: start_time: 1190901622 rtime: 366 utime: 321 stime: 45 cutime:0 cstime: 0 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227254096 (LWP 7380)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 165923

Thread 1 (Thread -1227254096 (LWP 7380))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/cmov/libc.so.6
  • #6 abort
    from /lib/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_list_item_new_with_label
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 g_sequence_iter_is_begin
  • #12 g_sequence_iter_is_begin
  • #13 g_sequence_sort_changed_iter
  • #14 gtk_list_item_new_with_label
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_list_store_set_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_list_store_set
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 eel_mime_application_chooser_get_type
    from /usr/lib/libeel-2-2.18.so
  • #18 eel_mime_application_chooser_new
    from /usr/lib/libeel-2-2.18.so
  • #19 fm_properties_window_get_type
  • #20 nautilus_directory_schedule_dequeue_pending
  • #21 nautilus_directory_async_state_changed
  • #22 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #26 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
** 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
Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.0/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store))
aborting...
--------------------------------------------------
Comment 1 André Klapper 2007-10-03 11:09:04 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 479483 ***