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 122131 - Crashed without interaction while using other application
Crashed without interaction while using other application
Status: RESOLVED DUPLICATE of bug 119370
Product: nautilus
Classification: Core
Component: general
2.4.x
Other other
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-09-12 15:29 UTC by Luciano
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luciano 2003-09-12 15:31:55 UTC
Distribution: Red Hat Linux release 9 (Shrike)
Package: nautilus
Severity: critical
Version: GNOME2.4.0 2.4.x
Gnome-Distributor: GARNOME
Synopsis: Crashed without interaction while using other application
Bugzilla-Product: nautilus
Bugzilla-Component: Accessibility
Bugzilla-Version: 2.4.x
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:

Opened a text file from the context menu using the 'open with' and called
emacs. While editing the file in emacs nautilus crashed. 

Steps to reproduce the crash:
1. Open nautilus
2. edit a file with emacs and if you are lucky enought...
3. 

Expected Results:

obvious

How often does this happen?

I could reproduce a couple of times but can't find a pattern. 

Additional Information:

RH9 with GARNOME 0.27.1

I start gnome from GDM opening a failsafe session and calling a garnome-session  script.


Debugging Information:

Backtrace was generated from '/home/gar/garnome/bin/nautilus'

[New Thread 1088233536 (LWP 5098)]
[New Thread 1094569264 (LWP 5113)]
[New Thread 1094303024 (LWP 5112)]
[New Thread 1092635952 (LWP 5101)]
[New Thread 1092369712 (LWP 5100)]
[New Thread 1092103472 (LWP 5099)]
0xffffe002 in ?? ()

Thread 1 (Thread 1088233536 (LWP 5098))

  • #0 ??
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 738
  • #2 <signal handler called>
  • #3 g_logv
  • #4 g_log
  • #5 realize
    at nautilus-icon-container.c line 3016
  • #6 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #7 g_type_class_meta_marshal
    at gclosure.c line 514
  • #8 g_closure_invoke
    at gclosure.c line 437
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2752
  • #10 g_signal_emit_valist
  • #11 g_signal_emit
    at gsignal.c line 2612
  • #12 gtk_widget_realize
    at gtkwidget.c line 2018
  • #13 eel_canvas_item_realize
    at eel-canvas.c line 354
  • #14 eel_canvas_item_realize
    at eel-canvas.c line 351
  • #15 eel_canvas_item_show
    at eel-canvas.c line 777
  • #16 finish_adding_icon
    at nautilus-icon-container.c line 4875
  • #17 finish_adding_new_icons
    at nautilus-icon-container.c line 4901
  • #18 redo_layout_internal
    at nautilus-icon-container.c line 1579
  • #19 redo_layout_callback
    at nautilus-icon-container.c line 1605
  • #20 g_idle_dispatch
    at gmain.c line 3272
  • #21 g_main_dispatch
    at gmain.c line 1751
  • #22 g_main_context_dispatch
    at gmain.c line 2299
  • #23 g_main_context_iterate
    at gmain.c line 2380
  • #24 g_main_loop_run
    at gmain.c line 2600
  • #25 gtk_main
    at gtkmain.c line 1093
  • #26 main
    at nautilus-main.c line 280
  • #27 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-09-12 11:31 -------

Reassigning to the default owner of the component, padraig.obriain@sun.com.

Comment 1 padraig.obriain 2003-09-23 10:04:48 UTC
I have changed the component nfrom Accessibility to general as this is
not an Accessibility bug.
Comment 2 mwehner 2003-09-25 15:42:11 UTC
Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs you find.

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