I have a virtual machine with CentOS 7 at school, but I need to work from home. So, I followed a tutorial to install Gnome and another to create a VNC server, all this to install TeamViewer. Then, I install TeamViewer 11, but when I open it, it says the famous message: Not ready, Please check your connection I tried to input proxy settings, but it didn't save the changes, so I had to edit the global.conf file. I know that the proxy is well in the system because I can navigate; I can even ping 178.77.120.1, and it works. But the problem still remains. Then, searching the web, I saw I could change the SELinux config to permissive. I do that in another virtual machine, and that works, but it doesn't work on my machine. It has a Wine problem. I try to fix it using the following: # setsebool -P mmap_low_allowed 1 but that doesn't work. Another solution was to add to mdns4 to host in /etc/nsswitch.conf, but it doesn't work. So I decide to uninstall, using: rpm -qa | grep teamviewer rpm -e But when I installed TeamViewer again, it loaded the proxy settings, so I think it didn't completely remove them. Here's today's log Start: 2016/09/08 08:37:06.584 (UTC-5:00) Version: 11.0.57095 ID: 0 Loglevel: LogAll (0) License: 0 Server: master14.teamviewer.com IC: 0 CPU: x86 Family 6 Model 45 Stepping 7, GenuineIntel CPU extensions: p8 OS: Lx CentOS 7 (Core) (32-bit) IP: xx.xx.xxx.xxx Proxy-Settings: Type=0 IP= User= AppPath: C:\TeamViewer\TeamViewer.exe UserAccount: root 2016/09/08 08:37:06.588 8 29 GX2 AutoLogin::Login: enabled: 0 2016/09/08 08:37:06.803 8 29 GX2 CMain::LoadResourceDLLs(): No custom resource dll found 2016/09/08 08:37:06.805 8 29 GX2 Win32_GUI::FontReallyExists: 'Segoe UI' found 0 matches. 2016/09/08 08:37:06.805 8 29 GX2 Win32_GUI::FontReallyExists: 'Liberation Sans' found 4 matches. 2016/09/08 08:37:06.814 8 29 GX2 InterProcessBase::StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector 2016/09/08 08:37:06.814 8 29 GX2 Opening local TCP connection to 127.0.0.1:5942 2016/09/08 08:37:06.815 8 29 GX2 Local TCP connection established 2016/09/08 08:37:06.815 8 29 GX2 Process ID: L 32511 / W 8 2016/09/08 08:37:06.902 8 29 GX2 SettingsIPCReception receive a SYNCHRONISE Settings command : UserSettings 2016/09/08 08:37:06.904 8 29 GX2 Received Control_InitIPC_Response processtype=1 2016/09/08 08:37:06.904 8 29 GX2 Received Control_InitIPC_Response runningProcesses=3 2016/09/08 08:37:06.904 8 29 GX2 Control_InitIPC_Response: all processes 3 completely initialized 2016/09/08 08:37:06.940 8 29 GX2!! ProxySearch.GetProxiesFromPAC: WinHttpGetProxyForUrl(WPAD) failed for URL 'http://www.teamviewer.com/ ' with error 12166, Errorcode=12166 2016/09/08 08:37:06.944 8 29 GX2!! ProxySearch.GetProxiesFromPAC: WinHttpGetProxyForUrl(WPAD) failed for URL 'https://www.teamviewer.com:443/ ' with error 12166, Errorcode=12166 2016/09/08 08:37:06.944 8 29 GX2 ProxySearch: found WinHTTP proxy: http//10.20.4.15:3128 2016/09/08 08:37:06.946 32646 4091542336 QX2 SessionBusWatcher: suitable bus found with address "unix:abstract=/tmp/dbus-LumdutjnU5,guid=8c230a14389528c505b45eeb57d008e6" 2016/09/08 08:37:07.070 8 9 GX2!! GetSimpleDisplayCertNameFromFile: File 'C:\TeamViewer\tv_w32.dll' does not exist., Errorcode=2 2016/09/08 08:37:07.070 8 9 GX2!! VerifyTeamViewerSignature() : WinVerifyTrust failed, result=2, Errorcode=2 2016/09/08 08:37:07.070 8 9 GX2!! MachineHooks: Library not found, Errorcode=2 2016/09/08 08:37:07.074 8 9 GX2 MachineID m=0 - 1 2016/09/08 08:37:07.077 8 9 GX2 TVUpdate::Init() Version-URL: download.teamviewer.com/download/update/ Update-URL: download.teamviewer.com/download/update/ 2016/09/08 08:37:07.077 8 9 GX2 TVUpdate::Init() Preview Channel Number : 1 2016/09/08 08:37:07.165 8 9 GX2!! TVW Wine: SetWindowManagerClassHint: No such window, Errorcode=120 2016/09/08 08:37:07.195 8 9 GX2!! TVW Wine: SetWindowManagerClassHint: No such window 2016/09/08 08:37:07.199 8 9 GX2!! TVW Wine: SetWindowManagerClassHint: No such window 2016/09/08 08:37:07.218 8 9 GX2 ManagerHolderStateMachine: Switching from None to NotReady 2016/09/08 08:37:07.219 8 21 GX2 ChatManager::ChatManager: created 2016/09/08 08:37:07.219 8 21 GX2 ChatManager::Factory: ChatManager created 2016/09/08 08:37:07.219 8 21 GX2 IncomingBetterChatCommandHandler::IncomingBetterChatCommandHandler: created 2016/09/08 08:37:07.219 8 21 GX2 IncomingChatCommandRegistration::Start: registering for ready state properties 2016/09/08 08:37:07.220 8 9 GX2!! DragDropRegistration: could not register window, HR=80040155 2016/09/08 08:37:07.222 8 9 GX2!! BuddyWindow.LoadWindowPosUnscaled: bad lexical cast 2016/09/08 08:37:07.227 8 9 GX2 AccountLoginGUI::CreateLoginKey(): [OnlineState] System is set to Visible. 2016/09/08 08:37:07.234 8 9 GX2!! TVW Wine: SetWindowManagerClassHint: No such window, Errorcode=120 2016/09/08 08:37:07.272 8 9 GX2 CMainWindow::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0 2016/09/08 08:37:07.278 8 9 GX2!! ServerControl: RegisterPowerSettingNotification failed with error 0 2016/09/08 08:37:07.323 32645 139768218244864 gX2 PulseAudio: Connected to server 'unix:/run/user/0/pulse/native' (protocol version 30, library version 6.0.0 2016/09/08 08:37:07.324 32645 139768311990016 gX2 PulseAudio: Connection established 2016/09/08 08:37:07.456 8 33 GX2!! WineMixer: Unable to initialise mixer -1 -1 2016/09/08 08:37:07.456 32645 139768218244864 gX2 PulseAudio: Exit main loop (0), err=-2 2016/09/08 08:37:36.780 8 9 GX2 CMainWindow::InitCloseTV(): Prepare to close TeamViewer 2016/09/08 08:37:36.780 8 9 GX2!! ServerControl: UnregisterPowerSettingNotification failed with error 0 2016/09/08 08:37:36.781 8 9 GX2!! TVW Wine: SetWindowManagerClassHint: No such window 2016/09/08 08:37:36.785 8 9 GX2 Chat::Stop: Stopping chat 2016/09/08 08:37:36.785 8 9 GX2 Chat::Stop: Cancelling of Start 2016/09/08 08:37:36.786 8 9 GX2 ChatManager::UnregisterIncomingCommandRegistration: destroying incomingCommandRegistration 2016/09/08 08:37:36.786 8 9 GX2 IncomingChatCommandRegistration::Stop: disconnecting ready state properties 2016/09/08 08:37:36.787 8 9 GX2 ChatManager::Close 2016/09/08 08:37:36.787 8 9 GX2 ChatManager::UnregisterIncomingCommandRegistration: destroying incomingCommandRegistration 2016/09/08 08:37:36.787 8 9 GX2 ChatManager::ClearAccountChat: clearPersistently = 0 2016/09/08 08:37:36.788 8 9 GX2 ChatManager::ClearNonAccountChat 2016/09/08 08:37:36.789 8 9 GX2 ChatManager::~ChatManager: destroyed 2016/09/08 08:37:36.789 8 9 GX2 IncomingBetterChatCommandHandler::IncomingBetterChatCommandHandler: destroyed 2016/09/08 08:37:36.789 8 9 GX2!! MainWindow.OnDestroy: WTSUnRegisterSessionNotification failed with error 0 2016/09/08 08:37:36.792 8 9 GX2 CMainWindow::OnDestroy(): Closing TeamViewer 2016/09/08 08:37:36.907 32645 139768235030272 gX2 XClipboard: Shutting down event loop 2016/09/08 08:37:36.955 32645 139768525608768 gX2 TVGuiSlave.64: Terminated 2016/09/08 08:37:37.008 8 9 GX2!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 1 failed with error 2 2016/09/08 08:37:37.008 8 9 GX2!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 1 failed with error 2 2016/09/08 08:37:37.009 5552 4147260224 S CInterProcessNetwork: Received DisconnectIPC from processID 32511 (ProcessType: 2 in Session 2) with reason 1 2016/09/08 08:37:37.009 5552 4147260224 S Process 32511 in session 2 has terminated 2016/09/08 08:37:37.009 5552 4147260224 S TerminalServer::ProcessTerminated_Finalize: process 32511 terminated 2016/09/08 08:37:37.009 5552 4147260224 S SysSessionInfoManager: updating session information for session 2 from GUI 2016/09/08 08:37:37.009 5552 4094196544 S XSession: 2 [SysSession 2 [type=1 tty=4294967295 pseudotty=1 info=1 id= user=root state=unknown active=0 reliable=0]] 2016/09/08 08:37:37.009 5552 4094196544 S Updated sessions: [ 1 ] [ 2 root ] [ 9 ] 2016/09/08 08:37:37.009 5552 4094196544 S UpdateOnlineState m_ManualStop 2016/09/08 08:37:37.010 8 22 GX2 CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=5552) 2016/09/08 08:37:37.010 8 22 GX2 CTcpProcessConnector::CloseConnection(): PID=5552 2016/09/08 08:37:37.010 8 22 GX2! InterProcessBase::EventFunctionInternal(): IPC-Connection Closed 2016/09/08 08:37:37.010 8 22 GX2 CTcpProcessConnector::CloseConnection(): PID=5552 2016/09/08 08:37:37.010 8 22 GX2 CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 10058: Unknown error 2016/09/08 08:37:37.010 5552 4147260224 S CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=32511) 2016/09/08 08:37:37.010 5552 4147260224 S CTcpProcessConnector::CloseConnection(): PID=32511 2016/09/08 08:37:37.010 5552 4147260224 S CInterProcessNetwork::NewInterProcessDataAvailable(): ConnectionClosed session=2 ptype=2 2016/09/08 08:37:37.010 5552 4147260224 S UpdateOnlineState m_ManualStop 2016/09/08 08:37:37.010 5552 4147260224 S CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 107: Transport endpoint is not connected 2016/09/08 08:37:37.011 8 22 GX2!! CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 10009: Unknown error, Errorcode=317 2016/09/08 08:37:37.012 8 9 GX2 interprocessbase::SecureNetwork destroyed 2016/09/08 08:37:37.013 8 9 GX2 TVW Terminating GUI slave 2016/09/08 08:37:37.013 8 9 GX2 Wine: Wine DLL freed 2016/09/08 08:37:37.015 32646 4113962752 QX2 TVGuiDelegate: Terminated

