Bear in mind I have had this installed since 16.04 was in development and now in 16.10.Source: https://ubuntuforums.org/showthread.php?t=2340067
So some time has passed since then...but I seem to remember struggling with the 64 bit .deb
Went through some old notes and found my install went like this.You have already done thisCode:sudo dpkg --add-architecture i386
And this also is already doneCode:sudo apt-get update
I choose the 32bit .debCode:wget http://download.teamviewer.com/download/teamviewer_i386.debCode:sudo dpkg -i --force-depends teamviewer_i386.deb
In case “dpkg” indicates missing dependencies, complete the installation by executing the following command:
complete the installation by executing the following command:Code:sudo apt-get install -f
Code:sudo teamviewer --daemon start
Monday, June 18, 2018
Ubuntu 16 install Teamviewer 12
Sunday, June 17, 2018
Format usb stick / drive using Linux
Get the tool:
sudo apt-get update
sudo apt-get install dosfstools
Mount the stick via GUI
Check its path using:
df -m
(yes there are other more sleek ways to check it)
unmount the drive:
sudo umount /dev/sd<...>
sudo apt-get update
sudo apt-get install dosfstools
Mount the stick via GUI
Check its path using:
df -m
(yes there are other more sleek ways to check it)
unmount the drive:
sudo umount /dev/sd<...>
format (FAT32 used as example here):
mkdosfs -F 32 -I /dev/sd<...>
Do not mix up drives, this erases all data irreversibly!
Friday, June 15, 2018
Set older kernel as default grub entry
First, make a backup copy of /etc/default/grub. If something goes wrong, you can easily revert to the known-good copy. sudo cp /etc/default/grub /etc/default/grub.bak
Then edit the file using the text editor of your choice (e.g. gedit, etc.).
sudo -H gedit /etc/default/grub
Find the line that contains
GRUB_DEFAULT - this is what you'll want to edit to set the default. You must know the full name of the kernel you want - e.g. Ubuntu, with Linux 3.13.0-53-generic - along with the full name of the "advanced menu" - e.g. Advanced options for Ubuntu.To list all kernels do:
dpkg --list | grep linux-imageYou then combine those two strings with
> and set GRUB_DEFAULT to them as: GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 3.13.0-53-generic" (including quotes).Save it, then build the updated grub menu.
sudo update-grub Sources:https://askubuntu.com/questions/216398/set-older-kernel-as-default-grub-entryhttps://www.cyberciti.biz/faq/howto-display-all-installed-linux-kernel-version/
KDE Linux update settings 16.04, prevent automatic updates
Start->System->Update Manager
More...->Advanced->Configure Software Sources
Enter sudo password for current account
In "Software Sources" choose "Updates" tab
Select radio button "Only notify about available updates"
More...->Advanced->Configure Software Sources
Enter sudo password for current account
In "Software Sources" choose "Updates" tab
Select radio button "Only notify about available updates"
Press “Close”, the choices will be saved this way.
Saturday, April 21, 2018
How to set up a single Dropbox folder on dual-boot Windows and Linux system
https://medium.com/@hivickylai/maintain-one-dropbox-folder-with-dual-boot-windows-and-linux-d338d790675a
Friday, April 20, 2018
Keeping git repositories on different hosts in sync
Source: https://softwareengineering.stackexchange.com/questions/195456/keeping-git-repositories-on-different-hosts-in-sync
Yes, that's exactly the beauty of DVCS such as git. You can use any
number of different repos with the same state as the one on bitbucket or
github.
Even you local copy (the repository on your computer) is usually a full clone of the remote repo.
The only thing you have to do to keep multiple repos in sync is pulling for one (usually called origin or upstream) and pushing to the backup copies.
Even you local copy (the repository on your computer) is usually a full clone of the remote repo.
The only thing you have to do to keep multiple repos in sync is pulling for one (usually called origin or upstream) and pushing to the backup copies.
Unfortunately all is not as shiny. See the cautionary take of KDE near-disaster. That is, make sure the backup does not delete things (branches, repositories, etc.) that were deleted on the backed up server.
Clone the remote repository, then pull all
updates (all branches) to it in regular intervals. A git clone contains
the history, it's not like an svn checkout that has only the latest
version.
Friday, April 13, 2018
older FIJI Jython scripts won't execute
workaround: replace
if __name__=='__main__':
with
if __name__ in ['__builtin__', '__main__']:
Subscribe to:
Posts (Atom)
