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 82329 - Nautilus crash on logging into Nautilus controlled desktop
Nautilus crash on logging into Nautilus controlled desktop
Status: RESOLVED DUPLICATE of bug 82078
Product: nautilus
Classification: Core
Component: Desktop
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-20 10:04 UTC by Duncan Innes
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Duncan Innes 2002-05-20 09:04:39 UTC
Package: nautilus
Severity: normal
Version: 1.1.16
Synopsis: Nautilus crash on logging into Nautilus controlled desktop 
Bugzilla-Product: nautilus
Bugzilla-Component: Desktop
BugBuddy-GnomeVersion: 2.0 (1.117.0)

Description:
Description of Problem:
Nautilus crashed immediately on logging into the GNOME desktop 

Steps to reproduce the problem:
1. Log into GNOME when desktop is controlled by Nautilus
2. 
3. 

Actual Results:
Application crash window appears

Expected Results:
Desktop drawn as normal with users icons shown on screen.

How often does this happen?
Certainly not all the time, but I would guess around 1 in 5 times that I
log in.

Additional Information:




Debugging Information:

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

[New Thread 1024 (LWP 9639)]
[New Thread 2049 (LWP 9642)]
[New Thread 1026 (LWP 9643)]
[New Thread 2051 (LWP 9644)]
0x40a69319 in __wait4 () from /lib/libc.so.6

Thread 1 (Thread 1024 (LWP 9639))

  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 592
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 g_logv
  • #7 g_log
    at gmessages.c line 526
  • #8 gdk_x_error
    at gdkmain-x11.c line 780
  • #9 bonobo_x_error_handler
    at bonobo-ui-main.c line 50
  • #10 _XError
    from /usr/X11R6/lib/libX11.so.6
  • #11 _XReply
    from /usr/X11R6/lib/libX11.so.6
  • #12 XSync
    from /usr/X11R6/lib/libX11.so.6
  • #13 gdk_flush
    at gdkevents-x11.c line 1888
  • #14 gdk_window_process_all_updates
    at gdkwindow.c line 2145
  • #15 gtk_container_idle_sizer
    at gtkcontainer.c line 1004
  • #16 g_idle_dispatch
    at gmain.c line 3129
  • #17 g_main_dispatch
    at gmain.c line 1617
  • #18 g_main_context_dispatch
    at gmain.c line 2161
  • #19 g_main_context_iterate
    at gmain.c line 2242
  • #20 g_main_loop_run
    at gmain.c line 2462
  • #21 gtk_main
    at gtkmain.c line 936
  • #22 main
    at nautilus-main.c line 263
  • #23 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/libc.so.6




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-20 05:04 -------

Unknown version 1.1.x in product nautilus. Setting version to the default, "unspecified".
The original reporter (duncan@innes.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 Dave Bordoley [Not Reading Bug Mail] 2002-05-20 15:13:11 UTC
there are a bunch of dupes of this one around, chris i think you filed
one too right???

*** This bug has been marked as a duplicate of 82230 ***
Comment 2 Luis Villa 2002-05-20 15:18:17 UTC
Surely you meant something else, Dave? Those stack traces are not at
all related. Anyway, Christian, you'll have to run nautilus as
'nautilus --sync' to get a trace that is useful. This one is not at
all, unfortunately.
Comment 3 Dave Bordoley [Not Reading Bug Mail] 2002-05-20 15:20:13 UTC
maybe i should of duped them the other way, basically i've seen the
nautilus crashes on startup bug a few times and just marked based on
that, didn't look at the trace actually probably a bad idea...i'll
flip the duping...


Comment 4 Luis Villa 2002-05-20 19:14:28 UTC
NEEDINFO; see my other comment wrt --sync.
Comment 5 Christian Fredrik Kalager Schaller 2002-05-20 19:51:08 UTC
Nope as far as I can remember I have not filed this crasher bug.
Comment 6 Elijah Newren 2002-10-30 22:26:37 UTC
Opening to mark as a duplicate of 82078.
Comment 7 Elijah Newren 2002-10-30 22:27:01 UTC

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