Lenvo P16 G1 Nvidia RTX A3000
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- linux
- Domain
- desktop-dev, operating-systems
Research direction
Start by reproducing the black screen during the experimental Wayland login on the Lenovo P16 G1 with an Nvidia RTX A3000 and dual monitors. Review the Wayland login behavior and Nvidia X Server Settings, then collect the missing logs or crash report. Done means reaching the desktop environment without the black screens.
Written by the indexing model from the issue text.
Description
Describe the bug
Running an Lenvo P16 G1 Nvidia RTX A3000 login with Wayland experimental.
I get an black screen when running the experimental setting on login.
I am able to log in via terminal.
I use dual Monitors.
It is an brand new installation full updated.
I have Installed Nvidia x server settings.
Screenshots
If applicable, add screenshots to help explain your problem, you can just drag & drop them here.
The screen dump is like
_
on the top left corner on both screens.
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
A clear and concise description of what you expected to happen.
I Expected that I would be login to the Desktop Environment.
Distribution:
- [x ] Linux Mint
- LMDE
- Other (please specify)
Software version:
Logs:
Crash report:
I do not know ware the crash report for Wayland is on the system.
Additional context
Locale:
- Dominant language
- Python
- Stars
- 425
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/mintupdate
-
BUG
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
linuxmint/mintupdate#1089 ·
-
BUG
Difficulty 1/5 Under an hour Newbie friendliness 88/100
linuxmint/mintupdate#1062 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
linuxmint/mintupdate#1041 · 1 comment ·
-
FEATURE REQUEST
Difficulty 1/5 Under an hour Newbie friendliness 65/100
linuxmint/mintupdate#910 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
linuxmint/mintupdate#903 ·
All issues in linuxmint/mintupdate
Similar issues
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31098 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
john-kurkowski/tldextract#382 ·
-
comp/tools duplicate P2 sweeper:risk-compatibility tool/mcp type/bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NousResearch/hermes-agent#132042 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
deepset-ai/haystack#13092 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
feder-cr/invisible_playwright_mcp#1408 ·
Maintainers usually reply within 1 day