[SOLVED] Dasher

Kyrinn · 10-03-2016, 08:07 PM

Hello, folks. So I'm taking a course on pen testing/security/etc. and need to use Kali. I've never used linux before, so to say I'm overwhemed would not be an understatement. The course does a good job of walking me through everything I need to know pertaining to the course itself, but unfortunately I need something extra to begin in earnest.

I'm extremely physically disabled, so to type with any kind of speed I need an onscreen keyboard with word prediction. The program that does this best in my opinion is Dasher... no question. The fact that it adapts to non-dictionary words would make it perfect for terminal use.

I don't know what the best way to ask for installation help is, but when I attempt to run ./autogen.sh I get this wall of indecipherable(to me) text.

Code:

root@kali:~/Desktop/dasher-DASHER_5_0_0_beta# ./autogen.sh
/usr/bin/gnome-autogen.sh
***Warning*** USE_COMMON_DOC_BUILD is deprecated, you may remove it from autogen.sh
***Warning*** USE_GNOME2_MACROS is deprecated, you may remove it from autogen.sh
***Warning*** PKG_NAME is deprecated, you may remove it from autogen.sh
aclocal.m4:16: warning: this file was generated for autoconf 2.63.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
fatal: No names found, cannot describe anything.
configure.ac:22: error: AC_INIT should be called with package and version arguments
aclocal.m4:409: AM_INIT_AUTOMAKE is expanded from...
configure.ac:22: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
checking for automake >= 1.8...
  testing automake... found 1.15
checking for autoreconf >= 2.53...
  testing autoreconf... found 2.69
aclocal.m4:16: warning: this file was generated for autoconf 2.63.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
fatal: No names found, cannot describe anything.
configure.ac:22: error: AC_INIT should be called with package and version arguments
aclocal.m4:409: AM_INIT_AUTOMAKE is expanded from...
configure.ac:22: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
checking for glib-gettext >= 2.2.0...
  testing glib-gettextize... found 2.50.0
checking for intltool >= 0.25...
  testing intltoolize... found 0.51.0
checking for pkg-config >= 0.14.0...
  testing pkg-config... found 0.28
Checking for required M4 macros...
**Warning**: I am going to run `configure' with no arguments.
If you wish to pass any to it, please specify them on the
`./autogen.sh' command line.

Processing ./configure.ac
aclocal.m4:16: warning: this file was generated for autoconf 2.63.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
fatal: No names found, cannot describe anything.
configure.ac:22: error: AC_INIT should be called with package and version arguments
aclocal.m4:409: AM_INIT_AUTOMAKE is expanded from...
configure.ac:22: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
Running glib-gettextize... Ignore non-fatal messages.
Copying file po/Makefile.in.in

Please add the files
  codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
  progtest.m4
from the /usr/share/aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.

Running intltoolize...
Running autoreconf...
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force --warnings=no-portability -I m4
fatal: No names found, cannot describe anything.
configure.ac:22: error: AC_INIT should be called with package and version arguments
/usr/share/aclocal-1.15/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
configure.ac:22: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: error: echo failed with exit status: 1
autoreconf: aclocal failed with exit status: 1

If there's a better way to describe what's going on, I will be happy to oblige. Is the terminal the best way to install things, or am I just making things more difficult than they need to be? I'm a little embarrassed I needed to ask for help, as I generally pride myself on my ability to figure computer related puzzles on my own.

Ztcoracat · 10-03-2016, 08:21 PM

Hi & Welcome to Linux Questions.

You can download the .iso image of Kali Linux from here.
https://www.kali.org/downloads/

Once it's downloaded check the integrity of the file. It should match the long number (SHA) on that page that I linked for you.

Next use unetbootin to place Kali on a usb pen drive and make it bootable or burn the .iso image of Kali to a CD/DVD.
https://unetbootin.github.io/

Go into the BIOS of your PC and change the boot order.
Make the first choice either USB or CDROM which ever method you used.
http://www.online-tech-tips.com/comp...order-windows/

-::_If you have the motherboard book to your PC it will tell you which key to press to get into the BIOS Setup.-::_

Kyrinn · 10-03-2016, 08:29 PM

Quote:

Originally Posted by Ztcoracat

Hi & Welcome to Linux Questions.

You can download the .iso image of Kali Linux from here.
https://www.kali.org/downloads/

Once it's downloaded check the integrity of the file. It should match the long number (SHA) on that page that I linked for you.

Next use unetbootin to place Kali on a usb pen drive and make it bootable or burn the .iso image of Kali to a CD/DVD.
https://unetbootin.github.io/

Go into the BIOS of your PC and change the boot order.
Make the first choice either USB or CDROM which ever method you used.
http://www.online-tech-tips.com/comp...order-windows/

-::_If you have the motherboard book to your PC it will tell you which key to press to get into the BIOS Setup.-::_

Thanks for the quick reply! I actually have Kali installed and configured. My problem is the installation of the onscreen keyboard Dasher. Sorry if that wasn't clear.

Ztcoracat · 10-04-2016, 08:14 PM

Sorry I misunderstood.

Your going to need a member that is good with this type of software.

