Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix this bug show after change login [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#26552•Fetched 2026-05-06 06:35:35
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
dev-frogdev-frog
Participants
dev-frogdev-froggemini-cli[bot]gemini-cli[bot]
Timeline (top)
commented ×1labeled ×1

Error Message

│ This is an unexpected error. Please file a bug report using the /bug tool. █│ │ Reason: Error: ENAMETOOLONG: name too long, lstat '/Users/frog/code/github/frog/perthclean/cleanerco.com.au">[email protected]</a></p> </div> <div class="schema-faq-section" █│ │ Error: ENAMETOOLONG: name too long, lstat '/Users/frog/code/github/frog/perthclean/cleanerco.com.au">[email protected]</a></p> </div> <div class="schema-faq-section" █│

RAW_BUFFERClick to expand / collapse

What happened?

[STARTUP] Phase 'load_builtin_commands' was started but never ended. Skipping metrics. █│ │ ℹ Authenticated via "oauth-personal". █│ │ ✖ ========================================= █│ │ This is an unexpected error. Please file a bug report using the /bug tool. █│ │ CRITICAL: Unhandled Promise Rejection! █│ │ ========================================= █│ │ Reason: Error: ENAMETOOLONG: name too long, lstat '/Users/frog/code/github/frog/perthclean/cleanerco.com.au">[email protected]</a></p> </div> <div class="schema-faq-section" █│ │ id="faq-question-1707139607755"><strong class="schema-faq-question">How do I cancel the service?</strong> <p class="schema-faq-answer">Please contact us via email, phone or text to cancel. We will accept█│ │ cancellations up to 24 hours before the service without any fees incurred. A cancellation fee will incur if the job is scheduled to start within the 24 hours.</p> </div> <div class="schema-faq-section" █│ │ id="faq-question-1707139628473"><strong class="schema-faq-question">Are you open on the weekend?</strong> <p class="schema-faq-answer">Yes, we are open both Saturday and Sunday</p> </div> <div █│ │ class="schema-faq-section" id="faq-question-1707139647145"><strong class="schema-faq-question">What are your opening hours?</strong> <p class="schema-faq-answer">We operate everyday 6am to 9pm, including█│ │ weekends.</p> </div> <div class="schema-faq-section" id="faq-question-1707139669325"><strong class="schema-faq-question">How do I contact you?</strong> <p class="schema-faq-answer">Please contact our █│ │ office via email, phone or text (7am – 6pm)<br>Phone/text: <a href="tel:1300' █│ │ Stack trace: █│ │ Error: ENAMETOOLONG: name too long, lstat '/Users/frog/code/github/frog/perthclean/cleanerco.com.au">[email protected]</a></p> </div> <div class="schema-faq-section" █│ │ id="faq-question-1707139607755"><strong class="schema-faq-question">How do I cancel the service?</strong> <p class="schema-faq-answer">Please contact us via email, phone or text to cancel. We will accept█│ │ cancellations up to 24 hours before the service without any fees incurred. A cancellation fee will incur if the job is scheduled to start within the 24 hours.</p> </div> <div class="schema-faq-section" █│ │ id="faq-question-1707139628473"><strong class="schema-faq-question">Are you open on the weekend?</strong> <p class="schema-faq-answer">Yes, we are open both Saturday and Sunday</p> </div> <div █│ │ class="schema-faq-section" id="faq-question-1707139647145"><strong class="schema-faq-question">What are your opening hours?</strong> <p class="schema-faq-answer">We operate everyday 6am to 9pm, including█│ │ weekends.</p> </div> <div class="schema-faq-section" id="faq-question-1707139669325"><strong class="schema-faq-question">How do I contact you?</strong> <p class="schema-faq-answer">Please contact our █│ │ office via email, phone or text (7am – 6pm)<br>Phone/text: <a href="tel:1300' █│ │ at Module.lstatSync (node:fs:1686:25) █│ │ at robustRealpath (file:///opt/homebrew/Cellar/gemini-cli/0.38.1/libexec/lib/node_modules/@google/gemini-cli/bundle/chunk-ETUADTWF.js:41909:27) █│ │ at resolveToRealPath (file:///opt/homebrew/Cellar/gemini-cli/0.38.1/libexec/lib/node_modules/@google/gemini-cli/bundle/chunk-ETUADTWF.js:41896:10) █│ │ at checkPermissions (file:///opt/homebrew/Cellar/gemini-cli/0.38.1/libexec/lib/node_modules/@google/gemini-cli/bundle/chunk-C3HWPYQ6.js:60877:30) █│ │ at file:///opt/homebrew/Cellar/gemini-cli/0.38.1/libexec/lib/node_modules/@google/gemini-cli/bundle/interactiveCli-EOCVNM6H.js:48651:37 █│ │ at file:///opt/homebrew/Cellar/gemini-cli/0.38.1/libexec/lib/node_modules/@google/gemini-cli/bundle/interactiveCli-EOCVNM6H.js:37035:7 █│ │ at Object.handleSubmit (file:///opt/homebrew/Cellar/gemini-cli/0.38.1/libexec/lib/node_modules/@google/gemini-cli/bundle/interactiveCli-EOCVNM6H.js:34562:9) █│ │ at file:///opt/homebrew/Cellar/gemini-cli/0.38.1/libexec/lib/node_modules/@google/gemini-cli/bundle/interactiveCli-EOCVNM6H.js:37084:20 █│ │ at file:///opt/homebrew/Cellar/gemini-cli/0.38.1/libexec/lib/node_modules/@google/gemini-cli/bundle/interactiveCli-EOCVNM6H.js:37623:13 █│ │ at file:///opt/homebrew/Cellar/gemini-cli/0.38.1/libexec/lib/node_modules/@google/gemini-cli/bundle/chunk-C3HWPYQ6.js:51170:15

What did you expect to happen?

Debug Console (F12 to close) │ │ │ │ ℹ Loaded cached credentials. │ │ │ │ ℹ Detected terminal background color: #1e1e2e │ │ │ │ ℹ Detected terminal name: tmux 3.5a

Client information

  • CLI Version: 0.38.1
  • Git Commit: 7f5580034
  • Session ID: e97b304f-4b12-4a0c-ba77-f97b85dd1b4d
  • Operating System: darwin v25.9.0
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3-flash-preview
  • Auth Type: oauth-personal
  • Memory Usage: 431.8 MB
  • Terminal Name: tmux 3.5a
  • Terminal Background: #1e1e2e
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The error ENAMETOOLONG: name too long suggests that a file path exceeds the maximum allowed length, causing the lstatSync function to fail.

Guidance

  1. Verify file path length: Check the file path /Users/frog/code/github/frog/perthclean/cleanerco.com.au">[email protected] for excessive length.
  2. Remove unnecessary characters: The file path appears to contain HTML tags and unnecessary characters, which may be contributing to the error.
  3. Use a shorter file path: Consider shortening the file path or using a symbolic link to reduce its length.
  4. Check for encoding issues: Ensure that the file path is properly encoded to avoid any character encoding issues.

Example

No code snippet is provided as the issue seems to be related to file path length rather than code syntax.

Notes

The error message indicates a problem with the file path length, but the provided stack trace and client information do not offer a clear solution. Further investigation into the file system and path handling is necessary.

Recommendation

Apply a workaround by shortening the file path or using a symbolic link to reduce its length, as the error is likely caused by the excessive length of the file path.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#indexing error#inference speed#output truncation#response parsing#generation error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING