@chromastone I have experience with building software from source, and
have a laptop that replicates the problem. I'll give it a shot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971933
Title:
Successfully replicated this bug on an HP Elitebook 8570p, 16 GB RAM,
Intel i5-3210M (if dmidecode is not deceiving me). I also cannot get the
touchpad to cause the system to wake from suspend even trying to enable
the wakeup files for all three of the USB controllers in my system. OS
is the
OK, so, after further research and testing, I learned the following:
1: It is not necessary to bind-mount all of /run - just /run/systemd/resolve
does the trick.
2: There's no need to add "libreoffice-l10n-$LOCALE" to the packages.conf file
- one of the packages already there must depend on it,
Thanks Kai-Heng.
I have updated this and will keep you posted:
$ sudo dmidecode -s bios-version
1.19.0
$ sudo dmidecode -s bios-release-date
03/22/2022
Devices that have been updated successfully:
• System Firmware (1.12.1 → 1.19.0)
--
You received this bug notification because you are a
Just by way of update, this does not happen very often. It happened to
me again today after I have changed around which ports I have things in,
perhaps for the first time since I reported this a month ago. The same
Thunderbolt ports are not working after suspend, but the USB-C only port
works.
--
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1975481/+attachment/5592248/+files/syslog
** Description changed:
Test hardware is an HP Z220 SFF Workstation, 32 GB RAM, 256 GB SSD + 1
TB SSD, UEFI, no secure boot. Test was done within Gnome Boxes,
** Attachment added: "media-info"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1975481/+attachment/5592247/+files/media-info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975481
** Attachment added: "initial-status.gz"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1975481/+attachment/5592246/+files/initial-status.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "debug"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1975481/+attachment/5592245/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975481
Title:
On an
** Attachment added: "casper.log"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1975481/+attachment/5592244/+files/casper.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975481
Public bug reported:
Test hardware is an HP Z220 SFF Workstation, 32 GB RAM, 256 GB SSD + 1
TB SSD, UEFI, no secure boot. Test was done within Gnome Boxes, VM was
given SeaBIOS, 4 GB RAM, 20 GB disk space. Host OS is Ubuntu Studio
22.04, guest OS is Lubuntu Kinetic.
If you install Lubuntu with
You are correct. I didn't realize what I was looking at, but you're
right, the window is resizing in a weird way.
** Summary changed:
- Strange graphical glitch during Ubuntu installation when clicking "Install
Now" after inputting disk encryption details
+ Ubiquity window resizes in an odd way
Public bug reported:
Hardware is an HP Z220 SFF Workstation, 256 GB SSD + 1 TB SSD, 32 GB
RAM, UEFI, no secure boot. Testing was done within a Gnome Boxes VM,
SeaBIOS, 4 GB RAM, Kubuntu Kinetic live session.
Steps to reproduce bug:
1: Open the Application Menu.
2: Type "KSystemLog".
3: Click
Apologies for the long delay, I've had a lot I was doing.
The command you listed successfully launches Firefox, with
https://ubuntu.com in the address bar, and the Ubuntu website visible.
Note that I'm on the same Kinetic install that I was on when I first
posted the bug report.
--
You received
** Tags added: kinetic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971933
Title:
Unable to wake laptop using trackpad input
To manage notifications about this bug go to:
Public bug reported:
Test hardware is an HP Z220 SFF Workstation, 32 GB RAM, 256 GB SSD.
Testing inside Gnome Boxes, VM is using SeaBIOS, 4 GB RAM. Bug is
showing up in a Kubuntu Kinetic live session with the latest ISO.
Discover version is Discover 5.24.5.
Steps to reproduce:
1: Click the
New ISP, now my systems keep thinking I'm in Denver (even my
Chromebook!). Closing this as invalid, since even Chrome OS is affected.
This is my Internet's fault, not Ubuntu's (unless there's something
wrong with GNU/Linux so deep that it affects Ubuntu and Chrome OS, which
I seriously doubt).
**
Hardware: HP Z220 SFF Workstation, 32 GB RAM, Intel Xeon CPU, UEFI, no
secure boot. Tested Lubuntu 2022-05-16 ISO in virt-manager (QEMU/KVM)
with SeaBIOS, 4 GB RAM, 2 CPU cores, and 20 GB disk space, manual
partitioning with btrfs install. All good, newly installed system was
bootable with no need
I'm attaching two videos. One is the full installation procedure
(including making the VM and logging into the new install), the other is
a snippet out of the first video containing just the part of the
installation that glitches out. I'm using the newest ISO from the QA
tracker.
Launchpad
Public bug reported:
Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD.
While reporting Bug #1973469, I discovered that ubuntu-bug was unable to
open Firefox at the very end of the process. Sadly, I closed the
terminal window that contained the initial error, but I was able to
easily
Public bug reported:
Test hardware is on an HP Elitebook 8570p, 16 GB RAM, 120 GB SSD.
My Elitebook has a hardware problem that requires that I detach the CMOS
battery and leave it that way in order for the system to function.
Additionally, if I shut the system down, I have to leave it unplugged
Public bug reported:
Trying to launch OBS studio with the package installed from apt gives an
error on Wayland.
$ obs
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
obs-studio installed via snap install obs-studio launches as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973340
Title:
22.04 obs-studio does not launch out of the box with Wayland
To
Well, this isn't the same system that I used during the install, but it
is the same network... and it thinks I'm smack in the middle of the
Cheney Reservoir, Kansas. Like, not in the general area, but it
literally thinks I'm living **in the middle of the water (?!)**. I'm
getting this from the
Interestingly enough, while doing a bit more testing, I just found out
that, if you hit keys on the keyboard during early boot (before Plymouth
shows up), you can get the prompt to show up. Both Kinetic and Jammy
behave the same way. I'm typing slowly but continually during the whole
entire early
Yep, happens in Jammy too. Hmm. That might mean it's actually a problem
with my host system. I'm about to have another bare-metal machine
(probably tomorrow) that will be available for bare-metal testing and
use as a VM host, so I'll be able to do more thorough testing then.
--
You received this
This bug also occurs in Ubuntu 22.04 (Jammy).
** 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/1973156
Title:
Strange graphical glitch during Ubuntu installation when clicking
Public bug reported:
This bug was discovered while doing an Ubuntu QA test, "Install (entire
disk with lvm and encryption)" for Ubuntu Kinetic. The host system specs
are the same as here:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150
At step 24, when I click the "Restart now"
Public bug reported:
This bug was discovered while doing an Ubuntu QA test, "Install (entire
disk with lvm and encryption)" for Ubuntu Kinetic. I'm using the same
host system specs as in this bug report:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150
While running the test, in
Public bug reported:
Note: This bug might be the fault of my ISP - I'm using Verizon's
Premium Mobile Hotspot plan as my home internet, and I've noticed a
similar problem in Lubuntu Jammy. Seems like this bug probably would
have been caught back then, so I'm pretty sure this isn't Ubuntu's
fault,
For some reason, Apport wasn't able to open /var/log/boot.log (maybe I
missed a password dialog?), so here you go.
** Attachment added: "boot.log"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150/+attachment/5589079/+files/boot.log
--
You received this bug notification
Public bug reported:
This bug was discovered while doing an Ubuntu QA test, "Install (entire
disk with lvm and encryption)" for Ubuntu Kinetic. I'm doing this within
a virtual machine - the host OS is Ubuntu Studio 21.10 running on an HP
Z220 SFF Workstation, UEFI, no secure boot, 16 GB of RAM,
Public bug reported:
Hello,
Since upgrading (fresh reinstall) to 22.04, I have had issues with Totem
crashing.
I have not been able to pin down when it works and when it doesn't, as
playing the same videos seems to work sometimes and not work others.
After it crashes, trying to open it again
(And Firefox gave me a notification about hitting version 100, so it
presumably did update)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972545
Title:
Ubuntu Dock does not show indicator for open
** Attachment added: "As expected, closing and reopening Firefox makes it work
as expected"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587903/+files/Screenshot%20from%202022-05-09%2013-44-45.png
--
You received this bug notification
** Attachment added: "Screenshot of the dock"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587901/+files/Screenshot%20from%202022-05-09%2013-32-20.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
I am using the Firefox Snap on a fresh install of 22.04 (using defaults,
as far as I know).
Normally, Firefox shows an indicator in the Dock showing that it is
running (the orange dot) and gives the ability to choose between open
windows.
At the moment, I have Firefox
Yes, I think that is correct.
If you look at this diagram:
https://www.dell.com/support/manuals/en-uk/xps-13-9370-laptop/xps-13-9370-setupandspecs/left?guid=guid-a06ee5db-8981-4955-86ab-82b36e5aff57=en-us
I normally plug the monitor with keyboard into the port labelled 2 and the
network adapter
** Tags removed: lubuntu
** Tags added: calamares kinetic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970270
Title:
LibreOffice localization is not working out of the box
To manage
@eeickmeyer I even looked for that package, and couldn't find it at
first! I see it now. Argh. Guess I'm getting used to Launchpad... I've
added calamares-settings-ubuntu to the affected packages. Should I
remove lubuntu-meta and ubuntustudio-meta from the list?
** Also affects:
Further testing has revealed that this bug (and the solution in comment
#7) affect Ubuntu Studio 22.04 as well.
** Also affects: ubuntustudio-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Alright, so it turns out that the problem was our Calamares
configuration after all, despite the hours of testing and fiddling I did
(with multiple distros!) that led me to believe that this was a
Calamares bug...
Thankfully, Adriaan de Groot on GitHub was able to spot the actual
problem and was
Pinpointed the Calamares bug:
https://github.com/calamares/calamares/issues/1942 Once this is fixed,
the fix in comment #4 ought to resolve this bug.
I also discovered that my /dev/null errors in comment #5 were due to the
fact that I didn't know what I was doing with chroots, so you can
probably
Public bug reported:
When I try to report a bug in Firefox on 22.04 with the Firefox Snap, it gives
an error:
"The problem cannot be reported:
firefox is provided by a snap published by mozilla. No contact address
has been provided; visit the forum at https://forum.snapcraft.io/ for
help."
I
So, further debugging on this issue has revealed that the "try_install"
section isn't installing anything within the newly installed system. I
changed "try_install" to "install", which resulted in an installer
crash. Further debugging revealed that it was likely due to apt-get's
inability to find
Saw the IRC logs - I will update the workaround guide to instruct users
to remove the option entirely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966774
Title:
btrfs partioning with calamares
I think I may have found the solution for this bug.
In calamares-settings-ubuntu/lubuntu/modules/packages.conf:
update_db: true
backend: apt
operations:
- remove:
- "^live-*"
- calamares-settings-lubuntu
- calamares
- hunspell-en-us
Looks like you found it. Ubuntu 22.04 desktop-default-languages points
to a number of other seed files (or at least I think they're seed files)
such as "desktop-de" and the like. In the Languages folder of
https://people.canonical.com/~ubuntu-
archive/seeds/ubuntu.jammy/languages/desktop-de,
: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: aaron-work 35648 F pulseaudio
/dev/snd/controlC0: aaron-work 35648 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 10:36:09 2022
InstallationDate: Installed
** Description changed:
Using Lubuntu 22.04 within a virtual machine made using virt-manager,
KVM, and QEMU.
When Lubuntu 22.04 is installed in a language other than English, the
LibreOffice UI displays in English, despite the user's language choice.
The issue can be worked around by
** Tags added: lubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970270
Title:
LibreOffice localization is not working out of the box
To manage notifications about this bug go to:
Finally managed to download and test the Ubuntu 22.04 image, and Ubuntu
22.04 does **not** have this issue, so this isn't a problem with Ubuntu
as a whole.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Using Lubuntu 22.04 within a virtual machine made using virt-manager,
KVM, and QEMU.
When Lubuntu 22.04 is installed in a language other than English, the
LibreOffice UI displays in English, despite the user's language choice.
The issue can be worked around by running "sudo
** Attachment added: "Headset back on, output has gone back to the headset but
microphone has not"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583423/+files/Screenshot%20from%202022-04-25%2009-43-46.png
--
You received this bug notification
** Attachment added: "Headset turned off, input and output revert to internal
ones"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583422/+files/Screenshot%20from%202022-04-25%2009-43-27.png
--
You received this bug notification because you are a
Public bug reported:
In Gnome's sound settings, it takes a sensible approach for my Bluetooth
headset speaker:
1) I set it as my preferred audio Output Device
2) I turn the headset off and it disappears, reverting to the built in speakers
3) I turn the headset on again and it switches back to
Public bug reported:
Running sudo apt-get update
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python3-distupgrade 1:20.04.38
ProcVersionSignature: Ubuntu 5.14.0-1032.35-oem 5.14.21
Uname: Linux 5.14.0-1032-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
Fixed 2 days ago in updated gdm package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969121
Title:
System fallback to gdm login screen when hot-plugging a external
monitor in 1st time
To
Public bug reported:
in the middle of install I decided not to bother with active directory.
I pushed back button twice.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.8
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
Thanks to many of your replies, I was able to fix the playback issue
caused by the kernal upgrade; comment #11 from Bravo Bravo was
particularly helpful. Unfortunately, I'm unable to record through a
Scarlett Solo on Audacity. Any and all configurations result in, "Error
opening recording device.
Public bug reported:
W:Target Packages (main/binary-amd64/Packages) is configured multiple
times in /etc/apt/sources.list.d/google-chrome.list:3 and
/etc/apt/sources.list.d/google-chrome.list:4, W:Target Packages
(main/binary-all/Packages) is configured multiple times in
(In reply to wolftune from comment #67)
> The shift+click workaround does NOT work for me when using the normal
> interface with the curvy-arrow "reply" buttons. No matter what I do, the
> account default for HTML or plain stays.
I now have shift+click working in the normal interface since I
Simple fix here, which will need to be applied until a new version of Fail2ban
with the fix included is released.
https://github.com/fail2ban/fail2ban/commit/294ec73f629d0e29cece3a1eb5dd60b6fccea41f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
[ 132.973872] BUG: kernel NULL pointer dereference, address: 0098
[ 132.973881] #PF: supervisor read access in kernel mode
[ 132.973885] #PF: error_code(0x) - not-present page
[ 132.973889] PGD 0 P4D 0
[ 132.973898] Oops: [#1] SMP PTI
[ 132.973907]
Thanks, booting into a different kernel version worked. I installed
5.11.0-46 like you said, but then when I went into advanced options in
my boot menu there were three versions listed, so maybe I didn't have to
do that. I also didn't bother changing my grub default. I'll just choose
my kernel
I'm thinking of trying to roll back my software so that I can continue
using my computer until this is fixed. Can anyone recommend which
package I should try rolling back, or how I should go about this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes, bug 1958591 is the exact same bug, except that if my computer
suspends without my monitor plugged in then the screen is black instead
of noisy when I try to wake it up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Update: I suspended my computer again. This time when I opened it the
monitor worked, the laptop screen was black, and the mouse had
completely disappeared.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Starting today my laptop will not wake up from suspend no matter what I
try. After closing my laptop or leaving it alone for a while, the screen
goes black like normal, but then no matter how much I mash the keyboard,
touch the mouse, press the power button etc. the screen
What kernel version did you have to revert to? I'm also experiencing
this bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956849
Title:
Almost all USB ports suddenly stopped working; unbootable
The shift+click workaround does NOT work for me when using the normal
interface with the curvy-arrow "reply" buttons. No matter what I do, the
account default for HTML or plain stays.
I figured out that the shift+click works ONLY if I choose "reply" from a
menu, either the "Message" menu or from
Thanks Bas, this bug really make the system unusable. Very annoying.
Any workaround would be appreciate.
I guess this issue is talking about similar thing.
https://github.com/DisplayLink/evdi/issues/181
** Bug watch added: github.com/DisplayLink/evdi/issues #181
Still no fix or workaround? Having a fresh ubuntu 20.04 installed.
nvidia 470.86
xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
5.11.0-43-generic
HP zbook, G5.
External monitor, Xorg high cpu load, external monitor random slow.
--
You received this bug notification
I installed the HWE kernel on 20.04, and the errors in guests are gone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950706
Title:
VMs running under qemu+kvm can't use xsaves processor feature
I upgraded to 21.04 to see if it's fixed there, and it is. So this may
just need to be closed considering the imminent retiring of 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950706
Title:
Public bug reported:
Virtual machines running under qemu using KVM acceleration run with
`-cpu host` can't use the xsaves feature of the processor. An example
guest dmesg log is attached, see errors about "unchecked MSR access
error". Using a `-cpu` model that doesn't advertise xsaves such as
I normally use Wayland. I just tested this using Xorg instead and it is
working fine. Back to Wayland and it crashes. Back to Xorg and it is
fine.
** Summary changed:
- Launching Pitivi repeatedly crashes user session and takes me back to login
screen
+ Launching Pitivi repeatedly crashes
It seems to also be doing something to my sound. I use a Plantronics
headset (bluetooth, but with a dongle so it looks on the system like an
analogue in and analogue out). When pitivi crashes and logs me out, my
headset no longer works once I log back in. Switching the sound settings
to use the
Public bug reported:
I was using Pitivi without any issues and created a video.
Now, opening Pitivi immediately crashes my user session and takes me
back to the login screen.
Ubuntu 20.04 with Pitivi from the archive -- hopefully all that is in
the attached logs, but let me know if anything
Tried some recent mainline kernels again. No luck with 5.13.19, but
5.14.13 is using both displays just fine. (Earlier I had tried 5.14.3
with no luck.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still happens on 21.10's 5.13.16-051316-generic with a fairly new HP
Pavilion 15. The workaround from Arch doesn't quite help -- internal
monitor did work after that but external display is not detected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Compiz will keep the width as I specify with Whisker Menu on Xfce. But
the height, it will always shrink it to default height.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic
** Changed in: b43-fwcutter (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/1899848
Title:
Broken WiFi Install on Ubuntu (MATE) 21.10 for BCM4306 (rev 03)
Bug has recurred after beta installation of 21.10 (Impish). b43 firmware
reverted to version 784.2, causing significant degradation of WiFi
performance. using b43-fwcutter to load firmware version 5.100.138
(666.2) resolved the issue.
** Summary changed:
- Broken WiFi Install on Ubuntu (MATE)
Public bug reported:
Upstream bug: https://gitlab.com/cryptsetup/cryptsetup/-/issues/627
This is a latent bug in cryptsetup versions before 2.3.5 that surfaced
due to a change in the behavior of the kernel's TTY driver. The bug was
not triggered on Focal's 5.8 kernels, but it is on the 5.11
Ah interesting, thanks Daniel. I did not realise Raspberry Pis were
doing Wayland by default.
Yes, it works as expected in xorg, but not in Wayland.
It's a Raspberry Pi 4 Model B - 8GB, in case that was not clear from my
logs.
--
You received this bug notification because you are a member of
Public bug reported:
I am running Hirsuite on a Raspberry Pi 4. My main keyboard for this
(TV) machine is a wireless Logitech K400r combined keyboard/trackpad.
When I first installed, I do not think there were any issues with the
keyboard. When I did updates, my keyboard half-stopped working. It
** Also affects: nvidia-graphics-drivers-460 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-465 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Additional Data on ubuntu 21.04 with kernel 5.11.0-18
Have tried several of the available drivers directly from NVIDIA on the
450, 460 and 465 driver lines.
465.31 - FAIL
465.27 - FAIL
465.24.02 - FAIL
460.84 - FAIL
460.80 - FAIL
460.73.01 - PASS
460.67 - PASS
460.56 - PASS
450.119.03 - PASS
.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: aaron 1502 F pulseaudio
/dev/snd/pcmC2D0p: aaron
I will create a patch accordance to the work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174827
Title:
CVE-2013-1979
To manage notifications about this bug go to:
I will create a patch accordance to the work.
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Aaron Farias (timido)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174827
Ti
sudo lspci -vt
** Attachment added: "sudo lspci -vt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+attachment/5499761/+files/20210524_lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+attachment/5499759/+files/20210524_dmesg_log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
sudo lspci -vvv
** Attachment added: "sudo lspci -vvv"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+attachment/5499760/+files/20210524_lspci-vvv.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Hello,
I have a certified Dell XPS 13 9370 that had Ubuntu pre-installed,
though I have since installed normal 20.04 on it. I have my mouse,
keyboard and headset dongle plugged in via my USB-C monitor. This works
well.
- Every evening, I suspend to RAM
Public bug reported:
Hello,
I have a certified Dell XPS 13 9370 that had Ubuntu pre-installed,
though I have since installed normal 20.04 on it. I have my mouse,
keyboard and headset dongle plugged in via my USB-C monitor. This works
well.
Every evening, I suspend to RAM (note that I changed
Public bug reported:
Observed on Ubuntu Core 18, which uses initramfs-tools-ubuntu-
core_0.7.45+ppa5_all.deb (see https://launchpad.net/~snappy-
dev/+archive/ubuntu/image/+sourcepub/11283241/+listing-archive-extra),
but this issue appears to affect the official package in addition to the
one in
Thanks for the response Lucas. I would prefer to see something to the
effect that the system is up to date, because that at least tells me
that update-notifier-common is there and working. But if the decision is
to not write anything in that case, then I strongly agree with Daniel.
The 3 blank
** Summary changed:
- Empty MOTD on update-to-date focal systems (includes fix)
+ Empty MOTD on up-to-date focal systems (includes fix)
** Summary changed:
- Empty MOTD on up-to-date focal systems (includes fix)
+ Empty MOTD on up-to-date systems (includes fix)
--
You received this bug
101 - 200 of 4813 matches
Mail list logo
