Adept Crash

[manchicken]

On Monday 30 July 2007 19:04:23 D. Michael McIntyre wrote:
> 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

I haven't seen any of these problems... I'm wondering if you could give me 
some more information about what's going on.  I certainly would rank crash 
bugs at the top of the priority, but I'm having a heck of a time replicating 
these issues on either gutsy (UNSTABLE) or feisty.  Could you answer some 
questions?

1) Could you please give me your sources.list so that I can see if there's 
anything strange there?

2) Can you give me he version numbers for libapt-pkg, libept, tagcoll, and 
adept?

3) Could you give me a more step-by-step way to replicate these issues?

Again, I would love to get to the bottom of these issues, I'm just completely 
unable to replicate the behavior you're describing.  Thanks for your help.

-- 
~ manchicken <><
(A)bort, (R)etry, (I)nfluence with large hammer.
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0


Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html