I'm having second thoughts about uninstalling previous version of TeamViewer. Now I have version 11 installed. I upgraded from version 10 by directly exexuting the version 11 installer. As you can see, in the Linux Mint 17.3 menu, there are 2 icons, both of which launch the same version of the program (11). I want to remove version 10. The problem is, as I said both of these icons run the same version of the program, I don't want to uninstall the latest version. How do I know, if those icons now launch the same version of the program, when I click on Uninstall on TeamViewer 10, it will NOT uninstall the latest version?

I can't connect via teamviewer on my remote linux machine when the monitor is disconnected. Teamviewer makes the connection to the remote machine but I'm always landing on the display management interface of linux but it doesn't show me a way to enter user name and password. I have described the whole issue/process along with the remote machine's hardware on the following forum .

Until now I used zerotier in order to reach a remote linux debian 9 machine that is a sort of vpn service, it assign you virtual router and you can add machines to it. Something got really strange since last update of the remote client. The machine is unreacheable, I have a person there with root access that can write a small list of command but he isn't very practical so keeping the list short is better. What list of command can I send to him in order to get a 100% sure functioning teamviewer installation so that I can get back and login in this machine ? The machine is a full classic Debian 9 installation with NO X or anything, only CLI classic terminal. I've read various teamviewer installation threads but every one seems to be very technical for linux, while I need something easy and unattended where the person have to do a command once, tell me his id and let me enter to fix all the mess zerotier last update leaved. BONUS: The command list can be also put online so he have to write a single line like a command runurl http:// some_pastebin_address ? Thanks!

