Re: [Evolution] evolution-2.32.1 (FreeBSD HEAD) && calendar not working

[Matthias Apitz <guru unixarea de>]

El día Monday, May 02, 2011 a las 04:03:13PM +0200, Milan Crha escribió:

> On Wed, 2011-04-27 at 08:22 +0200, Matthias Apitz wrote:
> > (gdb) bt
> > #0  0x29ddaa30 in ?? ()
> > #1  0x290b754b in g_hash_table_lookup ()
> > from /usr/local/lib/libglib-2.0.so.0
> > #2  0x29f46c26 in e2k_autoconfig_lookup_option (
> >     option=0x29f79ea0 "Disable-Plaintext") at e2k-autoconfig.c:1472 
>
>       Hi,
> thinking of it, I recalled some linking fixes, namely [1] and [2]. Maybe
> you are experiencing side-effects of those issues. Could you try to
> rebuild evolution-exchange with those patches included and check whether
> it'll help, please? (Though I have nothing else to try.)
>       Bye,
>       Milan
>
> [1] http://git.gnome.org/browse/evolution-exchange/commit/?id=f076c3931d
> [2] http://git.gnome.org/browse/evolution-exchange/commit/?id=2fcd8c70ad

Thanks for the hint I will later test this and let you know...

I wanted to start from scratch to make sure to
a) not have somehow a mix of older evo installed
b) go back to the official supported version 2.32.1 in FreeBSD ports
because they do patch something in the sources and I don't know if these
patches are clean for 2.32.3;

I completely removed:

evolution-2.32.3
evolution-data-server-2.32.3
evolution-exchange-2.32.3

and compiled from the ports the 2.32.1 versions of the above packages;

I removed as well in that target VM

rm -rf ~/.cache/evolution:
rm -rf ~/.config/evolution:
rm -rf ~/.g*

and compied over from my running VM with Evo 2.24.5

scp -rp .g* VM:.
scp -rp .evolution VM:.

I started in the VM the evolution 2.32.1 and it migrated the data of the
old ~/.evolution dir to the new dirs; Evo comes up fine and crashes fine
the e-calendar-factory; so far so good I was thinking because now we
have the clean situation to start debugging (and check your hints);

but now any further start of Evo 2.32.1 crashes Evo itself when I try to
go to calendar with this error message:

(evolution:25321): GLib-GObject-CRITICAL **: g_object_ref: assertion
`object->ref_count > 0' failed
Segmentation fault (core dumped)

the bt looks like this:

#0  0x29979c78 in g_type_class_meta_marshal (closure=0x2a6acd10, 
    return_value=0x0, n_param_values=4, param_values=0x305c8788, 
    invocation_hint=0xbfbfc60c, marshal_data=0x48) at gclosure.c:197
#1  0x299799ae in g_closure_invoke (closure=0x2a6acd10,
return_value=0x0, 
    n_param_values=4, param_values=0x305c8788,
invocation_hint=0xbfbfc60c)
    at gclosure.c:197
#2  0x29990f92 in signal_emit_unlocked_R (node=0x2a6b9340, detail=0, 
    instance=0x2a432330, emission_return=0x0,
instance_and_params=0x305c8788)
    at gutils.h:360
#3  0x2999019b in g_signal_emit_valist (instance=0x2a432330,
signal_id=553, 
    detail=0, var_args=0xbfbfc808 "(È¿¿9\026¥)") at gutils.h:360
#4  0x29990489 in g_signal_emit (instance=0x2a432330, signal_id=553,
detail=0)
    at gutils.h:360
#5  0x295465de in on_signal_received (connection=0x2aa5e348, 
    sender_name=0x2fafbb88 ":1.35", 
    object_path=0x2a76ce00
"/org/gnome/evolution/dataserver/calendar/CalView/25300/2", 
    interface_name=0x307a0a90
"org.gnome.evolution.dataserver.calendar.CalView",
signal_name=0x2fafbb70 "Done", parameters=0x2aada898,
user_data=0x2a432330)
    at gdbusproxy.c:135
#6  0x29536474 in emit_signal_instance_in_idle_cb (data=0x307a0a60)
    at gdbusconnection.c:260
#7  0x29a10463 in g_idle_dispatch (source=0x30621700, 
    callback=0x2953635e <emit_signal_instance_in_idle_cb>, 
    user_data=0x307a0a60) at gmain.c:431
#8  0x29a0c9d2 in g_main_dispatch (context=0x2a2a69b0) at gmain.c:431
#9  0x29a0dcc7 in g_main_context_dispatch (context=0x2a2a69b0) at
gmain.c:431
#10 0x29a0e11c in g_main_context_iterate (context=0x2a2a69b0, block=1, 
    dispatch=1, self=0x2a022250) at gmain.c:431
#11 0x29a0e303 in g_main_context_iteration (context=0x2a2a69b0,
may_block=1)
    at gmain.c:431
#12 0x286ff089 in ep_msg_send (msg=0x30621540) at e-passwords.c:157
#13 0x2870143b in e_passwords_get_password (
    component_name=0x3079adc0 "Exchange", 
    key=0x2a3b8d80 "exchange://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/")
    at e-passwords.c:157
#14 0x2b0d49c2 in auth_func_cb (ecal=0x2aaaecb0, 
    prompt=0x2a3b8b80 "Introduzca la contraseña para Kalender (usuario
XXXX\\xxxxxx)", key=0x2a3b8d80
"exchange://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/", 
    user_data=0x0) at authentication.c:48
#15 0x284f141f in open_calendar (ecal=0x2aaaecb0, only_if_exists=0, 
    error=0xbfbfcaf8, status=0xbfbfcaf4, needs_auth=0, async=1) at
e-cal.c:68
#16 0x284f1a1f in e_cal_open_async (ecal=0x2aaaecb0, only_if_exists=0)
    at e-cal.c:68

it seems it crashes when Evo wants to pop-up a message asking for the
password ("Introduzca la contraseña para Kalender" in Spanish, "Put in
the password for Kalender");

What does this mean?

        matthias

-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <guru unixarea de> - w http://www.unixarea.de/