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 472898 - crash in Email:
crash in Email:
Status: RESOLVED DUPLICATE of bug 431459
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-02 18:16 UTC by snippet345
Modified: 2007-09-03 13:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description snippet345 2007-09-02 18:16:37 UTC 
Version: 2.10

What were you doing when the application crashed?



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: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 191414272 vsize: 191414272 resident: 66039808 share: 57982976 rss: 66039808 rss_rlim: 4294967295
CPU usage: start_time: 1188756957 rtime: 138 utime: 119 stime: 19 cutime:3 cstime: 7 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 -1209035040 (LWP 6416)]
[New Thread -1347736688 (LWP 6481)]
[New Thread -1262273648 (LWP 6454)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 159884

Thread 1 (Thread -1209035040 (LWP 6416))

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


----------- .xsession-errors (4095 sec old) ---------------------
120600K .......... .......... .......... .......... ..........    1.42 MB/s
120650K .......... .......... .......... .......... ..........    1.29 MB/s
120700K .......... .......... .......... .......... ..........    1.27 MB/s
120750K .......... .......... .......... .......... ..........    1.44 MB/s
120800K .......... .......... .......... .......... ..........    1.65 MB/s
120850K .......... .......... .......... .......... ..........    1.45 MB/s
120900K .......... .......... .......... .......... ..........    2.06 MB/s
120950K .......... .......... .......... .......... ..........    1.58 MB/s
121000K .......... .......... .......... .......... ..........    1.44 MB/s
121050K .......... .......... .......... .......... ..........    1.68 MB/s
121100K .......... .......... .......... .......... ..........    1.15 MB/s
121150K .......... .......... .......... .......... ..........    2.35 MB/s
121200K .......... .......... .......... .......... ..........    2.47 MB/s
121250K .......... ...
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-03 13:09:21 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 ***