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 566930 - crash in Open Folder: i was closing it through...
crash in Open Folder: i was closing it through...
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
2.25.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-07 18:28 UTC by Nikola Yanev
Modified: 2009-01-08 12:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Nikola Yanev 2009-01-07 18:28:14 UTC 
Version: 2.25.2

What were you doing when the application crashed?
i was closing it through close button after copying a file in dir.


Distribution: Ubuntu 9.04 (jaunty)
Gnome Release: 2.25.4 2009-01-06 (Ubuntu)
BugBuddy Version: 2.24.1

System: Linux 2.6.28-4-generic #9-Ubuntu SMP Tue Jan 6 19:34:01 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10599003
Selinux: No
Accessibility: Disabled
GTK+ Theme: eGTK
Icon Theme: elementary

Memory status: size: 189501440 vsize: 189501440 resident: 38182912 share: 26292224 rss: 38182912 rss_rlim: 18446744073709551615
CPU usage: start_time: 1231352808 rtime: 795 utime: 736 stime: 59 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb705c750 (LWP 16337)]
[New Thread 0xab4f9b90 (LWP 16355)]
(no debugging symbols found)
0xb80cb430 in __kernel_vsyscall ()

+ Trace 211366

Thread 1 (Thread 0xb705c750 (LWP 16337))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #8 ??
    from /usr/lib/nautilus/extensions-2.0/libnautilus-actions.so
  • #9 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/nautilus/extensions-2.0/libnautilus-actions.so
  • #11 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #16 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(nautilus:16337): Gtk-WARNING **: Error parsing gtk-icon-sizes string:
	'panel-menu=24,24:panel=24:gtk-small-toolbar=16,16:gtk-large-toolbar=24,24:gtk-button=24,24'
** (nautilus:16337): WARNING **: Unable to add monitor: Not supported
seahorse nautilus module shutdown
/home/gericom/.themes/eGTK/gtk-2.0/panel.rc:54: Unable to locate image file in pixmap_path: "Menubar/menubar-item.png"
/home/gericom/.themes/eGTK/gtk-2.0/panel.rc:57: Background image options specified without filename
/home/gericom/.themes/eGTK/gtk-2.0/panel.rc:107: Unable to locate image file in pixmap_path: "Menubar/menubar-item.png"
/home/gericom/.themes/eGTK/gtk-2.0/panel.rc:110: Background image options specified without filename
/home/gericom/.themes/eGTK/gtk-2.0/gtkrc:147: Unable to locate image file in pixmap_path: "Menu/menubar.png"
/home/gericom/.themes/eGTK/gtk-2.0/gtkrc:150: Background image options specified without filename
(bug-buddy:16363): Gtk-WARNING **: Error parsing gtk-icon-sizes string:
	'panel-menu=24,24:panel=24:gtk-small-toolbar=16,16:gtk-large-toolbar=24,24:gtk-button=24,24'
--------------------------------------------------
Comment 1 palfrey 2009-01-08 12:13:02 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 480179 ***