Evolution does not start: GThread-ERROR **: file /build/buildd/glib2.0-2.20.1/gthread/gthread-posix.c

[Yasir M Elsharif]

Binary package hint: evolution

Evolution doesn't start when I click on it's icon, nor does when I write a command "evolution --component=mail" or "evolution", instead I got the message bellow:
-----------------------------------------------
$ evolution --component=mail
** (evolution:4232): DEBUG: Loading Exchange MAPI Plugin

** (evolution:4232): DEBUG: MAPI listener is constructed with 0 listed MAPI accounts
** (evolution:4232): DEBUG: mailto URL command: evolution %s
** (evolution:4232): DEBUG: mailto URL program: evolution
** (evolution:4232): DEBUG: EI: SHELL STARTUP

GThread-ERROR **: file /build/buildd/glib2.0-2.20.1/gthread/gthread-posix.c: line 171 (g_mutex_free_posix_impl): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
Aborted
-------------------------------------------------------------
some details here:
----------------------------------
$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
----------------------------------------
$ apt-cache policy evolution
evolution:
  Installed: 2.26.1-0ubuntu1
  Candidate: 2.26.1-0ubuntu1
  Version table:
 *** 2.26.1-0ubuntu1 0
        500 http://sd.archive.ubuntu.com jaunty/main Packages
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status
----------------------------------------

[Steve (stupendoussteve-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
We are closing this bug report because it lacks the information [backtrace] 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".