http://bugs.gentoo.org/show_bug.cgi?id=29047 is marked as closed, yet I see the exact behaviour described every time evolution is started. Steps to Reproduce: ACCEPT_KEYWORDS="~x86", emerge gnome emerge evolution Giving gnome2.4 and evolution1.4.4 before starting evolution: ps aux | grep evo pcassidy 4149 0.0 0.2 3668 560 pts/0 R 20:18 0:00 grep evo so no processes related to evolution running. pcassidy@orion pcassidy $ evolution & [1] 4153 immediately quit evolution from the file menu, application does not close but window stops updating. check for running evolution gives... pcassidy@orion pcassidy $ ps aux | grep evo pcassidy 4153 2.0 8.4 59220 18968 pts/0 S 20:19 0:00 evolution pcassidy 4155 0.4 3.0 24220 6872 ? S 20:19 0:00 /usr/libexec/evolution/1.4/evolution-wombat --oaf-activate-iid=OAFIID:GNOME_Evolution_Wombat_InterfaceCheck --oaf-ior-fd=35 pcassidy 4157 0.2 2.9 23344 6664 ? S 20:19 0:00 /usr/libexec/evolution/1.4/evolution-alarm-notify --oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_AlarmNotify_Factory --oaf-ior-fd=39 pcassidy 4162 0.0 8.4 59220 18968 pts/0 S 20:19 0:00 evolution pcassidy 4163 0.0 8.4 59220 18968 pts/0 S 20:19 0:00 evolution pcassidy 4164 0.0 8.4 59220 18968 pts/0 S 20:19 0:00 evolution pcassidy 4165 0.0 8.4 59220 18968 pts/0 S 20:19 0:00 evolution pcassidy 4176 0.0 0.2 3668 560 pts/0 R 20:19 0:00 grep evo
After some searching, I came up with a more accurate description of the problem and a possible patch... http://www.mail-archive.com/evolution-hackers@lists.ximian.com/msg01018.html also from the forums http://forums.gentoo.org/viewtopic.php?p=544088#544088
thanks for the link. seems very relevant but the fix should be in 1.4.5 .. it should be in portage after i've done a little testing
the patch mentioned in the posting on evolution hackers doesn't help for me. evolution-wombat still keeps crashing out of the blue and I don't know how to diagnose this problem with gdb
test 1.4.5 in portage now please
1.4.5 still has this issue.
what version(s) of bonobo-activation, libbonobo and ORBit2 are you guys using ?
* gnome-base/bonobo-activation Latest version available: 2.2.4 Latest version installed: [ Not Installed ] Size of downloaded files: 534 kB Homepage: http://www.gnome.org/ Description: Gnome2 replacement for OAF * gnome-base/libbonobo Latest version available: 2.4.0 Latest version installed: 2.4.0 Size of downloaded files: 1,313 kB Homepage: http://www.gnome.org/ Description: GNOME CORBA framework * gnome-base/ORBit2 Latest version available: 2.8.1 Latest version installed: 2.8.1 Size of downloaded files: 602 kB Homepage: http://www.gnome.org/ Description: ORBit2 is a high-performance CORBA ORB
hmm but this is an artificial case where you start evo and immediatly quit it ? In that case it's probably an evo bug where you interrupt init processes or something. In a normal situation this doesn't happen ?
for me here evolution-wombat keeps on freezing all the time. just out of the sudden. then I kill the process and can work on with evolution. but after another 5 to 10 minutes it freezes again.
this is what gdb tells me every time that wombat crashes: backend_last_client_gone_cb() called! I posted this already on evolution-hackers and we will see what it is.
Starting evolution and immediately quiting it may be artificial, but this problem also occurs during normal use. I didn't see this until I upgraded to gnome-2.4, so I think it must be to do with the gnome-2.4 libs used by evolution.
evolution freezes up sometimes using LDAP. Killing evolution-wombat unfreezes it but LDAP can't be used again until evolution is restarted. If you use any LDAP address books for auto-completion, you can usually just type a couple of characters in the To: list and it freezes up. Otherwise just the addressbook directly, it seems to usually freeze on the second or third query. gnome-base/libbonobo-2.4.0 * gnome-base/libbonoboui-2.4.0 * gnome-base/bonobo-1.0.22 * gnome-extra/bonobo-conf-0.16 * gnome-base/ORBit2-2.8.1 * net-mail/evolution-1.4.5 * and a 2.6 kernel + gcc-3.3.1. I'm going to recompile all these components with 3.3.1-r4 for safe measure; a few may be compiled with (more?) buggy versions.
here ya go. when i start evolution and i click on the ~4 side buttons to access email/calendar/tasks/summary views and then exit Evolution after doing this, my compilation also presents the similar "endless hang on exit" also. After doing this, a "--force-shutdown" is required to exit evolution. I too performed teh complete emerge sync && emerge -UD world to upgrade to gnome-2.4 also last night. (before upgrading evolution on any of my production boxes, i usually upgrade evolution or any of it's libs on a test box and perform teh above test. most bugs w/ evolution will usually present themselves immediately after doing so. If the compilation of evolution succeeds my 4-5 button test, i usually have zero problems with Evolution operating properly.)
Just a comment to say that the problem is still there even after having re-emerged evolution
yup. ditto here. i noticed the newer ebuild file and performed the rebuild as requested. doing my little test still distributes the endless hang of evolution on exit and requires the --force-shutdown option. :-( as of right now, i'm not upgrading any of my stable/production boxes becuase of this bug.
well, i think we're looking at some difficult to pinpoint evo/gnome interaction problem here. The LDAP problem described i think is something else and is not something i can test. Can our evo specialist maybe have another look ? ;) I can reproduce the other behaviour mentioned, but i have no problem using it (although i only use limited parts of evo).
hrmm .. i'm totally stumped here. there seems to be two problems here: 1. freeze on exit. is anyone able to run it thru gdb or strace and find out what it is doing in the freeze? i suspect it is something to do with bonobo, but i can't be sure. 2. freeze after 5-10mins. this is the one that andreas was reporting and brought up with evolution-hackers http://lists.ximian.com/archives/public/evolution-hackers/2003-September/001340.html https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=105715 http://lists.ximian.com/archives/public/evolution-hackers/2003-October/001390.html 3. some problems with pressing calendar buttons and then quitting. possibly the same as (1), but the symptoms seem a little different. so a question to you all, when it hangs, do you get the "evolution is closing down.." dialog box or does the whole evolution window just freezes? and can someone post their 'emerge info' and any gdb traces that might help? foser, you can produce the freezes? hrmm .. maybe i'm not using evolution enough or maybe you're just emailing too much :)
Hi, Yesterday I installed Evolution and expierienced the same problems as you guys: Crashes (mainly in the Settings-dialogs) and also freezes when closing evolution. The only thing to start evo again is to kill those processes or call "evolution --force-shutdown". BUT, it seems that the problems have gone. This is what I did: Updated system and gnome (both with --deep, wanted to make sure I dont have a buggy program or lib installed) and remerged evolution with "devensive" C(XX)FLAGS "-march=i586 -O2 -pipe" (see my original setting below). After finishing the build, the problems seem gone. Sorry I cant give you the exact reason, maybe someone of you can try to rebuild evolution with my settings. Should be easy to filter out other CFLAGS in the ebuild. I'll give you an update if something changes. Portage 2.0.49-r10 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r1, 2.4.22_pre2-gss) ================================================================= System uname: 2.4.22_pre2-gss i686 Mobile Intel(R) Celeron(TM) CPU 1333M Hz Gentoo Base System version 1.4.3.10p1 distcc 2.9 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.2 [enabled] ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -Os -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share /config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=pentium3 -Os -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs sandbox ccache" GENTOO_MIRRORS="http://gentoo.inode.at/ http://mirrors.sec.informatik.tu-darmsta dt.de/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 apm avi crypt encode foomaticdb gif jpeg libg++ mad mikmod mmx mpeg ncu rses pdflib png quicktime spell xml2 xmms xv zlib gdbm berkdb slang readline svg a java guile X sdl gpm tcpd pam libwww ssl perl python esd imlib gtk qt kde moti f opengl mozilla cdr truetype -tetex tiff gtk2 aalib nls dvd -cups gphoto2 oggvo rbis gnome arts alsa oss imap maildir -mbox ldap pda video_cards_i830"
ok. now i also remember evolution didn't like pentium3 optimizations... as well as some other at times. it may appear that these have resurfaced. i'll try commenting out my cflags section in the make.conf and see what happens.
just for reference: CFLAGS="-march=pentium3 -mcpu=pentium3 -O3 -pipe " when i get done building openoffice, i'll give evolution a shot and see if "-fomit-frame-pointer" was the culprit, and all else fails, i'll try no cflags.
Ok, here's the update. Evo crashed 2 times since yesterday, thats not great but at least it's now useable. Both crashes happend when switching between emails on an imap-server. No more freezes and I can start evo after the crash (it crashes with the Gnome-bugreport-dialog) normally, no need to kill the other processes. Testing without cflags sounds like a good idea.
The ebuild does filter the -O3 flag, but I never discovered which particular flag in -O3 was the culprit, or whether it was a local problem. I'll probably have to filter -Os as well. BTW, -O3 was filtered because I couldn't get evolution to start up with those flags, but it may have been a local problem. Through gdb I saw some really peculiar behaviour, like variables being passed through 3 functions but changing values between function calls and then changing back to their original value, even though nothing was modifying it in the code. But I suspect it was a problem with one of the older gcc-3.3.1. Portage 2.0.49-r12 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r1, 2.6.0-test5-mm3) ================================================================= System uname: 2.6.0-test5-mm3 i686 Celeron (Mendocino) Gentoo Base System version 1.4.3.10p1 distcc 2.11 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.2 [disabled] ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium2 -O3 -pipe -g" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" all that said, i currently don't experience any of the symptoms you guys have mentioned. if you could all tell me what gcc ver/flags and other info (thats why i need emerge info), maybe we can find something in common. btw, i use imap exclusively on evolution.
this bug might get fixed pretty soon. read: http://lists.ximian.com/archives/public/evolution-hackers/2003-October/001492.html "I've released ORBit2-2.8.2 with that fix, should be in Gnome 2.4.1shortly." so I'm waiting for this version of ORBit2. will I have to recompile evolution against it or will the bug be fixed with the new install of ORBit2?
do NOT update to ORBit2-2.8.2!! I can't send out emails anymore. but at least evolution doesn't freeze at all anymore.
just got an email: --- From: Jeffrey Stedfast <fejj@ximian.com> Subject: Re: Re:[Evolution-hackers] evo / ORBit2 oddness... you are suffering from a glibc 2.3.2 bug in gethostbyaddr_r() - you'll need to remove all blank lines and comment blocks from /etc/hosts Jeff --- so after all ORBit2-2.8.2 is good to use. no freezes, evolution just working wonderful. after I've removed all comments in /etc/hosts I can send out emails again. I this glibc bug already known?
I have just submitted a bug report for the glibc problem http://bugs.gentoo.org/show_bug.cgi?id=30865
I am also experiencing the LDAP lockup. I use evolution as my mailer and get an address book fro Exchange/Active Directory via LDAP at work. Unfortunately, since the upgrade to Gnome 2.4, using the address book locks up evolution hard. This is: evolution 1.4.4 libbonobo-2.4.0 ORBit2-2.8.1 I do not have bonobo-activation installed at all. I have been able to duplicate this on two separate machines.
just to affirm, i've recompiled with blank CFLAGS (default) and edited /etc/hosts accordingly & the hang on exit to still exists (although i thought it was irrelevant ;-).
try with ORBit2-2.8.2 in ~portage already, you might need to do a full session/*dm restart for it to have effect. chris : you don't need bonobo-activation with libbonobo-2.4
With ORBit2-2.8.2 it works just fine!!!
ok. i only upgraded to ORBit2.8.2 and I also see that the 'hang on exit' bug disappeared. there is no need to recompile evolution for this bug to disappear, as I had ORBit2.8.1 previously compiled/installed with the gnome-2.4 upgrade.
ORBit2-2.8.2 does appear to fix the problem (I no longer seem to have the LDAP problems), but you have to make sure you kill off any old evolution or ORBit-related processes. In particular you should kill bonobo-activation-server, and anything that starts with "evolution-".
evo-1.4.5 is now stable along with ORBit2-2.8.2. thanks for everyone's input
