This stopped happening for me, and I happily ran with fully operational
suspend/resume for a long time using the Linux-4.1.y series. Most
recently Linux-4.1.17. However, a few days ago I upgraded from
Linux-4.1.17 to the 4.4.y series — currently Linux-4.4.1 — and now the
same symptoms happen again:
Just a reminder: this has been fixed in upstream Tahoe-LAFS. Here is the
ticket in the Tahoe-LAFS issue tracker: https://tahoe-lafs.org/trac
/tahoe-lafs/ticket/2354
Here are the patches that fix this issue:
*
https://github.com/tahoe-lafs/tahoe-lafs/commit/ef455df990c5585e8755d1d791f4dac0ef95495
Public bug reported:
http://git-
annex.branchable.com/bugs/Can__39__t_initialize_Tahoe_special_remote/?updated
#comment-ac0f1a248200cdabe572a9c2e9140ad1
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2437
** Affects: tahoe-lafs
Importance: Unknown
Status: Unknown
** Affects: git-an
Dear derhannes: Thanks! I'm glad it is working for you. By the way, I'm
happy to hear of another Tahoe-LAFS user! Would you please send me an
email at zo...@leastauthority.com so I can ask you questions about how
you use it and how it works for you?
--
You received this bug notification because y
That's because of this change to setuptools which changed the meaning of
"," in dependency specifications:
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2354
You could apply the patch from here:
https://tahoe-lafs.org/trac/tahoe-lafs/changeset/ef455df990c5585e8755d1d791f4dac0ef954956/trunk
https
Public bug reported:
INFO:urllib3.connectionpool:Starting new HTTPS connection (1): api.twitter.com
INFO:urllib3.connectionpool:Starting new HTTPS connection (1): api.twitter.com
INFO:urllib3.connectionpool:Starting new HTTPS connection (1): api.twitter.com
INFO:urllib3.connectionpool:Starting new
Public bug reported:
I tried to use this app, and I can't figure how to turn it on. This is
all I see:
** Affects: friends-app (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "2015-01-19-220532_2560x1700_scrot.png"
https://bugs.launchpad.net/bugs/1412582/+attach
Confirming that the workaround from
https://bugs.launchpad.net/linux/+bug/1224689/comments/7 doesn't work
for me with Ubuntu 14.04.1 with (my own locally-compiled) kernel 3.18.1
** Also affects: chromium via
http://code.google.com/p/chromium/issues/detail?id=221905
Importance: Unknown
** Also affects: elisa (PLD Linux)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263697
Title:
installing elisa breaks the unit tests of unrelated Python
By the way, this patch replaced a regexp with json.loads():
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/quantal/software-
properties/quantal/revision/77
That was good, because a regexp could have been vulnerable to some sort
of xss/injection sort of problem. But, the patch mistakenly left
dkg0: you're right, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016643
Title:
add-apt-repository downloads gpg key in an insecure fashion
To manage notifications about this bug go to:
ht
By the way, this patch replaced a regexp with json.loads():
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/quantal/software-
properties/quantal/revision/77
That was good, because a regexp could have been vulnerable to some sort
of xss/injection sort of problem. But, the patch mistakenly left
If anybody knows of an upstream bug report about this, could you give
the link to it here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794453
Title:
First message is sent unencrypted
To manage no
I'd just like to say Thank You to Moritz for explaining the security
problem (resulting from the user experience) so well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794453
Title:
First message i
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989016
Title:
package dictionaries-common 1.12.1ubuntu2 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned
Public bug reported:
I suspect I may have run out of disk space during the 11.10→12.04
upgrade. Perhaps the tools that analyze and report problems should check
for the disk free amount.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: dictionaries-common 1.12.1ubuntu2
Uname: Linux 3.2.16
** Also affects: openssl (Fedora)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/944585
Title:
warnings from valgrind about openssl as used by CPython
To
** Bug watch added: OpenSSL RT #2747
http://rt.openssl.org/Ticket/Display.html?id=2747
** Also affects: openssl via
http://rt.openssl.org/Ticket/Display.html?id=2747
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Bug watch added: Python Roundup #14171
http://bugs.python.org/issue14171
** Also affects: python via
http://bugs.python.org/issue14171
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Attachment added: "cpython-openssl101.supp"
https://bugs.launchpad.net/ubuntu/+source/pycryptopp/+bug/944585/+attachment/2800041/+files/cpython-openssl101.supp
** Bug watch added: tahoe-lafs-org-trac-pycryptopp #82
https://tahoe-lafs.org/trac/pycryptopp/ticket/82
** Also affects: pycryp
Public bug reported:
The buildbot for the Tahoe-LAFS and pycryptopp projects runs CPython
under valgrind on Fedora, and valgrind emits warnings like this:
==30127== Conditional jump or move depends on uninitialised value(s)
==30127==at 0x4C2AD01: bcmp (mc_replace_strmem.c:889)
==30127==by
I opened a ticket on launchpad.net with which to track the progress of
this issue across multiple other issue trackers: pycryptopp, GCC,
Fedora, and possibly DJB's "nacl" crypto library if there is any way to
track such issues other than emailing the author.
https://bugs.launchpad.net/pycryptopp/+b
Thanks to Samuel Neves, the bug was identified in the application
(pycryptopp), not in gcc. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931542
Title:
using the gcc-4.7.0 prerelease as pack
Thanks to Samuel Neves, the bug was identified in pycryptopp. See the
pycryptopp ticket for details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931542
Title:
using the gcc-4.7.0 prerelease as pac
** Description changed:
This doesn't *actually* affect Ubuntu yet, at least not until Ubuntu
upgrades to gcc 4.7.0 and only if this bug is still present by then.
- But, I want to link together bug reports in various issue trackers and
- aggregate them in launchpad, and the only way I can do th
The hyperlink to the issue in the Fedora issue tracker is
https://bugzilla.redhat.com/show_bug.cgi?id=773443 .
(This is a test of LaunchPad. If you, oh noble LaunchPad, update this
ticket to have a hyperlink to that ticket in the table of other
projects/distros that this "Affects", at the top, the
** Changed in: libcrypto++ (Ubuntu)
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/915018
Title:
gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on
To manage notificat
** Also affects: pycryptopp (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=790114
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931542
Title:
Public bug reported:
This doesn't *actually* affect Ubuntu yet, at least not until Ubuntu
upgrades to gcc 4.7.0 and only if this bug is still present by then.
But, I want to link together bug reports in various issue trackers and
aggregate them in launchpad, and the only way I can do that currentl
I made some patches that fix this bug and let the current trunk of
pycryptopp build with the debian packaging plus my patches. You can
see my patches here:
https://code.launchpad.net/~zooko/pycryptopp/debian
And the launchpad autobuilder using those patches here:
https://code.launchpad.net/~taho
** Bug watch added: Debian Bug tracker #659206
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659206
** Changed in: pycryptopp (Debian)
Importance: Undecided => Unknown
** Changed in: pycryptopp (Debian)
Status: New => Unknown
** Changed in: pycryptopp (Debian)
Remote watch: None
Public bug reported:
Trunk has changed (for the better) so that now these patches are
unnecessary and no longer apply:
dpkg-source: warning: patches have not been applied, applying them now (use
--no-preparation to override)
dpkg-source: info: applying move_testvectors_outside_site-packages.patc
Here is a launchpad ticket tracking the effect of this bugfix on various
open source projects that were depending on the bug:
https://bugs.launchpad.net/cryptopp/+bug/915018
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Bug watch added: Red Hat Bugzilla #773443
https://bugzilla.redhat.com/show_bug.cgi?id=773443
** Also affects: libcrypto++ (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=773443
Importance: Unknown
Status: Unknown
** Also affects: gcc-4.7 (Fedora) via
https://bugzill
Public bug reported:
gcc 4.7.0 fixes a bug (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24163
) that Crypto++ 5.6.1 was inadvertently relying on
(http://sourceforge.net/apps/trac/cryptopp/ticket/14 ). This has been
discovered by the Fedora project upgrading to a 4.7.0 prerelease
(http://lists.fedo
35 matches
Mail list logo