[Pkg-lyx-devel] Bug#473077: Bug#473077: lyx: lyx can't start
Per Olofsson
pelle at dsv.su.se
Fri Mar 28 13:24:11 UTC 2008
Hi Arnaud,
Arnaud Baysse wrote:
>
> Here his the end of the log you asked.
>
> stat64("/mnt/windows/Documents and Settings/ideas/Mes
> documents/Projet/Congrès edsys 2008/edsys2008.lyx", 0xbf9dc24c) = -1
> EILSEQ (Invalid or incomplete multibyte or wide character)
> futex(0xb7428ce8, 0x81 /* FUTEX_??? */, 2147483647) = 0
> write(2, "terminate called after throwing "..., 48terminate called after
> throwing an instance of ') = 48
> write(2, "boost::filesystem::basic_filesys"...,
> 118boost::filesystem::basic_filesystem_error<boost::filesystem::basic_path<std::string,
> boost::filesystem::path_traits> >) = 118
> write(2, "\'\n", 2'
> ) = 2
> write(2, " what(): ", 11 what(): ) = 11
> write(2, "boost::filesystem::exists", 25boost::filesystem::exists) = 25
> write(2, "\n", 1
> ) = 1
> rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
> tgkill(3264, 3264, SIGABRT) = 0
> --- SIGABRT (Aborted) @ 0 (0) ---
> +++ killed by SIGABRT +++
> Process 3264 detached
>
> The file "edsys2008.lyx" is on a NTFS Windows partition. I mount it with
> ntfs-3g. I don't know if it can help...
I think the problem lies within ntfs-3g. I can't see any generic instances of
stat64 returning EILSEQ inside the kernel. However, lyx shouldn't crash because
of this in any case - there is either a bug in boost or in lyx.
Regarding ntfs-3g, I suspect that it has the wrong idea about your character set
or something like that. Have you tried opening the file with a text editor or a
pager?
--
Pelle
More information about the Pkg-lyx-devel
mailing list