** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've installed this package on Xenial, and it fixes this issue for me
(specifically, with openvpn).
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What makes this unsuitable for an SRU? Is the concern that this would be
considered an interface change?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547231
Title:
/proc/$pid/maps performance
** Description changed:
/proc/$pid/maps experienced a significant performance regression for
processes with large numbers of threads between Precise and Trusty due
to an upstream bug. This behavior is currently blocking my ability to
upgrade to Trusty, as we depend on applications with
Hey folks -
Anything I can do to get this into the next trusty kernel release? This
has now caused multiple production incidents for us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547231
Title:
Thanks Martin. I've confirmed that the package solves the issue for me.
** 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/bugs/1551897
Sorry about that, Martin. Not sure what happened. Just re-uploaded
without the noise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU utilization
To manage notifications
** Changed in: ccid (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU utilization
To manage notifications about
** Description changed:
+
+ [DESCRIPTION]
+
+ When hotplugging a composite USB device that expose multiple interfaces
+ (such as a Yubikey NEO or Yubikey 4), libccid does not correctly de-
+ initialize the USB library when it skips over the non-CCID interface.
+
+ This subsequently results in
This is actually a bug in ccid's handling of composite USB devices, and
has been fixed upstream (https://alioth.debian.org/plugins/scmgit/cgi-
bin/gitweb.cgi?p=pcsclite/CCID.git;a=commitdiff_plain;h=3c21f452543983f3625a1965ce234074cbda6865).
My experience was that this bug caused pcscd to
** Also affects: ccid (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ccid (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: pcsc-lite (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: ccid (Ubuntu Xenial)
Status:
@brian-murray: I just installed the package from proposed on trusty and
it seems to have improved things, although there's a 5-10 second delay
after nm-applet starts up where it hasn't registered itself as a secrets
provider. Still, this seems to be an improvement in behavior.
** Tags added:
** Changed in: python3.4 (Ubuntu Trusty)
Importance: Undecided => Critical
** Patch added: "python-botocore_0.29.0+repack-2ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1499075/+attachment/4472704/+files/python-botocore_0.29.0%2Brepack-2ubuntu0.1.debdiff
** Also affects: python-botocore (Ubuntu)
Importance: Undecided
Status: New
** Also affects: python3.4 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: python-botocore (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in:
I've attached fixes for the issue for Trusty and Utopic, the only two
affected releases. They're also building now in my PPA
(https://launchpad.net/~broder/+archive/ubuntu/ubuntu-tests). I'll
upload to -proposed once I can confirm the test packages work.
--
You received this bug notification
** Patch added: nsd_4.0.3-1ubuntu0.1.debdiff
https://bugs.launchpad.net/ubuntu/+source/nsd/+bug/1311886/+attachment/4295873/+files/nsd_4.0.3-1ubuntu0.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [IMPACT]
+
+ Currently, nsd fails to install. The postinst attempts to start the nsd
+ daemon before creating the nsd user, and fails when starting the daemon
+ fails.
+
+ The daemon is started by debhelper-generated snippets. The attached
+ fixes move the
** Also affects: nsd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: nsd (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: nsd (Ubuntu Trusty)
Status: New = Confirmed
** Changed in: nsd (Ubuntu Utopic)
Status: New = Confirmed
** Changed in: nsd (Ubuntu Trusty)
Status: Confirmed = In Progress
** Changed in: nsd (Ubuntu Utopic)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the approvals, Sebastian and Brian.
I've repeated the steps I outlined in the description and confirmed that
the bug does not occur with the packages in -proposed. I've also
installed the packages in our production nagios server and confirmed
that things seem to more or less work as
Thanks for the approvals, Sebastian and Brian.
I've repeated the steps I outlined in the description and confirmed that
the bug does not occur with the packages in -proposed. I've also
installed the packages in our production nagios server and confirmed
that things seem to more or less work as
** Also affects: nagios3 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: nagios3 (Ubuntu Precise)
Status: New = Confirmed
** Changed in: nagios3 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of
** Description changed:
- Description: Ubuntu 12.04.2 LTS
- Release: 12.04
+ [Impact]
+ Under nagios 3.2.3 with state retention enabled, any host aliases or display
names assigned to a host would be persisted into the retention file, and would
supersede subsequent configuration changes.
** Also affects: nagios3 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: nagios3 (Ubuntu Precise)
Status: New = Confirmed
** Changed in: nagios3 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of
** Description changed:
- Description: Ubuntu 12.04.2 LTS
- Release: 12.04
+ [Impact]
+ Under nagios 3.2.3 with state retention enabled, any host aliases or display
names assigned to a host would be persisted into the retention file, and would
supersede subsequent configuration changes.
There's a comment at http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/saucy/rsyslog/saucy/view/head:/tools/syslogd.c#L2428
that says we need to re-call GenerateLocalHostNameProperty after parsing
config, but as far as I can tell, that doesn't happen.
Does adding a call to queryLocalHostname()
** Changed in: ubuntu-dev-tools (Ubuntu)
Assignee: (unassigned) = Evan Broder (broder)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1106429
Title:
[backportpackage] -sa detection does
I did look at those - the patch for CVE-2009-5031 seems to have been
applied already. The link to the patch for CVE-2012-2751 (http://mod-
security.svn.sourceforge.net/viewvc/mod-
security?view=revisionsortby=logsortdir=downrevision=1918) appears to
be dead, so I haven't been able to tell whether
Ok, here's a patch with the fix for CVE-2012-2751 rolled in. I kind of
made up the DEP-3 fields, but I think they'll at least satisfy their
purpose.
I've tested that the resulting packages with this patch work at at least
a basic level, but I still don't have POCs to test with or anything.
**
Bleh, looks to have been a stupid copy/paste error (missing / for the
start of a /* comment). Builds for me now, and still seems to
install/work at a basic level.
** Patch added: libapache-mod-security_2.5.11-1ubuntu0.1.debdiff
** Changed in: modsecurity-apache (Ubuntu)
Status: In Progress = Triaged
** Changed in: modsecurity-apache (Ubuntu)
Assignee: Evan Broder (broder) = (unassigned)
** Changed in: libapache-mod-security (Ubuntu)
Assignee: (unassigned) = Evan Broder (broder)
--
You received this bug
Ok, I've installed this on one of my Lucid servers, and it still seems
to work at at least a basic level.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169030
Title:
CVE 2013-1915: local files
By the way, feel free to ping me (broder) in #ubuntu-hardened if I can
do anything to improve the debdiff.
** Changed in: libapache-mod-security (Ubuntu)
Status: In Progress = Triaged
** Changed in: libapache-mod-security (Ubuntu)
Assignee: Evan Broder (broder) = (unassigned
*** This bug is a security vulnerability ***
Public security bug reported:
http://marc.info/?l=oss-securitym=136499182131283w=2
http://people.canonical.com/~ubuntu-security/cve/2013/CVE-2013-1915.html
** Affects: modsecurity-apache (Ubuntu)
Importance: Undecided
Assignee: Evan Broder
Here's a patch which I believe be a correct backport of the upstream
patch to Lucid (it didn't apply cleanly due to other additions to
modsecurity since Lucid's release). I've verified that it builds but not
yet done any testing - I'll be doing so shortly.
** Patch added:
Public bug reported:
backportpackage's attempt to detect whether -sa is needed or not is
foiled by private PPAs, as hitting
https://launchpad.net/~whomever/+archive/whatever/+files/my_file
redirects to the login page. httplib2 follows redirects, and the login
page returns a 200, so
We used to generate backport version numbers of the form
VERSION_BEING_BACKPORTED~RELEASE_CODENAME1. It worked well at the time
because it guaranteed that a backport of the same version to, e.g.,
natty would have a lower version number than the backport to oneiric,
since the n would sort before o.
We used to generate backport version numbers of the form
VERSION_BEING_BACKPORTED~RELEASE_CODENAME1. It worked well at the time
because it guaranteed that a backport of the same version to, e.g.,
natty would have a lower version number than the backport to oneiric,
since the n would sort before o.
Hey guys -
Some quick updates based on assorted recent discussions.
As we move to a world where archive admins use APIs instead of shell
access to do their job, it's no longer really necessary for them to be
processing backports. Colin has said that he is OK with us uploading
backports
As part of trying to do a slightly better job of handling security and
stable updates, I'd like to propose reducing our testing requirements
for those backports.
Proposal: For stable and security updates of backported packages which
are not new upstream versions, it is not necessary to test
This has been uploaded and accepted. It will now build, and should be
available in the archive shortly. Thanks!
** Changed in: precise-backports
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is the
This has now been uploaded and accepted. It should build and become
available in the repositories over the next few hours. Thanks again!
** Changed in: oneiric-backports
Status: In Progress = Fix Released
** Changed in: lucid-backports
Status: In Progress = Fix Released
** Changed
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu
10.10 (Maverick Meerkat) no longer being supported.
It looks like you requested a backport to Ubuntu 10.04 (Lucid
Lynx). Now that Ubuntu 10.10 is no longer supported, it may be
possible to backport this package directly to Ubuntu
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
It looks like you requested a backport to Ubuntu 10.04 (Lucid Lynx). Now
that Ubuntu 10.10 is no longer supported, it may be possible to backport
this package directly to Ubuntu
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
It looks like you requested a backport to Ubuntu 10.04 (Lucid Lynx). Now
that Ubuntu 10.10 is no longer supported, it may be possible to backport
this package directly to Ubuntu
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
It looks like you requested a backport to Ubuntu 10.04 (Lucid Lynx). Now
that Ubuntu 10.10 is no longer supported, it may be possible to backport
this package directly to Ubuntu
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
Sure, not a problem. Apologies for the delay in review. You've already
confirmed that the package b/i/r on Lucid, Natty, and Oneiric, and tickr
has no reverse depends.
ACK from backporters; should be backported shortly.
** Changed in: oneiric-backports
Status: Incomplete = In Progress
**
Clayton - Thanks for the update. It does sound like your issue was
different than mine, but I'm glad it was resolved.
(For reference, because it's very difficult to detect whether a laptop
is actually docked, upower instead looks at whether or not multiple
displays are connected to the laptop,
Public bug reported:
Now that gnome-settings-daemon's power management code checks upower's
is-docked flag, it's important that it be accurate.
However, it is possible that the inputs to the is-docked state could
change while the laptop is suspended without generating a drm udev event
to trigger
Hi Clayton -
This sounds like it could be related to a bug I just filed (bug
#980746). With my bug, the laptop suspends if I choose suspend from the
system menu or by pressing the power button, but not if I close the
laptop lid. Is that what you see as well?
Could you run upower --dump after
Public bug reported:
Please backport mosh 1.1-1 (universe) from precise to lucid, maverick,
natty, oneiric.
Reason for the backport:
mosh is a new remote shell application that uses automatic
reconnection and predictive echo to deliver a better experience to
mobile
ACK from backporters
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for natty-backports.
https://bugs.launchpad.net/bugs/966511
Title:
Please backport mosh 1.1-1 (universe) from precise
To manage notifications about this bug go
It's unfortunately not that simple. We've always shipped the hedgewars
server as part of our packages. To drop the server in a post-release
update would not be acceptable. However, the Haskell language has
changed enough since early 2010 that the current server will not build
using the Haskell
Hi Derek -
Currently Ubuntu 11.10 has been updated to hedgewars 0.9.17. There are
pending updates for Ubuntu 10.10 and 11.04. However, before we can
release those updates to the general public, they need to be tested, and
so far nobody has stepped up to verify that the new packages work on
those
Public bug reported:
mosh is a remote shell updated for the realities of modern network
connectivity. It supports roaming (automatically reestablishes
connections if they get broken) and predictive local echo (for better
perceived interactivity on high-latency connections)
Version 1.0 of mosh is
** Attachment added: mosh_1.0-1_amd64.build
https://bugs.launchpad.net/bugs/961807/+attachment/2913944/+files/mosh_1.0-1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961807
Title:
Hi Derek -
Currently Ubuntu 11.10 has been updated to hedgewars 0.9.17. There are
pending updates for Ubuntu 10.10 and 11.04. However, before we can
release those updates to the general public, they need to be tested, and
so far nobody has stepped up to verify that the new packages work on
those
the VPN.
** Affects: network-manager-vpnc (Ubuntu)
Importance: Undecided
Assignee: Evan Broder (broder)
Status: In Progress
** Affects: vpnc (Ubuntu)
Importance: Undecided
Assignee: Evan Broder (broder)
Status: In Progress
--
You received this bug notification
** Changed in: vpnc (Ubuntu)
Assignee: (unassigned) = Evan Broder (broder)
** Changed in: vpnc (Ubuntu)
Status: New = In Progress
** Summary changed:
- vpnc does not support split DNS on Cisco VPN servers
+ vpnc, network-manager-vpnc don't support split DNS VPN attribute
** Also
in: vpnc (Ubuntu)
Status: In Progress = Triaged
** Changed in: vpnc (Ubuntu)
Assignee: Evan Broder (broder) = (unassigned)
** Changed in: vpnc (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: network-manager-vpnc (Ubuntu)
Importance: Undecided = Wishlist
--
You received
** Changed in: open-iscsi (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/394398
Title:
Logic to determine expected number of running session wrong
FYI, I looked into multiarching libpcsclite1 when I originally opened
this bug, and concluded that it probably couldn't easily be multiarched.
Because the protocol headers consist of shoving integers into structs,
it's not going to be endianness-agnostic.
--
You received this bug notification
On Mon, Mar 12, 2012 at 8:46 PM, Andrew Starr-Bochicchio
a.star...@gmail.com wrote:
I sent this to pitti a few days ago, seems like he hasn't had a chance
to get to it. In retrospect, he's probably not the only one that has
the answer to this question so there's really no reason to have
Alessio: Incidentally, for future reference, we added a requestbackport
script in Precise (it should also be in Wheezy). We're recommending that
people use it because the bug template it uses makes clear exactly what
has and hasn't been done.
--
You received this bug notification because you are
ACK from backporters for natty.
** Changed in: natty-backports
Status: New = In Progress
** Changed in: natty-backports
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for natty-backports.
Because packages from backports are not installed by default, we prefer
to only use backports as a way to offer new features, not fix bugs. Bugs
in packages should be fixed through the SRU process
(https://wiki.ubuntu.com/StableReleaseUpdates), so that all users of the
package can benefit from the
** Also affects: egenix-mx-base (Ubuntu Oneiric)
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/884619
Title:
Segfault with comparison to None
To manage
Normally we prefer to isolate just the necessary changes to fix the bug.
In this case, though, the entirety of the 3.2.1 release contains
bugfixes. In these cases, we can upload the new release as an SRU.
However, I made a mistake opening an SRU task on this bug, since bug
#884619 is already
This has already been fixed in the 3.2.1 upstream release, currently in
Precise as 3.2.1-1, so I'm closing the bug against the development
release.
I've gone ahead and uploaded an microrelease update of 3.2.1 to oneiric-
proposed. Somebody from the SRU team should be through to review the
SRU. In
To clarify above, I chose to update to 3.2.1 not because it's difficult
to isolate the relevant patch, but because all of the changes in the
3.2.1 release fix bugs in the code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 1419 matches
Mail list logo
