I started a VNC session 4 days ago to run a test that is 72 hours long. I want to see an output from a command I ran when I was setting everything up, but when I scroll all the way up, I do not see it anymore in the terminal log. Is there any way I can access this again?
Related
I am trying to get a GUI running on an AWS Centos 7 instance. Tiger vnc seems to run fine and I can get connected with the tigervnc viewer. However, all I get is a grey screen with 4 checkboxes in the upper right hand corner.
I installed Gnome and Server with GUI and I have tried changing my xstartup a hundred different ways, but I always get a grey screen. See the screenshot.
How can I get the gnome gui to work over my vnc session?
thanks
I found out that you will get this issue when using cPanel and WHM if you have the user in a jailed root. Open up the access and the full OS will load.
I would imagine that there is some way to work around this to keep a jailed root, but I am not a linux guru, so I don't know how to accomplish that.
I have a cron job whose command line looks like:
30 5 * * * osascript -e 'tell application "Terminal" to do script "bash-script-file"'
FWIW the base script file sets some environment variables and then runs a Ruby program.
Prior to last week, most days this ran just fine, but occasionally (~ twice/month) it would hang until I either unlocked the screen or attached remotely to the system. At that time I would see a terminal screen with a message about new mail and a command line prompt with the bash-script-file on it. At that point, I could wait and the script would proceed to run normally. I have checked System Settings and the computer is set to sleep never. I'm not locking the screen (instead allowing it to go to sleep), and of course I have the screen saver locked, requiring a password to wake up.
Last week (about five days ago), I added a second cron job of the same form (running another bash script that started another Ruby program), and since then, both jobs have hung every day until I attached remotely. What is causing this? What can I do to resolve it?
tl;dr cron-scheduled terminal jobs are hanging until the screen unlocks.
When I work from home, I remote desktop into my machine at work. Often when I do this, when I get to work and want to use the machine, the display is screwed up (see picture below) and I have to reboot or at least log off to fix it.
I don't want to log off or reboot as it takes forever. I was trying to fix it some other way. I went to the display, changed the resolution, and then changed it back hoping that would fix it but it did not.
Any suggestions?
When I set a breakpoint for an app which is currently running in full screen mode, I can not switch to any other screen when the breakpoint is reached. I'm stuck in the full screen app. The only chance I have is to hard reset the machine. I just found a single 7 year old post with Google that exactly describes my dilemma. There MUST be a solution (except having a 2nd machine) after 7 years seeing how much Apple is promoting this dreaded full screen mode.
After a fresh restart, the notify-send command on Cinnamon desktop successfully shows a couple of notifications. But afterwards (within the first 5 minutes, and after 3 notifications have been executed) they don't appear anymore; neither on the desktop nor in the history of notifications in the panel applet.
The command itself outputs nothing, and the man page doesn't mention anything about an error log. Is there some simple anti-spam limit maybe per-application? How do I find out why this happens?