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 161655 - Crash when dragging file to trash applet twice
Crash when dragging file to trash applet twice
Status: RESOLVED DUPLICATE of bug 158196
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.9.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-12-18 21:35 UTC by Francisco Camenforte Torres
Modified: 2005-09-30 18:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Francisco Camenforte Torres 2004-12-18 21:36:03 UTC 
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.9.2 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: Crash when dragging file to trash applet twice
Bugzilla-Product: nautilus
Bugzilla-Component: File and Folder Operations
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.9.1)
Description:
I dragged a file to trash applet. The results didn-t show up -probably
cause the CPU was busy compiling- so I repeated the operation. Nautilus
gave displayed an error dialog about being unabled to send to trash the
single file, and offering to delete it immediately. I hit the cancel
button and it crashed.



Debugging Information:

Backtrace was generated from '/home/jhbuild/gnome2/bin/nautilus'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread 1090795360 (LWP 13400)]
[New Thread 1119398832 (LWP 16447)]
[New Thread 1102134192 (LWP 13409)]
[New Thread 1101872048 (LWP 13408)]
[New Thread 1101609904 (LWP 13407)]
[New Thread 1100950448 (LWP 13401)]
0x40ca8511 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 53670

Thread 1 (Thread 1090795360 (LWP 13400))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 741
  • #2 <signal handler called>
  • #3 nautilus_icon_canvas_item_get_image
    at nautilus-icon-canvas-item.c line 473
  • #4 nautilus_icon_dnd_begin_drag
    at nautilus-icon-dnd.c line 1255
  • #5 motion_notify_event
    at nautilus-icon-container.c line 3609
  • #6 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #7 g_type_class_meta_marshal
    at gclosure.c line 514
  • #8 IA__g_closure_invoke
    at gclosure.c line 437
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2523
  • #10 IA__g_signal_emit_valist
    at gsignal.c line 2254
  • #11 IA__g_signal_emit
    at gsignal.c line 2288
  • #12 gtk_widget_event_internal
    at gtkwidget.c line 3616
  • #13 IA__gtk_widget_event
    at gtkwidget.c line 3422
  • #14 IA__gtk_propagate_event
    at gtkmain.c line 2145
  • #15 IA__gtk_main_do_event
    at gtkmain.c line 1383
  • #16 gdk_event_dispatch
    at gdkevents-x11.c line 2218
  • #17 g_main_dispatch
    at gmain.c line 1947
  • #18 IA__g_main_context_dispatch
    at gmain.c line 2497
  • #19 g_main_context_iterate
    at gmain.c line 2578
  • #20 IA__g_main_loop_run
    at gmain.c line 2782
  • #21 IA__gtk_main
    at gtkmain.c line 963
  • #22 main
    at nautilus-main.c line 327
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-18 16:36 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Elijah Newren 2004-12-19 02:25:07 UTC 
The stack trace matches the one in bug 135334, but that was marked as fixed in
2.4.0, so either there's been a regression or that was marked incorrectly, so
I'm leaving this open.
Comment 2 Luis Villa 2005-01-03 04:45:22 UTC 
cc'ing jamesh, since he wrote the applet and might have some clue what is
triggering the bug...
Comment 3 James Henstridge 2005-02-07 15:26:50 UTC 
Sorry about not following up on this bug.  The stack trace says it is from
Nautilus rather than the trashapplet, which is an independent process so
shouldn't be able to crash nautilus.
Comment 4 Christian Neumair 2005-09-13 23:25:54 UTC 
Yeah, this is from Nautilus and very likely a duplicate of bug 168196.
Comment 5 Christian Neumair 2005-09-13 23:29:29 UTC 
Sorry, I mean bug 158196.
Comment 6 Christian Neumair 2005-09-30 18:15:18 UTC 
Definitly a dup.

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