Install Vineforce Teams | Linux .deb Installer
Install Vineforce Teams on Linux (.deb Package)
Linux | GNOME / Wayland Display Server | Debian / Ubuntu (.deb)
This guide covers installing Vineforce Teams as a real Debian package. Instead of running a script every time, you build a .deb once and install it with standard apt/dpkg commands — dependencies, the .NET runtime, the GNOME Shell extension, a desktop menu entry, a custom icon, a CLI alias, and login autostart are all handled automatically as part of the install.
Two steps, start to finish:
- Run the build script — it downloads the app, converts the icon, stages the GNOME extension, and packages everything into a
.debfile - Run the install command the script prints —
apt/dpkgtakes it from there
No PowerShell required, no manual token or config file editing, and no need to remember a long list of setup commands ever again — reinstalling or updating is just rebuilding the .deb and reinstalling it.
Why a .deb instead of a plain script?
A real package means proper apt install / apt purge semantics: dependencies resolve automatically, removal is a single standard command, and the app shows up like any other installed program — in your app menu, on PATH, and with its own icon.
Windows installation For Windows deployment, see the Windows manual install guide.
Prerequisites
| Requirement | Details |
|---|---|
| Operating System | Debian/Ubuntu-based Linux with GNOME Shell and Wayland display server |
| Internet Access | Required to download the app, GNOME extension, icon, and (if missing) the .NET runtime |
| sudo Privileges | Required to install packages (imagemagick, fakeroot if missing) and to install the final .deb |
| curl / unzip | Used by the build script to fetch and extract the application |
| Vineforce Teams Credentials | Your username and password — no token required |
Wayland requirement
This app is designed for systems running Wayland with GNOME Shell. Most modern Linux distributions (Ubuntu 22.04+, Fedora 25+, Debian 12+) default to Wayland. Verify with echo $XDG_SESSION_TYPE — it should output wayland.
Step 1: Download the Build Script
Download build-vineforce-teams-deb.shSave it to your Linux machine — for example, to your Downloads folder:
~/Downloads/build-vineforce-teams-deb.sh
Step 2: Run the Build Script
Make it executable and run it in one command:
chmod +x ~/Downloads/build-vineforce-teams-deb.sh && ~/Downloads/build-vineforce-teams-deb.sh
The script runs fully automatically and prints progress for each stage:
=== Cleaning previous build ===
=== Creating package structure ===
=== Downloading application ===
=== Converting app icon ===
=== Downloading GNOME extension ===
=== Creating CLI symlink ===
=== Writing desktop menu entry ===
=== Writing autostart entry ===
=== Writing control file ===
=== Writing postinst script ===
=== Writing prerm script ===
=== Writing postrm script ===
=== Building .deb package ===
sudo password prompt
If ImageMagick or fakeroot aren't already installed, the script installs them via apt-get, which may prompt for your sudo password.
When it finishes, it prints the finished package path and two install command options — you only need to run one:
=== BUILD COMPLETE ===
Package: /home/you/vineforce-teams_build/vineforce-teams_1.0.0_amd64.deb
Install it with:
sudo apt install /home/you/vineforce-teams_build/vineforce-teams_1.0.0_amd64.deb
Or:
sudo dpkg -i /home/you/vineforce-teams_build/vineforce-teams_1.0.0_amd64.deb && sudo apt-get install -f
The Package: path above is just an example. Your terminal will print the actual path based on your home directory and the current package version — always use the exact line your terminal shows, not this sample.
Step 3: Install the .deb Package
The build script prints two ready-to-run install commands at the very end of its output, once it finishes — copy and run the exact line your terminal shows you, not the example below. The path and filename will differ depending on your username, build folder, and the app's current version.
Example format only (yours will differ):
Option A (recommended):
sudo apt install /home/<your-username>/vineforce-teams_build/vineforce-teams_<version>_amd64.deb
Option B:
sudo dpkg -i /home/<your-username>/vineforce-teams_build/vineforce-teams_<version>_amd64.deb && sudo apt-get install -f
apt install is generally preferred since it resolves the package's declared dependencies (procps, coreutils, sed, grep, gnome-shell-extension-prefs, dbus-x11, curl, gnome-screenshot, xdg-desktop-portal) automatically. The dpkg -i && apt-get install -f form does the same thing in two steps and is mainly useful if apt install isn't available for some reason.
What Happens During Install (Automatic)
Once you run the install command, apt/dpkg handles everything else.
Dependency Resolution
All required system packages are declared in the package's control file and installed automatically — no manual apt-get install needed.
.NET 10 Runtime
If .NET isn't already on the system, the package's postinst script installs the .NET 10 runtime into /opt/dotnet automatically, with a symlink at /usr/local/bin/dotnet.
GNOME Shell Extension
The window-calls-extended extension is staged system-wide at:
/usr/share/gnome-shell/extensions/[email protected]/
After installation If screenshot or window tracking features aren't working after the first run, log out and log back in to activate the extension. GNOME Shell extensions are activated on session start.
Desktop Menu Entry, Icon, and CLI Alias
- A menu shortcut named Vineforce Teams appears in your Applications menu, using a custom icon converted automatically from the app's
.icologo during the build - A
vineforce-teamscommand becomes available onPATH(/usr/bin/vineforce-teams), so you can launch it from any terminal - The running app's taskbar/dock icon matches the launcher icon too
Login Autostart
An entry at /etc/xdg/autostart/vineforce-teams.desktop ensures Vineforce Teams launches automatically every time any user logs in — system-wide, no per-user setup needed.
Immediate Launch
Unlike a typical package, this one also launches the app immediately as part of installation — you don't have to find it in the menu or wait for next login. The postinst script detects the currently logged-in desktop user and starts the app in their session automatically.
Step 4: Sign In with Username and Password
When Vineforce Teams opens, it will show a login screen. Enter your Vineforce Teams username and password — the same credentials you use to access the Vineforce Teams Web Application.
No token needed There's no auth token, config file, or environment variable to set for this app. Signing in through the app window is the only authentication step.
Step 5: Verify the Application is Running
Check the Process
ps aux | grep -i "Vineforce.Admin.Desktop.Avalonia"
Check the Menu Shortcut and Icon
Open your Applications menu and search for Vineforce Teams — it should appear with its custom icon, not a generic placeholder.
Check the CLI Alias
which vineforce-teams
Check with System Monitor
Open your desktop's System Monitor (GNOME: gnome-system-monitor) and search for Vineforce.
Troubleshooting
| Problem | Solution |
|---|---|
| Script permission denied | Run chmod +x build-vineforce-teams-deb.sh before executing. |
dpkg-deb: error: parsing file ... control | The control file's continuation formatting broke. Re-download the latest build script — this was fixed by keeping the Description field single-line. |
| Executable not found after download | The zip's internal folder structure may have changed. Check EXE_REL_PATH in the script against the actual extracted contents. |
| Icon still shows as generic | Confirm ICON_URL in the script is reachable, and check /usr/share/icons/hicolor/256x256/apps/vineforce-teams.png exists after install. A logout/login may be needed to refresh GNOME's icon cache in some cases. |
App keeps running after apt purge | Make sure you rebuilt with the latest script — the prerm script now sends SIGTERM, waits, then force-kills with SIGKILL if needed. |
| Login screen doesn't appear | Ensure the process launched successfully with ps aux | grep Vineforce. Try vineforce-teams from a terminal to see any error output directly. |
| Login fails with correct credentials | Confirm you're using your Vineforce Teams Web Application credentials, and check your network connection. |
apt install fails on dependencies | Run sudo apt-get update first, then retry the install command. |
| GNOME extension not working after install | Log out and log back in to activate it — this is required after first install. |
| App fails to launch (Wayland error) | Confirm your session is running Wayland: echo $XDG_SESSION_TYPE should output wayland. |
Uninstalling
Since this is a real package, removal is a single standard command:
sudo apt purge vineforce-teams
This stops the running app (via the package's prerm script), removes all installed files, the desktop entry, the CLI alias, the autostart entry, and the GNOME extension.
.NET runtime is not removed
The .NET 10 runtime installed to /opt/dotnet is left in place, since other applications might depend on it. Remove it manually if you're sure nothing else needs it:
sudo rm -rf /opt/dotnet /usr/local/bin/dotnet
Best Practices
- Rebuild to update — re-run the build script and reinstall the new
.debto update the application; there's no separate "update" command - Log out and log in after the first installation if screenshot or tracking features are not working — this reloads the GNOME Shell extension
- Keep your credentials handy — since there's no token file, you'll need your username and password on first launch (and again if your session expires)
- Use
sudo apt purge, notsudo apt remove, for a truly clean uninstall that also cleans up the GNOME extension and caches
What's Next?
Once Vineforce Teams is running and you've signed in, it will begin tracking activity and syncing with your Vineforce Teams environment.
View the recorded data by logging into the Vineforce Teams Web Application.
Need to remove Vineforce Teams? See the Uninstalling section above, or run sudo apt purge vineforce-teams.
For Windows deployment, see: