This is happening to me right now (On Ubuntu 19.10, kernel 5.3.0 and
5.3.9, nvidia drivers version 435 and 440)
It only happens when using nvidia GPU. If I prime-select my intel GPU then
there is no issue.
It seems related to the laptop display being on some internal display
port that gets
Do we have actually somebody assigned to this report? I've been playing with
the module parameters but nothing seem to be helping.
I added the debug parameter today, because none of the i915.enable_hangcheck=1
i915.error_capture=1 i915.verbose_state_checks=1 were helpful.
Should I fill a bug
The backlight device only gets registered after it's opened by graphical
session.
And the backlight gets unregistered when graphical session stops, hence
when systemd-backight@.service's "Conflicts=shutdown.target" triggers,
the backlight is already gone so the brightness wasn't saved.
Since
Well, apparently Nvidia driver doesn't do that.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1840592
Title:
systemd-backlight does not save and restore brightness for nvidia
Public bug reported:
I couldn't change brightness. Probably this bug is related to the
problem.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion:
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
** Changed in: oem-priority
Status: In Progress => Fix Released
** Changed in: oem-priority
Assignee: Shih-Yuan Lee (fourdollars) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-430 in Ubuntu.
This bug was fixed in the package nvidia-graphics-drivers-430 -
430.50-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-430 (430.50-0ubuntu0.18.04.2) bionic; urgency=medium
* debian/templates/control.in:
- Add Conflicts and Replaces to xserver-xorg-video-nvidia-#FLAVOUR#.
The verification of the Stable Release Update for nvidia-graphics-
drivers-435 has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
The verification of the Stable Release Update for nvidia-graphics-
drivers-435 has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
This bug was fixed in the package nvidia-graphics-drivers-430 -
430.50-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-430 (430.50-0ubuntu0.18.04.2) bionic; urgency=medium
* debian/templates/control.in:
- Add Conflicts and Replaces to xserver-xorg-video-nvidia-#FLAVOUR#.
This bug was fixed in the package nvidia-graphics-drivers-435 -
435.21-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-435 (435.21-0ubuntu0.18.04.2) bionic; urgency=medium
* debian/templates/control.in:
- Add Conflicts and Replaces to xserver-xorg-video-nvidia-#FLAVOUR#.
This bug was fixed in the package nvidia-graphics-drivers-435 -
435.21-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-435 (435.21-0ubuntu0.18.04.2) bionic; urgency=medium
* debian/templates/control.in:
- Add Conflicts and Replaces to xserver-xorg-video-nvidia-#FLAVOUR#.
This is fixed in focal-proposed:
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/440.31-0ubuntu1
The 440 series replaces the 430 series, and it builds correctly with
Linux 5.4
:~# dkms status
nvidia, 440.31, 5.3.0-21-generic, x86_64: installed
nvidia, 440.31, 5.4.0-4-generic,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1851349
Title:
Public bug reported:
Every time I adjust my laptop's screen brightness using the dedicated
brightness keys, there is a substantial delay between when I press the
button and the screen adjusts. Sometimes it even "twitches" and
decreasing the brightness by tapping the button two times will quickly
There are some computers and configurations I manage which rely on some
of these drivers:
evdev: there are some netbooks which have touchscreens that only work
with evdev, being detected by libinput but doing nothing. While this is
a libinput limitation, removing evdev would limit the netbooks'
@leosmuller
evdev was already marked invalid so it's not considered for removal as part of
this bug report. See comment #1.
siliconmotion - If they work for you on 18.04 LTS, you can keep running
that until 2023. I would be shocked if these are saving you power - and
happy to help with an
Is there a packaged version available with the fix for this bug? I'll
have one problematic machine for a few days so I can test. However, it
is an Intel Atom netbook, unlikely to be successful building onboard
directly on it.
--
You received this bug notification because you are a member of
** Changed in: oem-priority
Status: Confirmed => Invalid
** Changed in: oem-priority/bionic
Status: Confirmed => Invalid
** Changed in: xf86-input-wacom (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Tags added: desktop-lts-wishlist
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1791981
Title:
X Server session crash for "No space left on device"
To manage notifications about this
21 matches
Mail list logo
