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 135804 - error message says nautilus crashed, but it didn't really crash
error message says nautilus crashed, but it didn't really crash
Status: RESOLVED DUPLICATE of bug 133808
Product: nautilus
Classification: Core
Component: general
2.5.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-01 01:28 UTC by scott
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description scott 2004-03-01 01:32:54 UTC 
Distribution: Fedora Core release 1.90 (FC2 Test 1)
Package: nautilus
Severity: major
Version: GNOME2.5.90 2.5.x
Gnome-Distributor: Red Hat, Inc
Synopsis: error message says nautilus crashed, but it didn't really crash
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.5.x
BugBuddy-GnomeVersion: 2.0 (2.5.90)
Description:
Description of the crash:
upon launching nautilus from the command line, i receive an error dialog
box saying "The Application 'nautilus' has quit unexpectedly. however,
nautilus is still running fine, with seemingly no problems. this is with
version 2.5.8

the terminal gives this output:
#############################################
** ERROR **: file orbit-object.c: line 149 (do_unref): assertion failed:
(robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0)
aborting...
 
(gnome_segv:2199): Gtk-WARNING **: Ignoring the separator setting
#############################################

Steps to reproduce the crash:
1. start nautilus from command line


Expected Results:
expect nautilus to not tell the system it crashed, when it didn't

How often does this happen?
every time i launch nautilus from the command line

Additional Information:

debug info:
#############################################
Breakpoint 2, 0x00e0dcb3 in g_log () from /usr/lib/libglib-2.0.so.0
(gdb) where

+ Trace 44680

Thread 1 (Thread -1207077952 (LWP 2143))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #5 g_log
    from /usr/lib/libglib-2.0.so.0
  • #6 ORBit_RootObject_duplicate_T
    from /usr/lib/libORBit-2.so.0
  • #7 CORBA_any__freekids
    from /usr/lib/libORBit-2.so.0
  • #8 ORBit_policy_validate
    from /usr/lib/libORBit-2.so.0
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-02-29 20:32 -------

Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Comment 1 Martin Wehner 2004-03-01 01:52:11 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 133808 ***