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!

-- 
[Dapper] Adept won't start -- many defunct adept processes
https://launchpad.net/bugs/63036

-- 
kubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

Reply via email to