There is a suspicious thing that needs to confirm with Desktop team;
More specifically, the linux-generic-hwe-20.04 was updated from 5.8 to
5.11 when .2 release is used and with available networking.
So the question will be, is this behavior expected?
--
You received this bug notification
It seems like we just released the point release before filing the bug,
and at this point using .3 iso to verify this issue can't be reproduced
from my side; the only difference w/ and w/o the networking during
installation is firefox-locale-en.
** Description changed:
We were seeing the same sequence of errors heppened on KVM and ARM
device running UC20:
"""
[12450.684692] sd-umoun[5922]: Failed to unmount /oldroot: Device or resource
busy
[12450.693515] sd-remou[5923]: Failed to remount '/oldroot/run/mnt/data'
read-only:
@Dimitri,
The issue can be reproduced by http://cdimage.ubuntu.com/ubuntu-
core/20/stable/current/ubuntu-core-20-amd64.img.xz while I previously
fetched the image there to test, so if you think it's snap relevant, I
can check with snapd team.
--
You received this bug notification because you
Hi bluppfisk,
Can you help to provide the following information:
1. upload the /sys/kernel/security/tpm0/binary_bios_measurements, you
can cp it into ~/ and then upload it to Launchpad bug as it's in-memory
file, so it should be amount of bytes in size.
2. check if TCG event log can be
First coredump came from docker as below:
CPU: 2 PID: 2024 Comm: dockerd Not tainted 5.4.0-48-generic #52-Ubuntu
What's the deployment and configuration by using docker?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'd like to remove myself from assignee as this is still blocked by
sponsoring queue, unless someone who has MOTU can help to proceed the
SRU.
** Changed in: davfs2 (Ubuntu)
Status: In Progress => Confirmed
** Changed in: davfs2 (Ubuntu)
Assignee: Woodrow Shen (woodrow-s
I'd like to remove myself from assignee as this is still blocked by
sponsoring queue, unless someone who has MOTU can help to proceed the
SRU.
** Changed in: davfs2 (Ubuntu)
Status: In Progress => Confirmed
** Changed in: davfs2 (Ubuntu)
Assignee: Woodrow Shen (woodrow-s
Hi can you try to add nomodeset into kernel parameter? basically 20.04
image should work with UEFI/secure boot, and that's what I did set up
for all my machines/laptops. For example, one of my machines is Intel
NUC7 and it was installed by 20.04. Or, Maybe you can update BIOS if it
has the latest
The config file /usr/lib/sysctl.d/50-default.conf should come from
systemd source package, and you can refer this upstream
https://salsa.debian.org/systemd-
team/systemd/-/blob/debian/master/sysctl.d/50-default.conf.
Until now, groovy also has the same problem but it's not really a big
issue
But, basically, we may not use tpm 1.2 and its tool anymore due to
likely transitioning to 2.0 for the general case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802133
Title:
Do not start tcsd
For now, on 20.04, this problem still happened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802133
Title:
Do not start tcsd when a TPM 2.0 is on the system
To manage notifications about this
Hi Christian,
Thanks for pointing out my thought was wrong due to SRU policy. For
developer, I agree that any supported PPA or UCA should be enough to
move on what we'd like to do. Even building from scratch. But, some of
users like https://askubuntu.com/questions/1239579/want-kvm-qemu-
Public bug reported:
When I use pbuilder-dist to build the debian package for armhf/arm64
arch, the error messages was shown as below:
dpkg-buildpackage: info: host architecture arm64
fakeroot debian/rules clean
semop(1): encountered an error: Function not implemented
dpkg-buildpackage: error:
Hi Steve,
Can I confirm that the new grub2-signed (i.e. grub-efi-amd64-signed deb)
is able to enforce Secure Boot signature verification?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401532
Title:
Hi Steve and Mathieu,
Can I confirm that the new grub2-signed (i.e. grub-efi-amd64-signed deb)
is able to enforce Secure Boot signature verification? and does it mean
the xenial kernel is signed now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi edice,
Please note that davfs2 is universe package and people can contribute
patches via SRU process[1], and you can follow this flow to find someone
(motu developers) to sponsor this package if you're confident to these
changes.
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
**
** Changed in: davfs2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538445
Title:
davfs2 often freezes any program that uses it
To manage
Great, thanks. I'm looking forward to expecting community's feedback.
** Changed in: davfs2 (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/1851326
Due to the bug didn't update for a while, I'd like to set it as invalid.
Please use the latest version instead.
** Changed in: davfs2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Due to the bug didn't update for a while, please try the latest version
on focal or groovy. Set this to invalid.
** Changed in: davfs2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Due to the bug didn't update for a long time, I'd like to set it as
invalid. Please try the latest version on focal or groovy.
** Changed in: davfs2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I don't see the weird case from my side as I'm using focal to verify.
I'd like to set this as invalid, and of course please file an bug if
someone can reproduce again.
** Changed in: davfs2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a
Set the bug to invalid as we have 1.5.6 available for groovy.
** Changed in: davfs2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091183
Title:
davfs2
Please use focal or groovy to test if there is the same issue here. Set
it to invalid.
** Changed in: davfs2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Due to the bug didn't update since 2015, I'd like to set it as invalid.
Please report the bug again / or to upstream if it's still an issue.
** Changed in: davfs2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The latest version is 1.5.6-0.1 and it should not be an issue anymore.
Set to Fix Released.
** Changed in: davfs2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From my initial test, I don't hit this problem by opening nautilus on
focal, and I can remotely navigate directories mounted by davfs.
** Changed in: davfs2 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Please try to use 1.5.6-0.1 on groovy first to see if the issue is gone
or not. I'd like to set it as invalid.
** Changed in: davfs2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: davfs2 (Ubuntu)
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/1851326
Title:
davfs2 has problems with MS IIS 7.5 WebDAV server
To manage
Does someone try mounting via nautilus on focal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538445
Title:
davfs2 often freezes any program that uses it
To manage notifications about this bug
Due to the latest version is 1.5.6-0.1 on groovy and 1.5.5 on focal, I'd
like to close this as Fix Release.
** Changed in: davfs2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi edice,
Can you please report to this bug / patch to upstream
(https://savannah.nongnu.org/bugs/?group=davfs2) to have a better review
from the point of maintainers?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
1.5.6-0.1 is available now on groovy, and I'm working on focal SRU and
waiting for sponsoring.
** Changed in: davfs2 (Ubuntu)
Assignee: (unassigned) => Woodrow Shen (woodrow-shen)
** Changed in: davfs2 (Ubuntu)
Status: Confirmed => In Progress
--
You received th
Due to the bug was also reported by upstream, and it seems making a
shorten URL is reasonable for upstream, so here I'd like to close it
like the upstream bug.
[1] https://savannah.nongnu.org/support/?109941
** Changed in: davfs2 (Ubuntu)
Status: Triaged => Invalid
--
You received this
Due to the bug didn't update since 2016, I'd like to close it as
invalid.
** Changed in: davfs2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/466960
Hi,
I already did NMU upload to debian/groovy, so lets keep tracking focal
SRU afterward.
** Changed in: davfs2 (Ubuntu)
Status: New => In Progress
** Changed in: davfs2 (Ubuntu)
Assignee: (unassigned) => Woodrow Shen (woodrow-shen)
--
You received this bug notification b
It should be fixed by upstream 1.4.7, so I'd like to set it to invalid.
** Changed in: davfs2 (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933381
Title:
Due to the bug didn't update for a while, I assume it should be fixed
now. Set to invalid.
** Changed in: davfs2 (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also the same case here. Probably we'd like to collect the information
to report upstream first to see if the maintainer can gain some insight.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/185986
Please try to use the latest version - 1.5.6-0.1 to verify. I don't see
this anymore from my side.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307962
Title:
file operation (mv) unsusccessful -
Due to the bug didn't update for a while, I assume this is gone from my
test. Set to invalid.
** Changed in: davfs2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Due to no one didn't update the bug for a while, I assume this should be
gone according to my test. Set to invalid.
** Changed in: davfs2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
By following above steps, I can't reproduce this anymore using
1.5.6-0.1. Please install the latest one to give a try.
** Changed in: davfs2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ug/1884004/+attachment/5384897/+files/debdiff
** Changed in: davfs2 (Ubuntu)
Assignee: (unassigned) => Woodrow Shen (woodrow-shen)
** Changed in: davfs2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*
http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156=markup=MAIN
** Affects: davfs2 (Ubuntu)
Importance: Undecided
Assignee: Woodrow Shen (woodrow-shen)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I also hit the same problem on focal as well, and I'd like to sru focal
for this patch first as it is really annoying, and do NMU for upstream
release version 1.5.6 on debian and groovy later.
** Attachment added: "debdiff"
** Description changed:
- It's a special case that we may need to convert rootfs from ext4 to
+ [Impact]
+
+ * It's a special case that we may need to convert rootfs from ext4 to
btrfs, and we have to resize btrfs inside initramfs as well.
+
+ [Test Case]
+
+ * Use ubuntu-image to create a
from ext4 to
> btrfs, and we have to resize btrfs inside initramfs as well.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-devices/+bug/1881074/+subscriptions
>
--
Woodrow Shen
Software Engineer, Canonical
Revised the patch according to suggestions, thanks.
** Patch added: "debdiff.patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-devices/+bug/1881074/+attachment/537/+files/debdiff.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: "debdiff.patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-devices/+bug/1881074/+attachment/5377723/+files/debdiff.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
It's a special case that we may need to convert rootfs from ext4 to
btrfs, and we have to resize btrfs inside initramfs as well.
** Affects: initramfs-tools-devices (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
Hi Daniel,
After logging with wayland, this bug is gone. Thanks for confirmation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871997
Title:
The primary display will cause black screen when
** Changed in: hw-detect (Ubuntu)
Status: In Progress => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864965
Title:
Add Intel RAID/RST detection with NVMe devices
To manage
** Attachment added: "journal.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871997/+attachment/5351890/+files/journal.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871997
Title:
This following message could happen when I repeated to switch landscape/flipped
mode sometimes, but not always happened:
[ 3123.471] (WW) modeset(0): flip queue failed: Device or resource busy
[ 3123.471] (WW) modeset(0): Page flip failed: Device or resource busy
--
You received this bug
Public bug reported:
The primary (built-in) display will cause black screen when external 4K
monitor is configured to flipped
Steps to reproduce:
1. plug 4K monitor via HDMI
2. open gnome-control-center
3. select Displays -> Orientation -> Landscape (flipped)
4. apply
5. black screen on built-in
I confirmed this should be xorg related, close as invalid.
** Changed in: gnome-control-center (Ubuntu)
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/1871994
Title:
** Description changed:
- The primary display is black screen when external 4K monitor is
- configured to flipped
+ The primary (built-in) display will cause black screen when external 4K
+ monitor is configured to flipped
+
+ Steps to reproduce:
+ 1. plug 4K monitor via HDMI
+ 2. open
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871994/+attachment/5350951/+files/dmesg
** Description changed:
The primary (built-in) display will cause black screen when external 4K
monitor is configured to flipped
Steps to
Public bug reported:
The primary (built-in) display will cause black screen when external 4K
monitor is configured to flipped
Steps to reproduce:
1. plug 4K monitor via HDMI
2. open gnome-control-center
3. select Displays -> Orientation -> Landscape (flipped)
4. apply
5. black screen on built-in
** Description changed:
[Impact]
A new discover-remapped-nvme.sh supports to detect if Intel RAID/RST
mode is activated as NVMe devices are remapped to AHCI memory space.
Based on this, ubiquity installer can take advantage of detection and
handle such a case with improved user
I'm trying to extract the function as a new script due to the possible
case: (please rectify if I'm wrong):
disk-detect.sh seems not to be used in the ubiquity (but disk-detect.sh
will be called in the post-installation)
I think the possible call sequence will be like: ubi-partman ->
** Patch added: "hw-detect_1.117ubuntu8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1864965/+attachment/5336023/+files/hw-detect_1.117ubuntu8.debdiff
** Changed in: hw-detect (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you
** Description changed:
[Impact]
- The disk-detect.sh supports to detect if Intel RAID/RST mode is
- activated as NVMe devices are remapped to PCI bus. Based on this,
- ubiquity installer can take advantage of detection and handle such a
- case with improved user experience.
+ A new
Hi Iain,
The point for this patch is to identify if RAID/RST mode is enabled or
not. Based on this, ubiquity should consider any case in which the user
is able to install Ubuntu indeed. In your case, I think ubiquity can use
is_removable
** Patch added: "hw-detect_1.117ubuntu8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1864965/+attachment/5331532/+files/hw-detect_1.117ubuntu8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch removed: "hw-detect_1.117ubuntu8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1864965/+attachment/5331497/+files/hw-detect_1.117ubuntu8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "hw-detect_1.117ubuntu8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1864965/+attachment/5331497/+files/hw-detect_1.117ubuntu8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
mportance: Undecided
Assignee: Woodrow Shen (woodrow-shen)
Status: New
** Changed in: hw-detect (Ubuntu)
Assignee: (unassigned) => Woodrow Shen (woodrow-shen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
ledmon 0.94 on debian sid is landed, and successfully copied to focal
now.
** Changed in: ledmon (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: ledmon (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
Debian 0.94 version is waiting for sponsoring[1]
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951251
** Changed in: ledmon (Ubuntu Focal)
Status: New => In Progress
** Changed in: ledmon (Ubuntu Focal)
Assignee: (unassigned) => Woodrow Shen (woodrow-shen)
** Bug
After installing linux-oem-osp1 (5.0.0-1033.38) bionic in -proposed and
linux-firmware (1.173.14) bionic in -proposed, the test result is good
for me.
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The upstream version 0.93 is landed in focal now:
ledmon (0.93-3) unstable; urgency=medium
* Fix 32bit compilation error to prevent shift-count-overflow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The upstream version 0.93 is landed in focal now:
ledmon (0.93-3) unstable; urgency=medium
* Fix 32bit compilation error to prevent shift-count-overflow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I know this bug was gone for a while, but now there are my findings
which may be a regression:
Test environment:
MAAS version: 2.5.0 (7442-gdf68e30a5-0ubuntu1~18.04.1)
1. Dell G3 3590 laptop with secure boot enabled
Deploying 18.04 from MAAS => Got the same error as bug described.
Did you check if TPM chip was enabled on BIOS option?
Refer:
https://askubuntu.com/questions/1178285/how-to-solve-ima-error-communicating-to-tpm-chip-messages-during-boot/1178287
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
debdiff v1
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1831733/+attachment/5285723/+files/debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831733
a debdiff for new release of ledmon_0.92-0.1
** Patch removed: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1831733/+attachment/5285585/+files/debdiff
** Attachment added: "debdiff"
A quick debdiff for SRU / devel v0.92 upstream release
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1831733/+attachment/5285585/+files/debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: linux (Ubuntu)
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/1808097
Title:
Console got stuck using serial tty after logout
To manage
The -proposed kernel has verified on x86.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: linux (Ubuntu)
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/1808097
Title:
Console got stuck using serial tty after logout
To manage
** Description changed:
[Impact]
- The agetty stopped working using serial tty when user logged out, especially
if there is a remained process. The agetty failed to open tty device due to
serial port used by previous process was not released.
+ The agetty stopped working using serial tty
f96e
[Regression Potential]
Should be none, and it's regression becoz 4.4 kernel didn't have this case.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Woodrow Shen (woodrow-shen)
Status: Confirmed
** Changed in: linux (Ubuntu)
Status: New => Confirmed
**
The bug could be closed due to bug #1789786.
** Changed in: ledmon (Ubuntu)
Assignee: (unassigned) => Woodrow Shen (woodrow-shen)
** Changed in: ledmon (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: ledmon (Ubuntu)
Status: Fix Committed => Fix Released
Hi Michał,
Please see
https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1789786/comments/8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760937
Title:
[Feature Freeze Exception]Update Ledmon
I've done for upgrading -proposed package and it works well.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789786
Hi Intel,
The ledmon SRU into bionic is just landed into -proposed:
https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1789786/comments/8
However, I noticed that comment #34 provided several patches for fixing
some issues, I'm not sure if Dimitri will take a look, but I can do that
if
Hi Patricia,
I agree with Steve mentioned that ledmon should *not* be critical
requirement for VROC but more likely accessory to me, especially ledmon
package is not covering the systemd unit to trigger the service when
it's installed. What OEM Base image project proposed to include ledmon
was
Hi Stephane,
Just subscribe you and give a notify that a capser patch for cosmic is
waiting for someone's review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793444
Title:
[wishlist] Request to
Hi Christian,
Thanks for sharing more information for above, and seems like we'll just
follow Intel's changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage
Hi Christian,
As we're discussing with foundation team about ledmon, the reason behind
this MIR is OEM base image would include ledmon. However the foundation
team suggests we may need to file a MIR request and they will make a
decision for figuring out the resource of maintenance.
For me, I'm
** Description changed:
+ == Requirements ==
+
[Availability]
Currently in universe.
+ Package in LP: https://launchpad.net/ubuntu/+source/ledmon
+ Upstream: https://github.com/intel/ledmon
[Rationale]
1.OEM projects needs to include ledmon for VROC suport (LP: #1759225)
2.Intel
Public bug reported:
[Availability]
Currently in universe.
[Rationale]
1.OEM projects needs to include ledmon for VROC suport (LP: #1759225)
2.Intel still maintains upstream for that (LP: #1668126)
3.Dependencies already in main.
[Security]
[Quality Assurance]
[Dependencies]
[Standards
Hi Mathieu,
Thanks your sponsor, I think it's good enough for SRU now:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789786
Title:
SRU ledmon into Bionic
To manage notifications about this bug
Given mdadm as Recommends in debian/control
** Patch added: "add-md-support-v2.patch"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1793444/+attachment/5191271/+files/add-md-support-v2.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
: Undecided
Status: New
** Merge proposal linked:
https://code.launchpad.net/~woodrow-shen/ubuntu-seeds/+git/platform/+merge/355401
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793472
Title
** Patch added: "add-md-support.patch"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1793444/+attachment/5190843/+files/add-md-support.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
As OEM projects had a task of Intel VROC support, the one of targets is
to install customized desktop on VROC RAID devices. I found that current
casper can't support it with latest code:
https://git.launchpad.net/ubuntu/+source/casper/tree/scripts/casper?h=ubuntu
1 - 100 of 169 matches
Mail list logo
