Operating system
Linux
System version
Linux Mint 22.2 (Ubuntu 24.04 base)
Installation type
deb
Version
Throne-1.2.4-debian-amd64-system-qt.deb
Description
Description of the Bug
In Throne v1.2.4 (system-qt build) on Linux, when switching from one active profile to another in Tun Mode using the developer-recommended sequence, the "Tun device misbehaving" dialog appears because the TUN interface is temporarily busy. Inside this dialog, clicking the "Reset" button does absolutely nothing and fails to restart the Core process.
Currently, the Core can only be successfully restarted using one of these two workarounds:
- System tray icon context menu -> "Restart Core".
- Top-left application menu -> Program -> Restart Core.
The button inside the error dialog itself appears to be completely broken or disconnected from the restart routine.
Reproduction
- Start any initial profile first (with Tun Mode unchecked).
- Check the Tun Mode checkbox to route traffic (starts successfully as recommended).
- Try to switch directly to another profile while Tun Mode is active.
- The "Tun device misbehaving" window pops up with a
device or resource busy error.
- Click the "Reset" button inside that window.
- Notice that the Core process does not restart, and the error persists until you manually use the top menu or tray options.
Expected Behavior
Clicking the "Reset" button inside the error popup should trigger the exact same function as Program -> Restart Core to clear the stuck interface and allow the new profile to start.
Logs
Starting profile [WireGuard] 🇸🇪 WARP - 2
ERROR[0000] dns/underlying[dns-local]: No default interface
INFO[0000] network: updated default interface enp2s0, index 2
INFO[0000] dns/underlying[dns-local]: underlying dns set to 1.1.1.1:53
INFO[0000] inbound/direct[dns-in]: tcp server started at 127.0.0.1:5533
INFO[0000] inbound/direct[dns-in]: udp server started at 127.0.0.1:5533
INFO[0000] inbound/mixed[mixed-in]: tcp server started at 127.0.0.1:2080
<<<<<<<< Failed to start profile [WireGuard] 🇸🇪 WARP - 2
Operating system
Linux
System version
Linux Mint 22.2 (Ubuntu 24.04 base)
Installation type
deb
Version
Throne-1.2.4-debian-amd64-system-qt.deb
Description
Description of the Bug
In Throne v1.2.4 (system-qt build) on Linux, when switching from one active profile to another in Tun Mode using the developer-recommended sequence, the "Tun device misbehaving" dialog appears because the TUN interface is temporarily busy. Inside this dialog, clicking the "Reset" button does absolutely nothing and fails to restart the Core process.
Currently, the Core can only be successfully restarted using one of these two workarounds:
The button inside the error dialog itself appears to be completely broken or disconnected from the restart routine.
Reproduction
device or resource busyerror.Expected Behavior
Clicking the "Reset" button inside the error popup should trigger the exact same function as Program -> Restart Core to clear the stuck interface and allow the new profile to start.
Logs