TeamViewer packages for Puppy.....

[Mike Walsh]

Evening, everybody.

I thought I'd carry on with the good work I 'inherited' from cimarron... Accordingly, here's the most recent release of TeamViewer 12 (12.0.76279), which was released during the last week of March.....and if not for my recent bout of ill-health, would have undoubtedly been 'Puppyfied' somewhat sooner..!

Both .pet and SFS packages are available, from the same URL as in post #1. Seems that more Puppians than would care to admit it use this particular app, as evidenced by over 350 downloads since the previous 're-pack' back in December.....

Enjoy. Any probs, let me know, and we'll see if we can resolve 'em.


Mike.

[Mike Walsh]

Morning, everyone.

Not entirely sure how long this version's been out, but here's continuing with cimarron's good work:-

TeamViewer 12.0.85001

(EDIT:- Sept 18, apparently, so it's fairly recent.)

'Twould seem the GPU is now leveraged to help boost performance. I wouldn't quite like to say how this will affect some of the really old hardware running Pup; feedback from affected (or otherwise) 'Puppians' will be most useful, as per normal.

---------------------------------

Given that the Linux Teamviewer packages always come with a self-contained version of WINE 'built-in', the magic that enables all this to keep working (especially for those of us who, like myself, usually run WINE anyway) without conflicts between the different versions of WINE, is the /teamviewer script in /usr/bin. It utilises LD_PRELOAD to point TeamViewer in the direction of its own version, rather than attempting to 'mix'n'match' the two.....and at the same time, kills any other 'zombie' TV processes that might be interfering with things. Ultimately, cimarron and I both have CatDude to thank for this.....from a few years back.

It also explains why I could never get PhilB's TV10 and 11 pets to run.....because they simply linked to /teamviewer/tv_bin, without resolving this conflict. Anybody not running WINE, of course, wouldn't notice anything amiss.....

http://www.murga-linux.com/puppy/viewto ... 881#874881

---------------------------------

Pet & SFS packages are available from the usual location:-

https://www.mediafire.com/folder/dsso94 ... TeamViewer

As always, any probs, give me a shout. We'll try and see what's what.

Enjoy.


Mike.

[daviddem]

Hello,

I am on Slacko 6.3 and I would like to report success running your latest .pet package from the post above.

Unattended access, however, is not working ("Teamviewer needs to be installed first").

I found this and was wondering whether maybe you would be interested to make a .pet of it, for those of us who need unattended access?

[Mike Walsh]

Hallo, David.

I've looked at this before. The main reason I've never followed up on it is that TeamViewer Host requires the Qt5 package to work (this is what produces the GUI).....and the problem is that you have to install a package of nearly 300 MB in size (bigger than Puppy itself) in order to run a single, small 20 MB app.

Which rather defeats the purpose of Puppy, it being a small, lean, stripped-down OS.

On top of which, the TeamViewer Host package appears to make a lot of system-calls that simply don't translate easily into Pup's file-structure and layout.....and in addition to that, it refuses to run as /root.

And since there aren't too many Qt5 packages available for Pup (and my personal compiling skills are absolutely atrocious), this is why I've never taken it any further. Moreover, the newer Slackos seem to have plenty of problems running packages which are essentially set-up for the 'buntu-based/RedHat-based distros to run... Slackware packages tend to have rather unique requirements. Get the picture?


Mike.

[daviddem]

OK fair enough. I can actually let TV running permanently on the laptop, and the password won't change until I reboot the laptop or shut down TV. So I can still make your package work for my purposes.

Thank you for your work.

[Mike Walsh]

Hi, David.

That's pretty much what I do myself, on the odd occasions I want to use TV on my own system; leave the 'target' machine running, set-up ready to connect, then just make the connection remotely.

Works for my purposes.


Mike.

[vektor_alian]

Vic here ...

When I have a computer I want attached to my Teamviewer account I add it from one of my other computers already logged in. After that it auto logs in.

I hope that is what is wanted by the OP.

Vic

[Mike Walsh]

Just so y'all know, I'm retiring from the 'field of play' on this one.

From version 13 on, TeamViewer is becoming pretty much unworkable except for a very small handful of Puppies.

Reasons?

1.) It has, like so many apps, now gone 64-bit only.

2.) It requires the Qt5 packages. Qt5 is a monstrosity, requiring more space than Puppy itself does.....and, given the relatively small size of the app, this is an utterly ludicrous situation.

3.) In addition to that, it would require running as 'spot'; it refuses to run as /root any longer. More and more Linux apps/programs are going down this route; I believe that in a few years time, Puppy's 'root' model' is going to be all but unusable, and will require a serious re-think.

