Bug#850417: dpkg: error: dpkg status database is locked by another process

2017-07-26 Thread Vincent Lefevre
To make things clear in this bug, this bug has been confirmed: https://lists.debian.org/debian-dpkg/2017/01/msg00044.html (as referenced in bug 869546). -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#850417: dpkg: error: dpkg status database is locked by another process

2017-01-10 Thread Vincent Lefevre
Hi! On 2017-01-11 03:14:13 +0100, Guillem Jover wrote: > On Fri, 2017-01-06 at 13:46:14 +0100, Vincent Lefevre wrote: > > On 2017-01-06 13:15:18 +0100, Guillem Jover wrote: > > > That the system probably has some unnattended async calls to a > > > command that locks the dpkg database? > > > >

Bug#850417: dpkg: error: dpkg status database is locked by another process

2017-01-10 Thread Guillem Jover
Hi! On Fri, 2017-01-06 at 13:46:14 +0100, Vincent Lefevre wrote: > On 2017-01-06 13:15:18 +0100, Guillem Jover wrote: > > On Fri, 2017-01-06 at 11:33:08 +0100, Vincent Lefevre wrote: > > > Package: dpkg > > > Version: 1.18.18 > > > Severity: grave > > > Justification: renders package unusable > >

Bug#850417: dpkg: error: dpkg status database is locked by another process

2017-01-06 Thread Vincent Lefevre
Control: severity -1 normal On 2017-01-06 13:15:18 +0100, Guillem Jover wrote: > Hi! > > On Fri, 2017-01-06 at 11:33:08 +0100, Vincent Lefevre wrote: > > Package: dpkg > > Version: 1.18.18 > > Severity: grave > > Justification: renders package unusable > > I don't think this severity is right

Bug#850417: dpkg: error: dpkg status database is locked by another process

2017-01-06 Thread Guillem Jover
Hi! On Fri, 2017-01-06 at 11:33:08 +0100, Vincent Lefevre wrote: > Package: dpkg > Version: 1.18.18 > Severity: grave > Justification: renders package unusable I don't think this severity is right here, at least for dpkg, but let's see. > When I tried to upgrade from aptitude: > > Performing

Bug#850417: dpkg: error: dpkg status database is locked by another process

2017-01-06 Thread Vincent Lefevre
On 2017-01-06 12:05:19 +0100, Vincent Lefevre wrote: [...] > 2017-01-06 11:24:38 status installed libapt-pkg5.0:amd64 1.4~beta3 > 2017-01-06 11:24:40 startup packages configure > 2017-01-06 11:24:40 trigproc libc-bin:amd64 2.24-8 > 2017-01-06 11:24:40 status half-configured libc-bin:amd64 2.24-8

Bug#850417: dpkg: error: dpkg status database is locked by another process

2017-01-06 Thread Vincent Lefevre
Some additional information... In the /var/log/dpkg.log file: 2017-01-06 11:24:37 startup archives unpack 2017-01-06 11:24:38 upgrade libapt-pkg5.0:amd64 1.4~beta2 1.4~beta3 2017-01-06 11:24:38 status triggers-pending libc-bin:amd64 2.24-8 2017-01-06 11:24:38 status half-configured

Bug#850417: dpkg: error: dpkg status database is locked by another process

2017-01-06 Thread Vincent Lefevre
Package: dpkg Version: 1.18.18 Severity: grave Justification: renders package unusable When I tried to upgrade from aptitude: Performing actions... Retrieving bug reports... Done Parsing Found/Fixed information... Done Retrieving bug reports... Done Parsing Found/Fixed information... Done