Teamviewer GUI not starting in Slackware 15.0 with slim
 

Hello everyone,

I have convinced my parents to try using Slackware Linux instead of Windows. As part of this, they have asked me to make sure that I can remotely connect and help them when needed.

I wanted to use x2go but unfortunately their ISP does not allow direct outside connections so I am stuck using TeamViewer. I have run into a problem: TeamViewer GUI refuses to start under Slackware 15. I've done the usual Web and forum searching to discover that TeamViewer evidently needs a graphical display manager to work. Unfortunately, that doesn't seem to solve this issue.

What I have done on the test computer:

• Set initlevel to 4
• Installed slim
• Installed TeamViewer via SlackBuilds
• Set rc.teamviewer to +x
• Started the TV daemon
• Made sure the daemon was running before attempting to use the GUI

This is what I get when trying to run the Teamviewer GUI:

Nothing in any of the TeamViewer logs is helpful.

I'm at a loss right now but I'm considering trying gdm as the SlackBuilds build of gdm does have PAM support and maybe that's what TV is expecting.

Any thoughts or suggestions are appreciated!

Did you install Gnome via Slackbuilds.org?? Just asking because you are referring to gdm.

For this purpose, I'd hope that you're using 15.0 stable and not current. And preferably a full installation of it, complete with KDE.
There is a SlackBuild for TeamViewer. Are you using it? https://slackbuilds.org/repository/1...rch=TeamViewer

Another option is Google: https://remotedesktop.google.com/

The only other advice I'd offer is this: Don't switch people away from something they're comfortable with, even if (as in this case) the solution you're proposing is significantly better. You're creating a rod for your own back. They will call you with an urgent problem at a time when it is least convenient for you. Your dinners will go cold, you will miss story time with your kids, you won't have time for breakfast, you won't see the excellent shot your kid makes at Saturday morning sport, your phone will ring during job interviews or critically important business meetings or even while you're in the bathroom.

But, don't let me put you off... ;)

Slackware comes with the 'sddm' and 'xdm' login managers in a default install. I'd recommend trying one of those first before trying to add on 'gdm' since they are ready to go "out of the box" and have working PAM configs already installed. The gdm PAM config is based off of the sddm config also, so testing sddm would suffice.

For the record: I did a quick build of the 'slim' package to look at what it installs and can tell you that out of the box, it's PAM configuration is incorrect and will not work:
Slackware doesn't include a 'system-local-login' config, and there's no usage of elogind for session management. My guess is this is some boilerplate setup for Arch linux or something. Maybe there's some better build options, or a custom config has to be supplied, tailored for Slackware. xdm or sddm could be used as a reference to make a config that works for slim most likely, but I dont use the software myself.

In Slackware, TeamViewer works in KDE started with KDM. It's a mystery to me, what's missing otherwise.

No, I have now. I'm using XFCE.

I spent 35 years in IT as a system and a network administrator and was on call 24/7/365 for most of my adult life. I am medically retired and divorced, live alone, and have long been my parents' IT guy, so none of the above shocks me anymore. :)

My father is a victim of a car accident that caused severe traumatic brain injury 22 years ago and he has struggled to use a computer after that. I'm used to getting phone calls and texts at random times for computer issues. I consider that part of my duties as the oldest and only son (not to mention the only nerd in the family).

Thank you. I will take your advice and test 'sddm' this week and report back. I gave up on 'gdm' because of the absolute enormity of dependencies it has.

I use on some machines gdm 2.0 which I have here : https://github.com/BrunoLafleur/pbsl...builds/sbo/gdm

It depends only on libgnomecanvas :
https://github.com/BrunoLafleur/pbsl...libgnomecanvas

The both are for Slackware 15.0 and uses PAM, but as said above xdm and sddm also use PAM.

But as said above by 0XBF, a better config slim.pam for PAM like the one for SDDM maybe a good start point.

Also is the teamviewer.rc started successfully ? Try as root : cd /etc/rc.d;./teamviewer.rc stop then ./teamviewer.rc start and see if there are some messages.

I'm using sddm display manager with dwm as graphical environment. I used to let slackware init level set to 3, but due to this TeamViewer requirement I switched it to init 4 (graphical log in with sddm). TV package installed via SBo slackbuild.

PS.
Now I'm facing with an other issue about TeamViewer, it disconnects my remote session after 5 minutes. This morning is first time I noticed this new "Team Viewer policy".

As regards alternatives, any other suggestion a part of google remote desktop?
I have to connect from Slackware to a remote PC on which is running Win7, its IP should be public and dynamic. I need graphical desktop shown.

dwm is from SBo. It adds complexity to the problem with PAM for example. SDDM, KDM, XDM and GDM are known for having good configs for PAM. Other display manager are less well known.

Also you don't say if you change the PAM config for slim and if you try above suggestion for teamviewer.rc

I'm not the OP, my report was just to add my config.

Team Viewer needs init4 and a display managar like SDDM, or XDM or some other you mentioned. It's a known issue introduced qith last Team Viewr versions. I found many complains on the net by many "init3" users yet years ago.

I can confirm Team Viewer works properly with dwm, but dwm isn't a display manger, it doesn't manage login or similar stuff... it's just a window manager. A graphical display manager is needed. I'd suggest to try sddm just preinstalled in slackware.


My other request looking for alternatives to Team Viewer is not related to the OP user question. My question is due to new team viewer session time limitations and isn't related to any slackware software config like PAM or similar.

If you have a static IP at one end, and control the router at that end, then OpenVPN is not a bad choice.

There's 37 packages to build and install to get to gdm last I checked ;). You basically have to build the core gnome desktop minus the applications to use gdm, so if you're not after the whole desktop there are better options.

'sddm' is probably the easiest to test and more user friendly, although xdm is simpler overall. Based on what other users have said here it sounds like either should fix your TeamViewer problem. If not we can try to go from there.

The remote IP isn't static, and target PC is behind a LAN with a router provided by the ISP. Maybe I can try to change settings within the router, if I well remember it was preset by the ISP but it was installed by me years ago, there must be also its password written on paper somewhere within a desk... Anyway I prefer to leave it as is, because it manage some other devices and a wifi network for few other offices.

Perhaps openvpn could be used also in this situation, but I should subscribe some domain service like dynDNS or similar to reach at least the remote router. After that I don't know how to enter through the router and reach my PC without any port forwarding setting.
For this reason I'd prefer a solution like TeamViewer, I don't have to connect often to that PC, just few times in a month, but this new session-time limitation doesn't allow even any minimal stuff.