** Package changed: linux-signed-hwe (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850439
Title:
No sound on ASUS UX534FT
To manage notifications about this bug go to:
Can confirm I'm facing this issue too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850439
Title:
No sound on ASUS UX534FT
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-application (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-mate-settings (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I came to file this exact issue and I saw that someone has already filed
it; thank you Amr.
If chromium isn't provided in 20.04, then Ubuntu users that opt not to
use snaps will have to install Google's Chrome instead.
I tested the Buster chromium package in Focal and it worked fine.
** Description changed:
+ [Impact]
+
On my freshly installed eoan system I have two output devices:
- HDMI/DisplayPort 2 - GK208 ...
- Line Out - Family 17h ...
When I login into the system pulseaudio always select the "wrong"
one (HDMI) and I need to go to
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856813
Title:
Touchpad on X1 Carbon G6 is slow and sloppy
To manage notifications about this bug go to:
Yes coming soon :)
https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/commit/?h=ubuntu-
eoan=9eb759d419b5d2302bd1376e88c621381358509e
** Patch added: "pulseaudio_13.0-1ubuntu1.1.debdiff"
http://bit.do/fkVBJ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
Also please provide links to upstream changes/bugs in the patch, and/or
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855893
Title:
Properly let PCM leave suspended state when hardware
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium (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/1855594
Title:
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853197
Title:
Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec
This change was made by a bot.
** Changed in: linux (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/1856813
Title:
Touchpad on X1 Carbon G6 is slow and
** Description changed:
:~$ dmesg|grep error
[ 49.262644] systemd[1]: Couldn't move remaining userspace processes,
ignoring: Input/output error
+ systemd/focal-proposed,now 244-3ubuntu1 amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Touchpad on X1 Carbon G6 is slow and sloppy
Because:
[2.101906] psmouse serio1: synaptics: Your touchpad (PNP: LEN0091 PNP0f13)
says it can support a different bus. If i2c-hid and hid-rmi are not used, you
might want to try setting psmouse.synaptics_intertouch to 1 and
Here's the upstream fix:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.4=2a8e38a8b9b7fcce4b0b0bc7ca4f2d74cc7c1529
Mine is a LEN0091 but we should make sure we also have the fix for
LEN0092.
** Tags added: performance
--
You received this bug notification
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Public bug reported:
:~$ dmesg|grep error
[ 49.262644] systemd[1]: Couldn't move remaining userspace processes,
ignoring: Input/output error
** Affects: ubuntu
Importance: Undecided
Status: New
** Description changed:
- [ 49.262644] systemd[1]: Couldn't move remaining
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
This package failure looks like it was caused by bad ISO download,
corrupted install media, or device failure. eg. look in the logs and
you'll see messages like these :-
Dec 18 05:49:15 ubuntu kernel: [
Public bug reported:
Sending a screenshot of issue that may help.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.21
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Any new for me?
bye bye
On 16/12/19 6:24 μ.μ., Sebastien Bacher wrote:
> Thank you for your bug report, could you attach the output of those commands
> to the bug?
> $ journalctl -b 0
> $ gsettings get org.gnome.desktop.interface icon-theme
> $ dpkg -l | grep icon
>
> ** Package changed: xorg
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: Fix Committed => Fix Released
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
This package failure looks like it was caused by bad ISO download,
corrupted install media, or device failure. eg. look in the logs and
you'll see messages like these :-
Dec 18 05:26:36 ubuntu kernel: [
Public bug reported:
While OS installing it stopped saying there was an issue, stating that
one could possibly be that its an old hard drive.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.21
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** 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
** Changed in: pulseaudio (Ubuntu Eoan)
Status: Triaged => 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/1847570
Title:
PulseAudio automatically switches to HDMI sound output on
I just noticed the above patch. Now added to git:
https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/log/?h=ubuntu-
bionic
Please remember to put proposed changes in git so everyone is working
with the same source.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
**
** Changed in: linux-restricted-modules (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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 --
packages:
lrm:
** 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 --
+ packages:
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: Fix Committed => Fix Released
** 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 --
kernel-stable-master-bug:
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => 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/1854207
Title:
Unrevert "arm64: Use firmware to detect CPUs that are not
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => 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/1855059
Title:
[Regression] 4.15.0-73.82 Can not boot ThunderX
To
Hi trong luu, for me the error happened every day, which is why I ended
up using Qubes. It's the only way that I could find except for Windows
You can try older kernels but it didn't work for me. Remember that
downloading older ubuntus will still give you a recent kernel, you have
to downgrade by
[Expired for debian-installer (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: debian-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for apache2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apache2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The error still happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
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
** 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 --
packages:
** Summary changed:
- bionic/linux: -proposed tracker
+ bionic/linux: 4.15.0-74.83 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
If I remove the evdi or DisplayLink driver then the dock won't work. I
began using this dock and laptop almost 3 months ago with no issues so I
am not use what happened. Also, I tried removing and reinstall the
driver with no success. The weird thing is the bluetooth keyboard works
but the mouse
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-characters (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/1828664
Public bug reported:
Vitrage report error as follows when adding config plugins =
jaccard_correlation
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: Traceback (most recent call last):
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: File
"/usr/lib/python3.6/multiprocessing/process.py", line 258,
Public bug reported:
Vitrage report error as follows when adding config plugins =
jaccard_correlation
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: Traceback (most recent call last):
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: File
"/usr/lib/python3.6/multiprocessing/process.py", line 258,
** 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:
The recent CVE fix broke SCP support in libssh, which X2Go Client
(x2goclient) relies on.
Sessions now fail with error messages such as "SCP: Warning: status code
1 received: scp: ~username/.x2go/ssh: No such file or directory\n".
(Also note the literal "\n" there, but I
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1030.34
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840239/comments/17
** Changed in: oem-priority
Status: Confirmed => Fix Released
** Changed in: linux-oem (Ubuntu)
Status: New => Fix Released
--
You received
** Package changed: xorg (Ubuntu) => libreoffice (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856702
Title:
LibreOffice window behind Firefox was flickering when Firefox asked me
for a
Hello Fred,
Based on Dann's feedback on testing, I'm failing to see where your patch
fixes the "root" cause (despite being able to mitigate the issue by
changing the aio notification mechanism).
I think the root cause is best described in this 2 emails from the
thread:
I expect this problem will resolve itself after version
1:11.1-1ubuntu7.5 (or higher) gets re-released.
** Changed in: pulseaudio (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since this is a fault in the Ubuntu archive/mirror, not in the
PulseAudio packages themselves, I have to mark it as Invalid sorry.
But we can keep discussing solutions here.
** Changed in: pulseaudio (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
It appears your packaging configuration is confused. You have one
package from
bionic-proposed (1:11.1-1ubuntu7.5)
and are trying to install another from
bionic-updates (1:11.1-1ubuntu7.4)
I wonder if that's something we did wrong. Did we revert the newer
version from updates to proposed?
Although it would be fixable in the PulseAudio packages if we just
bumped the version.
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Low
** Changed in: pulseaudio (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of
Please report the issue to the upstream developers at:
https://gitlab.gnome.org/GNOME/gnome-shell/issues
and then tell us the new bug ID.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
**
** Description changed:
new device IDs are required for CMP-V, whether they are published or
not. Once that is clarified, documentations and device drivers need to
update accordingly.
ControllerIn intel-next Kernel Version Commit Approved to be
published Comments
Per the upstream bug(s) fdm is not the same program as gdm :)
** Changed in: gdm (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/1856668
Title:
fdm: Warning:
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856691
Title:
libpulse-mainloop-glib0:i386 cannot be installed
To manage notifications about this bug go to:
Per the upstream bug(s) fdm is not the same program as gdm :)
** Changed in: gdm (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/185
Title:
fdm: Model size
Thanks. This appears likely to be the problem; the Nvidia driver can't
find a monitor!?
Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (II)
NVIDIA(0): Validated MetaModes:
Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (II)
NVIDIA(0): "NULL"
Dec 17
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
That one is from gnome-boxes, not gnome-shell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856425
Title:
Gnome Shell crashs sporadically
To manage notifications about this bug go to:
@Norbert
The "deep" mem_sleep approach works for me. I also downgraded to
vanialla 19.10 kernel before trying this. Not sure if it also works with
5.4 kernel. Will try this weekend.
Earlier I was making a mistake in writing "deep" into mem_sleep. Just
sudo echo deep > /sys/power/mem_sleep does
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (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/1855757
Title:
*** This bug is a duplicate of bug 1854798 ***
https://bugs.launchpad.net/bugs/1854798
** This bug has been marked a duplicate of bug 1854798
Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (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/1855757
Title:
This bug is not useful because it is delayed heap corruption AND
presently shows no useful stack trace.
If you encounter a crash like this then please add:
MALLOC_CHECK_=3
to your /etc/environment. Then reboot and report a new crash next time
it happens. Hopefully that one won't land here.
This bug persists. It may be a regression associated with 5.0.0.37.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814262
Title:
Wired interface gets impossibly high metric 20100
To manage
Thanks. That gives us a more formal issue to track: bug 1856781:
https://errors.ubuntu.com/problem/731708dc951c98fdf8e0d2693f74cf366138768d
But not really.
The problem with heap corruption issues like this is that regardless of
the root cause they will often look the same. So in this particular
This bug is closed. Some people have said they still see an issue
though, so please use bug 1855757 from now on...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809407
Title:
[nvidia] Corrupted
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.34.1+git20191024-1ubuntu1~19.10.1, the problem page at
This bug is closed so if you experience any problem at all then please
open a new one by running:
ubuntu-bug gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723857
Title:
onscreen
** 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 --
Image is not ready.
** Changed in: kernel-sru-workflow/certification-testing
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/1854784
Title:
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
Public bug reported:
failed instal grub in format system
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.21
ProcVersionSignature: Ubuntu 5.3.0-18.19-lowlatency 5.3.1
Uname: Linux 5.3.0-18-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
I believe this fix causes a regression with NoteBook Fan Control (NBFC) as
lifting the kernel lockdown was used as a workaround to enable NBFC to control
fan speed.
See https://github.com/hirschmann/nbfc/issues/414#issuecomment-354274657 and
https://github.com/hirschmann/nbfc/issues/472
Would
Nevermind this bug tracker works differently than github issues :)
(my first bug here as you can probably tell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853440
Title:
Volume either 0 or 100%
I would have performed hundreds of 'live' QA-tests of Lubuntu 19.04
during it's cycle, and don't remember that occurring for me.
I'll provide http://iso.qa.ubuntu.com/qatracker/reports/testers which
lists me as performing 302 for the eoan/19.10 cycle, as 19.04 is no
longer easily available, but
1 - 100 of 522 matches
Mail list logo
