General :: Getting TeamViewer To Start Up 30/60 Seconds After Login?
Nov 14, 2010
configuring TeamViewer to start up 30 to 60 seconds after login.
At the moment, TV starts up straight away at login, but seeing as the wireless internet isn't connected straight away, TV's trying to connect without a connection, which is a problem when the wireless does connect as it will get stuck with 'Activating TeamViewer'.
Obviously, this is a straight forward task, just exit and then re-open TV. But seeing as I want to run a headless server, carrying my monitor and mouse to the server every time I want to activate TV isn't ideal.
The way I did set up TeamViewer to start up on login, was by dragging the icon into System>Preferences>Start-up Applications, so if the solution is to create a script of some sort.
I am overseas at the moment, and the wife has been having issues with my machine. After many hours of trying to to talk her through doing things, one of my geeks suggested installing Teamviewer and doing it myself.
I have SSH and WinSCP from work. I am using amd64 so the first attempt to install failed due to unmet dependencies. Then I read the MultiArch bit, installed ai32-libs and the install seemed to work. When my wife tried to start TV, it stated that the daemon was not running. When I try to restart the daemon, I get this.....
I recently powered up my netbook... Selected my user log in, entered my password, and after a couple seconds I briefly see what looks to be the console and am returned to the login splash screen... I can Ctrl+Alt+F2 to get to the console and log in... but that is as far as I can get. This is the case for Gnome, Remix, and Remix 2D.
I can sudo apt-get (update, upgrade, etc) as well. It is the right password because if I type in a wrong one it presents an authentication failure dialog box.
How can I fix my log in screen and get to my desktop? I am Currently running 10.04.... waiting to get 10.10
I have centos 5.3 i got the login screen but after logging shows error as-- your session only last less than 10 seconds . if you have not logged out yourself tyhis could mean that there is some installation problem or that you may out of disk space .try logging with one of fail session.
I have given support for my clients since 1985 and used "Remote Session", "Carbon Copy", "pcAnywhere", "TightVNC", and a few others. My choice of preference is to have a server I can trust under my supervision in order to avoid exposing my clients and friends private information from getting exposed? Using TeamViewer, an excellent product, does not secure both my files and theirs because when we connect, we are in their server and if they choose to, can interrupt, copy files, etc. during a remote session. Are there Linux versions for remote support available like TeamViewer that would be in my direct control?
I decided to install ubuntu again and downloaded 10.04. I had some issues installing with the desktop version, but everything installed fine with the alternate version.Now if I want to log in (on the KDE login-screen) the KDE-loading-symbols show up just as they are supposed to do, the desktop shows up (I can see "Desktop Folder and uBlog) and suddenly the mouse/system freezes. Neither Ctrl-Alt-Del isn't working nor Ctrl-Alt-F2 gives any response, all I can do is to reset my computer.
When I use Gnome as a desktop enviroment the computer totally freezes at the login-screen, without giving me any chance of logging in. Things I already tried: noapic, nomodeset, noacpi settings when booting, I successfully installed the latest ATI-Driver for my 3870, I disabled compiz.The kdm log says that there's some problem with an i-bus-daemon. Disabling/restarting the daemon has no effect on the behavior of my installation.
I am using GNOME. I notice that KOrganizer takes about 30 seconds to start. Once launched it is fine though. Is there a method to speed up it's startup?
As a side note, what is your favorite calendar in GNU/Linux?
Just installed Lucid Lynx on my Desktop and after logging in I would get a 15-20 second pause before Gnome appeared. I found many many potential solutions for this problem on the Internet but none solved it. Finally figured out that it was due to the system seeing a floppy controller when I have no floppy drive. I was led to this conclusion by the following two lines in my syslog (System > Administration > Log FIle Viewer > Syslog).
May 1 18:27:04 Desk-Ubuntu kernel: [ 34.636665] end_request: I/O error, dev fd0, sector 0 May 1 18:27:16 Desk-Ubuntu kernel: [ 46.813441] end_request: I/O error, dev fd0, sector 0
Note the 12 second delay when it tries to read again.
So if you are getting the pause and seeing the same thing your system log then ...
Enter your BIOS and disable the floppy drive Use sudo and edit /etc/fstab commenting out the line with fd0 in it
Hope I can save someone else the headache of hunting through the Interwebs and finding 5 different solutions none of which worked. Learning as I go with Ubuntu so I didn't even know how to carry out most of the "solutions" which required more googling. I am migrating from FreeBSD due to application requirements
When I log into my ubuntu 10.04 after booting my computer, I receive a 30-40 second lag before I can actually log in. During this lag, I can move the cursor and the login background is shown, but the computer seems to be doing nothing. It is as if there is a sleep command before I even log in. I am using a Sager 2096 computer but I got this computer for free and it did not come with the specs. I had installed a 64-bit version of Ubuntu because this computer has a 64-bit architecture. However, whenever I install software, it always has to install the x86 version because the x64 is "not supported." Perhaps I have a mix of 32 and 64 bit programs and that is what is screwing it up?
I am using Opera 10.60 browser for the past one month. Generally it use to take about 20 seconds to startup but since yesterday its taking more than 40. I don't know about the exact duration but certainly its taking a lot of time now.
Problem: Ubuntu freezes up 30 seconds or so after a successful login.
Background:I am running a Compaq Presario SR5030NX. It has had issues for a while with running Ubuntu properly. My computer suffers from this bug. I have managed to get the LiveCD running by adding the following to my boot parameters:
Code: vga=792 i915.modeset=0 When I was running the LiveCD I found that it would freeze after about 30 seconds. I solved this problem by again changing the boot options. This time I:Press F6 Check noapic, nolapic, and pci=noacpi
I then proceeded to install Ubuntu.
My problem arose when Ubuntu did not modify grub.cfg to match the setting I needed in order to boot. I managed to modify in some of the settings correctly, I believe at least, but not all of them.
In its current state Ubuntu is able to boot, but freezes 30 seconds or so after a successful login. If I do not graphically login, I do still have access to VTY1-6. The machine does not freeze until a successful graphical login has been made.
Below is the relevant section of my grub.cfg:
Code: menuentry "Ubuntu, Linux 2.6.31-14-generic" { recordfail=1 if [ -n ${have_grubenv} ]; then save_env recordfail; fi set quiet=1 insmod ext2 set root=(hd0,2) code....
On another note: The liveCD I have been running for 6 months is BackTrack 3 Final. Which does not have this issue at all. I would wager a guess that BackTrack 4 does though as it is based off Ubuntu instead of Slax.
I recently upgraded from Ubuntu 10.10 to 11.04. My hardware can't support fancy effects, so I'm using the "Classic (no effects)" desktop.When I logged in, all programs would be themed in one way, then 15 seconds later everything would change to a different theme. Neither of these themes was the theme that I had selected in the configuration. I came here to ask for advice, but discovered this first:http://www.romaco.ca/blog/2011/02/20...s-with-ubuntu/Summary:gnome-settings-daemon has a race condition that is triggered if it starts too fast.
Workaround: in /etc/xdg/autostart/gnome-settings-daemon.desktop
Well this problem has been here since Lucid. When I start up my computer and select Ubuntu, I get a blinking underscore for about most of the start up time for Ubuntu. Then It quickly shows the nice Ubuntu Loading Screen (Plymouth) for about two seconds, then it gets to the login screen. I am using the Open Source ATI drivers, I believe the open drivers are called "radeon".
Don't know what is going on here, but Evolution won't start. I've tried reinstalling. When I click the icon to open it, the little loading cursor displays for a few seconds then it disappears and nothing else happens.
I am using Kde 4.4 and I would like to start one of the applications automatically after every login to the system. How can I configure it? I remember I managed to find a dialog window in one of the previous versions, but I can't find it now.
I am using Fedora and trying to auto run a script soon after the unit boots to desktop. I found many suggestions and finally decided to use the Sessions->Startup Programs option (under System->Preferences->Personal->Sessions menu). I added my script in the Startup Programs with the command 'sh myscript.sh'. Now I have two questions here:1. When I use the command 'gnome-terminal -e myscript.sh', I get 'There was an error creating the child process for this terminal' message after logging into the desktop. Can any one tell if I am missing something here?2. Even if I use sh instead of gnome-terminal, I still want to see the script executing. In other words, my script has certain echo statements indicating the flow of the script. But I don't see any shell opening up with these echo statements showing up, after the unit boots to desktop. But the script was still executed with no problem
I recently aquired server with TWO hard drives.For reason unknown (hehe) i installed unbuntu server on both hard drives.This is causeing me some problems, and i would like to wipe everything and start over, would like to put unbuntu server on one hard drive and use the other for free space.P.S I have had Unbuntu server run succsessfully i am just unclear on how to clear a hard drive of any OS.Oh did i mention the first time i used linux was 3 days ago? Ye i am a newby (sigh)
This problem started within the last few minutes. I run a program in my browser that uploads data from my machine (ubuntu) to another machine (Fedora 13), for manipulation and then spits back the data that does not match our standardised information.
When I tried to run it a few minutes ago, it seemed to take a long time to make the connection. I went back and checked the machine, everything was connected and fine. I decided to reboot the machine from within KDE and then try again. Same result. I went to the machine again and tried to login through KDE, the screen goes black for a few seconds and then returns me to the login screen. I switched over to a virtual terminal and was able to login using the same credentials. I checked the .xsessions-errors file and this is what I am seeing:
I have installed redhat linux enterprise 5.Im unable to use teamviwer in it.Its showing successfully installed but unable to open....During the installtion I got the following message
"Unable to verify teamviewer6-6.0.9224-1.i386"
when I clicked on details I get this " "Package teamviewer_+linux.rpm is not signed"
I installed teamviewer recently. I can remotely access a windows system from my fedora machine. But i cannot access my fedora machine from the windows machine.
The windows machine is unable to connect to the fedora machine. Do I need to open some ports on fedora machine ?
It might be a totally different angle i should look at this, but here goes.I can start the linux variant of teamviewer by writing teamviewer in the terminal, on the box. Fine.I can start it via /opt/teamviewer/ teamviewer/5/bin/teamviewer.If i connect to the box via ssh and putty, i still can run those commands but nothing happens.My goal in this is to be able to start teamviewer remotely via putty.
I wish to start TeamViewer as a service in Ubuntu. In Windows I can load it as a service and remotely enter password at login screen. Is it possible with Ubuntu?
Problem: Whenever I try to use teamviewer it simply crashes. Weather I am trying to teamview someone or trying to get teamviewed, it crashes. I believe it is because of the ATI driver I installed. Before I had installed my ATI driver it wasnt crashing, ran perfectly fine. After installing though teamviewer would always crash. The same thing happened to my friend, and he has a completely different ATI card. Specs:
AMD Athlon 7550 x2 @ 2.6 Ghz ATI Radeon HD 2600xt (my friend has a 4850) 3 GB RAM
There is a very simple method to Run TeamViewer as a "root". This can be risky but if any users wants to running TeamViewer 5 and 6 As root then I have written a small article for the same. Requesting you to visit article and let me have some feedback or whatever comments you feel. read this article :- http://blog.ask4itsolutions.com/2011...tu-rhel-cento/ This practical performed on Red Hat Enterprise Linux 5.x, Ubuntu Desktop Edition, Fedora and CentOS
I installed teamviewer and immediately skype went offline. Upon logging in to skype I get the following error: "skype p2p connect failed" So I rebooted pc, router, performed the command: "rm -rf ~/.Skype" to no avail. Next I removed teamviewer and tried everything again & still the message persists. Skype was set to not use port 80 already, but if it won't log on then I can't get to full the options menu.