I'm trying to make my Raspberry pi 4 free from my hand in any situations. If something happens I could work remotely from my pc. To do so I choose teamviewer for it. But device could reboot occasionally and even in that I should be able to connect to it if something needs to be done. If the OS in Raspberry pi is window(i don't know if it's possible...) it would be easy because in window an option in teamviewer that make teamviewer start with the system(which means start on boot) worked fine. But in Raspberry pi linux... Here's the problem. I've turned on the option 'start teamviewer with system' and put this command /usr/bin/nohup /usr/bin/teamviewer & > /home/pi/log2.txt in rc.local file. But noting happens... When I reboot the Raspberry pi, teamviewer does not start on boot so I cannot connect to the device without turning teamviewer manually. Linux version of Raspberry pi is "Raspbian GNU/Linux 10 (buster)". Plus I trying to connect to teamviewer with 'ID and personal pwd' way. TeamViewer on PC I'm trying to connect is logged in but teamviewer on the device won't. Nothing prints out in log2.txt...

Recently I noticed that the teamviewer and virtualbox do not start on my ubuntu 20.04.
I try to start teamviewer by typing teamviewer on my console Init... CheckCPU: SSE2 support: yes Checking setup... Launching TeamViewer ... Launching TeamViewer GUI . But nothing launched. And for Virtualbox I type $ VBoxManage startvm "win10" --type headless Waiting for VM "win10" to power on... VM "win10" has been successfully started. The vm starts but i don't see the Windows screen although I can ping this win10.

