crash of adept_manager in Kubuntu 6.10

Can you run run it from a console and give us the exact error message please.

I got some info, here is it:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47518831236704 (LWP 5110)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00002b37d3c91c71 in nanosleep () from /lib/libc.so.6
#0 0x00002b37d3c91c71 in nanosleep () from /lib/libc.so.6
#1 0x00002b37d3c91a94 in sleep () from /lib/libc.so.6
#2 0x00002b37d3f45575 in KCrash::startDrKonqi ()
   from /usr/lib/libkdecore.so.4
#3 0x00002b37d3f59b07 in KCrash::defaultCrashHandler ()
   from /usr/lib/libkdecore.so.4
#4 0x00002b37d3c2d510 in killpg () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Sounds like this may be related to bug 73641.

https://launchpad.net/bugs/73641

If I run adept manager using kdesu -c adept_manager I get no stack trace (see 73641 for auth_log output in that case). If I run without kdesu I get this on standard output:

ramin@localhost:/home/ramin$ adept_manager
kapture::PkgSystem::PkgSystem()
ramin@localhost:/home/ramin$ KCrash: Application 'adept_manager' crashing...

And this in the back trace of the KDE crash handler:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233172816 (LWP 27017)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb718fb76 in QGDict::hashKeyAscii () from /usr/lib/libqt-mt.so.3
#7 0xb718fe8a in QGDict::look_ascii () from /usr/lib/libqt-mt.so.3
#8 0xb6e89be1 in QAsciiDict<QMetaData const>::insert ()
   from /usr/lib/libqt-mt.so.3
#9 0xb6e88942 in QMetaObject::init () from /usr/lib/libqt-mt.so.3
#10 0xb6e88ec6 in QMetaObject::QMetaObject () from /usr/lib/libqt-mt.so.3
#11 0xb6e89095 in QMetaObject::new_metaobject () from /usr/lib/libqt-mt.so.3
#12 0xb7d2dc6b in KFileDetailView::staticMetaObject ()
   from /usr/lib/libkio.so.4
#13 0xb7dbf727 in KFileDetailView::metaObject () from /usr/lib/libkio.so.4
#14 0xb6e988cf in QObject::connect () from /usr/lib/libqt-mt.so.3
#15 0xb7d7e53d in KFileDetailView::KFileDetailView ()
   from /usr/lib/libkio.so.4
#16 0x0813dc12 in PackageDetailsUi::staticMetaObject ()
#17 0x081323b8 in adept::PackageDetails::loadFileListWorker ()
#18 0x080b18ed in adept::PkgSystem::staticMetaObject ()
#19 0x0808e83d ...

This trace is quite useless without the debugs symbols, can you try with the -dbg KDE packages installed (I'm not a KDE user maybe someone more informed than me would like to explain the full progress)
And give a new trace with the debbuging symbols ?

Thanks for your bug report. The current version of adept works fine with no root privileges so I am marking it as fixed. If anyone sees this behaviour, please reopen. Please report more bugs as you find them.