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 480624 - crash in Tasks: recuperation de mail sur...
crash in Tasks: recuperation de mail sur...
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-26 15:02 UTC by ignace.bienville
Modified: 2008-05-02 10:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description ignace.bienville 2007-09-26 15:02:05 UTC 
Version: 2.10

What were you doing when the application crashed?
recuperation de mail sur evolution



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.20-2931.fc7xen #1 SMP Mon Aug 13 10:11:56 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 667783168 vsize: 667783168 resident: 71294976 share: 37416960 rss: 71294976 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190810220 rtime: 3627 utime: 1818 stime: 1809 cutime:216 cstime: 1601 timeout: 0 it_real_value: 0 frequency: 100

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

(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 46912496500880 (LWP 5003)]
[New Thread 1126455632 (LWP 5042)]
[New Thread 1084229968 (LWP 5007)]
(no debugging symbols found)
0x00000031f940d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 165667

Thread 1 (Thread 46912496500880 (LWP 5003))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #4 g_hash_table_foreach
    from /lib64/libglib-2.0.so.0
  • #5 e_tree_table_adapter_save_expanded_state
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #6 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #7 message_list_set_folder
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #8 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #9 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #10 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #11 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #12 ??
    from /lib64/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #15 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (22 sec old) ---------------------
(evolution:5003): camel-pop3-provider-WARNING **: Bad server response:  Disconnect because authentication is too long
(evolution:5003): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Impossible de se connecter au serveur POP pop.laposte.net.
Erreur lors de l'envoi du mot de passe : Opération maintenant en cours
(evolution:5003): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(evolution:5003): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(evolution:5003): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(evolution:5003): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
--------------------------------------------------
Comment 1 Akhil Laddha 2008-05-02 10:37:45 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
we are happy to tell you that the problem has already been fixed. It should be
solved in the next software version. You may want to check for a software
upgrade.

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