Announcement

Collapse
No announcement yet.

KDE Ends July With More Bug Fixes, Discover Improvements

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

  • KDE Ends July With More Bug Fixes, Discover Improvements

    Phoronix: KDE Ends July With More Bug Fixes, Discover Improvements

    KDE developers are wrapping up July with more bug fixes and other feature work underway for Plasma 5.26...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    KDE cyberpunk release in the year 2077 changelog:

    1. 2077 bugs fixes.
    2. Improved wayland support.
    3. Introducing new extra ugly compact cluttered theme because existing one isn't ugly enough.
    4. Add new shiny 77 features. Bug fixes will come. don't worry lol.

    Comment


    • #3
      Interesting tidbit is the "- Hotplugged mice will no longer lose their settings when the system is woken up or un-docked" feature.

      It ended up being a one line change (knowing where to look is half the battle), but this thread outlines how long it took: https://bugs.kde.org/show_bug.cgi?id=435113

      Plus it ended up having 56 people CC'd to it, as lots of people were getting the issue.

      Comment


      • #4
        Originally posted by joshx1 View Post
        Interesting tidbit is the "- Hotplugged mice will no longer lose their settings when the system is woken up or un-docked" feature.

        It ended up being a one line change (knowing where to look is half the battle), but this thread outlines how long it took: https://bugs.kde.org/show_bug.cgi?id=435113

        Plus it ended up having 56 people CC'd to it, as lots of people were getting the issue.
        That reminds me of the $200K consultant fee charged to kick a machine story. Guy maintained a large production line machine for many years, got fired in a round of layoffs so the company could save money, few months later the machine quits working, company calls guy to fix machine, he shows up, walks the line a few times inspecting stuff, kicks the machine in the right spot to make everything start working perfectly, and then billed the company a $200K consultation fee.

        The proprietary app one was funny as well. All over improperly formatted licenses. I almost wonder if that should be considered a downstream issue. It's not like it's KDE's fault that other people don't follow the defined standards.

        Comment


        • #5
          ngraham I see compilation errors in plasma-desktop-git since a couple of days:

          Code:
          Building CXX object kcms/touchpad/kcm/CMakeFiles/kcm_touchpad.dir/xlib/customslider.cpp.o
          In file included from /home/marcus/Downloads/KDE/plasma-desktop-git/src/plasma-desktop/kcms/tablet/inputdevice.cpp:7:
          /home/marcus/Downloads/KDE/plasma-desktop-git/src/plasma-desktop/kcms/tablet/inputdevice.h:195:79: error: no member named 'defaultOutputArea' in 'OrgKdeKWinInputDeviceInterface'
          &OrgKdeKWinInputDeviceInterface::defaultOutputArea ,
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
          /home/marcus/Downloads/KDE/plasma-desktop-git/src/plasma-desktop/kcms/tablet/inputdevice.h:196:79: error: no member named 'supportsOutputArea' in 'OrgKdeKWinInputDeviceInterface'
          &OrgKdeKWinInputDeviceInterface::supportsOutputAre a,
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
          [ 97%] Building CXX object kcms/touchpad/kcm/CMakeFiles/kcm_touchpad.dir/xlib/sliderpair.cpp.o
          [ 97%] Built target kcmspellchecking
          [ 97%] Building CXX object kcms/touchpad/kcm/CMakeFiles/kcm_touchpad.dir/xlib/testarea.cpp.o
          [ 97%] Built target kcm_componentchooser
          2 errors generated.
          make[2]: *** [kcms/tablet/CMakeFiles/kcm_tablet.dir/build.make:158: kcms/tablet/CMakeFiles/kcm_tablet.dir/inputdevice.cpp.o] Fehler 1
          make[2]: *** Es wird auf noch nicht beendete Prozesse gewartet....
          [ 97%] Building CXX object kcms/touchpad/kcm/CMakeFiles/kcm_touchpad.dir/xlib/testbutton.cpp.o
          [ 97%] Building CXX object kcms/touchpad/kcm/CMakeFiles/kcm_touchpad.dir/xlib/touchpadconfigxlib.cpp.o
          [ 98%] Building CXX object kcms/touchpad/kcm/CMakeFiles/kcm_touchpad.dir/xlib/customconfigdialogmanager.cpp.o
          [ 98%] Built target kcm_smserver
          [ 98%] Building CXX object kcms/touchpad/kcm/CMakeFiles/kcm_touchpad.dir/kcm_touchpad_autogen/EWIEGA46WW/qrc_resources.cpp.o
          In file included from /home/marcus/Downloads/KDE/plasma-desktop-git/src/plasma-desktop/kcms/tablet/devicesmodel.cpp:9:
          /home/marcus/Downloads/KDE/plasma-desktop-git/src/plasma-desktop/kcms/tablet/inputdevice.h:195:79: error: no member named 'defaultOutputArea' in 'OrgKdeKWinInputDeviceInterface'
          &OrgKdeKWinInputDeviceInterface::defaultOutputArea ,
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
          /home/marcus/Downloads/KDE/plasma-desktop-git/src/plasma-desktop/kcms/tablet/inputdevice.h:196:79: error: no member named 'supportsOutputArea' in 'OrgKdeKWinInputDeviceInterface'
          &OrgKdeKWinInputDeviceInterface::supportsOutputAre a,
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
          In file included from /home/marcus/Downloads/KDE/plasma-desktop-git/src/build/kcms/tablet/kcm_tablet_autogen/mocs_compilation.cpp:3:
          In file included from /home/marcus/Downloads/KDE/plasma-desktop-git/src/build/kcms/tablet/kcm_tablet_autogen/EWIEGA46WW/moc_inputdevice.cpp:10:
          /home/marcus/Downloads/KDE/plasma-desktop-git/src/build/kcms/tablet/kcm_tablet_autogen/EWIEGA46WW/../../../../../plasma-desktop/kcms/tablet/inputdevice.h:195:79: error: no member named 'defaultOutputArea' i
          n 'OrgKdeKWinInputDeviceInterface'
          &OrgKdeKWinInputDeviceInterface::defaultOutputArea ,
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
          /home/marcus/Downloads/KDE/plasma-desktop-git/src/build/kcms/tablet/kcm_tablet_autogen/EWIEGA46WW/../../../../../plasma-desktop/kcms/tablet/inputdevice.h:196:79: error: no member named 'supportsOutputArea'
          in 'OrgKdeKWinInputDeviceInterface'
          &OrgKdeKWinInputDeviceInterface::supportsOutputAre a,
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
          2 warnings generated.
          In file included from /home/marcus/Downloads/KDE/plasma-desktop-git/src/plasma-desktop/kcms/tablet/kcmtablet.cpp:9:
          /home/marcus/Downloads/KDE/plasma-desktop-git/src/plasma-desktop/kcms/tablet/inputdevice.h:195:79: error: no member named 'defaultOutputArea' in 'OrgKdeKWinInputDeviceInterface'
          &OrgKdeKWinInputDeviceInterface::defaultOutputArea ,
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
          /home/marcus/Downloads/KDE/plasma-desktop-git/src/plasma-desktop/kcms/tablet/inputdevice.h:196:79: error: no member named 'supportsOutputArea' in 'OrgKdeKWinInputDeviceInterface'
          &OrgKdeKWinInputDeviceInterface::supportsOutputAre a,
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
          2 errors generated.
          make[2]: *** [kcms/tablet/CMakeFiles/kcm_tablet.dir/build.make:144: kcms/tablet/CMakeFiles/kcm_tablet.dir/devicesmodel.cpp.o] Fehler 1
          2 errors generated.
          make[2]: *** [kcms/tablet/CMakeFiles/kcm_tablet.dir/build.make:87: kcms/tablet/CMakeFiles/kcm_tablet.dir/kcm_tablet_autogen/mocs_compilation.cpp.o] Fehler 1

          Comment


          • #6
            Originally posted by skeevy420 View Post
            The proprietary app one was funny as well. All over improperly formatted licenses. I almost wonder if that should be considered a downstream issue. It's not like it's KDE's fault that other people don't follow the defined standards.
            Really its not surprising to have this problem thinking that when a developer on Fedora decided todo a license audit found 200+ different wordings of MIT license.

            Improperly formatted licenses are horrible common.

            Comment


            • #7
              Originally posted by ms178 View Post
              ngraham I see compilation errors in plasma-desktop-git since a couple of days:
              did you also compile kwin first ?

              Comment


              • #8
                Originally posted by usta View Post
                did you also compile kwin first ?
                Hm, not exactly as I use KwinFT-git and its dependancies. However, I compiled KwinFT before. I also adjusted the PKGBUILD of plasma-desktop-git accordingly and it used to work just fine with KwinFT until it broke about a week ago.

                Comment


                • #9
                  Originally posted by ms178 View Post

                  Hm, not exactly as I use KwinFT-git and its dependancies. However, I compiled KwinFT before. I also adjusted the PKGBUILD of plasma-desktop-git accordingly and it used to work just fine with KwinFT until it broke about a week ago.
                  rg defaultOutputArea [ripgrep] result :

                  kwin/src/backends/libinput/device.h
                  142: Q_PROPERTY(QRectF defaultOutputArea READ defaultOutputArea CONSTANT)
                  626: QRectF defaultOutputArea() const;

                  kwin/src/backends/libinput/device.cpp
                  206: {ConfigKey::OutputArea, std::make_shared<ConfigData<QRectF>>(QByteArrayLit eral("OutputArea"), &Device::setOutputArea, &Device::defaultOutputArea)},
                  720:QRectF Device::defaultOutputArea() const

                  plasma-desktop/kcms/tablet/inputdevice.h
                  195: &OrgKdeKWinInputDeviceInterface::defaultOutputArea,

                  Comment


                  • #10
                    I've filed https://gitlab.com/kwinft/kwinft/-/issues/275 with KwinFT for this.

                    Comment

                    Working...
                    X