Issues with bottles and Winboat operations
Issues with bottles and Winboat operations
I'm working on MX Linux 25 (Debian 13). I added "mp3tag" using Bottles and it functioned perfectly. Now I can open the app, which modifies MP3 metadata. However, when selecting files, it doesn't display a folder containing my actual Linux directories with MP3s. It seems the program is running inside a container or VM. Do you think this is due to the app being hosted in a virtual environment? Is there a way to access that directory directly? I also tried installing the Windows version of Omnissa Horizon client, but it failed completely. In settings, I changed the Runner from Soda-9.0-1 to sys-wine-10.0, which helped show a black window when running the executable, though no installation appears. I’m unsure about other options or configurations. I also installed Winboat, which claims smooth operation. However, it reported an error saying "Winboat Guest API - Offline" and pointed me to troubleshooting pages. The site indicated it was likely a beta, but I’m curious if it’s stable enough for use. Is this just another VM with similar limitations? How does it differ from a VM with W11? Also, Discover doesn’t list Winboat as installed, even though Bottles does. This raises a concern—could this be a red flag? After some time, the Winboat site changed to look like it was loading Windows in the browser, which let me proceed. But now I’m stuck manually entering the path for the downloaded EXE file.
Mount your MP3 folder in the designated directory. Consider installing via system Wine rather than Bottles.
The mp3 files are located in my Linux home directory. I installed both Wine and WineCharm, but I can't locate Wine itself—it appears in Discover, though. I believe WineCharm acts as a graphical interface for Wine. When I open WineCharm, it opens the mp3 tag and lets me access the files. So the mp3tag issue seems fixed. Thanks. However, when I run the VMWare .exe, it installs many options.
The Linux client isn't working properly after installation attempts. The Proton/Wine setup is failing to complete, likely due to compatibility or configuration issues.
The Linux edition has a single key drawback when compared to Windows: in Windows, the task bar stays fixed and remains visible across all monitors, while in Linux it disappears entirely unless you enable auto-hide. This makes it feel like working directly from the office PC—especially noticeable when remote access is used. Keeping the task bar static limits you to one screen at a time, and the scroll bars appear on the image, not the actual work PC. The only solution I found was to set both monitors' taskbars to auto-hide, which hides them during remote sessions so the work PC appears correctly. This workaround isn’t ideal for daily use, so I explored the Windows version as a possible alternative. It’s possible the issue lies with KDE, and I’m also unsure if the WinBoat method would function properly with two monitors and remote access. Another concern is whether the remote setup might only support Windows versions, which could affect our IT setup. Currently, my approach is to keep Media PCs in Linux as a backup, while maintaining the two desktop PCs on Windows for reliability. The current setup meets 99% of my needs for now, but I’m open to improving it if possible.