I have confirmed that downgrading cpio to 2.13+dfsg-7 also resolves the
build error in that environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066157
Title:
cpio 2.13+dfsg-2ubuntu0.4
** Description changed:
I'm not sure where the true fault is but the problem only happens after
updating the cpio package from 2.13+dfsg-2ubuntu0.3 to
2.13+dfsg-2ubuntu0.3. The zfs build creates .rpms which are then
converted to .debs. The failure message is:
```
name=zfs; \
This same issue has been observed trying to build in a jammy system with
cpio=2.13+dfsg-7ubuntu0.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066157
Title:
cpio 2.13+dfsg-2ubuntu0.4 breaks zfs
Public bug reported:
I'm not sure where the true fault is but the problem only happens after
updating the cpio package from 2.13+dfsg-2ubuntu0.3 to
2.13+dfsg-2ubuntu0.3. The zfs build creates .rpms which are then
converted to .debs. The failure message is:
```
name=zfs; \
version=2.1.15-1; \
I've had a look at the x86 code where this error comes from:
/* Returns a pointer to the cpumask of CPUs on Node 'node'. */
static inline const struct cpumask *cpumask_of_node(int node)
{
return node_to_cpumask_map[node];
}
So it seems the error arises because it is asked for a negative
I have also encountered the same trace reported in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157/comments/15
on a Dell R450 system:
# lspci -vv -s 65:00.0
65:00.0 RAID bus controller: Broadcom / LSI MegaRAID 12GSAS/PCIe Secure SAS38xx
DeviceName: SL3 RAID
Not sure what format was best so this `acpidump -b` then tar gz.
** Attachment added: "Dell T440 `acpidump -b`"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962730/+attachment/5565825/+files/acpidump-t440.tar.gz
--
You received this bug notification because you are a member of
The tg3 patch did not work, from the pstore record:
<6>[ 328.733248] ACPI: Preparing to enter system sleep state S5
<0>[ 331.440360] {1}[Hardware Error]: Hardware error from APEI Generic
Hardware Error Source: 5
<0>[ 331.440361] {1}[Hardware Error]: event severity: fatal
<0>[ 331.440361]
dmesg had rolled out the early boot messages so this is
/var/log/kern.log for the current boot.
** Attachment added: "/var/log/kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962730/+attachment/5565219/+files/1962730-dmesg.txt
--
You received this bug notification because
The 'device_id: :01:00.1' mentioned in the stack trace is one port
of a dual interface network card.
** Attachment added: "Output of `lspci -vvnn`"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962730/+attachment/5565217/+files/1962730-lspci.txt
--
You received this bug
I have built a kernel with this commit reverted by including the
referenced mainline change which resolves the observed problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962730
Title:
Use
`apport-collect` can not be installed in this environment as it runs
from a read only / image.
** 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.
Public bug reported:
On a Dell T440 system the following crash is captured from reboot in
pstore. Although this example is not with the latest system BIOS it
does also happen with the latest (2.13.3). The upstream kernel tree has
reverted the patch applied for #1904225 in commit
I have installed the updated package and my issue with the backup
command has been resolved. Thank you:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952187
Title:
backup command raises
Public bug reported:
upstream report with proposed fix:
https://bugzilla.samba.org/show_bug.cgi?id=14918
Since the upgrade in 'focal' to 4.13 the samba domain backup script
fails if there is a dangling symbolic link in any of the directories
included in the backup.
running backup on dirs:
The version mismatch was the cause of a problem I had with `zfs
promote`: https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/1947568
In the end I'm using a 3rd party PPA to get updated user space tools but
I don't see that as the ideal solution.
--
You received this bug notification
This appears to be an issue with mismatched user/kernel zfs components.
After adding ppa:jonathonf/zfs
(https://launchpad.net/~jonathonf/+archive/ubuntu/zfs) and updating the
user components my `zfs promote` problem has been resolved.
# zfs version
zfs-2.1.1-0york0~20.04
zfs-kmod-2.0.2-1ubuntu5.1
Present with latest kernel and user space packages:
# zfs create -V1G rpool/test1
# zfs snapshot rpool/test1@test2
# zfs clone rpool/test1@test2 rpool/test3
# zfs promote rpool/test3
cannot promote 'rpool/test3': not a cloned filesystem
# lsb_release -a
No LSB modules are available.
Distributor
** Description changed:
I have a zvol containing a Windows image for a virtual machine. After
restarting the system a node under /dev/zvol/... was not created for the
virtual disk and no amount of prompting by `udevadm trigger` helped.
Instead I created a snapshot from the most recent
** Description changed:
I have a zvol containing a Windows image for a virtual machine. After
restarting the system a node under /dev/zvol/... was not created for the
virtual disk and no amount of prompting by `udevadm trigger` helped.
- Instead a create a snapshot from the most recent
Public bug reported:
I have a zvol containing a Windows image for a virtual machine. After
restarting the system a node under /dev/zvol/... was not created for the
virtual disk and no amount of prompting by `udevadm trigger` helped.
Instead a create a snapshot from the most recent hourly backup:
Do you have messages like this in the kernel boot log?
[ 2.072227] nvme nvme1: ignoring ctrl due to duplicate subnqn
(nqn.2017-12.org.nvmexpress:uuid:----).
[ 2.072231] nvme nvme1: Removing after probe failure status: -22
It looks like since 5.2
I rebuilt ntp to include the patch and it has run for over 10 minutes
without crashing after enabling the GPSD_JSON reference clock which
suggest it has resolved the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "copy of the upstream patch applied to my rebuild of ntp"
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1923059/+attachment/5485965/+files/ntp-1738.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
possibly related: https://bugs.ntp.org/show_bug.cgi?id=3691 - will test
the patch
** Summary changed:
- ntpd crashes using GPS_JSON clock
+ ntpd crashes using GPSD_JSON clock
** Bug watch added: bugs.ntp.org/ #3691
http://bugs.ntp.org/show_bug.cgi?id=3691
--
You received this bug
Public bug reported:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
# apt-cache policy ntp
ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu4
Candidate: 1:4.2.8p12+dfsg-3ubuntu4
Version table:
***
See also: https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/1808421
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921108
Title:
blkid reports disk as zfs_member if it has a zfs_member
Public bug reported:
Upstream bug report: https://github.com/karelzak/util-linux/issues/918
In summary if a disk partition used for zfs is at the end of the disk
then libblkid identifies the _whole_ disk as a zfs member which causes
udev information returned for other partitions to be incorrect.
** Package changed: ubuntu => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888400
Title:
grub-common: generated xen boot entries incorrect with root on zfs
To manage notifications
Public bug reported:
I was doing some experimentation with encrypted zvols and observed that
the zfs-volume-wait.service systemd unit does not start if the encrypted
zvol is locked. The /sbin/zvol_wait should not wait for links when the
volume has property keystatus=unavailable. The attached
** Summary changed:
- grub-common: root on zfs incorrect grub command for xen boots
+ grub-common: generated xen boot entries incorrect with root on zfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I have a system with a ZFS root (/) and which boots xen. The generated
grub.cfg kernel command line is ok for a non-xen boot but is missing the
pool name from the xen entries. Since upgrading from 18.04 it is
necessary to modify the command line via the grub editor during
#6 got a paste error, it should have been `dpkg-reconfigure grub-efi-
amd64` to (re)populate the missing debconf configuration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874318
Title:
package
I manually set the grub-efi/install_devices with the following command
where G1 and G2 were set to my two ESP devices.
echo grub-efi-amd64 grub-efi/install_devices multiselect $G1 $G2 |
debconf-set-selections
With a `set -x` added in /usr/lib/grub/grub-multi-install it now
complains about
On a problematic system this returns no values:
# debconf-get-selections | grep grub-efi
On another focal system the output is:
grub-efi-amd64 grub2/kfreebsd_cmdline_default string quiet splash
grub-efi-amd64 grub2/update_nvram boolean true
grub-efi-amd64 grub2/kfreebsd_cmdline
$ apt-cache policy autolog
autolog:
Installed: (none)
Candidate: 0.40+debian-2
Version table:
0.40+debian-2 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu
Public bug reported:
We use autolog to end idle sessions on systems which are configured with
nss_winbind. When the DOMAIN\user string is >20 chars this will crash
autolog as a fixed string field is overflowed. The source seems to have
not had much attention (presumably because it is either
Apologies if this isn't the place to ask this question... This bug
seems to be only about backporting compatibilty for the current 0.7
module but my system seems to have ended up with 0.8. This isn't a
problem for me but I would prefer that the userspace aligns with the
module so that new
I managed to build a working xen.efi on eoan with the following commits
from the xen git tree:
6561994b87af3e9cd28ee99c42e8b2697621687d (lz4 fix)
14b62ab3e5a79816edfc6dd3afce1bb68c106ac5 (lz4 fix)
45342cd88d564a7da2dfbbc921898805008b0b6c (gcc 9 fix)
2effc2f131145fdd40352085c11adb1e17164135 (gcc 9
Public bug reported:
Upstream issue: https://github.com/prometheus/node_exporter/issues/1049
Summary: Linux 4.19 changed the format of /proc/diskstats which breaks
node exporter. syslog has many messages of the form:
prometheus-node-exporter[615]: time="2019-09-06T13:09:11+01:00"
level=error
This issue affects me on Ubuntu Bionic 18.04 if I have a Firefox window
open with a frequently changing title bar. It seems that plasmashell
cannot keep up with re-rendering the label on the task bar buttons. The
specific Firefox operation that triggers it for me is using the HTML5
iKVM on a
Related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803692
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811755
Title:
X1 Extreme: only one of the two SSDs is loaded
To manage
The fix is available in the at least the 4.18 branch:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/log/drivers/nvme/host?h=Ubuntu-hwe-4.18.0-21.22_18.04.1
This is good enough for our needs so closing the issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
Public bug reported:
When building a disk image inside a docker container an `apt-get update`
executed in the chroot filesystem is very slow. This seems similar to
behaviour reported in #1332440.
Ubuntu bionic host docker-ce 5:18.09.1~3-0~ubuntu-bionic -> ubuntu:18.04
docker image -> bionic
The fix has been merged to the mainline kernel tree as commit
6299358d198a0635da2dd3c4b3ec37789e811e44.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-fixed-upstream
--
You received this bug notification
A workaround in the kernel nvme driver has been tested and proposed:
http://lists.infradead.org/pipermail/linux-
nvme/2018-November/021366.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
I tried to force install the Intel firmware which contains the fix but
that did not work as the utility refused to overwrite the custom Lenovo
firmware. I opened a support case with Lenovo referencing the Intel fix
but the case was closed with 'we don't support Linux' :( Perhaps it
would be
I have changed the bug to 'invalid' as I do not expect a fix in Ubuntu
for the firmware bug.
https://downloadcenter.intel.com/download/28320/Known-Issue-Intel-SSD-
760p-Pro-7600p-Series-SubNQN-Conflict-on-Linux
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received
The linked thread on fedoraproject.org indicates that a firmware update
for the device will be necessary to resolve this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
Title:
bionic
The issue exists upstream:
$ uname -r
4.20.0-042000rc3-generic
$ dmesg | grep nvme
[1.857861] nvme nvme0: pci function :02:00.0
[1.857900] nvme nvme1: pci function :04:00.0
[1.968167] nvme0n1: p1 p2 p3 p4
[2.072227] nvme nvme1: ignoring ctrl due to duplicate subnqn
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213429/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213427/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213425/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213428/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213426/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213423/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213424/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213422/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213420/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213419/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213421/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213415/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
Title:
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213418/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213410/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213413/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213414/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213412/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213411/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213416/+files/WifiSyslog.txt
** Tags removed: apport-collected trusty xenial
** Tags added: bionic
** Tags added: apport-collected trusty
** Description changed:
I have a system
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213409/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
Title:
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1803692/+attachment/5213408/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803692
apport information
** Tags added: apport-collected trusty
** Description changed:
I have a system containing two identical nvme devices. When booting a
trusty PXE image with kernel 4.4.0-38-generic both devices are detected
and available:
# nvme id-ctrl /dev/nvme0
NVME Identify
Public bug reported:
I have a system containing two identical nvme devices. When booting a
trusty PXE image with kernel 4.4.0-38-generic both devices are detected
and available:
# nvme id-ctrl /dev/nvme0
NVME Identify Controller:
vid : 0x8086
ssvid : 0x8086
sn : BTHH82250N1X1P0E
** Package changed: linux-lts-xenial (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743929
Title:
Kernel upgrade failing, trying to install Xenial Kernel, I am running
Public bug reported:
/etc/default/nfs-kernel-server invites you to pass additional arguments
to rpc.svcgssd by populating RPCSVCGSSDOPTS, e.g.:
RPCSVCGSSDOPTS="-n"
/lib/systemd/system/rpc-svcgssd.service passes additional arguments to
rpc.svcgssd from the variable $SVCGSSDARGS with the
This bug still appears to be present:
# apt-cache policy parted:
parted:
Installed: 2.3-19ubuntu1.14.04.1
Candidate: 2.3-19ubuntu1.14.04.1
Version table:
*** 2.3-19ubuntu1.14.04.1 0
500 http://apt.us.com:3142/ubuntu/ trusty-updates/main amd64 Packages
100
In my case the partition name is a zero length string but if I change it
then the output is correct.
This patch resolves the issue for me.
# diff -u parted-2.3/parted/parted.c parted-fixed/parted/parted.c
--- parted-2.3/parted/parted.c 2016-02-02 10:01:50.0 +
+++
I have built the xen sources from wily with the following patch to
enable HVM guest UEFI support:
diff -ur xen-4.5.0.orig/debian/control xen-4.5.0/debian/control
--- xen-4.5.0.orig/debian/control 2015-02-24 18:14:03.0 +
+++ xen-4.5.0/debian/control2015-04-11
I have built the xen sources from wily with the following patch to
enable HVM guest UEFI support:
diff -ur xen-4.5.0.orig/debian/control xen-4.5.0/debian/control
--- xen-4.5.0.orig/debian/control 2015-02-24 18:14:03.0 +
+++ xen-4.5.0/debian/control2015-04-11
Public bug reported:
The maxlength function to construct the bubble calculates string length
including escape sequences so although the colours are printed in the
output the surrounding bubble is malformed, e.g.:
$ figlet Hello World! | toilet -f term --metal | /usr/games/cowsay -n
This can be
Support for older versions of perl
** Patch added: perl-older-versions.diff
https://bugs.launchpad.net/ubuntu/+source/cowsay/+bug/1437804/+attachment/4359603/+files/perl-older-versions.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
From the man page:
-o print only subvolumes bellow specified path. [sic]
What it does with the default package:
root@ubuntu:/export/workspace# btrfs subvolume list -o .
ID 265 gen 221 top level 5 path ubuntu
ID 266 gen 218 top level 265 path ubuntu/precise
ID 268 gen 218 top level 266 path
Public bug reported:
btrfs subvolume list -o path should list only subvolumes below path
however it lists all subvolumes in the filesystem. This appears to be
fixed in upstream with http://git.kernel.org/cgit/linux/kernel/git/mason
/btrfs-progs.git/commit/btrfs-
We make our kernel tree with:
git clone -n git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git
cd ubuntu-precise
git remote add linux-stable
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
git fetch linux-stable
git checkout -b our-build Ubuntu-lts-3.8.0-13.22
git cherry-pick
The commit 7b2b160da7661bb2ade3f924b1bd3e3084e53341 cherry-picked
cleanly on top of the 3.8 LTS tree. I assumed it didn't make the
official 3.8 stable branch because it was EOL by the time it was
proposed for stable. Since we don't see the problem when we are on the
3.5 LTS kernel we didn't try
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1234662/+attachment/3863783/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234662
Title:
apport information
** Attachment added: HookError_cloud_archive.txt
https://bugs.launchpad.net/bugs/1234662/+attachment/3863778/+files/HookError_cloud_archive.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1234662/+attachment/3863777/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234662
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1234662/+attachment/3863780/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1234662/+attachment/3863779/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234662
apport information
** Tags added: apport-collected
** Description changed:
- We observed a problem with a Postfix database file created by postmap
- becoming corrupted in a Xen guest when the file was on an ext4
- filesystem with a 1kb block size. This was reported to the linux-ext4
- list in
I can't install apport on the original system where this problem was
observed (Precise + LTS kernel) but I have reproduced it on a Raring
install with 3.8.0-31-generic and submitted the apport information from
that environment.
--
You received this bug notification because you are a member of
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1234662/+attachment/3863782/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234662
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1234662/+attachment/3863784/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1234662/+attachment/3863781/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234662
@James Page
We moved our platform to 13.04 for other reasons and we stopped seeing
this issue due to a newer ovs release. I will try to find a system with
12.04 to test the proposed fix but I may not be able to do this
immediately.
James
--
You received this bug notification because you are a
@James Page
We moved our platform to 13.04 for other reasons and we stopped seeing
this issue due to a newer ovs release. I will try to find a system with
12.04 to test the proposed fix but I may not be able to do this
immediately.
James
--
You received this bug notification because you are a
I have tested this new version and it resolves the problem that we were
experiencing with certificate authenticated apt repositories.
Thanks,
James
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
We are currently facing an issue in Precise using certificate
authenticated apt repositories. It seems that this problem with the
gnutls library is the root cause of the issue that we are seeing.
Although upgrading to a different Ubuntu release would be a solution for
us it is significantly
Public bug reported:
When using Xen and OVS a log flood occurs (approx 10 entries /s) when
using stubdom based HVM guests with PV drivers. This issue was reported
to the OVS developers
(http://openvswitch.org/pipermail/dev/2013-February/025586.html) and a
fix was merged for the 1.4.6 release.
1 - 100 of 104 matches
Mail list logo