There are a lot of Warnings and configure errors and mention of having to rebuild things and things that failed with exit status. Sorry I'm not your man for this type of software.

I was fortunate to have help from knudfl in the past on getting Simon installed and working.
I couldn't of done it without his help.

Ztcoracat · 10-04-2016, 08:37 PM

http://www.bltt.org/software/dasher/

Kyrinn · 10-04-2016, 08:56 PM

Okay, well hopefully someone will find this post and point me in the right direction. I spent about 2 hours today trying to get around my inability to install Dasher. I thought that I might be able to get around it by installing Wine, and although I thought I had it, I couldn't actually do anything with the .msi install file for Dasher. From what I've read Kali is one of the worst ways to learn Linux, but due to the nature of the course, I don't really have another option.

Thanks in advance to anyone able to fix my quandary.

Ztcoracat · 10-04-2016, 09:11 PM

I downloaded Dasher.
I'll have to untar it, read the ReadME and or the INSTALL file and see if I can install it on my system. If I'm able to I'll let you know.

Might take me a few days; I'm not feeling well.

Kyrinn · 10-06-2016, 06:55 PM

Thanks, man. I really appreciate it. Get to feeling better.

Ztcoracat · 10-07-2016, 09:55 AM

Quote:

Originally Posted by Kyrinn

Thanks, man. I really appreciate it. Get to feeling better.

The antibiotics that the Dr. gave me is killing the sinus infection and I'm starting to feel better;thanks. However I'm having surgery next week.

I'll try to get Dasher installed or at least figured out before surgery if I can.

Ztcoracat · 10-07-2016, 10:07 AM

I read the INSTALL file that came with Dasher.

Briefly, the shell commands to install Dasher are `./configure; make; make install' should
configure, build, and install this package. When configure is done running and your back to your bash prompt than type make. When make is done become 'root' and than type make install.

If you get errors when running make it will generally tell you why and what is missing.
It's been my experience with make errors that most of the time you need to install the package or packages that make is complaining about that it needs. Than you can re-run ./configure and than make again.

Code:

1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.

     Running `configure' might take a while.  While running, it prints
     some messages telling which features it is checking for.

  2. Type `make' to compile the package.

  3. Optionally, type `make check' to run any self-tests that come with
     the package.

  4. Type `make install' to install the programs and any data files and
     documentation.

Kyrinn · 10-07-2016, 04:31 PM

Here's the error I get: bash: ./configure: No such file or directory

Am I running the configuration in the wrong directory? That would be embarrassing. I'm currently trying the 5.0 version of Dasher, though I tried the stable 4.11 with the same results. Here's exactly what I typed:

Code:

root@kali:~/dasher-DASHER_5_0_0_beta# ./configure
bash: ./configure: No such file or directory

Ztcoracat · 10-07-2016, 04:52 PM

Quote:

Originally Posted by Kyrinn

Here's the error I get: bash: ./configure: No such file or directory

Am I running the configuration in the wrong directory? That would be embarrassing. I'm currently trying the 5.0 version of Dasher, though I tried the stable 4.11 with the same results. Here's exactly what I typed:

Code:

root@kali:~/dasher-DASHER_5_0_0_beta# ./configure
bash: ./configure: No such file or directory

Yeah, your in the wrong directory:- And you shouldn't be running ./configure as root. Run it as regular user.

Here's my example. I downloaded Dasher to my Downloads directory and when I click on the dasher-4.11 file it gives me this exact PATH: home/zebracat/Downloads/dasher-4.11/.

So this is what it would look like in the terminal:

Code:

home/zebracat/Downloads/dasher-4.11/./configure

-::-your home/your username/directorythatdasher's in/dasher-4.11/./configure-::-

Kyrinn · 10-07-2016, 05:26 PM

I feel like I'm going crazy; same thing. I can actually see the configure.ac in the folder and the ls. Here's the exact message as I probably screwed something up.

Kyrinn@kali:~/Desktop/dasher-DASHER_4_11_0$ ./configure
bash: ./configure: No such file or directory

Ztcoracat · 10-07-2016, 06:40 PM

Quote:

Originally Posted by Kyrinn

I feel like I'm going crazy; same thing. I can actually see the configure.ac in the folder and the ls. Here's the exact message as I probably screwed something up.

Kyrinn@kali:~/Desktop/dasher-DASHER_4_11_0$ ./configure
bash: ./configure: No such file or directory

At your bash prompt try this:

Code:

cd Desktop/dasher-DASHER_4_11_0

Than hit the Enter key.
Next type ./configure at the end of /home/Desktop/dasher-DASHER_4_11_0

IF you still get no such file or directory run this for me and post the output of what the terminal returns.

Code:

cd Desktop
ls

Did you rename the dasher directory?

On my system dasher is "dasher-4.11" not DASHER_4_11_0-

Kyrinn · 10-07-2016, 11:19 PM

Well, I would let you know if that fixed the problem, but I appear to have bricked my kali install. The good news is that I'm running it on a VM just for this reason. I will probably need to set it up again from scratch... which honestly might not be a bad thing. I will let you know what's up after I (hopefully) undo my stupidity.