Announcement

Collapse
No announcement yet.

KDE Plasma 6.0 Ready For Release Next Week, Plasma 6.1 Seeing Early Feature Work

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ahjolinna
    replied
    Originally posted by V1tol View Post

    It is pointless for SMPlayer to migrate to Qt6 because it uses X11 embedding to spawn mpv process and display video inside its window. So simply saying, it works under XWayland. After long search I switched to QMPlay2 which uses libmpv directly and works perfectly under Wayland with Vulkan backend and stuff.
    I have been using Media Player Classic Qute Theater ("Mpc-Qt") for years, which uses libmpv also and has now Qt6 port done https://mpc-qt.github.io/

    Leave a comment:


  • user1
    replied
    Originally posted by hf_139 View Post
    Yes, "i don't use it", as every GNOMie says.
    It's flawless when you are on decade old hardware and "just don't use" things that everybody in the modern world with 4k screen considers as basic.
    If I had a higher resolution monitor, of course I would've probably wanted to use fractional scaling. I don't know what kind of a rock you live under, but 1080p monitor is not "decade old hardware". It's still the most widely used resolution and 1080p monitors are still being manufactured.

    Originally posted by hf_139 View Post
    The problem with that mindset is that you imply that it is ready for use. Ready to be shipped. Ready for everyone to use. Even if it is clearly not, because it is missing crucial things that everybody expects from modern software..
    I thought I also mentioned why Chromium's Wayland support is not completely flawless in my last comment, so how exactly do I imply that it is ready for use? It also should be obvious for everyone that Chromium Wayland is still not enabled by default for a good reason.

    Btw, you're wrong to think that Gnome users generally have "low standards" and are happy with everything that Gnome gives them on the plate. It's exactly why me and others have recently moved to KDE.

    Your claim about 1080p monitors has actually reminded me of a similar claim some Gnome dev has made. When they removed subpixel font antialiasing in GTK 4.0 (which is useful for lower resolutions like 1080p), their reasoning was that non HiDPi monitors are outdated.
    Last edited by user1; 24 February 2024, 12:27 PM.

    Leave a comment:


  • Jaxad0127
    replied
    Originally posted by DumbFsck View Post
    I say it is a pet peeve of mine because it is the stupidest thing ever. So I make a point to point it out as often as I can.
    Sounds like an attempt to avoid iPhone becoming generic and Apple loosing their trademark.

    Leave a comment:


  • hf_139
    replied
    Originally posted by user1 View Post

    Well, I don't use fractional scaling, because I have a 1080p monitor. I know that Chromium's Wayland support is still not completely flawless (for example VAAPI still probably doesn't work), but overally it was very stable on Gnome for the last 2.5 years. Since I currently use KDE, that's why I asked what exactly is wrong with Chromium on Plasma 6 Wayland.
    Yes, "i don't use it", as every GNOMie says.
    It's flawless when you are on decade old hardware and "just don't use" things that everybody in the modern world with 4k screen considers as basic.

    The problem with that mindset is that you imply that it is ready for use. Ready to be shipped. Ready for everyone to use. Even if it is clearly not, because it is missing crucial things that everybody expects from modern software.
    Last edited by hf_139; 24 February 2024, 11:18 AM.

    Leave a comment:


  • ngraham
    replied
    Nobody says "an iPhone phone", it sounds awkward. So that's why I don't write that--same reason why I don't omit the article before "iPhone". That sounds awkward too.

    Leave a comment:


  • DumbFsck
    replied
    ngrahamthere's sort of a typo and pet peeve of mine in the first item under bug fixes.

    According to Phill Schiller you shouldn't write "an iPhone", it should be just "iPhone". You can still use the "an" if after what apple people consider a proper noun you write the category they belong to.

    So the correct way of writing that should be "an iPhone phone".

    I say it is a pet peeve of mine because it is the stupidest thing ever. So I make a point to point it out as often as I can.

    For example, up until recently I always had two iPhone phones. I always pluralised it "correctly", saying stuff like "two iPhone phones" or "my iPhone phones" every time. It is absolutely ugly and dumb.

    Being ex-apple I expected the same from nate.

    Leave a comment:


  • gbcox
    replied
    Originally posted by V1tol View Post

    It is pointless for SMPlayer to migrate to Qt6 because it uses X11 embedding to spawn mpv process and display video inside its window. So simply saying, it works under XWayland. After long search I switched to QMPlay2 which uses libmpv directly and works perfectly under Wayland with Vulkan backend and stuff.
    Yes, I've switched to QMPlay2 also.

    Leave a comment:


  • user1
    replied
    Originally posted by hf_139 View Post

    Chromium has never been working flawlessly on wayland.

    Just one example: One year ago they released support for fractional scaling of wayland and it got reverted one day after the release again, because it broke wayland. Turned out that nobody ever tested it.
    But for a GNOME user it might be enough, because GNOME hides its fractional scaling controls and GTK doesn't support wayland fractional scaling yet.
    Well, I don't use fractional scaling, because I have a 1080p monitor. I know that Chromium's Wayland support is still not completely flawless (for example VAAPI still probably doesn't work), but overally it was very stable on Gnome for the last 2.5 years. Since I currently use KDE, that's why I asked what exactly is wrong with Chromium on Plasma 6 Wayland.

    Leave a comment:


  • hf_139
    replied
    Originally posted by user1 View Post

    This sounds a bit concerning, because Chromium based browsers (with native Wayland flag enabled) have been working flawlessly on Gnome for about 2.5 years already. What exactly doesn't work well in Chromium Wayland on Plasma 6?
    Chromium has never been working flawlessly on wayland.

    Just one example: One year ago they released support for fractional scaling of wayland and it got reverted one day after the release again, because it broke wayland. Turned out that nobody ever tested it.
    But for a GNOME user it might be enough, because GNOME hides its fractional scaling controls and GTK doesn't support wayland fractional scaling yet.

    Leave a comment:


  • user1
    replied
    Originally posted by FireBurn View Post
    I've been running KDE 6 from git since the beta, can't believe how much better the wayland experience is compared to Plasma 5, the last few niggles lie with Chromium not working well under wayland
    This sounds a bit concerning, because Chromium based browsers (with native Wayland flag enabled) have been working flawlessly for me on Gnome for about 2.5 years already. What exactly doesn't work well in Chromium Wayland on Plasma 6?
    Last edited by user1; 24 February 2024, 12:02 PM.

    Leave a comment:

Working...
X