As 13.10 is well past End of Life, I am marking this as "Incomplete".
If this is able to be reproduced in exactly the same way on 14.04 or any
other later supported release, please make a comment to that effect.
** Changed in: nginx (Ubuntu)
Status: Confirmed => Incomplete
--
You received
Hello.
It looks like your init script has a syntax error on it. If this is
still a problem, then please include the /etc/init.d/nginx script and
attach it to this bug. The error indicates that /etc/init.d/nginx has a
lot of things it shouldn't have in it, which would explain why it's
failing to
Related backport bug:
https://bugs.launchpad.net/trusty-backports/+bug/1448823 - swig3.0
backport request.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444943
Title:
trusty backport to remove ssl
NOTE: This bug is also not the correct method for requesting a backport.
I'll handle the backport requests for ZNC and related dependencies
(pending Backports team requests), however you should read
https://wiki.ubuntu.com/UbuntuBackports for the future, Anton.
--
You received this bug notificat
Related Security bug:
https://bugs.launchpad.net/ubuntu/+source/znc/+bug/1389264
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444943
Title:
trusty backport to remove sslv3
To manage notifications
Additional considerations:
Backport of ZNC from Vivid to Trusty would also need testing on Utopic.
Tests will need to be done as part of backport testing, however Bug
#1448823 is the prerequisite before any ZNC backport testing is done.
--
You received this bug notification because you are a mem
Mikaela: See https://bugs.launchpad.net/ubuntu/+source/znc/+bug/1444943
for the (start) of work to get ZNC 1.6.0 into trusty-backports and
utopic-backports. While this doesn't fully address the Security bug, it
does provide the 1.6.0 functionality via the backports repository.
--
You received t
*** This bug is a duplicate of bug 1449248 ***
https://bugs.launchpad.net/bugs/1449248
** This bug has been marked a duplicate of bug 1449248
Please backport znc 1.6.0-2 (universe) from vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Public bug reported:
This is an issue that I have confirmed in ZNC 1.6.
When a module is being compiled by znc-buildmod as part of znc-dev, and
relies on unicode support or any functions provided by the icu source
package (and libicu-dev), the modules will fail to build since the
`libicu-dev` pac
** Bug watch added: Debian Bug tracker #783546
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783546
** Also affects: znc (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783546
Importance: Unknown
Status: Unknown
--
You received this bug notification because you a
If this is not specific to NGINX there needs to be additonal bugs opened
against the other projects. This bug will only address NGINX.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413555
Title:
i
This bug is in the same state as
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1447294 - it is
missing information necessary for identification of the problem.
Please include output of the following commands:
systemctl status nginx.service
journalctl -xe
Also provide the output of `sudo ng
** Changed in: nginx
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224321
Title:
nginx_1.1.19-1ubuntu0.2 missing conf file on 12.04
To manage notifications about this
I've tested 1.1.19-1ubuntu0.4 in precise-proposed in a newly-installed
Precise VM, and this bug is indeed resolved by 1.1.19-1ubuntu0.4.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I'm setting this as "Incomplete" because this needs further research.
According to the wiki page (which by the way is INCOMPLETE and UNDER
CONSTRUCTION), the version of the software that *has* that software is
in squeeze-backports and is 1.2.1-2, not 1.1.19-1, which is in Ubuntu
and was in Debian
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170585
Title:
whitelist incorrect rule
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170586
Title:
Naxsi package lacking Stub Status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
This is why we don't explicitly trust Wikis or Debian.
Let me clarify the issue: The issue isn't what the Debian wiki says.
The issue is the 1.1.19 package and what was actually in it.
If 1.1.19 in Debian never had Stub Status, and Debian never intended
Stub Status in 1.1.19 then this is an Inva
Further clarification: When I say Debian in my prior comments, I mean
the Debian maintainers of the nginx package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170586
Title:
Naxsi package lacking
*** This bug is a duplicate of bug 1194074 ***
https://bugs.launchpad.net/bugs/1194074
** This bug has been marked a duplicate of bug 1194074
Default index.html blindly overwritten
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Confirmed because of duplicate bug #1245827
** Changed in: nginx (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194074
Title:
Default index.html blindly
Oh, wait, I answered that myself, 1.1.19 is what's in the repositories.
** Changed in: nginx
Status: Incomplete => New
** Also affects: nginx (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I believe this bug is related to the issue where the packages remove
configuration files and such and don't reinstall them.
Do me a favor and test this, please, Kelley. Do this, and see if the
configs show up again: dpkg --reconfigure nginx-common
--
You received this bug notification because y
Kelley,
It should not. However, I think the bug you ran into is related to a
known bug in Debian that has a fix in the precise-proposed repositories.
https://launchpad.net/bugs/1206878 is the bug where we noticed something
similar to this, but nobody's gone through and tested the version in the
Can someone post an example of their configuration, so I can attempt to
replicate this in Debian's packages? If this breakage also occurs in
Debian then it can be fixed there, and depending on how they fix it, I
may be able to SRU the updates for Ubuntu, but I will be able to fix the
issues in the
** Changed in: nginx
Importance: Undecided => Low
** Changed in: nginx (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1216817
Title:
issue with nginx cach
I have used a plain test example from Digital River on getting cache
working with php5-fpm, and can replicate this error with `fastcgi_cache`
in Debian. This is being forwarded to Debian for a fix, and I will
attach a bug number here later.
** Changed in: nginx
Status: Incomplete => Opinio
This is reported in Debian against the nginx-extras package as Debian
bug 732251. (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732251)
As this has been sent up to Debian for a fix, because this is replicated
in *their* packages first and foremost, I am marking both the Nginx
project bug and t
** Summary changed:
- issue with nginx cache and nginx push module in nginx-extra package
+ Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push
module to throw errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
+1 to Daniel Manrique (roadmr) for providing a translation assist for
the dpkg terminal logs.
This "bug" eerily reminds me of Bug 1206878, which we fixed in Precise,
but we may have overlooked Quantal, Raring, and Saucy.
Based on Debian upstream and changes here, this does not impact Trusty,
howe
"Unknown", can you please tell me what command(s) you were running to
get this "bug"? I'm unable to replicate with just a "purge", which
suggests it's *not* bug 1206878, however, without additional information
I cannot begin to diagnose the issue with this bug.
** Changed in: nginx (Ubuntu)
*** This bug is a duplicate of bug 1206878 ***
https://bugs.launchpad.net/bugs/1206878
** This bug has been marked a duplicate of bug 1206878
[SRU] Configuration should be purged only in nginx-common
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Ultimately, you can work around this error (unless others trigger) by
doing `sudo touch /etc/nginx/nginx.conf` which will create a blank file
that apt/dpkg can then remove.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
clel: Bug 1211066 is marked as a duplicate of this bug, if the root
cause is the same then when this bug is fixed it should fix the other
issues as quoted in Bug 1211066 and Bug 1228971 (which is also marked as
a duplicate of this one).
--
You received this bug notification because you are a memb
** Changed in: nautilus-dropbox (Ubuntu Saucy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242413
Title:
nautilus-dropbox needs a dependency on libappindicator1
T
** Changed in: firefox (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933726
Title:
Firefox, incorrect language pack on PPC
To manage notifications ab
"Won't Fix" status was requested by Phill Whiteside and set in
accordance with bug procedures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933726
Title:
Firefox, incorrect language pack on PPC
To
Bug status reset to Confirmed. Importance set to Medium per a request
in #ubuntu-bugs on IRC.
** Changed in: wicd (Ubuntu)
Importance: Undecided => Medium
** Changed in: wicd (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of
Robie: A, thanks for catching my mistake. I forgot all about
-extras. Thanks for amending the upload to have a fix for -extras as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206878
Tit
If you read the error you get, Josh, you need to specify the package or
process ID number.
That's easy, it's the same as if you were using the command line:
ubuntu-bug PACKAGENAMEORPID
Just replace PACKAGENAMEORPID with the name of the package, or the
process id number (you can get that from `pid
After Rohan Dighe emailed the Bug Squad mailing list regarding this
issue, I tested this on a properly configured SKS server that has no
peer servers. This server has actually been configured, which means
that I installed 'sks' and then configured the software for the key
database and the web inte
Remaining releases that have this bug: Precise (12.04), Quantal
(12.10), Raring (13.04).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219978
Title:
not installable because dependency pdumpfs is n
This has been fixed for Saucy, and the package has been removed.
Unfortunately, I'm not sure there's much that can be done for earlier
releases which have this problem.
However, if pdumpfs returns to Debian or Ubuntu, an attempt can be made
to backport the pdumpfs dependency to any remaining stab
This is not necessarily a bug.
You have something else listening on Port 80. You need to make sure
whatever else is listening on Port 80 is *not* listening on port 80 when
you install nginx, and then change nginx's site configurations to bind
to a different port.
** Changed in: nginx (Ubuntu)
I've set verification-done based on comment 8 here, where Roger says it
fixed the issue.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Odd, Apport decided to ignore the package hooks in the package in this
case.
Please run the following command in the terminal and include the output
as either an attachment to this bug or as a bug comment:
systemctl -l status nginx.service
With data from this we will be able to hopefully debug
Given that this is the first report of this in 18 months, I am going to
set this as "Priority Low", and ask that you investigate to determine
the cherry-pickable fix for this, or rather, the specific patch or
changes necessary to fix the issue. If the cherry pick is identified,
we may be able to g
Every version of Ubuntu Utopic or newer is not affected by this issue as
it was already fixed.
** Also affects: nginx (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: nginx (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you ar
** Summary changed:
- Please merge 1.9.4-1 (main) from Debian Unstable (main)
+ Please merge 1.9.6-1 (main) from Debian Unstable (main)
** Summary changed:
- Please merge 1.9.6-1 (main) from Debian Unstable (main)
+ Please merge 1.9.6-2 (main) from Debian Unstable (main)
** Description changed:
Mathew Hodson: Do not mark this bug or the related bug as a duplicate
of each other, they have different sponsoring/review/handling
procedures. Adam Conrad (infinity, on IRC) unduped these after he and I
discussed this on IRC, and they're being handled separately and
differently.
--
You receive
Oop, wait, i'm a little confused with two bugs. This one, regarding
blacklisting and removal is different from the SRU-like replace-with-
dummy-packages one you've linked, Mathew. They're handled differently
in this case.
--
You received this bug notification because you are a member of Ubuntu
And I forgot to put a vivid debdiff here. I'll go poke that now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481033
Title:
Please remove electrum from the archive
To manage notifications abou
After discussion with Adam Conrad of the team governing this bug is
being considered as a different request in a different category and is
being handled as such (standard triage procedures are not applicable in
this case). Blacklisting and removing a package in a devel release has
a different hand
@Maciej Lutostanski:
This bug here is marked Invalid as it is not giving us information, and
is against a superseded version of the package.
Please file a new bug with your information. You may wish to navigate
to /var/crash/, look for a .crash item related to nginx, then run
`ubuntu-bug /var/cr
This is not a bug, it's a broken installation. You are missing the following
file:
10月 17 13:25:37 sailor nginx[6608]: nginx: [emerg] open()
"/etc/nginx/mime.types" failed (2: No such file or directory) in
/etc/nginx/nginx.conf:26
That's installed usually but it sounds like it didn't get insta
*** This bug is a duplicate of bug 1413555 ***
https://bugs.launchpad.net/bugs/1413555
** This bug has been marked a duplicate of bug 1413555
init script fails with error code 0 when configuration test doesn't pass
--
You received this bug notification because you are a member of Ubuntu
B
Ubuntu Wily has a fix for this included as part of the 1.9.3-1ubuntu1
merge. The fix for this issue was introduced in nginx 1.7.0.
** Also affects: nginx (Ubuntu Wily)
Importance: Low
Status: Confirmed
** Changed in: nginx (Ubuntu Wily)
Status: Confirmed => Fix Released
** Desc
Benjamin,
Thanks for the post here. However, there's no debug information
available here, really, to poke at things. One huge difference from
14.04 and 15.04 is systemd, can you include some debug information (such
as the output of `systemctl -l status nginx.service` and `journalctl
-xe`) so we
This is an old bug, however this was added in 1.4.4 -4 in Debian, and
should now be available since Trusty...
** Changed in: nginx (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Do you have Apache or some other service set up and running on Port 80
already?
If so, disable that service (or at least stop the service) before
running `apt-get install -f` or similar to finish configuration. You
have a "cannot bind to port" error as a result of something else being
bound to th
** Summary changed:
- [Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not
being able to be bound to, due to "Address In Use" errors.
+ [Master Bug] Package nginx-* failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1 (due to
nx (Ubuntu)
Importance: Undecided
Assignee: Thomas Ward (teward)
Status: Invalid
** Tags: amd64 apport-package need-duplicate-check vivid
** Changed in: nginx (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
B
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512484
Title:
package nginx-extras 1.6.2-5ubuntu3.1 failed to install/upgrade:
subprocess installed post-instal
** Description changed:
This is a test bug. You can safely disregard this bug. It is needed
- for apport testing.
+ for apport duplicate detection pattern testing.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: nginx-extras 1.6.2-5ubuntu3.1
ProcVersionSignature: Ubuntu 3.
** Description changed:
- This is a test bug. You can safely disregard this bug. It is needed
- for apport duplicate detection pattern testing.
+ This is the master bug for "Address in use" errors with regards to
+ package install/upgrade failures caused by Port 80 being in use. All
+ bugs whic
** Summary changed:
- [Master Bug] Package nginx-* failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1 (due to Port 80 being in
use)
+ Package nginx-* failed to install/upgrade: subprocess installed
post-installation script returned error exit
** Changed in: nginx (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512344
Title:
[Master Bug] Package nginx-* failed to install/upgrade: subprocess
in
Has this actually been done? I see no uploads that back up this being
'completed'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499094
Title:
Please replace electrum with 'dummy' package in the r
We will not be adding additional modules to any of the flavors. On the
roadmap for NGINX in later releases is dynamically-loadable modules.
For Trusty, we are not changing existing functionality.
If you need other modules we don't provide, you will need to recompile
nginx yourself.
** Changed in
Hello.
If this issue still exists, please make a comment as such on this bug.
If there is no further activity in 60 days the bug will automatically be
closed as "Incomplete" and "Expired".
** Changed in: nginx (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
Support for other packages is not through here, you should consider
using a community support medium to get general recovery assistance.
With regards to NGINX, the system is trying to bind to 192.168.1.8:80,
but errors about not rig able to assign that address. Verify your
configuration of that I
I'm going to take the following actions on this bug, and the Server Team
is OK'd to say otherwise, since I'm slightly sleep deprived.
> Agreed, no need to patch this in Ubuntu. Should be done in Debian,
which I can see would have the same problem. -- Benjamin Bach, November
11, 2015, Comment 7
Gi
Note that because of the Bashisms whatever address was negotiated is not
assigned. This applies at least to IPv6, and if the bashisms interfere
in IPv4 then it also interferes there.
This means the essential function of the application does not operate,
and the bug should potentially be a higher
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3566
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505328
Title:
Cups SSL is vulernable to POODLE
To manage notifications abou
*** This bug is a duplicate of bug 1413555 ***
https://bugs.launchpad.net/bugs/1413555
** This bug has been marked a duplicate of bug 1413555
init script fails with error code 0 when configuration test doesn't pass
--
You received this bug notification because you are a member of Ubuntu
B
*** This bug is a duplicate of bug 1413555 ***
https://bugs.launchpad.net/bugs/1413555
NACK on the patch.
The proposed patch is not the correct approach to fix this or the master
bug. Debian has fixes, I'll dig them up.
--
You received this bug notification because you are a member of Ubun
) unstable; urgency=medium
[ Christos Trochalakis]
* New upstream release.
* debian/copyright:
+ Fix licence order.
-- Christos Trochalakis Mon, 24 Aug 2015
16:23:20 +0300
--
Build tests will be underway in
** Affects: nginx (Ubuntu)
Importance: Wishlist
Assi
** Description changed:
Please merge nginx 1.9.4 into Ubuntu. There are multiple changes, some
of which are bug fixes, and some of which are workarounds and other
changes.
--
Upstream changelog on 1.9.4 is available, as well as for subsequent and
prior releases, here: http:/
Public bug reported:
Environment: Trusty
Architecture: amd64
Kernel: lts-vivid
uname -a: Linux darksource 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8
10:21:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Previously, overlayfs was not available in schroot. It no longer errors
on this.
Howeve
Not a bug. If you read the systemctl output for the NGINX service or
read the service logs, you will get the information about why your
installation failed: NGINX could not bind to port 80. Check what's
bound to port 80, and turn that service off temporarily while you
install nginx.
** Changed in
*** This bug is a duplicate of bug 1512344 ***
https://bugs.launchpad.net/bugs/1512344
** This bug has been marked a duplicate of bug 1512344
[Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not
being able to be bound to.
--
You received this bug notification because
80.
To fix this issue, you need to first find what is listening on Port 80,
and turn it off. At that time, either install NGINX or use 'apt-get
install -f' to try and finish configuration.
** Affects: nginx (Ubuntu)
Importance: Undecided
Assignee: Thomas Ward (teward)
*** This bug is a duplicate of bug 1512344 ***
https://bugs.launchpad.net/bugs/1512344
** This bug has been marked a duplicate of bug 1512344
[Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not
being able to be bound to.
--
You received this bug notification because
*** This bug is a duplicate of bug 1512344 ***
https://bugs.launchpad.net/bugs/1512344
** This bug has been marked a duplicate of bug 1512344
[Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not
being able to be bound to.
--
You received this bug notification because
*** This bug is a duplicate of bug 1512344 ***
https://bugs.launchpad.net/bugs/1512344
** This bug has been marked a duplicate of bug 1512344
[Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not
being able to be bound to.
--
You received this bug notification because
*** This bug is a duplicate of bug 1512344 ***
https://bugs.launchpad.net/bugs/1512344
** This bug has been marked a duplicate of bug 1512344
[Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not
being able to be bound to.
--
You received this bug notification because
*** This bug is a duplicate of bug 1512344 ***
https://bugs.launchpad.net/bugs/1512344
** This bug has been marked a duplicate of bug 1512344
[Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not
being able to be bound to.
--
You received this bug notification because
*** This bug is a duplicate of bug 1512344 ***
https://bugs.launchpad.net/bugs/1512344
** This bug has been marked a duplicate of bug 1512344
[Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not
being able to be bound to.
--
You received this bug notification because
** Attachment added: "systemctl_output.txt"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1512344/+attachment/4511191/+files/systemctl_output.txt
** Description changed:
This is a master bug for all package-type nginx bugs with
install/upgrade failures as a result of port 80 being
When trying to fix this yourself...
(1) Check the output of one of these two commands:
'sudo netstat -tulpn | grep :80' OR'sudo ss -tulpn | grep
:80'
This will indicate what processes are listening on IP/Port combination
*:80
(2) Once you know the process/pid that is listening on
Per the notes on the CVE tracker:
sarnold> Backporting this fix is non-trivial and may break deployed
applications. Someone who really wanted this could use stunnel as a
work-around until 16.04 LTS is released.
This applies to Precise, Trusty, and Vivid.
** Changed in: nginx (Ubuntu Precise
** Patch added: "Removal DebDiff for Vivid"
https://bugs.launchpad.net/ubuntu/+source/electrum/+bug/1499094/+attachment/4472711/+files/electrum_removal_vivid.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Patch removed: "Removal DebDiff for Trusty"
https://bugs.launchpad.net/ubuntu/+source/electrum/+bug/1499094/+attachment/4472709/+files/electrum_removal_trusty.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
Related:
https://bugs.launchpad.net/ubuntu/+source/electrum/+bug/1481033
Request:
Please apply a retroactive SRU that will replace the Electrum binaries and such
with 'dummy' packages. A related removal/blacklist request is linked above,
and may be used as the supporting
** Patch added: "Removal DebDiff for Trusty"
https://bugs.launchpad.net/ubuntu/+source/electrum/+bug/1499094/+attachment/4472709/+files/electrum_removal_trusty.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Patch added: "Removal DebDiff for Trusty"
https://bugs.launchpad.net/ubuntu/+source/electrum/+bug/1499094/+attachment/4472712/+files/electrum_removal_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
While this won't fix the problem fully, I have a ZNC PPA that works on
Trusty that uses the packaging as is from Debian - see
https://launchpad.net/~teward/+archive/ubuntu/znc for it. The packaging
is the exact same thing from Debian (with minor changes on the Precise
builds)
** Changed in: znc (
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445595
Title:
Empty Trash Results in File Windows Opening
To manage notifications
NGINX 1.7.x is not in Ubuntu. As such this is not valid against the
Ubuntu package.
Which repository are you using for NGINX 1.7.x anyways?
** Tags added: third-party-package
** Changed in: nginx (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a me
Also, please elaborate what you mean by 'certain configuration
management tools' - unless they're used regularly by a substantial
portion of existence (such as a well known configuration management
tool) then I'm not sure the actual impact.
Until that's clarified, I'm marking importance on this as
901 - 1000 of 1914 matches
Mail list logo
