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 437708 - 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-05-11 15:30 UTC by Julio Gomez
Modified: 2007-06-17 22:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Julio Gomez 2007-05-11 15:30:17 UTC
What were you doing when the application crashed?



Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Free
Icon Theme: gnome

Memory status: size: 126091264 vsize: 126091264 resident: 27791360 share: 18886656 rss: 27791360 rss_rlim: 4294967295
CPU usage: start_time: 1178890082 rtime: 192 utime: 174 stime: 18 cutime:0 cstime: 0 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/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1236875552 (LWP 18204)]
[New Thread -1281295456 (LWP 18271)]
[New Thread -1327539296 (LWP 18270)]
[New Thread -1289688160 (LWP 18268)]
[New Thread -1302361184 (LWP 18240)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1236875552 (LWP 18204))

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


----------- .xsession-errors (14 sec old) ---------------------
unlocking urpmi database
getting exclusive lock on urpmi
unlocking urpmi database
kbuildsycoca running...
DCOP Cleaning up dead connections.
kio (KIOConnection): ERROR: Could not write data
CalDAV Eplugin starting up ...
(evolution:18204): evolution-smime-WARNING **: initializing security library without cert databases.
(evolution:18204): e-data-server-DEBUG: Loaded default categories
(evolution:18204): e-data-server-DEBUG: Saving categories to "/home/julio/.evolution/categories.xml"
(evolution:18204): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
** (evolution:18204): DEBUG: mailto URL command: evolution %s
** (evolution:18204): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 Susana 2007-05-12 00:45:24 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.
Could you please install some debugging packages [1], start the application as
normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk,
glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided
by your distribution). More details can be found here:
http://live.gnome.org/GettingTraces
Comment 2 André Klapper 2007-06-17 22:13:22 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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