[Dapper] Adept won't start -- many defunct adept processes

[Timothy Miller]

Binary package hint: adept

When I try to start Adept from the K menu, I am asked for my password, but Adept doesn't start. When I start it from a Konsole, it will start up (the messages I get don't mean much to me), but it won't install anything, making some comment about breaking things. It occurred to me that it might be that there's a lock being held on apt-get, so I looked for existing adept processes, and this is what I got:

ps -ef | grep adept
tim 5013 1 0 Sep09 ? 00:00:50 adept_notifier
root 4331 1 0 Sep22 ? 00:00:21 adept
tim 7413 4978 0 14:46 ? 00:00:00 kdesu -u root -c kdesu adept
root 7429 7426 0 14:46 ? 00:00:00 kdesu adept
root 7430 7429 0 14:46 ? 00:00:00 adept
root 7431 7430 0 14:46 ? 00:00:00 [adept] <defunct>
tim 7474 4978 0 14:47 ? 00:00:00 kdesu -u root -c kdesu adept
root 7489 7486 0 14:47 ? 00:00:00 kdesu adept
root 7490 7489 0 14:47 ? 00:00:00 adept
root 7494 7490 0 14:47 ? 00:00:00 [adept] <defunct>
tim 13652 4978 0 15:09 ? 00:00:00 kdesu -u root -c kdesu adept
root 13672 13669 0 15:09 ? 00:00:00 kdesu adept
root 13673 13672 0 15:09 ? 00:00:00 adept
root 13674 13673 0 15:09 ? 00:00:00 [adept] <defunct>
tim 19242 19830 0 15:20 pts/8 00:00:00 grep adept

Here's what I get when I try to start adept via konsole:

sudo adept
Password:
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kapture::PkgSystem::PkgSystem()
adept: PackageDetails::setPackage()
adept: PackageInfo::setPackage()
adept: PackageInfo::setVersion() (valid)
adept: PackageDetails::notifyPostChange()
adept: PackageDetails::loadFileList()
adept: PackageDetails::loadFileListWorker() entering loop
adept: PackageDetails::loadFileListWorker() leaving loop
ScimInputContextPlugin()
adept: TagList: scheduling update
adept: TagList: scheduling update
adept: ExtendableList::updateExtenders(); count = 3
adept: ExtendableList::updateExtenders(); count = 0
adept: ExtendableList::updateExtenders(); count = 0
adept: ExtendableList::updateExtenders(); count = 3
adept: ExtendableList::updateExtenders(); count = 3
adept: ERROR: Communication problem with adept, it probably crashed.
tim@hermione:/etc/init.d$ adept: rebuild running
adept: querying m_rangeProvider 0x84c8894...
adept: clearing...
adept: ExtendableList::clear()
adept: end of ExtendableList::clear()
adept: asyncCall to rebuildInsertRange...
adept: starting the thread...
adept: PackageDetails::updateLogical()
adept: PackageDetails::updateLogical: p = python-tclink p.component() = 0x834cc50
adept: rebuild running
adept: querying m_rangeProvider 0x8500f44...
python
python2.4-tclink
python
adept: clearing...
adept: ExtendableList::clear()
adept: end of ExtendableList::clear()
adept: asyncCall to rebuildInsertRange...
adept: starting the thread...
adept: ExtendableList::updateExtenders(); count = 3
adept: TagList (Tags I Want (drop tags here)): updating list
adept: TagList (Tags I Do Not Want (drop tags here)): updating list
adept: ExtendableList::updateExtenders(); count = 3
adept: thread finished...
adept: 3 entities synced, time = 1050
adept: thread finished...
adept: 18379 entities synced, time = 1050
adept: FilterSidebar::setCardinality
adept: PackageDetails::loadFileList() finished
adept: PackageDetails::setPackage()
adept: PackageInfo::setPackage()
adept: PackageInfo::setVersion() (valid)
adept: PackageDetails::notifyPostChange()
adept: PackageDetails::loadFileList()
adept: TagList: scheduling update
adept: TagList: scheduling update
adept: ExtendableList::updateExtenders(); count = 3
adept: ExtendableList::updateExtenders(); count = 0
adept: ExtendableList::updateExtenders(); count = 0
adept: PackageDetails::loadFileListWorker() entering loop
adept: PackageDetails::loadFileListWorker() leaving loop
adept: ExtendableList::updateExtenders(); count = 3
adept: ExtendableList::updateExtenders(); count = 3
adept: rebuild running
adept: querying m_rangeProvider 0x8b00a5c...
adept: clearing...
adept: ExtendableList::clear()
adept: end of ExtendableList::clear()
adept: asyncCall to rebuildInsertRange...
adept: starting the thread...
adept: PackageDetails::updateLogical()
adept: PackageDetails::updateLogical: p = python-tclink p.component() = 0x834cc50
adept: rebuild running
adept: querying m_rangeProvider 0x8b2bc0c...
python
python2.4-tclink
python
adept: clearing...
adept: ExtendableList::clear()
adept: end of ExtendableList::clear()
adept: asyncCall to rebuildInsertRange...
adept: starting the thread...
adept: ExtendableList::updateExtenders(); count = 3
adept: TagList (Tags I Want (drop tags here)): updating list
adept: TagList (Tags I Do Not Want (drop tags here)): updating list
adept: ExtendableList::updateExtenders(); count = 3
adept: thread finished...
adept: 3 entities synced, time = 1050
adept: thread finished...
adept: 18379 entities synced, time = 1050
adept: FilterSidebar::setCardinality
adept: PackageDetails::loadFileList() finished
Uh oh.. can't write data..
adept: ExtendableList::updateExtenders(); count = 3
adept: ExtendableList::updateExtenders(); count = 3
adept: ExtendableList::updateExtenders(); count = 3
adept: ExtendableList::updateExtenders(); count = 3
adept: ExtendableList::updateExtenders(); count = 0
adept: ExtendableList::updateExtenders(); count = 0
adept: ExtendableList::updateExtenders(); count = 0
adept: ExtendableList::updateExtenders(); count = 3
adept: ExtendableList::updateExtenders(); count = 0
adept: ExtendableList::updateExtenders(); count = 0
adept: ExtendableList::updateExtenders(); count = 0
adept: ExtendableList::updateExtenders(); count = 3
adept: ExtendableList::updateExtenders(); count = 0
adept: ExtendableList::updateExtenders(); count = 0
adept: ExtendableList::updateExtenders(); count = 3
adept: rebuild running
adept: querying m_rangeProvider 0x84c8894...
adept: clearing...
adept: ExtendableList::clear()
adept: end of ExtendableList::clear()
adept: asyncCall to rebuildInsertRange...
adept: starting the thread...
adept: ExtendableList::updateExtenders(); count = 0
adept: thread finished...
adept: 18379 entities synced, time = 1400
adept: Progress::Done()
adept: FilterSidebar::setCardinality
adept: ExtendableList::updateExtenders(); count = 0
adept: rebuild running
adept: querying m_rangeProvider 0x8b00a5c...
adept: clearing...
adept: ExtendableList::clear()
adept: end of ExtendableList::clear()
adept: asyncCall to rebuildInsertRange...
adept: starting the thread...
adept: thread finished...
adept: 0 entities synced, time = 220
adept: Progress::Done()
adept: FilterSidebar::setCardinality

