Teamviewer works in Virtualbox but NOT on real Hardware

judydudi · 2016-10-28 15:55

Hi,

my first topic here.
I tried Q4OS 32&64 bit installations on Virtual Box VM's. Teamviewer works fine there.
Installing Q4OS on a 32 or 64 bit PC System, Teamviewer will install sucsessfully, but by click on the icon the GUI is not shown. Teamviewer is running in the tasklist.
Does anyone had the same problem? Any Idea?

I was using Q4OS 1.6.3. live and CD, 32 and 64 bit.
With the 32bit live version i can install Teamviewer in the livesystem an it works fine on the real system!
With the 64bit live Version the is not enough memory in the live system.

greetings, jens

Last edited by judydudi (2016-10-28 16:11)

q4osteam · 2016-10-28 16:11

Welcome judydudi,

Which way did you install TeamViewer ? From the Q4OS Software Centre or another way ?

TeamViewer works fine here - on a real hardware. Please run terminal and run from:
$ teamviewer
and paste terminal output here to analyze.

judydudi · 2016-10-28 16:31

HI,

i installed it from the Software Centre.
Here is the output:

judydudi@5z5e543:~$ teamviewer

Init...
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
wine: /home/judydudi/.local/share/teamviewer11 is not owned by you
wine: /home/judydudi/.local/share/teamviewer11 is not owned by you
judydudi@5z5e543:~$ ^C
judydudi@5z5e543:~$

My /home is a NTFS Filesystem. on /sda4

Last edited by judydudi (2016-10-28 16:33)

q4osteam · 2016-10-28 16:37

Sounds like you started up TeamViewer as root, this would make the '~/.local/share/teamviewer11' folder a root owned folder.

Open a terminal, type in:
$ sudo rm -rf /home/judydudi/.local/share/teamviewer11

Try to run TeamViewer again:
$ teamviewer
and report back.

EDIT:
>> My /home is a NTFS Filesystem. on /sda4 <<
Oh, this could raise the problem up. You may need to reside your '$HOME' on ext4 filesystem

judydudi · 2016-10-28 17:08

ah yes. this might be it.

but i will not change to ext4.
i will share /home with a windows system (vm images etc.)

my intend is a stick with
sda1 : fat 32 (EFI boot)
sda2 : swap
sda3 : ext4 (Q4OS)
sda4 : ntfs (/home)

q4osteam · 2016-10-28 17:35

Well, we could try to check mount options for your 'home' folder, please run in terminal:
$ cat /etc/fstab
$ mount | grep home
$ ls -al ~
and paste output here.

Dai_trying · 2016-10-28 18:44

Hi Judydudi,
I just wanted to let you know how I share my documents etc with Windows (and other Os's).

First I install only to a single partition.

Next I create a partition to use for shared data and on this partition I create the folders Documents, Downloads, Pictures, Videos and any other folders you might want to use.

Now I create an entry in /etc/fstab to mount the partition on boot-up.

Then on my main (q4os) installation I create a soft-link for each folder on the shared partition to my home directory (after removing the Os created directories).

Now when I boot my machine the shared partition (can be any fs-type) will be mounted and accessible in /home/user/Documents (for instance) although the data is actually located on another partition.

This has the benefit of being able to use the same data folders for many different Os's (I currently have 7 on this laptop). If you use a shared home folder you will have issues if one Os uses a different configuration file or layout, which can cause serious system problems for another Os.

Last edited by Dai_trying (2016-10-28 18:44)

judydudi · 2016-10-29 15:44

Hi.

i see with installing Teamvier via software center one error: (Desktop Profile: keep installed ...)
Setting up teamviewer (11.0.67687) ...
Error in file "/opt/trinity/share/applications/tde/tdefontview.desktop": "fonts/package" is an invalid MIME type ("fonts" is an unregistered media type)
But end message says sucsessfully installed.

I tried to run teamviewer as root. That work's fine!

here is the output:

judydudi@fgtyhtr:~$ cat /etc/fstab
# UNCONFIGURED FSTAB FOR BASE SYSTEM
proc /proc proc defaults 0 0
# /dev/sda1
UUID=08D1-9E95 /boot/efi vfat defaults 0 0
# /dev/sda2
UUID=43bda7ff-6f3e-416b-b841-4149caad1041 swap swap sw 0 0
# /dev/sda3
UUID=d653e79e-207d-4246-a4f1-f5d3d8771224 / ext4 rw,errors=remoun
t-ro 0 1
# /dev/sda4
UUID=4762ABBB5BFF985E /home ntfs defaults 0 0

judydudi@fgtyhtr:~$ mount | grep home
/dev/sda4 on /home type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,bl
ksize=4096)

