Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Disable Solaris Gnome 3 screen blanker Post 303043782 by Michele31416 on Thursday 6th of February 2020 02:31:21 PM
Old 02-06-2020
Disable Solaris Gnome 3 screen blanker

One of the more annoying features of the Gnome 3 desktop in Solaris 11 is its insistence on blanking the screen after five minutes of inactivity. And for the life of me I can't figure out how to make it top doing that. I'm running it in a VNC viewer so the host PC can take care of screen blanking.

I tried the Dconf Editor going to org -> gnome -> settings-daemon -> plugins -> power and unchecked "idle-dim". sleep-inactive-ac-timeout was already et to 0.

I tried org -> desktop -> applications -> lockdown -> check "disable-lock-screen".

I tried exiting the vnc viewer and strarting a new vnc server. But none of this works. The screen still blanks after five minutes. There's plenty of stuff on the web on how to do this in Linux and indeed I was able to do it in a Ubuntu VM running Gnome 3 but I just can't get it to work in Solaris 11. What am I missing here?

UPDATE

There's something about posting a question in public that causes the answer to come to you. In this case here is what to do.

Run the DConf Editor (Top menu Applications-> System Tools -> dconf editor) and go to org -> gnome -> desktop -> session and set "idle-delay" to 0. The screen will no longer blank out. No reboot needed. I'll leave this topic up because AFAIK this is the only place on the web that has this secret,

Last edited by Michele31416; 02-06-2020 at 03:56 PM..
This User Gave Thanks to Michele31416 For This Post:
 

10 More Discussions You Might Find Interesting

1. Solaris

Gnome on Solaris 10

I have just installed Gnome on Solaris 10, I am wondering how to get it listed in the “session” selection box on the login screen, as it currently isn't. Any Ideas? :o (1 Reply)
Discussion started by: Dredz
1 Replies

2. UNIX for Dummies Questions & Answers

Solaris Express Slow to load Gnome

Hi, I recently installed the latest Solaris Express Developers Edition. I'm building a NAS and want to use RAID Z, and Solaris 10 didn't have the drivers for my HD controller card. Everything is up and running fine, but I notice it takes a good 8 minutes to load gnome (or X, not sure where it... (2 Replies)
Discussion started by: ciscocbee
2 Replies

3. Linux

Disable Maximize/Resize on GNOME

Hello, I would like to know wether if its possible or not to do the following: 1) Disable the maximize button on a "particular" window. 2) Disable the resize option on that "particular" window. 3) Disable the right-click properties that appear when you click on a minimized app thats sitting... (2 Replies)
Discussion started by: preacheronsunda
2 Replies

4. Solaris

How to install gnome in solaris

How to install gnome in solaris 9 and 10, how to enable java environment in solaris 9 and 10. Thanks in Advance (1 Reply)
Discussion started by: durgaprasadr13
1 Replies

5. UNIX for Advanced & Expert Users

How to disable the clearing of the first page when executing screen tool

Hi Guy, In order to monitor the user sessions, I have put the screen tool in the .profile in order to record the whole session. However, when the user logs in, the screen command is executed and the screen is first cleared, then the command prompt appears. so, I basically want to disable the... (2 Replies)
Discussion started by: saad26
2 Replies

6. Solaris

Gnome Packages on Solaris 10 u6

If my system is supposed to be a pure oracle database server can i remove all the GNOME packages from the system ? Currently system is installed with Everything+OEM and i want the image to be as small as possible remove the unnecessary softwares from it so that its a master image for other servers.... (2 Replies)
Discussion started by: fugitive
2 Replies

7. Solaris

Gnome in Solaris 9

Hi My problem is that I kind of opened gnome environment from the cde environment and now I do not know how to turn it off so any suggestions will be much appreciated. and I am running Solaris 9 as root user I am also a beginner in unix Thanks in advance (4 Replies)
Discussion started by: Theeb
4 Replies

8. Red Hat

command line tool to disable screen lock and/or screen saver

Hi, I have a simple question : how to disable screen lock and/or sreen saver with command line with RHEL5.4 ? (1 Reply)
Discussion started by: albator1932
1 Replies

9. Solaris

Solaris 11 disable IPv6

I've new installed Solaris 11 on Sparc T4-1. I'd like to disable IPv6 but with no luck. lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 net0: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 2 inet... (6 Replies)
Discussion started by: samer.odeh
6 Replies

10. UNIX and Linux Applications

vnc viewer presents black screen along with GNOME settings daemon errors.

Hello folks, I'm remotely connecting through VNC to two machines, each running Red Hat 5.9, from mine which is running Windows 7. Both connections were working well before. However, now one of the machines only gives me a black screen, with a pop up that says: "There was an error starting... (1 Reply)
Discussion started by: Miguel E. Perez
1 Replies
vncserver(1)						     Virtual Network Computing						      vncserver(1)

NAME
vncserver - start or stop a VNC server SYNOPSIS
vncserver [:display#] [-name desktop-name] [-geometry widthxheight] [-depth depth] [-pixelformat format] [-fp font-path] [-fg] [-autokill] [Xvnc-options...] vncserver -kill :display# DESCRIPTION
vncserver is used to start a VNC (Virtual Network Computing) desktop. vncserver is a Perl script which simplifies the process of starting an Xvnc server. It runs Xvnc with appropriate options and starts a window manager on the VNC desktop. vncserver can be run with no options at all. In this case it will choose the first available display number (usually :1), start Xvnc with that display number, and start the default window manager in the Xvnc session. You can also specify the display number, in which case vnc- server will attempt to start Xvnc with that display number and exit if the display number is not available. For example: vncserver :13 Editing the file $HOME/.vnc/xstartup allows you to change the applications run at startup (but note that this will not affect an existing VNC session.) OPTIONS
You can get a list of options by passing -h as an option to vncserver. In addition to the options listed below, any unrecognised options will be passed to Xvnc - see the Xvnc man page, or "Xvnc -help", for details. -name desktop-name Each VNC desktop has a name which may be displayed by the viewer. The desktop name defaults to "host:display# (username)", but you can change it with this option. The desktop name option is passed to the xstartup script via the $VNCDESKTOP environment variable, which allows you to run a different set of applications depending on the name of the desktop. -geometry widthxheight Specify the size of the VNC desktop to be created. Default is 1024x768. -depth depth Specify the pixel depth (in bits) of the VNC desktop to be created. Default is 24. Other possible values are 8, 15 and 16 - any- thing else is likely to cause strange behaviour by applications. -pixelformat format Specify pixel format for Xvnc to use (BGRnnn or RGBnnn). The default for depth 8 is BGR233 (meaning the most significant two bits represent blue, the next three green, and the least significant three represent red), the default for depth 16 is RGB565, and the default for depth 24 is RGB888. -cc 3 As an alternative to the default TrueColor visual, this allows you to run an Xvnc server with a PseudoColor visual (i.e. one which uses a color map or palette), which can be useful for running some old X applications which only work on such a display. Values other than 3 (PseudoColor) and 4 (TrueColor) for the -cc option may result in strange behaviour, and PseudoColor desktops must have an 8-bit depth. -kill :display# This kills a VNC desktop previously started with vncserver. It does this by killing the Xvnc process, whose process ID is stored in the file "$HOME/.vnc/host:display#.pid". The -kill option ignores anything preceding the first colon (":") in the display argument. Thus, you can invoke "vncserver -kill $DISPLAY", for example at the end of your xstartup file after a particular application exits. -list Lists running VNC servers. -fp font-path If the vncserver script detects that the X Font Server (XFS) is running, it will attempt to start Xvnc and configure Xvnc to use XFS for font handling. Otherwise, if XFS is not running, the vncserver script will attempt to start Xvnc and allow Xvnc to use its own preferred method of font handling (which may be a hard-coded font path or, on more recent systems, a font catalog.) In any case, if Xvnc fails to start, the vncserver script will then attempt to determine an appropriate X font path for this system and start Xvnc using that font path. The -fp argument allows you to override the above fallback logic and specify a font path for Xvnc to use. -fg Runs Xvnc as a foreground process. This has two effects: (1) The VNC server can be aborted with CTRL-C, and (2) the VNC server will exit as soon as the user logs out of the window manager in the VNC session. This may be necessary when launching TigerVNC from within certain grid computing environments. -autokill Automatically kill Xvnc whenever the xstartup script exits. In most cases, this has the effect of terminating Xvnc when the user logs out of the window manager. FILES
Several VNC-related files are found in the directory $HOME/.vnc: $HOME/.vnc/xstartup A shell script specifying X applications to be run when a VNC desktop is started. If this file does not exist, then vncserver will create a default xstartup script which attempts to launch your chosen window manager. $HOME/.vnc/passwd The VNC password file. $HOME/.vnc/host:display#.log The log file for Xvnc and applications started in xstartup. $HOME/.vnc/host:display#.pid Identifies the Xvnc process ID, used by the -kill option. SEE ALSO
vncviewer(1), vncpasswd(1), vncconfig(1), Xvnc(1) http://www.tigervnc.org AUTHOR
Tristan Richardson, RealVNC Ltd. D. R. Commander VNC was originally developed by the RealVNC team while at Olivetti Research Ltd / AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. Many other people participated in development, testing and support. TigerVNC 13 Mar 2011 vncserver(1)
All times are GMT -4. The time now is 06:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy