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 352418 - crash in Computer: Starting up Nautilus. I...
crash in Computer: Starting up Nautilus. I...
Status: RESOLVED FIXED
Product: gnome-system-tools
Classification: Deprecated
Component: shares-admin
2.15.x
Other All
: High critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
: 353713 353716 354236 356875 356987 357308 357311 358287 358473 358692 358900 358936 358950 358985 358987 359002 359019 359055 359097 359100 359128 361640 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-08-22 16:09 UTC by Daniel Sheridan
Modified: 2006-10-12 17:53 UTC
See Also:
GNOME target: 2.16.x
GNOME version: 2.15/2.16

Attachments
Partial stacktrace of the crash (10.44 KB, text/plain)
2006-10-02 14:10 UTC, David Planella 		Details
My smb.conf (7.71 KB, text/plain)
2006-10-02 15:33 UTC, David Planella 		Details

Description Daniel Sheridan 2006-08-22 16:09:04 UTC 
What were you doing when the application crashed?
Starting up Nautilus.

I see the following in the terminal:

** (nautilus:6970): CRITICAL **: oobs_share_smb_new: assertion `path[0] == '/'' failed

** (nautilus:6970): CRITICAL **: oobs_list_set: assertion `G_IS_OBJECT (data)' failed

(nautilus:6970): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

** (nautilus:6970): CRITICAL **: oobs_list_get: assertion `node->data != NULL' failed

** (nautilus:6970): CRITICAL **: oobs_share_get_path: assertion `OOBS_IS_SHARE (share)' failed



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 21549056 vsize: 0 resident: 21549056 share: 0 rss: 7974912 rss_rlim: 0
CPU usage: start_time: 1156262864 rtime: 0 utime: 22 stime: 0 cutime:19 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226426704 (LWP 6970)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 70825

Thread 1 (Thread -1226426704 (LWP 6970))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_insert
    from /usr/lib/libglib-2.0.so.0
  • #6 nautilus_shares_register_type
    from /usr/lib/nautilus/extensions-1.0/libnautilus-gst-shares.so
  • #7 nautilus_shares_register_type
    from /usr/lib/nautilus/extensions-1.0/libnautilus-gst-shares.so
  • #8 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_object_set
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #13 nautilus_module_add_type
    at nautilus-module.c line 253
  • #14 nautilus_module_init
    at nautilus-module.c line 160
  • #15 nautilus_application_startup
    at nautilus-application.c line 391
  • #16 main
    at nautilus-main.c line 360
  • #17 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #18 _start
  • #0 __kernel_vsyscall 






Comment 1


Karsten Bräckelmann





          2006-08-31 19:09:23 UTC
        



*** Bug 353713 has been marked as a duplicate of this bug. ***






Comment 2


Karsten Bräckelmann





          2006-08-31 19:12:22 UTC
        



*** Bug 353716 has been marked as a duplicate of this bug. ***






Comment 3


Karsten Bräckelmann





          2006-08-31 19:16:15 UTC
        



See bug 353716 for a stacktrace with glib debugging symbols.







Comment 4


Fabio Bonelli





          2006-09-04 08:19:57 UTC
        



*** Bug 354236 has been marked as a duplicate of this bug. ***






Comment 5


Karsten Bräckelmann





          2006-09-20 10:20:46 UTC
        



*** Bug 356875 has been marked as a duplicate of this bug. ***






Comment 6


Karsten Bräckelmann





          2006-09-20 23:49:02 UTC
        



*** Bug 356987 has been marked as a duplicate of this bug. ***






Comment 7


Karsten Bräckelmann





          2006-09-23 13:42:43 UTC
        



*** Bug 357311 has been marked as a duplicate of this bug. ***






Comment 8


Karsten Bräckelmann





          2006-09-23 13:42:55 UTC
        



*** Bug 357308 has been marked as a duplicate of this bug. ***






Comment 9


Karsten Bräckelmann





          2006-09-29 12:23:55 UTC
        



*** Bug 358287 has been marked as a duplicate of this bug. ***






Comment 10


André Klapper





          2006-09-30 12:26:21 UTC
        



*** Bug 358473 has been marked as a duplicate of this bug. ***






Comment 11


André Klapper





          2006-09-30 12:28:12 UTC
        



8 duplicates so far, i'm considering this as a GNOME 2.16 target.






Comment 12


Elijah Newren





          2006-10-01 06:17:36 UTC
        



*** Bug 358692 has been marked as a duplicate of this bug. ***






Comment 13


Elijah Newren





          2006-10-02 02:40:41 UTC
        



*** Bug 358900 has been marked as a duplicate of this bug. ***






Comment 14


André Klapper





          2006-10-02 08:26:03 UTC
        



