Comment # 9 on bug 1194126 from Larry Finger

(In reply to Andrei Borzenkov from comment #8)
> (In reply to Larry Finger from comment #7)
> > I reinstalled a TW KDE system in my TW VM. Now I can run Wayland and test my
> > system. I discovered the following:
> > 
> > When I login after boot to Plasma(Wayland), the shared volumes are mounted
> > by vboxsf, but screen resize can only be changed in Settings, not be pulling
> > on the corners. Is this the expected behavior? The shared clipboard does not
> > work even after enabling and starting the vboxclient-clipboard service.
> > 
> 
> I do not know what you are testing. The virtualbox-guest-tools-6.1.30-622.2
> still installs vboxclient-clipboard.service as system unit and I already
> told you it was not going to work. It must be user service stared as part of
> user session (or it can be started by any other means offered by desktop
> environment; I never claimed this is the only possible solution, I quite
> clear said "proof of concept").

I was testing a local version built with osc. I chose that to save a little
build time on OBS.

The service file is installed into
%{buildroot}%{_userunitdir}/vboxclient-clipboard.service and the user versions
of the pre- and post-macros are used. The file list for the guest tools package
shows the service file in the correct directory.
> 
> > 
> > If I logout of the Wayland session and login using X11, the screen resizes
> > the way I expect, and everything works.
> 
> When you log into X11 VBoxClient is started via xinit script. It is
> unrelated to the service vboxclient-clipboard.service.

I know that. I was just trying to understand how screen resizing worked under
Wayland as I will be the one getting the complaints when screen resizing
doesn't work the way it does under X11.
> 
> > Is "After=graphical-session.target" the correct condition? Something is
> > killing the service. Perhaps it is starting too early.
> > 
> 
> This is what worked for me. I wanted to be sure desktop session startup is
> complete. 
> 
> > Why isn't "/usr/bin/VBoxClient --clipboard" working for me?
> > 
> 
> You did not say anything about testing it. You said your service did not
> work, that is not the same. This command most certainly worked for me when
> started explicitly in Wayland GNOME session. Just as my example systemd
> *user* service.

I enabled the service with a 'systemctl --user enable vboxclient-clipboard'.

I then rebooted and logged into Wayland. At that point, 'systemctl --user
status  vboxclient-clipboard' showed the following:'

��������� vboxclient-clipboard.service - VirtualBox shared clipboard for Wayland
     Loaded: loaded (/usr/lib/systemd/user/vboxclient-clipboard.service;
enabled; vendor preset: disabled)
     Active: inactive (dead)

I then issued a 'systemctl --user restart vboxclient-clipboard'. At that point,
'systemctl --user status  vboxclient-clipboard' showed the following:

��������� vboxclient-clipboard.service - VirtualBox shared clipboard for Wayland
     Loaded: loaded (/usr/lib/systemd/user/vboxclient-clipboard.service;
enabled; vendor preset: disabled)
     Active: active (running) since Mon 2022-01-10 13:41:21 CST; 42s ago
    Process: 1828 ExecStart=/usr/bin/VBoxClient --clipboard (code=exited,
status=0/SUCCESS)
   Main PID: 1831 (VBoxClient)
      Tasks: 4 (limit: 2332)
     Memory: 3.5M
        CPU: 10ms
     CGroup:
/user.slice/user-1000.slice/user@1000.service/app.slice/vboxclient-clipboard.service
             ������������������1831 /usr/bin/VBoxClient --clipboard
             ������������������1832 /usr/bin/VBoxClient --clipboard

Jan 10 13:41:21 localhost.localdomain systemd[1459]: Starting VirtualBox shared
clipboard for Wayland...
Jan 10 13:41:21 localhost.localdomain systemd[1459]: Started VirtualBox shared
clipboard for Wayland.

At this point, /usr/bin/VBoxClient --clipboard should have been run, but I
still got no shared clipboard. Finally, I ran that command manually, and still
no shared clipboard. 

I just pushed my current working version to
https://build.opensuse.org/repositories/home:lwfinger:branches:Virtualization/virtualbox
It is still building, but it should be done within the hour. I verified that
the publish flag is still set for x86_64.