3 ms·

I don't know how much it affects priority, but they certainly accept bugs filed against older versions. Specifying versions is a big part of the form for a new

by topaz0 3y ago

I don't know how much it affects priority, but they certainly accept bugs filed against older versions. Specifying versions is a big part of the form for a new bug, and they let you select versions going way back.

Filligree 3y ago
I have a feeling they wouldn't accept bugs filed against NixOS, however, considering the huge number of patches applied. Which is a problem. NixOS remains by far the least aggravating OS I know, and... yeah. I wish there existed a desktop environment that played well with it.
- ParetoOptimal 3y ago
  Just submit a bug. If they dont accept it submit a bug to NixOS about KDE not accepting NixOS KDE users bugs.
- topaz0 3y ago
  I second my sibling comment -- just submit a bug. I think you are wrong that they would ignore it just because their context is somewhat different. Linux is full of differences like this. But also: Isn't one of the main benefits of NixOS that you can fairly painlessly get and try different versions of things? Just see if you can reproduce the bug in the same version of upstream. If so, file the bug with kde, if not, file the bug with NixOS because it's presumably caused by one of the patches.
  - NoahKAndrews 3y ago
    I think the point is that it won't run on NixOS without patches
    - bombcar 3y ago
      From my experience, reproducibility is king. If you can give a formula to reproduce a bug, even if it is obscure, it makes it so much easier to track down. That can be up to and including a downloadable VM image that shows the issue.
    - viraptor 3y ago
      This concern is a bit overblown here. There are 23 KDE patches at the moment, across multiple packages. kwin itself has 5, plasma-desktop has 4. Each one has an extremely limited scope - mostly one line changes related to paths rather than visible functionality. If you have a specific issue under nixos, it's going to be fairly easy to see if it's very unlikely to be caused by custom patches.
- kekebo 3y ago
  Out of interest, what are the issues you're facing? I'm having a great time with NixOS / Plasma 5
- aseipp 3y ago
  They have accepted bugs from NixOS before (there are nearly a 100 marked as "NixOS Linux" at bugs.kde.org), and I don't see any major reason they would stop. It's true there are many patches for the KDE libraries and Plasma, but realistically most of them are fairly "procedural" changes to adapt to non-FHS layouts, etc. For reference I count about ~66 patch files among the KDE expression in nixpkgs as of today, including Plasma, all libraries, and related apps. Most of them are in the range of 20 lines long, and they are .patch files, i.e. the actual applied diff is smaller than that. The largest patch is barely 190 lines long and it's for Akonadi, mostly rewriting hardcoded FHS paths throughout the codebase. I agree there are some quirks with most desktop environments on NixOS in my experience but realistically there's a huge amount of stuff in the ecosystem that plays anywhere from well-to-poorly in such environments, and the Linux desktop stack definitely was not designed at a time where this stuff was common. It is what it is, I guess.
- Aerbil313 3y ago
  I am using KDE on NixOS and IME there are no issues except the occasional screen freeze on X11 with Nvidia cards (and none with Wayland, you read that right!). Filed bugs and merged changes too.
- Arnavion 3y ago
  FWIW your attitude is correct in general. When you have a bug with a distro package and you haven't root-caused it yourself to a bug in upstream source, the best thing is to report it on the distro tracker. The distro package maintainer can then do that root-causing, and if they determine it's an upstream bug they can forward it to upstream. This is how it used to work (and still does with enterprise distros, because you might as well use the support contract you paid for). But users these days have gotten savvy enough to start engaging with upstream directly, especially since many upstreams have made it easier to be engaged with by using GitHub etc instead of mailing lists etc. Sometimes engaging directly with upstream works, as it apparently does with KDE according to other comments in this thread. Sometimes upstream gets annoyed because they only care about their tree, eg systemd devs get annoyed when users report bugs that have long been fixed in master, but still exist in an old stable release that happens to be the latest on some LTS distro. It depends on the project, so when in doubt start with the distro tracker.

by topaz0 3y ago

Filligree 3y ago

I have a feeling they wouldn't accept bugs filed against NixOS, however, considering the huge number of patches applied. Which is a problem. NixOS remains by far the least aggravating OS I know, and... yeah. I wish there existed a desktop environment that played well with it.

ParetoOptimal 3y ago
Just submit a bug. If they dont accept it submit a bug to NixOS about KDE not accepting NixOS KDE users bugs.
topaz0 3y ago
I second my sibling comment -- just submit a bug. I think you are wrong that they would ignore it just because their context is somewhat different. Linux is full of differences like this. But also: Isn't one of the main benefits of NixOS that you can fairly painlessly get and try different versions of things? Just see if you can reproduce the bug in the same version of upstream. If so, file the bug with kde, if not, file the bug with NixOS because it's presumably caused by one of the patches.
- NoahKAndrews 3y ago
  I think the point is that it won't run on NixOS without patches
  - bombcar 3y ago
    From my experience, reproducibility is king. If you can give a formula to reproduce a bug, even if it is obscure, it makes it so much easier to track down. That can be up to and including a downloadable VM image that shows the issue.
  - viraptor 3y ago
    This concern is a bit overblown here. There are 23 KDE patches at the moment, across multiple packages. kwin itself has 5, plasma-desktop has 4. Each one has an extremely limited scope - mostly one line changes related to paths rather than visible functionality. If you have a specific issue under nixos, it's going to be fairly easy to see if it's very unlikely to be caused by custom patches.
kekebo 3y ago
Out of interest, what are the issues you're facing? I'm having a great time with NixOS / Plasma 5
aseipp 3y ago
They have accepted bugs from NixOS before (there are nearly a 100 marked as "NixOS Linux" at bugs.kde.org), and I don't see any major reason they would stop. It's true there are many patches for the KDE libraries and Plasma, but realistically most of them are fairly "procedural" changes to adapt to non-FHS layouts, etc. For reference I count about ~66 patch files among the KDE expression in nixpkgs as of today, including Plasma, all libraries, and related apps. Most of them are in the range of 20 lines long, and they are .patch files, i.e. the actual applied diff is smaller than that. The largest patch is barely 190 lines long and it's for Akonadi, mostly rewriting hardcoded FHS paths throughout the codebase. I agree there are some quirks with most desktop environments on NixOS in my experience but realistically there's a huge amount of stuff in the ecosystem that plays anywhere from well-to-poorly in such environments, and the Linux desktop stack definitely was not designed at a time where this stuff was common. It is what it is, I guess.
Aerbil313 3y ago
I am using KDE on NixOS and IME there are no issues except the occasional screen freeze on X11 with Nvidia cards (and none with Wayland, you read that right!). Filed bugs and merged changes too.
Arnavion 3y ago
FWIW your attitude is correct in general. When you have a bug with a distro package and you haven't root-caused it yourself to a bug in upstream source, the best thing is to report it on the distro tracker. The distro package maintainer can then do that root-causing, and if they determine it's an upstream bug they can forward it to upstream. This is how it used to work (and still does with enterprise distros, because you might as well use the support contract you paid for). But users these days have gotten savvy enough to start engaging with upstream directly, especially since many upstreams have made it easier to be engaged with by using GitHub etc instead of mailing lists etc. Sometimes engaging directly with upstream works, as it apparently does with KDE according to other comments in this thread. Sometimes upstream gets annoyed because they only care about their tree, eg systemd devs get annoyed when users report bugs that have long been fixed in master, but still exist in an old stable release that happens to be the latest on some LTS distro. It depends on the project, so when in doubt start with the distro tracker.