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 562076 - crash in Open Folder: Starting Gnome
crash in Open Folder: Starting Gnome
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-24 00:45 UTC by paulbarbee
Modified: 2008-11-24 20:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description paulbarbee 2008-11-24 00:45:55 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Starting Gnome


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-amd64 #1 SMP Sat Nov 8 18:25:23 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: oxygen

Memory status: size: 361377792 vsize: 361377792 resident: 13279232 share: 10625024 rss: 13279232 rss_rlim: 18446744073709551615
CPU usage: start_time: 1227487495 rtime: 12 utime: 8 stime: 4 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 0x7f538ade6780 (LWP 5832)]
(no debugging symbols found)
0x00007f5385de55ef in waitpid () from /lib/libpthread.so.0

+ Trace 210158

Thread 1 (Thread 0x7f538ade6780 (LWP 5832))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #7 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #8 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #10 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #11 nautilus_module_extension_list_free
  • #12 eel_debug_shut_down
    from /usr/lib/libeel-2-2.20.so
  • #13 ??
  • #14 __libc_start_main
    from /lib/libc.so.6
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
** (gnome-panel:5829): WARNING **: Failed to establish a connection with GDM: No such file or directory
(awn-applet-activation:5862): Gtk-WARNING **: Theme directory scalable/animations/small/16x16 of theme oxygen has no size field
(awn-applet-activation:5862): Gtk-WARNING **: Theme directory scalable/animations/small/22x22 of theme oxygen has no size field
/usr/local/lib/awn/applets/stacks/stacks_icons.py:148: DeprecationWarning: integer argument expected, got float
  gtk.gdk.INTERP_BILINEAR)
/usr/local/lib/awn/applets/stacks/stacks_icons.py:186: GtkWarning: Theme directory scalable/animations/small/16x16 of theme oxygen has no size field
  info = icon_theme.lookup_icon(icon_name, icon_size, gtk.ICON_LOOKUP_USE_BUILTIN)
/usr/local/lib/awn/applets/stacks/stacks_icons.py:186: GtkWarning: Theme directory scalable/animations/small/22x22 of theme oxygen has no size field
  info = icon_theme.lookup_icon(icon_name, icon_size, gtk.ICON_LOOKUP_USE_BUILTIN)
--------------------------------------------------
Comment 1 palfrey 2008-11-24 20:10:43 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 ***