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 104263 - Crashed Application
Crashed Application
Status: RESOLVED DUPLICATE of bug 105745
Product: nautilus
Classification: Core
Component: general
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Reported: 2003-01-23 19:50 UTC by Yoav
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0

Description Yoav 2003-01-23 19:50:37 UTC
Description of Problem:
Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)...(no debugging
symbols found)...
(no debugging symbols found)...(no debugging
symbols found)...
0x40923c0c in waitpid () from
  • #0 waitpid
    from /lib/i686/
  • #1 libgnomeui_module_info_get
    from /usr/lib/
  • #2 <signal handler called>
  • #3 gdk_event_get_graphics_expose
    from /usr/lib/
  • #4 gdk_add_client_message_filter
    from /usr/lib/
  • #5 _gdk_events_queue
    from /usr/lib/
  • #6 _gdk_events_queue
    from /usr/lib/
  • #7 g_get_current_time
    from /usr/lib/
  • #8 g_main_context_dispatch
    from /usr/lib/
  • #9 g_main_context_dispatch
    from /usr/lib/
  • #10 g_main_loop_run
    from /usr/lib/
  • #11 gtk_main
    from /usr/lib/
  • #12 main
  • #13 __libc_start_main
    from /lib/i686/

Steps to reproduce the problem:

Actual Results:

Expected Results:

How often does this happen? 

Additional Information:
Comment 1 Elijah Newren 2003-01-23 20:43:29 UTC
Shortening the ridiculously long summary.

Also, this looks like the stack trace in bug 104253, but that bug was
against gnome-session.  Maybe they're dups?

Reporter: What version of nautilus are you using?
Comment 2 Yoav 2003-01-24 04:55:57 UTC
i am using Gnome 2.1.4 so maybe natuluios is 2.1.4
Comment 3 Anand 2003-02-12 10:45:42 UTC
Stack trace same as 105745. Also, the other bug has li'l more
additional information. So, marking this bug a dupe of 105745 :)

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