On Fri, 2012-11-23 at 18:03 +0100, Daniel CLEMENT wrote:
> Well it's still the bulky version of the output, because with the
> redirection (which, BTW, I thought you had omitted for a reason) I get:
>
> daniel@m6400 ~ $ strace -e
> trace=file /usr/lib/syncevolution/syncevo-dbus-server 2>&1 | grep
> 'syncevolution\.mo' -e INFO -e ERROR > strace_output.txt
> grep: syncevolution\.mo: Aucun fichier ou dossier de ce type
Should have been "grep -e 'syncevolution\.mo' -e INFO -e ERROR"
^^
Anyway, there's really no access to syncevolution.mo anywhere. Strange.
I see the access to that happening shortly after opening libnotify. This
is with syncevolution 1.3.1 from syncevolution.org:
[DEBUG syncevo-dbus-server 00:00:01] using libnotify.so.4
open("/usr/share/locale/de_DE/LC_MESSAGES/syncevolution.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/share/locale/de/LC_MESSAGES/syncevolution.mo", O_RDONLY) = 10
open("/usr/share/locale/de_DE/LC_MESSAGES/glib20.mo", O_RDONLY) = -1 ENOENT (No
such file or directory)
open("/usr/share/locale/de/LC_MESSAGES/glib20.mo", O_RDONLY) = 10
Which binaries do you use? Does it happen with 1.3.1 from syncevolution.org?
What is the result of:
env | grep -e LC -e LANG
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
