Michael Ekstrand <[EMAIL PROTECTED]> writes:

tags 364386 confirmed
thanks

Hello Michael,

I hope it is ok for you if I quote you on the public bugreport logs,
since you have not CCed the Bug Tracking System. (but I stripped your
URLs)

> This morning, I re-upgraded to the TeXmacs in testing to try what you
> wanted; it re-read the config directory as a version upgrade, started,
> and opened my file beautifully.  So, TeXmacs from Testing works just
> fine now.
>
> The first TeXmacs used on this computer was the one from testing, and
> never worked until now.  My ~/.TeXmacs directory is part of my home
> directory copied from my old FreeBSD workstation when I built my
> current computer; it was created by whatever version of TeXmacs FreeBSD
> had in ports in Jan. or Feb.  It was either 1.0.5 or 1.0.6.

I now tried starting TeXmacs with your configuration from FreeBSD and
can indeed reproduce the segfault. 

> A gzipped core file and a tarball of my ~/.TeXmacs directory have
> been uploaded.  tm-config.tgz is the TeXmacs config as copied from
> FreeBSD, and tm-current.tgz is the TeXmacs config as it sits on my
> Debian machine with TeXmacs in stable working.

The core file that you uploaded lacks reading permissions for me. But
it's ok, I do not need it anymore since I can reproduce the segfault
now. tm-config.tgz makes TeXmacs from Unstable also crash, while
texmacs-current.tgz works just fine.

Thanks for your information, I'll start debugging now. ;-)

Have a nice Sunday,
     René

-- 
  _,_   
 / , \  René van Bevern <[EMAIL PROTECTED]>       
 | \_/  Debian GNU/Linux Developer             
  \     http://progn.org  http://www.debian.org

Attachment: pgpnKxAN0MDDn.pgp
Description: PGP signature

Reply via email to