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 308223 - Nautilus crashes first time, subsequent runs are fine
Nautilus crashes first time, subsequent runs are fine
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: general
2.10.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-18 21:38 UTC by Andrew Conkling
Modified: 2005-12-30 05:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Andrew Conkling 2005-06-18 21:38:17 UTC 
Distribution/Version: Arch

I can't figure out why, but Nautilus crashes the first time I run it; 
afterwards, it runs fine.  Here's what I get in gdb:

gdb nautilus
(gdb) run
Starting program: /opt/gnome/bin/nautilus
(no debugging symbols found)
[SNIP]
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226839520 (LWP 31031)]
(no debugging symbols found)
[SNIP]
(no debugging symbols found)
[New Thread -1231565904 (LWP 31034)]
(no debugging symbols found)
[New Thread -1239970896 (LWP 31042)]
[New Thread -1240237136 (LWP 31043)]
[New Thread -1240503376 (LWP 31044)]

Program received signal SIG33, Real-time event 33.

+ Trace 61232

Thread NaN (LWP 31034)

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 poll
    from /lib/tls/libc.so.6
  • #5 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #7 link_io_thread_fn
    from /opt/gnome/lib/libORBit-2.so.0
  • #8 g_thread_create_proxy
    from /usr/lib/libglib-2.0.so.0
  • #9 start_thread
    from /lib/tls/libpthread.so.0
  • #10 clone
    from /lib/tls/libc.so.6 






Comment 1


Sebastien Bacher





          2005-06-19 11:16:49 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash. Can you get us one with debugging symbols?
Please see http://live.gnome.org/GettingTraces for more information on how to do so.






Comment 2


Andrew Conkling





          2005-06-23 03:52:22 UTC
        



Well, here's the bt as mentioned in that Gnome site.  It doesn't really look any 
more detailed though....

(gdb) thread apply all bt




+
Trace
    61435
















Comment 3


Andrew Conkling





          2005-08-11 23:56:30 UTC
        



Sebastien,
Can you confirm whether this bt was useful?  It's been a while since I posted it 
and I don't really want it to fall through the cracks.






Comment 4


Sebastien Bacher





          2005-08-12 10:43:07 UTC
        



sorry, but it seems that you still use stripped libraries, there is no debug
information with this backtrace ...






Comment 5


Andrew Conkling





          2005-08-12 11:11:20 UTC
        



Thanks for getting back to me.  Do you know which libraries I should recompile 
without the stripping?






Comment 6


Olav Vitters





          2005-12-29 21:55:47 UTC
        



Andrew: glib, gtk, gnome-vfs and nautilus






Comment 7


Andrew Conkling





          2005-12-30 05:03:20 UTC
        



Isn't it great to dredge up old bugs?  I'm not sure if it was configuration or the upgrade to 2.12, but I haven't noticed this problem in a while.  I'll go ahead and close this for now; rest assured, I'll reopen it if I can reproduce it again in the future. :)