*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
dominix, thanks. I have marked the SRU as verified now.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
I want to remind everyone subscribed to this bug to please test the
fixed package and verify it.
If you get an error during the installation process (see bug 1642966),
please run the commands
sudo service cups stop
sudo apt-get install -f
sudo service cups start
in a terminal window to complete
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
Note that bug 1642966 which many people observed when updating is not
caused by the changes of this SRU (small patch removed from CUPS
daemon). So do not worry and apply the workaround shown there, should
you also run into a problem with the update. Once your installed CUPS
packages being
For everyone who is reading here as his report is added as a duplicate
of this one:
First, see my comment #2 and comment #3.
In one of the duplicates a user reported that he could solve the problem
(get new CUPS package installed) doing the following commands in a
terminal window:
sudo service
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
The SRU for Xenial (bug 1598300) is a one-line patch removal on the CUPS
daemon, the problem observed here and in many other reports is on the
shutdown of the old CUPS daemon. So it seems that some independent
change, in a not yet known package, causes problems shutting down CUPS,
but the problem
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
*** This bug is a duplicate of bug 1642966 ***
https://bugs.launchpad.net/bugs/1642966
** This bug has been marked a duplicate of bug 1642966
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
--
You received this bug
This is not caused by xenial-proposed. xenial-proposed is version
2.1.3-4ubuntu0.1 and I got tons of reports on version 2.1.3-4 which is
before xenial-proposed. So the origin must be somewhere else.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Fixed package uploaded to xenial-proposed. Please test the package as
soon as it gets available and appropriate test instructions will get
posted here. Your feedback is needed in order to make the fix an
official update for Xenial.
SRU team: debdiff attached.
** Description changed:
after 6
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/537970
Title:
Evince does not print images in some pdf
** Changed in: cups (Ubuntu)
Status: Confirmed => Invalid
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
The backslashes were caused by a bug in cups-browsed (package cups-
filters) which I have already fixed before release of 16.10. So after
once removing these entries manually, they should not show up again and
show the crash should not occur again.
But in general, CUPS has no sufficien protection
CUPS is the printing subsystem. I do not know exactly where the
Bluetooth support belongs to. Moving to the kernel ...
** Package changed: cups (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups
Your problem is not a CUPS bug but a problem with the proprietary driver
from Brother. See these lines in error_log:
D [28/Sep/2016:16:08:11 +0100] [Job 50]
/usr/lib/cups/filter/brother_lpdwrapper_DCP1610W: 103:
/usr/lib/cups/filter/brother_lpdwrapper_DCP1610W:
CUPS 2.2.0-2 is in Yakkety now. Please test whether it fixes this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1616548
Title:
Cups causes LibreOffice unittests to
** Changed in: cups (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1616548
Title:
Cups causes LibreOffice unittests to
Seb, the final patch for https://github.com/apple/cups/issues/4870 is
already backported into CUPS 2.2.0 in the cups 2.2.0-2 package in Debian
(today in the morning CEST). So now I am doing
syncpackage --force -d unstable -r yakkety-proposed cups
until I do not get
syncpackage: Error: Debian
SRU fix for Xenial is simple. In the CUPS 2.1.3 used there the upstream
bug (https://github.com/apple/cups/issues/4755) is already fixed but it
seems that the removal of the workaround patch (auto-shutdown-on-idle-
also-with-webinterface-on.patch) got forgotten. So removing this patch
seems to be
Not having "ListenStream=631" in the systemd cups.socket file is
intended. See the answer from Mike Sweet, author of CUPS:
--
First, the reason why we don't include "ListenStream=631" is because that
exposes cupsd to remote attack. And we don't listen on localhost (which has a
similar
Please follow the instructions on
https://wiki.ubuntu.com/DebuggingPrintingProblems, especially the
section "CUPS error_log".
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
What was in your /etc/cups/client.conf (now /etc/cups/client.conf_bak)?
If it pointed to a CUPS on a remote machine, all your CUPS access (from
applications/command line, not web interface) was directed to the remote
machine with a different CUPS setup. Now you are using always the CUPS
on your
I have done some tests and have found a solution. Please try it out.
Edit the file (with sudo):
/lib/systemd/system/cups.socket
adding a line
ListenStream=631
in the "[Socket]" section. The file should look like this then:
--
[Unit]
Description=CUPS Scheduler
[Socket]
I tried now the following:
till@till-x1carbon:~/printing/cups/bzr/y$ sudo systemctl stop cups
Warning: Stopping cups.service, but it can still be activated by:
cups.socket
cups.path
till@till-x1carbon:~/printing/cups/bzr/y$ ps auxwww | grep cupsd
till 4265 0.0 0.0 14224 896 pts/19
First, xinetd is not needed. systemd handles running services on-demand
well.
Important to know is that there are two access methods for CUPS:
1. The domain socket file /var/run/cups/cups.sock
2. IP Port 631
CUPS can be configured to use one of these methods or both.
Both methods can be used
Recently, CUPS in Ubuntu was configured to run on-demand, to save
resources, especially laptop or phone batteries. Perhaps one should
somehow make CUPS run permanently, perhaps as long as sbuild is doing a
build. Please try this.
--
You received this bug notification because you are a member of
I posted an upstream feature request now to improve the web interface
for CUPS running on-demand. See
https://github.com/apple/cups/issues/4874.
** Bug watch added: github.com/apple/cups/issues #4874
https://github.com/apple/cups/issues/4874
--
You received this bug notification because you
Uploaded. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fonts-android in Ubuntu.
https://bugs.launchpad.net/bugs/1621210
Title:
[MIR] fonts-android
Status in fonts-android package in Ubuntu:
Incomplete
Status
I do not find any Ghostscript with a depends/recommends/suggests on
fonts-noto-cjk. Can someone tell me which Ghostscript version? Or can
someone post a patch to switch Ghostscript to fonts-noto-cjk?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
This was simply an oversight when I tried minimize the delta between
Debian and Ubuntu, letting the new Ghostscript package be based on
Debian's with the only difference that the libopenjpeg shipped with
Ghostscript is used and not the system's one.
I can simply reapply the change to get it
Seth, this means then that this is an AppArmor bug and not a CUPS bug.
Moving ...
** Package changed: cups (Ubuntu) => apparmor (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
OdyX, Jamie, Marc, should we simply allow cupsd accessing
/etc/ld.so.preload? Or are there any security reasons against it? If
there are reasons against it, how can we silence these messages?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1598300 ***
https://bugs.launchpad.net/bugs/1598300
** This bug has been marked a duplicate of bug 1598300
cups hang after a while
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
To the developers of sbuild: If sbuild is used on a desktop machine
(which is running CUPS) and the package built inside sbuild has a
"BuildRequires: cups-daemon" making another instance of CUPS running in
sbuild's chroot, could this lead to conflicts like both CUPS daemons
claiming port 631 and
** Also affects: sbuild (Ubuntu)
Importance: Undecided
Status: New
** Changed in: sbuild (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Please follow the instructions of the section "CUPS error_log" on
https://wiki.ubuntu.com/DebuggingPrintingProblems. Thanks.
** Changed in: cups (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Are there "audit" messages in the syslog file (of the host, of the
chroot)?
Can you try to run CUPS in aa-complain mode of AppArmor?
Can you run CUPS in debug mode and supply the error_log file?
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug
Aravind, now run the following commands:
ldd /usr/lib/sane/libsane-epkowa.so.1.0.15
ldd /usr/lib/libesmod.so.2.0.0
ldd /usr/bin/iscan
ldd /usr/sbin/iscan-registry
ldd /usr/lib/gimp/2.0/plug-ins/iscan
and also attach the files:
/etc/sane.d/dll.d/iscan
/etc/sane.d/epkowa.conf
--
You received
Aravind, please run the following commands now
dpkg -L epson-inkjet-printer-201207w
dpkg -L iscan
and post the output here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
Aravind, and anyone who has scanning problems, please run the following
commands:
dpkg -l | grep -i epson
and post the output here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
Aravind, and anyone who has followed the instructions of comment #101.
Please chack the "log" file from strace again whether you generally find
lines with file paths with "epson" or "EPSON" in it. They do not need to
contain "/opt/".
Run also ldd on these file paths.
** Summary changed:
-
Everyone who is not able to scan, please try scanning as root:
sudo simple-scan
sudo scanimage ...
Does this work?
Also run
strace scanimage -L > log 2>&1
and attach the "log" file (uncompressed) to this bug report.
In the "log" file search for lines containing "epson" or "EPSON". If
they
What does not work?
Please follow the instructions on
https://wiki.ubuntu.com/DebuggingPrintingProblems
when you report printing-related bugs.
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Summary changed:
- cupds cause apparmor denials for /etc/ld.so.preload
+ cupsd cause apparmor denials for /etc/ld.so.preload
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
** Summary changed:
- Samsung printer automatically diabled; cannot print
+ Samsung printer automatically disabled; cannot print
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Looking into the error_log which got automatically attached to this bug
report, CUPS is not finding its auxiliary files, especially filters and
backends.Has the CUPS daemon access to all required directories and to
the root file system in general? Are all needed packages installed (like
Can you please attach your /var/log/syslog file? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1584367
Title:
Samsung printer automatically diabled; cannot print
*** This bug is a duplicate of bug 1579905 ***
https://bugs.launchpad.net/bugs/1579905
Note that cups-filters 1.8.3-2ubuntu3 does not contain the fix
("Requires=cups.service" in the cups-browsed.service file). So in Xenial
the bug is still there. It is tracked in bug 1579905 and there I have
Moving on this MIR to openjpeg2.
** Changed in: openjpeg (Ubuntu)
Milestone: ubuntu-16.04 => None
** Package changed: openjpeg (Ubuntu) => openjpeg2 (Ubuntu)
** Summary changed:
- [MIR] openjpeg
+ [MIR] openjpeg2
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1593013 ***
https://bugs.launchpad.net/bugs/1593013
Public bug reported:
.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 230-5
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion:
Finally, the new lsb package made it into -proposed.
Now I did suceessfully:
sudo apt-get install lsb
sudo dpkg -i epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter
ldd
Another hint:
https://bugs.linuxfoundation.org/show_bug.cgi?id=1266
Comment #2:
I've seen it. When I remember right it happened here on all systems when there
was the default setting "BrowseRemoteProtocols DNSSD,CUP" enabled.
Changing it to "BrowseRemoteProtocols DNSSD" fixes the hang at
Some more hints:
cups-browsed uses avahi-daemon for printer discovery. It does not matter
whether avahi-daemon shuts down before or after cups-browsed. If avahi-
daemon shuts down first, cups-browsed removes its queues triggered by
them going away from DNS-SD, if cups-browsed shuts down first, it
Is the fix of bug 1579905 applied? Does that fix also solve the problem
here? Or is pitti's suggestion of comment #6 also needed.
I think that pitti's approach is also important as cups-browsed needs
the network. At least on some systems it communicates with CUPS via
localhost:631 which probably
So can you post the output of
lpstat -p
then?
And can you also attach an error_log during which you have manually
enabled the printer and the printer got automatically disabled?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Unfortunately, your error_log is not capturing the execution of a job.
Is your print queue enabled and accepting jobs?
Please attach an error_log which contains the execution of a job which
did not print for you.
--
You received this bug notification because you are a member of Ubuntu
Touch
Now with the printer detected and set up but not printing I would need
error_log again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1584367
Title:
Samsung printer
Please go to
https://wiki.ubuntu.com/DebuggingPrintingProblems
and follow the instructions of the section "Printer detection"/"USB
printer" and post the results here.
Also run the command
sudo lsusb -vvv 2>&1 | tee lsusb-vvv.log
in a terminal and attach the output file.
Do not compress any
I see that you access the printer through the URI
lpd://localhost
meaning that an LPD server (port 515) must be on your local machine. Are
you running some daemon on your machine to access the printer via a
proprietary communication protocol? Some software you got somehow from
Samsung (download
When one looks at
https://launchpad.net/ubuntu/+source/lsb/9.20160110ubuntu0.1
the builds on all platforms got completed correctly, but it seems to
have gotten stuck right after that, as under "Binary Packages" near the
bottom there is nothing.
--
You received this bug notification because you
Arup, the new lsb packages indeed did not make it yet into -proposed.
They need to get approved by the SRU team. When this is done (can take
some days) an announcement is posted here asking for testing the
packages.
--
You received this bug notification because you are a member of Ubuntu
Touch
When the call for verification of this SRU is announced in this bug
report, the package is in -proposed. You add -proposed and do
sudo apt-get install lsb
sudo apt-get install lsb-printing
Don't worry if the second gives an error, but please tell us if so.
After that remove -proposed again so
Arup, yes, you will not need the Trusty repos any more.
If you want to verify this SRU, make sue that when you add xenial-
proposed that you remove all Trusty repos.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in
Thomas, probably it is possible to build FF and TB with the system's
libcairo. I do not know why the maintainers of these packages stick to
stone-old libraries which have many bugs which are already fixed in the
current version.
But I will not do this fix as I am not the maintainer of FF and TB.
Public bug reported:
.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 230-2git1
ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
Date: Wed Jun 15 08:48:24 2016
ExecutablePath:
Public bug reported:
.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 230-2git1
ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Mon Jun 13 15:58:37 2016
Fails also, but at a later point:
https://launchpadlibrarian.net/265602766/buildlog_ubuntu-yakkety-
ppc64el.krb5_1.14.2+dfsg-1ubuntu1+ppa4_BUILDING.txt.gz
What you need to do is the following:
Build the package on the system which you have at hand (amd64, i386,
...), directing the build output
With your last debdiff I was able to generate a source package which I
have uploaded to my PPA (ppc64el activated before) but it still does not
build on ppc64el. Here is the build log:
https://launchpad.net/~till-
kamppeter/+archive/ubuntu/ppa/+build/10024486/+files/buildlog_ubuntu-
yakkety
Sam, your debdiff does not work this way. You have directly edited the
upstream code instead of creating a patch in debian/patches/. Can you do
a new debdiff with a proper patch for your change? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I tried to replace the -O3 in the CFLAGS by -O2, by adding
DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
ifeq ($(DEB_HOST_ARCH),ppc64el)
export DEB_CFLAGS_MAINT_STRIP = -O3
export DEB_CFLAGS_MAINT_APPEND = -O2
endif
to debian/rules near the beginning, as it was done in the
701 - 800 of 1091 matches
Mail list logo