Puppy as we currently know it, won't be able to exist any longer, unless users wish to exist in a 'timewarp' bubble, disconnected from reality.

I don't know why they didn't just leave TeamViewer running from its own built-in version of WINE. Quite why you should need to have a rendering system bigger than the OS it runs on, to produce almost exactly the same GUI, beats me; but that's the devs for ya; full of bright ideas to make their lives easier.....and 'Sod' the poor old end-user.

So; if anybody else believes they can do summat with it; feel free. I know my limits..! Essentially, that leaves us with Remmina for remote desktop stuff.....and at the best of times that's something of a 'mixed bag'.

The existing packages will, of course, remain available. They work fine for our use-case; once again, it's a case of 'newer is not always better'.

It is, of course, highly likely that as in so many cases, there's only a small fraction of the Qt5 'modules'/libs actually needed for TeamViewer to work. With the current state of my personal life, I don't really have the sort of time I need to go through all this, step by laborious step, to discover which those might be.....


Mike.

[Max Headroom]

I've installed TeamViewer 13 on Xenialpup 7.5 32 bit, but it won't run because of missing dependencies, Specifically, qtbase-abi-5-5-1 & qtdeclarative-abi-5-5-0 after Hunting down many others! But Testing is supposed 2 Start in little more than 7 hours, so I'm in a bit of a Desperate Panic! This is supposed 2 be 4 a Community Wireless Trust 2 Remotely Monitor the Network. Your Help Will be Greatly Appreciated, Thanx! ;-)K

[mikeslr]

qtbase-abi-5-5-1 @ https://pkgs.org/download/qtbase-abi-5-5-1

qtdeclarative-abi-5-5-0 @ https://pkgs.org/download/qtdeclarative-abi-5-5-0, or at least that's what the search box at pkgs.org reports.

[Mike Walsh]

@ Max Headroom:-

Personally, unless you have a really pressing need for it to be TeamViewer and nothing else will do, IMHO the best app for this job is now Smokey01's 'Back Seat Driver'. Much, much smaller.....and just as effective. Especially since you can now tie it in with Puppy's built-in VOIP 'softphone', PSIP.

I was helping to test the earlier versions, and was chatting to Smokey some 11,000 miles away, at the same time as controlling each other's desktops remotely. It works brilliantly. Live messaging and file transfers are also available.

You can read about it in the January edition of the Puppy Newsletter, here:-

http://smokey01.com/newsletters/2019/Ja ... 19.html#14

I've already run up some packages for this, but will not be releasing them until FatDog 64 800 officially goes to full, stable release. This is Smokey's 'baby' (and a few other contributers), and I'll not steal his thunder, since it will be built-in to FatDog 800.

---------------------------------------

I haven't even bothered to try and get versions 13 and 14 of TeamViewer working, since they now require (as you've found out), Qt5. Qt5 and me do not get on very well. I've yet to get a Qt5-based app of any kind actually working.....

Just be patient, until I release the BackSeatDriver packages. It'll be well worth the wait, trust me.


Mike.

[Max Headroom]

Thanx Mike 4 your Timely Reply, However I had already been 2 those sites & DownLoaded those Files, But they don't work! Wot Next, Please? ;-\K

[Max Headroom]

@ Mike, I just noticed your other post as I sent my previous 1... the Reason 4 Using TeamViewer is that the person Monitoring the CWT Network is most Familiar w/ Teamviewer also it's not intended 2 be used 4 Video Conferencing in this instance ( in Fact there won't be anyone eLse @ the Remote Location 2 have a session w/ )

;-\K

[Mike Walsh]

@ Max:-

In that case, just use the TV12 package at both ends (12.0.85001). It won't hurt being an older version, so long as it's the same package at both ends; TeamViewer gets really stroppy if you try to run a newer version from an older one, or vice versa!


Mike.

[Max Headroom]

Thanx Mike, that's wot I did & it Works, there was a warning about Deprecation or sumthing.

The Person that I Built the TeamViewer PC 4 is Really impressed w/ its Speed & How it Revived otherwize useless computers in2 sumthing Useful!

;-)K

[gjuhasz]

In that case, just use the TV12 package at both ends (12.0.85001). It won't hurt being an older version, so long as it's the same package at both ends; TeamViewer gets really stroppy if you try to run a newer version from an older one, or vice versa!

Hi,

I also prefer TV 12.0.85001. However, due to some compatibility issues with old Androids, I use TeamViewer 10.0.93450 on the server side and different TeamViewer clients v10, 12, and 13 without any hiccup. Remote sounds are played, too.

