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 477646 - crash in Computer: I was trying to connect ...
crash in Computer: I was trying to connect ...
Status: RESOLVED DUPLICATE of bug 365624
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-17 04:05 UTC by Pierre-Olivier Dufresne
Modified: 2007-10-21 22:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Pierre-Olivier Dufresne 2007-09-17 04:05:44 UTC 
Version: 2.18.1

What were you doing when the application crashed?
I was trying to connect to an FTP server


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 583077888 vsize: 583077888 resident: 133881856 share: 21188608 rss: 133881856 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189997554 rtime: 3053 utime: 2692 stime: 361 cutime:11 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912697156272 (LWP 3839)]
[New Thread 1126189392 (LWP 5821)]
[New Thread 1105209680 (LWP 4468)]
(no debugging symbols found)
0x00002aaab1170956 in poll () from /lib64/libc.so.6

+ Trace 163451

Thread 2 (Thread 1126189392 (LWP 5821))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib64/libc.so.6
  • #4 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/gnome-vfs-2.0/modules/libftp.so
  • #5 gnome_vfs_directory_read_next_cancellable
    from /usr/lib64/libgnomevfs-2.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #7 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #8 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #9 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #10 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #11 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #12 start_thread
    from /lib64/libpthread.so.0
  • #13 clone
    from /lib64/libc.so.6 


----------- .xsession-errors (631 sec old) ---------------------
(gnome-background-properties:5763): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(gnome-background-properties:5763): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(gnome-background-properties:5763): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed
(gnome-background-properties:5763): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(gnome-background-properties:5763): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(gnome-background-properties:5763): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed
(gnome-background-properties:5763): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-10-21 22:21:06 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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