rizinorg/cutter

Cutter doesn't save settings if first run has binary from terminal

Open

#3,080 opened on Jan 11, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (14,852 stars) (1,123 forks)batch import
good first issue

Description

Environment information

  • Operating System: Parrot 5.1.2
  • Cutter version: 2.1.2
  • Obtained from:
    • Built from source
    • Downloaded release from Cutter website or GitHub
    • Distribution repository
  • File format: ELF

Describe the bug

When first run of Cutter has a binary to analysis, it won't show the first init widget to save settings like themes. Therefore, some settings are not saved

To Reproduce

  1. Install Cutter from repository (no pre-config settings were written) sudo apt install rizin-cutter (the name is on Parrot's repository. It could be different on other distro)
  2. Open Cutter to analysis a binary cutter /usr/bin/ls
  3. Use Cutter normally, change theme settings, ... (let say that user changed theme to dark theme)
  4. Open Cutter without any binary files from args
  5. Cutter will have the first run widget which asks themes and the other settings. The theme is light.

If user runs Cutter with a binary file in step 4, the theme setting won't be changed. Theme will be light theme

Expected behavior

Settings should be saved and maybe the first run widget will not show

Contributor guide

Tech stack
cpp
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C++Qt framework basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Examine the startup code in Cutter's main entry point (e.g., main.cpp or CutterApplication.cpp). Look for the condition that shows the first run settings widget. Determine why the widget does not appear when a binary is passed as an argument, causing settings not to be saved. Check if settings are loaded/saved properly in that scenario. Potential fix could involve ensuring settings are initialized regardless of command line arguments.