Ubuntu
evolution-exchange package

evolution-exchange-storage crashed with SIGSEGV in e_folder_exchange_bpropfind_start()

Bug #150387 reported by Zac Barton
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
evolution-exchange
Expired
Critical
evolution-exchange (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution-exchange

loaded up evolution fine but got error when refreshing folders

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Oct 8 09:39:30 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/evolution/2.12/evolution-exchange-storage
NonfreeKernelModules: nvidia
Package: evolution-exchange 2.12.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/evolution/2.12/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Connector_CalFactory:1.2 --oaf-ior-fd=23
ProcCwd: /
ProcEnviron:
 PATH=/home/zac/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution-exchange
Stacktrace:
 #0 0xb7177135 in e_folder_exchange_bpropfind_start ()
    from /usr/lib/libexchange-storage-1.2.so.3
 #1 0x0805c95a in ?? ()
 #2 0x0843af48 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 e_folder_exchange_bpropfind_start ()
 ?? ()
 ?? ()
 ?? ()
Title: evolution-exchange-storage crashed with SIGSEGV in e_folder_exchange_bpropfind_start()
Uname: Linux thecollective 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0xb7177135 <e_folder_exchange_bpropfind_start+37>: cmp (%edx),%eax
 PC (0xb7177135) ok
 source "(%edx)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA

See original description
Tags: apport-crash
Revision history for this message
Zac Barton (zacbarton) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:e_folder_exchange_bpropfind_start (folder=0x843af48, op=0x0, hrefs=0x856a4c0, nhrefs=63,
refresh_folder_internal (stub=0x80a8cd0, mfld=0x8204a88, background=0) at mail-stub-exchange.c:1386
refresh_folder (stub=0x80a8cd0, folder_name=0x83d5838 "personal/Inbox") at mail-stub-exchange.c:1522
connection_handler (source=0x80f3f08, condition=G_IO_IN, data=0x80a8cd0) at mail-stub.c:170
g_io_unix_dispatch (source=0x80f7030, callback=0x80635f0 <connection_handler>, user_data=0x80a8cd0)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in evolution-exchange:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=484709

Changed in evolution-exchange:
assignee: nobody → desktop-bugs
status: New → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in evolution-exchange:
status: Unknown → New
Kees Cook (kees)
description: updated
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We have evolution exchange 2.30 on Maverick and the upstream maintainers are asking for testing on that version, may you please test with it and provide feedback ? Thanks in advance.

Changed in evolution-exchange (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: Triaged → Incomplete
Bug Watch Updater (bug-watch-updater)
Changed in evolution-exchange:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in evolution-exchange:
status: Incomplete → Invalid
Changed in evolution-exchange (Ubuntu):
status: Incomplete → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in evolution-exchange:
importance: Unknown → Critical
status: Invalid → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.