SRSI Support was added to the upstream kernel in November 2013. The
Ubuntu Trusty kernels got this support for 'free'.
Checked the source code for Trusty to verify it was there:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
trusty.git;a=commitdiff;h=8f8b899563f28ef26e381a6eb90d12dead77389f
Verified on precise with both the stock precise kernel as well as the
hwe-Trusty kernel. In both cases the openipmi service started without
issues.
Thanks!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of
The OpenIPMI portion of this issue now seems to be fixed in Utopic
Trusty and I will try and verify the fix for Precise:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verified on precise with both the stock precise kernel as well as the
hwe-Trusty kernel. In both cases the openipmi service started without
issues.
Thanks!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of
** Changed in: dell-poweredge
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349920
Title:
ledmon does not work in Ubuntu 14.04
To manage notifications
Package tested was:
http://launchpad.net/ubuntu/+source/ledmon/0.79-0.2ubuntu0.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349920
Title:
ledmon does not work in Ubuntu 14.04
To manage
To clarify further this was tested on 13G hardware as well as 12G. My
mention of 12G was to ensure that there were no regressions with
existing hardware. 13G hardware is also working fine with the patched
package.
--
You received this bug notification because you are a member of Ubuntu
** Patch added: fix-ledmon-trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1349920/+attachment/4166671/+files/fix-ledmon-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
New debdiff for Trusty
** Patch removed: fix-ledmon-trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1349920/+attachment/4166199/+files/fix-ledmon-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There is a ledmon 0.79-2 uploaded to Debian with the fix. Waiting for
it to show up.
Not sure if we need to sync that or just apply the attached Utopic
debdiff.
** Patch added: fix-ledmon-utopic.debdiff
To clarify further this was tested on 13G hardware as well as 12G. My
mention of 12G was to ensure that there were no regressions with
existing hardware. 13G hardware is also working fine with the patched
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
For Utopic, all that needs to be done is sync the latest package with
Debian. For Trusty we need to pull in the upstream patch then test it
out.
** Description changed:
ledmon will not work in Ubuntu 14.04, due to a change in kernel 3.13.
I've tested this with ICH10R and C600/X79
** Description changed:
ledmon will not work in Ubuntu 14.04, due to a change in kernel 3.13.
I've tested this with ICH10R and C600/X79 chipset.
Symptoms: ledctl gives 'enclosure management not supported' on supported
hardware.
This problem has just been fixed by upstream, see
debdiff for trusty
** Patch added: fix-ledmon-trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1349920/+attachment/4166199/+files/fix-ledmon-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
the not supported message on
the console.
** Changed in: dell-poweredge
Status: New = Confirmed
** Changed in: dell-poweredge
Status: Confirmed = In Progress
** Changed in: dell-poweredge
Importance: Undecided = High
** Changed in: dell-poweredge
Assignee: (unassigned) = Kent
Tested on Dell Hardware, paying particular attention to existing 12G
systems so that nothing 'broke' with the update. Looking good.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Tested on Dell Hardware, paying particular attention to existing 12G
systems so that nothing 'broke' with the update. Looking good.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736
It's better we can have it in 14.04 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+subscriptions
--
Kent Baxley
Field Engineer, Canonical
kent.bax...@canonical.com
Updated description with required SRU fields. Please let me know if I
need to add anything else. Thanks for your help, Robie!
** Description changed:
The 13G line of Dell PowerEdge servers will be rolling out later this
year.
A patch was submitted upstream recently to add support into
@Gabriele and anyone else that sees power consumption problems,
Please open a separate bug on the power consumption. This issue is to
inclue driver support for the touchpad, which Synaptics continues to
work on / refine upstream.
--
You received this bug notification because you are a member
Updated description with required SRU fields. Please let me know if I
need to add anything else. Thanks for your help, Robie!
** Description changed:
The 13G line of Dell PowerEdge servers will be rolling out later this
year.
A patch was submitted upstream recently to add support into
Yes, I have done some testing on new generation as well as current
generation systems with the patch, with emphasis on the delloem
commands, since that's what the patches touch the most. Everything
seems to be working fine on both sets of hardware.
I'm fine with whatever direction ulitmately
Yes, I have done some testing on new generation as well as current
generation systems with the patch, with emphasis on the delloem
commands, since that's what the patches touch the most. Everything
seems to be working fine on both sets of hardware.
I'm fine with whatever direction ulitmately
Public bug reported:
The 13G line of Dell PowerEdge servers will be rolling out later this
year.
A patch was submitted upstream recently to add support into ipmitool for
these new servers:
http://sourceforge.net/p/ipmitool/patches/102/
We need to get this into ipmitool for Trusty and Utopic so
Debdiff for trusty
** Patch added: ipmitool-trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+attachment/4154821/+files/ipmitool-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool
Utopic Debdiff
** Patch added: ipmitool-utopic.debdiff
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+attachment/4154831/+files/ipmitool-utopic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in
Hey Michael,
Looks good now! Thanks for your help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335324
Title:
Update wsmancli to 2.3.1 for Utopic
To manage notifications about this bug go to:
Public bug reported:
The 13G line of Dell PowerEdge servers will be rolling out later this
year.
A patch was submitted upstream recently to add support into ipmitool for
these new servers:
http://sourceforge.net/p/ipmitool/patches/102/
We need to get this into ipmitool for Trusty and Utopic so
Debdiff for trusty
** Patch added: ipmitool-trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+attachment/4154821/+files/ipmitool-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Utopic Debdiff
** Patch added: ipmitool-utopic.debdiff
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+attachment/4154831/+files/ipmitool-utopic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
It appears we don't set the CONFIG_GPIO_SYSFS on Trusty (or Utopic?) for
x86.
By enabled, I mean:
CONFIG_GPIO_SYSFS=y
This option (along with a few gpio devices) is needed to enable
programming of such things as the I2C Mux through via the CPLDs on some
OEM 'whitebox'
Run quilt pop -a on the openwsman 2.4.3 sources before applying the
debdiff above for 2.4.7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1334832
Title:
Update to upstream 2.4.7 for Utopic
To
Request to turn on a kernel config option. No logs required.
** 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/1342153
Title:
Try the script mentioned above and post the output:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1321885/comments/22
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1321885
Try the script mentioned above and post the output:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1321885/comments/22
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321885
Title:
IPMI
Hi Michael,
Thanks for the review and cleanup. No worries on the length. The build
you have from the source tarball from github indeed builds, but, none of
the executables are generated in order to run wsman...for example, after
installing or upgrading to your package on a Utopic test box,
** Patch added: openwsman.debdiff
https://bugs.launchpad.net/ubuntu/+source/openwsman/+bug/1334832/+attachment/4149603/+files/openwsman.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks, Adam.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1332187
Title:
driver-injection-disk script needs to support disk and usb-partition
devices
To manage notifications about this bug go
Tested the trusty-proposed package with two scenarios:
1) Whole-disk with an OEMDRV label (i.e. /dev/sdb) and driver packages
contained therein.
2) usb-partition with an OEMDRV labe (i.e. /dev/sdb1) and driver
packages contained therein.
In both cases the new driver injection disk package
Sanity-checked package updates. Diff can be found here:
https://launchpad.net/~kentb/+archive/wsman-upstream/+files/cim-
schema_2.38.0-0ubuntu2_2.41.0-0ubuntu1.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Diff can be located here:
https://launchpad.net/~kentb/+archive/wsman-
upstream/+files/wsmancli_2.3.0-0ubuntu4_2.3.1-0ubuntu1.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335324
Title:
Tested packages to ensure things still worked after an upgrade. Diff
can be located here:
https://launchpad.net/~kentb/+archive/wsman-upstream/+files/sblim-
sfcc_2.2.6-0ubuntu2_2.2.7-0ubuntu1.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tested packages from my ppa to ensure everything still worked after an
upgrade. Diff can be located here:
https://launchpad.net/~kentb/+archive/wsman-upstream/+files/sblim-
sfcb_1.4.6-0ubuntu4_1.4.8-0ubuntu1.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Took a shot at trying to address this. We'll see what the maintainers
say.
** Branch linked: lp:~kentb/maas/bug-1321885
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1321885
Took a shot at trying to address this. We'll see what the maintainers
say.
** Branch linked: lp:~kentb/maas/bug-1321885
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321885
Title:
IPMI detection
Fixed the bug title from the original reporter so that it's easier to
find.
** Summary changed:
- IMPI detection and automatic setting fail in ubuntu 14.4 maas
+ IPMI detection and automatic setting fail in ubuntu 14.04 maas
--
You received this bug notification because you are a member of
grick23's workaround also seems to 'fix' this for a PowerEdge R805.
Previously, this machine also had trouble with MAAS auto-detecting the
IPMI settings with 14.04. So, it looks like many Dell 10th generation
(10G) and older machines will run into problems based on the type of
DRAC / BMC
@Sarubh,
Please file a separate bug for your issue as your touchpad does not
appear to be the same as what's being worked on here. Alternatively,
you can add your comments to this bug, which I think covers your
touchpad device:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307015
--
** Changed in: dell-poweredge
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253443
Title:
failure writing to sector error at boot with Advanced Format
Fixed the bug title from the original reporter so that it's easier to
find.
** Summary changed:
- IMPI detection and automatic setting fail in ubuntu 14.4 maas
+ IPMI detection and automatic setting fail in ubuntu 14.04 maas
--
You received this bug notification because you are a member of
grick23's workaround also seems to 'fix' this for a PowerEdge R805.
Previously, this machine also had trouble with MAAS auto-detecting the
IPMI settings with 14.04. So, it looks like many Dell 10th generation
(10G) and older machines will run into problems based on the type of
DRAC / BMC
If the 1950's and 1750's are having problems, what type of response do
you get from this command?:
ipmipower -h bmc ip address -u bmc username -p bmc password --stat
Preferably you'll want to run that from the maas server running 14.04.
On a very basic level, that's what MAAS is using to bring
..and if that doesn't work, then try:
ipmipower -D LAN -h bmc ip address -u bmc username -p bmc password
--stat
Plus, I know these machines are older, but, is the latest BMC firmware
installed on these affected systems?
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Latest release is 1.4.8. Laundry list of bug fixes since 1.4.6 and a
few new features:
* new features:
- [sfcb-tix:#99] Add config property enableSslCipherServerPref
- [sfcb-tix:#101] Add config property indicationCurlUseExpect100
- [sfcb-tix:#102] Add config
Public bug reported:
Changes in 2.2.7
New Features:
- [bugs:#2692] SFCC: SfcbLocal interface should expose markHeap() and
releaseHeap()
Bugs:
- [bugs:#2728] Missing tag definition for REFARRAY
- [bugs:#2729] Improper type handling for EmbeddedObject in PARAMVALUE
-
Builds of upstream sblim-sfcb for Utopic can be found here:
https://launchpad.net/~kentb/+archive/wsman-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335907
Title:
Update to version
Utopic test builds can be located here:
https://launchpad.net/~kentb/+archive/wsman-upstream/+packages
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335941
Public bug reported:
Update cim-schema to version 2.41.0 for Utopic so that we are in sync
with the latest upstream releases.
Updates since 2.38.0:
Core/CIM_ProtocolService.mofCIMCoreCR01945.001 Errata: Remove Min(1)
on CIM_ProtocolService.MinValue( 1)
Core/CIM_ProtocolService.mof
Updated packages currently housed here for review and testing:
https://launchpad.net/~kentb/+archive/wsman-upstream/+packages
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed error is gone with the grub2 from proposed on Advanced Format
Drives.
** 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.
Specific version is 1.99-21ubuntu3.15 for Precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253443
Title:
failure writing to sector error at boot with Advanced Format Disks
To manage
If the 1950's and 1750's are having problems, what type of response do
you get from this command?:
ipmipower -h bmc ip address -u bmc username -p bmc password --stat
Preferably you'll want to run that from the maas server running 14.04.
On a very basic level, that's what MAAS is using to bring
..and if that doesn't work, then try:
ipmipower -D LAN -h bmc ip address -u bmc username -p bmc password
--stat
Plus, I know these machines are older, but, is the latest BMC firmware
installed on these affected systems?
--
You received this bug notification because you are a member of Ubuntu
** Branch linked: lp:~kentb/ubuntu/utopic/openwsman/bug-1334832
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1334832
Title:
Update to upstream 2.4.7 for Utopic
To manage notifications about this
** Branch linked: lp:~kentb/ubuntu/utopic/hw-detect/bug-1332187
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1332187
Title:
driver-injection-disk script needs to support disk and usb-partition
Thanks, Adam. Refactored my bzr merge proposal to reflect a much
cleaner way to handle this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1332187
Title:
driver-injection-disk script needs to
Packages are brewing here:
https://launchpad.net/~kentb/+archive/wsman-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1334832
Title:
Update to upstream 2.4.7 for Utopic
To manage
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1334832
Title:
Update to upstream 2.4.7 for Utopic
To manage notifications about this bug go to:
Tested the upgrade from 2.4.3 to 2.4.7. All looks well.
Also confirmed that wsman continues to work OK after an update to 2.4.7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1334832
Title:
Public bug reported:
Version 2.3.1 was released a few months ago. Let's try and get it into
Utopic.
Fixes and features include:
- exit with non-zero code if connection fails
- read credentials from environment
wsman: WSMAN_USER, WSMAN_PASS, WSMAN_EVENT_USER, WSMAN_EVENT_PASS
** Changed in: dell-poweredge
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065281
Title:
Installer crashed when trying to partition 4k/4k sector hard
** Changed in: dell-poweredge
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215458
Title:
Auto-partitioning with LVM on Advanced Format Disks causes
*** This bug is a duplicate of bug 1331513 ***
https://bugs.launchpad.net/bugs/1331513
** This bug has been marked a duplicate of bug 1331513
14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Now that 12.04.4 is out, we can close this as the patches are in the LTS
Enablement kernels.
** Changed in: dell-poweredge
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Built packages are here:
https://launchpad.net/~kentb/+archive/wsman-upstream/+packages
Sanity checked that an upgrade from 2.3.0 works OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335324
Public bug reported:
A few bug fixes and new features:
2.4.7
- Bugfixes
- file authenticator: allow password hash of up to 128 characters
- libu: don't exit() on malloc errors
2.4.6
- Features
- Support large hashes (like SHA512) in file authentication
- use constant-time password
** Changed in: sblim-sfcc (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262346
Title:
Please update sblim-sfcc to latest upstream for trusty
To
Working on a reproducer. I've been able to set up the following:
A Xen HVM guest booting off of an iscsi-attached LVM LUN.
Guest is running Wheezy.
Dom0 is 12.04 on a PowerEdge R620, running the 3.11-based LTS kernels.
The eth1 NIC is being used for the iscsi traffic. This is one of the
@wonko,
If there's any more specific information about the Xen VM, please let me
know. What I'm looking for are any special storage or network drivers
that the VM is using outside of what the standard Xen VM would use. If
there's nothing special about the VM in that respect, then I'll continue
Hi Dan,
Here's how we ultimately got it working (for now):
1) Make sure there are no alsa daily builds installed on that laptop, including
any oem-audio daily build packages.
2) modify the alsa-base.conf file and add a comma before dell, like so:
model=,dell-headset-multi
3) reboot
4) Plug in
Understood. I didn't realize it was *that* specific. How big is the
database you are importing and is there anything special about the VM
itself? I'll try and get this as close as possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
14.04 LTS (and older) does not support driver injection via micro deb
(udeb) package when mounted from iLO virtual media.
iLO does not present an OEMDRV device with a partition, therefore, the
Ubuntu installer overlooks that media as being viable. Instead of a
/etc/modprobe.d/alsa-base.conf and add the line “options
snd-hda-intel model=dell-headset-multi”, reboot and test and see if it
works?
On 2014-06-19 19:28, Kent Baxley wrote:
Hi David,
I've had a report or two from some co-workers that own the Dell XPS 15
laptop that state
Bernard,
I may also want to go ahead and get a soup-to-nuts list of how to set up
a machine to reproduce this. I've got an R620 and access to an iscsi
volume in my lab. I'm trying currently to reproduce on a simpler scale,
but, not having much luck at this time (which is no surprise).
--
You
** Changed in: dell-poweredge
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331513
Title:
tg3 eth1: transmit timed out, resetting on BCM5720
To manage
Please also try with thethe lts-trusty kernels, ported to precise, which
are based on 3.13:
sudo apt-get install linux-generic-lts-trusty linux-headers-generic-lts-
trusty linux-image-generic-lts-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: linux (Ubuntu)
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/1331513
Title:
tg3 eth1: transmit timed out, resetting on BCM5720
To
I've updated my branch to break out each patch individually as well as
*only* include relevant stuff for security fixes.
I was unable to make any headway with upstream with regard to getting
help filing CVE's. Since these patches are already in upstream, I'm
hoping that we can include them
** Description changed:
- Upstream maintainer for openwsman has added in a bunch of security fixes
- after our security team conducted an audit of the code. There are still
- a few patches left to go, but, I would like to go ahead and include
- what's already upstream into the 14.04 release:
+
** Branch linked: lp:~kentb/ubuntu/trusty/openwsman/bug-1319098
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319089
Title:
Add security fixes from upstream
To manage notifications about this bug
Hi David, I still can't reproduce any jumpy mouse behavior on my
touchpad, even with your steps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305522
Title:
Backport Synaptics HID touchpad driver
Hi AceLan,
So far I can't reproduce the jumpy mouse issues.
@David,
If you have any more specifics about what will reproduce it or how long
it takes to see the issue after booting up and loggin in, I'll be glad
to try it out on my sample here. I've tried both single-finger tap as
well as
For those with the XPS 13's that still have a PS/2 interface showing up,
it looks as if that doesn't seem to 'break' anything. The model I have
in the lab has a much older touchpad firmware on it than the ones you
guys have, so, that may be why things are showing up on your systems
like they are.
Also for everyone that still sees a PS/2 device in xinput after applying
AceLan's kernels, can you please paste the output of the following
command in this bug?:
dmesg | grep psmouse
lsmod | grep psmouse
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks, all.
It turns out on my XPS 13 that I was booted to the wrong kernel, which
is why the PS/2 mouse device wasn't showing up. Once I booted into
Aclean's test kernel the PS/2 device shows up in xinput.
My dmesg output is the same as what Hans is seeing. The psmouse module
is loading up
AceLan and Arash,
I also have an XPS13 Haswell Edition in the Dell lab. This unit does
NOT reproduce what Arash is seeing with your test kernel. In other
words, the PS/2 mouse does not show up in the xinput list. For my
system, xinput reports things as I expect to see them.
The touchscreen
Sent requests in this morning. I'll start breaking things out once I
receive CVE numbers:
http://www.openwall.com/lists/oss-security/2014/05/19/8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok. I'll start working on this and have something early next week.
Thanks for all the pointers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319089
Title:
Add security fixes from upstream
To
Can't reproduce this on an XPS 15 here in the Dell lab.
This one has:
Intel Graphics
Qualcomm Wifi / bluetooth (I think Dell calls this the DW1420 or something like
that)
Quad-core i7
8GB RAM
Seagate 500GB Hybrid drive
I put it to sleep at 14:30 yesterday by closing the lid. At 15:30 today
I
Tested here with our lab sample. Touchscreen is working again and the
touchpad is working even better than it did with the previous test
kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305522
1 - 100 of 726 matches
Mail list logo
