Re: 1 new message in 1 topic - digest

On Sunday 03 September 2006 19:57, Father Gordon Gilbert wrote:
> 1. My ports tree is via cvsup.  My son is one of the maintainers, and he
> has always said that when I want to upgrade anything, I should have the
> latest ports --

Well, you might grep an inconsistent state this way. But I do the same - so 
probably no problem here. Note, that cvsup updates the ports only - the 
installed software is not affected by this! To upgrade usually portupgrade is 
been used.

> 2.  So my latest cvsup was within a week before installing (well,
> portupgrading -- much the same I think) Krusader 1.70

ls /var/bd/pkg | grep krusader

will tell

> 3.  I don't do any self-compiling (except for Lilypond, and their stuff is
> really easy).  KDE and all other programs are installed via ports if I do
> them, and even my son does it this way 99.9% of the time.

This is a more imprtant question: how do upgrade the ports? I guess via 
portupgrade. Do you use the -P or -PP switch? If so, portupgrade is 
downloading compiled packages and installes them. If not it downloades the 
source codes and does the compilation for you.

> 4.  KDE version is the latest (2.5.3), because I upgraded that since the
> install of the non-working Krusader.  QT is version 3.3.5

I guess you mean 3.5.3. 

ls /var/db/pkg | grep kde     

will tell

> 5.  KCrash did not come up.  The only thing I got was a "core dump" line in
> the xterm.

This is because of fvwm I guess

> 6.  I don't have the complete KDE system running -- I use FVWM2 as my
> window manager (simple, but I like it) and so I use XTerms when I need
> something like that.  No helpful info came from that.  Here's what happens
> when I do that:

That *might* be an issue. I never tried krusader under fvwm2. But on the other 
hand it worked before and I do not know, what change might have stopped this.

I am not sure how to continue. One idea might be to leave the system as it is 
but to go back to the krusader version, which was working (to see if it still 
does). The "how" depends on the answers on the questions above.

The other is to analyze the core dump. If you go (with xterm) into the 
directory you started krusader from, what does 

ls -l *.core

show? And what does

ls -l /usr/local/bin/krusader

show?


Heiner


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"krusader-users" group.
To post to this group, send email to krusader-users@xxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to 
krusader-users-unsubscribe@xxxxxxxxxxxxxxxx
For more options, visit this group at 
http://groups.google.com/group/krusader-users
-~----------~----~----~----~------~----~------~--~---