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 129758 - Segmentation fault, when i tries to delete an "Invalid Unicode" folder
Segmentation fault, when i tries to delete an "Invalid Unicode" folder
Status: RESOLVED DUPLICATE of bug 126042
Product: nautilus
Classification: Core
Component: File and Folder Operations
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-12-21 00:33 UTC by bugzilla
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description bugzilla 2003-12-21 00:34:03 UTC 
Package: nautilus
Severity: normal
Version: 2.2.1
Synopsis: Segmentation fault, when i tries to delete an "Invalid Unicode" folder
Bugzilla-Product: nautilus
Bugzilla-Component: File and Folder Operations
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
When i tring to delete a folder copied from a spanish windows-2000
partition, it's causes a segmentation fault.
If you prefeer, i can send a tgz file, with a folder that can cause the
fatal error

Steps to reproduce the problem:
1. Copy a folder called "Menú de Inicio" (Start Menu) from an spanish
windows 2000 to a ext3 Linux folder
2. try to delete
3. suffer

How often does this happen?
ever

Additional Information:
win 2000 profesional, spanish



Debugging Information:

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

(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)...[New Thread 16384 (LWP 10075)]
[New Thread 32769 (LWP 10078)]
[New Thread 16386 (LWP 10079)]
[New Thread 32771 (LWP 10080)]
[New Thread 49156 (LWP 10083)]
[New Thread 65541 (LWP 10084)]
[New Thread 81926 (LWP 10085)]
[New Thread 98311 (LWP 10086)]
0x40ad9844 in waitpid ()
   from /lib/libpthread.so.0

+ Trace 42806

Thread 1 (Thread 16384 (LWP 10075))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 nautilus_file_operations_progress_resume_timeout
    from /usr/lib/libnautilus-private.so.2
  • #5 nautilus_file_operations_progress_resume_timeout
    from /usr/lib/libnautilus-private.so.2
  • #6 nautilus_file_operations_progress_resume_timeout
    from /usr/lib/libnautilus-private.so.2
  • #7 nautilus_file_operations_progress_resume_timeout
    from /usr/lib/libnautilus-private.so.2
  • #8 _gnome_vfs_job_complete
    from /usr/lib/libgnomevfs-2.so.0
  • #9 _gnome_vfs_job_complete
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_timeout_add
    from /usr/lib/libglib-2.0.so.0
  • #11 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 main
  • #17 __libc_start_main
    from /lib/libc.so.6
  • #0 waitpid
    from /lib/libpthread.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-12-20 19:34 -------

Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Comment 1 Matthew Gatto 2003-12-21 00:57:16 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 bug has been marked as a duplicate of 126042 ***