> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.flowace.ai/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # Data Not Populating: Ubuntu Interactive App (XUI) What to check, step by step, when Flowace isn’t tracking or no data is showing. | Item | Details | | ---- | ---- | | App | Ubuntu Interactive App (XUI) | | Platform | Ubuntu | | Visible to the user | Yes. Flowace is in the apps menu. | | Signs in with | Workspace address, email and password. | | Where to find it | Terminal | Use this guide when the Interactive App on Ubuntu isn’t tracking, or no data is showing. Work top to bottom: check that the app is installed, then running, then logged in. Most issues are fixed by Level 3. --- ### Start here: three questions Ask these three questions, in this order. | Question | Go to | | ---- | ---- | | Is it installed? | Level 1 | | Is it running? | Level 2 | | Is the user logged in? | Level 3 | If all three are yes but there is still no data, go to Level 4 (Wayland and sync) and then Advanced. --- ### Names to look for The app shows under different names in the apps menu and process lists. Look for any of these. | Where you look | What to look for | | ---- | ---- | | App name | Flowace | | Process list | Flowace, Flowace Helper | | Developer / publisher signature | Flowace Technologies Pvt Ltd | --- ### Level 1: Verify it’s installed Goal: confirm the app files are on the computer. * Easy way: open the apps menu and look for Flowace. * Commands: open Terminal. ``` ls -l ~/.local/flowace/ ls -l ~/.local/share/applications/flowace.desktop ``` ||| If app is not installed: Install it first (see the Installation Guide). Don’t go further until the files are present. --- ### Level 2: Verify it’s running Installed isn’t the same as running. Confirm the app is active right now. * **Commands (Terminal):** ``` ps aux | grep -i flowace ``` Shows the running app. Ignore the line containing “grep”. ``` systemctl --user status flowace-monitor ``` * Should say **active**. **To start it:** open Flowace from the apps menu, or run: ``` systemctl --user start flowace-monitor ``` ||| If it’s installed but won’t stay running: The quickest first fix is to restart the computer once. The app is set to start automatically on boot. --- ### Level 3: Verify the user is logged in This is the most common reason for “no data” when the app is installed and running. * Open Flowace (apps menu). * You should see **“You’re in Work mode”**. If you see the **login screen** instead, the user is logged out, and that’s why there’s no data. * **Fix:** log in with the three details: * Workspace: * Email and Password (use Forget Password if needed) * Also check the **work mode**. If it says **Privacy mode**, tracking is paused on purpose. Click Move to Work mode. --- ### Level 4: Display type, Wayland and data sync Reach here only if it’s installed, running, and logged in, but data is still thin or missing. **Ubuntu display and Wayland** * Some Ubuntu machines use **Wayland**. On those, after install the user must **log out of Ubuntu and log back in** once to activate window tracking. * Check which display server is in use (Terminal): ``` echo $XDG_SESSION_TYPE ``` Prints wayland or x11. * Wayland window-title tracking needs **GNOME 45–48**. Check the version: ``` gnome-shell --version ``` * On older GNOME (for example Ubuntu 22.04 with GNOME 42), Wayland tracking is limited. Write to support@flowace.ai. * Confirm the tracking helper extension is present: ``` ls ~/.local/share/gnome-shell/extensions/ | grep -i flowace ``` **Confirm data is syncing** * Leave the computer on and in use for about 5 minutes. * Open your Flowace dashboard and find the user. * You should see fresh activity and screenshots arriving. * Still nothing after 5 minutes? Re-check the login and permissions, then move to Advanced. --- ### Advanced: logs, restart, reinstall and support When the basic levels didn’t fix it. Share the log output with support when you write in. **Read the logs** Use the **Report Issue** option in the Flowace menu-bar menu. It uploads the logs for you. **Force a restart** ``` systemctl --user restart flowace-monitor ``` * When in doubt, reboot the computer. The app is set to start automatically on boot. **Reinstall (last resort)** Uninstall first, then run the install again from the Installation Guide. Run f**lowace_linux_uninstall_script.sh** (as the normal user). **When to write to support** Write to support@flowace.ai with the logs, your workspace address and the Ubuntu version if: * Data still doesn’t appear after login and the checks above pass. * The install or uninstall command errors out and re-running doesn’t help. * The machine is on an older or unsupported Ubuntu / GNOME version. --- ### Reading command output: what good and bad look like Match what you see to the examples. **Copy a command, paste it into the Terminal app, press Enter.** A line starting with $ is what you type. The lines under it are what the computer prints back. **Is it installed?** ``` $ ls -l ~/.local/flowace/Flowace-x86_64.AppImage ``` A line that starts with -rwx means it’s installed and runnable. The x means executable. ``` $ ls -l ~/.local/flowace/Flowace-x86_64.AppImagels: cannot access …: No such file or directory ``` **Not good:** It’s not installed. If the file exists but has no x (it shows -rw-r--r--), make it runnable: ``` chmod +x ~/.local/flowace/Flowace-x86_64.AppImage ``` **Is it running?** For **ps aux | grep -i flowace**, the first line mentioning Flowace means it’s **running**. Ignore the last line, which is just your search command showing itself. If only the grep line shows, it’s **not running**. For **systemctl --user status flowace-monitor, active** means good. **inactive (dead)** means it’s stopped. Restart it (see Advanced). “Unit … could not be found” means it’s not installed. Press q to exit the screen. **Display type and GNOME version** ``` $ echo $XDG_SESSION_TYPE wayland ``` This machine uses **Wayland**. The “log out and back in once” step is required, and it needs GNOME 45–48. If it prints x11, no Wayland steps are needed. ``` $ gnome-shell --version GNOME Shell 46.0 ``` **Good:** 46 is within 45–48, so Wayland tracking works. Below 45 (for example 42.x) it’s limited. Write to support. --- ### FAQs * **Why is no data showing even though the app is running?** Check the app is logged in. If you see the login screen, the user is logged out. Also check it isn’t in Privacy mode. * **What does Privacy mode do?** Tracking is paused on purpose. Click Move to Work mode. * **How long until data shows after a fix?** Leave the computer on and in use for about 5 minutes, then check your Flowace dashboard. * **What should I send to support?** The logs, your workspace address and the Ubuntu version. --- ### Related articles * [Troubleshooting on Linux/Ubuntu](https://help.flowace.ai/en/article/troubleshooting-flowace-on-ubuntu-1xbmt3n/) **Need more help?** Reach out to and our team will be happy to assist. --- © Flowace Technologies Pvt Ltd | flowace.ai