FruityLoops FLStudio flstudio 26 Verification Error SHA256

Open
#491 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
desktop

Research direction

Start with the FLStudio26 entry in the BottlesManifest and compare its download URL and checksum with the Image-Line installer for version 26.1.4.5589. Confirm the manifest’s installer verification succeeds and that the FL Studio 26 installation completes without the reported verification error.

Written by the indexing model from the issue text.

Description

I use Linux Nobara KDE NV 2weeks now and its amazing and it works better then Windows with everything I personally need. The only issue i have, is to open the latest FL Studio Application that works. I downloaded the FLStudio25App in bottles and it updated it without any Problem (Version 26.1.3.5570). After a Fix or new available update from ImageLine 26.1.4.5589 my FLStudio has an verification error and i can´t open it no matter which dependencies i change use analyse .... now i came to the conclusion that the checksum and the downloadlink in the BottlesManifest for FLStudio isn´t the same as the DownloadApp from the ImageLine homepage so PLS WINE or Bottles or who is in charge of this great systems CHANGE THE THINGS U HAVE TO CHANGE SO WE CAN HAVE THE LATEST FLSTUDIO APP!!! I made one Manifest but am knowing nothing about Manifests or everythings going on or to change manifests (2Week in the LinuxGame) i tried my best.

Name: flstudio26
Description: FL Studio 26 Custom Installer
Grade: Gold
Arch: win64

Dependencies:

  • allfonts
  • webview2

Parameters:
dxvk: true
sync: esync

Executable:
name: FL Studio 26
icon: flstudio.png
file: FL64.exe
path: Program Files/Image-Line/FL Studio 26/FL64.exe
arguments: ""

Steps:

Dominant language
No language data
Stars
111
Forks
93
Avg merge
1d 1h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bottlesdevs/programs

All issues in bottlesdevs/programs

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.