** Summary changed:
- Network manager unable to control wifi after suspend in 16.04
+ Network manager applet unable to control wifi after suspend in 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Patch added: "partman-auto-lvm.merge.debdiff"
https://bugs.launchpad.net/ubuntu/+source/partman-auto-lvm/+bug/1581595/+attachment/4664860/+files/partman-auto-lvm.merge.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Patch removed: "partman-auto-lvm.merge.debdiff"
https://bugs.launchpad.net/ubuntu/+source/partman-auto-lvm/+bug/1581595/+attachment/4664860/+files/partman-auto-lvm.merge.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Patch added: "partman-auto-lvm.merge.debdiff"
https://bugs.launchpad.net/ubuntu/+source/partman-auto-lvm/+bug/1581595/+attachment/4664867/+files/partman-auto-lvm.merge.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
@aeaeaeaeaeae, virbr0 is owned/created by libvirt as the default network
for kvm. This issue very likely unrelated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576747
Title:
Network manager unab
I just tried 1.2.0-0ubuntu0.16.04.2, shutdown, started up, suspended
resumed, and still see this issue.
I'm sorry, I haven't had more time to debug this myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Can you please test version 1.0.6-2ubuntu0.14.04.4 from
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214
This is now available in the most recent trusty archives.
The bug doesn't look to be too related, but the underlying change
modifies the way numa nodes are processed.
Thanks,
I'll move this to Fix Released, if this is not resolved via the above
mentioned fix please switch it back to confirmed.
** Changed in: irqbalance (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: irqbalance (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug n
Public bug reported:
Test case
# sudo apt-get install linux-crashdump
set USE_KDUMP=1 in /etc/default/kdump-tools
echo 1 | sudo tee /proc/sys/kernel/sysrq
echo c | sudo tee /proc/sysrq-trigger
It looks like there was insufficient memory devoted to the crash kernel.
The defaults were used, and th
Other kernel combinations may also be affected.
** Description changed:
Test case
# sudo apt-get install linux-crashdump
set USE_KDUMP=1 in /etc/default/kdump-tools
+
+ # sudo shutdown -r now
+
echo 1 | sudo tee /proc/sys/kernel/sysrq
echo c | sudo tee /proc/sysrq-trigger
It l
It was also suggested that
nr_cpus=1 and or kvm_cma_resv_ratio=0 should be considered for defaults for
the crash kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567539
Title:
Failure to du
According to
https://wiki.ubuntu.com/ppc64el/Recommendations#Crash_Kernel_recommendations
it looks like the following should be used.
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
These should be made as defaults for crash on ppc64 at the very least.
--
You receiv
This really seems to be an issue with packer, and not the Ubuntu
installer.
May I suggest a better alternative. Instead of using packer why not use the
ubuntu cloud images available
http://cloud-images.ubuntu.com/
or use virt-install and the netboot installers a.la.
virt-install \
--c
For those affected by this in xenial, I have created a PPA with fips
removed from the openssl binaries.
See it here.
https://launchpad.net/~chiluk/+archive/ubuntu/openssl+nofips
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5
*
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: New
** Tags: sts
** Attachment added: "Additiona
Shut the front door bug-bot.
** 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/1616193
Title:
3.13: libvirtd: page allocation failur
Fix submitted to kernel-t...@lists.ubuntu.com.
** Description changed:
- [Impact]
- * libvirtd is no longer able to open the vhost_net device. This causes the
guest VM to hang. This happens if memory becomes fragmented to the point where
vhost_net_open is not able to successfully kmalloc.
+
It's possible. I'll mark this as a dupe once we know more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576747
Title:
Network manager unable to control wifi after suspend in 16.04
To manage noti
So it looks as though I'm able to reproduce this by
1. Connecting to wifi access point
2. Suspend
3. Move out of range, but in range of another saved access point.
4. Resume.
My computer automatically connected to the new access point, but does
not show any information to that effect.
I'm not su
Public bug reported:
After resume from suspend network manager no longer allows me to control
my wifi card, view available wireless networks, or select new ones.
Oddly enough, I'm still able to communicate on the network that I was
connected to prior to suspend.
Running
# sudo service network-man
Public bug reported:
[Impact]
* zfs services fail on firstboot if zfs-utils is integrated into the
deployment image.
* Output from systemd -
sudo systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● zfs-import-scan.service loaded failed failed Import ZFS pools by device
scanning
● zfs-mo
Personally I think we should modify MNTTAB in zfs-linux to point to
/proc/self/mounts. This may not be completely straightforward *(there
are a number of places that point to /etc/mnttab directly, or have logic
around it and /proc/mounts), but it should be doable. I like this
solution most becaus
I was able to remove the nvidia card from my desktop and check again.
Removing the nvidia card and enabling the integrated graphics resulted
in my machine reaching pc6. So I'll leave this as expired for the time
being.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576692
Title:
fully support package installation in systemd
To manage notifications about this bug go to:
https://bugs.launchpad.ne
IMEI firmware update definitely appears to be the fix as it is now verified
independently.
https://bugzilla.kernel.org/show_bug.cgi?id=116591
** Bug watch added: Linux Kernel Bug Tracker #116591
http://bugzilla.kernel.org/show_bug.cgi?id=116591
--
You received this bug notification because y
** Patch removed: "lp1631474.yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757084/+files/lp1631474.yakkety.debdiff
** Patch removed: "lp1631474.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+att
Updated debdiff to handle ip=:bootif use case.
** Patch added: "lp1631474.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759967/+files/lp1631474.xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bu
** Patch added: "lp1631474.yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759968/+files/lp1631474.yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
I have uploaded a new version of initramfs-tools to my ppa, I would
again appreciate testing on this. Notably I fixed an bug that was
causing all_netbootable_devices to be tried instead of the interface
specified on the command line.
I also now handle the case where ip=:bootif , which really
** Description changed:
[Impact]
- * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
+ * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
ip=dhcp or ip=:eth0:dhcp
- * Regression-updates
+ * Regression-updates
- * The fix better parses the ip= co
I tested maas's command line as well.
/proc/cmdline from a maas pxe boot is
BOOT_IMAGE=ubuntu/amd64/hwe-y/yakkety/daily/boot-kernel nomodeset
iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily
iscsi_target_ip=192.168.1.5 iscsi_target_port=3260 iscsi_initiato
** Description changed:
[Impact]
* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
ip=dhcp or ip=:eth0:dhcp
* Regression-updates
* The fix better parses the ip= command line argument.
[Test Case]
* Create a machine that boots using an nfsroot.
Regression tracked via bug #1631474
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628306
Title:
network booting fails for iscsi root if no ip is set
To manage notifications about this bug go to:
h
With my recent update to Yakkety I no longer seem to be experiencing
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/1589401
Title:
cannot view wifi networks after re-enabling wifi
To man
I spoke too soon still exists in Yakkety.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
To manage notifications about this bug go to:
Alright so the problem at present appears to be that the machine is pxe
booting off of a nic with a mac address that is not showing up after the
kernel boots.
The way the boot works is the bios/efi launches a pxe network stack.
This typically makes a dhcp request. The DHCP server responds with an
possibly also
the firmware of the usb-c device?
Thanks,
Dave Chiluk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639202
Title:
Cannot enlist/commission machines in MAAS 2.1 with usb network adapter
To
Another thought is that the pxe firmware of the usb-c device was missed
in the rebranding process by dell. This is actually quite likely in my
opinion.
Either way we need to engage Dell in order to remedy this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
So apparently this is a feature of the dell-branded usb-c devices.
Please see the knowledge base.
http://www.dell.com/support/article/us/en/04/SLN301147
I've heard back from our contacts at dell, and the issue you are seeing
is apparently resolved via a firmware update.
--
You received this bug
Tested trusty. Trusty not affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634304
Title:
Unable to complete install: 'Couldn't find hvm kernel for Ubuntu tree
To manage notifications about
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644351
Title:
Offer both the GA and HWE Kernel for 16.04.2 server images
To manage notifications about this bug go to:
https://bugs
It will be fixed as soon as I can get sponsorship for my debdiffs.
** Changed in: virt-manager (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: virt-manager (Ubuntu Yakkety)
Status: New => Incomplete
** Changed in: virt-manager (Ubuntu Yakkety)
Status: Incomplete => C
Updated changelog entry for debdiffs.
** Patch removed: "lp1634304.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1634304/+attachment/4784828/+files/lp1634304.xenial.debdiff
** Patch removed: "lp1634304.yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+sourc
Updated changelog, and renamed patch so it's obvious that this patch
applies to be yakkety and zesty.
** Patch added: "lp1634304.zesty+yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1634304/+attachment/4788762/+files/lp1634304.zesty+yakkety.debdiff
** Tags added:
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
** Changed in: maas-images
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/1639202
Title:
Cannot en
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634304
Title:
Unable to complete install: 'Couldn't find hvm kernel for Ubuntu tree
To manage notifications abo
** Description changed:
[Impact]
- * On Xenial after installing lvm2, you must reboot before you are able to
run vgcreate.
- * The package installer should be starting lvmetad.service.
- * $ sudo vgcreate localvg
- /run/lvm/lvmetad.socket: connect failed: No such file or directory
-
I deployed a trusty vm, and checked the logs for the error, and did not
see it so I'm marking this verification-done.
** 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
So I've been doing a lot of work in this area recently. After looking
closely through partman-partitioning, and create_new_label forces a gpt
partition table if the volume is above 2TB. This makes sense, since
disks >2TB tend to have issue with msdos partition tables.
Unfortunately my slightly ol
Public bug reported:
[Impact]
* On Xenial after installing lvm2, you must reboot before you are able to run
vgcreate.
* The package installer should be starting lvmetad.service.
* $ sudo vgcreate localvg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed
Public bug reported:
VIA VL812 hub stops working with 4.4.0-40.60. Works fine with
4.4.0-39.59.
Logs include both boot with 4.4.0-39 *(most recent) and 4.4.0-40
(previous boot).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.40.42
ProcVersionSignature: Ubuntu 4.
So I just rebooted 4 times with the -40 kernel, and everything seems to
be going well. I'm going to chalk this one up to hardware misbehaving.
At least until someone else hits this as well.
Keep in mind the hub, does not work in usb 3.0 mode. That is not what
this bug is about.
--
You received
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628363
Titl
This really should have been worked via one of the myriad of other older
open bugs related to this, like 1576747. I'll start duping against this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585
*** This bug is a duplicate of bug 1585863 ***
https://bugs.launchpad.net/bugs/1585863
This appears to be getting some progress via 1585863, so I'm marking it
as a dupe, even though this one is older.
** This bug has been marked a duplicate of bug 1585863
WiFi malfunction after suspend & r
The above patches do not resolve this issue for my machine. de-duping
1576747.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585863
Title:
WiFi malfunction after suspend & resume stress
To manage
I went tested the patches for 1585863, but still saw the issue.
** This bug is no longer a duplicate of bug 1585863
WiFi malfunction after suspend & resume stress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
@cyphermox
Here's the debug output we worked on today. I removed most everything
from before I suspended the machine. Everything remaining is either
from the suspend or the resume.
The output was achieved by adding --log-level=debug to
/lib/systemd/system/NetworkManager.service at the ExecStart
Public bug reported:
Ubuntu is detecting that my battery has depleted to low or 0% which
results in the OS forcing suspend. Normally this would be correct
behavior, but in my case the battery has closer to 90% of remaining
battery left.
I have experienced this with 4.4.0-22 and 4.4.0-23, and am
I received another update from the end user.
"A fresh 14.04.4 DVD Ubuntu install with updates (3.16.0-69 kernel) in a
diskful setup (no NFS, no aufs, 1T swap disk) also fails to kdump, either hangs
or OOMS."
My understanding is that it OOMS on too little crashkernel assignment,
hangs if enou
I can confirm that the following settings for crashkernel on powernv result in
the following console log.
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
I will now test with @32M options.
modoc login: [ 1374.418348] SysRq : Trigger a crash
[ 1374.418424] Unable to ha
2G:512M@32M,32G-64G:1024M@32M,64G-128G:2048M@32M,128G-:4096M@32M"
** Affects: grub2 (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: New
** Tags: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
It turns out I was hitting issues related to the following bug.
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1569567
I will rerun my test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567539
Apparently update-grub was using kexec-tools.cfg, and completely
ignoring /etc/default/grub as I expected. So that's the workaround, but
setting in /etc/default/grub should still work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
With
ubuntu@modoc:~$ cat /proc/cmdline
root=/dev/mapper/mpath0-part2 ro console=hvc0
crashkernel=2G-4G:320M@32M,4G-32G:512M@32M,32G-64G:1024M@32M,64G-128G:2048M@32M,128G-:4096M@32M
I get the following console log
[ 191.833046] SysRq : Trigger a crash
[ 191.833117] Unable to handle kernel pagin
So it looks like this crashkernel argument is not resulting in any reserved
memory.
The correct crashkernel argument should look like this.
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@32M
Additionally my earlier failures here were the result of no reserved
memory b
I just verified on x86 + 14.04, and it looks like any changes to the
GRUB_CMDLINE_LINUX_DEFAULT do not end up making their way into
/boot/grub/grub.cfg.
It turns out /etc/default/grub.d/50-curtin-settings.cfg
sets GRUB_CMDLINE_LINUX_DEFAULT=""
I'm not exactly sure why this is, but I'll move this
This may also affect initramfs-tools, as that will likely be the place
that any fix needs to be implemented.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Reproducer
1. Deploy trusty on a multipath rooted machine *(tested on ppc64el, may affect
x86 as well).
2. Install 3.16 kernel *(has not been verified with other kernels).
3. sudo apt-get install linux-crashdump
4. Set USE_KDUMP=1 in /etc/default/kdump-tools
5. Set
cras
Reproduced on
maas1.9.0+bzr4533-0ubuntu1~trusty1
python-curtin 0.1.0~bzr314-0ubuntu1
Attached is the output requested.
http://paste.ubuntu.com/15855923/
** Attachment added: "node-config.txt"
https://bugs.launchpad.net/ubuntu/+source/cur
Sorry Joe, this may be related to userspace as well, as I was able to
reproduce this with other kernels as well. Although not as reliably.
** Also affects: indicator-power (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubun
** Summary changed:
- Incorrect low-battery detected forcing suspend
+ Incorrect 0% remaining battery detected forcing suspend
** Changed in: indicator-power (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
So as I haven't really messed with power monitoring, I discovered upower
--monitor-detail.
After having been unplugged for a few minutes the below state change
occurred. I'm open to advice on how to continue looking into this. My
first guess is to open the upower sources to see where it's gettin
Running 4.4.0-23-generic, I see the same errors as
https://bugs.freedesktop.org/show_bug.cgi?id=89055
I see
[ 1248.953987] PM: early resume of devices complete after 6.795 msecs
[ 1248.956059] rtc_cmos 00:02: System wakeup disabled by ACPI
[ 1249.227488] usb 1-8: reset high-speed USB device numbe
Here's a log of me pulling power, and plugging it back in.
** Also affects: upower (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "upower.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588944/+attachment/4679103/+files/upower.out
--
You received this b
fantastically. Shame on me for suspecting our beloved
OS.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: upower (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed i
@Greg
Our Haswell servers aren't seeing this, but one of my desktops is.
By chance do you happen to have an nvidia card in that machine? I've
been meaning to rip it out of my desktop and try again, but I haven't
found the time.
Also please run apport-collect and upload the logs to this case.
T
So I recently had to run a certain Microsoft OS while debugging another
issue. I ran a number updates during that session. The most important
of which was an IMEI firmware update. I can't prove for certain that
the IMEI firmware update resolved this issue, but it is the mostly
likely considering
Sorry hit post too quickly.
Anyhow, so it looks like upgrading the IMEI firmware now allows my
amt/vpro capable laptop to reach low-power power pc-states.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
In case anyone else hits this on their laptop and would like to disable
the auto-suspend, I installed dconf-editor, and changed critical-
battery-action to nothing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
So I don't seem to be able to reproduce this any more. I did recently
boot windows on my laptop, and then ran updates. I no longer seem to be
able to reproduce this issue.
One of the important updates was an update to the IMEI firmware on my
machine. Can someone else on this bug please upgrade
There is a firmware component for IMEI. If I'm not mistaken the IMEI
firmware is what is responsible for vpro / AMT functionality. According
to this FAQ https://software.intel.com/en-us/articles/intel-vpro-
technology-faq, it is capable of controlling a wireless card even while
in sleep states.
Mingming, did you just create an empty file?
I did that, and it removed my warnings, but did not fix my program.
This is still an issue. the im-ibus.so should be getting included in
ia32-libs, as there now appears to be some dependency on it.
Also I just verified that this still exists running t
Public bug reported:
Binary package hint: ia32-libs
When trying to execute my 32-bit application under maverick, I get the
following errors. I have ia32-libs installed, but the loader is trying
to load the 64-bit ones.
chi...@blackandblue:/opt/agns/bin$ file ./agnclient
./agnclient: ELF 32-bit
Upon further inspection this may be an issue with the libraries
themselves not loading the correct binaries *(I'm not sure how that
trickle down loading all works).
Here's my ldd output for agnclient. Conspicuously absent is a line for
libpixbufloader-png.so. and libpixbufloader-svg.so which lea
** Tags added: ua
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302605
Title:
Calls to /libx32/ld-linux-x32.so.2 hang when using auditd
To manage notifications about this bug go to:
https://bugs.l
** Also affects: linux-lts-trusty (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-lts-trusty (Ubuntu Lucid)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Saucy)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Utopic)
Public bug reported:
How to reproduce with linux-lts-trusty
1. Enable "wake on lan" in bios
2. Boot *(however you want to boot)
3. Check that device supports wakeonlan
ethtool eth0
# the Wake-on: setting should include g
4. shutdown -h now
5. wakeonlan -i
in my case
/usr/bin/wakeonlan -i 1
Looks like this is already resolved in mainline v3.17-rc2-utopic. I
will bisect how upstream resolved the issue
** Tags added: kernel-bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363361
Title:
v3.14.17-utopic - fails
v3.15-rc1-trusty - is fixed
Now for bed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363361
Title:
Machine does not wake up to wakeonlan magic packets after shutdown -h
hopefully this is quite a bit more isolated than I originally
believed.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: linux-lts-trusty (Ubuntu)
Assignee: (unassig
On 08/12/2015 03:59 AM, Andrei Demin wrote:
> Seems Samsung fixed this bug in kernel
> (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f3f5da624e0a891c34d8cd513c57f1d9b0c7dadc)
> and blacklist is no longer needed. Maybe we should remove blacklist and
> apply this patch i
** Description changed:
[Impact]
- * df displays bind mounts instead of "real" mounts if the bind mount is
+ * df displays bind mounts instead of "real" mounts if the bind mount is
mounted to a shorter directory.
- * justification - This is a change of behavior from precise
+ * justi
Fixed version and added origin information to debdiff.
** Patch removed: "lp1432871.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1432871/+attachment/4351938/+files/lp1432871.trusty.debdiff
** Patch added: "lp1432871.trusty.debdiff"
https://bugs.launchpad.net/ub
I've integrated the 9a9324d396967 NO NCQ Trim fix into this ppa.
https://launchpad.net/~chiluk/+archive/ubuntu/samsungncqtrim
Please test it and report back here either way. I'll remove the ppa
when the fix hits the kernels in -updates.
--
You received this bug notification because you are a m
*** This bug is a duplicate of bug 1338706 ***
https://bugs.launchpad.net/bugs/1338706
** This bug has been marked a duplicate of bug 1338706
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set
xfermode (err_mask=0x40) on upstream kernels >= 3.12
--
You received this
** Changed in: linux (Ubuntu)
Milestone: None => trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
** Description changed:
+ [Impact]
+
+ * Users with Samsung 8** SSD drives see miscellaneous errors and
+ warning messages in the logs depending on the firmware level of the
+ drive while booting or after running trim.
+
+ [Test Case]
+
+ * Run this script, and then check logs for errors.
+ #
** Description changed:
[Impact]
- * Users with Samsung 8** SSD drives see miscellaneous errors and
+ * Users with Samsung 8** SSD drives see miscellaneous errors and
warning messages in the logs depending on the firmware level of the
drive while booting or after running trim.
[Tes
** Tags added: cts sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460737
Title:
[SRU] MAAS 1.7.5
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bu
301 - 400 of 946 matches
Mail list logo
