Open GoogleCodeExporter opened 9 years ago
Same issue to the letter.
Original comment by ho0...@gmail.com
on 18 Jan 2009 at 1:03
ho0ber, this issue appears to be completely related to Arch and not a bug in
naim.
Refer to http://bbs.archlinux.org/viewtopic.php?id=55775
It is a really ugly fix we are using, but it works until someone gets un-lazy
enough
to figure out why the wrong libraries are being linked against in Arch.
Original comment by wub...@gmail.com
on 21 Jan 2009 at 9:31
If you run ldd /usr/bin/naim, there should be a line about "libncurses". Are you
linked against libncurses.so or libncursesw.so?
Original comment by nml...@google.com
on 21 Jan 2009 at 9:36
libncursesw.so, it appears.
wubaga: I had that suspicion, but I figured I'd at least second your findings.
Original comment by ho0...@gmail.com
on 21 Jan 2009 at 9:40
Commenting out the assertion will make it start, but over time you may notice
corruption creeping into your chat windows as ncurses and naim get confused
about
what's actually on the screen.
I think we're going look into making naim print a more-helpful error if it
detects
it's linked against libncursesw instead of libncurses, just to make it clear
what's
going on (rather than relying on failing the assertion).
Original comment by nml...@google.com
on 21 Jan 2009 at 9:54
Great. Thanks for the help! Hopefully someone will find the issue in Arch (I'm
not
quite at the point where I would know where to start) as well.
Original comment by ho0...@gmail.com
on 21 Jan 2009 at 9:58
Original issue reported on code.google.com by
wub...@gmail.com
on 17 Sep 2008 at 9:26