Game: Steam Deck Gaming mode crash report has no game log #1259
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1259
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reported on Discord
Version and channel
Longshot v3.0.0-rc.5 (release candidate).
System
Steam Deck LCD, SteamOS 3.9.5.
Steps and actual behavior
In Gaming mode, launch Longshot from a non-Steam-game shortcut. It crashes and a crash report is created, but
logs/longshot_log.txtis missing. In Desktop mode, launchingbin/longshotcreates logs as expected.Expected behavior
The game log should be present when the crash report is created, as it is in Desktop mode.
Still needed
logs/longshot_log.txt.Related but different: Longshot#1059 concerns Linux log handling after a restart, not missing logs on a Gaming-mode crash.
Updated with more from Discord: Added exact Longshot version/channel and confirmed gaming-mode launch method, crash report creation, and desktop-mode comparison.