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

Bug #256958 reported by Paul Wagland
2
Affects Status Importance Assigned to Milestone
evolution-exchange
Expired
Critical
evolution-exchange (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: evolution-exchange

Reporting as a new problem since it crashes in a different place, but this might be another instantiation of http://bugzilla.gnome.org/show_bug.cgi?id=544115

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/evolution/2.24/evolution-exchange-storage
NonfreeKernelModules: nvidia
Package: evolution-exchange 2.23.6-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/evolution/2.24/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Connector_CalFactory:1.2 --oaf-ior-fd=27
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
Signal: 11
SourcePackage: evolution-exchange
StacktraceTop:
 get_folder_contents_online_func (data=0x3319f60)
 ?? () from /usr/lib/libglib-2.0.so.0
 start_thread () from /lib/libpthread.so.0
 clone () from /lib/libc.so.6
 ?? ()
Title: evolution-exchange-storage crashed with SIGSEGV in get_folder_contents_online_func()
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin audio cdrom dialout dip disk floppy haldaemon lpadmin messagebus plugdev scanner vboxusers video

Tags: apport-crash
Revision history for this message
Paul Wagland (paul-kungfoocoder) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks for the report, looks like bug http://bugzilla.gnome.org/show_bug.cgi?id=542505

Changed in evolution-exchange:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Paul Wagland (paul-kungfoocoder) wrote :

I am not sure that this is the same problem, as that was reported against a very different version of the software, and this is quite a new problem for me. I believe that this was introduced in 2.23.6, and is actually an instantiation of the problem that I linked to in the first comment.

Changed in evolution-exchange:
status: Unknown → Incomplete
Changed in evolution-exchange:
status: Incomplete → Invalid
Revision history for this message
Pedro Villavicencio (pedro) wrote :

are you still having this issue? could you try with latest package on jaunty?

Changed in evolution-exchange:
status: Triaged → Incomplete
Changed in evolution-exchange:
status: Incomplete → Fix Released
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.

Other bug subscribers

Remote bug watches

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