Announcement

Collapse
No announcement yet.

KDE 4.6.0 Has Arrived

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

  • #31
    Originally posted by deanjo View Post
    Indeed, looks like Blackstar is pointing fingers at the wrong group again.
    Look, I don't really know who is at fault here. The problem appeared as soon as I upgraded from 4.5.x to 4.6.0, so that's my primary lead. Someone warned about crashes on Nvidia 260.xx and newer; I did the same about R600c.

    What's the common thread between these crashes?

    Funnily enough, KDE tries to collect information for a bug report but then fails whining that "not enough information is available". That's, ugh, helpful.

    Comment


    • #32
      Originally posted by BlackStar View Post
      Look, I don't really know who is at fault here. The problem appeared as soon as I upgraded from 4.5.x to 4.6.0, so that's my primary lead. Someone warned about crashes on Nvidia 260.xx and newer; I did the same about R600c.
      I am unable to reproduce the crash here with Nvidia 260.xx and newer drivers.

      What's the common thread between these crashes?
      Common thread is that it is the same people that are always having the problems.

      Comment


      • #33
        Originally posted by BlackStar View Post
        Look, I don't really know who is at fault here. The problem appeared as soon as I upgraded from 4.5.x to 4.6.0, so that's my primary lead. Someone warned about crashes on Nvidia 260.xx and newer; I did the same about R600c.

        What's the common thread between these crashes?
        They are both caused by Xorg-compatible drivers developed by some big corporation?
        NVidia 260.x doesn't crash only Plasma 4.6. It also happens on 4.4.x as soon as NVidia 260.x is installed. As stated in https://bugs.kde.org/show_bug.cgi?id=251719#c1 the drivers causes a malfunction in glibc, so any software accessing that can potentially misbehave.

        Comment


        • #34
          Originally posted by BlackStar View Post
          Funnily enough, KDE tries to collect information for a bug report but then fails whining that "not enough information is available". That's, ugh, helpful.
          Doesn't it tell you to install the debuginfo packages for KDE from your distro?

          Comment


          • #35
            Originally posted by RealNC View Post
            Doesn't it tell you to install the debuginfo packages for KDE from your distro?
            Yes it does, but on Arch it seems they aren't separated from the standard packages. I'm not exactly sure what that means, but I bet you have to compile the program you want to debug with a debug parameter activated or something like that.

            Comment


            • #36
              Originally posted by Awesomeness View Post
              They are both caused by Xorg-compatible drivers developed by some big corporation?
              I thought radeon was developed by the community?

              Originally posted by deanjo
              Common thread is that it is the same people that are always having the problems.
              Yeah yeah, how about suggesting potential workarounds instead? My desktop crashes but I can still invoke commands, open windows or even use 3d.

              Any ideas? Can I switch to R600g without recompiling stuff? I don't wish to move to fglrx on this system.

              Comment


              • #37
                Originally posted by BlackStar View Post
                I thought radeon was developed by the community?
                If you are really that clueless, you should better leave Phoronix for good.

                Comment


                • #38
                  Originally posted by Awesomeness View Post
                  If you are really that clueless, you should better leave Phoronix for good.
                  Explain yourself.

                  Comment


                  • #39
                    Originally posted by BlackStar View Post
                    Explain yourself.
                    Dude, you obviously don't even read the articles here. In pretty much every article about radeon drivers it's clearly stated that it's developed by AMD and not a community project.
                    Easy conclusion: You're only here to troll in the forums.

                    Comment


                    • #40
                      Well that was a hell of an unexpected twist! I can't wait to find out how this plot develops.

                      [CTRL+R]

                      Comment


                      • #41
                        Originally posted by Awesomeness View Post
                        Dude, you obviously don't even read the articles here. In pretty much every article about radeon drivers it's clearly stated that it's developed by AMD and not a community project.
                        Easy conclusion: You're only here to troll in the forums.
                        Oh yeah? Here is the list of all radeon contributors (ohloh) - all 138 of them. 3 work for AMD. The rest just prove that you are not a very good troll.

                        Care to try again?

                        Comment


                        • #42
                          Originally posted by Awesomeness View Post
                          Dude, you obviously don't even read the articles here. In pretty much every article about radeon drivers it's clearly stated that it's developed by AMD and not a community project.
                          I have to disagree with this. The addition of initial support for new hardware features is primarily done by AMD, and Alex (agd5f) has added a number of new driver features such as EXA/Xv, tear-free and initial power management, but a *lot* of the work is done by community developers either working as independent volunteers or for other companies.

                          AMD developers do form *part* of the community, as do developers from a half dozen other companies, but (as examples) agd5f and airlied were very active community developers before they came to work for AMD and Red Hat respectively, and they are continuing to do what they did before -- they just do it during the day now rather than having to work a full time job doing something else then work on the drivers in the evening.

                          You can find examples to support pretty much any argument you want to make. The r300g driver was developed almost entirely by independent community developers, and the r600g driver was developed by a combination of RH and independent developers. All of the work made use of documentation / code / support from AMD but we're certainly not the only people developing the drivers.

                          If you want another good example, agd5f (AMD) releases the X driver, airlied (RH) releases the kernel driver, and Ian R (Intel) releases the 3D driver

                          Comment


                          • #43
                            Originally posted by bridgman View Post
                            I have to disagree with this. The addition of initial support for new hardware features is primarily done by AMD, and Alex (agd5f) has added a number of new driver features such as EXA/Xv, tear-free and initial power management, but a *lot* of the work is done by community developers either working as independent volunteers or for other companies.

                            AMD developers do form *part* of the community, as do developers from a half dozen other companies, but (as examples) agd5f and airlied were very active community developers before they came to work for AMD and Red Hat respectively, and they are continuing to do what they did before -- they just do it during the day now rather than having to work a full time job doing something else then work on the drivers in the evening.

                            You can find examples to support pretty much any argument you want to make. The r300g driver was developed almost entirely by independent community developers, and the r600g driver was developed by a combination of RH and independent developers. All of the work made use of documentation / code / support from AMD but we're certainly not the only people developing the drivers.

                            If you want another good example, agd5f (AMD) releases the X driver, airlied (RH) releases the kernel driver, and Ian R (Intel) releases the 3D driver
                            yayyyy 138 opensource dev's strike back sounds really good to me.

                            maybe microsoft and nvidia is on the wrong way.

                            Comment


                            • #44
                              I might be the only one but I don't care about KDE 4.6. KDE has gone to crap. Ever since 4, it's gone down hill. KDE 4 has way too many bugs. I hate to say it but I'm planning on changing my KDE 4 installs to Gnome. I could just add GDM/Gnome but then have tons of KDE stuff still.......

                              Anyway, KDE seems to ignore bugs or are way too selective....

                              Too bad.

                              Comment


                              • #45
                                That's a serious problem with KDE. Instead of fixing bugs, as soon as 4.6 was out the door, developers started concentrating on the features of 4.7. What they should be concentrating on is making 4.6 rock-solid first. On bugs.kde.org, devs commenting on bugs are saying that they lack manpower to fix bugs. If they lack manpower, don't start working on 4.7. Continue working on 4.6 until its stable.

                                If it continues that way, KDE will never have a truly stable release.

                                Comment

                                Working...
                                X