Bug 1177602 - HDMI display only allows 640x480
HDMI display only allows 640x480
Status: RESOLVED DUPLICATE of bug 1177618
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma)
64bit openSUSE Tumbleweed
: P5 - None : Critical (vote)
: ---
Assigned To: E-Mail List
E-mail List
Depends on:
  Show dependency treegraph
Reported: 2020-10-12 19:39 UTC by teo teo
Modified: 2020-10-14 05:56 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Note You need to log in before you can comment on or make changes to this bug.
Description teo teo 2020-10-12 19:39:29 UTC
I have an external monitor that I connect via HDMI.

It has a high resolution, like 1900x1080, now I don't remember exactly.

When I connect it to my new laptop with freshly installed Tumbleweed, it only allows me to select a shitty 640x480 resolution.

I have used the same display on Ubuntu on an older laptop for ages, and I have never had this issue (also, never with other screens). With Ubuntu on the old laptop, regardless of whether I connected it via HDMI or VGA, it always worked fine.

On the new laptop with OpenSUSE I only have HDMI, so I cannot try VGA.

So now I cannot use my external high-resolution monitor.

Thanks a lot, OpenSUSE!

I need a workaround URGENTLY.
Comment 1 Fabian Vogt 2020-10-12 20:06:39 UTC
Sounds like the proprietary nvidia driver.

What's the output of "xrandr"?
Try restarting X with Ctrl-Alt-Bksp+Bksp.
Comment 2 Wolfgang Bauer 2020-10-13 10:57:33 UTC
It seems the reporter opened a new bug, because:
> I already reported this bug, I got a reply asking for more info,
> but the link to the bug no longer works, the bug report has vanished.

See bug#1177618.

I suppose we can close this one then?
Comment 3 Wolfgang Bauer 2020-10-13 10:59:41 UTC
(In reply to Wolfgang Bauer from comment #2)
> See bug#1177618.
The xrandr output there shows 640x480 as only available resolution, so it can't really be a bug in Plasma anyway.
Comment 4 Wolfgang Bauer 2020-10-14 05:56:17 UTC
I think it's best to mark this as a duplicate.
It seems to be rather unlikely that we ever get a response here...

*** This bug has been marked as a duplicate of bug 1177618 ***