[SOLVED] Slackware-current - today's update screwed up laptop monitor power settings
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Rep:
Slackware-current - today's update screwed up laptop monitor power settings
Slackware-current 64-bit
System update: 6/16/2022
After update laptop monitor setting are screwed up: after login screen is very dark. It flickers and then it goes dim.
Only way to fix this it set brightness in the settings.
However brightness settings on AC power are 70% and screen is still very dark.
If I move slider anywhere and back to 70%, screen is bright again. Unfortunately, after reboot monitor power settings are screwed up again.
Also I have different brightness when system is on battery. These settings do not work at all when unplugging laptop.
Chances are you didn't review the new config files and select to keep any you have customized. They should still be there now labeled something like /etc/foo/foo.orig and are easily restored.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Original Poster
Rep:
Quote:
Originally Posted by enorbet
Chances are you didn't review the new config files and select to keep any you have customized. They should still be there now labeled something like /etc/foo/foo.orig and are easily restored.
Thank you enorbet but no, I did not see a prompt regarding new config files.
Chances are you didn't review the new config files and select to keep any you have customized. They should still be there now labeled something like /etc/foo/foo.orig and are easily restored.
Chances are GKH and co screwed up another kernel release, it took them a month to fix a nasty usb bug a year ago, OP might want to track downthe previous kernel set and install it, I think Tadgy has a server of them but I forget the URL.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Original Poster
Rep:
Quote:
Originally Posted by Nobby6
Chances are GKH and co screwed up another kernel release, it took them a month to fix a nasty usb bug a year ago, OP might want to track downthe previous kernel set and install it, I think Tadgy has a server of them but I forget the URL.
I think that this is an issue with plasma. I still have 5.17.13 installed. So I just rebooted to 5.17.13 and nothing changed: when plugging/unplugging laptop, screen flickers, but brightness does not change.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.