Public bug reported:
Binary package hint: evolution
Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0
Memory status: size: 376389632 vsize: 376389632 resident: 32436224 share:
10338304 rss: 32436224 rss_rlim: -1
CPU usage: start_time:
Public bug reported:
Binary package hint: evolution
http://bugzilla.gnome.org/show_bug.cgi?id=363526
** Affects: evolution (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
http://bugzilla.gnome.org/show_bug.cgi?id=363526
https://launchpad.net/bugs/67043
--
ubuntu-bugs
I'm still having this issue. I'm using edgy, evolution 2.8.1-0ubuntu1
The crash happens when accessing to my Courier IMAP server. I think
gnome-keyring is not the problem.
Running evolution with --disable-eplugin flag still crashes
Here I post you a evolution --debug log
The problem could be in search function:
Running gdb evolution :
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47595276938528 (LWP 8535)]
emfb_search_config_search (efb=0x5a1520, rule=0x91, id=-1, query=0xcd2fe0
Advanced Search, data=0x73f260) at
I simply start evolution, but the initial folder selected is a search
folder, which I'm afraid its triggering the crash.
--
evolution crashes since last edgy update
https://launchpad.net/bugs/64771
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Deleting cmeta from the folder has resolved the crash.
--
evolution crashes since last edgy update
https://launchpad.net/bugs/64771
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
http://bugzilla.gnome.org/show_bug.cgi?id=359822
** Affects: evolution (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
evolution crashes since last edgy update
https://launchpad.net/bugs/64771
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Now when I type st, the letter s dissapears from the rendering, so it
appears a misstype. I have seen this behaviour in meld and evolution
mail writing component. As this can potentially induct rhe user to break
data, I would suggest to elevate the importance of this issue.
--
Serif and