I seemed to install it successfully, but when I attempted to launch it kept throwing errors: Ran with su then got this: Init... CheckCPU: SSE2 support: yes XRandRWait: No value set. Using default. XRandRWait: Started by user. Checking setup... Launching TeamViewer ... Starting network process (no daemon) terminate called without an active exception /opt/teamviewer/tv_bin/script/tvw_exec: line 40: 4093 Aborted "$TV_BIN_DIR/teamviewerd" -n -f Network process already started (or error) Launching TeamViewer GUI ... A box popped up after a minute saying: > The TeamViewer daemon is not running! Please start the daemon (needs root permissions) before running TeamViewer. teamviewer --daemon start If you did not disable the daemon, please contact Teamviewer support Run the following Command to obtain all log files teamviewer --ziplog I did that and have a zip file that I don't know what to do with.. Also, the support claims they can't help me without a license... What can I do about this? I'm on linux mint 18.1 Serena Cinnamon 64-bit If you want the zip file, let me know. EDIT1: Also, for some reason, it tried to launch again 20 hours after I'd left it alone... it was confusing and a little alarming... I did get it from the official website so...

I am on Linux Mint 19.3 and would like to make the TeamViewer systemd service only run when I launch the GUI app (/opt/teamviewer/tv_bin/script/teamviewer). On Windows, this is fairly easy to do from the Services dialog by selecting the TeamViewer and changing its "Startup Type" from "Automatic" to "Manual". In Linux, I have TeamViewer 15 (installed via deb file from official site). I am seeing that the systemd service file has: $ cat /etc/systemd/system/teamviewerd.service [Unit] Description = TeamViewer remote control daemon After = network.target network-online.target dbus.service Wants = network-online.target Requires = dbus.service [Service] Type = forking PIDFile = /var/run/teamviewerd.pid ExecStart = /opt/teamviewer/tv_bin/teamviewerd -d Restart = on-abort StartLimitInterval = 60 StartLimitBurst = 10 [Install] WantedBy = multi-user.target and the service autostarts during login which I don't want. I don't mind hacking out a new bash script to start the service just before launching the gui but I'm not great with editing systemd services and had a concern about new versions overwriting my changes. ### Questions: 1. I could probably just remove the service file and use a bash wrapper script just before/after the gui process starts/ends vs just launching its 'ExecStart' args directly. *BUT*... seems like this could be bad if the gui process were to interface with the service process using systemd calls... If I were going to keep the systemd service file around for better compat, is there a way to configure the service file to still have the service enabled but NOT to run on startup but still allow it to be manually controlled via sudo systemctl [start|stop] teamviewerd ? 2. Is there a way in apt to specify a post-install script for a particular package. (e.g. when apt etc installs a new version of teamviewer which presumably reinstalls the systemd service and *.desktop files, I would like to have it automatically run a script to "fix" those things). I saw [this](https://www.cyberciti.biz/faq/debian-ubuntu-linux-hook-a-script-command-to-apt-get-upgrade-command/) and [this](https://askubuntu.com/questions/869219/how-can-i-run-a-script-after-a-specific-package-is-upgraded) and get that I would need something like /etc/apt/apt.conf.d/custom-hooks with a path to a script but not seeing how to: a) pass a list of last installed packages or b) find out which packages were just installed by apt. Is there a more elegant way to do things than capturing a list in the PRE hook and then recapturing and checking for changes in the POST hook? 3. Is there a more elegant approach that I have not considered?

