Paolo wrote: > > Try it in sid/lenny please before reporting a bug.. > > that'd mean I'd shut up till I eventually upgrade a machine to Lenny, which
Or quickly set up a chroot with lenny or sid. > Testing and gathering infos for a bug report takes some effort, if you're > not going to consider bug.rep. against BPO, pls state so clearly - possibly I am not saying that, I just say you should try on the real codelines (sid/testing), too. And that you should report bugs against them then. > > > this is part of Bug#471348 saga, only that I'm filing against the - > > > hoeply - > > > proper sub-pkg. > > > > In which you didn't submit any info with which the author can debug it. > > And in this bug you didn't either. > > wrong, check your mailbox: > > !> Date: Sat, 22 Mar 2008 07:01:01 +0100 > !> To: Rene Engelhard <[EMAIL PROTECTED]> > !> Subject: Re: Bug#471348: openoffice.org: Segmentation fault trying to open > a .sdc > !> Message-ID: <[EMAIL PROTECTED]>' > > in which I attached one of those problematic files. > Assuming such msg didn't vanished midway, of course. Hrm, yes, sorry, It seems I oversaw it. That said, it works in 2.4.1-2 for me (see my other mail) > answering to your other msg: SEGV was the best/worst case: best since OOo2 > died before taking the system down, worst since - well - it segv. > That was for OOo2.3.1, OOo2.4.0 worked on those files, though (Debian's) OOo2 > takes much more CPU to do the job than OOo1.1.5 *and* official OOo's > OOo2.4.0 (which works just fine, so far). > I feel I'm seeing effects of the some bug, in SO import filters. Hmm. > > No one even remotely cares about OOo 1.1.5 anymore. > > guess so; though I'm not reporting a bug against OOo1x, the fact that OOo1 > get it right may give some hint. It doesn't, no one even can follow anymore what changed since it. > > Where have you been the last years? > > doing something else than keeping on upgrade & break working systems. I did not say you should upgrade your main system. Regards, Rene -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]