[Jonathan Jesse (jjesse)]

Hello I noticed this bug references Dapper and I am unable to replicate this bug on my Dapper build. I am also able to run Adept correctly in Edgy as well as Feisty.
Are you still having problems with running Adept? If so could you please use apt to update your system to make sure it is on the latest version and then try to reproduce this bug?

Thanks,

Jonathan

[Timothy Miller (theosib)]

This problem doesn't happen incredibly often, but it does happen now and again, and it still happens even now. Sometimes, Adept will get "stuck" in some way that makes it not quit properly. The window is gone, because I told it to close, but the process is still running. When I later decide to install something else, I try to run adept, and nothing happens. I'll wait a few minutes and try again. Then I'll think to check the process table, and discover that the original process was still there, along with each of the retries.

Bug 1: Adept doesn't always quit properly.

Bug 2: If Adept sees another adept process already running, it silently slips into the background, running, but doing nothing. It should produce some sort of error message!

[Jonathan Jesse (jjesse)]

I know the developers have a done a ton of work on Adept for Feisty and I was wondering if you had a chance to test things there or not?

[Timothy Miller (theosib)]

I'm afraid I can't try Feisty for my main desktop. I'm running software RAID, which is known to get broken during upgrades (on top of all of the other horrors that happen in Dapper -> Edgy upgrades).

I did try installing Feisty under Parallels, but the installer always locks up, so I had to use CentOS instead. As soon as ubuntu developers have fixed the installer bugs, I'll try again.

[arashi_kage (barrett-152)]

I am using Feisty and am having a similar problem. Adept repeatedly does not start the first time from the K menu or the auto notifier. It will work if I try it again. When it fails to start it also fails to bring up the password window. This is how I judge if it is going to work.

[Jonathan Jesse (jjesse)]

Changing it back to unassigned as it goes beyond what I can troubleshoot

[grenerd (grenerd)]

hey guys I recently encountered the same problem. The way I fixed it was to open Ksysguard (Kubuntu Performance monitor) and search for adept. Next i went into the console and did a :

sudo kill (PID from ksysguard).

I did it maybe twice and they all disappeared. Hope this helps!

[Timothy Miller (theosib)]

In any case, adept processes shouldn't be left lying around so that users have to manually kill them.

[Marco Maini (maini10)]

This problem looks like bug 64422, currently confirmed in the development version Gutsy. I'll mark as duplicate of that. Thanks again for your collaboration.

[Launchpad Janitor (janitor)]

[Expired for adept (Ubuntu) because there has been no activity for 60 days.]