Server is installed on Win10, clients run on Android 2.34 ... 9 and on Puli 32/64 bit versions.

I have played with the TeamViewer plugin for Chromium based browsers as well (especially, on Iron). Runs fine.

Have fun!
Regards,

gjuhasz

[Mike Walsh]

Evening, all.

Following the discovery of Fredx181's thread about some scripts he's put together that allow you to build your own AppImages (I like AppImages..!), here's the last Wine-based version of TeamViewer, 12.0.85001, re-packaged as an AppImage.

Just download, put it anywhere you want, and click on it to run.....

https://drive.google.com/file/d/1V0uyGO ... sp=sharing

Enjoy.


Mike.

[rockedge]

Hi Mike, I am getting these errrors with teamviewer app you've put together

Code: Select all

./usr/bin/teamviewer: line 4: cd: /opt/teamviewer: No such file or directory
./usr/bin/teamviewer: line 5: ./teamviewer: No such file or directory
/tmp/.mount_TeamVi9avoch/AppRun: line 20: 25937 Killed                  $EXEC "$@"
Checking teamviewer for missing libraries.
Adding these depencencies will probably fix if the program doesn't run

[Mike Walsh]

@ rockedge:-

Huh. I think I was a wee bit premature rushing this out..!

See Fred's post in the other thread, and my response immediately below....


Mike.

[jp734]

Hello all - Just checking if anybody have tried installing TV14. Been searching the forum but could not find anything. I installed TV14 on my pc and all its dependencies (what were listed on TV14 "control" file). So far, the best I get is a TV window come up for a couple of seconds before it crashes. Executing TV in terminal gives me:

Checking setup...
Launching TeamViewer...
Launching TeamViewer GUI ...
Aborted

Below is the log file. It says something about DBusServices failing (I have libqt5dbus5 installed). Just want to try if anyone have any suggestion before I try Remmina. That is if you can use Remmina to connect to TeamViewer users. Thanks in advance.

2019/05/03 19:09:18.566 32390 139857498938752 GX0 Logger started.
2019/05/03 19:09:18.567 32390 139857498938752 GX0 Found 6 stack dump files ...
2019/05/03 19:09:18.569 32390 139857498938752 GX0 Found 6 core dump files ...
2019/05/03 19:09:18.571 32390 139857498938752 GX0 Shutting down System DBus
2019/05/03 19:09:18.571 32390 139857498938752 GX0 SysSessionInfoManager: observing sessions from logind is marked as unreliable
2019/05/03 19:09:18.572 32390 139857498938752 GX0 Shutting down System DBus
2019/05/03 19:09:18.573 32390 139857498938752 GX0 SysSessionInfoManager: Session Information provided by VT [priority: 2]
2019/05/03 19:09:18.573 32390 139857498938752 GX0 XSocket observer: watching /tmp/.X11-unix
2019/05/03 19:09:18.597 32390 139857498938752 GX0 XSocketEnumerator: adding XSession '2288559862' for display 0
2019/05/03 19:09:18.598 32390 139857498938752 GX0 SysSessionInfoManager: assigned session 2288559862 to info provider 'VT'
2019/05/03 19:09:18.599 32390 139857498938752 GX0 SysSessionInfoManager: own session cache set to '2288559862'
2019/05/03 19:09:18.605 32390 139857498938752 GX0 Running on Qt 5.7.1
2019/05/03 19:09:18.635 32390 139857498938752 GX0 Initialised XRandR extension 1.5 (base=89 error=147)
2019/05/03 19:09:18.752 32390 139857498938752 GX0 MonitorInfo: [XRandR 1.2] CRTC VGA1 1920x1080@60Hz [0, 0, 1920, 1080] - 1
2019/05/03 19:09:18.753 32390 139857498938752 GX0 MonitorInfo: [XRandR 1.2] CRTC HDMI1 1920x1080@60Hz [1920, 0, 3840, 1080] - 1
2019/05/03 19:09:18.753 32390 139857498938752 GX0 MonitorInfo: [XRandR 1.2] CRTC 2 has no outputs
2019/05/03 19:09:18.753 32390 139857498938752 GX0 Virtual Desktop [0, 0, 3840, 1080]
2019/05/03 19:09:18.753 32390 139857498938752 GX0 MonitorInfo: [XRandR 1.2] CRTC VGA1 1920x1080@60Hz [0, 0, 1920, 1080] - 1
2019/05/03 19:09:18.753 32390 139857498938752 GX0 MonitorInfo: [XRandR 1.2] CRTC HDMI1 1920x1080@60Hz [1920, 0, 3840, 1080] - 1
2019/05/03 19:09:18.753 32390 139857498938752 GX0 MonitorInfo: [XRandR 1.2] CRTC 2 has no outputs
2019/05/03 19:09:18.753 32390 139857498938752 GX0 Virtual Desktop [0, 0, 3840, 1080]
2019/05/03 19:09:18.764 32390 139857498938752 GX0! DBusServices: could not register application. Connected: 0
2019/05/03 19:09:18.773 32390 139857498938752 GX0!! ResourceLoader: loaded file '/opt/teamviewer/tv_bin/resources/TVResource_en.so' version (8352) is not matching with application version (14.2.8352), Errorcode=10
2019/05/03 19:09:18.773 32390 139857498938752 GX0 Loaded language 'en', using locale 'en'
2019/05/03 19:09:18.773 32390 139857498938752 GX0 InterProcessBase::SecureNetwork created
2019/05/03 19:09:18.774 32390 139857498938752 GX0 AutoLogin::Login: enabled: 1
2019/05/03 19:09:18.774 32390 139857498938752 GX0 AccountLoginStateMachine::Reset
2019/05/03 19:09:18.774 32390 139857498938752 GX0!! ApplicationLookOfflineState::ApplicationAppearanceOfflineState: state not loaded, Errorcode=10
2019/05/03 19:09:18.775 32390 139856660973312 GX0 InterProcessBase::StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector
2019/05/03 19:09:18.775 32390 139856660973312 GX0 Opening local TCP connection to 127.0.0.1:7341, tcp?
2019/05/03 19:09:18.775 32390 139857206032128 GX0 Local TCP connection established
2019/05/03 19:09:18.861 32390 139857206032128 GX0 SettingsIPCReception receive a SYNCHRONISE Settings command : UserSettings
2019/05/03 19:09:18.861 32390 139857214424832 GX0 Received Control_InitIPC_Response processtype=1
2019/05/03 19:09:18.861 32390 139857214424832 GX0 Received Control_InitIPC_Response runningProcesses=3
2019/05/03 19:09:18.861 32390 139857214424832 GX0 Control_InitIPC_Response: all processes 3 completely initialized



