** Also affects: dell-poweredge
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/1262290
Title:
[MIR] wsmancli
To manage notifications about this bug go to:
** 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/1065281
Title:
Installer crashed when trying to partition 4k/4k sector hard di
Confirmed 14.04 boots cleanly now. Thanks!
Will also test 12.04 when I see the notice go out on this bug report.
** 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 Ubun
Public bug reported:
Please update cim-schema to 2.38.0 for Trusty.
The package hasn't seen an update in over two years and it'd be nice to
try and stay in sync with upstream.
I have built and tested version 2.38.0 using packages from this PPA:
https://launchpad.net/~dell-poweredge-team/+archiv
Yes. You can get it here:
http://sourceforge.net/projects/sblim/files/development%20pkgs/sblim-cmpi-devel/2.0.3/sblim-cmpi-devel-2.0.3.tar.bz2/download
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12
Although it doesn't change the overall outcome with regard to booting
straight from the FusionIO card, it also looks like I can get past the
efivars error by passing "efi_no_storage_paranoia" at the kernel command
line at install time.
--
You received this bug notification because you are a membe
@Joshua,
To answer your question, it definitely looks as if the OS is using the
grub/ directory off the SATA disk get grub up and going in the case
where you have a parallel install of Ubuntu on the HDD in addition to
the FIO device. It is also pulling the kernel and initrd off of the
SATA disk.
** Changed in: dell-poweredge
Status: In Progress => 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/1207387
Title:
Please update pciutils for 12.04.3
To manage notifications abou
** Changed in: dell-poweredge
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206602
Title:
Add hotplug support for Micron's PCIe-SSD devices
To manage notifi
Turns out these patches were too invasive to port to 13.04. They do
look to be in 13.10 and these should also be available in the 12.04.4
Saucy HWE kernel once it releases in January.
** Changed in: dell-poweredge
Status: In Progress => Fix Committed
--
You received this bug notification
** 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/1215458
Title:
Auto-partitioning with LVM on Advanced Format Disks causes
pa
For 13.10, I confirmed that the new grub2 packages allow us to fully
boot into the operating system (yay!!).
This is true for both LVM and non-LVM auto-partitioning options.
Thanks for all of your help, Colin.
I'll also test what fixes are present for 12.04.
--
You received this bug notificati
I tried today's build of 12.04, which seemed to have the two fixes
committed yesterday.
The installer completed OK, but, it appears that the EFI boot entry
somehow didn't get set..In other words, the server couldn't find
anything to boot from and, upon further inspection, there was no
'ubuntu' ent
some style problems using kernel's checkpatch.
* Remove indentation info
* Correct indentation according to the Linux coding style using indent
* Update Copyright year to 2013
* Fix support for Dell PCIe SSD Devices
* More minor fixes revealed by a coverity scan
* Minor fixes reveale
Verified that partman-basicfilesystems didn't cause any regressions with
the installation and LVM. I will try the ubiquity fixes tomorrow.
--
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:
With today's Precise Server image I can now boot the Operating System!
I do, however, see one seemingly minor error pop up as soon as I select
Ubuntu in the gru menu:
error: efidisk write error
Press any key to continue
The system will boot up after about 10 seconds.
I'm wondering if it i
I don't see any issues with ubiquity with regard to this issue, so, I'll
mark 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.
https://bugs.launchp
@Brandon,
Thanks for testing that on Precise. I also assume that you were able to
successfully boot from that point (I think the efi module for the fio
device has to be loaded by hand)? I just want to confirm so that way I
won't be testing the same thing twice.
Once the grub2 fixes go out for
@Brandon,
No thoughts on that without seeing the actual output of what happened
during boot. The driver disk is certainly the way to go for this. I
think I have a theory on what that might be with regard to your boot
failure. I need to test it first, though.
--
You received this bug notificat
@Brandon,
I was able to successfully boot into 12.04. The trick, I think, is that
you need two sets of driver disks in order to pull this off.
I tested this on a PowerEdge C8000 series server, which allowed me to
boot trouble-free into an EFI shell to load the Fusion-io.efi module.
The reason i
We got some additional help from Stuart Hayes at Dell. After some
analysis and testing, he got the 4k drive to boot by creating a larger
fat32 partition than what we're creating right now:
The version of Ubuntu that you gave me (13.10) was creating a FAT32
filesystem (on the EFI system partition)
For 12.04.3, we'll also need whatever fixes are necessary for the fat32
system partition plus these two fixes so that 4k drives are handled
correctly. The partman-base fix should take care of the installer not
properly detecting the size of the disk.
---
partman-base (163ubuntu2) rar
We also ran into another segfault with 13.10 when trying to auto-
partition with LVM on these drives. I'll attach a crash file in a
little while. Auto-partitioning without LVM works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Here is the specific commit for partman-base that needs to be ported to
12.04:
http://bazaar.launchpad.net/~ubuntu-core-dev/partman-
base/ubuntu/revision/1377
For efibootmgr, it is this one:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/raring/efibootmgr
/raring-proposed/revision/17
Both
Here is the crash file from 13.10 when selecting lvm in the partitioning
phase. parted_server is what segfaults.
** Attachment added: "_bin_parted_server.0.crash"
https://bugs.launchpad.net/oem-priority/+bug/1065281/+attachment/3766384/+files/_bin_parted_server.0.crash
--
You received this
Here's what parted sees from a successful RHEL6.4 install:
NumberStart End Size File system Name
Flags
11049KB211MB 210MB
boot
2211MB 735MB524MB
@James, Thanks. I'll be ready to look at your changes at any time.
An additional note:
I was also able to repeat Stuart's work in a pure Ubuntu
environment...there is one trick, though, and we might want to consider
using it in the installer. Here's what I did:
1) Installed Ubuntu 13.10 and v
Another update from Stuart regarding mkdosfs/mkfs.vfat that may be
relevant and it may lend some ammo to possibly adding the "-s 1" flag to
the mkdosfs command mentioned above?
"So it looks like mkdosfs / mkfs.vfat is calculating an initial guess
for "bs.cluster_size" (the internal variable name)
I ran some experiments today and this so far seems to be the 'sweet
spot' with regard to the EFI system partition:
1) Before installing, I created a 133MB partition on my gpt disk using parted,
type FAT32 and bootable.
2) I formatted the partition using "mkfs.vfat -s1 /dev/sda1"
3) Booted to the
The above experiment was also performed with today's 12.04.3 builds and
patched versions of efibootmgr and partman-base. I can also
automatically boot to a grub prompt with 12.04.3 using a 133MB EFI
partition formatted with mkfs.vfat -s 1.
--
You received this bug notification because you are a
I'll also be trying this again with 266MB for the EFI system partition. The
reason is because Stuart earlier mentioned that the minimum “proper” FAT32
partition (at least 64K clusters) is ~133MB—it is actually ~266MB. He
multiplied incorrectly. It
is ~33MB for 512-byte sectors, so it is ~33MB
I can get the system to successfully boot from the grub prompt by
running:
grub> linux (hd0,gpt2)/vmlinuz root=/dev/sda2
grub> initrd (hd0,gpt2)/initrd.img
grub> boot
This was done during my experiments with creating a 266MB fat32 fs on
the EFI system partition. What I'd like to try next is a sl
For 13.10, so far, this seems to be the way to get these disks to boot:
1) Prior to installation, carve out a partition of at least 133MB in parted
using a GPT partition table. Toggle the boot flag.
2) Format the disk using 'mkdosfs -s 1 /dev/sda1'
3) Start up the server installer.
4) Select man
Public bug reported:
The latest update to systemd in 13.10 seems to have broken the touchpad
disable / enable hotkey on Dell laptops. This so far includes the
Latitude series (E6430, 6430u, E6530, etc), Precision M (M6700, M4700)
and some of the newer Inspiron laptops.
The Latitude and Precision
I just tried it on my Latitude 6430u and it so far has not had any
effect. All other hotkeys still work but touchpad hotkey doesn't
respond.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218433
Titl
Here's the output from export-db
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218433
Title:
Latest systemd updates break touchpad disable hotkey on Dell laptops
To manage notifications about this
Here's the output from the shell command
** Attachment added: "test-builtin"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1218433/+attachment/3794105/+files/test-builtin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Attachment added: "udev.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1218433/+attachment/3794104/+files/udev.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218433
Title:
La
Ok. Making some progress, here.
With the new hwdb update it looks as if the hotkey does respond, but,
not like one would expect :-) The touchpad hotkey now behaves like it
did in the past before we put the keyboard-force-release rules in place.
i.e., things appear to get 'stuck' whenever we pres
And the re-run of the test-builtin keyboard script
** Attachment added: "test-builtin"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1218433/+attachment/3795397/+files/test-builtin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here's the new udevadm output
** Attachment added: "udev-new.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1218433/+attachment/3795387/+files/udev-new.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Indeed it is! The touchpad hotkey is now working again on my Latitude.
Attaching output from the "udevadm test-builtin keyboard" script.
I'll also test this on an Inspiron laptop later today to make sure it's
fixed, too.
** Attachment added: "test-builtin-with-fix-applied"
https://bugs.launc
The fixes also work for the Inspiron laptop. Touchpad hotkey
functionality is restored and not hotkeys appear to have regressed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218433
Title:
Latest s
Hi Martin,
Your latest hwdb.d keymap doesn't seem to introduce any new problems on
my test laptops. Everything still appears to work OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218433
Title:
Hi David and Gabor,
I found the problem. The udpated language pack for Simplified Chinese
is still in -proposed, while I was looking for it in -updates.
When I tested the language pack from -proposed (which is indeed from
last week), the power management tool is now fully translated.
Thanks!
Wiki has also been updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/878856
Title:
The Power Settings tool in System Settings is not fully translated
into Simplified Chinese
To manage notifi
** Also affects: oem-priority
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/962082
Title:
Profiles that require duplex audio like Head Set (HSP) and Hands
** 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:
+ Th
** 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
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 anyw
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 tg3-b
@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
w
** 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 ma
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 compar
** 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 b
** 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
de
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 suppo
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 notificat
** 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:
https://bugs.l
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:
Update
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
wseventmgr:
** 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 d
** 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
p
*** 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 i
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.
https://bugs.launc
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
Titl
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 p
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
- [bugs:#2730
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 1.4.8
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
T
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.mofC
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.
https://bugs.launch
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.
https://bugs.launchpad.net/bugs/1253
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 notifi
If the 1950's and 1750's are having problems, what type of response do
you get from this command?:
ipmipower -h -u -p --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 the nodes up
and down. If your MAAS se
..and if that doesn't work, then try:
ipmipower -D LAN -h -u -p
--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
Bugs, which is subscribed to Ubuntu.
htt
@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
--
Yo
** 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 Ubun
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 install
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
Published to Trusty last night. Closing out. Thanks for your help,
Chris!
** Changed in: sblim-cmpi-devel (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
Please update openwsman to the latest upstream release version 2.4.3 for
Trusty.
This package provides a somewhat easier way to setup a CIM
infrastructure and is an important piece in many OEM's efforts (such as
Dell) to move to an 'agentless' method of systems management.
T
Adding debdiff between older and new release
** Patch added: "openwsman_2.4.3-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openwsman/+bug/1268707/+attachment/3947926/+files/openwsman_2.4.3-0ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubunt
I have added openwsman's latest release to the dell poweredge tools ppa,
and here are the relevant source, debian, and dsc files:
https://launchpad.net/~dell-poweredge-team/+archive/poweredge-tools/+files/openwsman_2.4.3-0ubuntu2.debian.tar.gz
https://launchpad.net/~dell-poweredge-team/+archive/p
Adding newer, more relevant debdiff
** Patch added: "openwsman_2.4.3-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openwsman/+bug/1268707/+attachment/3947927/+files/openwsman_2.4.3-0ubuntu2.debdiff
** Tags added: upgrade-software-version
--
You received this bug notification b
** Patch removed: "openwsman_2.4.3-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openwsman/+bug/1268707/+attachment/3947926/+files/openwsman_2.4.3-0ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Adding a fixed up debdiff which applies cleanly this time.
** Patch added: "openwsman-latest.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openwsman/+bug/1268707/+attachment/3948003/+files/openwsman-latest.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Changed in: ubuntu
Status: New => 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/1262336
Title:
[needs-packaging] please package sblim-sfc-common for universe
To manage notifi
Public bug reported:
The resulting packages from sblim-cmpi-devel source fail to build on
ppc64el. I'm thinking that some dh-autoreconf needs to come into play
to address it?
I'm going to post a proposed fix and I'd like for it to be reviewed.
** Affects: sblim-cmpi-devel (Ubuntu)
Importan
** Branch linked: lp:~kentb/ubuntu/trusty/sblim-cmpi-devel/fix-
for-1269934
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269934
Title:
Fix FTBFS on ppc64el
To manage notifications about this bug
Hey Seth,
Thanks for the review. I'll drop the quilt patches to make the diff
easier to look at.
Klaus does not have any CVE numbers generated, so, I believe they'll
need to be requested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Seth, here's the debdiff with the quilt patches popped. Let me know if
this is what you need or if I can get you anything else on this.
Thanks!
** Patch added: "bug-1310989-popped.diff"
https://bugs.launchpad.net/ubuntu/+source/openwsman/+bug/1319089/+attachment/4111635/+files/bug-1310989-pop
Tested on XPS 15 Haswell with a non-i2c Synaptics touchpad. No loss in
functionality of the touchpad with the test kernel and wifi, audio, usb
ports, bluetooth all continued to function.
Also ran 30 suspend/ resumes in a row with fwts and didn't see any
problems.
--
You received this bug notif
@John Hupp,
No. This is adding support for i2c-based Synaptics touchpads, which are
relatively new devices.
The XPS 15 with the non-i2c touchpad has had no problems double tapping
anything so far, even before this patched kernel was applied.
--
You received this bug notification because you ar
Tested an Inspiron 3421, which also has a non-i2c synaptics touchpad. I
tested the same components as earlier along with suspend and resume. So
far so good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
med a new set of HID touchpad driver:
>
>
> http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4&id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736
>
> It's better we can have it in 14.04 .
>
> To manage notifications about this bug go to:
&
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 subsc
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 chipset.
** 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 t
101 - 200 of 679 matches
Mail list logo
