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 456079 - crash in Evolution: Reading emails...
crash in Evolution: Reading emails...
Status: RESOLVED DUPLICATE of bug 431459
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-12 00:42 UTC by Shane Donohoe
Modified: 2007-10-14 13:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Shane Donohoe 2007-07-12 00:42:02 UTC
What were you doing when the application crashed?
Reading emails...


Distribution: Unknown
Gnome Release: 2.18.1 2007-04-23 (Archlinux)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-ARCH #1 SMP PREEMPT Sat Apr 7 17:08:55 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaEssenseAquish
Icon Theme: Tango-custom

Memory status: size: 341909504 vsize: 341909504 resident: 39104512 share: 20828160 rss: 39104512 rss_rlim: 18446744073709551615
CPU usage: start_time: 1180279690 rtime: 221 utime: 193 stime: 28 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 48011399558432 (LWP 5330)]
[New Thread 1115703616 (LWP 5373)]
[New Thread 1107310912 (LWP 5370)]
[New Thread 1124096320 (LWP 5366)]
[New Thread 1140881728 (LWP 5341)]
[New Thread 1132489024 (LWP 5340)]
[New Thread 1098918208 (LWP 5335)]
[New Thread 1090525504 (LWP 5334)]
[New Thread 1082132800 (LWP 5333)]
(no debugging symbols found)
0x00002baa7fda9a9f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 48011399558432 (LWP 5330))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_segv_handle
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #5 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #6 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #7 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (25 sec old) ---------------------
** Message: volume = 0
(evolution-2.10:5330): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one
(evolution-2.10:5330): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0'
** (evolution-2.10:5330): DEBUG: mailto URL command: evolution %s
** (evolution-2.10:5330): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
get donohoe.shane pop://donohoe.shane@pop.gmail.com/
Find Items 0
get priestoftime pop://priestoftime@pop.gmail.com/
Find Items 0
get marycatdon pop://marycatdon@pop.gmail.com/
Find Items 0
--------------------------------------------------
Comment 1 palfrey 2007-07-12 11:23:07 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!
Comment 2 Tobias Mueller 2007-10-14 13:20:52 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 431459 ***