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 571538 - crash in Open Folder: Trying to change directo...
crash in Open Folder: Trying to change directo...
Status: RESOLVED DUPLICATE of bug 503232
Product: nautilus
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-02-12 20:43 UTC by jtanen
Modified: 2009-02-12 20:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description jtanen 2009-02-12 20:43:10 UTC 
Version: 2.22.2

What were you doing when the application crashed?
Trying to change directory name on smb host


Distribution: openSUSE 11.0 (X86-64)
Gnome Release: 2.22.1 2008-06-07 (SUSE)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.20-0.1-default #1 SMP 2008-12-12 20:30:38 +0100 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Synchronicity
Icon Theme: umicons

Memory status: size: 557260800 vsize: 557260800 resident: 25178112 share: 27062272 rss: 52240384 rss_rlim: 1793981440
CPU usage: start_time: 1234461749 rtime: 922 utime: 854 stime: 68 cutime:10 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7fe0180a0700 (LWP 4240)]
[New Thread 0x40d8e950 (LWP 20932)]
[New Thread 0x4158f950 (LWP 13658)]
0x00007fe01047364f in waitpid () from /lib64/libpthread.so.0

+ Trace 212523

Thread 1 (Thread 0x7fe0180a0700 (LWP 4240))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib64/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib64/libglib-2.0.so.0
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 nautilus_file_is_hidden_file
  • #7 nautilus_file_should_show
  • #8 still_should_show_file
  • #9 process_new_files
  • #10 display_pending_callback
  • #11 ??
    from /usr/lib64/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #13 ??
    from /usr/lib64/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 main
  • #0 waitpid
    from /lib64/libpthread.so.0 

----------- .xsession-errors ---------------------
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:47: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:48: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
(nautilus:4240): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `NautilusFile'
(nautilus:4240): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `NautilusFile'
** (nautilus:4240): CRITICAL **: nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed
** (nautilus:4240): CRITICAL **: nautilus_file_is_gone: assertion `NAUTILUS_IS_FILE (file)' failed
** (nautilus:4240): CRITICAL **: nautilus_file_ref: assertion `NAUTILUS_IS_FILE (file)' failed
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:46: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:47: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:48: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2009-02-12 20:48:37 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 503232 ***