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 300066 - nautilus crashing while connecting to a server
nautilus crashing while connecting to a server
Status: RESOLVED DUPLICATE of bug 134985
Product: nautilus
Classification: Core
Component: general
2.10.x
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-04-10 08:50 UTC by Marco Frattola
Modified: 2005-04-11 21:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Marco Frattola 2005-04-10 08:50:05 UTC
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: nautilus crashing while connecting to a server
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash: i tried to connect to a ftp server within
nautilus
at first id didn't recognize the password (which it was corrected - i
tested thru command line ftp client) and after 3 times, it crashed


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

Expected Results:


How often does this happen?


Additional Information:



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 -1223924480 (LWP 9199)]
[New Thread -1238799440 (LWP 9238)]
[New Thread -1238533200 (LWP 9237)]
[New Thread -1238266960 (LWP 9236)]
[New Thread -1238000720 (LWP 9235)]
[New Thread -1237734480 (LWP 9234)]
[New Thread -1237468240 (LWP 9233)]
[New Thread -1237202000 (LWP 9232)]
[New Thread -1236935760 (LWP 9231)]
[New Thread -1236276304 (LWP 9230)]
[New Thread -1225872464 (LWP 9210)]
(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)
(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)
(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)
(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)
(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)
(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)
0xffffe410 in __kernel_vsyscall ()

Thread 11 (Thread -1225872464 (LWP 9210))

  • #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
  • #0 __kernel_vsyscall




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-10 04:50 -------


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, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was framar@sbarrax.it.
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 Sebastien Bacher 2005-04-10 10:44:02 UTC
can you get a backtrace of the crash with libglib2.0-0-dbg libgnomevfs2-0-dbg
libgtk2.0-0-dbg nautilus-dbg installed ? what kind of ftp are you trying to
connect ?
Comment 2 Christian Kirbach 2005-04-11 07:16:16 UTC

*** This bug has been marked as a duplicate of 170890 ***
Comment 3 Christian Kirbach 2005-04-11 07:20:00 UTC

*** This bug has been marked as a duplicate of 134985 ***
Comment 4 Marco Frattola 2005-04-11 20:41:22 UTC
i was trying to connect to a password-protected ftp account
i should say that account name is particular: it contains "@" within login name;
does this matter?

i had a look to bug 134985 but i didn't get that much from it...

(using: Gnome 2.10.0 on Ubuntu 5.04 Hoary)

if is it still useful to you (Sebastien Bacher), i can get "a backtrace of the
crash with libglib2.0-0-dbg libgnomevfs2-0-dbg libgtk2.0-0-dbg nautilus-dbg",
but  could you please give some indications how to do that?
thanks
Comment 5 Sebastien Bacher 2005-04-11 21:55:26 UTC
thanks but the duplicate has a patch so the maintainers probably don't need
extra informations for this one. Just for information the backtrace is part with
all the function from the comment #1. You can install the -dbg packages from
synaptic, they have extra informations on what happen during the crash and are
useful for maintainers to track them.