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 363185 - crash in Computer: I had just barely logged...
crash in Computer: I had just barely logged...
Status: RESOLVED DUPLICATE of bug 350758
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-18 17:10 UTC by Elijah Newren
Modified: 2006-10-18 17:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Elijah Newren 2006-10-18 17:10:51 UTC 
What were you doing when the application crashed?
I had just barely logged in to my newly-built-from-tarballs GNOME 2.17.1; hadn't done anything else.


Distribution: Fedora Core release 5.92 (FC6 Test3)
Gnome Release: 2.16.1 2006-10-16 (JHBuild)
BugBuddy Version: 2.16.0

Memory status: size: 23093248 vsize: 0 resident: 23093248 share: 0 rss: 6942720 rss_rlim: 0
CPU usage: start_time: 1161191615 rtime: 0 utime: 9 stime: 0 cutime:4 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/tarball-gnome2/bin/nautilus'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208400192 (LWP 21352)]
0xb7fb5402 in __kernel_vsyscall ()

+ Trace 77005

Thread 1 (Thread -1208400192 (LWP 21352))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 IA__g_logv
  • #8 IA__g_log
  • #9 IA__g_assert_warning
    at gmessages.c line 552
  • #10 oobs_session_init
    at oobs-session.c line 103
  • #11 IA__g_type_create_instance
    at gtype.c line 1567
  • #12 g_object_constructor
    at gobject.c line 1041
  • #13 IA__g_object_newv
    at gobject.c line 937
  • #14 IA__g_object_new_valist
    at gobject.c line 981
  • #15 IA__g_object_new
    at gobject.c line 795
  • #16 oobs_session_get
    at oobs-session.c line 212
  • #17 nautilus_shares_init
    at nautilus-shares.c line 243
  • #18 IA__g_type_create_instance
    at gtype.c line 1567
  • #19 g_object_constructor
    at gobject.c line 1041
  • #20 IA__g_object_newv
    at gobject.c line 937
  • #21 IA__g_object_new_valist
    at gobject.c line 981
  • #22 IA__g_object_new
    at gobject.c line 795
  • #23 nautilus_module_add_type
    at nautilus-module.c line 253
  • #24 nautilus_module_init
    at nautilus-module.c line 160
  • #25 nautilus_application_startup
    at nautilus-application.c line 391
  • #26 main
    at nautilus-main.c line 359
  • #0 __kernel_vsyscall 






Comment 1


Elijah Newren





          2006-10-18 17:16:07 UTC
        



Appears to be fully repeatable, making nautilus unlaunchable.  When launched from the terminal:

(nautilus:21440): Liboobs-CRITICAL **: Failed to connect to socket /opt/tarball-gnome2/var/run/dbus/system_bus_socket: No such file or directory

Liboobs-ERROR **: file oobs-session.c: line 103 (oobs_session_init): should not be reached
aborting...

** (bug-buddy:21444): WARNING **: Couldn't load icon for Bonobo Component Browser

** (bug-buddy:21444): WARNING **: Couldn't load icon for Open Folder


Due to the critical warning, looks like a duplicate of bug 350758, so perhaps we need to bump the external dependency versions at http://live.gnome.org/TwoPointSeventeen/ExternalDependencies...

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