** Summary changed:
- Screen brightness of HP laptop is not saved after restart
+ [HP ENVY Laptop 15-ep0xxx] Screen brightness is not saved after restart
** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu)
** Tags added: nvidia
--
You received this bug notification because you
** Package changed: ubuntu => xorg (Ubuntu)
--
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/1931318
Title:
Screen brightness of HP laptop is not saved after restart
To manage notifications
You have been subscribed to a public bug:
When the computer is turned on, screen brightness is always 100% instead
of the last set brightness. The computer is HP Envy 15 laptop. The
Ubuntu version is 20.04 LTS.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
This bug was fixed in the package nvidia-settings -
460.73.01-0ubuntu0.21.04.1
---
nvidia-settings (460.73.01-0ubuntu0.21.04.1) hirsute; urgency=medium
* New upstream release (LP: #1925522).
-- Alberto Milone Thu, 13 May 2021
11:52:30 +0200
--
You received this bug
This bug was fixed in the package nvidia-settings -
460.73.01-0ubuntu0.20.04.1
---
nvidia-settings (460.73.01-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1925522).
* debian/patches/08_add_prime_support.patch:
- Stop the timeout after the child is
This bug was fixed in the package nvidia-settings -
460.73.01-0ubuntu0.20.10.1
---
nvidia-settings (460.73.01-0ubuntu0.20.10.1) groovy; urgency=medium
* New upstream release (LP: #1925522).
* debian/patches/08_add_prime_support.patch:
- Stop the timeout after the child is
This bug was fixed in the package nvidia-settings -
460.73.01-0ubuntu0.18.04.1
---
nvidia-settings (460.73.01-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1925522).
* debian/patches/08_add_prime_support.patch:
- Stop the timeout after the child is
Thanks for the bug report. Those look like a few different unrelated
kernel crashes. This usually happens when there is a faulty RAM module
so please use these tools to do a full health check of the system
memory:
https://www.memtest.org/
https://www.memtest86.com/
It will take several
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1598
https://gitlab.freedesktop.org/drm/amd/-/issues/1598
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #920
https://gitlab.freedesktop.org/drm/amd/-/issues/920
--
You received this bug notification because you are
Thanks for your input.
Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher escreveu:
> Can you narrow down which specific firmware file causes the problem?
Ok, I will try.
Also, is it possible and/or worthwhile trying to bisect firmware versions from
the linux-firmware repo? How
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1931251
Title:
package nvidia-kernel-common-390 390.143-0ubuntu0.20.04.1 failed to
Here's a PPA build with the mesa fix Alex mentioned backported:
https://launchpad.net/~superm1/+archive/ubuntu/lp1928393
If you can follow the directions to add that PPA and upgrade to that
mesa package you can see if that indeed fixes it.
** Also affects: mesa (Ubuntu)
Importance: Undecided
Public bug reported:
I saw the following error in the kernel log (kern.log) directly after
the crash occurred. I was watching my system with a tail -f kern.log on
a remote shell.
---
Jun 8 11:29:56 workstation kernel: [49956.666945] general
It might also be the compositor/WM causing leaks in Xorg. Certainly
'metacity' is second in your list, but it is meant to use a lot of
memory because it has to keep copies of all windows. To check to see if
it's the cause you would need to log into a different desktop
environment that's not
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libinput (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1881421
i don't think it is libreoffice. I last restarted X 4 days ago, and
memory usage has gone from under 1% to 8%. Libreoffice has stayed
unchanged at 459376K total (with 2 docs open). metacity has grown but
not conclusively. So I'll give it another week
--
You received this bug notification because
17 matches
Mail list logo
