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 149394 - no se puede eliminar un pdf
no se puede eliminar un pdf
Status: RESOLVED DUPLICATE of bug 149202
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Balsa maintainers
Balsa maintainers
Depends on:
Blocks:
 
 
Reported: 2004-08-05 13:30 UTC by pipis384
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description pipis384 2004-08-05 13:30:41 UTC
Distribution: Fedora Core release 1 (Yarrow)
Package: balsa
Severity: normal
Version: GNOME2.4.0 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: no se puede eliminar un pdf
Bugzilla-Product: balsa
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
error
Steps to reproduce the crash:
1. a
2. b
3. c

Expected Results:

a
How often does this happen?

a
Additional Information:
a


Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(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)...[Thread debugging using libthread_db
enabled]
[New Thread -1084528768 (LWP 4903)]
[New Thread -1089655888 (LWP 4906)]
[New Thread -1087296592 (LWP 4905)]
[New Thread -1087030352 (LWP 4904)]
(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)...0x0036ec32 in _dl_sysinfo_int80 ()
   from /lib/ld-linux.so.2
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.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 unblock_source
    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 ??
  • #17 ??
  • #18 nautilus_application_new




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-05 09:30 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "balsa".
   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 pipis384@latinmail.com.
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 Vincent Noel 2004-08-06 19:32:30 UTC

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