Announcement

Collapse
No announcement yet.

Adept database locked because of wrong sources.list entry

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Adept database locked because of wrong sources.list entry

    I entered a new mirror to upgrade to KDE 3.5.7 and when I copied the URL I missed the d which is in front of each repository ( eb should be deb). When i tried to update, the system tells me the database is locked. I fixed the sources.list file, ran dpkg --configure -a, deleted the lock files in the var directory and still it is broken.

    Can only think it has written somewhere that the old sources.list is wrong.

    Any ideas?

    #2
    Re: Adept database locked because of wrong sources.list entry

    Originally posted by hvralpha
    Any ideas?
    Code:
    sudo apt-get update
    "Plan B": http://www.ubuntu-nl.org/source-o-matic/

    Comment


      #3
      Re: Adept database locked because of wrong sources.list entry

      Tried that, and most other options and it did not work.
      The problem was that I fixed sources.list but the error was also in the sources file.
      When I fixed that too and ran dpkg --configure -a it worked.
      Hard experience not to be forgotten. Who thought it will write in 2 files !
      Thanks for the help. Hopes it helps other people!!

      Comment


        #4
        Re: Adept database locked because of wrong sources.list entry

        I am too new at this to help, myself, however, I had this Adept problem and there may be similarities that would allow a similar fix for your problem. I will tell you my problem, then the fix. If you can see a way to use the code to ameliorate your problem, enjoy.

        Adept locked me out of Administration. The reason it gave was that another application was running at the same time and to shut off that application prior to attempting entry into Adept. I could find nothing like that happening.

        Bruce Marshall gave me this fix, and it worked great.

        Or, if you do not wish to reboot, but want to fix your problem anyways
        do the following:
        ps -ewf| grep adept|grep -v grep|awk '{print $2}'

        This will list all process being used by adept, one per line. Next you
        want a sure way to destroy these processes:

        sudo kill -9 <process>

        Where <process> is each process number separated by a space. for
        example if you got two lines like these:
        7513
        12158

        Your command will look like this:

        sudo kill -9 7513 12158

        Tpe your password when asked for it here.


        Once that is done, just use adept as you ussually do.

        If you understand this stuff, you may see a way to use this to end whatever is stopping Adept from performing. I don't know. I am just anxious to start being a contributor, and when I could see no response for your problem, I thought this might help. It took a long time to get an answer to my problem that worked.

        Comment


          #5
          Re: Adept database locked because of wrong sources.list entry

          Code:
          kdesu kate /etc/apt/sources.list
          Then find the repository in question and add the "d"

          Code:
          sudo apt-get update

          Comment


            #6
            Re: Adept database locked because of wrong sources.list entry

            Thanks Guys, see my fix in 2nd post.
            The apt-get update sequence did not work in my case.
            Worked after I fixed sources.list and sources with kate in superusermode.
            And deleted lock files in \var directory
            And used sudo dpkg --configure -a

            Comment


              #7
              Re: Adept database locked because of wrong sources.list entry

              I currently have a problem with Adept too, but previously I had a problem similar to yours and the solution for that was as follows, do the following:
              ps -ewf| grep adept|grep -v grep|awk '{print $2}'

              This will list all process being used by adept, one per line. Next you
              want a sure way to destroy these processes:

              sudo kill -9 <process>

              Where <process> is each process number separated by a space. for
              example if you got two lines like these:
              7513
              12158

              Your command will look like this:

              sudo kill -9 7513 12158

              Tpe your password when asked for it here.

              Once that is done, just use adept as you usually do.

              Note: if you did not get any process numbers, it might be some apt-get
              process, in this case replace 'adept' in the first command for 'apt'
              instead.

              Good Luck!

              Comment

              Working...
              X