Bug 498918 – crash in Evolution:

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 498918 - crash in Evolution:


Summary:	crash in Evolution:


Status:	RESOLVED DUPLICATE of bug 426237

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.12.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-22 08:07 UTC by Mike
Modified:	2007-11-24 23:02 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description Mike 2007-11-22 08:07:37 UTC

What were you doing when the application crashed?



Distribution: Mandriva Linux release 2008.0 (Cooker) for x86_64
Gnome Release: 2.19.5 2007-07-08 (Mandriva)
BugBuddy Version: 2.20.1

System: Linux 2.6.22.9-desktop-1mdv #1 SMP Wed Sep 26 22:36:49 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Ia Ora Free
Icon Theme: gnome

Memory status: size: 371650560 vsize: 371650560 resident: 24797184 share: 6553600 rss: 24797184 rss_rlim: 18446744073709551615
CPU usage: start_time: 1195667957 rtime: 178 utime: 163 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib64/evolution-data-server-1.12'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47954347578432 (LWP 3835)]
[New Thread 1149540688 (LWP 27256)]
[New Thread 1115969872 (LWP 3869)]
[New Thread 1074006352 (LWP 3836)]
(no debugging symbols found)
0x00002b9d3d6c891e in waitpid () from /lib64/libc.so.6

+ Trace 179217

Thread 2 (Thread 1149540688 (LWP 27256))

#0 __lll_mutex_lock_wait
from /lib64/libpthread.so.0
#1 _L_mutex_lock_97
from /lib64/libpthread.so.0
#2 pthread_mutex_lock
from /lib64/libpthread.so.0
#3 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
#4 <signal handler called>
#5 g_type_check_is_value_type
from /usr/lib64/libgobject-2.0.so.0
#6 g_value_type_compatible
from /usr/lib64/libgobject-2.0.so.0
#7 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
from /usr/lib64/libgobject-2.0.so.0
#8 g_object_new_valist
from /usr/lib64/libgobject-2.0.so.0
#9 g_object_new
from /usr/lib64/libgobject-2.0.so.0
#10 e_data_cal_view_new
from /usr/lib64/libedata-cal-1.2.so.6
#11 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
from /usr/lib64/libedata-cal-1.2.so.6
#12 ORBit_small_invoke_adaptor
from /usr/lib64/libORBit-2.so.0
#13 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
from /usr/lib64/libORBit-2.so.0
#14 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
from /usr/lib64/libORBit-2.so.0
#15 giop_thread_queue_process
from /usr/lib64/libORBit-2.so.0
#16 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
from /usr/lib64/libORBit-2.so.0
#17 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
from /usr/lib64/libglib-2.0.so.0
#18 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
from /usr/lib64/libglib-2.0.so.0
#19 start_thread
from /lib64/libpthread.so.0
#20 clone
from /lib64/libc.so.6



----------- .xsession-errors ---------------------
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x19865f2
X Error: BadAccess (attempt to access private resource denied) 10
  Major opcode:  2
  Minor opcode:  0
  Resource id:  0x380000e
total-tracks: 1
testing-track: 0
MP4 - 2 channels @ 46909632851012 Hz
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x252
--------------------------------------------------

Comment 1 Susana 2007-11-24 23:02:02 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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