lmstudio-ai / lmstudio-ai/lmstudio-bug-tracker

gpu survey unsuccessful

Open
#643 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
152
Forks
38
PR merge metrics
No merged PRs in 30d

Description

LM Studio 0.3.15
under latest linux mint, everything is up to date
fails to detect my gpu (laptop rtx4060)
i deleted the .lmstudio folder because lmstudio was failing to detect my gpu after downloading and using the latest version and found in one of the issues from february that this could solve the problem
now i : lost all my models and chat that was working before (i was aware of this, but still went forward in hopes that i could actually use lmstudio)

error snippet when searching:

RPC handler: TypeError: fetch failed
at node:internal/deps/undici/undici:13185:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async _0x1ca865 (/tmp/.mount_LM-StuXW8Kh4/resources/app/.webpack/main/index.js:1:68902)
at async _0x5454ff..search (/tmp/.mount_LM-StuXW8Kh4/resources/app/.webpack/main/index.js:370:31183)
at async _0x20ac7c.quickSearchOne (/tmp/.mount_LM-StuXW8Kh4/resources/app/.webpack/main/index.js:373:8746)
at async Object.handler (/tmp/.mount_LM-StuXW8Kh4/resources/app/.webpack/main/index.js:223:57320)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing LM Studio 0.3.15 on latest Linux Mint with the laptop RTX 4060 and inspect the RPC handler failure shown in resources/app/.webpack/main/index.js. Compare GPU survey and search behavior before and after the .lmstudio reset; done means the GPU is detected without requiring deletion of user data and the reported RPC error is understood or resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.