Just kill process 'evolution-data-server-2.26'.
Restart Evolution..
--
evolution crashes on startup
https://bugs.launchpad.net/bugs/373842
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
there is no crash listed there, do you get that every time?
--
evolution crashes on startup
https://bugs.launchpad.net/bugs/373842
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
When I do this it locks up when I switch to calendar.
Here is what I get
(gdb) continue
Continuing.
[New Thread 0xb63a8b90 (LWP 4251)]
Cannot get thread event message: debugger service failed
(gdb) backtrace
#0 0xb7ef2430 in __kernel_vsyscall ()
#1 0xb73b6ae7 in poll () from /lib/tls/i686/cmov
the log you got shows it's eds crashing and not evolution
the way to get a stacktrace is either to use apport or gdb this way
- start evolution on the email component
- gdb --pid `pidof evolution-data-server-2.26`
(gdb) continue
- switch evolution to the calendar
- the gdb prompt will be stopped
the way to get a stacktrace is either to use apport or gdb this way
- start evolution on the email component
- gdb --pid `pidof evolution-data-server-2.26`
(gdb) continue
- switch evolution to the calendar
- the gdb prompt will be stopped on the e-d-s crash
(gdb) backtrace
--
evolution crashes on
Hello Sebastien,
I am not sure of the difference between a stacktrace and a backtrace.
Here is what I do
In terminal
gdb evolution 2>&1 | tee gdb-evolution.txt
handle SIG33 pass nostop noprint
set pagination 0
run
Then in the Evolution gui
Create an event that recurs every week.
Save the eve
could you get an evolution-data-server stacktrace using gdb?
--
evolution crashes on startup
https://bugs.launchpad.net/bugs/373842
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I just tried the proposed evolution-data-server and it still freezes. I also
tried the proposed libical
as per bug #368508 but still no luck.
--
evolution crashes on startup
https://bugs.launchpad.net/bugs/373842
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Well, without trying I was able to replicate the events that led to the
first lock up. In Calendar, I was modifying a recurring event,
selected All Instances and wham. I renamed the .evolution file,
restarted and was able to replicate it a third time. I am not sure how
to generate the stacktr
--
evolution crashes on startup
https://bugs.launchpad.net/bugs/373842
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I was able to get Evolution working again by renaming the .evolution
directory and then restarting. No big deal since I had only been using
it a few hours and my messages were still on the my email servers.
Unfortunately while I was trying to recreate the bug I accidently wrote
over the old .evolu
the stacktrace indicates an evolution-data-server crash, could you get a
stacktrace for this one? you could also try the update on bug #368508
and see if it workaround the bug
** Package changed: evolution (Ubuntu) => evolution-data-server (Ubuntu)
** Changed in: evolution-data-server (Ubuntu)
Hello Pedro,
There are no files in /var/crash. When I launch Evolution it freezes
and I have to use force quit to close it. This doesn't seem to generate
a crash file. I generated a backtrace which is attached. Should I
submit this?
Cheers, Jeff
Pedro Villavicencio wrote:
> Thank you fo
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
14 matches
Mail list logo
