Update of Feisty herd 4 Fails

[Peter Lindener]

Binary package hint: adept-installer

Virgin Feisty herd 4 install, on a Dell Inspiron laptop.
Install works just fine, but then the updater downloads just fine but during install a number of packages a window comes up indicating that the "nice value must be between -20 and 19 ( I think ) it said.
can't get back there though because the update installer ( Apt, Adept ? )'s data base has been left locked due to the erroring out of the program, so now when I reattempt I get a message the the data base is in use most likely by a another running copy of the program ( no not really )

    So sufice it to say this problem of upgrade will most likely come up for most users comming up on a clean slate, from Feisty herd 4, as soon as they attempt to update there system, As I recall the updater aborts for good when it errors during x11 updates.

    There were also some I think unrelated IO error messages prior under Adept's detail log,
I would send all of this if I could get back in, but I'm locked out of Adept's data base... Should I wait a day or two for Feisty herd 5..... this does seem like a real show stoper for any who would like to upgade there packages.

      otherwise, Feisty is looking real nice
            Cheers
                -Peter

ProblemType: Bug
Date: Sat Feb 17 11:19:02 2007
DistroRelease: Ubuntu 7.04
Uname: Linux whoey 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux

[Witold Krakowski (wkrakowski-gmail)]

"..., so now when I reattempt I get a message the the data base is in use most likely by a another running copy of the program ( no not really )"

Did you try to see the whether apt or adept process is not still locking the database?
Could You please try something like "ps aux | grep adept" or "ps aux | grep apt" in konsole? It is possible that adept's crash brought down the gui, but left a process locking the db....

For what regards the initial part of your report, it is a known issue, reported in bug #85800 and #85864, so I'll mark it as a duplicate of them. I also agree this is a showstopper.

Best Regards,
Witold

[Witold Krakowski (wkrakowski-gmail)]

I marked this as a duplicate of 87641, since that bug contains additional debug information.