I have created the bugreport in the lesstif Bugzilla:
http://sourceforge.net/tracker/index.php?func=detail&aid=1529729&group_id=8596&atid=108596
So this bug probably could be reassigned to lesstif package.
Best regards,
Andrey
--
Andrey V. Kiselev
ICQ# 26871517
--
To UNSUBSCRIBE, email to
On Mon, Jul 24, 2006 at 12:25:04PM -0400, James Vega wrote:
> > > This was reported a week or so ago on the vim-dev mailing list,
> > > too. It seems that using lesstiff-dev/lesstiff1 also works well.
> >
> > I have tried the lesstiff-dev/lesstiff1 without success. Can't build vim
> > with it...
On Wed, Jul 19, 2006 at 01:53:54PM +0200, Stefano Zacchiroli wrote:
> > In addition I have built vim package using libmotif from unstable
> > (2.2.3-1.4) and it works just fine. So it is most likely a problem with
> > lesstif, but it renders vim-lesstif completely unusable.
>
> Could you please co
On Wed, Jul 19, 2006 at 09:32:00AM -0400, James Vega wrote:
> > In addition I have built vim package using libmotif from unstable
> > (2.2.3-1.4) and it works just fine. So it is most likely a problem with
> > lesstif, but it renders vim-lesstif completely unusable.
>
> This was reported a week or
On Tue, Jul 18, 2006 at 06:44:29PM +0400, Andrey Kiselev wrote:
> Lesstif variant of gvim does not work on my system and crashes during
> startup. There is backtrace log from the gdb:
In addition I have built vim package using libmotif from unstable
(2.2.3-1.4) and it works just fine. So
Package: vim-lesstif
Version: 1:7.0-035+1
Severity: grave
Justification: renders package unusable
Lesstif variant of gvim does not work on my system and crashes during
startup. There is backtrace log from the gdb:
Program received signal SIGSEGV, Segmentation fault.
0x545c in ?? ()
(gdb) bt
6 matches
Mail list logo