In my workspace, citrix nsg is applied. Given that they don't have a rpm of nsg client, I can't use it from my fedora. As an alternative, they have provided me a desktop with teamviewer. Problem is, now I can use the desktop from my local machine using temaviewer,ssh fails to connect fk desktop's network. I am confused how is this possible? If there is no ip, what teamviewer connected?

I have a pi and a pc, both connected to the Internet but not visible to it. Normally I would use TeamViewer to connect both and use the vpn feature to get a Bridge. Now my Problem is that Raspbian teamviewer don't has the vpn feature. I found many other vpn's with this feature but the Problem is that I don't want to be visible to the Internet and because of that cant directly connect to a IP address. Also the IP addresses are changing so the Connection over a Code via TeamViewer was perfect. I there any other vpn service that does this kind of vpn that TeamViewer has? (Like from)

I have an Red Hat Enterprise Linux 8.2 as vm guest OS in Hyper-V. And I have installed the TeamViewer 15.5.3. But when I run the update command below: yum update --nobest --skip-broken I got such error:

[root@rhel8-1 admin]# yum update --nobest --skip-broken
Updating Subscription Management repositories.
gitlab_gitlab-ee                                                                              134  B/s | 862  B     00:06    
TeamViewer Internal (Dev Nightly Packages) - x86_64                                           0.0  B/s |   0  B     00:16    
Errors during downloading metadata for repository 'tvinternal_dev':
  - Curl error (6): Couldn't resolve host name for http://lnxrelease-02/yum/stable/main/binary-x86_64/repodata/repomd.xml  [Could not resolve host: lnxrelease-02]
Error: Failed to download metadata for repo 'tvinternal_dev': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

