*** This bug is a duplicate of bug 304385 ***
https://bugs.launchpad.net/bugs/304385
** This bug has been marked a duplicate of bug 304385
crash in account_changed ()
--
evolution crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/306161
You received this bug notif
Given that there is an upstream bug report of the same bug, which
includes detailed backtrace, and the upstream developers have confirmed
this bug, I think we can safely say that this is confirmed.
Also, given that it appears to affect a number of users, is a common
configuration, I request that t
I noticed this bug only occuring for IMAP-Accounts. When editing a POP-
Account everything is fine, when editing IMAP-Accounts it crashes.
--
evolution crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/306161
You received this bug notification because you are a member of
The root cause seems to me this upstream bug:
http://bugzilla.gnome.org/show_bug.cgi?id=560188
Which is marked duplicated of this bug:
http://bugzilla.gnome.org/show_bug.cgi?id=552583
Bug 552583 is fixed upstream already, so we probably need to wait for
2.24.3. Planned upstream release is
the apport retracing didn't work that's why a stacktrace is required,
the delay is due to the number of bugs compared to the number of
volunter to work on those, the wiki page indicated has the required
details on how to get the informations
--
evolution crashed with SIGSEGV in g_closure_invoke()
It took a month to decide you needed a backtrace?
First, you tell me to use apport because it gives you all the
information you need, and then you say you don't have it all, and
require a backtrace now. So tell me how exactly can I generate a
backtrace because I don't know? Your first two contri
I tried to do a backtrace, it's my first time though and I'm not sure i
did it write. Hope this helps.
** Attachment added: "gdb-evolution.txt.gz"
http://launchpadlibrarian.net/21054338/gdb-evolution.txt.gz
--
evolution crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bug
As said in my previous comment we need a backtrace of the crash without
one the bug is no use for the developers in order to fix it, thanks.
** Attachment removed: "CoreDump.gz"
http://launchpadlibrarian.net/20298088/CoreDump.gz
--
evolution crashed with SIGSEGV in g_closure_invoke()
https:/
I can confirm this email too with GMAIL IMAP and local copies of
messages.
--
evolution crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/306161
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
I can also confirm this, it's very anoying. I can also add that I've
noticed this happenning after trying to set up an account with 'local
delivery' to read my local emails sent to me by cron. I'm not sure how
it's related, but I know that the local delivery feature/ read mbox
feature also doesn't
StacktraceTop:?? ()
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist ()
g_signal_emit () from /usr/lib/libgobject-2.0.so.0
** Tags removed: need-amd64-retrace
** Tags added: apport-failed-retrace
** Attachment added: "Stacktrace.
Can someone explain why this is marked as incomplete? I used the Ubuntu
Bug reporting application to open this bug, therefore if it's incomplete
- please explain what you need?
I was told to use the bug reporting application, because the original
bug I reported lacked information. Now, when I re
** Changed in: evolution (Ubuntu)
Status: New => Incomplete
--
evolution crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/306161
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
Please do not attach .crash reports to the reports, if you want to , you
can take a backtrace with the instructions located at
http://wiki.ubuntu.com/DebuggingProgramCrash ; thanks.
** Attachment removed: "_usr_bin_evolution.1000.crash.gz"
http://launchpadlibrarian.net/20390517/_usr_bin_evolution
I have the exact same error. Evolution exits with
(evolution:10227): e-data-server-CRITICAL **: e_account_set_string: assertion
`ea != NULL' failed
Segmentation fault (core dumped)
It results in Evolution being unusable since I can't modify any
settings.
** Attachment added: "_usr_bin_evolutio
I can confirm this bug. Evolution crashes as soon as you hit the "Apply"
Button in the account settings. Regardless if you really changed
anything or not.
--
evolution crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/306161
You received this bug notification because you
Any ideas on a fix?
** Visibility changed to: Public
--
evolution crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/306161
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in ubuntu.
--
desktop-bugs ma
17 matches
Mail list logo
