Adept Crash

[D. Michael McIntyre]

On Monday 30 July 2007, Ollie Killingback wrote:

> it's caused by signal 11 (SIGSEGV).  When I look at backtrace all seems
> to be going well until

> (no debugging symbols found)
> [KCrash handler]
> #6  0x0817641b in ?? ()

> Does this tell me where it crashed?

No, it's a completely useless trace that tells you nothing.

I've been having problems with Adept crashing since I upgraded to Feisty.  I 
don't think I've completed a whole update cycle without a crash.  Also, when 
I click on the little taskbar icon to launch this application, nothing 
happens.  The other day, I did something or other, I don't know exactly what, 
and suddenly 10 Adept Updaters all winked into being at once.  They were 
stalled out waiting on whatever I did.

Something's definitely screwy, but I haven't tried to fix it.  I just do 
things the old fashioned way, from the command line.

-- 
D. Michael McIntyre