/media/robert/Shared is an NTFS in a partition of my first internal drive.
I do not have this problem with the 4 external USB drives with NTFS file
systems. The larger (> 5TB) external drives are ext4, since Ubuntu does not
work with NTFS on large drives. I did notice the everyone permissions, so
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a
There is no output through the speaker or headphone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833582
Title:
ASUS Zenbook UX333F, sound not working
To manage notifications about this bug go
** 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 --
** 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 --
Downgrade was not so easy, because apt wanted to remove a heck of a lot of
other packages.
In the end I manually unpacked libsssl1.1_1.1.0g-2ubuntu4.3_amd64.deb and
copied the files over.
-> The problem was fixed.
So indeed the openssl library 1.1.1 caused these issues.
--
You received this
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1833169
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: kernel-package (Ubuntu)
** No longer affects: linux-meta-hwe (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
--
You received this bug notification because you
** 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 --
** Description changed:
chtmax98090 intel HD audio device doesn't work out of the box after
installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
audio devices.
Audio options shows device and it works if I do this:
- git clone https://github.com/plbossart/UCM.git
-
*** This bug is a duplicate of bug 1833169 ***
https://bugs.launchpad.net/bugs/1833169
** This bug has been marked a duplicate of bug 1833169
intel_max_cstate is needed with baytrail to aviod hangups
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-disco
** 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.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta-hwe (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/1833169
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kernel-package (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/1833169
I am running Ubunti 18.04.2 in an Enhanced Hyper-V session -
https://www.zdnet.com/article/windows-10-tip-run-ubuntu-linux-in-an-
enhanced-hyper-v-session/.
I am facing the same problem.
Tried
Switching input method between xim and ibus
Changing theme to Adwaita
Nothing works for me.
Given
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
--
You received this bug notification because you
** 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 --
[Expired for linux-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (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/1825775
[Expired for linux-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (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-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for flatpak (Ubuntu) because there has been no activity for 60
days.]
** Changed in: flatpak (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/1825754
[Expired for linux-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (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/1825711
[Expired for linux-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (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-hwe (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Any chances the fixed version will make it to Ubuntu 16.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700283
Title:
No SNI support
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 --
Internal audio is disabled in the BIOS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833652
Title:
[SB-XFi - Creative X-Fi, playback] No sound at all
To manage notifications about this bug go
Public bug reported:
Installed a new X-Fi sound card, but no audio is being heard during
playback on Ubuntu 18.04.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-22-generic
** 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 --
Please reproduce the freeze again, then reboot and run:
journalctl -b-1 > prevboot.txt
and send us the file 'prevboot.txt'.
** Tags added: amdgpu
** Summary changed:
- screen freeze after suspend
+ [amdgpu] screen freeze after suspend
** Package changed: xorg (Ubuntu) =>
*** This bug is a duplicate of bug 1832000 ***
https://bugs.launchpad.net/bugs/1832000
** This bug has been marked a duplicate of bug 1832000
NVidia fails everytime a new kernel update is released : nvidia-340
340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build
--
You
I might have the same issue, I'm not sure. I have a Ubuntu 19.04 server
with an onboard e1000e interface and a usb ax88179_178a interface,
routing traffic between the two.
The e1000e interface drops a couple of times a day and I see "Detected
Hardware Unit Hang" / "Reset adapter unexpectedly"
In isolation I don't think it's correct to say that Wayland sessions
have "no external monitors". Wayland sessions do work with external
monitors on the Nvidia driver if you have nvidia-drm.modeset=1. I've
confirmed this on a desktop at least.
It sounds like you're describing some other
Kernel changes to be released in linux-oem-osp1 5.0.0-1011.12.
** Changed in: linux-oem-osp1 (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tracking in:
https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f
** Description changed:
+ https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f
+
gnome shell crashes when I go to Settings -> Devices -> Displays
ProblemType: Crash
It appears there's only one caller of this function in gnome-shell:
js/ui/osdMonitorLabeler.js:let monitor =
this._monitorManager.get_monitor_for_connector(connector);
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
*** This bug is a duplicate of bug 1833558 ***
https://bugs.launchpad.net/bugs/1833558
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.32.1-1ubuntu1~19.04.1, the
*** This bug is a duplicate of bug 1833558 ***
https://bugs.launchpad.net/bugs/1833558
** This bug has been marked a duplicate of private bug 1833558
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1833527 ***
https://bugs.launchpad.net/bugs/1833527
** This bug has been marked a duplicate of bug 1833527
in gnome settings audio section does not see any sound card
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
just one last thing, possibly you are not aware that 19.04 Ubuntu wayland
sessions have exactly the same problem: no external monitors. While this
bug refers to Xorg, the problem is not limited to Xorg. At least on my
Optimus laptop. And when I use its multiplexor to go into pure Nvidia mode,
no
It's good if you can't reproduce a bug any more. Although your
AlsaInfo.txt shows the main problem was that pulseaudio wasn't running
at all:
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - No
Let us know if you wish to investigate that problem again.
** Changed in:
gnome-shell!587 only says it fixes gnome-shell#1325. If you think it
also fixes gnome-shell#1370 then you should probably add a comment here:
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/587
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640
** This bug has been marked a duplicate of bug 1793640
Pulseaudio fails to detect sound card, while timidity is installed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Actually, maybe those other DMs don't run as root. My memory is failing.
So again maybe we do want a similar workaround in gdm3. But that doesn't
seem to be the root cause of the bug.
** Changed in: gdm3 (Ubuntu)
Status: Invalid => Opinion
** No longer affects: mutter (Ubuntu)
--
You
> If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)
I don't understand the question, sorry. The statement "it won't work" is
wrong. Wayland does work. This bug is about
I think that "Fix Released" status is misleading. Even the Debian bug
mentions the problem is in 2.14.0-8 and that's the latest version in
Ubuntu and Debian.
It looks like the Debian bug was closed prematurely without a fix being
released. I was going to unlink it here but maybe not... Let's just
I think that "Fix Released" status is misleading. It's showing as fixed
in the same version where we still have the bug.
I'm going to remove that bug link since its of limited relevance here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
I think his point was to isolate the problem as being gdm3's wayland code.
If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)
my point was that you marked this as invalid,
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1833637
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: thunderbird
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/1813471
Title:
Thunderbird crashes with GTK_USE_PORTAL environment variable.
To manage
Here are the crash reports generated using the beta
bp-b5718f8c-7977-46a4-84b8-d190b0190618 <-- with 'GTK_USE_PORTAL=0
thunderbird'
bp-0fd780e4-9d38-4b70-b887-208e50190618 <-- with 'GTK_USE_PORTAL=1
thunderbird'
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind
of pointless. It's pointless because the most common reason for using
nvidia-drm.modeset=1 is to get Wayland support. I know there are other
reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in
PRIME setups.
I've tested 6.70.0, 6.70.1, 68.0b1, and the daily on Ubuntu 19.04, all
crash after all dialogs are closed and it seems (still needs a little
more testing) at least one email account is setup.
Whats odd is that unless you explicitly set GTK_USE_PORTAL = 1 in the
string to launch TB (i.e.
This bug was fixed in the package partman-auto-lvm - 59ubuntu4
---
partman-auto-lvm (59ubuntu4) eoan; urgency=medium
* Switch default VG name to vg$hostname, since $hostname-vg gets encoded
doubledashed in /dev/mapper/. Also switch fallback VG name to
vgubuntu. LP: #1782507
Public bug reported:
SRU justification:
[Impact]
Trackpoint middle button not reported to kernel.
[Fix]
Add these new PNPIDs support in kernel for 2 new thinkpads.
[Test]
Verified on hardware. Tests result are good.
[Regression Potential]
Low, 2 new PNPID added. No affection to other
I found out it only occurs using Kubuntu 19.10 and ubiquity version
19.10.5, which it now uses.
The current Ubuntu 19.10 still uses ubiquity 19.10.3 and it installs
correctly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "ubiquity-kde-version"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1833626/+attachment/5271947/+files/ubiquity-kde-version
** Attachment removed: "ubiquity-kde-dm"
** Attachment added: "ubiquity-kde-dm"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1833626/+attachment/5271945/+files/ubiquity-kde-dm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "ubiquity-kde-syslog"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1833626/+attachment/5271946/+files/ubiquity-kde-syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "ubiquity-kde-dm"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1833626/+attachment/5271944/+files/ubiquity-kde-dm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ubiquity 19.10.3 installs using swap partition, ubiquity 19.10.5 FAILS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833626
Title:
Failed to create swap space
To manage notifications about this
Confirmed this is still happening in 5.0.0-17
update-initramfs: Generating /boot/initrd.img-5.0.0-17-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs'
@ahasenack, I found this post (took plenty of Google foo) but it was
helpful.
For anyone else, 18.04 LTS STILL has this issue. The following fixed
it:
After=network-online.target
Wants=network-online.target
These are in my [Unit] section at the top of
/etc/systemd/system/sshd.service
[Unit]
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825189
Title:
Using full disk encryption, on a multipath device (in this case FCP)
ended up in trying to open/unlock a
According to the log, there is no obvious problem. So what do you mean
＂sound not working" here? can't find the speaker in the UI or can't
output sound from speaker?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package open-iscsi - 2.0.874-7.1ubuntu2
---
open-iscsi (2.0.874-7.1ubuntu2) eoan; urgency=medium
* debian/open-iscsi.kmod: drop; no static module list is needed if we let
iscsid load modules itself. LP: #1833586.
* debian/extra/initramfs.hook: add
** Tags removed: block-proposed
** No longer affects: multipath-tools (Ubuntu)
** No longer affects: parted (Ubuntu)
** No longer affects: partman-base (Ubuntu)
** No longer affects: debian-installer (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Google and CPC have completed verification of this update for all
releases. It's ready to promote.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-disco verification-needed-xenial
** Tags added: verification-done
vg$hostname it is, i think camel case and mixed _- is ugly too.
** Package changed: partman-lvm (Ubuntu) => partman-auto-lvm (Ubuntu)
** Changed in: partman-auto-lvm (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
I did not do anything special outside of the steps in my repro to
specifically enable SSL in the nginx configs, but should that matter in
terms of running these SSL tests? With the Dockerfile in the description
as it is, I can already see in the test output that SSL tests are
running and
Ok, including my own testing we got 4 positive feedback.
With that being said, I have just submitted the patch to our kernel team a few
minutes ago.
This will be part of the next cycle 01-July through 21-July.
Thanks for the pre-SRU testing, we will need you guys one more time
during the
Public bug reported:
The timeout is too long. Might had been fine in init days but with
systemd it locks the boot process if the interface is up and lacks dhcp.
See this : https://askubuntu.com/questions/773973/ubuntu-16-04-system-
boot-waits-saying-raise-network-interfaces/841432#841432
Please
"gdm3 compile without wayland", I meant
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
To manage notifications about this
What we know about this bug is that gdm3, nvidia and modeset=1 is broken
under configurations which are not broken when sddm and lightdm are
used.
we know that gdm3 sessions with external monitors work with root
permissions.
we know that gdm3 compiled with wayland also works (according to the
I should add that the "fix" I reported is only a narrow fix. The
internal display works. But external displays don't work if you have
nvidia drivers, gdm3 and if you are using modeset=1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1833630
and then change the status of the bug to 'Confirmed'.
If, due to the
fetchmailconf is deprecated upstream (as per comment #5), and does not
appear to be something we specifically rely on or directly support for
Ubuntu, I do not expect this to be an issue we would work on
independently of upstream, so I'm closing it as wontfix. If someone
does wish to see this
The version of pastebinit in the proposed pocket of Disco that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because
As fetchmail is a service, it should have (at least) three types of
tests:
1. Check that primary bits are installed, and that fetchmail --version
/ --help aren't erroring.
2. Check that the service is up
3. Check operation by setting up a local POP3 mail service, sending an
email to it, and
The version of python-eventlet in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of
The version of pastebinit in the proposed pocket of Disco that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because
The version of python-eventlet in the proposed pocket of Cosmic that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Tags removed: verification-needed-cosmic
--
You received this bug
The version of pastebinit in the proposed pocket of Disco that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
** Changed in: pastebinit (Ubuntu Disco)
The version of python-eventlet in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of
The version of python-eventlet in the proposed pocket of Cosmic that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of
The version of python-eventlet in the proposed pocket of Cosmic that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Tags removed: verification-needed-bionic
--
You received this bug
The version of python-eventlet in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: python-eventlet (Ubuntu Bionic)
Status: Fix
Public bug reported:
Leonvo Yoga C930 has similar issues with ideapad_laptop and rfkill switches to
the following bugs:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519900
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397021
System info:
sudo dmidecode | grep 'System
The version of python-eventlet in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of
The version of python-eventlet in the proposed pocket of Cosmic that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: python-eventlet (Ubuntu Cosmic)
Status: Fix
Reviewed: https://review.opendev.org/664578
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=8b1442c70860091c63f2e343d23105abd19fb6bb
Submitter: Zuul
Branch:master
commit 8b1442c70860091c63f2e343d23105abd19fb6bb
Author: James Page
Date: Tue Jun 11 14:02:44 2019
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
Additional confirmation...
Looks like this updated kernel fixes the issue on the affected test VM I
created.
Using the detailed directions in comment #75, I was able to install the
new test kernel and reboot.
Verified the expected version value with uname and then installed the
packages that
Ubuntu/Kubuntu 19.20 "eoan" version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833626
Title:
Failed to create swap space
To manage notifications about this bug go to:
1 - 100 of 494 matches
Mail list logo