judydudi@fgtyhtr:~$ ls -al ~
total 62
drwxrwxrwx 1 root root 4096 Oct 29 16:06 .
drwxrwxrwx 1 root root 4096 Oct 28 19:18 ..
drwxrwxrwx 1 root root 0 Oct 29 15:54 .appsetup2
-rwxrwxrwx 1 root root 28 Oct 29 16:04 .bash_history
-rwxrwxrwx 1 root root 220 Oct 28 19:18 .bash_logout
-rwxrwxrwx 1 root root 3515 Oct 28 19:18 .bashrc
drwxrwxrwx 1 root root 0 Oct 29 15:52 .cache
-rwxrwxrwx 1 root root 1786 Sep 1 2015 .compton-tde.conf
drwxrwxrwx 1 root root 4096 Oct 29 16:01 .config
-rwxrwxrwx 1 root root 52 Oct 29 16:06 .DCOPserver_fgtyhtr__0
lrwxrwxrwx 1 root root 80 Oct 29 16:06 .DCOPserver_fgtyhtr_:0 -> /home/judydudi /.DCOPserver_fgtyhtr__0
drwxrwxrwx 1 root root 0 Oct 29 16:01 Desktop
-rwxrwxrwx 1 root root 26 Oct 29 15:44 .dmrc
drwxrwxrwx 1 root root 4096 Oct 29 16:04 Documents
-rwxrwxrwx 1 root root 3876 Oct 28 19:18 .face.icon
drwxrwxrwx 1 root root 0 Feb 6 2015 .gconf
-rwxrwxrwx 1 root root 898 Nov 28 2015 .gtkrc-q4os
-rwxrwxrwx 1 root root 898 Nov 28 2015 .gtkrc-q4os-kde4
-rwxrwxrwx 1 root root 189 Oct 29 16:06 .ICEauthority
drwxrwxrwx 1 root root 0 Oct 17 2014 .kde
drwxrwxrwx 1 root root 0 Dec 17 2014 .local
drwxrwxrwx 1 root root 0 Oct 29 15:44 .mcop
-rwxrwxrwx 1 root root 31 Oct 29 15:44 .mcoprc
-rwxrwxrwx 1 root root 675 Oct 28 19:18 .profile
drwxrwxrwx 1 root root 0 Oct 14 2014 .q4data
drwxrwxrwx 1 root root 4096 Oct 29 16:01 .qt
-rwxrwxrwx 1 root root 522 Oct 12 2014 .tderc
drwxrwxrwx 1 root root 4096 Oct 29 15:44 .trinity
-rwxrwxrwx 1 root root 52 Oct 29 16:06 .Xauthority
-rwxrwxrwx 1 root root 384 Sep 1 2015 .xcompmgrrc
-rwxrwxrwx 1 root root 171 Dec 23 2014 .Xresources
-rwxrwxrwx 1 root root 2543 Oct 29 16:07 .xsession-errors
-rwxrwxrwx 1 root root 649 Dec 23 2014 .xsettingsd
judydudi@fgtyhtr:~$

@Dai_trying

Thank you for your feedback. I will try to make the configuration and check the usability for me.

Last edited by judydudi (2016-10-29 15:45)

Dai_trying · 2016-10-29 16:03

You're welcome, it works well for me but there are many different ways of doing things with Linux

And just as a note, I don't think it is ever a good idea to set up a system as only root user, but as I don't know your use case for the machine I will assume you know what you are doing.

q4osteam · 2016-10-29 16:51

@judydudi
We could try to change mount options for your fstab as well as to setup ownership for /home files:

First install 'ntfs-3g' package:
$ sudo apt-get install ntfs-3g

Edit your '/etc/fstab' and modify the /dev/sda4 line:
/dev/sda4 UUID=4762ABBB5BFF985E /home ntfs-3g exec,permissions,defaults 0 0

Reboot or remount '/home'. Now change ownership for all files in your home from terminal:
$ sudo chown -R judydudi:judydudi /home/judydudi

Now, you could try to run TeamViewer as user. If you will run it as root, you will have to set ownership again.

judydudi · 2016-10-29 19:16

@q4os team

the ntfs-3g packages are already installed in the base system.

After edit the fstab as you discribe and reboot i can not login any more.
(screen becames black and login screen returns)

Last edited by judydudi (2016-10-29 19:17)

q4osteam · 2016-10-29 19:30

You need to take ownership of your home files. Switch to the console, press 'ctrl-alt-f2' on the login screen, then login to the console and run:
$ sudo chown -R judydudi:judydudi /home/judydudi
$ sudo reboot
Reboot. Now you should be able to login.

judydudi · 2016-10-29 20:42

That's it. Now it works fine to me!
Thank you Q4OS Team.

This solution works fine for me with Q4OS on a Pendrive Stick (Corsair GTX) and Windows on the Computer.
With the Stick i always have the best System with me ;-)

For more Systems on the stick it seems to me better to use Dai_trying's solution.

Dai_trying · 2016-10-29 21:20

One thing to be aware of if you plan on using this on other computers as well, the entries in fstab will not be found when booting and may cause a 90 second delay while looking for the correct partition UUID to try and automount.

Q4OS Forum

#1 2016-10-28 15:55

Teamviewer works in Virtualbox but NOT on real Hardware

#2 2016-10-28 16:11

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#3 2016-10-28 16:31

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#4 2016-10-28 16:37

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#5 2016-10-28 17:08

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#6 2016-10-28 17:35

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#7 2016-10-28 18:44

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#8 2016-10-29 15:44

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#9 2016-10-29 16:03

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#10 2016-10-29 16:51

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#11 2016-10-29 19:16

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#12 2016-10-29 19:30

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#13 2016-10-29 20:42

Re: Teamviewer works in Virtualbox but NOT on real Hardware

#14 2016-10-29 21:20

Re: Teamviewer works in Virtualbox but NOT on real Hardware

Board footer