Fmstrat / Fmstrat/winapps

Amazingly bugged as hell application

Open
#209 8 comments 2 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
10.3k
Forks
452
PR merge metrics
No merged PRs in 30d

Description

I tried this app and almost broke my entire linux session: this is a terribly deadly software for your linux session, believe me you will need switch to TTY1 (GDM) then TTY2 (GNOME):
- When you run the software for the first time you need to inject a crazy complicated registry key otherwise it will fail with a shady error message
- Make sure to have your VirtualBox vm user locked otherwise, well you will break your entire session and you must go into TTY3 access processes and force terminate the freerdp garbage
- Now you can run install check which will totally break your entire display and will give you two buttons, click Yes, No will simply quit software
- Normally you're back on GNOME with two windows file explorers, looks nice until you realize that most input events are broken: dash to dock no longer works, input events are processed by incorrect applications and if you move one explorer to screen #2 then this explorer is dead (no more interaction possible you just have to process kill freerdp again)

I think these huge bugs should be mentioned in the README. I do not expect to have to switch to a TTY3 in order to process kill a broken app that breaks your entire session.

Here is my hardware config if you'd like to try to debug these huge bugs:

Host:
- Intel Core i7 4th generation 3.7 GHz 4 cores 8 threads
- 24Gb RAM
- NVIDIA GTX 650 Ti DirectCU 2 2GB VRAM

Guest:
- 2 cores allocated
- Win10 Pro x64
- 8Gb RAM
- No 3D

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the README and the first-run/install-check flow described in the report, then reproduce the failures on the listed Linux/GNOME setup while observing the freerdp process. Done means the reported session, input, display, and multi-screen failures are isolated or clearly documented with reliable reproduction steps and expected behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, shell
Domain
desktop-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.