• Bro666@lemmy.kde.socialM
    205·
    6 months ago

    A gentle hint: If you suggest anything, you must be willing to put in the time to champion the task and carry out to completion.

    Also, do your suggesting here by following the instructions laid out in the blog post linked above.

    If you don’t do that, nobody is going to take up anything you suggest here.

  • kolorafa@lemmy.world
    172·
    6 months ago

    Make the plasmashell especially kwin stable, as its crashing a lot, and with wayland it’s taking whole session down…

    To the point I went back to Xorg

    • boredsquirrel@slrpnk.net
      81·
      6 months ago

      Cannot reproduce at all on Fedora Kinoite. I havent had any crashes since a long time. None on Plasma 6 since the beta is over.

      • Reach@feddit.uk
        2·
        6 months ago

        I’d second Kinoite, it has been rock solid and really does feel next gen. Especially nice that Universal Blue extends its capacity, being just one rebase away.

      • kolorafa@lemmy.worldEnglish
        41·
        6 months ago

        Whenever i get the Crash report window I fill it as much as possible and send, I stopped manually going into bugs.kde.org and manually create bug after the response I got was “it’s probably nvidia issue”, but for last months I’m on new AMD gpu and those issues still persist and I already learned to just periodically run kwin_x11 --replace& disown; exit to fix them and go with my life.

        And yes, the issues is probably not easy to track, as it only happen after at least few days or running it.

        Just recently the switch from plasma 5 to plasma 6 introduced another bug with the windows - every few hours/days i get a window that is visible but all mouse clicks go thru it and actually the window behind it receive those clicks, to fix it I (once again) do kwin replace.

        And yes, I’m heavy user with 2 workspaces * 2 desktops * a lot of open apps/windows running 24h/day, to the point just few days ago I got and error in console “maximum number of clients reached” when on X11 when trying to open any new window… (And I didn’t run out off RAM (48GB) or VRAM (16GB))

        So as much as I’m full time on Linux desktop for 8 years, the experience did improve a lot, but the stability of long running KDE Plasma slowly degraded over last years, hence my response.

        And I did have the same issues on my 8 year installation of Arch and on KDE Plasma.

        I had only few crashes and only on plasma 6, yes I did switch to 6.0.1 which is very quite new, so few crashes could be expected, but I’m on 6.0.4 (will update to 6.0.5) and kwin is still buggy with window ordering, and compared to xorg, on wayland I can’t do kwin_wayland --replace because it closes all my open windows/apps which is annoying. Heck, even killing/restarting plasmashell also shutdown all apps that was started from menu…

        Why did I switch? Because of hoping that issues from 5.x was fixed in 6.x but that was not the case :(

        Same that not many issues will crash whole kwin so they will never trigger “crash report”. It would be nice to have some some way to easy “trigger” state dump and open issue. That I would like the ‘stability’ and those last 0.001% of stability polish to be the focus for KDE.

        So as much as I love <3 KDE Plasma, and I yearly donate to KDE, I still can’t with clear mind suggest anyone to switch from MS Win to Linux (KDE) especially now with Wayland that made me lose all my unsaved work 3 weeks ago due to kwin crash.

  • boredsquirrel@slrpnk.net
    82·
    6 months ago

    Unifying a few codebases, and make Plasma more modular.

    1. A minimal Plasma

    I think Plasma is the best desktop and suited for minimal installs on machines with like 2GB of RAM. Reducing the needed dependencies (currently working on that in Fedora) to the bare minimum. Making all the fancy desktop effects, animations, blur, transparency, floating, … optional.

    And yes, please also remove the default plasmoids from the needed install. Maybe keep the ones default in the panel. Maybe add a way to find them as “official plasmoids” which would help a lot.

    2. Merge parallel works

    Gwenview, Spectacle, Kolourpaint, digiKam all have image editing bars. The one of spectacle is pretty good, Gwenview and digiKam could be merged, Kolourpaint could maybe get an additional few things specific to the app.

    • fossphi@lemm.eeEnglish
      6·
      6 months ago

      Merge parallel works

      Oh this is such a good idea. I think an approach analogous to ktexteditor (or the embedded konsole terminal in apps like dolphin and kile, too) would be amazing. Having the same editing expertise across Kate, kwrite, kile and other text editing apps is fantastic.

      • boredsquirrel@slrpnk.net
        51·
        6 months ago

        True, the default plasmoids being critical dependencies is insane.

        Please make these plasmoids optional.

        There are some where other plasmoids use their code, like the weather applet. But apart from that, a comic reader??

  • klangcola@reddthat.com
    6·
    6 months ago

    I hope a previously suggested goal of improving KDE for organizations makes a comeback. It was basically all about all the things a business/organisation would need to roll out a fleet of KDE computers, mainly tools for remote / centralised management by an IT department.

    In the wake of Windows’s recent and continued trend, more and more public institutions, universities, government etc should be looking at switching away from Windows. There’s also EUs recent Digital Sovereignty Initiative.

    German state Schleswig-Holstein is already swapping 30k computers to Linux

    • Aux@lemmy.world
      1·
      6 months ago

      Germany is swapping to open source software for the last two decades. It just shows you how hard the process actually is.

  • Codilingus@sh.itjust.works
    5·
    6 months ago

    Fix multi monitor support, and windows opening up where ever the hell they want, and whatever size they want. I don’t want to have to make a rule for every single thing I use to apply initially size and position. 1/2 the time those don’t work anyways.

  • penquin@lemm.ee
    4·
    6 months ago

    An option in the wallpaper settings to have the wallpaper span both monitors is like a dream for me. And if I knew how to code it, I’d start on it right now, but I’ll need about a year to learn and do it 😂

      • Mehrad :kde: :emacs: :rstats:@fosstodon.org
        24·
        6 months ago

        @Bro666
        Those are bugs reports and feature requests for all KDE applications including plasma and also including Kate, Yakuake, Konsole, Kmail, rkward …

        Not complaining here, but none of the bugs I ever reported or I’m following were addressed. To me this sounds like a good place to focus on, because these are issues that the community have faced or the suggestions they have come up with.

        • Bro666@lemmy.kde.socialM
          6·
          6 months ago

          Bugs are solved all the time. It is not a project for the community because the community already works on correcting bugs all the time. If the correction of bugs is not fast enough for you, we cordially and officially invite you to help out:

          https://community.kde.org/Get_Involved

          Remember: bugs are corrected by volunteers, many of which also have day jobs and other things going on. We are always understaffed. You can help.

          • Mehrad :kde: :emacs: :rstats:@fosstodon.org
            12·
            6 months ago

            @Bro666
            Thanks for your invitation, then I cordially and officially invite you accept the KDE Invent (Gitlab) access which I requested months and months ago.

            It is not right to randomly throw such messages and accuse people of not contributing when the contribution is locked behind a login screen that needs approval and the access is never given. I mean you can, but it is, unethical and unfriendly.

            For now all I could contribute is by donating money (check the records, it’s public).

            @kde

            • Bro666@lemmy.kde.socialM
              2·
              6 months ago

              Thanks for your invitation, then I cordially and officially invite you accept the KDE Invent (Gitlab) access which I requested months and months ago.

              A developer account, the kind of account that gives contributors full access to GitLab, gives the power to do a lot of damage too. In view of how malware has been injected into FLOSS projects in the past, you will understand why KDE’s Invent instance is not an open, free-for-all affaire.

              You have to go through a process, wherein one of the steps entails being sponsored by someone who is already a veteran contributor to KDE. This, in turn, entails contributing to KDE for a while, maybe in a non-development role, or by using the open services of invent. If you have not gone through that process, the sysadmin team will ignore your petition.

              That said, properly submitted requests for developer accounts are approved all the time.

              See here on how to proceed:

              https://community.kde.org/Infrastructure/Get_a_Developer_Account

              Notwithstanding, when it comes to bugs, which seems to be your main concern, there is a lot you can do without a developer account. Triaging, for example, wherein you confirm that a bug exists, check if it happens everywhere (i.e. across platforms and distros), and figure out what triggers it is an invaluable contribution that will save developers many hours of hunting and testing.

              Why not start there? All you need is an account on https://bugs.kde.org and you will also revive bugs that may have flown under the radar and contribute to getting them sorted once and for all. Your help could be key to that.

              For now all I could contribute is by donating money (check the records, it’s public).

              And that is much appreciated too. Thanks

              • Mehrad :kde: :emacs: :rstats:@fosstodon.org
                11·
                6 months ago

                @Bro666
                I sense some hostility here which I don’t appreciate.

                >> A developer account, the kind of account that gives contributors full access to GitLab, gives the power to do a lot of damage too.

                That sounds very wrong. All PRs (in case of Gitlab MRs) should be ultimately approved, so I cannot see why your Gitlab is vulnerable where as all other instances of Gitlab, the Github and all instances of Forgejo are nor susceptible these “damages”!

                🧵 👇🏼

                • Mehrad :kde: :emacs: :rstats:@fosstodon.org
                  1·
                  6 months ago

                  🧵 👆🏼
                  @Bro666
                  >> developer accounts are approved all the time.

                  Not mine! So “all the time” is as false as it gets. No one communicated to me that I need to provide certain information or details!! pure radio silence. So let’s be factual.

                  >> when it comes to bugs, which seems to be your main concern, there is a lot you can do without a developer account.

                  Bugs **and** feature requests are my main concern.

                  🧵 👇🏼