![]() I am posting this here because I was kind of hoping openSUSE would win because like I said it would make my life easier to use one distribution instead of two, so I was hoping that maybe you could correct me if my comparison is wrong and maybe you who know Tumbleweed much better than me have some good arguments about why it is better than Arch (because if you thought Arch is better I assume you would not be here). The most important part was Nr.1 because I didn’t find in the main official repositories some of the software I am using (like Eclipse and Code::Blocks), and some where missing even from OBS (like teamviewer and truecrypt).īut I am not sure about several points since I am new to openSUSE so maybe you can correct me. So I tested in the last few weeks openSUSE Tumbleweed and these are my conclusions (from my point of view only, for what I need):Īs you can see, from my point of view, it seems that Arch is still the better option for me (as this is a comparison for my needs, for someone else some of the points where I chose a winner would be reversed). Now that Tumbleweed seems to have become, from a small project, an important part of openSUSE I was thinking that maybe I could use openSUSE stable (Leap) on my stable computers and Tumbleweed for my bleeding edge installations to make my life a little easier by not having to use two very different systems. If you check the PKGBUILD file you'll see it installs a system service for you, so the "systemd" way would have been: systemctl enable teamviewerd systemctl start teamviewerd or, if you want to run the daemon only when you need it, just systemctl.I am not sure where I should have posted this question/comparison and I am sorry if this is not the proper location.įor the last several years I have been using ubuntu on my stable linux installations and Arch Linux for my bleeding edge ones. ![]() Sources Manjaro Linux Forum – 4 Jan 18 Teamviewer-beta 13, "Not ready, please check connection" In xdg-terminal: systemctl disable teamviewerd To ease security concerns, you can also do this so teamviewerd isn’t enabled on restart until otherwise: After all, it does allow for remote network access, and inadvertently leaving it on, no matter how secure you think you are could be exploited. Turning it offīut that’s not all! Presumably, the reason why teamviewerd isn’t enabled by default is for security concerns. Once you enable the daemon, TeamViewer should work immediately every subsequent boot of your Manjaro / Arch instance. ![]() In xdg-terminal: systemctl enable teamviewerd To keep it on between restarts, do this: In xdg-terminal: systemctl start teamviewerd ![]() To enable TeamViewer’s remote capabilities immediately, do this: ![]() Rather than trying to over-complicate with a solution that most likely will not work, try enabling the service so the software functions as intended. PrefaceĪ quick tip for people who need a solution fast: Having installed TeamViewer from the AUR and opening it, you may notice it doesn’t work right away. A republishing of my original TeamViewer thread revised to fit the forum’s new support-focused approach for people who don’t want to search the web for a solution to this very problem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |