I install jupyterlab on RHEL 7 (RedHat) with
pip3 install jupyterlab
Now I am trying to start it. I need to run it only locally (no need to open any ports). I found where file is located, but still cannot launch it. I tried jupyterlab and got back command not found.... I am guessing I need to add it to PATH, but I still expect it to run when launched from the same directory. Whatever limited experience I have with Ubuntu, does not work on RedHat.
OS: Linux Mint 18.3 Sylvia
DE: xfce4
I have to set up several PCs and want to write a script which configures the launcher-applets in the panel. So the script would contain in the end something like:
sudo cp ./my-predefined-config-file.type /path/to/location/
Edit:
I figured out that the launchers are saved at the following file-path:
/home/user/.config/xfce4/panel/
However copying a launcher, from another system, into this directory does not make them appear in the panel:
~$ cp -r ~/Desktop/launcher-1/ ~/.config/xfce4/panel/
So there must be still somewhere a config-file which i have to edit in order to make the launcher appear in the panel.
PS:
After changing something I am of course always reloading xfce in order to see the changes:
~$ xfce4-panel -r && xfwm4 --replace
For the record, on my Linux Mint 19.2 with Cinnamon install (not: xfce4 as in the question), the panel launcher config file is at
~/.cinnamon/configs/panel-launchers#cinnamon.org/3.json
Background: I have created an Ubuntu VirtualBox from LAPP stack and added the Ubuntu desktop (Unity: sudo apt-get install ubuntu-desktop). Now I am attempting to install the MCR without loosing Unity.
Download MCR zip and extract to MCR_SOURCE
Go to my folder that contains the files: cd /media/sf_shared/MCR_ SOURCE
Change installer_input.txt file:
destinationFolder=/opt/MCR
agreeToLicense=yes
outputFile=/opt/install.log
mode=silent
product.MATLAB
product.MATLAB_Builder_JA
# Note: To find out the required toolboxes >> start Matlab >> run your code and find out which toolboxes were used with: license('inuse')
Install MCR: sudo ./install -inputFile /media/sf_shared/MCR_SOURCE/installer_input.txt >> success
Restart Ubuntu >> test whether Ubuntu’s Unity still exists >> everything is fine
Attention the next step will “ kill ” your Ubuntu desktop configuration!!! (i.e. copy your hardisk, anything you must do to recover quickly) – now configure: sudo gedit /etc/environment
LD_LIBRARY_PATH="/opt/MCR/v84/runtime/glnxa64:/opt/MCR/v84/bin/glnxa64:/opt/MCR/v84/sys/os/glnxa64:${LD_LIBRARY_PATH}"
XAPPLRESDIR="/opt/MCR/v84/X11/app-defaults"
# Note: X11/app-defaults folder has not been created during installation
Restart Ubuntu >> Unity is gone, recovery attempts such as deleting the above lines do not recover Unity; reinstalling the Ubuntu desktop does not help either.
I have tried an alternative route with exporting the variables, which also "kills" Unity. By the way this affects all users.
Any ideas?
It is not necessary to register these environment variables in /etc/environment, which means that the Unity sidebar will not be affected.
Instead register the environment variables temporarily either as local user or via sudo -i:
export LD_LIBRARY_PATH="/opt/MCR/v84/runtime/glnxa64:/opt/MCR/v84/bin/glnxa64:/opt/MCR/v84/sys/os/glnxa64:${LD_LIBRARY_PATH}"
export XAPPLRESDIR="/opt/MCR/v84/X11/app-defaults"
Now it is possible to run Matlab Apps without "killing" Ubuntu's desktop. For instance to run the Java compiled makesqr.m file.
java -classpath "/opt/MCR/v84/toolbox/javabuilder/jar/javabuilder.jar:/media/sf_shared/for_testing/makesqr.jar" makesqr.Class1 5
The Java package makesqr was created using Matlab's JavaBuilder tutorial. This was done on my Windows 7 machine, which runs Matlab R2014b.
Please ensure that the owner and permissions of the /opt/MCR and /media/sf_shared/for_testing folders are set correctly (see here for details).
I am working on a project similar to the one at http://www.instructables.com/id/Raspberry-Pi-Wall-Mounted-Google-Calendar/?ALLSTEPS
Similarly, I need my pi to stay on constantly. I have the regular Raspbian OS installed and I am using Iceweasel browser to run a web application all day.
I have tried every single one of these suggestions from this link http://www.bitpi.co/2015/02/14/prevent-raspberry-pi-from-sleeping/
Yet the pi fails to stay on longer than 10 minutes. Any help would be greatly appreciated.
I installed xscreensaver
sudo apt-get install xscreensaver
Once installed, go to Rpi's desktop "Menu" (left top corner)
Go to preference --> screensaver.
You will see a screen saver main menu. In the mode drop-down menu, select "disable screensaver" then close the window.
Reboot the Raspberry PI.
It should work now.
You don't need to install lib, just edit lightdm
1 - Open lightdm using your prefer text editor, eg using default editor(nano).:
sudo nano /etc/lightdm/lightdm.conf
2 - Add this line
xserver-command=X -s 0 -p 0 -dpms
I recently installed Raspian Buster with Desktop (circa 2019-September) - the smaller install with the Desktop, but without the "recommended software". I found there are two settings that have to be changed as either one of them will blank the screen in ten minutes under the default settings.
set screen saver timeout to zero:
xset s 0
and set dpms (EnergyStar) to disabled:
xset -dpms
This way I haven't needed to install anything (no screensaver). It was confusing because I'd tried both items, but it wasn't until I learned they both were blanking the screen at ten minutes that I saw what was going on. As this has tested out OK, the next step for me is to put them into an autostart routine.
ps Verify your settings with
xset q
Without installing anything, official Raspberry Pi doc:
On the Console
If you are using the Raspberry Pi solely on the console (no desktop GUI), you need to set the console blanking. The current setting, in seconds, can be displayed using
cat /sys/module/kernel/parameters/consoleblank
Here, consoleblank is a kernel parameter. In order to be permanently set, it needs to be defined on the kernel command line.
sudo nano /boot/cmdline.txt
Add consoleblank=0 to turn screen blanking off completely, or edit it to set the number of seconds of inactivity before the console will blank. Note the kernel command line must be a single line of text.
https://www.raspberrypi.org/documentation/configuration/screensaver.md
Simply enter the config with sudo raspi-config and disable screen blanking in the display settings.
I've created a picture frame with a pi 3 and want to stop the screen going blank. I installed xscreensaver as in answer 22 and it's working a treat:
sudo apt-get install xscreensaver
After install, went to Rpi's desktop "Menu" (left top corner)
Went to preference ---> screensaver.
Then In mode : section, selected "disable screensaver" and closed.
Rebooted Rpi.
I had the same issue with Raspbian OS that was installed on raspberry Pi device. I just installed xscreensaver by using the following command in default Command panel.
sudo apt-get install xscreensaver
After installation is completed, Go to the menu in the left corner and select preference. First time you will see a pop up to enable xscreensaver on your screen. Just accept it. After that you can disable the screensaver.
Yesterday I installed Teamviewer 7 on my Centos 5.8 desktop. After a reboot, am not able to see the login screen. Only a blue color screen is visible.
I read https://superuser.com/questions/403548/os-x-stuck-at-blue-screen-after-installing-teamviewer-host-and-rebooting?rq=1
But how do I do that on Centos?
I know that to login to Single User Mode, we need to press a key while the os boots up. And then type single in the cmd. And then?
Once in Single User Mode, you can try to remove TeamViewer from your system.
For example, if you have installed TeamViewer by running the rpm -ivh teamviewer_linux.rpm command, you can run the rpm -e teamviewer_linux command to uninstall it.
I don't think that the Mac OS link you've referred to can be very useful in your case.
If you peek into the teamviewer_linux.rpm (for example by running the command rpm -qpl teamviewer_linux.rpm) you won't find any "Launch Agents and Daemons", since on CentOS TeamViewer is wrapped around a Windows Emulator (wine).
By default the TeamViewer files gets installed in the /opt/teamviewer folder; the only exception is the startup script /usr/bin/teamviewer7.
Finally, the rpm post-installation script does nothing more and nothing less than create a desktop icon and add a menu entry, so I can't really understand how the TeamViewer installation could have broken your system.