Announcement

Collapse
No announcement yet.

Ubuntu 22.04 LTS Release Schedule Published

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

  • arQon
    replied
    Originally posted by bple2137 View Post
    Some of them might not be into finding out what's the problem and how to fix it, but rather immediately login back to X11 session.
    Which is hardly unreasonable. It's not THEIR job to fix the Wayland fiasco, it's the Wayland team's.

    It's nice to see that Wayland is apparently close enough to usable that Canonical is willing to risk it for an LTS release, but it still sucks hard on so many important missing features that TBH I don't see how they can stick with that decision for any reason other than being tired of all the whining. Either that, or XWayland is going to be doing an awful lot of heavy lifting.

    Leave a comment:


  • mangeek
    replied
    bple2137 , I don't think they get any more conservative with LTS releases. The rolling release certainly lets them get more time under their belt for new technologies, but it seems like things are integrated and updated at a fairly even pace regardless of whether the next release is short-term or LTS.

    Leave a comment:


  • ThoreauHD
    replied
    Will this version require your vaccination QR code to use it?

    Leave a comment:


  • lucrus
    replied
    Distrowatch: "Put the fun back into computing: Use LInux, BSD."

    Canonical: "Put the boredom back into the fun: Use Ubuntu."

    Don't get me wrong, it's just I don't like it.

    Leave a comment:


  • elatllat
    replied
    PHP 8 will be good for servers.

    Waland is now stable on the last lts (used to crash).
    For me the last lts needs upstream kernel, blender, chromium, fontforge, eclipse, and netbeans, nodejs. Maybe Pop, Arch or Tumbleweed would be more suitable... Meh; it works.
    Last edited by elatllat; 27 August 2021, 04:56 PM.

    Leave a comment:


  • user1
    replied
    Originally posted by DanL View Post

    You can easily configure this in daemon.conf
    Also, why would you want everything resampled to 48k? If you're playing 44.1k audio, why would you want it needlessly resampled to 48k?
    My USB DAC makes an audible click each time it changes sample rate according to the source and it also results in a slight delay before audio starts playing (the DAC has a display which shows the current sample rate). It might not be a problem with onboard audio, but with a USB DAC like mine it's annoying when it constantly switches between 44100hz and 48000hz sources like that. I would actually like to know why is this the default behavior in Pulseaudio? Is it trying to deliver bit perfect audio or something? If you want bit perfect audio on Linux, you just use ALSA directly anyway AFAIK. I think the way Pipewire works (only 48000hz by default just like on Mac and Windows) is the sane default behavior.
    Last edited by user1; 27 August 2021, 12:53 PM.

    Leave a comment:


  • DanL
    replied
    Originally posted by user1 View Post
    For example, Pulseaudio has some really weird behavior like constantly changing the sample rate between 44100hz and 48000hz on my USB DAC which is really annoying.
    You can easily configure this in daemon.conf
    Also, why would you want everything resampled to 48k? If you're playing 44.1k audio, why would you want it needlessly resampled to 48k?

    Leave a comment:


  • bple2137
    replied
    Apparently, that's already being discussed and they want to switch to PW, though it's not confirmed yet: https://youtu.be/SmthCRF-NQQ?t=741

    Leave a comment:


  • user1
    replied
    Originally posted by bple2137 View Post

    I can't see where's the inconsistency is, really. There will be 2 releases with default Wayland session before the 22.04 LTS already. Looks like they didn't encounter any crucial issues this time and I haven't seen any sign of them being about to roll that back. I just said that they had no chance to test PW in any stable release so far, so that's unlikely to have that in the LTS release.
    Personally, I don't understand why people compare the transition from Pulseaudio to Pipewire to the transition from X to Wayland. I mean audio is much simpler if you compare it to a complete display stack. If Canonical is focusing on making Wayland the default in 22.04 LTS, when Wayland still has some serious flaws like forced vsync or other rough edges, I'm sure making the switch to Pipewire will not be an issue for LTS. Unlike Wayland, I haven't experienced any issues with Pipewire and I haven't even heard someone experiencing any serious isues with it. Like maybe some small ones that are most likely even issues on the user's end. So I think even one release before LTS is enough to test Pipewire.

    Leave a comment:


  • bple2137
    replied
    Originally posted by perpetually high View Post

    Had me in the first half, not gonna lie. That didn't compute for me. Not being mean or a bully. Just didn't compute. X11 stays default. PulseAudio stays default. Be consistent.
    I can't see where's the inconsistency is, really. There will be 2 releases with default Wayland session before the 22.04 LTS already. Looks like they didn't encounter any crucial issues this time and I haven't seen any sign of them being about to roll that back. I just said that they had no chance to test PW in any stable release so far, so that's unlikely to have that in the LTS release.

    Leave a comment:

Working...
X