Olá, desde já muito obrigado pela atenção pois eu fiz uma atualização do
Ubuntu para a versão 17.04 desde já muito obrigado pela ajuda.
Em 20 de nov de 2017 6:21 AM, "Tinku Girdhar"
escreveu:
> Sure
> anuragjha1...@gmail.com
> You can refer to him
>
> On 20-Nov-2017 5:11
Sure
anuragjha1...@gmail.com
You can refer to him
On 20-Nov-2017 5:11 AM, "andrew buffa" <1642...@bugs.launchpad.net>
wrote:
> thank you very much
>
> Happy Thanksgiving
>
> ANDREW . . .
> On 11/19/2017 03:57 PM, caj411 wrote:
> > not if you backup and restore your home directory OR have it on a
thank you very much
Happy Thanksgiving
ANDREW . . .
On 11/19/2017 03:57 PM, caj411 wrote:
> not if you backup and restore your home directory OR have it on a separate
> partition.
>
> On Sun, Nov 19, 2017 at 3:30 PM andrew buffa <1642...@bugs.launchpad.net>
> wrote:
>
>> can you direct me to
not if you backup and restore your home directory OR have it on a separate
partition.
On Sun, Nov 19, 2017 at 3:30 PM andrew buffa <1642...@bugs.launchpad.net>
wrote:
> can you direct me to someone who would know?
>
> ANDREW . . .
> On 11/19/2017 03:12 PM, Tinku Girdhar wrote:
> > I don't know.
can you direct me to someone who would know?
ANDREW . . .
On 11/19/2017 03:12 PM, Tinku Girdhar wrote:
> I don't know.
>
> On 20-Nov-2017 12:01 AM, "andrew buffa" <1642...@bugs.launchpad.net>
> wrote:
>
>> I have a question
>>
>> if I were to re-install ubuntu would it delete my existing e-mails?
I don't know.
On 20-Nov-2017 12:01 AM, "andrew buffa" <1642...@bugs.launchpad.net>
wrote:
> I have a question
>
> if I were to re-install ubuntu would it delete my existing e-mails?
>
>
> ANDREW . . .
> On 08/31/2017 08:22 AM, Launchpad Bug Tracker wrote:
> > This bug was fixed in the package
I have a question
if I were to re-install ubuntu would it delete my existing e-mails?
ANDREW . . .
On 08/31/2017 08:22 AM, Launchpad Bug Tracker wrote:
> This bug was fixed in the package cups - 2.1.3-4ubuntu0.3
>
> ---
> cups (2.1.3-4ubuntu0.3) xenial; urgency=high
>
>* Adding
This bug was fixed in the package cups - 2.1.3-4ubuntu0.3
---
cups (2.1.3-4ubuntu0.3) xenial; urgency=high
* Adding maintainer script debian/cups-daemon.prerm to deal with situations
where "old-version" (installed package) prerm script fails. (LP: #1642966).
cups
I am able to install virtual box at Ubuntu now. I am not sure what was
update. This bug is related to any of my request ?
Thanks,
Sharad
On Thu, Aug 24, 2017 at 10:49 AM, Mateusz Pawlowski <
1642...@bugs.launchpad.net> wrote:
> I've tested upgrading cups-daemon package to version
** Tags removed: patch regression-proposed verification-needed
verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
I've tested upgrading cups-daemon package to version 2.1.3-4ubuntu0.3 on
KVM, LXD and Virtualbox and I haven't found any issues so far.
Testbed specs:
1. KVM - Xenial 16.04 / qemu-system-x86 1:2.5+dfsg-5ubuntu10.14
2. LXD - Xenial 16.04 / lxd 2.0.10-0ubuntu1~16.04.1
3. Virtualbox - Xenial 16.04 /
I've tested upgrading cups-daemon package to version 2.1.3-4ubuntu0.3 on
KVM, LXD and Virtualbox and I haven't found any issues so far.
Testbed specs:
1. KVM - Xenial 16.04 / qemu-system-x86 1:2.5+dfsg-5ubuntu10.14
2. LXD - Xenial 16.04 / lxd 2.0.10-0ubuntu1~16.04.1
3. Virtualbox - Xenial 16.04
** Description changed:
This concerns only Xenial (16.04)!
[Impact]
* fail to upgrade
[testcase]
Root cause is believed to be reproducible with:
#!/bin/bash
systemctl stop cups.path cups.service
rm /var/cache/cups/org.cups.cupsd
systemctl start cups.path
touch
On Wed, Aug 23, 2017 at 02:54:51PM -, Till Kamppeter wrote:
> About the c2esp regressio mentioned in the description (see also below):
> It seems that c2esp never built/worked on arnhf. I see this also with
> several other printing-related packages (like cups-filters). So you can
> safely
** Description changed:
This concerns only Xenial (16.04)!
[Impact]
* fail to upgrade
[testcase]
Root cause is believed to be reproducible with:
#!/bin/bash
systemctl stop cups.path cups.service
rm /var/cache/cups/org.cups.cupsd
systemctl start cups.path
touch
** Description changed:
This concerns only Xenial (16.04)!
[Impact]
* fail to upgrade
[testcase]
Root cause is believed to be reproducible with:
#!/bin/bash
systemctl stop cups.path cups.service
rm /var/cache/cups/org.cups.cupsd
systemctl start cups.path
touch
About the c2esp regressio mentioned in the description (see also below):
It seems that c2esp never built/worked on arnhf. I see this also with several
other printing-related packages (like cups-filters). So you can safely ignore
it.
--
Regression found in pending SRU page :
*
** Description changed:
This is in xenial-proposed, please block release to -updates accordingly
:)
[Impact]
* fail to upgrade
[testcase]
Root cause is believed to be reproducible with:
#!/bin/bash
systemctl stop cups.path cups.service
rm /var/cache/cups/org.cups.cupsd
Hello Mark, or anyone else affected,
Accepted cups into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The patch has been uploaded in the xenial upload queue.
It is now waiting for the SRU verification team approval for the CUPS
derived binary packages to start building in xenial-proposed and re-
enter in the users test phase.
- Eric
--
You received this bug notification because you are a
Here's a debdiff[1] that I have tested and mitigate the situation with
the reproducer using VirtualBox.
The proposal patch integrate a custom "debian/cups-daemon.prerm"
maintainer script in case the pre-removal "old-version" from the
installed package fails (as seen using the above reproducer)
** Patch removed: "lp1642966_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+attachment/4934838/+files/lp1642966_xenial.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
lp1642966_xenial.debdiff
** Patch added: "lp1642966_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+attachment/4934838/+files/lp1642966_xenial.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups
@iiro,
I just uploaded a new version of the test package a few minutes ago...
Please make sure when you will give the PPA a try that you are upgrading
to "2.1.3-4ubuntu0.3+test1" version.
- Eric
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hi iiro,
Could you please give it a try with the following test package I have
prepare for you :
sudo add-apt-repository ppa:slashd/cupsupgrade
sudo apt-get update
Use the same exact reproducer but instead of upgrading from xenial-
proposed like you normally do, please upgrade from this PPA.
If I manually stop or stop/start cups.socket & cups.path, then
cups.service is stopping successfully, and I can now proceed with the
cups upgrade on a broken system.
With that being said, this could be a good workaround for Xenial users
blocked by this situation.
systemctl stop cups.socket
On a broken VirtualBox system, if I perform ;
systemctl stop cups.service
I got the following message : "Job for cups.service canceled."
Obviously, cups remain started with same PID, so no effect on the stop
action requested.
Exactly as during the package upgrade.
On the other side, syslog
Using Desktop image on KVM :
--
Log started: 2017-08-08 14:07:24
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
Using Desktop image on VirtualBox :
--
Log started: 2017-08-10 10:07:00
(Reading database ... ^M(Reading database ... 5%^M(Reading database ...
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database
... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading
@iiro,
I was able to reproduce the situation (explained in comment #111) ONLY
using virtualbox.
To recap :
- Desktop image using KVM: Success # Same result for iiro and I
- Xenial image using LXC: Success
- Server image using KVM: Success
- Desktop image using
@iiro,
That is interesting ...
To recap using KVM you can't reproduce the situation (just like me) that
you are experience using virtualbox ... so we are on the same page about
not being able to reproduce using LXC nor KVM, but you can reproduce it
if using virtualbox.
I'll give it a try this
Here's the relevant journalctl log on VirtualBox. It complains something
about colord. "Laitetta tai osoitetta ei ole" means "No such device or
address".
elo 09 20:32:09 il-VirtualBox colord[1431]: (colord:1431): Cd-WARNING **:
failed to get session [pid 3130]: Laitetta tai osoitetta ei ole
elo
On Wed, Aug 09, 2017 at 04:28:43PM -, Iiro Laiho wrote:
> Cannot reproduce. Maybe this has something to do with VirtualBox.
Sounds like a race.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
After talking with slashd, I did my own experiment in the same way I did
with virtualbox, but this time I used virt-manager and KVM instead.
Cannot reproduce. Maybe this has something to do with VirtualBox.
--
You received this bug notification because you are a member of Desktop
Packages, which
I tried the same exact reproducer (as described by iiro) using different
scenarios such as :
- Server image inside LXC and KVM guest
- Server image inside KVM guest
- Desktop image inside a KVM guest
and every time it worked well for me without any issue.
- Eric
--
You received this bug
Here are log entries that result from the "sudo apt -t xenial-proposed
install cups-daemon"
Preparing to unpack .../libcupsppdc1_2.1.3-4ubuntu0.2_amd64.deb ...
Unpacking libcupsppdc1:amd64 (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../libcupsmime1_2.1.3-4ubuntu0.2_amd64.deb ...
The last step in #109 is important. When doing the upgrade of cups-
daemon, it may look like it succeeded but with warnings. However, the
packaging system does break down and will became unable to successfully
do "apt upgrade".
--
You received this bug notification because you are a member of
Nope, the problem is still present in -proposed. Here's a more detailed
procedure of reproducing the bug:
- Do a clean Ubuntu install. I installed Ubuntu from the 16.04.3 desktop media
to a VirtualBox VM.
- Do a "apt update && apt upgrade" as usual
- Per the instructions from
@iiro, yes I tried your reproducer a couple of time without success.
- Clean Ubuntu install
- Install updates
- Enable -proposed
- Make sure that cupsd is running with stuck job using an invalid printer IP
--
▼ ID ▼ NameUserSizePages State Control
Bug1642966-1Unknown
@slashd, Maybe something has changed in systemd or something? I'll check
it out sometime when I have time.
Did you make a clean install? How did you ensure that the job was stuck
in the queue? I remember that adding a socket:// printer with an invalid
address did the trick.
--
You received this
I tried to reproduce on my side using the reproducer explain in comment
#98 and #99, and I couldn't reproduce it.
@xnox
Since foundation know how to fix it, can we try to fixing it blind for
now ? Upload in xenial-proposed, and wait for users feedbacks ?
If something goes wrong, we can still
Comment #98 seems to be a good recipe to reproduce the actual problem
here. Also have a look at the comments afterwards.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
Suggested fix (and AFAIR it is the one working in Yakkety and Zesty) is
in comment #52. Reproducers are in comment #18, comment #21, and comment
#37. I do not know why this does not work in Xenial.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hi,
After some discussions with xnox and tkamppeter, here's a summary of the
situations for this particular bug.
The foundation team know how to fix this issue, but so far they do not
have a broken system to test the fixes on, before uploading, thus not
reproducer.
We basically needs someone
Wie kann ich als Anfänger den Schaden beheben?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
The root cause of this problem is probably that the "invoke-rc.d cups
stop" command fails on Xenial if there are jobs in queue. The dpkg
preremoval script runs that command and thus the upgrade procedure
fails. In the newer Ubuntu versions the command executes flawlessly.
Until that problem is
Sorry, the "Make sure that cupsd is running" part should apparently be
"Make sure there is a stuck job in cups"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package
I have concluded that this problem only appears if the -proposed package
has never been installed AND cupsd is running.
So, the way to reproduce this is:
- Do a clean Ubuntu install
- Install updates
- Enable -proposed
- Make sure that cupsd is running
- Update cups-daemon.
When I do this, the
till-kamppeter, what do you mean by "restarting systemd"? Does it mean
that we could try adding something like this to the postinstall script:
"if dpkg --compare-versions "$2" lt-nl "2.1.3-4ubuntu0.2"; then
systemctl daemon-reexec
fi"?
Does it belong inside of the "if [ "$1" = configure ]"
The bug appeared only once as Till Kamppeter wrote on 2017-03-28 after
updating cups-daemon on a clean Ubuntu installation. Until there all of
the proposed updates were made. The printers installed on the system do
their work.
--
You received this bug notification because you are a member of
So, what would be a reliable way to reproduce the problem?
Should the following sequence always trigger this issue:
- Do a clean Ubuntu install
- Install updates
- Enable -proposed
- Update cups-daemon?
--
You received this bug notification because you are a member of Desktop
Packages, which
** Changed in: cups (Ubuntu Xenial)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon 2.1.3-4 failed to
Changed xenial status by error, should be 'Triaged'. Can't change it
back, sorry :(
** Changed in: cups (Ubuntu Xenial)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
A problem of this bug seems to be that it occurs only once for each
user. So a user who observed in in the first place will not observe it
again when it comes to verification of the SRU. So the SRU gets verified
even without the bug actually fixed. The complaints after the SRU having
put into
It's all started when I tried to install Dropbox 64bit deb package from
their website.Two systems got effected in same manner.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
xnox, a possible cause can be that when the old package is removed
before the update, the shutdown is perhaps made with the old systemd
service files (which do not contain the fix). So probably additional
methods, like explicitly deactivating cups.path, or at least restarting
systemd need to get
I forced the update with sudo apt-get -f upgrade and it worked, so I guess
its a mute point. thanks
On Mon, Mar 27, 2017 at 2:41 PM Till Kamppeter <1642...@bugs.launchpad.net>
wrote:
> xnox, your fixed package actually contains the fix we agreed on to apply
> and it even seems to work in the
xnox, your fixed package actually contains the fix we agreed on to apply
and it even seems to work in the newer Ubuntu versions Yakkety and
Zesty, but seems not to work in Xenial. Do you have any idea what is
happening here? Perhaps a bug in systemd?
--
You received this bug notification because
** Description changed:
This is in xenial-proposed, please block release to -updates accordingly
:)
[Impact]
* fail to upgrade
[testcase]
Root cause is believed to be reproducible with:
#!/bin/bash
systemctl stop cups.path cups.service
rm /var/cache/cups/org.cups.cupsd
This appears not yet fixed in Xenial in 2.1.3-4ubuntu0.2. After
releasing 2.1.3-4ubuntu0.2 we got further reports that I'm duping to bug
1676380.
** Changed in: cups (Ubuntu Xenial)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Desktop
Before getting to here, I did sudo apt-get -f install , but there
are the log files:
error_log 0 byte
error_log.1291 bytes
E [23/Mar/2017:11:22:34 -0300] [cups-deviced] PID 4786 (gutenprint52+usb)
stopped with status 1!
E [24/Mar/2017:10:13:07 -0300] [cups-deviced] PID 3065
** Changed in: cups (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon 2.1.3-4 failed to
** Changed in: cups (Ubuntu Yakkety)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
** Changed in: cups (Ubuntu Xenial)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
The package that was just SRU'ed caused this very error. Apport-info in
LP: #1676380
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon 2.1.3-4 failed to
desculpe mas eu removi o sistema e coloquei outro sistema
2017-03-27 4:22 GMT-03:00 Robie Basak <1642...@bugs.launchpad.net>:
> Looks like you verified Xenial but not Yakkety? Not a problem and we
> appreciate your testing; just adjusting the tags so we don't
> accidentally release an untested
This bug was fixed in the package cups - 2.1.3-4ubuntu0.2
---
cups (2.1.3-4ubuntu0.2) xenial; urgency=medium
* Make cups.path unit be part of the cups.service, since cups.path
should stop if and when cups.service is stopped. LP: #1642966
-- Dimitri John Ledkov
Looks like you verified Xenial but not Yakkety? Not a problem and we
appreciate your testing; just adjusting the tags so we don't
accidentally release an untested Yakkety.
** Tags removed: verification-done
** Tags added: verification-done-xenial
--
You received this bug notification because
Also, the test case in the bug report seems to return 0 unless there is
a job in queue. That job does not however affect the update process, so
I'll put verification-done to this.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because
I ran this test. The machine was a 64-bit Ubuntu 16.04.2 on a VirtualBox
VM. Before running the command I enabled -proposed and ensured that CUPS
will not shut down by having a stuck job in the queue. The upgrade
completed correctly.
Console output of the "apt update && apt install cups-daemon"
Note that this bug is only a problem of the package installation
process. So it is fixed (or not reproducible) if you install the
proposed package and the installation does not error. There is no
difference between before and after on the system's behavior.
--
You received this bug notification
Just to clarify why this bug has so many me-too votes: the bug happened
once to me, during an update, and never happened again (i.e. it fixed
itself, and I can print just fine, etc.). I subscribed to this thread
because I was curious as to what was going on, and I did see the problem
myself once
This bug report got 418 (!) me-too votes and has tons of duplicates and
no one wants to verify the proposed fix? Please, come up, install the
proposed package and see whether it installs smoothly without hick-up
and give us your feedback here. You will help a lot of people if your
feedback makes
And we are on 419 me-too votes now! So who ever has voted now, please
try the proposed fix! Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon
Brian:
how do I fix with no internet connection
the last update disconnected it
Andrew
On 2/16/2017 2:43 PM, Brian Murray wrote:
> Hello Mark, or anyone else affected,
>
> Accepted cups into xenial-proposed. The package will build now and be
> available at
Hello Mark, or anyone else affected,
Accepted cups into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Mark, or anyone else affected,
Accepted cups into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cups/2.2.0-2ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
@blacksheep001: Sorry, but this is a bug tracker, not a support forum.
Please take your question about lost Internet connectivity for example
to the Ubuntu forums (http://ubuntuforums.org/), maybe they can help
there.
--
You received this bug notification because you are a member of Desktop
Hello
I'm a newbie
how do I fix this?
after the failed install, I no longer have internet access for the past
two weeks
Andrew
On 2/11/2017 6:36 AM, Iiro Laiho wrote:
> Added patch tag because there is a patched PPA linked in comment #61.
>
> ** Tags added: patch
>
---
This email has been
Added patch tag because there is a patched PPA linked in comment #61.
** Tags added: patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon 2.1.3-4
The change is already done since the package was updated to the lastest
upstream version.
** Changed in: cups (Ubuntu Zesty)
Status: Triaged => Fix Released
** Changed in: cups (Ubuntu Zesty)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug notification
I dont know
03.02.2017 18:31, andrew buffa пишет:
> I'm a newbie
>
> how do I do that & why/how does the printer affect internet connection?
>
> Andrew
> On 2/2/2017 10:31 PM, rusbunker wrote:
>> yes. I purge driver of printer and reinstall it again. That all.
>> Everything ok.
>>
>>
>>
I'm a newbie
how do I do that & why/how does the printer affect internet connection?
Andrew
On 2/2/2017 10:31 PM, rusbunker wrote:
> yes. I purge driver of printer and reinstall it again. That all.
> Everything ok.
>
>
> 03.02.2017 00:37, andrew buffa пишет:
>> how do I fix?
>>
>> I now have no
yes. I purge driver of printer and reinstall it again. That all.
Everything ok.
03.02.2017 00:37, andrew buffa пишет:
> how do I fix?
>
> I now have no internet connection
>
> am using a backup pc
>
> Andrew
> On 1/31/2017 11:56 PM, rusbunker wrote:
>> Дмитрий добрый день! Я правильно понимаю
how do I fix?
I now have no internet connection
am using a backup pc
Andrew
On 1/31/2017 11:56 PM, rusbunker wrote:
> Дмитрий добрый день! Я правильно понимаю что если выполню инструкции
> прописанные в этом сообщении, я получу желаемое? А именно устновлю принтер.
>
>
> 31.01.2017 13:33,
Дмитрий добрый день! Я правильно понимаю что если выполню инструкции
прописанные в этом сообщении, я получу желаемое? А именно устновлю принтер.
31.01.2017 13:33, Dimitri John Ledkov пишет:
> ** Changed in: cups (Ubuntu Zesty)
> Milestone: ubuntu-17.01 => ubuntu-17.02
>
--
You received
** Changed in: cups (Ubuntu Zesty)
Milestone: ubuntu-17.01 => ubuntu-17.02
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon 2.1.3-4 failed to
xnox, if you make an SRU for this bug, can you merge it with the SRU for
bug 1598300. Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon 2.1.3-4
** Changed in: cups (Ubuntu Zesty)
Milestone: ubuntu-16.12 => ubuntu-17.01
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon 2.1.3-4 failed to
Thx
On Dec 22, 2016 12:01 PM, "Dimitri John Ledkov"
wrote:
> ** Description changed:
>
> This is in xenial-proposed, please block release to -updates accordingly
> :)
> +
> + [Impact]
> + * fail to upgrade
> +
> + [testcase]
> + Root cause is believed to be
SRU is uploaded into bileto silo at
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2323/+packages
Bileto details at https://bileto.ubuntu.com/#/ticket/2323
It is an ephemeral PPA which will be removed after this SRU is
published.
One can test this proposed update by enabling it
Upstream bug
https://github.com/apple/cups/issues/4935
is fixed now, the fix will be in upstream CUPS from version 2.2.2 on.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Changed in: init-system-helpers (Ubuntu)
Status: Confirmed => Invalid
** Changed in: cups (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: cups (Ubuntu)
Milestone: None =>
** Description changed:
This is in xenial-proposed, please block release to -updates accordingly
:)
+
+ [Impact]
+ * fail to upgrade
+
+ [testcase]
+ Root cause is believed to be reproducible with:
+
+ #!/bin/bash
+ systemctl stop cups.path cups.service
+ rm /var/cache/cups/org.cups.cupsd
xnox, I think that your suggestion of a generator in comment #57 makes
things too complicated. The "PartOf=cups.service" solution works just
fine.
But could you prepare a debdiff and/or PPA package implementing your
suggestion of comment #58? Thanks.
--
You received this bug notification
On 20 December 2016 at 21:39, Till Kamppeter <1642...@bugs.launchpad.net> wrote:
> xnox, it seems that the suggested fix of comment #52 is the solution for
> this bug, and I could at any time add a patch to the CUPS package and
> issue it as an SRU. Only problem is, if I do only this, will the SRU
On 21 December 2016 at 08:13, Martin Pitt wrote:
>
> Till Kamppeter [2016-12-19 16:48 -]:
> > Then edit the file /lib/systemd/system/cups.path adding a line
> > "PartOf=cups.service" to the [Unit] section, so that the file looks like
> > this:
> >
> > --
> >
Till Kamppeter [2016-12-19 16:48 -]:
> Then edit the file /lib/systemd/system/cups.path adding a line
> "PartOf=cups.service" to the [Unit] section, so that the file looks like
> this:
>
> --
> [Unit]
> Description=CUPS Scheduler
> PartOf=cups.service
I suppose that cups.path is only
xnox, it seems that the suggested fix of comment #52 is the solution for
this bug, and I could at any time add a patch to the CUPS package and
issue it as an SRU. Only problem is, if I do only this, will the SRU
smoothly install? Or are additional measures required?
--
You received this bug
Reported the suggested solution of comment #52 to CUPS upstream as
https://github.com/apple/cups/issues/4935
The change will get applied in the next release of CUPS (2.2.2, in
January).
** Bug watch added: github.com/apple/cups/issues #4935
https://github.com/apple/cups/issues/4935
--
You
Editing /lib/systemd/system/cups.path as instructed in post #52 above
has resolved the issue on my 16.04 LTS install.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
1 - 100 of 155 matches
Mail list logo