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.
It might help if you could be more specific about what you want to do. There's an awful lot of stuff about dbus on the internet and providing that information might help persons decide what might be relevant or even answer your question directly.
frankbell, yea sorry...i really am not great at asking questions. what i want to do is for my screen not to blank out during a long period of "no input (keyboard)" interaction. my lcd screens have an "off" adjustment that is set to off, so that they are not green at all and always on and i just checked them to make sure they are all set to off.
since the update to 14.2 my monitors have been turning off, meaning they are not getting a signal from the source because the screen tells me the source input has stopped inputting, as if i unplugged the video cable from the input port. i clearly did not so i thought that there is something in the new kernel or a daemon that is doing that which led me to UPower and etc. so how do i find what is blanking out my screens? as of tonus what i have found is just may be telling me that i have the facade of ability to control this system but not really, apparently.
so i hope this answers your question, because as i was reading about dbus i thought i was just missing where to find the program to change the suspend and hibernation settings to no/no. is there any other daemons that will control the signal blank of stdout?
and tonus i am beginning to believe that too. but still left wondering why/how the video signal is being stopped from being sent from the machine.
Why don't you want your monitors to turn off after a period without keyboard input? Are they turning when you're playing games (and your system is receiving gamepad not keyboard input) and watching movies? See this thread for a lot of ideas for how to deal with that:
dugan, this particular user interface is a command line environment with only a keyboard. if i move to another interface (on another networked machine setup) after about 5 or so minutes the screen on the first system blanks out. before i upgraded to the 14.2 ver. i was using slackware 10.4 and did not have this problem. all the machines i have upgraded now all blank out after a short period of inactivity weather command line or with xterm running.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.