You are not logged in.

Feisty Adept problem - [Solved]

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

leftbas

Trainee

  • "leftbas" started this thread

Posts: 58

Location: Los Angeles, Ca, USA

Occupation: Senior Desktop Support Analyst

  • Send private message

1

Friday, April 20th 2007, 7:32pm

Feisty Adept problem - [Solved]

Hey, all. I just upgraded to to Feisty last night, and when I rebooted everything looked great! But adept claims the database is in use by another program. I rebooted a couple of times to clear out any mysterious programs that I might not recognize needing the use of the adept data file, but it didn't help. I can't even manage repositories. Anyone else have a problem like this after the upgrade?
In retrospect, everything is funny.

-- Unknown

This post has been edited 2 times, last edit by "leftbas" (Apr 23rd 2007, 6:33am)

leftbas

Trainee

  • "leftbas" started this thread

Posts: 58

Location: Los Angeles, Ca, USA

Occupation: Senior Desktop Support Analyst

  • Send private message

2

Monday, April 23rd 2007, 1:16am

No one, eh? If a screen shot would help, here it is. Maybe someone could tell me where the database is that I can check its permissions or something. I feel like I'm really stuck here if I can't update my system.

Thanks in advance.
leftbas has attached the following image:
  • adept error.png
In retrospect, everything is funny.

-- Unknown

leftbas

Trainee

  • "leftbas" started this thread

Posts: 58

Location: Los Angeles, Ca, USA

Occupation: Senior Desktop Support Analyst

  • Send private message

3

Monday, April 23rd 2007, 6:32am

Since I was able to figure this one out on my own, I guess my new status of Leading Software Engineer is warranted. For anyone else experiencing this problem, and it seems to be rather wide-spread, just run this command:

sudo dpkg --configure -a

I pulled the info from the following article:

https://answers.launchpad.net/ubuntu/+so…/+question/5301
In retrospect, everything is funny.

-- Unknown

This post has been edited 1 times, last edit by "leftbas" (Apr 23rd 2007, 6:33am)