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 494807 - crash in Evolution: switched my calendar fro...
crash in Evolution: switched my calendar fro...
Status: RESOLVED DUPLICATE of bug 450551
Product: evolution
Classification: Applications
Component: general
2.12.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-11-08 00:48 UTC by Sam Morris
Modified: 2008-02-22 14:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Sam Morris 2007-11-08 00:48:04 UTC
What were you doing when the application crashed?
switched my calendar from Month to Day view


Distribution: Debian lenny/sid
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-fixdso #1 SMP Sat Aug 25 16:14:05 BST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: gnome

Memory status: size: 272441344 vsize: 272441344 resident: 18804736 share: 6393856 rss: 18804736 rss_rlim: 4294967295
CPU usage: start_time: 1194469032 rtime: 2995 utime: 2810 stime: 185 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-data-server-1.12'

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb73406b0 (LWP 9597)]
[New Thread 0xa57b6b90 (LWP 16607)]
[New Thread 0xb67d8b90 (LWP 9636)]
[New Thread 0xb7096b90 (LWP 9598)]
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread 0xa57b6b90 (LWP 16607))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_mutex_lock_86
    from /lib/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #4 gnome_segv_handler
    at server.c line 101
  • #5 <signal handler called>
  • #6 g_value_object_collect_value
    at /tmp/buildd/glib2.0-2.14.1/gobject/gobject.c line 1957
  • #7 IA__g_object_new_valist
    at /tmp/buildd/glib2.0-2.14.1/gobject/gobject.c line 1015
  • #8 IA__g_object_new
    at /tmp/buildd/glib2.0-2.14.1/gobject/gobject.c line 795
  • #9 e_data_cal_view_new
    at e-data-cal-view.c line 422
  • #10 impl_Cal_getQuery
  • #11 _ORBIT_skel_small_GNOME_Evolution_Calendar_Cal_getQuery
    at Evolution-DataServer-Calendar-common.c line 136
  • #12 ORBit_POAObject_invoke
    at poa.c line 1142
  • #13 ORBit_OAObject_invoke
    at orbit-adaptor.c line 338
  • #14 ORBit_small_invoke_adaptor
    at orbit-small.c line 844
  • #15 ORBit_POAObject_handle_request
    at poa.c line 1351
  • #16 ORBit_POAObject_invoke_incoming_request
    at poa.c line 1421
  • #17 giop_thread_queue_process
    at giop.c line 771
  • #18 giop_request_handler_thread
    at giop.c line 481
  • #19 g_thread_pool_thread_proxy
    at /tmp/buildd/glib2.0-2.14.1/glib/gthreadpool.c line 265
  • #20 g_thread_create_proxy
    at /tmp/buildd/glib2.0-2.14.1/glib/gthread.c line 635
  • #21 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #22 clone
    from /lib/i686/cmov/libc.so.6


----------- .xsession-errors (166553 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Milan Crha 2008-02-22 14:35:36 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 450551 ***