Package: sup-mail
Version: 0.8.1-1
Severity: normal

Pressing 'L' for sup-mail should do a quick label search. However, as
soon as 'L' is presses, sup-mail crashes and the following error is
displayed:

ruby: symbol lookup error: /usr/lib/ruby/1.8/i486-linux/ncurses_bin.so:
undefined symbol: funcall

The terminal is then "messed up". Whereby typing any command causes
characters to be printed all over the place
(http://pastebin.com/f6be3e21)

Also, sup-mail leaves a .lock file behind. This means that when
relaunching sup-mail again it detects the lock file and asks the user if
the process should be killed. Selecting 'yes' does not do anything as
the process has already been terminated. Removing the .lock file
manually fixes the issue.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sup-mail depends on:
ii  libchronic-ruby               0.2.3-1    natural language date parser
ii  libferret-ruby1.8             0.11.6-2   full text search engine library fo
ii  libgettext-ruby1.8            1.93.0-1   Gettext for ruby1.8
ii  libhighline-ruby              1.5.1-1    High-level interactive IO Ruby lib
ii  liblockfile-ruby              1.4.3-2    create NFS-safe lockfiles
ii  libmime-types-ruby            1.15-2     guess MIME type of files
ii  libncurses-ruby               1.2.2-1    ruby Extension for the ncurses C l
ii  libnet-ssh-ruby1.8            1.1.2-1    pure ruby module that emulates an 
ii  librmail-ruby1.8              0.17-1     lightweight mail library for Ruby 
ii  libtrollop-ruby               1.9-1      command-line argument processing l
ii  ruby                          4.2        An interpreter of object-oriented 

sup-mail recommends no packages.

sup-mail suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to