Announcement

Collapse
No announcement yet.

KDE SC 4.7.0 Officially Released

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

  • #31
    Originally posted by RealNC View Post
    Of course I enabled it. Would be stupid otherwise.
    As already suggested try setting EGL_PLATFORM=x11 or disable gbm (configure with --disable-gbm)

    Comment


    • #32
      Originally posted by RealNC View Post
      Both the parent post and the bug you linked to provide a workaround:

      The bug only occurs with drm platform. With x11 everything should work fine.
      A workaround would be
      a) Setting EGL_PLATFORM=x11
      b) Don't build drm platform, so that x11 is chosen by default.
      (--with-egl-platforms=x11 instead of --with-egl-platforms=drm,x11)
      Getting buggy stuff like gbm before it's ready is the price you pay running mesa from git.

      Comment


      • #33
        Originally posted by smitty3268 View Post
        Both the parent post and the bug you linked to provide a workaround:
        Setting EGL_PLATFORM=x11 allows it work, but now it's even slower! Even glxgears dropped from 6000FPS to 2500FPS.

        Getting buggy stuff like gbm before it's ready is the price you pay running mesa from git.
        Trying with --disable-gbm results in:

        configure: error: EGL platform drm needs gbm

        About the "price to pay" for Mesa git, if I don't use latest Git right now, Flash locks up the system in fullscreen with page flipping enabled. Similar bugs prevented me in the past from using normal releases. There was often some bug that was only fixed in Git.

        Comment


        • #34
          Originally posted by RealNC View Post
          Setting EGL_PLATFORM=x11 allows it work, but now it's even slower! Even glxgears dropped from 6000FPS to 2500FPS.
          glxgears is not a valid benchmark, even at the best of times. And in this case, it's completely bypassing the EGL/GL ES setup you're running anyway. glxgears

          The real question is how the desktop effects are working, and how normal desktop apps are running on top of it. So far, commenters seem to be pretty universally saying the situation is better, so you seem to be the outlier here.

          About the "price to pay" for Mesa git, if I don't use latest Git right now, Flash locks up the system in fullscreen with page flipping enabled. Similar bugs prevented me in the past from using normal releases. There was often some bug that was only fixed in Git.
          Sure, there's a price to pay for using old Mesa versions as well. But I don't think you can complain that a version from git is broken, especially since it's the still somewhat experimental EGL/GL ES functionality that's broken. I think gbm was only checked in a week or so ago, so people not quite on the bleeding edge may have more success.

          Comment


          • #35
            Originally posted by smitty3268 View Post
            glxgears is not a valid benchmark, even at the best of times. And in this case, it's completely bypassing the EGL/GL ES setup you're running anyway. glxgears
            Not quite. glxgears is running inside the compositor, so it's affected by its performance. So from that perspective, it's useful as a benchmark.

            Sure, there's a price to pay for using old Mesa versions as well. But I don't think you can complain that a version from git is broken, especially since it's the still somewhat experimental EGL/GL ES functionality that's broken. I think gbm was only checked in a week or so ago, so people not quite on the bleeding edge may have more success.
            I "downgraded" Mesa to 7.11 RC2. The crash still happens and gbm is still there.

            Comment


            • #36
              Originally posted by RealNC View Post
              Not quite. glxgears is running inside the compositor, so it's affected by its performance. So from that perspective, it's useful as a benchmark.
              Very, very marginally. I'm tempted to say it's such a bad benchmark it's completely useless, but that is a big enough drop that I suppose we can probably say something bad MAY be happening. I'd want a lot more evidence, though, before actually claiming it. A glxgears framerate by itself is nothing, it just points out that maybe you should keep looking into other benchmarks to see if there is really something going on or not.

              I "downgraded" Mesa to 7.11 RC2. The crash still happens and gbm is still there.
              You're right, it looks like it was added June 23 which is longer back than i thought.

              Comment


              • #37
                Originally posted by smitty3268 View Post
                Very, very marginally. I'm tempted to say it's such a bad benchmark it's completely useless, but that is a big enough drop
                6000 fps == 0.000167 seconds / frame
                2500 fps == 0.000400 seconds / frame

                This is a differencee of 233 μs, which is closer to "trivial" than "big". The kernel sneezes and you get larger fluctuations than that.

                glxgears is not a benchmark glxgears is not a benchmark glxgears is not a benchmark
                glxgears is not a benchmark glxgears is not a benchmark glxgears is not a benchmark
                glxgears is not a benchmark glxgears is not a benchmark glxgears is not a benchmark



                (Even worse, there is no "upstream" for glxgears, so you cannot fix it to report proper frametimes. Sucks.)

                Comment


                • #38
                  I only upgraded to kde 4.7 yesterday but compared to previous upgrades there seems to be a lack of noticeable refinements to how you actuality interact with the gui.

                  Is this a sign they've got it close to how they ultimately want it to work or a lack of new ideas? Maybe I'm missing something or perhaps I'm simply expecting too much from every release? A new version of kde 4 does typically deliver noticeable improvements.

                  Comment


                  • #39
                    Originally posted by BlackStar View Post
                    glxgears is not a benchmark glxgears is not a benchmark glxgears is not a benchmark
                    glxgears is not a benchmark glxgears is not a benchmark glxgears is not a benchmark
                    glxgears is not a benchmark glxgears is not a benchmark glxgears is not a benchmark
                    I could never understand why they got rid of the -glxgearsisnotabenchmark switch

                    Comment


                    • #40
                      Originally posted by Nevertime View Post
                      perhaps I'm simply expecting too much from every release?
                      I think this is the case. Not every release of a product has to have more "whiz bang" end user visible changes.

                      Comment


                      • #41
                        There are always two sides on the stick

                        Some would complain that they introduce new stuff instead of stabilizing it, the others would complaing that they don't introduce new stuff (but you never hear them complain that it is stable ).

                        I think KDE has come to the point where it is mature and quite stable. The good thing is that they are not going to make some instabilities when moving to Qt 5 and ultimately to KDE 5 so there will be no 4.0 experiences

                        Comment


                        • #42
                          My experience.

                          1. I made that post in Martin Grlin blog. That's true: my GeForce 6150 is running just great, and I tried to stick to stock Fedora packages, so, no OpenGL ES for me. Maybe if I compile the OpenGL ES KWin I can get even better performance.

                          2. About this:

                          Originally posted by gedgon View Post
                          Nepomuk/Strigi - i'm curious - when will be usable? Here's simple test and big fail (again).

                          There are memory leaks in nepomukstorage and a lot of regressions, partly because of Strigi. You NEED an updated Strigi, and you won't get it with any distro (no, 0.7.2 won't cut it). Vishesh Handa of the Nepomuk team is working hard to fix those leaks, with the backtraces I provided. Let's hope to have a better Nepomuk in KDE 4.7.1.

                          Comment


                          • #43
                            Originally posted by Nevertime View Post
                            I only upgraded to kde 4.7 yesterday but compared to previous upgrades there seems to be a lack of noticeable refinements to how you actuality interact with the gui.

                            Is this a sign they've got it close to how they ultimately want it to work or a lack of new ideas? Maybe I'm missing something or perhaps I'm simply expecting too much from every release? A new version of kde 4 does typically deliver noticeable improvements.
                            It's a sign of the developers working on other stuff. Many core devs are currently working on further modularizing the Frameworks, even replacing technology that is based on functionality which is going to be deprecated in Qt 5.0 (eg. they're writing QML bindings), and Plasma Workspace devs are currently mostly concentrating on Plasma Active which in the long run will also be the future for a purely QML-powered Plasma Desktop.

                            KDE devs are still working like crazy but with so much going on behind the scenes on boring technical stuff, it's hard to show off fancy GUI results.

                            Comment


                            • #44
                              Totaly unrelated, but I whish I would know how to develop for KDE, because I would do so many things differently.

                              I like KDE more than anything, but someone needs to fill the gap between total usability [Gnome] and total technology and feature [KDE]...

                              I dreamed up an interface and functionality today... Maybe somthing for the future...

                              Comment


                              • #45
                                Originally posted by Awesomeness View Post
                                It's a sign of the developers working on other stuff. Many core devs are currently working on further modularizing the Frameworks, even replacing technology that is based on functionality which is going to be deprecated in Qt 5.0 (eg. they're writing QML bindings), and Plasma Workspace devs are currently mostly concentrating on Plasma Active which in the long run will also be the future for a purely QML-powered Plasma Desktop.

                                KDE devs are still working like crazy but with so much going on behind the scenes on boring technical stuff, it's hard to show off fancy GUI results.
                                Of course these efforts allow KDE to expand out onto other devices using multiple specialized UX's rather than one generic one, which then assuming these efforts take off means many more developers, when I look at the whole of whats going on, I think there's a KDE everywhere strategy in play here.which ultimately could work as a catalyst for Linux domination on the desktop. Think about it, if you can move the core of usage into KDE programs, then the user doesn't care about the backend do they?

                                Originally posted by V!NCENT View Post
                                Totaly unrelated, but I whish I would know how to develop for KDE, because I would do so many things differently.
                                I like KDE more than anything, but someone needs to fill the gap between total usability [Gnome] and total technology and feature [KDE]...
                                I dreamed up an interface and functionality today... Maybe somthing for the future...
                                How does gnome (assuming you're speaking of 3) have absolute usability? I thought usability = use ability, the ability of an average user to sit down and use it without prompting. I'll grant you that gnome 2's interface is downright obvious how to use, but Gnome 3 like OS X and Unity is just backwards. KDE can be argued to be less usable in the default paradigm than gnome 2 however that is only valid if and only if the person has never dealt with the paradigm that windows introduced, it could also be argued that lancelot as opposed to the kickoff applications launcher would be a better usability default. That being said I think that I could grab an average user off the streets set them in front of KDE and they'd know what to do, they might not utilize some of the more advanced functionality but they'd fulfill their purposes easily enough.

                                Comment

                                Working...
                                X