<mizmo> mbarnes, :( do you think i should reinstall my system clean to get gnome stable?
<mizmo> mbarnes, i was working with my calendar, i switched from week view to list view, and it froze and force closed. now i can't restart evo unless i log back out and in, but it freezes as soon as i open in
<mizmo> when i ran it from the terminal it spewed out a bunch of errors like
<mizmo> (evolution:5883): libecal-WARNING **: Failed to dispose cal view: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.gnome.evolution.dataserver.CalendarView' on object at path /org/gnome/evolution/dataserver/CalendarView/5635/8
<mizmo> (evolution:5883): calendar-gui-DEBUG: get_view_cb: Failed to get view: No such interface `org.gnome.evolution.dataserver.Calendar' on object at path /org/gnome/evolution/dataserver/Calendar/5635/11
<mizmo> it seems to start in express mode
<mbarnes> mizmo: yikes, that kinda looks like evolution and evolution-data-server are mismatched, but that shouldn't be possible
<mizmo> and if i do evolution -c mail it works.... but it i click on the calendar, or if i do evolution -c calendar, it crashes hard again
<mbarnes> mizmo: you can force evolution back to the mailer on startup with "evolution --component=mail"
<mbarnes> mizmo: maybe also run "package-cleanup --dupes" to see if you have multiple evolution-data-server packages installed
* acunaa (~acunaa@pal01cs002.americas.hp.net) has joined #evolution
<mizmo> mbarnes, is there any way to run evo in a debug mode so if i do evolution -c calendar, it might spit out something useful rather than just locking the GUI?
<mizmo> oh i see, --debug=file
<mbarnes> meh, that doesn't do anything useful
* mbarnes makes a note to just kill that option...
<mbarnes> mizmo: try shutting down evolution and then kill the evolution-calendar-factory process
<mbarnes> that's the dbus service it's trying to talk to
<mbarnes> maybe the dbus service went haywire
<mizmo> mbarnes, so i'm doing ps ax | grep evo and i'm not seeing the calendar factory process
<mbarnes> hmm
<mizmo> (maybe that's the issue?)
<mizmo> i've logged out and back in a few times
<mizmo> maybe it needs a reboot?
* caillon (~caillon@209.132.181.86) has joined #evolution
<mbarnes> mizmo: try running "/usr/libexec/evolution-calendar-factory -r" in its own terminal window, and then start evolution
<mbarnes> we'll see if it's crashing or something
<mizmo> mbarnes, so... :( i don't have /usr/libexec/evolution-calendar-factory :(
<mbarnes> mizmo: oh, it might still be called "e-calendar-factory" in F-16... sorry
<mbarnes> that's probably why it didn't show up in "ps ax"
* acunaa has quit (Leaving.)
* acunaa (~acunaa@pal01cs002.americas.hp.net) has joined #evolution
<mizmo> mbarnes, i don't see e-calendar-factory either
<mizmo> oh there it is okay
<mizmo> mbarnes, so, if i do ps ax | grep cal, i see two copies of e-calendar-factory running, and a gnome-shell-calendar-server
<mizmo> mbarnes, what should i do? kill the e-calendar-factory processes and re-run it?
<mbarnes> mizmo: yeah, kill both e-calendar-factory processes and restart evolution
<mizmo> mbarnes, okay. so killing the e-calendars made evo start up fine, and i could finally view the calendar tab. however, if i click on 'list' view again, it locks up again
* acunaa (~acunaa@pal01cs002.americas.hp.net) has left #evolution
<mbarnes> mizmo: do you see the same terminal warnings as before, or different ones (if any)?
<mizmo> i didn't run it from the terminal this time :( (i should have)
<mizmo> let me try again
<mizmo> mbarnes, no terminal output, just freeze :( this time it let me do week / work week / month / list, when i clicked back on week, it froze again
<mbarnes> mizmo: so it sounds like as long as you avoid list view it's fairly stable?
<mizmo> mbarnes, it seems random which view crashes it
<mizmo> but at least i know which process to kill now to restart and get it working again! :)
<mbarnes> mizmo: think you could kill e-calendar-factory again and run it under gdb this time?
<mbarnes> my guess is it's crashing and so we'll need to see a back trace
<mbarnes> mizmo: run e-calendar-factory under gdb, I meant.  not evolution.
<mizmo> kk i'll give it a shot, i need some debuginfos tho
<mbarnes> oh yeah, thanks
<mizmo> mbarnes, so this time it's not freezing up, but it's spitting out those dbus thingys again, and my calendars are showing up blank
* mizmo wonders if it's a zimbra issue
<mizmo> mbarnes, http://fpaste.org/C27Z/
<mizmo> mbarnes, okay! i have it frozen now, and i'm at the gdb prompt, what should i do?
<mizmo> oh maybe i did this all wrong. i ran /usr/libexec/e-calendar-factory with gdb, now it doesn't seem to be attached though :-/
<mbarnes> oh, sorry.  I think I explained things too vaguely...
<mbarnes> okay, start over:
<mizmo> run evo from gdb too?
<mbarnes> not yet, I think the problem's in e-calendar-factory
<mizmo> kk
<mbarnes> first, kill any leftover e-calendar-factory processes
<mizmo> check, they're all gone
<mbarnes> then in a terminal window: "gdb --args /usr/libexec/e-calendar-factory -r"
<mbarnes> wait for the (gdb) prompt, then "run" to actually start the e-calendar-factory process
<mizmo> okay! cool
<mizmo> then start evo?
<mbarnes> yeah
* ced117 has quit (Quitte)
<mizmo> argh
<mizmo> complaining about more missing debug infos
<mizmo> but
<mizmo> Program received signal SIGSEGV, Segmentation fault.
<mbarnes> there we go
<mizmo> here's the whole shebang http://fpaste.org/eiwK/
<mizmo> i'll quit, grab those debuginfos, and do it again?
<mbarnes> hang on
<mbarnes> before you exit gdb, do "thread apply all backtrace"
* FL1SK has quit (Remote closed the connection)
<mizmo> mbarnes, http://fpaste.org/j49o/ <= that's all of it
<mbarnes> okay, I think know this one...
* mbarnes digs...
* dvratil (~progdan@ip4-95-82-187-209.cust.nbox.cz) has joined #evolution
<mbarnes> mizmo: rpm -q evolution-data-server ?
<mizmo> evolution-data-server-3.2.3-1.fc16.x86_64
<mizmo> (it's from updates-testing)
<mbarnes> nuts, the bug I'm thinking of supposedly got FIXED in 3.2.3...
<mizmo> funnily, i had the same issue in the stable version, i updated from updates-testing in hopes it had been hehe
<mbarnes> the problem in general here is libical (which we don't control) is not thread-safe
<mbarnes> it's the same issue that plagues GConf...
<mbarnes> but we committed a workaround to e-calendar-factory back in November that I *thought* fixed this
<mbarnes> and that should have crept into 3.2.3
<mbarnes> mizmo: how about: rpm -q libical ?
* dave_largo has quit (Client exiting)
* mbarnes afk for a bit...
* mbarnes is now known as mbarnes|afk
* hubutm20 has quit (Ulliendo)
<mizmo> mbarnes|afk, libical-0.48-1.fc16.x86_64
<m4nti5> mbarnes: hey, why there is a separation between http connections for 2003 and 2010 servers?
* mbarnes|afk is now known as mbarnes
* JanC_ has quit (Bye!)
<mbarnes> mizmo: okay, I guess upstream libical hasn't fixed this yet
<mbarnes> mizmo: mind throwing this issue up on bugzilla.gnome.org?  you can just paste the IRC log and backtrace there if you want.
<mbarnes> m4nti5: because there was no publicly available documentation from Microsoft for talking to Exchange servers until Exchange Web Services was introduced in Exchange 2007
<mbarnes> m4nti5: evolution-exchange and evolution-mapi were only possible after much reverse engineering
<mizmo> mbarnes, sure
<m4nti5> mbarnes: I see, but if we try the ews with a 2003 server, will it fail?
<mbarnes> m4nti5: yes, because Exchange Web Services was only introduced in Exchange 2007
<m4nti5> (I would try it myself but currently I only have a 2010 server for testing purposes :( )
<mizmo> mbarnes, file against evolution?
<mbarnes> mizmo: evolution-data-server
* JanC (~janc@ip-81-11-190-162.dsl.scarlet.be) has joined #evolution
<mizmo> kk
<mizmo> thanks for all of your help
<mbarnes> mizmo: sure, sorry this is still not resolved
* mbarnes is now known as mbarnes|afk
