3 ms·

What's odd is that detection of headphone jack worked in every distro and DE I've ever used (currently Arch Linux with pulseaudio and Gnome 3 on Wayland) Gnome

What's odd is that detection of headphone jack worked in every distro and DE I've ever used (currently Arch Linux with pulseaudio and Gnome 3 on Wayland) Gnome 3 on Wayland, by the way, was the only one that got fractional scaling right in my tests, with perfectly crisp fonts, after fiddling with gsettings Well, at least for Wayland apps (XWayland gets blurry, unfortunately). I've heard people say that KDE on Xorg is okay, but, it feels a bit blurry still (or maybe it's because it has another default fonts), specially in browsers.

ylyn 5y ago
> What's odd is that detection of headphone jack worked in every distro and DE I've ever used (currently Arch Linux with pulseaudio and Gnome 3 on Wayland) This needs the kernel driver to get it right. It doesn't depend so much on what userspace audio server you use. In the end they all use ALSA.
phendrenad2 5y ago
No offense, but every complaint about something not functioning under Linux gets this exact response. "It worked for me, on my completely different hardware". And this is the core of the problem, two people using the same hardware and experiencing the same problem rarely meet online. Really sells System 76 and other Linux-focused hardware.
- nextaccountic 5y ago
  This is true, sorry. I'm just saying it felt odd because over a number of different computers, a lot of things didn't work right, but this specific thing always did. I didn't even know it could not work right.
- AtlasBarfed 5y ago
  And that's where Intel screwed up. It could have devoted .001% of quarterly revenues to fund ten years of linux hardware compatibility testing and driver development. It would have hedged against Microsoft in numerous ways: business dependence, forcing the hardware utilization Intel always accused Windows of ignoring, probably would have given them a functional beachhead in netbooks, mobile phones, and kept them abreast of other developments like ARM. Google could have also done this for pennies to hedge Microsoft. IBM could have used it to push back into consumer hardware. But the ship has sailed for Google with Android and ChromeOS. IBM is dying. Intel is the only one that is still has some market incentive.
AshamedCaptain 5y ago
To this day wayland does not do fractional scaling. It just blurries individual windows a la macOS. The only toolkit around here that can do actual fractional scaling is Qt. Which is why all gtk based DEs like xfce are at a disadvantage.
- cycomanic 5y ago
  That's not true, fractional scaling works fine both in sway and gnome on wayland. There was an issue with fractional scaling of xwayland windows, which caused blurriness, but I think this has been fixed a while ago (I can't see the blurriness anymore).
  - AshamedCaptain 5y ago
    Gtk does not do fractional scaling at all. It just does integer scaling then relies on the compositor to zoom in/out the window as necessary. This results in blurriness and poor performance. Qt can do true arbitrary fractional scaling, which has other problems.
    - nextaccountic 5y ago
      > Gtk does not do fractional scaling at all. It just does integer scaling then relies on the compositor to zoom in/out the window as necessary. This results in blurriness and poor performance. Are you sure? Maybe you mean on X11? I'm running Gnome on Wayland and with this setting: > gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" I get not blurriness at all. I'm actually kind of paranoid about this issue so can you maybe point me to some online docs describing this issue?
      - AshamedCaptain 5y ago
        This is a toolkit problem, it has nothing to do with wayland or x11. See https://developer.gnome.org/gdk3/stable/gdk3-Windows.html#gdk-window-get-scale-factor https://developer.gnome.org/gdk3/stable/gdk3-Windows.html#gd... , gtk just supports integers as an scaling factor. The mutter setting you are mentioning just enables framebuffer scaling (ie bitmap, http://blog.3v1n0.net/informatica/linux/gnome-fractional-and-multi-monitor-scaling-hackfest-the-report/ http://blog.3v1n0.net/informatica/linux/gnome-fractional-and... ). It will first ask gtk to render at the next integer scale then zoom out the resulting bitmap as necessary. This definitely results in blurriness that I do not see on windows (but you can see on macOS). Compare Qt which does support true fractional scaling albeit as I was saying this leads to another significant problem https://doc.qt.io/qt-5/qt.html#HighDpiScaleFactorRoundingPolicy-enum https://doc.qt.io/qt-5/qt.html#HighDpiScaleFactorRoundingPol... , but it does often result in a level of sharpness that cannot be matched, and it is trivial to see when you compare gtk with qt programs.