It looks like the team-viewer set the wrong repository release url http://lnxrelease-02/yum/stable/main/binary-x86_64/repodata/repomd.xml in the interal_dev version. And I have no idea the correct one. So I tried to disable the repository tvinternal_dev via the command: sudo subscription-manager repos --disable 'tvinternal_dev' It says: Error: 'tvinternal_dev' does not match a valid repository ID. Use "subscription-manager repos --list" to see valid repositories. After I run the command subscription-manager repos --list as suggested, I cannot see the repository tvinternal_dev. What should I do to skip/disable the repository tvinternal_dev to continue the updating process? Otherwise, do I have chance to correct the release URl of TeamViewer such kind of inreral_dev repository? I am new to the Linux and any suggestion will be graceful. Thanks in advance for any help.

I Have tried to install Teamviewer 10 on kubuntu. It's showing me below error: root@ubuntu:~# apt-get install teamviewer_linux.deb Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package teamviewer_linux.deb E: Couldn't find any package by glob 'teamviewer_linux.deb' E: Couldn't find any package by regex 'teamviewer_linux.deb'

I am having this weird issue where I can't make TeamViewer to work meaning I am getting this error (check image below) and therefore I can't connect to any remote PC: > TeamViewer not ready. Please check your connection At office others developers using Ubuntu and Windows 7/10 are able to use TeamViewer without problems so I am not sure what the problem is. I have checked the firewall status and isn't running: $ service firewalld status Redirecting to /bin/systemctl status firewalld.service ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:firewalld(1) I have checked SELinux status and it's disabled: $ getenforce Disabled I have Internet connection since I am opening this post from the PC where the problem with Teamviewer is happening. Maybe is something related to this other issue I am having but I can't be sure at all. I have checked some docs on Internet like this one but that's not my problem so ... any help? > Note: If you need anything from my side (debug info) let me know and > I'll add as part of the OP. Also I am not sure if this post should be > on this community but I believe the problem is coming from my Linux > and not from Teamviewer itself. **Update**: After follow the suggestion from @phg I am still researching the issue and I have found this . Apparently is an issue with Wayland and it's not fixed yet and it happen only on Fedora 25. We need to wait on a fix from Teamviewer team. **Update 1 (01/27/2017)**: There is a workaround where you can use the tarball non supported file and it works, I've already test it but this approach has a problem since Teamviewer doesn't run as a service and therefore you can't add the PC where it's running to your "computers & contacts" (very useful). Maybe there is a way to make the executable to run as a service but I didn't try this part, if anyone could try and leave an answer around will be good for newcomers.

What I need to achieve is this: 1. Run Teamviewer host on Ubuntu headless server CLI 2. Increase the resolution to something workable 3. Open a browser on the server through TV without installing a complete desktop enviroment. 1) I got working but the problem is the resolution is only 640x480 when no monitor is connected. 2) I got working as well (when connected to a monitor) but it breaks Teamviewer. To increase the resolution I tried things such as adding a line to Grub or install the dummby xorg driver and use a dummby config. This all breaks Teamviewer. Basically on a out of the box 18.04 server install as soon as you install something like xinit or whatever Teamviewer will just not work anymore. I think this is because after installing the above it is not detecting a monitor anymore because as soon as I connect a monitor I Teamviewer starts working again. Also all commands I can find such as xrandr always say unable to open monitor, even with a real monitor connected.

I'm using Adobe Connect 9.1 for the meetings and I often have to demonstrate something from my Linux Mint 17.2 machine. Unfortunately, Adobe Connect AddIn doesn't support screen sharing on Linux. It used to support in version 8, but for some reason they decided Linux users are not their target group. I would personally use some alternative such as Google hangout, but my company officially use Adobe connect for meetings, so I'm stuck with it. I'm wondering if there is any solution for this problem. I thought that it might be possible to have VirtualBox with Windows OS, and use it for screen sharing of the Linux host. However, it didn't work. Did anyone try something similar? For me, it would also work to use other Windows 7 laptop on the same LAN and access Linux through something like Team Viewer, so I can share screen in Adobe Connect. I know it is possible to share through the Google Hangout, but at some meetings I'm required to use Adobe Connect.

