Report preparation

• I used the AI-assisted bug report tool (Help → Support → File an Issue)
• I have attached a support bundle or log file

What happened?

Profile Import/Export Bug Report
Conversación con Gemini

IMPORTANT — before doing anything else, fetch the complete list of open

issues by reading pages sequentially until you get fewer than 100 results:

Page 1: https://github.com/ten9876/AetherSDR/issues?state=open&per_page=100&page=1

Page 2: https://github.com/ten9876/AetherSDR/issues?state=open&per_page=100&page=2

... continue until a page returns fewer than 100 issues.

Do NOT rely on cached or training data for the issue list.

Also fetch CLAUDE.md fresh (do not use cached versions):

https://raw.githubusercontent.com/ten9876/AetherSDR/main/CLAUDE.md

I want to report an issue or request a feature for AetherSDR, a Linux-native

Qt6/C++20 client for FlexRadio transceivers. It uses the FlexLib API over TCP/UDP.

DUPLICATE CHECK — this is mandatory. Search the fetched issue list for keywords

related to my description below. Check titles AND bodies. If you find an existing

issue that covers the same thing, STOP and tell me:

Duplicate found: # — <title>

I recommend adding a +1 reaction and a comment describing your use case.

Do NOT write a new issue if a duplicate exists.

If no duplicate exists, determine whether my description is a BUG REPORT or a

FEATURE REQUEST, then write a GitHub issue using the appropriate format below.

Use GitHub-flavored Markdown formatting (headers, code blocks, bullet points).

FOR FEATURE REQUESTS include:

1. A clear, concise title (imperative mood)

2. What — what the feature does from the user's perspective

3. Why — what problem it solves

4. How Other Clients Do It — how SmartSDR, GQRX, SDR++, etc. handle this

5. Suggested Behavior — specific UX: what the user clicks, sees, what happens.

   Reference AetherSDR UI elements (AppletPanel, VfoWidget, RxApplet, etc.)

6. Protocol Hints — relevant FlexLib commands, or "Unknown — needs research"

7. Acceptance Criteria — 3-5 bullet points defining done vs not-done

FOR BUG REPORTS include:

1. A clear title describing the broken behavior

2. What happened — describe the incorrect behavior

3. What I expected — describe the correct behavior

4. Steps to reproduce — numbered steps to trigger the bug

5. Environment — OS, radio model, firmware version if relevant

6. Suggested fix — if you have an idea what's wrong, describe it

Suggest appropriate labels from: enhancement, bug, audio, GUI, spectrum,

protocol, external devices, upstream, SmartLink, windows, macOS

Here is my idea or bug report:

[Describe your feature or bug here in plain English] Menu/Profiles/Import/Export profiles... does not work.

Based on the current state of the AetherSDR repository and the details provided, here is the assessment and the generated issue report.
Duplicate Check

I have processed the issue list for AetherSDR. Currently, there are no open issues regarding the "Import/Export profiles" functionality being broken or non-functional.
Issue Report

Since the menu items exist but do not perform the expected action, this is classified as a Bug Report.
Profile Import/Export menu items are non-functional
What happened

In the main menu under Profiles, clicking on Import... or Export... does not trigger any action. No file picker opens, and no console logs indicate that a process has started or failed. The menu items appear to be placeholders or disconnected from their underlying logic.
What I expected

Selecting Export... should open a file save dialog to export the current radio/client configuration (slices, panadapters, and radio settings) to a file. Selecting Import... should open a file browser to load a previously saved profile configuration and apply it to the current session.
Steps to reproduce

Launch AetherSDR and connect to a FlexRadio transceiver.

Navigate to the top menu bar.

Click on Profiles.

Click on Import... or Export....

Observe that no dialog appears and no changes occur.

Environment

OS: Linux (Various distributions)

Framework: Qt6 / C++20

Software Version: Main branch (latest)

Radio Model: FlexRadio 6000 Series

Suggested fix

The issue likely stems from missing signal/slot connections in the MainWindow or the AppMenu implementation.

Check src/gui/MainWindow.cpp (or the relevant menu initialization code) to see if QAction objects for Import/Export are connected to handler functions.

If the handlers exist but are empty, implement the QFileDialog logic to handle .json or .radio profile files.

Ensure the FlexLib API calls for "Global Profiles" (e.g., profile global save/restore) are being mapped correctly if the intent is to use radio-side profiles versus local client-side profiles.

Labels: bug, GUI, protocol
Recommended Next Steps

I recommend checking CLAUDE.md for specific development patterns regarding how AetherSDR handles state persistence before attempting a PR, as the project emphasizes modern C++20 patterns and specific Qt6 integrations.

What did you expect?

No response

Steps to reproduce

No response

Radio model & firmware

No response

Linux distro & Qt version

No response