[Bug]: Cannot submit bug report and functions not working

[Prog-Tsunmi]

What happened?

A bug happened!

Every single function in my lantern is not working, it's saying that a error has occured, I tried clearing the settings configuration but it dosen't work

lantern_macos.log
lantern-crash.log
lantern.log
lantern-app.log
flutter.log

Version

9.1.17 build 705

Which platform(s) does this affect?

• Android
• iOS
• Desktop (Windows)
• Desktop (MacOS)
• Desktop (Linux)

Related Support Tickets

No response

[DelaLantern]

Thanks for flagging this - I have surfaced your logs to our engineering team.

[Monsieur-Nico]

Took a look at the attached logs, might save some time narrowing this down.

flutter.log shows every backend call failing the same way throughout the session — fetching plans, routing mode, split-tunnel settings, telemetry, and the "report issue" call itself — all return:

PlatformException(..., ipc: status 403: permission denied, Error Domain=go Code=1 ...)

So the "cannot submit bug report" symptom looks like the same failure as everything else, not a separate bug.

That 403 traces to the local IPC server in getlantern/radiance. Every call is gated behind peerCanAccess/isAdmin in ipc/middlewares.go:

func peerCanAccess(peer usr) bool {
    return peer.isAdmin
}

On macOS/Linux, isAdmin is resolved in ipc/usr.go by shelling out non-interactively to:

exec.CommandContext(ctx, "sudo", "--other-user="+usr, "--list", executable).Run()

By contrast, the Windows path (ipc/usr_windows.go) just checks membership in WinBuiltinAdministratorsSid — a static, direct check. The macOS sudo --list shell-out seems like a much more fragile way to determine admin status and is a plausible source of the pervasive 403s here, though I haven't confirmed the exact trigger (e.g. what user/context the IPC server process itself runs as).

Separately, and likely unrelated to the above: lantern_macos.log shows repeated system-extension activation failures because the app is running from ~/Desktop / ~/Applications rather than /Applications:

error=App containing System Extension to be activated must be in /Applications folder

macOS requires system extensions to launch from /Applications, so worth having the reporter move the app there as a separate check.

Happy to dig further into the canSudo behavior or put together a PR mirroring the Windows admin-group check if that'd be useful.