ylyn 5y ago

> What's odd is that detection of headphone jack worked in every distro and DE I've ever used (currently Arch Linux with pulseaudio and Gnome 3 on Wayland) This needs the kernel driver to get it right. It doesn't depend so much on what userspace audio server you use. In the end they all use ALSA.

phendrenad2 5y ago

No offense, but every complaint about something not functioning under Linux gets this exact response. "It worked for me, on my completely different hardware". And this is the core of the problem, two people using the same hardware and experiencing the same problem rarely meet online. Really sells System 76 and other Linux-focused hardware.

nextaccountic 5y ago
This is true, sorry. I'm just saying it felt odd because over a number of different computers, a lot of things didn't work right, but this specific thing always did. I didn't even know it could not work right.
AtlasBarfed 5y ago
And that's where Intel screwed up. It could have devoted .001% of quarterly revenues to fund ten years of linux hardware compatibility testing and driver development. It would have hedged against Microsoft in numerous ways: business dependence, forcing the hardware utilization Intel always accused Windows of ignoring, probably would have given them a functional beachhead in netbooks, mobile phones, and kept them abreast of other developments like ARM. Google could have also done this for pennies to hedge Microsoft. IBM could have used it to push back into consumer hardware. But the ship has sailed for Google with Android and ChromeOS. IBM is dying. Intel is the only one that is still has some market incentive.

AshamedCaptain 5y ago

To this day wayland does not do fractional scaling. It just blurries individual windows a la macOS. The only toolkit around here that can do actual fractional scaling is Qt. Which is why all gtk based DEs like xfce are at a disadvantage.

cycomanic 5y ago
That's not true, fractional scaling works fine both in sway and gnome on wayland. There was an issue with fractional scaling of xwayland windows, which caused blurriness, but I think this has been fixed a while ago (I can't see the blurriness anymore).
- AshamedCaptain 5y ago
  Gtk does not do fractional scaling at all. It just does integer scaling then relies on the compositor to zoom in/out the window as necessary. This results in blurriness and poor performance. Qt can do true arbitrary fractional scaling, which has other problems.
  - nextaccountic 5y ago
    > Gtk does not do fractional scaling at all. It just does integer scaling then relies on the compositor to zoom in/out the window as necessary. This results in blurriness and poor performance. Are you sure? Maybe you mean on X11? I'm running Gnome on Wayland and with this setting: > gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" I get not blurriness at all. I'm actually kind of paranoid about this issue so can you maybe point me to some online docs describing this issue?
    - AshamedCaptain 5y ago
      This is a toolkit problem, it has nothing to do with wayland or x11. See https://developer.gnome.org/gdk3/stable/gdk3-Windows.html#gdk-window-get-scale-factor https://developer.gnome.org/gdk3/stable/gdk3-Windows.html#gd... , gtk just supports integers as an scaling factor. The mutter setting you are mentioning just enables framebuffer scaling (ie bitmap, http://blog.3v1n0.net/informatica/linux/gnome-fractional-and-multi-monitor-scaling-hackfest-the-report/ http://blog.3v1n0.net/informatica/linux/gnome-fractional-and... ). It will first ask gtk to render at the next integer scale then zoom out the resulting bitmap as necessary. This definitely results in blurriness that I do not see on windows (but you can see on macOS). Compare Qt which does support true fractional scaling albeit as I was saying this leads to another significant problem https://doc.qt.io/qt-5/qt.html#HighDpiScaleFactorRoundingPolicy-enum https://doc.qt.io/qt-5/qt.html#HighDpiScaleFactorRoundingPol... , but it does often result in a level of sharpness that cannot be matched, and it is trivial to see when you compare gtk with qt programs.