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 652445 - crash in Open Folder: I was quiting gnome
crash in Open Folder: I was quiting gnome
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
1.0.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 652319 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-06-13 11:06 UTC by dominique.michel
Modified: 2011-06-13 11:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Description dominique.michel 2011-06-13 11:06:43 UTC 
Version: 2.32.2.1

What were you doing when the application crashed?
I was quiting gnome


Distribution: Gentoo Base System release 2.0.2
Gnome Release: 2.32.1 2011-04-30 (Gentoo)
BugBuddy Version: 2.32.0

System: Linux 2.6.37-gentoo-3Dnew #4 SMP PREEMPT Sun Apr 24 02:42:56 CEST 2011 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 11002000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomesegvhandler, canberra-gtk-module

Memory status: size: 675368960 vsize: 675368960 resident: 37150720 share: 24014848 rss: 37150720 rss_rlim: 18446744073709551615
CPU usage: start_time: 1307962929 rtime: 257 utime: 200 stime: 57 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 0x7f3c8256f700 (LWP 30423)]
[New Thread 0x7f3c93a7d700 (LWP 30369)]
0x00007f3c9d2f03dd in __libc_waitpid (pid=<value optimized out>, stat_loc=<value optimized out>, options=<value optimized out>) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 227458

Thread 1 (Thread 0x7f3ca03c6900 (LWP 30341))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 g_spawn_sync
    at gspawn.c line 392
  • #2 g_spawn_command_line_sync
    at gspawn.c line 706
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomesegvhandler.so
  • #4 <signal handler called>
  • #5 gconf_client_remove_dir
    at gconf-client.c line 755
  • #6 nautilus_actions_config_gconf_reader_finalize
    at nautilus-actions-config-gconf-reader.c line 63
  • #7 g_object_unref
    at gobject.c line 2734
  • #8 nautilus_actions_instance_dispose
    at nautilus-actions.c line 178
  • #9 g_object_unref
    at gobject.c line 2697
  • #10 free_module_objects
    at nautilus-module.c line 216
  • #11 eel_debug_shut_down
    at eel-debug.c line 109
  • #12 main
    at nautilus-main.c line 554 

	Inferior 1 [process 30341] will be detached.

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


----------- .xsession-errors (69574 sec old) ---------------------
virtual void Soprano::Server::ServerConnection::run() thread done. 
virtual Soprano::ODBC::Connection::~Connection() Soprano::Server::ServerConnection(0x7f8420005c80) 
virtual Soprano::ODBC::Connection::~Connection() QThread(0x18caa10) 
Shutting down virtuoso instance 19612
ProcessControl: Application '/usr/bin/nepomukservicestub' stopped unexpected (Process crashed)
Application '/usr/bin/nepomukservicestub nepomukstorage' crashed. No restart!
NepomukServer(19561)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
startkde: Running shutdown scripts...
startkde: Done.
D-Bus session bus went down - quitting
D-Bus session bus went down - quitting
terminating service threads 
terminating connection threads 
stopping db process 
Application 'akonadiserver' exited normally...
--------------------------------------------------
Comment 1 André Klapper 2011-06-13 11:15:06 UTC 
*** Bug 652319 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2011-06-13 11:15:12 UTC 
Same as bug 480179.
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 bug 480179 ***