This application crashes in a large number of ways and should not be marked stable. The more serious errors include System.NullReferenceException, reference counts <0, critically bad use of file descriptors and thousands of failed runtime assertions. The application hangs and crashes repeatedly.
Why don
Why don´t you complain upstream? That´s the best you get from Novell right now. :-p @gnome herd: The homepage is 404. This one seems to work: http://www.novell.com/products/desktop/features/evolution.html
this bug got absolutely zero useful info. Don't file crap like this.
here we go: opening evolution: ------------------------------------------- (evolution-2.2:8627): camel-WARNING **: Invalid root: '/home/heimat/.evolution/mail/local/Drafts.ibex.index' (evolution-2.2:8627): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution-2.2:8627): camel-WARNING **: block size: 1024 (1024) OK (evolution-2.2:8627): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution-2.2:8627): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution-2.2:8627): camel-WARNING **: flags: unSYNC update flow align BBDB spinning up... ------------------------------------------ reading mail: ------------------------------------------ ** (evolution-2.2:8627): CRITICAL **: bbdb_do_it: assertion `book != NULL' failed (evolution-2.2:8627): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ------------------------------------------ writing reply: (after I pressed Send button evolution simply hung up) ------------------------------------------ Unhandled Exception: System.NullReferenceException: A null value was found where an object instance was required. All of those - just 30 secs... Ok, I think that evolution-2.2.1.1 is buggy so it's really important to mask ebuild until novell provides really stable version PS. CTRL-C in the console and we've got next flowers: ** (evolution-2.2:8628): WARNING **: Serious fd usage error 15 ** (evolution-2.2:8628): WARNING **: Serious fd usage error 13
2.2.1.1 works great here, and has for a long time. No stability issues at all. Just as a reference.
And if I don't file it, you're going to leave this package marked stable. What exactly would be useful info? I'm not trying to get bugs fixed here - that's for people with more time. I'm simply trying to get this package marked unstable, which it clearly is. On that basis, what would you consider useful information? A survey of systems on which it crashes miserably?
I must admit, evolution-2.2.1.1 is very unstable here as well, and several features do not work (although they did work in 2.0.4). I know this comment doesn't add much, but I do see the point of the original reporter.
this is just a useless bugreport, i have no intention of investigating it. I didn't close this because I don't think evo doesn't have any problems, i closed it because the bug is meaningless in this state. File a new report and now go trough all the steps to get us some useful info other than 'hey this doesn't work, it sucks'. btw even from the crappy info you gave, i suspect that you have non-gentoo stuff on your system and that would invalidate this bugreport anyway.
Steps to reproduce: Launch evo. Wait. It immediately issues a lot of warnings, several NPEs and some refcount<0s, especially when calendaring. Wait long enough and it freezes or crashes. Exit cleanly, and get serious FD usage errors. There's enough evidence here to get the package marked unstable. Systems include Athlon, Opteron and Pentium-M UP and SMP systems. All pure and recent Gentoo. Gnome versions include 2.4, 2.6 and 2.8. No special use flags. No special CFLAGS. No shit. No magic. I don't know what gives you rise to believe that I have non-Gentoo stuff on the system. Perhaps it's a form of extra-sensory perception or prescience. Either way, it's faulty. I suspect you've simply taken objection to this particular report. This latter is your problem not mine. The bug has been reported. Merry christmas.
I told you what to do, you still don't give the info I want. I don't want it in this bug anyway.
I launch evo. I wait. No instability. No hangs. No crashes. On all workstations here at work, with gnome 2.8 and gnome 2.10. (note that Evo is now part of gnome 2.10 and won't necessarily work with 2.8, under all circumstances). Works fine with pop, imap, and exchange. Calendering works fine, as does calendering via exchange. Works fine on assorted x86 and amd64. Without much more specific information, there's nothing we can do. I suggest that if you care about getting it fixed, do as foser suggests and submit a real bug. If you don't care about getting it fixed, mask it locally.
