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 312583 - EDS crashing tracking bug
EDS crashing tracking bug
Status: RESOLVED INCOMPLETE
Product: evolution-data-server
Classification: Platform
Component: Calendar
1.4.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
evolution[groupwise]
Depends on:
Blocks: 327516
 
 
Reported: 2005-08-04 14:27 UTC by Poornima
Modified: 2013-09-14 16:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Poornima 2005-08-04 14:27:16 UTC
Crashes while launching evolution


Backtrace was generated from '/opt/gnome/libexec/evolution-data-server-1.4'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1085519424 (LWP 31944)]
[New Thread 1115904944 (LWP 32000)]
[Thread debugging using libthread_db enabled]
[New Thread 1085519424 (LWP 31944)]
[New Thread 1115904944 (LWP 32000)]
[Thread debugging using libthread_db enabled]
[New Thread 1085519424 (LWP 31944)]
[New Thread 1115904944 (LWP 32000)]
[New Thread 1113803696 (LWP 31998)]
[New Thread 1098820528 (LWP 31968)]
[New Thread 1091922864 (LWP 31945)]
0xffffe410 in ?? ()

Thread 2 (Thread 1115904944 (LWP 32000))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __lll_mutex_lock_wait
    from /lib/tls/libpthread.so.0
  • #5 _L_mutex_lock_33
    from /lib/tls/libpthread.so.0
  • #6 ??
  • #7 ??
  • #8 ??
    from /lib/tls/libc.so.6
  • #9 main_arena
    from /lib/tls/libc.so.6
  • #10 ??
  • #11 ??
  • #12 gnome_segv_handler
    at server.c line 92
  • #13 gnome_segv_handler
    at server.c line 92
  • #14 <signal handler called>
  • #15 _int_malloc
    from /lib/tls/libc.so.6
  • #16 malloc
    from /lib/tls/libc.so.6
  • #17 g_malloc
    from /opt/gnome/lib/libglib-2.0.so.0
  • #18 scan_attachment
    at e-cal-component.c line 522
  • #19 scan_property
    at e-cal-component.c line 664
  • #20 scan_icalcomponent
    at e-cal-component.c line 943
  • #21 e_cal_component_set_icalcomponent
    at e-cal-component.c line 1105
  • #22 e_cal_backend_cache_get_components
    at e-cal-backend-cache.c line 438
  • #23 cache_init
    at e-cal-backend-groupwise.c line 676
  • #24 g_thread_create_full
    from /opt/gnome/lib/libglib-2.0.so.0
  • #25 start_thread
    from /lib/tls/libpthread.so.0
  • #26 clone
    from /lib/tls/libc.so.6

Comment 1 Poornima 2005-08-04 14:28:53 UTC
Groupwise debug traces fo the above crash

POST /soap HTTP/1.1
SOAP-Debug: 0x41267b18 @ 1123165600
Host: 164.99.169.177
Connection: Keep-Alive
User-Agent: Evolution/1.3.6
Content-Type: text/xml
SOAPAction: getCategoryListRequest

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"><SOAP-ENV:Header
SOAP-ENV:encodingStyle=""><session>Xire2wHu2mmvRFfu</session></SOAP-ENV:Header><SOAP-ENV:Body
xmlns:types="http://schemas.novell.com/2003/10/NCSP/types.xsd"
SOAP-ENV:encodingStyle=""><getCategoryListRequest/></SOAP-ENV:Body></SOAP-ENV:Envelope>

libecalbackendgroupwise-Message: e-cal-backend-groupwise.c:1454: Starting query (#t)
libecalbackendgroupwise-Message: e-cal-backend-groupwise.c:1408: Getting object
list (#t)
200
SOAP-Debug: 0x41267b18 @ 1123165600
Pragma: no-cache
Date: Thu, 04 Aug 2005 19:56:17 GMT
Server: Windows NT GroupWise POA 7.0
Content-Length: 1285
Content-Type: text/xml

<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header
SOAP-ENV:encodingStyle=""/><SOAP-ENV:Body SOAP-ENV:encodingStyle=""
xmlns:types="http://schemas.novell.com/2003/10/NCSP/types.xsd"><getCategoryListResponse><categories><category><id>4.dell.net.100.0.1.0.1@61</id><name>Low
priority</name><version>1</version><modified>2005-07-15T19:30:01Z</modified><type>LowPriority</type><color>12632256</color></category><category><id>3.dell.net.100.0.1.0.1@61</id><name>Urgent</name><version>1</version><modified>2005-07-15T19:30:01Z</modified><type>Urgent</type><color>255</color></category><category><id>2.dell.net.100.0.1.0.1@61</id><name>Follow-up</name><version>1</version><modified>2005-07-15T19:30:01Z</modified><type>FollowUp</type><color>33023</color></category><category><id>1.dell.net.100.0.1.0.1@61</id><name>Personal</name><version>1</version><modified>2005-07-15T19:30:01Z</modified><type>Personal</type><color>16711680</color></category></categories><status><code>0</code></status></getCategoryListResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
libecalbackendgroupwise-Message: e-cal-backend-groupwise.c:1454: Starting query
((has-alarms-in-range? (make-time "20050804T142640Z") (make-time
"20050804T183000Z")))
libecalbackendgroupwise-Message: e-cal-backend-groupwise.c:1408: Getting object
list ((has-alarms-in-range? (make-time "20050804T142640Z") (make-time
"20050804T183000Z")))
Comment 2 Poornima 2005-08-05 06:55:33 UTC
Changing priority as its crashing repeatedly with these crashe traces
Comment 3 viren 2005-09-09 06:48:12 UTC
Does this still occur with the recent version(s) ?
Comment 4 Poornima 2005-09-12 09:42:31 UTC
This bug I dont see happening now. If u feel it has got fixed due to fix for
some other bug, this bug can be closed. Since these are random crashes you
should not close it unless u are sure fix for some other bug has fixed this bug.
Comment 5 André Klapper 2005-09-28 12:10:06 UTC
retargetting from 1.3 to 1.5 to get rid of that busted milestones (as discussed
with harish on irc)
Comment 6 André Klapper 2006-02-09 21:52:16 UTC
Closing this bug report as no further information has been provided.