Where have all my testers gone? This patch isn't going in without some
feedback.
Hmm.. Half a year... To Debian I guess
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Will it be ported to lucid?
** Also affects: qemu-kvm
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/705509
Title:
/dev/kvm is owned by
*** This bug is a duplicate of bug 790863 ***
https://bugs.launchpad.net/bugs/790863
** This bug is no longer a duplicate of bug 796937
Disable CONFIG_NET_NS (for #720095) breaks LXC
** This bug has been marked a duplicate of bug 790863
Unable to start lxc container after update to
*** This bug is a duplicate of bug 790863 ***
https://bugs.launchpad.net/bugs/790863
** This bug has been marked a duplicate of bug 790863
Unable to start lxc container after update to 2.6.32-32
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Provided patch solving this issue.
** Patch added: jot-9.0-random-number-geterator.patch
https://bugs.launchpad.net/ubuntu/+source/athena-jot/+bug/804355/+attachment/2875909/+files/jot-9.0-random-number-geterator.patch
--
You received this bug notification because you are a member of Ubuntu
Oh... Previous patch by any means was not supposed to go to mainline. It
was just dirty-hacky-PoC.
Here is our QA version. Changes:
* Switched to dpkg-source 3.0 (quilt) format
* Added dbg package
* Removed auto-generated files
* Applied arc4random patch
PS. I'm .rpm guy so I could messed up
Public bug reported:
We noticed that after adding IPv6 address to vlan route to local network
is added with expiration time. If after `ip link set vlanXXX up` up we
wait until vlan's link state becomes UP then route get added without
expiration time.
We are using Ubuntu LTS 10.04: Ubuntu
** Changed in: linux (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/917643
Title:
Adding address to vlan in UNKNOWN state results in routes that expire
** Summary changed:
- Adding address to vlan in UNKNOWN state results in routes that expire within
30 days.
+ Adding IPv6 address to vlan in UNKNOWN state results in routes that expire
within 30 days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tested on Ubuntu Oneiric's 3.0 - there is no such problem there.
I've also can test it on other backport kernels when i get to work.
** Tags removed: needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are
Will it be ported to lucid?
** Also affects: qemu-kvm
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/705509
Title:
/dev/kvm is owned by root:root after
Public bug reported:
SRU Justification:
There are lots of server boxes with more than 16 CPUs. Current KVM
implementation can give up to 16 vCPUs to guest system. It would be nice if we
could rise this limit.
Upstream commit:
** Attachment added: 0001-KVM-Bump-maximum-vcpu-count-to-64.patch
https://bugs.launchpad.net/bugs/908981/+attachment/2648033/+files/0001-KVM-Bump-maximum-vcpu-count-to-64.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (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/908981
Title:
SRU: Bump KVM_MAX_VCPUS to 64
To manage notifications about this bug
** Description changed:
SRU Justification:
There are lots of server boxes with more than 16 CPUs. Current KVM
implementation can give up to 16 vCPUs to guest system. It would be nice if we
could rise this limit.
Upstream commit:
Where have all my testers gone? This patch isn't going in without some
feedback.
Hmm.. Half a year... To Debian I guess
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to
Any progress after two weeks?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/614322
Title:
libvirt not recognizing NUMA architecture
To manage notifications about this bug go to:
Public bug reported:
jot -r generates same random numbers within one second time so it's
unusable in batch jobs like shell scripts.
There is code for initializing random seed:
s = (randomize ? time(0) : STEP_DEF);
/*... snip */
srand((int) s);
Here is an example of this
Public bug reported:
Having the limits file world readable will ease the task of system
management on systems where root privileges might be restricted.
Having admin restricted with root priviledges, he/she could not check
other users process' limits.
Also it'd align with most of the /proc stat
** Changed in: linux (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/839630
Title:
proc: make /proc/pid/limits world readable
To manage notifications
Is it going to be backported to LTS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/582769
Title:
/lib/security/pam_cap.so: undefined symbol: pam_get_item
To manage notifications about this bug go
I think it has even greater impact: pam module is not working so we
can't set per-user inheritable capabilities via
/etc/security/capability.conf in common-auth
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Fri, May 4, 2012 at 5:20 AM, Balbir Singh bsinghar...@gmail.com wrote:
On Thu, May 3, 2012 at 11:59 PM, Christian Kujau
493...@bugs.launchpad.net wrote:
Whooha, language!
And I think they fixed it, albeit in a weird way:
CONFIG_TASK_DELAY_ACCT is enabled in the kernel config, but the
Backport to Lucid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/811016
Title:
Move to /run breaks pbuilder --execute
To manage notifications about this bug go to:
Public bug reported:
4.10 kernel is commonly used for test BBR Congestion Control
deployments.
Recent 4.13 release had a bunch of fixes for the initial BBR release, namely:
4aea287e90dd61a48268ff2994b56f9799441b62 tcp_bbr: cut pacing rate only if
filled pipe
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708604
Title:
Backport recent bbr bugfixes to 4.10 kernel
To manage notifications
** Description changed:
- 4.10 kernel is commonly used for test BBR Congestion Control
- deployments.
+ 4.10 kernel is commonly used to test BBR Congestion Control deployments.
- Recent 4.13 release had a bunch of fixes for the initial BBR release, namely:
+ Recent net-next pull in 4.13-rc1
Sadly, we've already workedaround that problem with a custom-built
module. Let me see if my colleagues can test the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708604
Title:
Backport
The log message[1] says that this issues is under investigation:
> For the moment turn it off while it can be investigated.
Did we find the root cause? Seems like Debian is successfully uses it nowadays:
```
tar -xOzf linux_5.10.19-1.debian.tar.xz ./debian/config/config | fgrep
Is it possible (pun intended) to compromise on
`CONFIG_SQUASHFS_DECOMP_MULTI` (which uses num_online_cpus) instead of
`CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU` (which uses `num_possible_cpus`)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
30 matches
Mail list logo
