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 115301 - Unknown crash
Unknown crash
Status: RESOLVED DUPLICATE of bug 105745
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-06-16 16:44 UTC by singularity
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description singularity 2003-06-16 16:45:00 UTC
Package: nautilus
Severity: normal
Version: 2.2.1
Synopsis: Unknown crash
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
Nautilus crashed while I was browsing through newspostings in Pan.

Steps to reproduce the problem:
1. N/A
2. N/A
3. N/A

Actual Results:
Nautilus crashed.

Expected Results:
Nautilus should have continued to run and been available for me whenever
I needed to use it.

How often does this happen?
Rarely.

Additional Information:
Red Hat 9 up-to-date system.



Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1087959360 (LWP 1095)]
[New Thread 1175698736 (LWP 1113)]
[New Thread 1167306032 (LWP 1112)]
[New Thread 1158913328 (LWP 1111)]
[New Thread 1150520624 (LWP 1110)]
[New Thread 1142127920 (LWP 1109)]
[New Thread 1133735216 (LWP 1108)]
[New Thread 1125342512 (LWP 1107)]
[New Thread 1116949808 (LWP 1106)]
[New Thread 1099795760 (LWP 1105)]
0xffffe002 in ?? ()

Thread 1 (Thread 1087959360 (LWP 1095))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #5 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #6 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-16 12:45 -------

The original reporter (singularity@home.no) 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 Elijah Newren 2003-06-16 18:19:37 UTC
This looks like the mysterious gtk+ crash that is showing up
everywhere [See specifically bug 105745 for more info].
                                                                     
          
A number of people are getting this, but the stack traces are
unfortunately useless and we don't know how to reproduce the problem.
Can you get a stacktrace with symbols for us?                        
                                                         You can do so
with the following easy method; otherwise this will require
recompiling from source:
                                                                     
          
  Install
  http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm
  and if the problem occurs again, submit the backtrace you get.
  Installing the debuginfo package will make the backtrace much more
  useful.
                                                                     
          
I am adding myself to the cc and marking as needinfo for now.
Comment 2 Elijah Newren 2003-06-17 15:18:37 UTC
Kjartan: If I made a mistake by marking this as NEEDINFO (which seems
to be implied by the fact that you reopened this), could you please
explain why so that I can mark other bugs properly?  Thanks.
Comment 3 Alex Duggan 2003-07-02 12:39:54 UTC

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