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 518362 - crash in Open Folder: Right clicked on folder
crash in Open Folder: Right clicked on folder
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-24 04:43 UTC by whumphreys
Modified: 2008-02-24 11:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description whumphreys 2008-02-24 04:43:56 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Right clicked on folder


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-7.fc7xen #1 SMP Tue Feb 12 12:32:24 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 84217856 vsize: 84217856 resident: 31199232 share: 20475904 rss: 31199232 rss_rlim: 4294967295
CPU usage: start_time: 1203524378 rtime: 438 utime: 381 stime: 57 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208490272 (LWP 26296)]
0x00de0402 in __kernel_vsyscall ()

+ Trace 190256

Thread 1 (Thread -1208490272 (LWP 26296))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/nosegneg/libc.so.6
  • #6 abort
    from /lib/i686/nosegneg/libc.so.6
  • #7 IA__g_logv
  • #8 IA__g_log
  • #9 IA__g_assert_warning
  • #10 gtk_list_store_compare_func
    at gtkliststore.c line 1677
  • #11 ??
  • #12 ??
  • #13 g_sequence_sort_changed_iter
  • #14 gtk_list_store_sort_iter_changed
    at gtkliststore.c line 1758
  • #15 IA__gtk_list_store_set_valist
    at gtkliststore.c line 901
  • #16 IA__gtk_list_store_set
    at gtkliststore.c line 934
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 g_idle_dispatch
    at gmain.c line 4132
  • #24 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #25 g_main_context_iterate
    at gmain.c line 2694
  • #26 IA__g_main_loop_run
    at gmain.c line 2898
  • #27 IA__gtk_main
    at gtkmain.c line 1144
  • #28 main
  • #0 __kernel_vsyscall 






Comment 1


Cosimo Cecchi





          2008-02-24 11:02:20 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 440988 ***