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 301546 - Can't copy files from an ssh source
Can't copy files from an ssh source
Status: RESOLVED DUPLICATE of bug 153679
Product: nautilus
Classification: Core
Component: general
2.10.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 171262 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-04-22 05:09 UTC by Emmanuel Rodriguez
Modified: 2005-08-05 18:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Emmanuel Rodriguez 2005-04-22 05:09:58 UTC
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: Can't copy files from an ssh source
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
Nautilus crashes when trying to copy files from an SSH source

Steps to reproduce the crash:
1. Drand an Drop the SSH folder to copy into a local folder.
2. 
3. 

Expected Results:


How often does this happen?
All the time

Additional Information:
This bug should be linked with
http://bugzilla.gnome.org/show_bug.cgi?id=171262
This time I did install the packages libgtk2.0-0-dbg and
libglib2.0-0-dbg


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1223908096 (LWP 8475)]
[New Thread -1237861456 (LWP 8548)]
[New Thread -1237595216 (LWP 8547)]
[New Thread -1237328976 (LWP 8546)]
[New Thread -1237062736 (LWP 8545)]
[New Thread -1236390992 (LWP 8542)]
[New Thread -1226019920 (LWP 8530)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 7 (Thread -1226019920 (LWP 8530))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_context_poll
    at gmain.c line 2880
  • #3 g_main_context_iterate
    at gmain.c line 2573
  • #4 IA__g_main_loop_run
    at gmain.c line 2782
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 __JCR_LIST__
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_thread_create_proxy
    at gthread.c line 561
  • #0 __kernel_vsyscall




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-22 01:09 -------


Unknown version 2.10.0 in product nautilus.  Setting version to "2.10.x".
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 2005-04-24 03:33:52 UTC
*** Bug 171262 has been marked as a duplicate of this bug. ***
Comment 2 Emmanuel Rodriguez 2005-04-24 06:28:05 UTC
I'm sorry if i created a new bug but I was simply using the GNOME built-in
tracking tool and there doesn't seem to be a way to link a bug report with an
existing one. At least I did provide the URL of the "original" bug!
If the debug output of any help?
Comment 3 Sebastien Bacher 2005-05-05 17:59:48 UTC
from the duplicate:

Thread 5 (Thread -1225708624 (LWP 21678))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_static_private_free
    from /usr/lib/libglib-2.0.so.0


Seems to be a gtk or xorg issue, reassigning to gtk
Comment 4 Owen Taylor 2005-07-26 22:19:36 UTC
No reason to think this is a GTK+ issue. Backtraces are unclear, but the
threads in X seem to simply be blocking for a reply from the X server.
Comment 5 Martin Wehner 2005-08-05 18:07:00 UTC
Most likely a dup of bug 153679.

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