Re: 2 new messages in 1 topic - digest

[Father Gordon Gilbert]

Hi again folks,

Thanks for your help, Csaba.  But I've come to a problem already.  I downloaded the file, then did the tar, but when I did the next step, it said "autoconf not found"  so I looked for that, and I have two versions of autoconf, both newer than required.  Am I in the wrong dir or something?

How do I continue from here?

Fr. Gordon Gilbert

On 31/08/06, krusader-users group < nor...@googlegroups.com> wrote:

krusader-users
http://groups.google.com/group/krusader-users

krusade...@googlegroups.com

Today's topics:

* Help! My new install of 1.70 crashes! - 2 messages, 2 authors
http://groups.google.com/group/krusader-users/browse_thread/thread/3bdd97ff513ddd0e

==============================================================================
TOPIC: Help! My new install of 1.70 crashes!
http://groups.google.com/group/krusader-users/browse_thread/thread/3bdd97ff513ddd0e
==============================================================================

== 1 of 2 ==
Date: Wed, Aug 30 2006 3:42am
From: "FrGord"


Hi group,

I'm new to this, but I need help.  I've used Krusader for years now,
and found it very helpful.  I run FreeBSD 6.x on a pretty decent
machine.  In FreeBSD, they have ports with which to install programs,
and 'portupgrade' to upgrade apps to newer versions.

A few days ago, I portupgraded Krusader from 1.60.0 (or so) to 1.70.0_1
(I think).  The upgrade appeared to go nominally, but when I tried to
fire it up, it simply crashed.  "Segmentation fault" is all I get, no
helpful log or anything.  In an effort to fix the situation, I also
portupgraded all my KDE, and that also seemed to go nominally, with no
failures or problems.

I'm reasonably savvy about computers, and not afraid to use a command
line, but I am not a geek.  So any poking around I might do at
someone's suggestion, the instructions must be very detailed -- I can't
fill in the blanks.

But your help will be appreciated to help me get Krusader back.

Blessings,

Fr. Gordon Gilbert





== 2 of 2 ==
Date: Wed, Aug 30 2006 2:00pm
From: Karai Csaba


Hi!

Probably your package is wrong.

You should compile the 1.70.1 version manually, or try to get a working
package from somewhere.

There are 3 possibilities:
1. - the package is wrong / or some deps are missing (most probable)
2. - 1.70.1 crashes, CVS not (not all crashfix were ported from CVS)
3. - Krusader is buggy and all version crashes

What to do: try to compile krusader
- Install the kdevelop package (this will install all developer files)
   The total size of KDevelop with its dependencies is close to
   500 MByte. Take care of it.
   After compiling a working krusader you could remove those new
   packages installed by kdevelop.

- Download the source

http://prdownloads.sourceforge.net/krusader/krusader-1.70.1.tar.gz?download

- Compile Krusader
   tar xvfz krusader-1.70.1.tar.gz
   cd krusader-1,70.1
   make -f Makefile.cvs
   ./configure --prefix=/usr/
   make
   make install

- Start Krusader: krusader

   If it crashes, please try it with the CVS version

   http://krusader.sourceforge.net/downloads/krusader-cvs-20060830.tar.gz


- If it also crashes, please try to debug

   compile a new Krusader with debug options

   ./configure --prefix=/usr/ --enable-debug
   make
   gdb krusader/krusader
   (gdb)r

   ---- here krusader crashes

   (gdb)bt

   ---- here the stack trace is listed, send this list to us on e-mail

   ---- we will correct the bug and krusader won't crash any more :-)))

Bye,


     Csaba


ext FrGord írta:
> Hi group,
>
> I'm new to this, but I need help.  I've used Krusader for years now,
> and found it very helpful.  I run FreeBSD 6.x on a pretty decent
> machine.  In FreeBSD, they have ports with which to install programs,
> and 'portupgrade' to upgrade apps to newer versions.
>
> A few days ago, I portupgraded Krusader from 1.60.0 (or so) to 1.70.0_1
> (I think).  The upgrade appeared to go nominally, but when I tried to
> fire it up, it simply crashed.  "Segmentation fault" is all I get, no
> helpful log or anything.  In an effort to fix the situation, I also
> portupgraded all my KDE, and that also seemed to go nominally, with no
> failures or problems.
>
> I'm reasonably savvy about computers, and not afraid to use a command
> line, but I am not a geek.  So any poking around I might do at
> someone's suggestion, the instructions must be very detailed -- I can't
> fill in the blanks.
>
> But your help will be appreciated to help me get Krusader back.
>
> Blessings,
>
> Fr. Gordon Gilbert
>
>
> >





==============================================================================

You received this message because you are subscribed to the Google Groups "krusader-users"
group.

To post to this group, send email to krusade...@googlegroups.com or visit http://groups.google.com/group/krusader-users

To unsubscribe from this group, send email to krusader-user...@googlegroups.com

To change the way you get mail from this group, visit:
http://groups.google.com/group/krusader-users/subscribe

To report abuse, send email explaining the problem to ab...@googlegroups.com

==============================================================================
Google Groups: http://groups.google.com

[Heiner]

On Friday 01 September 2006 02:19, Father Gordon Gilbert wrote:
> Hi again folks,
>
> Thanks for your help, Csaba. But I've come to a problem already. I
> downloaded the file, then did the tar, but when I did the next step, it
> said "autoconf not found" so I looked for that, and I have two versions of
> autoconf, both newer than required. Am I in the wrong dir or something?

Hi!

Please note, that FreeBSD differs from linux a bit here. In FreeBSD there is
no default autoconf. So I first apply the attached patch to the cvs. It
requires

7of9# ls /var/db/pkg | grep auto
autoconf-2.59_2
automake-1.9.6

to be installed. Others might work as well, but then you need to adjust the
patch. The actual build I do with the attached following script.

But this is for development only. Ordinary user should stuck to the port
system, which does all the magic for you.

Currently 1.70.1 is in the port system. I do not know, where you got a
1.70.0_1 from - this should never have been existed!

To further track down your problems, the following questions may help:

- where did you get your port tree from? From a cd or via cvsup?
- when have you updated your ports tree last time?
- how did you install kde & friends? Self compiled or from the binary
packages?
- what are the installed qt/kde versions?
- did the crash give a usefull KCrash message? If KCrash did not come up or
contains mainly question marks, the answer is no
- could you create a back trace? To do so, start krusader from the konsole via

/usr/local/bin/krusader --nocrashhandler

After the crash, go into the directory with the .core file and type

gdb -c krusader.core /usr/local/bin/krusader

On the command prompt, type bt followed by enter.
Maybe that you must press enter some times now. The whole output is of
interest.

Heiner