On 16/6/21 10:25, Samuel Sieb wrote:
On 2021-06-15 4:58 p.m., Stephen Morris wrote:
On 15/6/21 23:42, Ed Greshko wrote:
On 15/06/2021 20:36, Stephen Morris wrote:
Just as a side issue to this, when I was searching on the net for
information on video resizing, I found an entry for a person
raising an issue with video resizing in KDE on Wayland in F34. One
of the responses in the issue said that KDE on Wayland was not
stable. I remember that in F33 you mentioned to me that KDE on
Wayland was not stable, hence is that still the case in F34?
I don't know if I ever used the phrase "not stable" as "stable"
would need to be defined to be more specific.
Anyway, I've tried Plasma on Wayland with the current nVidia
drivers. It is OK, but should get better when the nVidia
driver are updated. I tried this not long after F34 was released
but I didn't take notes. Except for the clipboard issues
I don't recall what else was bothersome to me.
I would follow https://community.kde.org/Plasma/Wayland_Showstoppers
and check and see if anything there is a
showstopper for you.
I haven't read that article yet, but the thing that is a show stopper
for me is that with both Gnome and Plasma is that Wayland will not
scale above 2560x1600, which was the maximum resolution reported by
xrandr until I put in the xorg modelines. The article I found about
Wayland not being ready with Plasma yet, also mention a video config
file that Wayland uses and when I looked at that it listed all the
same resolutions as those reported by xrandr under both Xorg and
Wayland.
Something to keep in mind is that "Wayland" is a protocol. Each
provider implements it independently although I believe there is a
common helper library. When I tested F34 Gnome under qemu, it offered
resolutions up to 5120x2160. I included a screenshot of that in an
earlier email. If you're still talking about running it under vmware,
then that's where the problem is. Vmware isn't providing the
resolutions you want.
What I'm trying to figure out how to determine is, is the issue vmware,
or its it the driver which may be supplied by Fedora or vmware (I'm not
entirely sure which), or is it the monitor not honouring the EDID requests?
regards,
Steve
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