Start: 2019/05/03 19:09:18.862 (UTC+8:00)
Version: 14.2.8352
ID: 0
Loglevel: Info (100)
License: 10000
Server: master13.teamviewer.com
IC: -325157759
CPU: Intel(R) Celeron(R) CPU G470 @ 2.00GHz
CPU extensions: y8
OS: Lx xenialpup64 7.5 (x86_64)
IP: xxx.xxx.xxx.xxx
Proxy-Settings: Type=0 IP= User=

2019/05/03 19:09:18.864 32390 139857498938752 GX0 SystemID m=2 s=1 b03001c7e8fca13d3e8d09d25ccc0e07
2019/05/03 19:09:18.866 32390 139857498938752 GX0 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2019/05/03 19:09:18.866 32390 139857498938752 GX0 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2019/05/03 19:09:18.866 32390 139857498938752 GX0 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2019/05/03 19:09:19.774 32390 139857498938752 GX0! DBusServices: RegisterApplicationObject failed.
2019/05/03 19:09:19.775 32390 139857498938752 GX0!! ApplicationLookOfflineState::ApplicationAppearanceOfflineState: state not loaded, Errorcode=11
2019/05/03 19:09:19.775 32390 139857498938752 GX0 ManagerHolderStateMachine: Switching from None to NotReady
2019/05/03 19:09:19.775 32390 139857214424832 GX0 ChatManager::ChatManager: created
2019/05/03 19:09:19.775 32390 139857214424832 GX0 ChatManager::Factory: ChatManager created
2019/05/03 19:09:19.775 32390 139857214424832 GX0 IncomingBetterChatCommandHandler::IncomingBetterChatCommandHandler: created
2019/05/03 19:09:19.775 32390 139857214424832 GX0 IncomingCommandRegistration::Start: registering for ready state properties
2019/05/03 19:09:19.776 32390 139857498938752 GX0 Initialised XFixes extension (base=87 error=140)
2019/05/03 19:09:19.793 32390 139857498938752 GX0!!!Crash: stack dump has been written at '/opt/teamviewer/logfiles/TeamViewer_FI_14.2.8352_2019-05-03-190919.amd64.stack', Errorcode=22
2019/05/03 19:09:21.863 32390 139857498938752 GX0!!!Crash: Coredump '/opt/teamviewer/logfiles/TeamViewer_FI_14.2.8352_2019-05-03-190919.amd64.core' could not been written. Error 14, Errorcode=14
2019/05/03 19:09:21.863 32390 139857498938752 GX0 Process received fatal SIGABRT