FYI, this is also traced in Debian's bugtracker : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524362

It's just a warning.
What exact Evolution version is this about?

Evo 2.26.1.1

(In reply to comment #2)
> It's just a warning.

Yes, that's what it says ;-)

Maybe stating which file it is about would help figure out what's warned indeed :-/

could you try to run evolution-data-server under gdb, place breakpoint to g_logv and paste here the backtrace of this warning, please? Because my evolution-data-server doesn't claim this on its startup. Thanks in advance.

Amazing.... I've added a bunch of logs to this ticket... and all is gone ?

Was bugzilla restored from an ancient backup ?

No. Nothing was ever added here, otherwise I would have gotten an email about it.

(In reply to comment #6)
> Amazing.... I've added a bunch of logs to this ticket... and all is gone ?
> 
> Was bugzilla restored from an ancient backup ?
> 

Maybe the log is too large, try "t a a bt", not the "full" backtrace. (Though I do not know what exactly you tried to attach.)

Closing this bug report as no further information has been provided. Please
feel free to reopen this bug if you can provide the information asked for.
Thanks!

(In reply to comment #9)
> Closing this bug report as no further information has been provided. Please
> feel free to reopen this bug if you can provide the information asked for.
> Thanks!

Closing it won't solve the problem.

I haven't had the time to work on trying to produce another trace... but the problem isn't solved... so please, don't close it.

And no progress from reporter also does not solve the problem... ;-)
NEEDINFO.

(In reply to comment #5)
> could you try to run evolution-data-server under gdb, place breakpoint to
> g_logv and paste here the backtrace of this warning, please? Because my
> evolution-data-server doesn't claim this on its startup. Thanks in advance.

I tried again, but there's nothing happening in e-d-s when the message is printed (other logs printed before at e-d-s startup, so the breakpoint is indeed active).

The message is thus in the code of the evolution executable and not in e-d-s.

Any suggestion for another bt to be set in evolution ?

OK, found it : this time, I tried the same on gdb evolution, and got :

Breakpoint 1, IA__g_logv (log_domain=0xb7c7cb75 "e-data-server-ui", log_level=G_LOG_LEVEL_WARNING, format=0xb7c7ed9c "%s", args1=0xbffff36c "(\36\16\b\354Oŷ\344\67\6\b")
    at /build/buildd-glib2.0_2.20.4-1-i386-6KfM1O/glib2.0-2.20.4/glib/gmessages.c:396
396	/build/buildd-glib2.0_2.20.4-1-i386-6KfM1O/glib2.0-2.20.4/glib/gmessages.c: Aucun fichier ou dossier de ce type.
	in /build/buildd-glib2.0_2.20.4-1-i386-6KfM1O/glib2.0-2.20.4/glib/gmessages.c
(gdb) bt

+ Trace 217166

Best regards,

Trying to signal that I provided the needed info

damn... I have no possibility to do more than unconfirmed or resolved, now... anyway, the details or a fix are here, I suppose.

It is already signalled by your comment to people on CC list, actually.

The warning is coming from Evolution trying to read your ~/.gnome2_private/Evolution password file, but apparently it's empty.  Double check that and delete the file if necessary.

I'm curious why Evolution is even reading that file to begin with.  Is Debian still not using the gnome-keyring integration?  Maybe it's time to enable that by default.

I indeed have a ~/.gnome2_private/Evolution size 0.
$ ls -l /home/olivier/.gnome2_private/Evolution 
-rw-r--r-- 1 olivier olivier 0 jan 23  2006 /home/olivier/.gnome2_private/Evolution

I'll try and remove it and will see what happens, and maybe it's a sequel of an old version ?

I can confirm that removing that file avoided having the message in stdout.

It would be probably interesting to fix the message so that the filename is displayed, then.

Agreed and done:
http://git.gnome.org/cgit/evolution-data-server/commit/?id=1f82183f21038adcc14cf33366de368c4c16fed4

Closing this as fixed.

Many thanks