PUD crashing again.

[Jeff Mitchell]

Casey,

Try to be careful with your backtraces -- read them.  It should have been a 
clue that the PUD isn't at fault when not one instance of the word "popup" is 
to be found in your backtrace.

It's a complex backtrace with a bazillion threads, but a good thing to look at 
is always "<signal handler called>".  In your case:

Thread 9 (Thread 0xaebc9b90 (LWP 21401)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb7dcaeeb in waitpid () from /lib/libpthread.so.0
#2  0xb78c9faa in CueFile::load (this=0xb, mediaLength=51) at
/share/devel/kdesvn/extragear/amarokgit/src/cuefile.cpp:110
#3  <signal handler called>
#4  0xaf3fd5be in SqlQueryMaker::handleResult (this=0xa7635f0,
result=@0xaebc924c) at
/share/devel/kdesvn/extragear/amarokgit/src/collection/sqlcollection/SqlQueryMaker.cpp:598

As Ian pointed out, the "this=0xb" is troubling, but it's also strange that it 
happened *after* the signal handler was called.  Regardless, your problem is 
almost sure to lie in SqlQueryMaker::handleResult.

--Jeff