|
Home > Archive > Linux Debian support > July 2006 > E: Sub-process /usr/bin/dpkg returned an error code (1)
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
E: Sub-process /usr/bin/dpkg returned an error code (1)
|
|
|
| Can some kind person tell me what this means and how to correct it? I
have searched for answers in the Google archives and tried to find a
solution using my limited knowledge to no avail.
I am using the latest version of GenieOS, formerly known as Debian Pure.
--
A Bitey Copyleft Production ;p~~~
| |
| Bill Marcum 2006-07-20, 7:21 am |
| On Wed, 19 Jul 2006 18:33:59 -0700, Bitey
<bitey@batcave.rafters> wrote:
> Can some kind person tell me what this means and how to correct it? I
> have searched for answers in the Google archives and tried to find a
> solution using my limited knowledge to no avail.
>
This message is usually caused by an error in a package install or
remove script. The scripts are found in
/var/lib/dpkg/info/packagename.*
> I am using the latest version of GenieOS, formerly known as Debian Pure.
>
If you are using a testing or unstable version, you may have to wait a
few days for a bug fix. Or if you can find the script that causes the
error, you could insert an "exit 0".
--
You don't have to wait--you can have it in 5.004_54 or so. :-)
-- Larry Wall in <199710221740.KAA24455@wall.org>
| |
|
| Bill Marcum wrote this gem. Seriously... :
> On Wed, 19 Jul 2006 18:33:59 -0700, Bitey
> <bitey@batcave.rafters> wrote:
> This message is usually caused by an error in a package install or
> remove script. The scripts are found in
> /var/lib/dpkg/info/packagename.*
>
> If you are using a testing or unstable version, you may have to wait a
> few days for a bug fix. Or if you can find the script that causes the
> error, you could insert an "exit 0".
Thank you for your reply. I have narrowed it down to an error while
installing the following:
The following NEW packages will be installed:
samba samba-common samba-dbg
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get
6591kB/11.1MB of archives. After unpacking 40.4MB of additional disk space
will be used. Get:1 http://security.debian.org stable/updates/main
samba-dbg 3.0.14a-3sarge2 [6591kB] Fetched 6591kB in 37s (176kB/s)
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
another process (Reading database ... dpkg: error processing
/var/cache/apt/archives/samba-common_3.0.14a-3sarge2_i386.deb (--unpack):
files list file for package `samba' contains empty filename
Errors were encountered while processing:
/var/cache/apt/archives/samba-common_3.0.14a-3sarge2_i386.deb
Processing was halted because there were too many errors. E: Sub-process
/usr/bin/dpkg returned an error code (1) RESULT=100
The line that starts with 'debconf: DbDriver "config":' has me stumped.
Locked by another process?? Can you (or anyone) shed some light on how I
would find out which process is locked and why?
--
A Bitey Copyleft Production ;p~~~
| |
|
| Bitey wrote this gem. Seriously... :
> Bill Marcum wrote this gem. Seriously... :
>
>
> Thank you for your reply. I have narrowed it down to an error while
> installing the following:
>
> The following NEW packages will be installed:
> samba samba-common samba-dbg
> 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get
> 6591kB/11.1MB of archives. After unpacking 40.4MB of additional disk space
> will be used. Get:1 http://security.debian.org stable/updates/main
> samba-dbg 3.0.14a-3sarge2 [6591kB] Fetched 6591kB in 37s (176kB/s)
> debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
> another process (Reading database ... dpkg: error processing
> /var/cache/apt/archives/samba-common_3.0.14a-3sarge2_i386.deb (--unpack):
> files list file for package `samba' contains empty filename
> Errors were encountered while processing:
> /var/cache/apt/archives/samba-common_3.0.14a-3sarge2_i386.deb
> Processing was halted because there were too many errors. E: Sub-process
> /usr/bin/dpkg returned an error code (1) RESULT=100
>
> The line that starts with 'debconf: DbDriver "config":' has me stumped.
> Locked by another process?? Can you (or anyone) shed some light on how I
> would find out which process is locked and why?
Addendum: Nevermind, thanks anyway, I decided to reinstall and be more
careful about what I install as extras.
--
A Bitey Copyleft Production ;p~~~
|
|
|
|
|