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 104331 - Tried to view the application in BlueCurve on RH 8.0
Tried to view the application in BlueCurve on RH 8.0
Status: RESOLVED DUPLICATE of bug 135334
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.0.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-01-24 16:39 UTC by cpt_morian
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description cpt_morian 2003-01-24 15:37:33 UTC
Package: nautilus
Severity: major
Version: 2.0.6
Synopsis: Tried to view the application in BlueCurve on RH 8.0
Bugzilla-Product: nautilus
Bugzilla-Component: File and Folder Operations
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:


Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:




Debugging Information:

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

(no debugging symbols found)...[New Thread 8192 (LWP 1052)]
[New Thread 16385 (LWP 1061)]
[New Thread 8194 (LWP 1062)]
[New Thread 16387 (LWP 1063)]
[New Thread 24580 (LWP 1064)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

Thread 1 (Thread 8192 (LWP 1052))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 nautilus_icon_canvas_item_get_image
    at nautilus-icon-canvas-item.c line 399
  • #7 nautilus_icon_dnd_begin_drag
    at nautilus-icon-dnd.c line 1089
  • #8 motion_notify_event
    at nautilus-icon-container.c line 2898
  • #9 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_type_class_meta_marshal
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_signal_emit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_widget_event_internal
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gdk_event_dispatch
    from /usr/lib/libgdk-x11-2.0.so.0
  • #19 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 main
  • #25 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-24 10:37 -------

The original reporter (cpt_morian@cptmorian.homelinux.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 Elijah Newren 2003-01-24 18:57:46 UTC
This is a unique stack trace, according to the simple-dup-finder. 
Setting version->2.0.x, adding the GNOMEVER2.0 and bugsquad keywords,
setting priority->high & severity->critical (it's a crasher), and
marking as new.

Reporter: What application did you try to open?
Comment 2 Kjartan Maraas 2003-10-31 16:54:25 UTC
No feedback. Closing.
Comment 3 Matthew Gatto 2004-02-26 18:14:07 UTC
Reopening to mark as dup of bug 135334 which has better information.
Comment 4 Matthew Gatto 2004-02-26 18:15:03 UTC

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