I have to assume a lot upfront since steam does the heavy lifting of figuring out what software is mandatory.
# Assumed you have protontricks installed
# Assumed you have steam installed
# Assumed you have command and conquer zero hour installed with english language
# Assumed you have started command and conquer at least once before
# installing generals online
# Assumed you want to install generals online
# Assumed you've downloaded the GeneralsOnline.exe from
# ref: https://www.playgenerals.online/
protontricks-launch --appid 2732960 "/path/to/the/GeneralsOnline_setup_*.exe"
# Choose "/path/to/steam/steamapps/common/Command & Conquer Generals - Zero Hour/Generals.exe"
# Assumed you want to start your game with mangohud
mangohud protontricks-launch --appid 2732960 "/path/to/steam/steamapps/common/Command & Conquer Generals - Zero Hour/GeneralsOnlineZH.exe"
# Click on Multiplayer->Online and login via steam
That's it. Enjoy it and see you on the battlefield commander!
I am not an heavy user of the nextcloud polls application, so this issue could be an oldie but goldie.
I am working on a nextcloud version 30.0.5.1 and I wanted to create a poll.
First discovery, all polls are gone and I was not able to configure anything Preference section. A tail on the nextcloud.log told me that apps/polls/lib/Controller/PollController.php is producing a unknown config key log entry.
Long story short, this link from the closed issue/3806 pointed me to the right direct.
Logged in as admin, I've opened the settings/admin/polls and disabled and enabled the Enable the poll creation globally option. After that and a page reload as a user, almost all is working fine. There is only one open issue with the "copy link to clipboard" option :-.
My first solution is a fix for my all actors in one worker.
The fix here was to remove the dramatiq setup call from within each actor and to centralize it in the one worker file before importing the actors per context.
My second solution is a fix for my one worker per context.
The fix here was to add a state to the dramatiq setup to prevent creating brokers instances after broker instances.
With my code, you are now able to create python project that uses dramatiq and has multiple actors defined in multiple worker files.
Sounds simple but took me more than an week. Hope it prevents at least one to waste that time!