evolution crashes with segmentation fault

Bug #793381 reported by joshiss
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: evolution

I have a typical situation
I am across my office proxy using ubuntu 11.04.
I have set the static ip and also the network proxy to entire system through network proxy settings.
I use and like evolution as my mail handler and i am using it for almost 5 years now. This problem which i will tell you was not there before ubuntu 11.04.
To update i use to use apt-get command from command window. it was not working after upgrade to ubuntu 11.04. from ubuntu community i found out to add lines given below in my /home/`/.bashrc
export http_proxy=192.168.90.94:8080
export https_proxy=192.168.90.94:8080
export ftp_proxy=192.168.90.94:8080

In evolution I have set network preferences as use system defaults.
Now when io try to use evolution to send and receive mails it does not work it gives error of time out.
Next when i set network proxy system wide to direct connection and then run evolution from user prompt in command window then the evolution starts fetchin mails and sending them. I tried with removing the lines from .bashrc and then using system proxy settings it never worked.
i ried to set proxy in evolution separately it still didn't work. This has become a great unconvinience as if i use direct connection settings in network proxy settings it stops browsers and other applications from using internet across proxy and only evolution fetches mails. and vice a versa. Am i amking any mistake. can this be set right.
Please help.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: evolution 2.32.2-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Jun 6 11:53:46 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110419)
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, user)
 LANG=en_IN
 LC_MESSAGES=en_IN.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
joshiss (joshiss) wrote :
Revision history for this message
Maarten Bezemer (veger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

According to the title you are having a 'crash with a segmentation fault', in your description you do not mention this anymore and provide a lot of configuration settings/tries.

Could you update your description by telling when the crash occurs (which configuration settings are at fault), and provide a backtrace so we can (better) see what happend?

More instructions on obtaining backtraces can be found at http://wiki.ubuntu.com/DebuggingProgramCrash specific information on obtaining backtraces for evolution can be found at http://projects.gnome.org/evolution/bugs.shtml

Changed in evolution (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in evolution (Ubuntu):
status: Incomplete → Invalid
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.