** Changed in: evolution
Importance: Unknown = Critical
--
Crashes on close
https://bugs.launchpad.net/bugs/57975
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: evolution (upstream)
Status: Confirmed = Fix Released
--
Crashes on close
https://launchpad.net/bugs/57975
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Upstream has a patch ready at
http://bugzilla.gnome.org/attachment.cgi?id=75922action=view
--
Crashes on close
https://launchpad.net/bugs/57975
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I followed up on the upstream bug report.
--
Crashes on close
https://launchpad.net/bugs/57975
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Can you try to install the debug symbols of evolution-data-server libc6
too? (http://wiki.ubuntu.com/DebuggingProgramCrash)
--
Crashes on close
https://launchpad.net/bugs/57975
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
There is now a new backtrace, which appears to be more informative:
#0 0x082acf41 in ?? ()
#1 0x082ce710 in ?? ()
#2 0x082ce760 in ?? ()
#3 0x0867df40 in ?? ()
#4 0xb73ce61c in ?? () from /usr/lib/libcamel-1.2.so.8
#5 0xb21b7350 in ?? ()
#6 0x0001 in ?? ()
#7 0xb21b73a8 in ?? ()
#8
Unfortunately, I was wrong. For one entire gnome-session it seemed not
to crash, but once I restarted, it was back to normal.
I should have posted earlier, but I was carried away by my work.
Kind Regards,
Matthew
--
Crashes on close
https://launchpad.net/bugs/57975
--
desktop-bugs mailing
marking as fixed then, feel free to reopen if you get the issue again
** Changed in: evolution (Ubuntu)
Status: Needs Info = Fix Released
--
Crashes on close
https://launchpad.net/bugs/57975
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Hurrah!
With the latest packages released for Evolution in Ubuntu Edgy, it no
longer crashes when you close evolution. I do not anticipate a
regression of behaviour, but if it does, I shall let you know.
Thank you for your hard work **^^**.
Kind Regards,
Matthew
--
Crashes on close
Hmmm - it is only happening occasionally now. I think it shuts down
properly when firefox is running, but not otherwise.
That is not yet proven, but it seems to work generally.
Kind Regards,
Matthew
--
Crashes on close
https://launchpad.net/bugs/57975
--
desktop-bugs mailing list
Do you get the crash every time if firefox is not running?
--
Crashes on close
https://launchpad.net/bugs/57975
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
With the latest evolution (2.8.0), I cannot reproduce this.
Occasionally, seemingly sporadically, it actually quits without fault -
but I cannot find a trend.
If it is important, which I doubt, the backtrace has changed slightly in
the values of the memory sectors - but I do not think it is
After upgrading to the latest version available, the backtrace (after
installing libc6-dbg is:
---
#0 0x082789c8 in ?? ()
Cannot access memory at address 0xaeb572fc
If the amount of error messages means anything, then it is almost fixed
:P.
Kind Regards,
** Changed in: evolution (upstream)
Status: Unknown = Confirmed
--
Crashes on close
https://launchpad.net/bugs/57975
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I close Bug Buddy by clicking close, because it will not send the error
report by itself - complaining that a product or component has not been
specified.
The GDB output is pasted below, and again happens after I close evolution:
This looks a lot like
https://launchpad.net/distros/ubuntu/+source/evolution/+bug/57975 -
could you install libc6-dbg and get another backtrace?
** Bug watch added: GNOME Bug Tracker #330157
http://bugzilla.gnome.org/show_bug.cgi?id=330157
** Also affects: evolution (upstream) via
Hello again.
I do not use the Empty trash on exit feature, so I do not think this
is the same bug. I have installed the debug packages, and have pasted
below the new backtrace.
Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92
Memory status:
Thanks for your comment. How do you close bug-buddy? Could you get a backtrace
using gdb instead of bug-buddy?
- gdb evolution
(gdb) run
... close it, get the crash
(gdb) bt
--
Crashes on close
https://launchpad.net/bugs/57975
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Thanks for your bug. Could you get a backtrace with evolution-dbg and
evolution-data-server-dbg installed? Do you use the empty trash on
exit option? That could be the same issue than bug # 38455 by example
** Changed in: evolution (Ubuntu)
Importance: Untriaged = Medium
Assignee:
19 matches
Mail list logo
