And still existing on Sunday, March 13, 2022! Driver in use: 510.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1822937
Title:
NVIDIA settings won't write to /etc/xorg
Mariusz, what kernel version are you now seeing this in?
** Changed in: linux-hwe-5.13 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
Public bug reported:
no
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-460 470.103.01-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
Uname: Linux 5.14.0-1027-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
** No longer affects: nvidia-graphics-drivers-470 (Ubuntu)
** Summary changed:
- Displaylink is extremely slow
+ Displaylink is extremely slow in Xorg sessions
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470
This bug is closed. If you're seeing the problem in kernel 5.13.0-30 or
later then please use bug 1958523.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1958591
Title:
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964722
Title:
sleep no longer working since
Public bug reported:
Since upgrading to jammy (development) sleep is no longer working.
Symptoms are that the laptop will attempt to sleep, but the system never
goes to the actual standby, but hangs, using lots of power and the fans
start spinning.
The powerbutton becomes unresponsive and the
Was able to reproduce this bug on two of my machines aswell. Both were
using Nvidia 3000 Series graphics. Booting the 5.15.0-18 Kernel or 5.16
Mainline Kernels didn't have this issue.
Seems like only 5.15.0-22 is affected by this bug.
--
You received this bug notification because you are a
I'm faced with almost the same issue:
$ uname -r
5.13.0-35-generic
Ubuntu 21.10
$ sudo dmesg | grep iwlwifi
[sudo] password for nsimonov:
[2.116670] Loading modules backported from iwlwifi
[2.116671] iwlwifi-stack-public:master:9340:55438a77
[2.170158] iwlwifi :00:14.3:
Was able to reproduce this issue on two of my machines aswell. Both were
installed in EFI Mode.
Booting the older 5.15.0-18 kernel or 5.16 mainline kernels work around
this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964713
Title:
Can't boot anymore with
Public bug reported:
upgrade from 5.15.0-17 to 5.15.0-22 seems to have broken my system.
After showing the splash screen, screen does black and system is stuck
(need to hard reboot).
>From grub, going back to 5.15.0-17 recovery mode allows to boot.
5.15.0-22 recovery mode freezes on initramfs
Well, the problem was probably not tied to linux-iamge, as I could
recover a fully functional system with Zsys, going 3 days back. And in
this state, my kernel is 5.15.0-22-generic...
So the origin of the problem was something else... don't konw what.
Closing the report.
** Changed in: linux
[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 Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1948877
Title:
Bluetooth headphones media buttons no longer work
** Summary changed:
- [nvidia] One monitor fails to wake after resuming from sleep
+ [nvidia] One monitor remains black on startup or resume from sleep
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a
Is it the IBM or the LG monitor that remains black?
I can't see any hints of a problem in the log. It sounds like maybe
GNOME can't uniquely identify one of the monitors and so can't remember
its preferred setting.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
Maybe try enabling Wayland and then see if logging into 'Ubuntu on
Wayland' avoids the problem.
To enable Wayland you will need to change the kernel parameter:
nomodeset
to:
nvidia-drm.modeset=1
and then run:
sudo update-grub
and reboot.
--
You received this bug notification because
Public bug reported:
+ nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1)
+
+ * New upstream release (LP: #1961075):
+ - Fixed a bug that could cause GPU exceptions when minimizing a
+ fullscreen Vulkan application on certain desktops, such as
+ Plasma.
+ *
Public bug reported:
ı can't go further with my poor knowledge
hata: alt süreci 2 hatalı çıkış kodu ile sona erdi
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libllvm12 1:12.0.0-3ubuntu1~20.04.4
ProcVersionSignature: Ubuntu
I just verified the patch in Ubuntu 20.04 under kernel version 5.13. All
of my components now show up in open RGB. I compiled the kernel myself
using the steps provided in
https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984#note_872699651.
As mentioned above, I was not able to verify the PPA
Is this Linux patch series back-ported to older kernels, like the 5.13
kernel that came with my Ubuntu 20.04 installation, or any LTS kernel?
I'm not fully familiar with the Linux kernel release behaviour.
I'm asking this because I'm looking for the best way to apply this patch
on an older kernel
22 matches
Mail list logo
