Is Adept not working??

[mitchhobbs]

Successfully installed Fiesty, over 200 updates to install through adept updater including adept itself. After updating adept doesn't work now. Have tried in terminal to: sudo apt-get update and sudo apt-get upgrade. This works in terminal but when I start adept it crashes and the updater shows there is 1 update to install but when I start it, it also crashes. Is there a bug with adept? Oh, I'm running Fiesty 4. Saw an earlier thread about adept crashing but he fixes there don't work with mine. Would apprechiate any help or info.

[dibl]

Re: Is Adept not working??

Yes, I can confirm that yesterday's upgrade broke Adept. I got the upgrade as 2.6.20-9-generic, (upgrade to my 2.6.20-8-generic), and it brought back 2.6.20-5-386, which I had commented out of my Grub menu last week. I had to reinstall the Nvidia driver in 2.6.20-9-generic, and now I've got back to a good Xserver and all seems stable, except Adept is broken. I did all the apt-get commands in the manual, but no joy. I think we're waiting ......



BTW, I attempted to install the Nvidia driver in 2.6.20-5-386, and it won't go -- seems to be lacking some essential library files. My CPU is an Intel X6800 so one would think the 386 kernel would be the best, but I've been consistently getting a much happier system using the generic kernel. I'd love to hear of other folks' experiences with both kernels on Intel CPUs.

[claydoh]

Re: Is Adept not working??

http://kubuntuforums.net/forums/inde...55047#msg55047

try reinstalling kubuntu-desktop and adept, I think it is all fleshed out now, as is the nvidia-glx driver for the new kernel - it hadn't been uploaded yet, but is there now.

[dibl]

Re: Is Adept not working??

Thanks Claydoh -- yes, I'm not risking anything crucial with my Feisty system -- it's for playing and experiments (and breaking ....).

Also, I didn't state clearly that I'm using the proprietary -9746 Nvidia driver downloaded from their site, not the glx driver from the repos.

Thanks again -- appreciate the advice!

[claydoh]

Re: Is Adept not working??

Then you must know you will need to reinstall that driver every time the kernel changes
but those missing files should be there now

Are the new drivers simply adding newer card support? I have seen no advantage/performance gain in using any newer nvidia drivers on my fx6200 and fx5500 cards so I stick with the 'stock' Ubuntu ones at the moment

[dibl]

Re: Is Adept not working??

I didn't spent much time with the glx driver, but I quickly got the impression after the first time that I installed -9746 that I've got considerably more capabilities with the Xserver configuration utility that the glx driver had. I can twiddle the monitor settings a lot, and have them written to the xorg.conf file (although that feature doesn't seem to be working today as well as it did last week ...).

If you haven't tried Nvidia's installation routine and their new proprietary driver, you should try it once just to see how you like it. It begins to approach the functionality of the ATI and Nvidia drivers for Windows, believe it or not.



Or, maybe I didn't explore the glx driver as far as I should have ....

:P

[andreab]

Re: Is Adept not working??

same problem form me , adept starts , and crashes after loading the bar on the right bottom corner.

(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)
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1233217840 (LWP 6899)]
(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 0xb68989f6 in ?? () from /lib/tls/i686/cmov/libc.so.6
#7 0xb7fcef42 in ?? () from /lib/ld-linux.so.2
#8 0xb689ae18 in ?? () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7ef7b42 in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#10 0xb7eeff9c in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#11 0xb7eec56c in ?? () from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#12 0x00000001 in ?? ()
#13 0xb7fdfff4 in ?? () from /lib/ld-linux.so.2
#14 0xb7fc4a18 in ?? ()
#15 0xbfec35e8 in ?? ()
#16 0xbfec3604 in ?? ()
#17 0xb7fcf103 in ?? () from /lib/ld-linux.so.2
#18 0xb689c5ee in malloc () from /lib/tls/i686/cmov/libc.so.6
#19 0xb6a5e1e7 in operator new () from /usr/lib/libstdc++.so.6
#20 0xb7f8bd45 in debIFTypeStatus::CreatePkgParser ()
from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#21 0xb7f342c6 in pkgRecords:kgRecords ()
from /usr/lib/libapt-pkg-libc6.4-6.so.3.53
#22 0x08136fce in ?? ()
#23 0x0812d104 in ?? ()
#24 0x08128fec in ?? ()
#25 0x08129ece in ?? ()
#26 0x0807ae7c in ?? ()
#27 0x0807bd64 in ?? ()
#28 0x080768fd in ?? ()
#29 0x0807722e in ?? ()
#30 0xb708f813 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#31 0xb741b91c in QSignal::signal () from /usr/lib/libqt-mt.so.3
#32 0xb70af7a6 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#33 0xb70b71bc in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#34 0xb70269e8 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#35 0xb7028817 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#36 0xb77ebd52 in KApplication::notify () from /usr/lib/libkdecore.so.4
#37 0xb6fb91e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#38 0xb7019433 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#39 0xb6fcdd25 in QEventLoop:rocessEvents () from /usr/lib/libqt-mt.so.3
#40 0xb70410be in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#41 0xb7040ece in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#42 0xb7028591 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#43 0x08073225 in ?? ()
#44 0xb6848ebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#45 0x08072f51 in ?? ()


that is

[tonihele]

Re: Is Adept not working??

I can confirm this too.

[dibl]

Re: Is Adept not working??

Yep, still broke, after running apt-get dist-upgrade, apt-get update, and apt-get --reinstall install adept. I get the same crash traceback as Andrea. So, I'm satisfied we're still waiting for the fix.

[claydoh]

Re: Is Adept not working??

Launchpad is a good place to report or find info about these things.

here is one of the bug reports concerning this, I do believe they are working on it. Until then, either use apt/aptitude or try out synaptic.

Ahhh, they joys of development testing

[dibl]

Re: Is Adept not working??

I was wondering if Synaptic is OK to install in Kubuntu. I played with it on an elive installation and it seems pretty nice.

[Bongo5HH]

Re: Is Adept not working??

Someone told me to install Synaptic to solve a problem I was having - which turns out was that Adept was broken. I can report that it works great.

I find it a bit more cumbersom (spelling?) than Adept but it does work. And in the end that's what I need. So you ask what am I doing running an OS that's still in Alpha? I'm just dumb I guess, just dumb.

Kev

[dibl]

Re: Is Adept not working??

Yep, I'm dumb like that too.

:P

I'm going to give Aptitude a try when I'm home this evening, along with Synaptic. Might as well break it all!

[claydoh]

Re: Is Adept not working??

lol I have 2 Feisties to deal with, fun fun fun (so I m twice as dumb)
Synaptic is a nice app, It doesn't really have many deps to install either. I find myself using Ddept more and more lately, it has become rather nice.

[caryb]

Re: Is Adept not working??

I can report mine is broken too! have added it to the launchpad bug filed:-(


Cary