wsman can admittedly be a bit complex with regard to running commands.
For example, to power on and off an AMT-capable laptop using wsman, one
can run the following command:
test@test-Latitude-6430U:~$ wsman invoke -a RequestPowerStateChange -J
request.xml http://schemas.dmtf.org/wbem/wscim/1/cim
I talked to the person that helped package this a few months ago.
If memory serves correctly, he believes the tests were disabled because
the ones in question were being run as a part of post-compile/packaging
and he thinks the way they were coded seemed to require an installation
of the code itse
@Warren,
What they're suggesting by development release is downloading the latest
iso for 14.04 and trying it as well. Those kernels are (I think) still
on version 3.12 instead of the release-candidate 3.13 ones. I believe
the idea is that if the problem is fixed in 3.12-based kernels it'll
prob
** Changed in: dell-poweredge
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152580
Title:
[Dell PowerEdge M520] BCM95720 Network disconnects and resets
To manage noti
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 and
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, wh
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 bu
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 doing
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
Thank you, Colin! I believe we can build the FusionIO modules for
14.04. We got some updated code that plays nicer with 3.10 and newer
kernels.
It will be Monday morning before I can hop onto this, but, we will
definitely get back to you as soon as we get something put together and
tested.
Tha
I tried this earlier today, and the installer is failing at the grub
installation when trying to install grub-efi-amd64-signed. I think this
is because grub-efi-amd64-signed depends on grub-efi-amd64
2.00-19ubuntu3 and our packages from the ppa are at ubuntu4.
I do, however, see some improvement
Tested with 12.04 daily builds. I confirm that the crashes no longer
occur when using LVM with advanced format disks.
Thanks.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Attaching crash dump from today's 13.10 build
I reproduced using xubuntu's desktop since the server's gfx adapter was
painfully slow on unity.
I'll also attach contents of /var/log/ next.
** Attachment added: "_bin_parted_server.0.crash"
https://bugs.launchpad.net/ubuntu/+source/partman-basi
I can also verify that the -proposed set allows me to avoid the
bootstrap issues on Precise and juju-core 1.13. So far no new breakage
/ regressions have occurred with this update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Attachment added: "logs.tgz"
https://bugs.launchpad.net/ubuntu/+source/partman-basicfilesystems/+bug/1215458/+attachment/3811398/+files/logs.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/121
For 12.04.3, I can also successfully boot using the steps above, along
with feeding the correct commands to grub at the grub prompt. The only
difference is that I have to apply the patches to partman-base, partman-
utils, and efibootmgr. Those fixes are in 13.04 and above, but, not in
precise (ye
Tested pciutils 1:3.18-2ubuntu6 on affected hardware. lspci output
looks good. Thanks!
** 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/
whoops, that should be 1:3.1.8-2ubuntu6 instead of 1:3.18-2ubuntu6
--
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 about th
@Francisco and others,
Please check here for the latest status on what's going on upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=47941
Some users have popped out of the woodwork to declare that the most recent
patches that went in *breaks* the backlight completely (black screen on boot)
Public bug reported:
When installing Ubuntu Server 13.10 (as well as 13.04, 12.10, and
12.04.{2,3}) on Advanced Format hard drives with native 4k/4k sectors,
we encounter a crash in partman_server when electing to auto-partition
using LVM. This also happens on the desktop versions.
Steps to repr
Crash dump from a recent attempt.
** Attachment added: "_bin_parted_server.0.crash"
https://bugs.launchpad.net/ubuntu/+source/partman-basicfilesystems/+bug/1215458/+attachment/3782524/+files/_bin_parted_server.0.crash
--
You received this bug notification because you are a member of Ubuntu
B
** Also affects: dell-poweredge
Importance: Undecided
Status: New
** Changed in: dell-poweredge
Status: New => In Progress
** Changed in: dell-poweredge
Assignee: (unassigned) => Kent Baxley (kentb)
** Changed in: dell-poweredge
Importance: Undecided => High
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dell-poweredge
Status: New => Confirmed
** Changed in: dell-poweredge
Assignee: (unassigned) => Kent Baxley (kentb)
** Changed in: dell-poweredge
Importance: Undecided => High
@Richard and others,
If you are interested in seeing a potential fix for 12.04, then please
get a separate bug report opened up as this one won't get any traction
with regard to a fix for the 12.04 release.
I can get 12.04 with OMSA 7.4 installed on a PowerEdge machine to see if
we can try and du
Tested on XPS 13 Haswell and confirmed that the following worked and /
or continue to work:
Synaptics touchpad now recognizes multi-touch gestures in i2c mode
Major components like wifi, audio, bluetooth did not seem to regress in
their functionality.
Ran 30 suspend/resumes using fwts and did no
@ Joseph and AceLan,
I can also confirm that the touchscreen stops working, but, I think I
can see why. The -proposed kernel loads a different driver for the
touchscreen than what is in the 'stock' kernel.
With the stock kernel, syslog reports the following:
hid-multitouch 0003:06CB:0AF8.001: 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
Also tested acelan's kernels with an XPS15 (model 9530) which has the
same touchscreen but a non i2c synaptics touchpad. The touchscreen and
touchpad both work fine and I don't see an regression in behavior. This
machine survived 30 S3's.
The Inspiron 14 (3421) with just a non-i2c synaptics touc
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 mana
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
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.
https://bugs.launchpad.net/bugs/1319089
It looks like I can browse my phone and send files to it now, once I get
everything set up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899858
Title:
regression in gvfs to connect/browse using obe
Someone else also needs to verify this as well as the behavior with my
phone appears to be spotty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899858
Title:
regression in gvfs to connect/browse us
James,
This looks good in 12.04. Everything from what I can tell looks to be
translated into Simplified Chinese where it is supposed to be.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/8766
Public bug reported:
ubiquity-2.9.27
I am working on a ubiquity plugin for oem-config and I ran into a
problem when calling "self.controller.toggle_top_level()"
The installer will crash and message I get from the oem-config.log is:
File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 1
** Attachment added: "plugin sample"
https://bugs.launchpad.net/bugs/954312/+attachment/2864684/+files/test-video.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954312
Title:
crash in toggle_t
** Attachment added: "oem-config.log"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/954312/+attachment/2864711/+files/oem-config.log
** Description changed:
+ ubiquity-2.9.27
+
I am working on a ubiquity plugin for oem-config and I ran into a
problem when calling "self.controll
Thanks, Stefan. The 'fix' you proposed earlier did stop the crashes
from occuring, but, I will look at your recommendations instead for my
plugin. Thank you for the tips!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** This bug is no longer a duplicate of bug 861663
Port to GStreamer 1.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873712
Title:
Lack of GstMiniObject means Gst.Message is broken, can't get E
For engineering,
This issue has been fixed in Maverick, but, the customer would also like
to have this ported to Lucid. They still deploy Lucid pretty widely.
The issue here is that mozilla-packagekit declares a breaks on
firefox-3.0, which is a transitional package in Lucid to migrate Hardy
upg
** Changed in: oem-priority
Importance: Undecided => High
--
[lucid] mozilla-packagekit cannot be installed with firefox 3.5
https://bugs.launchpad.net/bugs/606910
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
Confirmed that this update fixes the issue on a Dell Latitude E4310 as
well as other Latitude models.
--
Video out hot key sends super + p + return on many upcoming Dell & HP systems
https://bugs.launchpad.net/bugs/539477
You received this bug notification because you are a member of Ubuntu
Bugs,
Martin,
Yes. Unless someone has anything different to add, that's the fix that
IBM would like to see ported to Lucid.
--
[lucid] mozilla-packagekit cannot be installed with firefox 3.5
https://bugs.launchpad.net/bugs/606910
You received this bug notification because you are a member of Ubuntu
B
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686662
Title:
Fn+F5 sends correct keycode, but, touchpad is not disabled / enabled
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
Public bug reported:
Binary package hint: udev
OS Version: Ubuntu Maverick Meerkat 10.10 i386
Problem: When pressing the Fn+F5 hotkey on a Dell Latitude E-series
laptop to toggle the touchpad, the correct keycode is sent, but, the
touchpad does not respond. Instead, there are other side effect
Scan code for Fn+F5 according to sudo /lib/udev/keymap -i input/event4
is:
scan code: 0x9E key code: f22
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686662
Title:
Fn+F5 sends correct keycode, bu
product info from /sys/class/dmi/id/sys_vendor and product_name
** Attachment added: "product_info.txt"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/686662/+attachment/1758773/+files/product_info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
current mapping info
** Attachment added: "orig-map.txt"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/686662/+attachment/1758774/+files/orig-map.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
device dump
** Attachment added: "udev-db.txt"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/686662/+attachment/1758775/+files/udev-db.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/68666
Hi Martin,
This looks a lot better! I no longer get a hung keyboard when pressing
the Fn+F5 hotkey. The keyboard remains functional and I no longer lose
'clicking' functionality with the touchpad or the mouse buttons. The
OSD notification now appears instantly for the touchpad enable/disable
i
Hi Martin,
Per Mario's question I can confirm that Precision M is also affected by
this. They have the same breed of touchpad that these Latitude E models
have and use the same keycode sequence to turn on / off the touchpad
(Fn+F5 with 0x9E)
The information from /sys/class/dmi/id/sys_vendor is:
Just confirmed that the same fix applies to Precision M. I tested the
'fix' posted in #6 and substituted Latitude E* with Precision M*,
rebooted, and the touchpad key is now un-stuck on these machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Changed in: oem-priority
Status: New => Fix Released
--
[lucid] mozilla-packagekit cannot be installed with firefox 3.5
https://bugs.launchpad.net/bugs/606910
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Public bug reported:
Binary package hint: ubiquity
Approximately 3/4 of the way through the installation, Ubiquity crashes
and the installer cannot continue.
Steps to reproduce
1) Download the 64-bit Natty Alpha1 release and generate a USB startup disk
2) Boot from the USB drive and select "Ins
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684921
Title:
Natty Installer Crashes
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
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 t
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 postin
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.
https://bugs.laun
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:
Up
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 subscri
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,
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, notic
** 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.
https://bugs.launchpad.net/bugs/13348
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 detecti
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' switc
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 mana
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:
Enabl
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 Ub
Public bug reported:
When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
failed to start on reboot. After running 'sudo service openipmi start',
the service would still fail to start because it failed to load the ipmi
modules.
Kernel 3.13.0-8, which was previously on the system,
This is the kernel that worked for me:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc4-trusty/
I can also go back and test the others until I find one that breaks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I've uploaded the .apport file, since the server can't get out to the
internet very easily. Let me know if you need anything else.
** Attachment added: "openipmi.apport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+attachment/3994996/+files/openipmi.apport
** Changed in: lin
Public bug reported:
During the 13.10 cycle, some changes were made to the server installer
that (from what I understand) allow the driver-injection-disk udeb to be
loaded by default. Before that, one had to pass such boot parameters
such as "anna/choose_modules=driver-injection-disk-detect" on t
Tested today's 12.04 builds that contain what appears to be the bulk of
the grub2 version 1.99-21ubuntu3.11 packages.
Install completes without crashing, but, I still end up with no 'ubuntu'
entry in the EFI boot menu. I can navigate to the grubx64.efi file on
the hard disk via EFI boot menu, tho
Attaching a full log from an installation. Right now, we're having to
base things on 13.04 because we're having problems getting a working
kernel module for the fusionio device on the 3.11-based kernels in 13.10
and higher.
Steps taken:
1) Copy driver packages to a USB stick with the OEMDRV driv
It is possible to boot from the Fusion io device by doing the following:
1) Install on the Fusionio card and verify that it won't boot up using the
steps above.
2) Re-install the OS, this time on a local SATA disk in the same machine as the
FusionIO card.
3) Boot from the SATA disk. The grub m
I know for sure that it's using the grub directory off of the SATA drive
to get things going. Not so sure about the kernel and initrd. I'll
have to take a closer look at that and see if I can determine something.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Public bug reported:
Please sync ipmitool 1.8.13-1 (universe) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* d/p/revert_default_cipher_suite_id: cherry-pick upstream reversion of
regressed default protocol selection (LP: #1176202).
* d/p/revert_de
I'm pretty sure that the "Oct 24 03:33:28 grub-installer: invalid
numeric value" error comes from grub-install running efibootmgr against
the Fusion-IO device. The naming scheme, of course, for that adapter
is /dev/fioa1...the grub-install script, however, runs the following at
around line 892:
The efibootmgr problems mentioned above are most likely resolved
already. In 13.04, there was a kernel bug where the kernel would
sometimes fail to update EFI vars. I think that's partly what we were
hitting here. Here's the bug, and the issue has since been fixed:
https://bugs.launchpad.net/ub
Also, the grub-installer script that runs at install time identifies the
fioa device's partition label as loop.
Oct 23 18:17:10 grub-installer: info: Identified partition label for
/dev/fioa2: loop
When installing to the ATA device, the sda devices are seen as gpt:
Oct 24 15:50:51 grub-installer
Tried again with the latest 14.04 build for Ubuntu server along with an
updated fusionio driver. No surprise, but, we still aren't able to boot
directly from the device. Attaching latest logs from an install
attempt.
** Attachment added: "logs-1404.tar.gz"
https://bugs.launchpad.net/ubuntu/+
** Attachment added: "syslog-9-11.tgz"
https://bugs.launchpad.net/ubuntu/+source/partman-basicfilesystems/+bug/1215458/+attachment/3815369/+files/syslog-9-11.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Latest round of traces and logs with the 911.1 Xubuntu live cd.
** Attachment added: "_bin_parted_server.0.crash"
https://bugs.launchpad.net/ubuntu/+source/partman-basicfilesystems/+bug/1215458/+attachment/3815368/+files/_bin_parted_server.0.crash
--
You received this bug notification becaus
Looks like it fixes it for me. I installed the new ceph package then
restarted ceph-mon-all and the charm status went from being stuck at
"installed" to "started".
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a membe
With the latest partman-basicfilesystems package in today's 13.10 build
I'm able to perform an auto-partition with LVM without a crash. Thanks!
I am, however, presented with an unbootable machine, but, this may be
more related to what we are working through in this bug with the EFI
system partiti
Logs from an unmodified 50format_efi.
Note the warning in the syslog:
Sep 13 19:28:14 partman: WARNING: Not enough clusters for a 32 bit FAT!
...it appears to try and create the filesystem anyway, but, apparently
it's in a state that the EFI firmware on the server can't understand
when it comes
Logs from an installation where 50format_efi was modified with the "-s
1" option for mkdosfs. This allowed the server to drop us to a grub
prompt and boot the OS by hand with a few grub commands. I'm guessing
grub2 might also need some work. Possibly this patch would help?
http://osdir.com/ml/s
With the latest fixes on 13.10 I still fail to boot the OS, even with a
larger FAT32 EFI partition in place. In other words the server cannot
find anything to boot from and asks me to press F1 to try again, F11 to
return to the EFI boot menu, etc.
**HOWEVER**
If I restart the installation and ed
** Changed in: ubuntu
Status: Confirmed => Fix Released
** 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/1068766
Title:
Public bug reported:
Please consider adding openwsman, libopenwsman1, libopenwsman-dev to
main.
Rationale - openwsman is an open-source implementation of the Web-
Services Management spec (WS-Management). It's job is to expose systems
management information on Linux using the WS-Management proto
** Summary changed:
- [MIR] openwsman, libopenwsman1
+ [MIR] libopenwsman1
** Description changed:
- Please consider adding openwsman, libopenwsman1, libopenwsman-dev to
- main.
-
- Rationale - openwsman is an open-source implementation of the Web-
- Services Management spec (WS-Management). I
Public bug reported:
Please consider adding wsmancli to the main repository for Ubuntu
Server.
Availability - Latest upstream stable release was added to Universe for
Trusty Tahr. Dell had previously been building unofficial ports of this
package for Ubuntu for their server user base.
Rational
libopenwsman1 request:
https://bugs.launchpad.net/ubuntu/+source/openwsman/+bug/1262299
** Description changed:
Please consider adding wsmancli to the main repository for Ubuntu
Server.
Availability - Latest upstream stable release was added to Universe for
Trusty Tahr. Dell had prev
Public bug reported:
Please package sblim-sfc-common for trusty's universe repo
This package provides common libraries for functions shared between
sfcb and sfcc.
This is part of the sblim project and is now a necessary build-depends
and installation depends for the latest sfcb releases.
http:
Public bug reported:
Please update sblim-cmpi-devel to the latest upstream for trusty, which
is 2.0.3.
The current version in Ubuntu is 1.0.5 and is over 5 years old.
This new version is required as a build-depends for the latest version
of sfcb, which I have filed a request for here:
https://b
Public bug reported:
Please update sfcb to the latest stable upstream release, which is
1.4.6:
http://sourceforge.net/apps/mediawiki/sblim/index.php?title=Sfcb
Currently we are running a version that is 3 years old, 1.3.8.
Dell pulls this package directly from Ubuntu as a dependency for their
O
Public bug reported:
Please update sblim-sfcc to latest upstream which is 2.2.6.
http://sourceforge.net/projects/sblim/files/sblim-sfcc/
We currently have 2.2.5 available.
2.2.6 has a few minor fixes in it and it would be nice to make sure
we're in line with upstream.
Changes in 2.2.6
===
** 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/1262299
Title:
[MIR] libopenwsman1
To manage notifications about this bug g
1 - 100 of 679 matches
Mail list logo
