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 471513 - crash in Tasks: Intentando copiar archiv...
crash in Tasks: Intentando copiar archiv...
Status: RESOLVED DUPLICATE of bug 444924
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-29 18:49 UTC by carlos.sepulveda
Modified: 2007-08-30 04:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description carlos.sepulveda 2007-08-29 18:49:54 UTC
Version: 2.10

What were you doing when the application crashed?
Intentando copiar archivos entre la carpeta SPAM y una IMAP en el servidor


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Bluecurve

Memory status: size: 264388608 vsize: 264388608 resident: 93270016 share: 76902400 rss: 93270016 rss_rlim: 4294967295
CPU usage: start_time: 1188402517 rtime: 6352 utime: 6068 stime: 284 cutime:581 cstime: 51 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209121056 (LWP 10435)]
[New Thread -1261864048 (LWP 10495)]
[New Thread -1367082096 (LWP 10494)]
[New Thread -1272358000 (LWP 10456)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209121056 (LWP 10435))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free_chain_with_offset
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #16 ??
    from /lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #18 ??
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /lib/libglib-2.0.so.0
  • #23 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #24 ??
    from /lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #26 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #27 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (10568 sec old) ---------------------
new dimensions = (48,48)
initial setting of an image.  no scaling
scale = 1
new dimensions = (48,48)
we need to scale up
scale = 1
new dimensions = (48,48)
initial setting of an image.  no scaling
scale = 1
new dimensions = (48,48)
we need to scale up
scale = 1
DEBUG: INBOX/Mas Servicio (imap://casep@smtp.tuxpan.com/INBOX/Mas%20Servicio)
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Tobias Mueller 2007-08-30 04:47:41 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 444924 ***