Bug 678740 – net-misc/teamviewer-14.1.9025 - ResourceLoader: loaded file '/opt/teamviewer14/tv_bin/resources/TVResource_ru.so' version (9025) is not matching with application version (14.1.9025)

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Victor Kustov 2019-02-25 10:39:25 UTC]

GUI start failed, in logs:
ResourceLoader: loaded file '/opt/teamviewer14/tv_bin/resources/TVResource_ru.so' version (9025) is not matching with application version (14.1.9025)

[Comment 1 Adam Carter 2019-04-21 02:38:01 UTC]

Created attachment 573494 [details]
emerge --info for teamviewer

[Comment 2 Adam Carter 2019-04-21 02:39:46 UTC]

Same issue for me, here's a bit more of the tv log


2019/04/21 12:17:13.273  3832 123839326182656 G!  DBusServices: could not register application. Connected: 0
2019/04/21 12:17:13.277  3832 123839326182656 G!! ResourceLoader: loaded file '/opt/teamviewer/tv_bin/resources/TVResource_en.so' version (2558) is not matching with application version (14.2.2558), Errorcode=2
2019/04/21 12:17:13.277  3832 123839326182656 G   Loaded language 'en', using locale 'en'
2019/04/21 12:17:13.277  3832 123839326182656 G   InterProcessBase::SecureNetwork created
2019/04/21 12:17:13.278  3832 123839326182656 G   AutoLogin::Login: enabled: 1
2019/04/21 12:17:13.278  3832 123839326182656 G   AccountLoginStateMachine::Reset
2019/04/21 12:17:13.278  3832 123839326182656 G!! ApplicationLookOfflineState::ApplicationAppearanceOfflineState: state not loaded, Errorcode=2
2019/04/21 12:17:13.278  3832 123839326182656 G!!!Own session could not be resolved, unable to startup, Errorcode=2
2019/04/21 12:17:13.278  3832 123839326182656 G   Chat::Stop: Stopping chat
2019/04/21 12:17:13.279  3832 123839326182656 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 9 failed with error 2, Errorcode=2
2019/04/21 12:17:13.279  3832 123839326182656 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 5 failed with error 2, Errorcode=2
2019/04/21 12:17:13.279  3832 123839326182656 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 6 failed with error 2, Errorcode=2
2019/04/21 12:17:13.279  3832 123839326182656 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 10 failed with error 2, Errorcode=2
2019/04/21 12:17:13.279  3832 123839326182656 G   interprocessbase::SecureNetwork destroyed
2019/04/21 12:17:13.284  3832 123839326182656 G   Shutting down System DBus

[Comment 3 andreas 2019-04-25 08:10:26 UTC]

try to kill elogind(-daemon) process. it works for me.

[Comment 4 Ondrej 2019-06-13 07:22:32 UTC]

Same for me.

[Comment 5 Ondrej 2019-06-13 07:24:11 UTC]

Created attachment 579690 [details]
teamviewer14/logfiles/startup.log

[Comment 6 Ondrej 2019-06-13 07:26:32 UTC]

Created attachment 579694 [details]
teamviewer14/logfiles/TeamViewer14_Logfile.log

[Comment 7 Michael 2019-07-06 13:35:56 UTC]

https://forums.gentoo.org/viewtopic-p-8332956.html?sid=3cc21e5a27935e38975ee85bf03317ae#8332956

[Comment 8 Maxim Koltsov (RETIRED) 2019-08-04 19:17:41 UTC]

I've blocked consolekit in teamviewer ebuild and wrote a warning message in the ebuild. Thanks for the report!

[Comment 9 Michael 2019-08-04 19:34:14 UTC]

(In reply to Maxim Koltsov from comment #8)
> I've blocked consolekit in teamviewer ebuild and wrote a warning message in
> the ebuild. Thanks for the report!

It can technically work with consolekit or elogind. It just can't work if they are both installed and running at the same time. Which I suppose is not specific to teamviewer. Two session managers is probably not a good idea in general.

[Comment 10 Maxim Koltsov (RETIRED) 2019-08-04 19:38:39 UTC]

(In reply to Michael from comment #9)
> (In reply to Maxim Koltsov from comment #8)
> > I've blocked consolekit in teamviewer ebuild and wrote a warning message in
> > the ebuild. Thanks for the report!
> 
> It can technically work with consolekit or elogind. It just can't work if
> they are both installed and running at the same time. Which I suppose is not
> specific to teamviewer. Two session managers is probably not a good idea in
> general.

So you mean that '^^ (elogind systemd consolekit)' dependecy will be more precise?

[Comment 11 Michael 2019-08-04 19:45:48 UTC]

(In reply to Maxim Koltsov from comment #10)
> (In reply to Michael from comment #9)
> > (In reply to Maxim Koltsov from comment #8)
> > > I've blocked consolekit in teamviewer ebuild and wrote a warning message in
> > > the ebuild. Thanks for the report!
> > 
> > It can technically work with consolekit or elogind. It just can't work if
> > they are both installed and running at the same time. Which I suppose is not
> > specific to teamviewer. Two session managers is probably not a good idea in
> > general.
> 
> So you mean that '^^ (elogind systemd consolekit)' dependecy will be more
> precise?


I'm not entirely sure what the right solution is. Maybe one of (elogind systemd consolekit).