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 407105 - nautilus_module_load_file adding NULL object
nautilus_module_load_file adding NULL object
Status: RESOLVED DUPLICATE of bug 449488
Product: nautilus
Classification: Core
Component: general
2.17.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-12 15:58 UTC by ndelmonico
Modified: 2007-06-26 17:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description ndelmonico 2007-02-12 15:58:03 UTC 
Version: 2.17.90

What were you doing when the application crashed?
Starting Gnome.  The file icons that usually are on the desktop are not present.


Distribution: Unknown
Gnome Release: 2.17.90 2007-02-01 (FreeBSD GNOME Project)
BugBuddy Version: 2.17.3

System: FreeBSD 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Feb  2 07:28:46 CST 2007     root@Anandavardhana.dot:/usr/obj/usr/src/sys/ANANDA amd64
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: No
Accessibility: Disabled

Memory status: size: 154600 vsize: 154600 resident: 27556 share: 155039288 rss: 27556 rss_rlim: 6889
CPU usage: start_time: 1862566291 rtime: 0 utime: 64 stime: 3953558 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133

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

[New LWP 100085]
[Switching to LWP 100085]
0x00000008062ce8ca in wait4 () at wait4.S:2
	in wait4.S
Current language:  auto; currently asm

+ Trace 110108

Thread 1 (LWP 100085)

  • #0 wait4
    at wait4.S line 2
  • #1 __waitpid
    at /usr/src/lib/libc/gen/waitpid.c line 46
  • #2 _waitpid
    at /usr/src/lib/libpthread/thread/thr_waitpid.c line 51
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #4 sigfatal_handler
    at nautilus-main.c line 284
  • #5 _thr_sig_handler
    at /usr/src/lib/libpthread/thread/thr_sig.c line 383
  • #6 <signal handler called>
  • #7 kill
    at kill.S line 2
  • #8 _raise
    at /usr/src/lib/libpthread/thread/thr_raise.c line 47
  • #9 abort
    at /usr/src/lib/libc/stdlib/abort.c line 65
  • #10 IA__g_logv
    at gmessages.c line 497
  • #11 IA__g_log
    at gmessages.c line 517
  • #12 IA__g_return_if_fail_warning
  • #13 IA__g_object_new
    at gobject.c line 792
  • #14 nautilus_module_add_type
    at nautilus-module.c line 253
  • #15 add_module_objects
    at nautilus-module.c line 160
  • #16 nautilus_module_load_file
    at nautilus-module.c line 173
  • #17 load_module_dir
    at nautilus-module.c line 199
  • #18 nautilus_module_init
    at nautilus-module.c line 216
  • #19 finish_startup
    at nautilus-application.c line 400
  • #20 nautilus_application_startup
    at nautilus-application.c line 535
  • #21 main
    at nautilus-main.c line 533 


----------- .xsession-errors ---------------------
(nautilus:26189): Liboobs-WARNING **: There was an unknown error communicating with the backends: The name org.freedesktop.SystemToolsBackends was not provided by any .service files
(nautilus:26189): Liboobs-WARNING **: There was an unknown error communicating with the backends: The name org.freedesktop.SystemToolsBackends was not provided by any .service files
Initializing gnome-mount extension
** (nautilus:26189): WARNING **: Failed to initialize libhal context: (null) : (null)
** (nautilus:26189): WARNING **: Could not initialize hal context
GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
aborting...
warning: Unable to get location for thread creation breakpoint: generic error
2	wait4.S: No such file or directory.
--------------------------------------------------
Comment 1 Christian Kirbach 2007-02-12 22:22:57 UTC 
good trace, unique, confirming
Comment 2 André Klapper 2007-02-28 16:02:02 UTC 
i guess that bug 412121 is the same issue
Comment 3 André Klapper 2007-06-24 21:48:53 UTC 
christian: dup of bug 449488?
Comment 4 Christian Kirbach 2007-06-26 17:49:29 UTC 
most likely

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 449488 ***