[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#817748: marked as done (cups-daemon will not fully install )

Your message dated Mon, 1 Jan 2018 18:01:41 +0000
with message-id <01012018175102.52dccf1b62df@desktop.copernicus.org.uk>
and subject line Re: Bug#817748: cups-daemon will not fully install
has caused the Debian Bug report #817748,
regarding cups-daemon will not fully install 
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
817748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817748
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cups-daemon
Version : cups-daemon_1.7.5-11+deb8u1_amd64.deb
System : amd64: Jessie

Hi, maintainers

The text below is self-evident
###########################################################
# apt-get install --reinstall cups-daemon
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 42 not upgraded.
Need to get 0 B/375 kB of archives.
After this operation, 0 B of additional disk space will be used.
Selecting previously unselected package cups-daemon.
(Reading database ... 305047 files and directories currently installed.)
Preparing to unpack .../cups-daemon_1.7.5-11+deb8u1_amd64.deb ...
Failed to stop cups.path: Unit cups.path not loaded.
dpkg: warning: subprocess old pre-removal script returned error exit status 5
dpkg: trying script from the new package instead ...
Failed to stop cups.path: Unit cups.path not loaded.
dpkg: error processing archive /var/cache/apt/archives/cups-daemon_1.7.5-11+deb8u1_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 5
/usr/bin/deb-systemd-helper: error: unable to read cups.service
/usr/bin/deb-systemd-helper: error: unable to read cups.socket
/usr/bin/deb-systemd-helper: error: unable to read cups.path
Failed to start cups.path: Unit cups.path failed to load: No such file or directory.
Errors were encountered while processing:
 /var/cache/apt/archives/cups-daemon_1.7.5-11+deb8u1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
###################################################################

The present system was restored after a motherboard failed. 
There may be some legacy problems from the old system. 

I had a look at 
Debian Bug report logs - #814340
as that seemed closest to this problem. 

I have files in /var/spool/cups

I looked for /lib/systemd/system/cups.path
there was no file, nor cups.service cups.socket 
# find / -name 'cups.path' reports this 
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups.path

And # apt-get install cups-daemon
Reading package lists... Done
Building dependency tree       
Reading state information... Done
cups-daemon is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 42 not upgraded.

regards

richard

--- End Message ---
--- Begin Message --- 
Thank you for your report, info2014.

On Wed 09 Mar 2016 at 20:59:18 +0000, info2014@mail.sheugh.com wrote:

> Package: cups-daemon
> Version : cups-daemon_1.7.5-11+deb8u1_amd64.deb
> System : amd64: Jessie
> 
> Hi, maintainers
> 
> The text below is self-evident
> ###########################################################
> # apt-get install --reinstall cups-daemon
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 42 not upgraded.
> Need to get 0 B/375 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> Selecting previously unselected package cups-daemon.
> (Reading database ... 305047 files and directories currently installed.)
> Preparing to unpack .../cups-daemon_1.7.5-11+deb8u1_amd64.deb ..

Ok up to here.
.
> Failed to stop cups.path: Unit cups.path not loaded.
> dpkg: warning: subprocess old pre-removal script returned error exit status 5
> dpkg: trying script from the new package instead ...
> Failed to stop cups.path: Unit cups.path not loaded.
> dpkg: error processing archive /var/cache/apt/archives/cups-daemon_1.7.5-11+deb8u1_amd64.deb (--unpack):
>  subprocess new pre-removal script returned error exit status 5
> /usr/bin/deb-systemd-helper: error: unable to read cups.service
> /usr/bin/deb-systemd-helper: error: unable to read cups.socket
> /usr/bin/deb-systemd-helper: error: unable to read cups.path
> Failed to start cups.path: Unit cups.path failed to load: No such file or directory.

I have had occasion to reinstall cups-daemon on unstable quite a few
times over the past couple of weeks and never encountered anything like
this. Why it is impossible to read the systemd files is beyond me.

> Errors were encountered while processing:
>  /var/cache/apt/archives/cups-daemon_1.7.5-11+deb8u1_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> ###################################################################
> 
> The present system was restored after a motherboard failed. 
> There may be some legacy problems from the old system. 

Whatever the cause I'd say it did not lie with the printing system.

> I had a look at 
> Debian Bug report logs - #814340
> as that seemed closest to this problem. 

A different bug.

> I have files in /var/spool/cups
> 
> I looked for /lib/systemd/system/cups.path
> there was no file, nor cups.service cups.socket 
> # find / -name 'cups.path' reports this 
> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups.path
> 
> And # apt-get install cups-daemon
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> cups-daemon is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 42 not upgraded.

After this length of time you will have moved on and the effort of
investigating the cause will not benefit either of us. Therefore I
am closing the report.

Regards,

Brian.

--- End Message ---
Reply to: