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 367759 - send-to crashed in send operation
send-to crashed in send operation
Status: RESOLVED DUPLICATE of bug 317081
Product: nautilus-sendto
Classification: Applications
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Roberto Majadas
Roberto Majadas
Depends on:
Blocks:
 
 
Reported: 2006-10-30 16:41 UTC by jmsarltd
Modified: 2006-10-30 17:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description jmsarltd 2006-10-30 16:40:54 UTC
From:  <jmsarltd@yahoo.com>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: send-to crashed in send operation

Distribution: Ubuntu 6.06 (dapper)
Package: nautilus-sendto
Severity: Normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Ubuntu
Synopsis: send-to crashed in send operation
Bugzilla-Product: nautilus-sendto
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash: While in an open Nautalis
window, I
highlighted three gif files and opened the contex menu
(right-click) and
chose send-to.  The send-to seemed to be working, but
came back with an
unnamed error.  It crashed and now I am sending this
report to you.  I
am running Unbuntu 6.x (latest stable update), on an
HP Pavilion 4453
(stock set up), and using a Linksys network card with
a DSL connection. 
I use Firefox 2.x (latest update), which has about 9
tabs open in one
window.  I am also running The GIMP 2.x (latest
update) with no open
windows.  I am also running Open Office 2.x (latest
update) with one
writer document open.  The "Desktop - File Browser"
window is open to
home/oem/Desktop file, in which the gif files are
currently.  I was
going to send them to a new folder I had just created
in
home/oem/blogs/graphic_elements.  That is when it
crashed.  There are
only three other computers using this network, one
laptop (win-tel), and
two desktops (win-tels), at this time.  I may be able
to provide log
data if it will be helpful.  My contact email is
jmsarltd@yahoo.com. 
Thanks -JED-

Steps to reproduce the crash:
1. Open: Desktop - File Browser (as above)
2. Highlight: multiple gif files
3. Open: context menu (right-click) and chose send-to
option

Expected Results: I expected that it would provide me
with an option
dialog box so that I could move the selected files
from the current
directory to the desired directory.


How often does this happen? This is the first time
this has happened. 
It is also the first time I have tried this option in
this version of
Unbuntu 6.x, or Nautalis.


Additional Information: If I can provide further
information email me at
jmsarltd@yahoo.com, and I will send log files and
additional
information, if I can remember it.  I will try to
write something down
in a text file so I can remember this event in case
there needs to be a
reference to it.  Thanks -JED-



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223956800 (LWP 32313)]
[New Thread -1251451984 (LWP 32337)]
[New Thread -1243063376 (LWP 32324)]
(no debugging symbols found)
0xb7ad6031 in __waitpid_nocancel () from
/lib/tls/libpthread.so.0

Thread 1 (Thread -1223956800 (LWP 32313))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/tls/libc.so.6
  • #4 abort
    from /lib/tls/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 add_evolution_contacts_to_model
    from /usr/lib/nautilus-sendto/plugins/libevolution.so
  • #8 add_evolution_contacts_to_model
    from /usr/lib/nautilus-sendto/plugins/libevolution.so
  • #9 set_contact_widgets
  • #10 nautilus_sendto_create_ui
  • #11 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0


*as an update:  I have since repeated the procedure
without the problem above described.  I am guessing
that the problem was actually my computer, not the
program.  I am still sending the event, but it has
worked for me since.  I do believe though that it
should not have happened, and I am still of a mind
that it is a failure of the technology, both hardware
and software that such events occur.  Memory is still
too expensive with error correction (which would have
most likely prevented this problem), and without a
memory dump feature of some kind, software will
continue to have issues with allocation.  True
multi-threaded systems have yet to be developed that
can handle multiple event request well.  However we
must keep in mind that in truth computer technology is
a youth technology, it took them 30 years to make
telephones even generally useful, and almost 50 years
to make it expected.  Therefore I would say in general
that the software is quite adequate in comparrison.  I
would sugest Unbuntu (or variations thereof) to
others, including those that have never used
computers.  I am going to start loading my custom
computers with the software (although I will be using
Kubuntu) for a lower cost alternative to the other
Linux offerings.  Currently I do not see a Windows
user converting easily to any form of Linux until
there is more offerings on OEM computers.

Hope this helps...
James Doud
jmsarltd@yahoo.com


 
____________________________________________________________________________________
We have the perfect Group for you. Check out the handy changes to Yahoo! Groups 
(http://groups.yahoo.com)




------- Bug created by bug-buddy at 2006-10-30 16:41 -------

Comment 1 André Klapper 2006-10-30 17:09:46 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 is fixed in GNOME 2.16.

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