I installed net-misc/teamviewer-11.0.57095 using USE="-system-wine", ran "sudo /etc/init.d/teamviewerd11 start" and ran teamviewer11, but there is no "Connect to partner" button, and if I enter their ID and hit enter nothing happens. Haven't and won't try using USE="system-wine". Reproducible: Always
Created attachment 430590 [details] screenshot
I also experience this issue with -system-wine, but do not experience this issue with system-wine
Looks like we are missing a dependency (new?) on media-libs/libpng:1.2[abi_x86_32(-)], presumably my system-wine is OK because of the png USE flag for that
I have media-libs/libpng-1.6.19 (0) emerged.
(In reply to DrSlony from comment #4) > I have media-libs/libpng-1.6.19 (0) emerged. I said media-libs/libpng:1.2 with USE=abi_x86_32
Yes I saw you say that :) I'm saying that I don't have that, to add support to your claim.
(In reply to DrSlony from comment #6) > Yes I saw you say that :) I'm saying that I don't have that, to add support > to your claim. Can you please try whether emerging media-libs/libpng:1.2 with USE=abi_x86_32 fixes the issue for you?
Hello Apologies for the delay, I will not be able to test this for another two weeks. Please ping me if I still haven't gotten back to you in three weeks
I was unable to fix it using +system-wine (but I have really old version 1.7.11). Emerging media-libs/libpng:1.2 with USE=abi_x86_32 fixed the same issue for me.
I can confirm the bug and the solution given by NP-Hardass. Until the ebuild in the main Portage tree is fixed, I have created an ebuild for TeamViewer 11.0.57095 in the local overlay on my laptop, with the following extra line: RDEPEND=" system-wine? ( app-emulation/wine[abi_x86_32(-)] ) sys-apps/dbus[abi_x86_32(-)] dev-qt/qtcore:4[abi_x86_32(-)] dev-qt/qtgui:4[abi_x86_32(-)] dev-qt/qtwebkit:4[abi_x86_32(-)] media-libs/alsa-lib[abi_x86_32(-)] + media-libs/libpng:1.2[abi_x86_32(-)] x11-libs/libICE[abi_x86_32(-)] x11-libs/libSM[abi_x86_32(-)] x11-libs/libX11[abi_x86_32(-)] x11-libs/libXau[abi_x86_32(-)] x11-libs/libXdamage[abi_x86_32(-)] x11-libs/libXdmcp[abi_x86_32(-)] x11-libs/libXext[abi_x86_32(-)] x11-libs/libXfixes[abi_x86_32(-)] x11-libs/libXrandr[abi_x86_32(-)] x11-libs/libXtst[abi_x86_32(-)]"
Thank you for confirming the fix. Resolved in 1213177dcd9da5b2997efabbbbe599e343f8a394.
When installed months ago, I had to use -system-wine in order to have teamviewer working. And now it's set the same way. That's odd. All's well that ends well.
(In reply to NP-Hardass from comment #11) > Thank you for confirming the fix. > > > Resolved in 1213177dcd9da5b2997efabbbbe599e343f8a394. Hi. Thanks for updating the ebuild so quickly. I have a quick non-rhetorical question regarding that commit: RDEPEND=" - system-wine? ( app-emulation/wine[abi_x86_32(-)] ) + system-wine? ( app-emulation/wine[abi_x86_32(-),png] ) + !system-wine? ( media-libs/libpng:1.2[abi_x86_32(-)] ) sys-apps/dbus[abi_x86_32(-)] dev-qt/qtcore:4[abi_x86_32(-)] dev-qt/qtgui:4[abi_x86_32(-)] I already had the png flag set for app-emulation/wine but it didn't pull in libpng:1.2, it pulled in libpng:0 with ABI_X86="32 64 -x32". Isn't it still necessary to have libpng:1.2 when TeamViewer is built with USE="system-wine"?
(In reply to Fitzcarraldo from comment #13) > (In reply to NP-Hardass from comment #11) > > Thank you for confirming the fix. > > > > > > Resolved in 1213177dcd9da5b2997efabbbbe599e343f8a394. > > Hi. Thanks for updating the ebuild so quickly. I have a quick non-rhetorical > question regarding that commit: > > RDEPEND=" > - system-wine? ( app-emulation/wine[abi_x86_32(-)] ) > + system-wine? ( app-emulation/wine[abi_x86_32(-),png] ) > + !system-wine? ( media-libs/libpng:1.2[abi_x86_32(-)] ) > sys-apps/dbus[abi_x86_32(-)] > dev-qt/qtcore:4[abi_x86_32(-)] > dev-qt/qtgui:4[abi_x86_32(-)] > > I already had the png flag set for app-emulation/wine but it didn't pull in > libpng:1.2, it pulled in libpng:0 with ABI_X86="32 64 -x32". Isn't it still > necessary to have libpng:1.2 when TeamViewer is built with USE="system-wine"? Honestly, its been two and a half months since I last looked at it, (and requested that the fix be tested) so it isn't fresh in my mind. What I remember discovering was that there was PNG support added to the windows binary. The need for libpng:1.2 is due to the fact that the dinky, years old, bundled wine-1.6 was built against that old version. I had confirmed at the time in NY end that an updated wine, built against modern libpng displayed the missing buttons, thus the core issue was PNG support for wine, with the prebuilt binary requiring ,,1.2 specifically.