Fixed in 3.0 beta 2.
** Changed in: adept (Ubuntu)
Status: In Progress = Fix Released
--
Poor resolution of database locked problem
https://bugs.launchpad.net/bugs/48627
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Hi all,
Some comments. I have apt Version 0.7.9ubuntu15
I was doing sudo aptitude update
While downloading the index one of the index files was corrupt or something.
It did the whole cycle of the update.
Then I tried to re-update the index the following things came up :-
[EMAIL
On Wed, 02 Apr 2008 19:36:53 +0100, Yuriy Kozlov [EMAIL PROTECTED]
wrote:
James: Thanks for your interest in testing. However, the attached patch
has already been applied and it seems it still doesn't fix the problem
in some situations such as yours. You should be able to work around
Try this command, it should solve the problem:
sudo fuser -vki /var/lib/dpkg/lock; sudo dpkg --configure -a
Yes, the patch is already applied in the distribution. This has nothing
to do with a failed attempt to install SuSE, it has to do with a failed
attempt to install a package in Adept and
Hi,
I recently opened a new bug report called Cannot update packages at all Bug
no [EMAIL PROTECTED]
However, on reading this bug report I think that this is the problem I am
experiencing. I tried downloading the patch but it loads as a Text file.
Being quite new to this I wondered if somone
James: Thanks for your interest in testing. However, the attached patch has
already been applied and it seems it still doesn't fix the problem in some
situations such as yours. You should be able to work around this bug by
running:
dpkg --configure -a
--
Poor resolution of database locked
Confirmed hardy beta (64bit). This bug was the only way I figured out
how to fix it.
I was having multiple problems with Adept refusing to install/resintall
certain package before this happened. Then after a few attempts it
refused to open. Using `dpkg --configure -a` allowed Adept to restart
omg i was loosing my mind till i found this page thankx all this must
have worked cause after the dpkg --configure -a in terminal sudo dpkg
--configure -a i dont get the error message so now off to install beryl
--
Poor resolution of database locked problem
https://bugs.launchpad.net/bugs/48627
I've the same problem with hardy alpha 4. From the message box Another
process is using the packaging system database (probably some other Adept
application or apt-get or aptitude).Would you like to attempt to resolve this
problem? No will enter read-only mode and Cancel to quit and resolve
** Changed in: adept (Ubuntu)
Assignee: Martin Böhm (martin.bohm) = (unassigned)
--
Poor resolution of database locked problem
https://bugs.launchpad.net/bugs/48627
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
I'm changing the status of this bug to In Progress, since a fix has
been, in fact, released, but not working perfectly.
Launching Adept will trigger a popup which asks how the user wants to
resolve the locked database problem. If the user chooses Yes, the dpkg
command will be run, but it will
As the fix obviously hasn't improved anything, I'm resetting the status
to confirmed.
** Changed in: adept (Ubuntu)
Status: Fix Committed = Confirmed
--
Poor resolution of database locked problem
https://bugs.launchpad.net/bugs/48627
You received this bug notification because you are a
Still crashing in Gutsy on clicking yes. Apt-get is smart enough to
determine that dpkg --configure -a is required, so this should be
possible for Adept too. See also the related bug #172592.
--
Poor resolution of database locked problem
https://bugs.launchpad.net/bugs/48627
You received this
yes on beta gutsy I still experience the problem described by nfinity if I
click on YES
and the crash is not usable
( a dpkg --configure -a was required )
--
Poor resolution of database locked problem
https://bugs.launchpad.net/bugs/48627
You received this bug notification because you are
I don't know if it fixes the problem, but in Kubuntu 7.10 tribe5 I still have
this problem.
Clicking on Yes - I would like to attempt to resolve the problem does not
resolve the problem, instead it crashes.
--
Poor resolution of database locked problem
https://bugs.launchpad.net/bugs/48627
You
Confirmed
--
Poor resolution of database locked problem
https://bugs.launchpad.net/bugs/48627
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Patch applied and uploaded, will close the bug when someone confirms it
fixes the issue.
** Changed in: adept (Ubuntu)
Status: In Progress = Fix Committed
--
Poor resolution of database locked problem
https://bugs.launchpad.net/bugs/48627
You received this bug notification because you
Here's a patch for this issue. After investigating the work necessary
for this fix, I've discovered that it would be just as simple to call
dpkg directly rather than using another script to do this. I know this
seems like duplication of work, and I greatly apologize for this, but in
the interest
Personally I've got lost trying to figure out how things were working.
So I guess I'll not object to something simple that just do the equivalent of
'dpkg --configure -a'.
--
Poor resolution of database locked problem
https://bugs.launchpad.net/bugs/48627
You received this bug notification
I believe what is proposed is avoiding to fix the real problem.
I believe one of the real problem is at:
adept-2.1.2ubuntu27/adept/updater/app.cpp where we have:
aptFront::Manager m;
m.setProgressCallback( m_progress-callback() );
m.setUpdateInterval( 10 );
try {
On Monday 02 July 2007 12:22:14 Paul Dufresne wrote:
I believe what is proposed is avoiding to fix the real problem.
I believe one of the real problem is at:
adept-2.1.2ubuntu27/adept/updater/app.cpp where we have:
aptFront::Manager m;
m.setProgressCallback( m_progress-callback() );
On Monday 02 July 2007 12:22:14 Paul Dufresne wrote:
I believe what is proposed is avoiding to fix the real problem.
I believe one of the real problem is at:
adept-2.1.2ubuntu27/adept/updater/app.cpp where we have:
aptFront::Manager m;
m.setProgressCallback( m_progress-callback() );
I also believe that m.commit() is a synchronous call... so I believe that it
does wait for the m.commit() to finish. I could be wrong though.
Well, by experience I know I see in the details window that it continue while
showing the message.
So I firmly inclined to believe it is not so
my bug report (would of saved allot of my time posting it if it could of found
This and just added an small comment as i am now)
https://bugs.launchpad.net/ubuntu/+source/adept/+bug/123343
java made mine stop but in any case it should be cleaned up (is that
tool ready yet?)
--
Poor resolution
Good news: I have created a small Python tool called Adept
Resolverthat detects and fixes this problem. It has a simple KDE GUI as
well.
However, in order to make Adept compatible with this tool, we need to
make Adept realize that dpkg --configure -a is required. The apt-get
application is able
I'm going to try and take care of this bug. Marked it as In Progress
because a fix (the Adept Resolver tool) is currently underway as a
branch in Launchpad: https://code.launchpad.net/~martin.bohm/adept
/adept-resolver .
** Changed in: adept (Ubuntu)
Assignee: (unassigned) = Martin Böhm
I get the same basic issue with sudo aptitude update. It was hanging
on one of the package repositories, so I had to ctrl-C it. Subsequent
attempt to re-run the command gave me this error:
E: Could not get lock /var/lib/apt/lists/lock - open (11 Resource temporarily
unavailable)
E: Couldn't
Confirmed , and I agree.
--
Poor resolution of database locked problem
https://launchpad.net/bugs/48627
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
I totally agree. Also, when an installation hangs/is interrupted, adept
should unlock itself automatically.
--
Poor resolution of database locked problem
https://launchpad.net/bugs/48627
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
The dialog should say something like If you are not running another
instance of Adept, click fix. And then a button to run the command to
fix it and restart Adept.
** Changed in: adept (Ubuntu)
Status: Unconfirmed = Confirmed
--
Poor resolution of database locked problem
30 matches
Mail list logo
