- This topic has 19 replies, 4 voices, and was last updated Jun 26-11:32 am by HJ.
-
Posts
-
HJ
I might ask when does changing configuration file manually make it invalid?
perhaps not applicable to the current situation, but a frequently-seen example of “when”:
When a configuration file, owned by current user, is edited AsRoot… upon saving, due to its altered file permissions, it becomes inaccessable to, unreadable by, any user-owned processes.
No kidding on the permissions thing. I have become spoiled all those years with Puppy since it runs root by default. The Ubuntu family especially onerous about permissions. The ultimate “Mother, may I?” distributions. Though suspect they are more aimed at folks who will never open a terminal. I finally just gave default user in Lubuntu root access, for most part that made life lot easier, though sometimes still have to sudo but rarely have to enter a password. Oh thinking about it, not important but gnome-ppp in AntiX19 has a problem writing to some file so no DNS server access. I have to start gnome-ppp either sudo from regular terminal or from root terminal. Then it works correctly. It should probably have default root access to files necessary to connect and surf.
SamK
Are you using 32bit version?
Yes, 32bit and 64bit.
I might ask when does changing configuration file manually make it invalid?
You have misinterpreted. Post #23845.
The results you obtained are invalid.
It is the results you posted that are invalid not the file.
The way you did it did not allow the immediate change of the screen to occur. Because Screenlight was prevented from working correctly the results obtained are invalid.
Backlight Brightness is still in menu but you click on it and get error that “controller not found”.
That cannot be reproduced here. Backlight Brightness launches via the menu OK and works correctly. It is an indication that at least part of the problem may be local to your system.
…slowly adjusting it one way or other on the fly.
When you see it working correctly it will become apparent this is also the way for Screenlight.
But honestly no reason for me to lie to you about it.
No one has suggested this other than you.
Xecure
EDIT2: Returned.
Sorry for the delay. I always have trouble booting from the desktop computer. It is the only device that, after selecting to boot, it peeps and everyhting freezes. Anyway.Experience from desktop computer (live-USB, 64bit no persistance).
Backlight Brightness: Doesn’t work. I get this error:
‘no controller found’
It is to be expected, as it is a desktop and I can only change the brightness with the monitor buttons.
Leafpad: Almost the same behaviour as HJ.
Any changes to brightness and contrast that are then saved don’t take effect. Applying changes with Screenlight menu doesn’t take effect.Geany: The same as leafpad.
Perliminary conclusion: HJ’s problem is related to a missing controller for the screen brightness. If this isn’t a virtual machine (but installed), and changing brightness worked with a different distro, figuring out what the controller for the screen was and installing it could help with the problem.
EDIT3: Wait a moment. I have 2 monitors connected to my desktop computer! Maybe I cannot change the brightness because the Screenlight app can not handdle two monitors!
I will try again with only one monitor and publish in a new reply.Ok. Now I have tested with only 1 screen (HDMI) on my desktop.
I have had the exact same error with Backligh Brightness.
I couldn’t modify brightness no matter what editor I used, the same as with Edit2.
The main difference: I COULD modify Contrast. (same behaviour as before: leafpad saved changes took effect and geany only the first save).
I decided to try out the Night brightness: No change at all. (What did change was the color thing, I can’t remember the name now, that took effect inmidiatly after my fisrt “Apply Night Brightness”).Preliminary conclusion: Multimonitors are ignored by Screenlight. Screenlight cannot identify or separate monitors so changes don’t take effect. If only one monitor is detected, Screenlight works OK.
The other problem related to brightness on this desktop may be caused by a missing controller (couldn’t check for updates as my desktops has problems with the net = no connection).
It is quite late now, and I don’t feel like mounting the live environment again today for more testing. Tomorrow I will add the screipt HJ used from the ubuntu answers in the USB drive and see if this makes my monitor birghtness change.I hope something here helps your SamK.
PD: By the way, on the Night color thing, I think there is an error with “most red =1000” comment in the file. “1000” made no change at all with screen color, but “1001” did. It could be my computer, but you can test it out to see yourself if I am wrong.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure
After testing out the script referenced by HJ in comment #23835, on both my desktop with a separate monitor and my laptop (built in monitor).
Results:
On the desktop monitor, though it seemed brighter, it was only a contrast and color change. This was confirmed on my laptop, where I do have support for Backlight Brightness, and where changing the real brightness values changed the real screen brightness (maintaining proper colors). While using the referenced script did lighten the screen, it was more of a color and contrast change. In my results, there is greater control with the Screenlight menu app, except that I cannot increase the contrast as much (cannot make it as “light”/white as with the script).After connecting my HDMI monitor to the laptop and entering a live environment of antiX 19b1, I tested out Backlight Brightness and the laptop’s screen brightness does increase (but not the monitors). Changing this brightness in Screenlight gives the same results (only changes on the laptop’s screen but not the external monitor). Contrast changes in the file don’t work for any of the screens. Color changes in the night file only take effect on the laptop’s screen. Absolutely no changes work on the external monitor.
This is my experience with the limited hardware available for me.Incorrect generalization: Brightness changes (from both Backlight Brightness and Screenlight) only work on systems with the correct controllers, and only in one monitor (in multimonitor sets). Contrast has problems working on multimonitor sets.
Possible solutions:
– Being able to select the monitor and apply the changes for the selected monitor. This would increase the number of files in the screenlight folder and the complexity of the program.
– Change the program to select between “Hardware Brightness” (current workings of brightness) and “Software Brightness” using xrandr instead by modifying the “xrandr brightness values” when no controller is detected.
– Warn the user about multimonitor/controller problems. Include a modified version of xRandr script (referenced above) for the user to use.Sorry for wasting mine and your time.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure is certainly thorough and has very succinct way of putting the facts. Meaning he went lot more in depth and says it lot more clearly than I do. So apparently this all depends on the hardware. My hardware just definitely isnt supported by Backlight Brightness (no controller found) and seems not to be by Screenlight. At least that script works for me. Though still experimenting with it, doesnt seem to hold the settings on reboot.
- You must be logged in to reply to this topic.
