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 637008 - crash in Open Folder: nothing
crash in Open Folder: nothing
Status: RESOLVED DUPLICATE of bug 631793
Product: nautilus
Classification: Core
Component: general
2.32.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-12-11 08:15 UTC by hghj
Modified: 2010-12-13 03:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32



Description hghj 2010-12-11 08:15:36 UTC
Version: 2.32.0

What were you doing when the application crashed?
nothing		


Distribution: Ubuntu 10.10 (maverick)
Gnome Release: 2.32.0 2010-09-27 (Ubuntu)
BugBuddy Version: 2.31.92

System: Linux 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 19:48:22 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ambiance
Icon Theme: ubuntu-mono-dark
GTK+ Modules: gnomesegvhandler, canberra-gtk-module

Memory status: size: 142827520 vsize: 142827520 resident: 24010752 share: 16568320 rss: 24010752 rss_rlim: 18446744073709551615
CPU usage: start_time: 1292091296 rtime: 119 utime: 107 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb2f17b70 (LWP 1863)]
[New Thread 0xb7508b70 (LWP 1859)]
0x00e28422 in __kernel_vsyscall ()

	Inferior 1 [process 1858] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** GConf **: gconf_value_free: assertion `value != NULL' failed 


----------- .xsession-errors ---------------------
Connecting to daemon [        ###  ]Connecting to daemon [       ###   ]Connecting to daemon [      ###    ]Connecting to daemon [     ###     ]** (gnome-session:1464): DEBUG: GsmDBusClient: obj_p
** (gnome-session:1464): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1464): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
Connecting to daemon [    ###      ]** (gnome-session:1464): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1464): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1464): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1464): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1464): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:1464): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
Connecting to daemon [   ###       ]Connecting to daemon [  ###        ]Connecting to daemon [ ###         ]Connecting to daemon [###          ]Connecting to daemon [ ###         ]Connecting to 
warning: the debug information found in "/usr/lib/debug//usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch).
Connecting to daemon [    ###      ]Connecting to daemon [     ###     ]Connecting to daemon [      ###    ]Connecting to daemon [       ###   ]Connecting to daemon [        ###  ]Connecting to 
--------------------------------------------------
Comment 1 Akhil Laddha 2010-12-13 03:54:44 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 bug 631793 ***