home.social

#regressions — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #regressions, aggregated by home.social.

fetched live
  1. Az AI sorra tárja fel a Linux hibáit, ezért a Canonical heti kernelkiadásokra áll át. Ez gyorsabb javításokat ígér, de te bevállalod-e a -proposed korai buildjeit a gyorsabb patch-ekért? Tudd meg, hogyan őrzik meg a megbízhatóságot.

    linuxmint.hu/hir/2026/09/annyi

    #Ubuntu #Canonical #Linux #kernel #CVE #AI #security #kernelrelease #ubuntu-proposed #bugfixes #regressions #kernelorg

  2. Az AI sorra tárja fel a Linux hibáit, ezért a Canonical heti kernelkiadásokra áll át. Ez gyorsabb javításokat ígér, de te bevállalod-e a -proposed korai buildjeit a gyorsabb patch-ekért? Tudd meg, hogyan őrzik meg a megbízhatóságot.

    linuxmint.hu/hir/2026/09/annyi

    #Ubuntu #Canonical #Linux #kernel #CVE #AI #security #kernelrelease #ubuntu-proposed #bugfixes #regressions #kernelorg

  3. Az AI sorra tárja fel a Linux hibáit, ezért a Canonical heti kernelkiadásokra áll át. Ez gyorsabb javításokat ígér, de te bevállalod-e a -proposed korai buildjeit a gyorsabb patch-ekért? Tudd meg, hogyan őrzik meg a megbízhatóságot.

    linuxmint.hu/hir/2026/09/annyi

    #Ubuntu #Canonical #Linux #kernel #CVE #AI #security #kernelrelease #ubuntu-proposed #bugfixes #regressions #kernelorg

  4. Az AI sorra tárja fel a Linux hibáit, ezért a Canonical heti kernelkiadásokra áll át. Ez gyorsabb javításokat ígér, de te bevállalod-e a -proposed korai buildjeit a gyorsabb patch-ekért? Tudd meg, hogyan őrzik meg a megbízhatóságot.

    linuxmint.hu/hir/2026/09/annyi

    #Ubuntu #Canonical #Linux #kernel #CVE #AI #security #kernelrelease #ubuntu-proposed #bugfixes #regressions #kernelorg

  5. 🚨 #Régressions : le projet de loi "simplification" revient à l'Assemblée nationale.

    - Suppression des ZFE sans alternatives contre la pollution de l’air
    - Dérogations au Zéro Artificialisation Nette
    - Affaiblissement du dialogue démocratique en rendant les CESER facultatifs

    ⬇️ (1/2)

  6. 🚨 #Régressions : le projet de loi "simplification" revient à l'Assemblée nationale.

    - Suppression des ZFE sans alternatives contre la pollution de l’air
    - Dérogations au Zéro Artificialisation Nette
    - Affaiblissement du dialogue démocratique en rendant les CESER facultatifs

    ⬇️ (1/2)

  7. 🚨 #Régressions : le projet de loi "simplification" revient à l'Assemblée nationale.

    - Suppression des ZFE sans alternatives contre la pollution de l’air
    - Dérogations au Zéro Artificialisation Nette
    - Affaiblissement du dialogue démocratique en rendant les CESER facultatifs

    ⬇️ (1/2)

  8. 🚨 #Régressions : le projet de loi "simplification" revient à l'Assemblée nationale.

    - Suppression des ZFE sans alternatives contre la pollution de l’air
    - Dérogations au Zéro Artificialisation Nette
    - Affaiblissement du dialogue démocratique en rendant les CESER facultatifs

    ⬇️ (1/2)

  9. CW: Rant about bugs in Gnome

    Seriously #gnome don't you test your new apps?
    1. "Papers" the new PDF viewer prints a single landscape page blatantly horizontal on the piece of paper, cutting off half of the contents, wasting paper and ink. While I can fix that *manually* for each print in the print dialog this was *never* an issue with the older Evince.
    2. "Loupe" the new image viewer supposedly can rotate images. Well, it has a nice rotation animation but then the image snaps right back. Opened in "Eye of Gnome" everything works just fine 🤦‍♂️
    3. Nautilus also had smaller issues after big updates, sometimes not refreshing after file operations or getting stuck with cut and paste.

    What happened to form follows function?

    I'm done for today, don't even feel like reporting those bugs. (If anyone does: thank you, feel free to share the link ❤️ )

    I'll switch back to evince&eog for now. They are still working fine thankfully.

    #fedora43 #regressions

  10. CW: Rant about bugs in Gnome

    Seriously don't you test your new apps?
    1. "Papers" the new PDF viewer prints a single landscape page blatantly horizontal on the piece of paper, cutting off half of the contents, wasting paper and ink. While I can fix that *manually* for each print in the print dialog this was *never* an issue with the older Evince.
    2. "Loupe" the new image viewer supposedly can rotate images. Well, it has a nice rotation animation but then the image snaps right back. Opened in "Eye of Gnome" everything works just fine 🤦‍♂️
    3. Nautilus also had smaller issues after big updates, sometimes not refreshing after file operations or getting stuck with cut and paste.

    What happened to form follows function?

    I'm done for today, don't even feel like reporting those bugs. (If anyone does: thank you, feel free to share the link ❤️ )

    I'll switch back to evince&eog for now. They are still working fine thankfully.

  11. CW: Rant about bugs in Gnome

    Seriously #gnome don't you test your new apps?
    1. "Papers" the new PDF viewer prints a single landscape page blatantly horizontal on the piece of paper, cutting off half of the contents, wasting paper and ink. While I can fix that *manually* for each print in the print dialog this was *never* an issue with the older Evince.
    2. "Loupe" the new image viewer supposedly can rotate images. Well, it has a nice rotation animation but then the image snaps right back. Opened in "Eye of Gnome" everything works just fine 🤦‍♂️
    3. Nautilus also had smaller issues after big updates, sometimes not refreshing after file operations or getting stuck with cut and paste.

    What happened to form follows function?

    I'm done for today, don't even feel like reporting those bugs. (If anyone does: thank you, feel free to share the link ❤️ )

    I'll switch back to evince&eog for now. They are still working fine thankfully.

    #fedora43 #regressions

  12. CW: Rant about bugs in Gnome

    Seriously #gnome don't you test your new apps?
    1. "Papers" the new PDF viewer prints a single landscape page blatantly horizontal on the piece of paper, cutting off half of the contents, wasting paper and ink. While I can fix that *manually* for each print in the print dialog this was *never* an issue with the older Evince.
    2. "Loupe" the new image viewer supposedly can rotate images. Well, it has a nice rotation animation but then the image snaps right back. Opened in "Eye of Gnome" everything works just fine 🤦‍♂️
    3. Nautilus also had smaller issues after big updates, sometimes not refreshing after file operations or getting stuck with cut and paste.

    What happened to form follows function?

    I'm done for today, don't even feel like reporting those bugs. (If anyone does: thank you, feel free to share the link ❤️ )

    I'll switch back to evince&eog for now. They are still working fine thankfully.

    #fedora43 #regressions

  13. Well, the house destruction metaphor was pretty apt today when I decided to try new JJ Flex "improvements." First I couldn't even run the thing, then I could hear radio but I couldn't close the application, then I could see the app but the menu bar and tuning frequencies didn't exist. Lucky for you, the observer, it's all good now. We have a menu bar and I think you can tune the thing. I think you can even tune via the waterfall. Suffice to say, this release that you won't ever see unless you are bored enough to spy on me via github. The real hope is that all the pain will be worth it in the end. #regressions #jjflexradio

  14. Well, the house destruction metaphor was pretty apt today when I decided to try new JJ Flex "improvements." First I couldn't even run the thing, then I could hear radio but I couldn't close the application, then I could see the app but the menu bar and tuning frequencies didn't exist. Lucky for you, the observer, it's all good now. We have a menu bar and I think you can tune the thing. I think you can even tune via the waterfall. Suffice to say, this release that you won't ever see unless you are bored enough to spy on me via github. The real hope is that all the pain will be worth it in the end. #regressions #jjflexradio

  15. Well, the house destruction metaphor was pretty apt today when I decided to try new JJ Flex "improvements." First I couldn't even run the thing, then I could hear radio but I couldn't close the application, then I could see the app but the menu bar and tuning frequencies didn't exist. Lucky for you, the observer, it's all good now. We have a menu bar and I think you can tune the thing. I think you can even tune via the waterfall. Suffice to say, this release that you won't ever see unless you are bored enough to spy on me via github. The real hope is that all the pain will be worth it in the end. #regressions #jjflexradio

  16. We're starting to see the immense effect #AI has on #softwaredevelopment. For example, #Gitlab now has 3 #regressions that annoy me (at least two of which we've reported).

    One of them has a """fix""" submitted by "totally not Gpu McSlopperson," which added two comments and called it a day.

    I'm going to insist on 3* hourly rate if I get tasked fixing that sort of shite.
  17. We're starting to see the immense effect #AI has on #softwaredevelopment. For example, #Gitlab now has 3 #regressions that annoy me (at least two of which we've reported).

    One of them has a """fix""" submitted by "totally not Gpu McSlopperson," which added two comments and called it a day.

    I'm going to insist on 3* hourly rate if I get tasked fixing that sort of shite.
  18. We're starting to see the immense effect #AI has on #softwaredevelopment. For example, #Gitlab now has 3 #regressions that annoy me (at least two of which we've reported).

    One of them has a """fix""" submitted by "totally not Gpu McSlopperson," which added two comments and called it a day.

    I'm going to insist on 3* hourly rate if I get tasked fixing that sort of shite.
  19. ""Within a week, preferably before the next rc.""

    That's about the time in which Linus wants #Linux #kernel regression fixed users reported. Through a revert if necessary, ""so that maintainers don't get stressed out over having a pending problem report that people keep pestering them about.""

    In case you wondered.

    lore.kernel.org/all/CAHk-%3Dwi

    #LinuxKernel #regressions

  20. ""Within a week, preferably before the next rc.""

    That's about the time in which Linus wants regression fixed users reported. Through a revert if necessary, ""so that maintainers don't get stressed out over having a pending problem report that people keep pestering them about.""

    In case you wondered.

    lore.kernel.org/all/CAHk-%3Dwi

  21. ""Within a week, preferably before the next rc.""

    That's about the time in which Linus wants #Linux #kernel regression fixed users reported. Through a revert if necessary, ""so that maintainers don't get stressed out over having a pending problem report that people keep pestering them about.""

    In case you wondered.

    lore.kernel.org/all/CAHk-%3Dwi

    #LinuxKernel #regressions

  22. ""Within a week, preferably before the next rc.""

    That's about the time in which Linus wants #Linux #kernel regression fixed users reported. Through a revert if necessary, ""so that maintainers don't get stressed out over having a pending problem report that people keep pestering them about.""

    In case you wondered.

    lore.kernel.org/all/CAHk-%3Dwi

    #LinuxKernel #regressions

  23. #WTF
    #Nextcloud Android App

    Severe #regressions

    Photo uploads:
    EXIF GPS data is stripped. WTF1

    Autouploads:
    no-media files are not automatically uploaded WTF2

    Already filed and discussed in several issues like recently in

    github.com/nextcloud/android/i

    and previously in

    github.com/nextcloud/android/i

  24. #WTF
    #Nextcloud Android App

    Severe #regressions

    Photo uploads:
    EXIF GPS data is stripped. WTF1

    Autouploads:
    no-media files are not automatically uploaded WTF2

    Already filed and discussed in several issues like recently in

    github.com/nextcloud/android/i

    and previously in

    github.com/nextcloud/android/i

  25. #WTF
    #Nextcloud Android App

    Severe #regressions

    Photo uploads:
    EXIF GPS data is stripped. WTF1

    Autouploads:
    no-media files are not automatically uploaded WTF2

    Already filed and discussed in several issues like recently in

    github.com/nextcloud/android/i

    and previously in

    github.com/nextcloud/android/i

  26. #WTF
    #Nextcloud Android App

    Severe #regressions

    Photo uploads:
    EXIF GPS data is stripped. WTF1

    Autouploads:
    no-media files are not automatically uploaded WTF2

    Already filed and discussed in several issues like recently in

    github.com/nextcloud/android/i

    and previously in

    github.com/nextcloud/android/i

  27. 'Causal Discovery with Generalized Linear Models through Peeling Algorithms', by Minjie Wang, Xiaotong Shen, Wei Pan.

    jmlr.org/papers/v25/23-1228.ht

    #causal #alzheimer #regressions

  28. 'Causal Discovery with Generalized Linear Models through Peeling Algorithms', by Minjie Wang, Xiaotong Shen, Wei Pan.

    jmlr.org/papers/v25/23-1228.ht

    #causal #alzheimer #regressions

  29. 'Causal Discovery with Generalized Linear Models through Peeling Algorithms', by Minjie Wang, Xiaotong Shen, Wei Pan.

    jmlr.org/papers/v25/23-1228.ht

    #causal #alzheimer #regressions

  30. 'Causal Discovery with Generalized Linear Models through Peeling Algorithms', by Minjie Wang, Xiaotong Shen, Wei Pan.

    jmlr.org/papers/v25/23-1228.ht

    #causal #alzheimer #regressions

  31. The two [1] recently affecting many people in mainline and various stable/longterm series should soon be a thing of the past:

    Linus merged fixes into 6.12-rc4[2] and Greg queued them for the next stable releases[3].

    Wondering what we should learn from this wrt to handling such regressions quickly and ideally even preventing them from hitting stable.

    [1] lore.kernel.org/all/4e1977ca-6

    [2] git.kernel.org/torvalds/c/d7f5

    [3] lore.kernel.org/all/2024102100

  32. The two #Bluetooth #regressions[1] recently affecting many people in #Linux mainline and various stable/longterm #kernel series should soon be a thing of the past:

    Linus merged fixes into #LinuxKernel 6.12-rc4[2] and Greg queued them for the next stable releases[3].

    Wondering what we should learn from this wrt to handling such regressions quickly and ideally even preventing them from hitting stable.

    [1] lore.kernel.org/all/4e1977ca-6

    [2] git.kernel.org/torvalds/c/d7f5

    [3] lore.kernel.org/all/2024102100

  33. The two #Bluetooth #regressions[1] recently affecting many people in #Linux mainline and various stable/longterm #kernel series should soon be a thing of the past:

    Linus merged fixes into #LinuxKernel 6.12-rc4[2] and Greg queued them for the next stable releases[3].

    Wondering what we should learn from this wrt to handling such regressions quickly and ideally even preventing them from hitting stable.

    [1] lore.kernel.org/all/4e1977ca-6

    [2] git.kernel.org/torvalds/c/d7f5

    [3] lore.kernel.org/all/2024102100

  34. The two #Bluetooth #regressions[1] recently affecting many people in #Linux mainline and various stable/longterm #kernel series should soon be a thing of the past:

    Linus merged fixes into #LinuxKernel 6.12-rc4[2] and Greg queued them for the next stable releases[3].

    Wondering what we should learn from this wrt to handling such regressions quickly and ideally even preventing them from hitting stable.

    [1] lore.kernel.org/all/4e1977ca-6

    [2] git.kernel.org/torvalds/c/d7f5

    [3] lore.kernel.org/all/2024102100

  35. Can you come up with convincing *stats* on why backporting a huge pile of patches (say 800+, like in the case of 6.10.3) to stable series just days after being mainlined *during the merge window* and thus included in a mainline -rc1 is *worse* than quickly backporting changes mainlined *during the rest of the development cycle*?

    Then tell me about it, because then I'll bring this up on the maintainers summit while talking about .

    1/ FWIW, this is what I tried: I…

  36. Can you come up with convincing *stats* on why backporting a huge pile of patches (say 800+, like in the case of #Linux 6.10.3) to stable #kernel series just days after being mainlined *during the merge window* and thus included in a mainline -rc1 is *worse* than quickly backporting changes mainlined *during the rest of the development cycle*?

    Then tell me about it, because then I'll bring this up on the maintainers summit while talking about #regressions.

    1/ FWIW, this is what I tried: I…

  37. Can you come up with convincing *stats* on why backporting a huge pile of patches (say 800+, like in the case of #Linux 6.10.3) to stable #kernel series just days after being mainlined *during the merge window* and thus included in a mainline -rc1 is *worse* than quickly backporting changes mainlined *during the rest of the development cycle*?

    Then tell me about it, because then I'll bring this up on the maintainers summit while talking about #regressions.

    1/ FWIW, this is what I tried: I…

  38. Can you come up with convincing *stats* on why backporting a huge pile of patches (say 800+, like in the case of #Linux 6.10.3) to stable #kernel series just days after being mainlined *during the merge window* and thus included in a mainline -rc1 is *worse* than quickly backporting changes mainlined *during the rest of the development cycle*?

    Then tell me about it, because then I'll bring this up on the maintainers summit while talking about #regressions.

    1/ FWIW, this is what I tried: I…