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 494194 - crash in Evolution:
crash in Evolution:
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-11-06 15:09 UTC by plessis.adrien
Modified: 2008-02-20 13:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description plessis.adrien 2007-11-06 15:09:58 UTC
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: Gorilla

Memory status: size: 461844480 vsize: 461844480 resident: 35426304 share: 19689472 rss: 35426304 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194358229 rtime: 160 utime: 134 stime: 26 cutime:3 cstime: 11 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 0x2adab94fcf90 (LWP 16881)]
[New Thread 0x42804950 (LWP 16926)]
[New Thread 0x42003950 (LWP 16925)]
[New Thread 0x41802950 (LWP 16905)]
[New Thread 0x41001950 (LWP 16904)]
[New Thread 0x40800950 (LWP 16901)]
(no debugging symbols found)
0x00002adab13e0c7f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2adab94fcf90 (LWP 16881))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    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 ??
    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 (872 sec old) ---------------------
2b629b9cc000-2b629bbcc000 ---p 0002a000 08:01 854825                     /usr/lib/openoffice/program/typemgr.uno.so
2b629bbcc000-2b629bbcf000 rw-p 0002a000 08:01 854825                     /usr/lib/openoffice/program/typemgr.uno.so
2b629bbcf000-2b629bbe3000 r-xp 00000000 08:01 854784                     /usr/lib/openoffice/program/implreg.uno.so
2b629bbe3000-2b629bde3000 ---p 00014000 08:01 854784                     /usr/lib/openoffice/program/implreg.uno.so
2b629bde3000-2b629bde4000 rw-p 00014000 08:01 854784                     /usr/lib/openoffice/program/implreg.uno.so
2b629bde4000-2b629be02000 r-xp 00000000 08:01 854815                     /usr/lib/openoffice/program/security.uno.so
2b629be02000-2b629c002000 ---p 0001e000 08:01 854815                     /usr/lib/openoffice/program/security.uno.so
2b629c002000-2b629c004000 rw-p 0001e000 08:01 854815                     /usr/lib/openoffice/program/security.uno.so
2b629c004000-2b629c024000 r-xp 00000000 08:01 854809                     /usr/lib/openoffice/program/libreg.so.3
2b629c024000-2b629c224000 ---p 00020000 08:01 854809                     /usr/lib/openoffice/program/libreg.so.3
2b629c224000-2b629c225000 rw-p 00020000 08:01 854809                     /usr/lib/openoffice/program/libreg.so.3
2b629c225000-2b629c241000 r-xp 00000000 08:01 854820                     /usr/lib/openoffice/program/libstore.so.3
2b629c241000-2b629c440000 ---p 0001c000 08:01 854820                     /usr/lib/openoffice/program/libstore.so.3
2b629c440000-2b629c44200
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-20 13:33:26 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 ***