** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890061
Title:
MATE Focal "amplified" sound controls do not sync with keyboard
buttons
To manage notifications about this bug go
Documentation is horribly insufficient in this regard. To quote the link
given, "Ubuntu Desktop flavour now always tracks HWE kernel (hardware
enablement). It means that from 20.04.2 release Ubuntu Desktop will gain
new major kernel versions every 6 months through to summer of 2022".
The words "fr
Documentation is horribly insufficient in this regard. To quote the link
given, "Ubuntu Desktop flavour now always tracks HWE kernel (hardware
enablement). It means that from 20.04.2 release Ubuntu Desktop will gain
new major kernel versions every 6 months through to summer of 2022".
The words "fr
Documentation is horribly insufficient in this regard. To quote the link
given, "Ubuntu Desktop flavour now always tracks HWE kernel (hardware
enablement). It means that from 20.04.2 release Ubuntu Desktop will gain
new major kernel versions every 6 months through to summer of 2022".
The words "fr
*** This bug is a duplicate of bug 1910709 ***
https://bugs.launchpad.net/bugs/1910709
** This bug has been marked a duplicate of bug 1910709
DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
*** This bug is a duplicate of bug 1910709 ***
https://bugs.launchpad.net/bugs/1910709
** This bug has been marked a duplicate of bug 1910709
DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
--
You received this bug notification because you are a member of Kernel
Packages, whi
Upgrading to nvidia-opencl-icd-340:amd64 (340.108-0ubuntu2,
340.108-0ubuntu5.20.04.1) from focal-proposed solves this problem. See
bug #1910709.
I came to this conclusion after testing the focal-daily (20210116) and
finding that nvidia-340 installed just fine. Since LTS daily builds
always have th
Upgrading to nvidia-opencl-icd-340:amd64 (340.108-0ubuntu2,
340.108-0ubuntu5.20.04.1) from focal-proposed solves this problem. See
bug #1910709.
I came to this conclusion after testing the focal-daily (20210116) and
finding that nvidia-340 installed just fine. Since LTS daily builds
always have th
I changed the package name from "meta" to just linux to get apport-
collect to work. Hope that's OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
Nvidia-340 fails to build during Foc
I changed the package name from "meta" to just linux to get apport-
collect to work. Hope that's OK.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
Nvidia-340 fails to bui
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453633/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453635/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453634/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453636/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453636/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453635/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
Nv
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453634/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
Nv
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453633/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Titl
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453629/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453632/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453630/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453632/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453631/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453624/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453627/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453622/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453625/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/19
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453628/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453621/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Ti
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453623/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/19
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453626/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453631/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/191
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453630/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453629/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453628/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453627/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453626/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
Nvid
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453624/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
Nvid
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453623/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453625/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453622/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453621/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
Nvidia
apport information
** Package changed: linux-meta-hwe-5.8 (Ubuntu) => linux (Ubuntu)
** Tags added: apport-collected
** Description changed:
This is really the result of the 20.04.1 iso images being built with
'linux-generic-hwe-20.04' which shouldn't have been included until
20.04.2 is r
apport information
** Package changed: linux-meta-hwe-5.8 (Ubuntu) => linux (Ubuntu)
** Tags added: apport-collected
** Description changed:
This is really the result of the 20.04.1 iso images being built with
'linux-generic-hwe-20.04' which shouldn't have been included until
20.04.2 is r
Even if that were the only consideration, which it's not, how do you
explain the fact that 20.04.2 has not yet been released?
>From my daily driver:
lance@lance-desktop:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Hardware specs can't hurt.
** Attachment added: "hw.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+attachment/5453595/+files/hw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Also may be helpful.
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+attachment/5453586/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Looks helpful to me.
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+attachment/5453585/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I clearly did something wrong based on the lack of attachments to this
and I can't get apport-collect to work so I'll attach a few on my own
but I sure could use some help :^)
** Attachment added: "media-info"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+attachmen
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
Nvidia-340 fails to build during Focal install due to upgrade to 5.8
kernel
I filed bug #1912032 concerning the failure of nvidia drivers to install
during a fresh installation of Ubuntu 20.04.1 because when download
updates is selected it auto-updates to a 5.8 series kernel during
installation.
--
You received this bug notification because you are a member of Ubuntu
Bug
I filed bug #1912032 concerning the failure of nvidia drivers to install
during a fresh installation of Ubuntu 20.04.1 because when download
updates is selected it auto-updates to a 5.8 series kernel during
installation.
--
You received this bug notification because you are a member of Desktop
Pa
I filed bug #1912032 concerning the failure of nvidia drivers to install
during a fresh installation of Ubuntu 20.04.1 because when download
updates is selected it auto-updates to a 5.8 series kernel during
installation.
--
You received this bug notification because you are a member of Ubuntu
Tou
I updated the bug description to better explain why I believe this is a
bug, but I left the original content below the break.
** Description changed:
Beginning about January 8th Focal users that installed Focal using
either the Ubuntu 20.04 or 20.04.1 installation media began getting
update
I updated the bug description to better explain why I believe this is a
bug, but I left the original content below the break.
** Description changed:
Beginning about January 8th Focal users that installed Focal using
either the Ubuntu 20.04 or 20.04.1 installation media began getting
update
I updated the bug description to better explain why I believe this is a
bug, but I left the original content below the break.
** Description changed:
Beginning about January 8th Focal users that installed Focal using
either the Ubuntu 20.04 or 20.04.1 installation media began getting
update
I added the packaging tag because this was a packaging error in the
20.04 and 20.04.1 images.
** Tags added: packaging
** Description changed:
+ Beginning about January 8th Focal users that installed Focal using
+ either the Ubuntu 20.04 or 20.04.1 installation media began getting
+ updated to t
I added the packaging tag because this was a packaging error in the
20.04 and 20.04.1 images.
** Tags added: packaging
** Description changed:
+ Beginning about January 8th Focal users that installed Focal using
+ either the Ubuntu 20.04 or 20.04.1 installation media began getting
+ updated to t
I added the packaging tag because this was a packaging error in the
20.04 and 20.04.1 images.
** Tags added: packaging
** Description changed:
+ Beginning about January 8th Focal users that installed Focal using
+ either the Ubuntu 20.04 or 20.04.1 installation media began getting
+ updated to t
Unfortunately apport-collect just says "no additional info collected"
(see pic added). I presume because 'ubuntu-meta' is not an installed
package? I struggled a bit trying to decide what the best way was to
report a bug like this because it's not actually a bug in the kernel
itself, it's just
Unfortunately apport-collect just says "no additional info collected"
(see pic added). I presume because 'ubuntu-meta' is not an installed
package? I struggled a bit trying to decide what the best way was to
report a bug like this because it's not actually a bug in the kernel
itself, it's just
Unfortunately apport-collect just says "no additional info collected"
(see pic added). I presume because 'ubuntu-meta' is not an installed
package? I struggled a bit trying to decide what the best way was to
report a bug like this because it's not actually a bug in the kernel
itself, it's just
Public bug reported:
Just as the title says, the 20.04 and 20.04.1 images use the HWE version
of linux-generic resulting in upgrades to the 5.8 series kernel. This
seems to effect Ubuntu only, or I should say I checked the Kubuntu,
Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctl
Public bug reported:
Just as the title says, the 20.04 and 20.04.1 images use the HWE version
of linux-generic resulting in upgrades to the 5.8 series kernel. This
seems to effect Ubuntu only, or I should say I checked the Kubuntu,
Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctl
Public bug reported:
Just as the title says, the 20.04 and 20.04.1 images use the HWE version
of linux-generic resulting in upgrades to the 5.8 series kernel. This
seems to effect Ubuntu only, or I should say I checked the Kubuntu,
Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctl
Thanks Alberts. I'd been trying to figure that out for some time now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742193
Title:
nemo-desktop does not show background on GNOME FlashBack session
T
Bad on me - I didn't realize we now needed an EFI System partition on
ALL installations.
** Changed in: ubiquity (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/19
Public bug reported:
Fairly simple install on non-efi Dell Latitude E6400. Just selected
"something else" and used an existing partition for /. Another OS is
already installed next to it (on sda3 I think).
Installation ended with a grub install warning. Not sure what will
happen when I reboot but
Although not intentionally so, this now works fine on both the E6400 and
E6510 laptops. Both initial boots, and subsequent boots. Just works
perfect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18993
Worst case scenario on those older Latitude laptops a DVD still works
fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
Title:
failure to boot groovy daily (again)
To manage notification
http://cdimage.ubuntu.com/ubuntu/daily-live/20201016.1/groovy-desktop-
amd64.manifest still shows casper 1.452
Is that correct or is the manifest just not updated? It's still not
working on the Dell latitude E6510 and E6400 previously mentioned. On
the E6510 I tried both legacy and UEFI modes and
Also seems to effect Dell Latitude E6400 with C2D CPU's and an E6510
with i7 M620 CPU laptops using 20201015 Ubuntu image created with
Startup Disk Creator in 20.04. The same USB with the same image works OK
in my old Intel Desktop so I'm reasonably certain it's hardware
specific.
Typical behavior
** Tags added: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890061
Title:
MATE Focal "amplified" sound controls do not sync with keyboard
buttons
To manage notifications about this
Public bug reported:
I probably have the package wrong but I was grabbing at straws :^)
Just recently testing Ubuntu MATE 20.04.1 release candidates and I
notice that you can increase volume beyond 100% by opening Sound
Settings, and once you've done that you can also increase beyond 100%
using t
Sorry I lumped so much text into one box. I must have been asleep at the
wheel.
I was just setting up another of these today with 18.04.1 and it's also
effected but I know Xenial worked fine out-of-box so I'm just guessing
(with inadequate studying) that the change to GNOME as default resulted
in
Sorry I lumped so much text into one box. I must have been asleep at the
wheel.
I was just setting up another of these today with 18.04.1 and it's also
effected but I know Xenial worked fine out-of-box so I'm just guessing
(with inadequate studying) that the change to GNOME as default resulted
in
Sorry I lumped so much text into one box. I must have been asleep at the
wheel.
I was just setting up another of these today with 18.04.1 and it's also
effected but I know Xenial worked fine out-of-box so I'm just guessing
(with inadequate studying) that the change to GNOME as default resulted
in
Sorry for the delay. I performed a fresh install of 20191014 last night,
then updated it this AM so we'd be working with an out-of-box
experience. After the update and a reboot I opened System Settings >
Devices > Mouse & Touchpad and changed Natural Scrolling and Tap-to-
click to off while also ch
Sorry for the delay. I performed a fresh install of 20191014 last night,
then updated it this AM so we'd be working with an out-of-box
experience. After the update and a reboot I opened System Settings >
Devices > Mouse & Touchpad and changed Natural Scrolling and Tap-to-
click to off while also ch
Sorry for the delay. I performed a fresh install of 20191014 last night,
then updated it this AM so we'd be working with an out-of-box
experience. After the update and a reboot I opened System Settings >
Devices > Mouse & Touchpad and changed Natural Scrolling and Tap-to-
click to off while also ch
** Tags added: eoan gnome-panel
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1743686
Title:
File system folder in nautilus Artful/Bionic flashback session does
nothing
Status in
** Tags added: eoan gnome-panel
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1743686
Title:
File system folder in nautilus Artful/Bionic flashback session does
nothing
To man
** Tags added: eoan gnome-panel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743686
Title:
File system folder in nautilus Artful/Bionic flashback session does
nothing
To manage notifications ab
Public bug reported:
After installing the Eoan Beta on a Dell Latitude E6400 attempting to
set touchpad Edge Scrolling was unsuccessful. It actually seemed to work
as long as the System Settings window was left open but as soon as the
window is closed the Edge Scrolling setting reverts to off.
I
Public bug reported:
After installing the Eoan Beta on a Dell Latitude E6400 attempting to
set touchpad Edge Scrolling was unsuccessful. It actually seemed to work
as long as the System Settings window was left open but as soon as the
window is closed the Edge Scrolling setting reverts to off.
I
Public bug reported:
After installing the Eoan Beta on a Dell Latitude E6400 attempting to
set touchpad Edge Scrolling was unsuccessful. It actually seemed to work
as long as the System Settings window was left open but as soon as the
window is closed the Edge Scrolling setting reverts to off.
I
I will follow up ASAP. The plot continues to thicken. I tried a
different set of hardware today with a B43 chipset and it didn't seem to
be effected. But that board has only DVI and VGA outputs whereas the
effected board with a G43 chipset has DVI and HDMI. I'd been using HDMI
so now I ran another
I will follow up ASAP. The plot continues to thicken. I tried a
different set of hardware today with a B43 chipset and it didn't seem to
be effected. But that board has only DVI and VGA outputs whereas the
effected board with a G43 chipset has DVI and HDMI. I'd been using HDMI
so now I ran another
Sadly /var/crash is empty, and errors.ubuntu.com + whoopsie-id just
displays a blank page. Also applying the workaround from bug 994921 does
not result in creating a crash report.
I started testing Ubuntu Disco 20190416 tonight and knowing what I know
now I can say with certainty that the easiest
Sadly /var/crash is empty, and errors.ubuntu.com + whoopsie-id just
displays a blank page. Also applying the workaround from bug 994921 does
not result in creating a crash report.
I started testing Ubuntu Disco 20190416 tonight and knowing what I know
now I can say with certainty that the easiest
Based on those most recent results I ran "dpkg-reconfigure grub-pc" and
removed "quiet splash". Now it boots to the gdm3 screen every time. So
maybe something to do with how plymouth hands off the boot process to
gdm3? Or how quickly that hand off is completed?
--
You received this bug notificati
Based on those most recent results I ran "dpkg-reconfigure grub-pc" and
removed "quiet splash". Now it boots to the gdm3 screen every time. So
maybe something to do with how plymouth hands off the boot process to
gdm3? Or how quickly that hand off is completed?
--
You received this bug notificati
This was tricky but I finally got a successful boot (following several
failed boots) using gdm3 by selecting the kernel with "e" from grub and
then removing 'quiet splash'. So I hope this is more helpful.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1
This was tricky but I finally got a successful boot (following several
failed boots) using gdm3 by selecting the kernel with "e" from grub and
then removing 'quiet splash'. So I hope this is more helpful.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1
Method used to collect this info:
(1) Fresh installed 20190413.2 choosing not to auto-login.
(2) Rebooted after install and surprisingly gdm3 appeared as it should so I
booted to desktop and just rebooted.
(3) That reboot failed as had been the previous case - just a black screen,
totally unresp
Method used to collect this info:
(1) Fresh installed 20190413.2 choosing not to auto-login.
(2) Rebooted after install and surprisingly gdm3 appeared as it should so I
booted to desktop and just rebooted.
(3) That reboot failed as had been the previous case - just a black screen,
totally unresp
As requested. Definitely C2D era board (Intel DG43GT) running a Pentium
Dual Core.
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256044/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Desk
As requested. Definitely C2D era board (Intel DG43GT) running a Pentium
Dual Core.
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256044/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs
Slight change in behavior testing a fresh install of 20190413.2 - if
installed with auto-login switched on logout did load and give the
expected choices of Ubuntu and Ubuntu w/Wayland. But if auto-login is
turned off I still get a black screen on reboot. I suspect that gdm3 is
not even loading beca
Slight change in behavior testing a fresh install of 20190413.2 - if
installed with auto-login switched on logout did load and give the
expected choices of Ubuntu and Ubuntu w/Wayland. But if auto-login is
turned off I still get a black screen on reboot. I suspect that gdm3 is
not even loading beca
1 - 100 of 3062 matches
Mail list logo