*** Bug 358936 has been marked as a duplicate of this bug. ***






Comment 15


André Klapper





          2006-10-02 09:58:21 UTC
        



*** Bug 358950 has been marked as a duplicate of this bug. ***






Comment 16


André Klapper





          2006-10-02 10:00:50 UTC
        



Can anyone here please get us a stacktrace with debugging symbols to help the developers fix this issue? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks very much in advance!







Comment 17


andrew





          2006-10-02 10:20:47 UTC
        



I've just updated the computer that I had running Ubuntu Edgy to the latest version of everything (aptitude update; aptitude upgrade), and that seems to have fixed the problem.
The bug dissapeared when nautilus-cd-burner was upgraded.

It's probably not worth trying to fix a bug that isn't there anymore.






Comment 18


maurizio.merli





          2006-10-02 12:59:28 UTC
        



I've updated my ubuntu too but the bug remain!






Comment 19


Karsten Bräckelmann





          2006-10-02 13:05:38 UTC
        



*** Bug 358985 has been marked as a duplicate of this bug. ***






Comment 20


Karsten Bräckelmann





          2006-10-02 13:05:49 UTC
        



*** Bug 358987 has been marked as a duplicate of this bug. ***






Comment 21


Karsten Bräckelmann





          2006-10-02 13:55:50 UTC
        



*** Bug 359002 has been marked as a duplicate of this bug. ***






Comment 22


David Planella





          2006-10-02 14:10:26 UTC
        



Created attachment 73850 [details]
Partial stacktrace of the crash

I am also an Ubuntu Edgy user, and unlike the previous poster, I started having this issue when I upgraded to the latest nautilus/nautilus-cd-burner packages.

Here is a partial stacktrace with nautilus debugging symbols enabled. That's all I can do for the moment. I will try to compile all required packages with debugging symbols, but I just haven't got the time right now.

I hope this helps.






Comment 23


Sebastien Bacher





          2006-10-02 14:36:22 UTC
        



that's a gnome-system-tools issue, probably similar to bug #350758, reassigning






Comment 24


Karsten Bräckelmann





          2006-10-02 14:40:38 UTC
        



*** Bug 359019 has been marked as a duplicate of this bug. ***






Comment 25


André Klapper





          2006-10-02 14:47:57 UTC
        



bernat: thanks very much for your help, however, that stacktrace is still missing the two most important "symbols" (= names of functions and line numbers) in





+
Trace
    74081






    

  • 
#6
nautilus_shares_register_type

    
                from
                /usr/lib/nautilus/extensions-1.0/libnautilus-gst-shares.so

    

    • 

  • 
#7
nautilus_shares_register_type

    
                from
                /usr/lib/nautilus/extensions-1.0/libnautilus-gst-shares.so

    

    • 








anyway, this already brings us nearer to the core of the problem... if there is any debug or devel package available for liboobs, feel free to install. thanks in advance. ;-)






Comment 26


Sebastien Bacher





          2006-10-02 15:23:03 UTC
        



Maybe you could attach /etc/samba/smb.conf (after replacing private datas if there is any) to the bug?






Comment 27


David Planella





          2006-10-02 15:33:24 UTC
        



Created attachment 73852 [details]
My smb.conf

Here's my smb.conf. I've got no private data there, so it is an exact copy of what I've got on my system.

BTW, I installed the ubuntu edgy liboobs1-2-dbg and liboobs1-2-dev packages, but that did not add any more information to the stacktrace, so I did not submit it. If necessary, could anyone point me out to which product's debug symbols I should be looking for?

Apparently, the Ubuntu bug (https://launchpad.net/distros/ubuntu/+source/gnome-system-tools/+bug/62739) has been fixed, but not yet released. So I'm looking forward to see if that is a fix for this same issue.

Cheers.






Comment 28


Carlos Garnacho





          2006-10-02 15:52:33 UTC
        



Thanks, there's now a fix in s-t-b HEAD. Also liboobs has been made more robust






Comment 29


Elijah Newren





          2006-10-02 17:37:35 UTC
        



*** Bug 359055 has been marked as a duplicate of this bug. ***






Comment 30


Elijah Newren





          2006-10-02 19:56:29 UTC
        



*** Bug 359097 has been marked as a duplicate of this bug. ***






Comment 31


Elijah Newren





          2006-10-02 20:03:06 UTC
        



*** Bug 359100 has been marked as a duplicate of this bug. ***






Comment 32


Elijah Newren





          2006-10-02 21:58:26 UTC
        



*** Bug 359128 has been marked as a duplicate of this bug. ***






Comment 33


Karsten Bräckelmann





          2006-10-12 17:53:21 UTC
        



*** Bug 361640 has been marked as a duplicate of this bug. ***