TV 14 "Not ready..." on Manjaro KDE
jackdinn
Posts: 23
in Linux only
I have tried just about everything suggested in all the threads on this forum, still can not get it to work.
❰greg❙~❱✔≻ sudo systemctl status teamviewerd
● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2019-10-25 22:03:32 BST; 43s ago
Process: 30817 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
Main PID: 30819 (teamviewerd)
Tasks: 16 (limit: 4915)
Memory: 4.3M
CGroup: /system.slice/teamviewerd.service
└─30819 /opt/teamviewer/tv_bin/teamviewerd -d
Oct 25 22:03:31 greg-pc systemd[1]: Starting TeamViewer remote control daemon...
Oct 25 22:03:32 greg-pc systemd[1]: Started TeamViewer remote control daemon.
❰greg❙~❱✔≻ /opt/teamviewer/tv_bin/script/teamviewer
Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
❰greg❙~❱✔≻
I have rebooted,
Tried wired connection &/or wifi,
Tried open DNS,
It's not the firewall (switched off while testing this),
started the service,
stopped and re-started the service,
re-installed teamviewer,
re-boot system some more just for fun...
Im open to any suggestions as i need to assist my dad get his printer installed but im as stuck on this as he is on that.
Im on Manjaro KDE, All up to date.
Host: greg-pc Kernel: 5.3.6-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0 Desktop: KDE Plasma 5.16.5 Distro: Manjaro Linux
Tagged:
0
Comments
hi,
i've install a Manjaro with KDE in a VM; installed Teamviewer 14 ( tar dist.);
it works ( incoming and outgoing connecttion) fine from the first attempt.
you description is a bit confusing to me. I assume, that you want to do an outgoing connection from your Manjaro box to your dads ( windows? ) PC. right?
did you check the TV log files in the directory logfiles ?
Hi, Yes you assume correctly, I am trying to connect from my linux to a windows client to offer support.
My log file:-
Hi, I did already respond to this but the forum has removed my post , so im posting again so sorry if this is a duplicate ,god dam it.
Yes you are correct, i am trying to connect from my linux system to a windows client to offer support.
My log:-
Hi, sorry but the forum will not allow me to post any response. I keep trying to post my log files but the forum just keeps deleting my posts.
I would try pastebin or something but i suspect it would see me posting a link as "spam" to and remove that post to.
I shall keep trying to post my logs
attempt number 6 to post some logs. (i shall just paste them as plain text this time).
Start: 2019/10/27 11:03:07.095 (UTC+0:00)
Version: 14.6.2452
ID: 0
Loglevel: Info (100)
License: 0
Server: master13.teamviewer.com
IC: -**Please do not post TeamViewer IDs**
CPU: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
CPU extensions: l9
OS: Lx Manjaro Linux (x86_64)
IP: 192.168.2.106
Proxy-Settings: Type=0 IP= User=
2019/10/27 11:03:07.103 26935 **Please do not post TeamViewer IDs**81472 GX0 SystemID m=1 s=1 f48ad995d1d94f05a2259fdf8e02a280
2019/10/27 11:03:07.104 26935 **Please do not post TeamViewer IDs**81472 GX0 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2019/10/27 11:03:07.104 26935 **Please do not post TeamViewer IDs**81472 GX0 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2019/10/27 11:03:07.104 26935 **Please do not post TeamViewer IDs**81472 GX0 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2019/10/27 11:03:07.420 26935 **Please do not post TeamViewer IDs**81472 GX0!! ApplicationLookOfflineState::ApplicationAppearanceOfflineState: state not loaded, Errorcode=2
2019/10/27 11:03:07.421 26935 **Please do not post TeamViewer IDs**81472 GX0 ManagerHolderStateMachine: Switching from None to NotReady
2019/10/27 11:03:07.421 26935 **Please do not post TeamViewer IDs**80256 GX0 ChatManager::ChatManager: created
2019/10/27 11:03:07.421 26935 **Please do not post TeamViewer IDs**80256 GX0 ChatManager::Factory: ChatManager created
2019/10/27 11:03:07.421 26935 **Please do not post TeamViewer IDs**80256 GX0 IncomingBetterChatCommandHandler::IncomingBetterChatCommandHandler: created
2019/10/27 11:03:07.421 26935 **Please do not post TeamViewer IDs**80256 GX0 IncomingCommandRegistration::Start: registering for ready state properties
2019/10/27 11:03:07.421 26935 **Please do not post TeamViewer IDs**81472 GX0 Initialised XFixes extension (base=87 error=140)
2019/10/27 11:03:07.424 26935 **Please do not post TeamViewer IDs**81472 GX0 DBusStatusNotifier: registered at org.kde.StatusNotifierWatcher
2019/10/27 11:03:29.133 26935 **Please do not post TeamViewer IDs**81472 GX0 Process received SIGINT from process: 0
2019/10/27 11:03:29.134 26935 **Please do not post TeamViewer IDs**28992 GX0 XClipboard: Shutting down event loop
2019/10/27 11:03:29.135 26935 **Please do not post TeamViewer IDs**81472 GX0 Chat::Stop: Stopping chat
2019/10/27 11:03:29.135 26935 **Please do not post TeamViewer IDs**81472 GX0 ChatManager::UnregisterIncomingCommandRegistration: destroying incomingCommandRegistration
2019/10/27 11:03:29.135 26935 **Please do not post TeamViewer IDs**81472 GX0 IncomingCommandRegistration::Stop: disconnecting ready state properties
2019/10/27 11:03:29.135 26935 **Please do not post TeamViewer IDs**81472 GX0 ChatManager::~ChatManager: destroyed
2019/10/27 11:03:29.135 26935 **Please do not post TeamViewer IDs**81472 GX0 IncomingBetterChatCommandHandler::IncomingBetterChatCommandHandler: destroyed
2019/10/27 11:03:29.212 26935 **Please do not post TeamViewer IDs**87552 GX0 CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=26684)
2019/10/27 11:03:29.212 26935 **Please do not post TeamViewer IDs**87552 GX0 CTcpProcessConnector::CloseConnection(): PID=26684
2019/10/27 11:03:29.212 26935 **Please do not post TeamViewer IDs**87552 GX0 InterProcessBase::EventFunctionInternal(): IPC-Connection Closed
2019/10/27 11:03:29.212 26935 **Please do not post TeamViewer IDs**87552 GX0 CTcpProcessConnector::CloseConnection(): PID=26684
2019/10/27 11:03:29.212 26935 **Please do not post TeamViewer IDs**87552 GX0 CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 107: Transport endpoint is not connected
2019/10/27 11:03:29.234 26935 **Please do not post TeamViewer IDs**81472 GX0 Shutting down System DBus
2019/10/27 11:03:29.234 26935 **Please do not post TeamViewer IDs**81472 GX0 InterProcessConfigurationHub::SendToConfigurationHandler(): IPC not available, could not send command: CC=1 CT=110
2019/10/27 11:03:29.234 26935 **Please do not post TeamViewer IDs**81472 GX0 interprocessbase::SecureNetwork destroyed
attempt number 6 at posting my logs, god dam.
Start: 2019/10/27 11:07:15.618 (UTC+0:00)
Version: 14.6.2452
ID: 0
Loglevel: Info (100)
License: 0
Server: master12.teamviewer.com
IC: -**Please do not post TeamViewer IDs**
CPU: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
CPU extensions: l9
OS: Lx Manjaro Linux (x86_64)
IP: 192.168.2.106
Proxy-Settings: Type=0 IP= User=
2019/10/27 11:07:15.625 28874 GX0 SystemID m=1 s=1 f48ad995d1d94f05a2259fdf8e02a280
2019/10/27 11:07:15.627 28874 GX0 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2019/10/27 11:07:15.627 28874 GX0 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2019/10/27 11:07:15.627 28874 GX0 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2019/10/27 11:07:15.962 28874 GX0!! ApplicationLookOfflineState::ApplicationAppearanceOfflineState: state not loaded, Errorcode=25
2019/10/27 11:07:15.962 28874 GX0 ManagerHolderStateMachine: Switching from None to NotReady
2019/10/27 11:07:15.962 28874 GX0 ChatManager::ChatManager: created
2019/10/27 11:07:15.962 28874 GX0 ChatManager::Factory: ChatManager created
2019/10/27 11:07:15.962 28874 GX0 IncomingBetterChatCommandHandler::IncomingBetterChatCommandHandler: created
2019/10/27 11:07:15.962 28874 GX0 IncomingCommandRegistration::Start: registering for ready state properties
2019/10/27 11:07:15.962 28874 GX0 Initialised XFixes extension (base=87 error=140)
2019/10/27 11:07:15.965 28874 GX0 DBusStatusNotifier: registered at org.kde.StatusNotifierWatcher
2019/10/27 11:07:24.164 28874 GX0 XClipboard: Shutting down event loop
2019/10/27 11:07:24.165 28874 GX0 Chat::Stop: Stopping chat
2019/10/27 11:07:24.165 28874 GX0 ChatManager::UnregisterIncomingCommandRegistration: destroying incomingCommandRegistration
2019/10/27 11:07:24.166 28874 GX0 IncomingCommandRegistration::Stop: disconnecting ready state properties
2019/10/27 11:07:24.166 28874 GX0 ChatManager::Close
2019/10/27 11:07:24.166 28874 GX0 ChatManager::UnregisterIncomingCommandRegistration: destroying incomingCommandRegistration
2019/10/27 11:07:24.166 28874 GX0 ChatManager::ClearAccountChat: clearPersistently = 0
2019/10/27 11:07:24.166 28874 GX0 ChatManager::ClearNonAccountChat
2019/10/27 11:07:24.166 28874 GX0 ChatManager::~ChatManager: destroyed
2019/10/27 11:07:24.166 28874 GX0 IncomingBetterChatCommandHandler::IncomingBetterChatCommandHandler: destroyed
2019/10/27 11:07:24.213 28874 GX0 CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=26684)
2019/10/27 11:07:24.213 28874 GX0 CTcpProcessConnector::CloseConnection(): PID=26684
2019/10/27 11:07:24.213 28874 GX0 InterProcessBase::EventFunctionInternal(): IPC-Connection Closed
2019/10/27 11:07:24.213 28874 GX0 CTcpProcessConnector::CloseConnection(): PID=26684
2019/10/27 11:07:24.213 28874 GX0 CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 107: Transport endpoint is not connected
2019/10/27 11:07:24.231 28874 GX0 Shutting down System DBus
2019/10/27 11:07:24.231 28874 GX0 InterProcessConfigurationHub::SendToConfigurationHandler(): IPC not available, could not send command: CC=1 CT=110
2019/10/27 11:07:24.232 28874 GX0 interprocessbase::SecureNetwork destroyed
can someone please tell me how to post my logs , please!
Lets try a picture of my logs and see if the forum will accept that.
[the link has been removed as per the community guidelines.]
Yes this is correct.
Sorry i did already answer this but that was on one of my post that the forum has already deleted.
the logs show after a few lines already the shutdown and cleanup. there is a 2 mins gap in the logs.
the problem must have happend already earlier.
when I start TV here, i can see a 2nd thread running, dealing with networking.
The entire log is 3400 lines long and i dont have a clue what im looking at.
I would post the entire log but after already having 8/9 post deleted from this thread already i just do not know how to.
Why would they build logs that cant not be posted in their support forum ?
Thx for your help but i dont know how to procede.
@rolandg
does this mean anything? these are the errors in my log marked with a "GX0!!"
don't think so; my log file shows the same line.
Im still trying to figure this out but i still get all my posts deleted if i even attempt to show logs.
What exactly do i need to remove from the logs that is causing them to delete the posts ??
I need advice PLEASE.
@rolandgHay i found something interesting.
I downloaded the tarball teamviewer_14.0.14470_amd64.tar.xz and i found i could run teamviewer directly from there and it connects (green light). So i remove my old installation > yay -Rsn teamviewer then i try to install from the tar
what is Qtquickcontrols? how do i install it? why does running TV directly from the download work fine without it? what is wrong with the install from the AUR repos?
Thx man.
p.s. just checking i do have the following installed
hmm, just realised that it was version teamviewer_14.0.14470_amd64.tar.xz that was working directly from the extracted tar (although i still could not install it, see Qt error mentioned above)
So 14.0.1447 will work but only directly from the extracted tar folder.
14.7 will not even work from the extracted tar.
Installing from the Arch AUR does not work.
Looks like i can only use the 14.0.1 and only in its own tar extraction, i cant not install that either. What a dam mess or a linux version and this forum is no better since iv had to battle against most of my post being deleted by the bot. I do not even know if 14.0.1 will work/connect to more up to date clients, i shall have to test it some time.
I would still like to install this app properly so if anyone has any suggestions i'm all ears. thx.
tv-setup seems to be a small wrapper around tv_bin/script/teamviewer_setup
that's a bash script, and at line 240 you will find the simple check for QtQuick controls.
But the check does not work on Manjaro. check the output of
$ packman -Qlq qt5-quickcontrols | grep qmldir
I think teamviewer_setup could have an additional check for the directory /usr/lib/qt/qml/QtQuick/Controls/qmldir
ps: fixed cli above: the option on pacman is -Qlq ( not -Qlp )
means the message QtQuickControls seems to be missing is a false warning.
the set of Qt libraries is good enough for TV.
your getting a bit over my head now but i can see i do have qt5-quickcontrols but pacman -Qlp qt5-quickcontrols throws an error :-
I have tried clicking "Continue" when trying to install from the tar's but when i run it it still just will not connect (remains red "Not ready ....")
The only time it is working is from the older version directly from the extracted tar, none of the instalations have worked from any of the other methods or versions.
Ok so i have been able to install ver 14.0.14470 properly from the tar (i had to clean out /opt/teamviewer manually). I did try 14.7 again but it still fails.
So 14.0.14470 does work but new versions of TV just do not. I hope this version will connect to more up to date clients otherwise im buggered we shall see.
Does anyne know why i can install & run 14.0.14470 but not later versions?
(Sorry for double posting, but it fits better in this posting, because it's about Arch and the issue is newer)
I have the same issue.
I tried Google DNS, restarted the service many times, signed in with the browser and authorized my device, reboot etc. Also tried to install it from the TAR. Can't make it work.
It worked previously on other OS, like MX Linux. But on Manjaro it just doesn't want to connect.
Yea im still waiting for an answer too
Did you try 14.0.14470 ? https://teamviewer.app.box.com/s/ksjaac6bjv2dh6r8wha5akmot4zdy7tj as i did manage to get that version to work after completely cleaning TV of my system first.
I still don't know if this older version is compatible with the current version of TV client because in the end i manually traveled 90 miles to go and assist my dad and his printer problem so i have never actually tested it but its connecting ok.
My father is about 10.000km away, so that's not a solution for me. But actually I just use TV to fix my father's computer :-D
Finally I can connect and login with my account! I saw the solution in the forum, but I didn't have the link. Thank you!!!
Haven't tried to connect to another computer yet.
The solution worked for two weeks. But now 15 was released. My partners updated and I can not connect with 14 any longer...
And when I install the current 15 version, I have the issue again, that I can not connect. So we are again back at square one...
Thats really odd cos when i installed TV 15 it connects fine. Try a complete removal of TV and its settings and a re-install (dont ask me how though but maybe yay -Rsn and the a system wide search for teamviewer remnants).