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 521868 - crash in Email: exit from evolution
crash in Email: exit from evolution
Status: RESOLVED DUPLICATE of bug 431459
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-03-11 21:30 UTC by bugzilla
Modified: 2008-03-12 16:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bugzilla 2008-03-11 21:30:38 UTC 
Version: 2.10

What were you doing when the application crashed?
exit from evolution


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-15 (ASPLinux)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.15-80.0.120asp #1 SMP Thu Feb 28 20:15:16 EET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 121020416 vsize: 121020416 resident: 48390144 share: 38428672 rss: 48390144 rss_rlim: 4294967295
CPU usage: start_time: 1205269043 rtime: 282 utime: 256 stime: 26 cutime:0 cstime: 3 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 -1209014560 (LWP 3420)]
[New Thread -1275057264 (LWP 14296)]
[New Thread -1233126512 (LWP 3463)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 192125

Thread 1 (Thread -1209014560 (LWP 3420))

  • #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 






Comment 1


Tobias Mueller





          2008-03-12 16:30:50 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 ***