Thanks for that.
It seems you are reporting multiple different issues here. The black
flickering on window resizing seems to be a new problem so I'll make
that the main bug.
The asymmetric artifacts seen when restoring from maximized is an old
bug
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [regression] Artifacts appears when windows are maximizing or minimizing
+ [regression] Artifacts appears when windows are maximizing or minimizing
(Intel Apollo Lake)
--
You received this bug
Apologies for misinterpreting this issue when initially triaging it - I
have re-marked it as Security. I notice from your linked bug report that
this was still happening with the upstream code as of September 2016 -
but upstream did not appear to engage on the issue. Can you confirm
whether this
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Do you see this issue on Linux v5.0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813496
Title:
powertop does not accurately determine battery discharge rate on HP
Elitebook 850 G5
To manage
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835521
Title:
1. I am not using any extensions.
I have done this commands. Please, take these files.
пн, 8 июл. 2019 г. в 05:00, Daniel van Vugt
:
> 3. Please also run:
>
>dpkg -l > allpackages.txt
>
>and send us the file 'allpackages.txt'.
>
> --
> You received this bug notification because you are
I am not using any extensions.
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1835521/+attachment/5275544/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: lubuntu-meta (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/1835679
Title:
Calamares don't offer a partitioning scheme on mmcblk devices
Please test this kernel:
https://people.canonical.com/~khfeng/lp1835040/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835040
Title:
Touchpd not working properly on Linux
To manage notifications
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
variant: debs
** Affects:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782608
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828227
[Expired for xca (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xca (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661310
[Expired for maas (Ubuntu) because there has been no activity for 60
days.]
** Changed in: maas (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824434
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792672
[Expired for lubuntu-meta (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: lubuntu-meta (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826831
Also applies to Cosmic, Disco & Eoan. Never been fixed.
Just installed Debian Buster to see how it handled grub. I did not
select an ESP and it told me to go back and choose a partition as
/efi/boot. I choose sdb's ESP and it installed without issue to ESP on
sda, and did not overwrite my Ubuntu
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so I am closing it and converting it to a
question in the support tracker. I understand the difficulties you are
facing, but it
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Public bug reported:
1) lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
2) apt-cache policy zfsutils-linux
zfsutils-linux:
Installed: 0.8.1-1ubuntu5
Candidate: 0.8.1-1ubuntu5
Version table:
*** 0.8.1-1ubuntu5 500
500
This bug results in an unbootable system after the failed upgrade
occurs. As this is being run in a virtual machine I will be restoring
the original environment in case further testing is needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This sounds like a problem:
[ 163.566] (II) event10 - Logitech G102 Prodigy Gaming Mouse System Control:
is tagged by udev as: Keyboard
[ 163.566] (II) event10 - Logitech G102 Prodigy Gaming Mouse System Control:
device is a keyboard
** Package changed: xorg (Ubuntu) =>
** Changed in: gnome-desktop
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991002
Title:
Use the modern English name Bangla instead of Bengali for the language
code
** Changed in: gnome-shell
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807056
Title:
Occasional Keyboard freeze
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835677
Title:
Megal33t bug: touchpad with mousewheel is broken >:]
To manage
Looks like a duplicate to bug 1835150. Please try linux-oem-osp1 version
5.0.0-1013.14 from eoan-proposed, which should have included the fix.
https://launchpad.net/ubuntu/+source/linux-oem-osp1/5.0.0-1013.14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
[D/E][PATCH 0/1] LP#1829563 bcache: pending patch for Disco/Eoan
https://lists.ubuntu.com/archives/kernel-team/2019-July/102006.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829563
Title:
I/O Error Test 6 (for the Disco kernel)
commit: 'Revert "bcache: set CACHE_SET_IO_DISABLE in
bch_cached_dev_error()"'
Problem: if one backing device hits I/O errors the cache device
is disabled, but if that cache device is shared by other bcache
devices they stop too (even with
@Maher AlAsfar (malasfar)
What's cloud-init version on the Ubuntu16.04? The version need be greater or
equal to 18.2 to make customization work.
What's open-vm-tools version on the Ubuntu16.04?
If you customize Ubuntu with cloud-init, please do NOT add any
"After=dbus.x" to
Public bug reported:
Hie I am currently running on Ubuntu 18.04. and my hardware is Lenovo
ThinkPad l480.
Lenovo ThinkPad l480 comes with an inbuild fingerprint reader. It works
fine in windows os. but it is not able to detect in ubuntu.
the output of lsusb:
Bus 002 Device 001: ID 1d6b:0003
** Changed in: rtl8812au (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536309
Title:
New Upstream Version
To manage notifications about this bug go
** Changed in: rtl8812au (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705820
Title:
Wrong build when kernel upgrade (about kernel header path)
To manage
Public bug reported:
After do-release-upgrade from 16.04.6 to 18.04.2, my login motd still
keeps telling me to upgrade from 16.04 which is no longer the current
version
$ hwe-support-status
You have packages from the Hardware Enablement Stack (HWE) installed that
are going out of support on
** Description changed:
1) Ubuntu version: 18.04.2
- 2) Package: python3-pip
+ 2) Package: python3-pip
3) Version: 9.0.1-2.3~ubuntu1.18.04.1
- 4) Expected: pip3 list --outdated should return outdated packages
- 5) Actual: Got an exception with HTTP 404 error because
@klfyt, please understand you must share as much information with other
as possible if you need other people to help without the hardware. It's
already difficult to work without physical access to the target, let
alone not having any log, details from you. Changing the status to
CONFIRMED doesn't
I have been spending so many cycle on this, here are the Testing Tasks around
Ubuntu 16.04 Customization with Cloud-init
and its expected behaviour for vSphere Provisioning
Using After=dbus.socket doesn't work so stick the KB i mentioned below
if you want to do it yourself its Test 2 with DHCP
Public bug reported:
1) Ubuntu version: 18.04.2
2) Package: python3-pip
3) Version: 9.0.1-2.3~ubuntu1.18.04.1
4) Expected: pip3 list --outdated should return outdated packages
5) Actual: Got an exception with HTTP 404 error because
https://pypi.org/simple/xkit/ was not found
DEPRECATION: The
** Changed in: ibus
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991002
Title:
Use the modern English name Bangla instead of Bengali for the language
code bn
To
I have been spending so many cycle on this, here are the Testing Tasks around
Ubuntu 16.04 Customization with Cloud-init on vSphere
and its expected behaviour
-
- Create an Ubuntu 16.04 Virtual Machine on vSphere 6.7 U2.
- Apply the latest updates and upgrades -> sudo apt-get update && sudo
** Summary changed:
- virtualbox-guest-dkms-hwe 5.2.18-dfsg-3~ubuntu18.04.3 fails to build on 5.0
based kernels
+ virtualbox-guest-dkms-hwe 5.2.18-dfsg-3~ubuntu18.04.3 fails to build on 5.0
based kernels [In function ‘VBoxGuest_RTR0MemUserIsValidAddr’: error: macro
"access_ok" passed 3
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292398
Title:
Second screen position isn't saved from one session to another
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1292398 ***
https://bugs.launchpad.net/bugs/1292398
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1292398, so it is being marked as such. Please
3. Please also run:
dpkg -l > allpackages.txt
and send us the file 'allpackages.txt'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835521
Title:
[regression] Artifacts appears when
1. Are you using any extensions?
2. Please run this command:
lspci -k > lspcik.txt
and send us the file 'lspcik.txt'.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
I think this is fixable per comment #4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832426
Title:
"Program" is not responding when debugging in gdb
To manage notifications about this bug go to:
** Package changed: xorg-server (Ubuntu) => mutter (Ubuntu)
** Also affects: xorg-server (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/1835487
** Bug watch added: github.com/ibus/ibus/issues #2104
https://github.com/ibus/ibus/issues/2104
** Also affects: ibus via
https://github.com/ibus/ibus/issues/2104
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks for the video!
This kind of flickering is going to be low-level. So we should look at
the kernel log. If the kernel driver isn't reporting errors then it
would probably be a hardware fault.
Please wait until the problem happens again and then run:
dmesg > dmesgonflicker.txt
and send
[C][PATCH 0/2] LP#1829563 bcache: pending patches for Cosmic
https://lists.ubuntu.com/archives/kernel-team/2019-July/102001.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829563
Title:
bcache:
I/O Error Test 6 (for the Cosmic kernel)
commit: 'Revert "bcache: set CACHE_SET_IO_DISABLE in
bch_cached_dev_error()"'
Problem: if one backing device hits I/O errors the cache device
is disabled, but if that cache device is shared by other bcache
devices they stop too (even with
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #907
https://gitlab.gnome.org/GNOME/gnome-shell/issues/907
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/907
Importance: Unknown
Status: Unknown
--
You received this bug
I/O Error Test 7
commit: "bcache: fix ioctl in flash device"
This test needs QEMU+GDB since there's no way to set the variable
from the kernel, because it references incorrect memory/pointer.
In the original kernel, the ioctl() to a flash-only volume
goes from ioctl_dev() down
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Hi, I am getting the error:
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault
When I try to execute a Hello World binary on my amd64 machine, with
Hello World built by mips-linux-gnu-g++, using either mips binfmt
extensions (./hello) or qemu-mips-static hello.
[B][PATCH 00/11] LP#1829563 bcache: risk of data loss on I/O errors in backing
or caching devices
https://lists.ubuntu.com/archives/kernel-team/2019-July/101989.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-desktop/issues #49
https://gitlab.gnome.org/GNOME/gnome-desktop/issues/49
** Also affects: gnome-desktop via
https://gitlab.gnome.org/GNOME/gnome-desktop/issues/49
Importance: Unknown
Status: Unknown
** No longer affects:
The xcb/xcb_bitops.h used to be part of xcb-util, but was dropped in
version 0.4.0 from that package and moved to xcb-util-image.
Unfortunately, the package fails to include the header, which can result
in e.g. compilation failures.
It is also affected by Ubuntu 19.04 disco. Compilation for xcb
** Changed in: xfwm4
Status: Confirmed => Invalid
** Bug watch added: freedesktop.org Bugzilla #107117
https://bugs.freedesktop.org/show_bug.cgi?id=107117
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
- * The bcache code in Bionic lacks several fixes to handle
-I/O errors in both backing devices and caching devices.
+ * The bcache code in Bionic lacks several fixes to handle
+ I/O errors in both backing devices and caching devices.
- * Partial
Installed package versions are:
- xfwm4 4.13.3-0ubuntu1~18.04
- libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835622
Title:
Cannot start desktop session
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: torbrowser-launcher (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/1835154
This is an issue in Mesa DRI driver for Intel, that shows when Mesa is
built with asserts() enabled (typically debug).
See:
https://bugs.freedesktop.org/show_bug.cgi?id=107117
https://patchwork.freedesktop.org/patch/237490/
--
You received this bug notification because you are a member of
I/O Error Test 1
commit "bcache: add CACHE_SET_IO_DISABLE to struct cache_set flags"
Problem: the cacheset is not retired immediately on I/O errors in
cache device if I/O requests keep coming.
Original kernel: bcache device remains on top of caching device,
and 'fio' never
I/O Error Test 3
commit "bcache: fix inaccurate io state for detached bcache devices"
Probçem: on detached bcache devices, iostat reports non-zero 'avgqu-sz'
and '%util' even after IO stopped.
Original kernel: iostat fields are non-zero on I/O idle.
Modified kernel: iostat
I/O Error Test 2
commit "bcache: add stop_when_cache_set_failed option to backing device"
Problem: upon too many io errors on cache device, bcache code retires cache set,
but it doesn't stop the bcache device.
(in writeback mode, if it continue to write, writes go to backing
I/O Error Test 6
Make sure that if two bcache devices share a cache device,
only one bcache device is offlined in case of I/O errors
in only one backing device.
Original
# uname -rv
4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019
#
I/O Error Test 4
commit "bcache: add io_disable to struct cached_dev"
Problem: in case of the backing device hits I/o errors or is
disconected, the I/O can still be accepted to the bcache device.
Original kernel: dd writes in writeback mode to failed backing device complete.
I/O Error Test 5
commit "bcache: stop bcache device when backing device is offline"
Problem: bcache is unaware that a backing device goes offline,
and accepts writes.
Original kernel: bcache doesn't realize backing device is offline.
Modified kernel: bcache device is removed
Public bug reported:
1) Ubuntu 19.04
2) 67.0.4+build1-0ubuntu0.19.04.1
3) When holding down F11 in FireFox, it will go into fullscreen mode and it
will not do anything else as the button is held down.
4) All it takes to crash gnome-shell... this is amazing. Just open firefox and
take your
This was already mentioned in the manual: “Advanced partitioning/ If you
have had a previous linux install and want to put the entire disk or
just replace an entire partition you will need to unmount them. In this
case running sudo swapoff -a will unmount them and any partitions with
data mounted
** Attachment added: "setup-sda.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275534/+files/setup-sda.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829563
Tests with I/O errors
=
The I/O error tests in the caching and backing device have been
simulated with the device mapper dm-linear and dm-error targets.
The tests are based on the patch messages, which describe a
problem and/or expected behavior, so to exercise the change.
This issue is solved. This occurred because the eMMC card in the mmcblk
devices must be unmounted before we install the OS to allow the
automatic partitioning option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "setup-two-bcache-one-cache.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275535/+files/setup-two-bcache-one-cache.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "setup.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275533/+files/setup.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829563
Title:
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835181
Title:
OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between
ldaps://
** Attachment added: "test-bcache-cache-modes.fio.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275532/+files/test-bcache-cache-modes.fio.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tests with fio
==
The fio tool has been run for performance tests on the original
and modified kernels in sequential (rw) and random read/write (randrw)
on all cache modes available (writethrough, writeback, writearound, none).
Summary: no regressions observed, same IOPS and BW
Tests with xfstests
===
The xfstests test suite has been run on the original
and modified kernels -- on all cache modes available
(writethrough, writeback, writearound, none).
Summary: no regressions observed; apparently one FIX
achieved in the writearound cache mode
** Attachment added: "test-bcache-cache-modes.xfstests.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275531/+files/test-bcache-cache-modes.xfstests.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Summary changed:
- ubuntu-bug calamares
+ Calamares don't offer a partitioning scheme on mmcblk devices
** Description changed:
- Lubuntu 19.04: Calamares don't offer a partitioning scheme on mmcblk
- devices
-
-
- During installation on mmcblk devices, Calamares detects existing
Please provide the Calamares log and check to see if anything's mounted
first. Perhaps file a new bug with `ubuntu-bug calamares`.
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Need some additional help with your essays Barely manage to complete all
assignments in time? Stop worrying and contact the team of professional
writers of the great essays and get rid of all tasks! https://great-
essays.com/article/classification-and-division-essays/
--
You received this bug
** Description changed:
- Lubuntu 19.04: during the installation on mmcblk devices, Calamares
- detects existing partitioning and OS but fails to offer automatic
- partitioning scheme, being necessary to do the partition manually.
+ Lubuntu 19.04: Calamares don't offer a partitioning scheme on
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
I enabled -proposed and installed 4.4.0-1088-aws #99-Ubuntu, and again
went through the test case on a c5.large instance on aws.
The problem is solved and performance is restored, and performs the same
as a non-snapshot mounted disk.
Again, we can see merging has been enabled with:
$ cat
Public bug reported:
Lubuntu 19.04: during the installation on mmcblk devices, Calamares
detects existing partitioning and OS but fails to offer automatic
partitioning scheme, being necessary to do the partition manually.
** Affects: lubuntu-meta (Ubuntu)
Importance: Undecided
** Package changed: ubuntu => initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
initramfs unpacking failed
To manage notifications about this bug go to:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Hi. Logs aren't needed. >:]
** 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/1835677
Title:
Megal33t bug: touchpad with
This failure has not been due to Juju but rather the setup of the CI
environment. We have not seen any consecutive failures of this nature,
so the issue has been resolved.
I am closing this report.
** Changed in: juju
Status: Incomplete => Fix Released
** Changed in: dbus (Ubuntu)
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
1 - 100 of 208 matches
Mail list logo