I need to have 2 different versions of teamviewer (version 8 and version 12) at the same time on a Ubuntu 16.04.2 LTS system. How do i install them both? What console commands do i have to use?

I am trying to run TeamViewer on Ubuntu Server 18.04 through Putty connection but I am getting following errors. I have already sudo installed Ubuntu Desktop on this server and I am hoping to create a remote connect to the GUI but I am stuck here a@gisdev05:~$ teamviewer mkdir: cannot create directory ‘/home/a/.local/share/teamviewer13’: Permission denied Error: Could not create /home/a/.local/share/teamviewer13/logfiles mkdir: cannot create directory ‘/home/a/.local/share/teamviewer13’: Permission denied Error: Could not create /home/a/.local/share/teamviewer13/logfiles Error: InitDirs failed. (2) a@gisdev05:~$ ^C I was however able to run the TeamViewer before running sudo apt-get install ubuntu-desktop Can you please let me know how to fix this?

I have installed Centos 7 minimal core on a machine and remoting to it with TeamViewer. Can anyone tell me why I can't type square bracket, pipeline and so on. I can only do it on the physical keyboard/computer I can do it on windows OS. I have a danish keyboard, I normally use alt + 8 to make brackets

This is a sudoers file which I have on a **Debian 9** server and it **works**. /etc/sudoers contains: Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # the following line I've added for sudo to work on Debian, which by default does not vlastimil ALL=(ALL:ALL) ALL # and this line I've added just now, so I could enable / disable teamviewer daemon as I wish vlastimil ALL = (root) NOPASSWD: /usr/bin/teamviewer # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d Meaning I can now run e.g. the following without entering password: sudo teamviewer daemon disable sudo teamviewer daemon enable This, however, is a **non-working** sudoers file on **Linux Mint 18** in a sense, it still asks me for password. /etc/sudoers contains: Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # this line I've added myself, because I felt it is needed, however user vlastimil has had sudo access all the time, added just now vlastimil ALL=(ALL:ALL) ALL # and this line I've added just now, so I could enable / disable teamviewer daemon as I wish, but it does not work vlastimil ALL = (root) NOPASSWD: /usr/bin/teamviewer # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d I guess there is some difference between Debian and Mint, which makes the added lines non-working. I read different answers like on this page: https://unix.stackexchange.com/questions/18830/how-to-run-a-specific-program-as-root-without-a-password-prompt But I am not clever from it. **EDIT1:** The first answer gives on Linux Mint a strange error: $ sudo /usr/bin/teamviewer Init... *** TeamViewer can not be executed with sudo! *** Either use your normal user account without sudo or use a the real root account to log in to your desktop (not recommended!). I don't get this either. ------------------------------------ $ which teamviewer /usr/bin/teamviewer $ file /usr/bin/teamviewer /usr/bin/teamviewer: symbolic link to /opt/teamviewer/tv_bin/script/teamviewer $ file /opt/teamviewer/tv_bin/script/teamviewer /opt/teamviewer/tv_bin/script/teamviewer: Bourne-Again shell script, ASCII text executable $ cat /opt/teamviewer/tv_bin/script/teamviewer #!/bin/bash # If you see this message, you probably attempted to start TeamViewer. # Please open a terminal (Konsole, gnome-terminal, xterm), # navigate to this folder (type 'cd /path/to/teamviewer' [Enter]) # then execute TeamViewer (type './teamviewer' [Enter]) TV_SCRIPT_DIR="$(dirname "$(readlink -e "$0")")" source "$TV_SCRIPT_DIR/tvw_main" Main "$@" **EDIT2:** For instance on AskUbuntu, as suggested in comments: Why is sudoers NOPASSWD option not working? and on many other places, there is a solution where they put the rule **after** admin group rule. I've tried it, even rebooted afterwards, but it's still not working.

As i need to install team viewer to my local pc which has ubuntu 16 in it .Can i get steps for how to install team viewer in ubuntu16 operating system . Thank you.