Announcement

Collapse
No announcement yet.

KDE Releases Plasma Active One User Experience

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

  • #11
    Originally posted by lgstoian View Post
    When is the last time you used KDE ? And I hope it wasn't on Kubuntu.
    I have used KDE 4.7 on Archlinux (which means it is pretty much vanilla) for some time now and I agree.

    Colored subpixel hinting is one of the things that annoy me very much.
    plasma-desktop uses it no matter what settings: https://bugs.kde.org/show_bug.cgi?id=190627
    Maybe this isn't a bug in KDE itself but as this bug has been open for 2.5 years I believe they should just put in a workaround.

    Since the update to 4.7.2 a few days ago KDE introduced this new bug:


    At least plasma-desktop itself is somewhat stable now. They even fixed the segfault when shaking the panel a but to the bottom while resizing that has been in there since 4.0! But it still sometimes vanishes, but apparently without a segfault.
    And I nearly forgot the bug that the taskbar sometimes fails to order all entries in one line as I have set in the settings. It will leave out a place and instead put an entry in a second line (since 3 major versions ago): https://bugs.kde.org/show_bug.cgi?id=224447

    Some random applications I use on KDE:

    Akonadi... Well, at least it doesn't spam my logs with segfaults anymore. If anybody wonders, it looked like this:
    Code:
    localhost kernel: [33266.779159] akonadi_agent_l[10315]: segfault at 0 ip 00007f774a7e1856 sp 00007fff7c4549d0 error 4 in libQtCore.so.4.7.4[7f774a667000+280000]
    localhost kernel: [33266.808308] akonadi_agent_l[10316]: segfault at 0 ip 00007fc2de55c856 sp 00007fffdd15ee70 error 4
    localhost kernel: [33266.808314] akonadi_agent_l[10317]: segfault at 0 ip 00007f2a86427856 sp 00007fff3cda8dd0 error 4 in libQtCore.so.4.7.4[7fc2de3e2000+280000]
    localhost kernel: [33266.913378] akonadi_agent_l[10320]: segfault at 0 ip 00007f0754331856 sp 00007fffba5fb980 error 4 in libQtCore.so.4.7.4[7f07541b7000+280000]
    localhost kernel: [ 1221.804303] akonadi_agent_l[1100]: segfault at 7f00d517beb0 ip 00007f00e0091ba8 sp 00007fff80709ce8 error 4 in libQtGui.so.4.7.4[7f00dfcc0000+a41000]
    localhost kernel: [ 1221.810826] akonadi_agent_l[1101]: segfault at 7f910b102eb0 ip 00007f9116018ba8 sp 00007fff9fb5ab18 error 4 in libQtGui.so.4.7.4[7f9115c47000+a41000]
    localhost kernel: [ 1221.814405] akonadi_agent_l[1099]: segfault at 7f5d36b7eeb0 ip 00007f5d41a94ba8 sp 00007fff581ff618 error 4 in libQtGui.so.4.7.4[7f5d416c3000+a41000]
    localhost kernel: [ 1221.816889] akonadi_agent_l[1126]: segfault at 7f2889cf6eb0 ip 00007f2894c13ba8 sp 00007fff00bc8bf8 error 4 in libQtGui.so.4.7.4[7f2894842000+a41000]
    localhost kernel: [ 1238.003004] akonadi_agent_l[2229]: segfault at 0 ip 00007f83485f7856 sp 00007fff2cf0da80 error 4 in libQtCore.so.4.7.4[7f834847d000+280000]
    localhost kernel: [ 1238.034117] akonadi_agent_l[2227]: segfault at 0 ip 00007fb49d380856 sp 00007fffc189c5a0 error 4 in libQtCore.so.4.7.4[7fb49d206000+280000]
    localhost kernel: [ 1238.034192] akonadi_agent_l[2228]: segfault at 0 ip 00007f6d30203856 sp 00007fff927949f0 error 4 in libQtCore.so.4.7.4[7f6d30089000+280000]
    localhost kernel: [ 1238.128459] akonadi_agent_l[2232]: segfault at 0 ip 00007f049d674856 sp 00007fffffa2da00 error 4 in libQtCore.so.4.7.4[7f049d4fa000+280000]
    localhost kernel: [ 6382.271163] akonadi_agent_l[1174]: segfault at 7fd623ff7eb0 ip 00007fd6331e7ba8 sp 00007fffca875c98 error 4 in libQtGui.so.4.7.4[7fd632e16000+a41000]
    localhost kernel: [ 6382.278069] akonadi_agent_l[1175]: segfault at 7f03d6465eb0 ip 00007f03e137bba8 sp 00007fff524c96f8 error 4 in libQtGui.so.4.7.4[7f03e0faa000+a41000]
    localhost kernel: [ 6382.282640] akonadi_agent_l[1194]: segfault at 7f8720da4eb0 ip 00007f872bcc1ba8 sp 00007fff50a7d768 error 4 in libQtGui.so.4.7.4[7f872b8f0000+a41000]
    localhost kernel: [ 6382.284357] akonadi_agent_l[1176]: segfault at 7f3e72fd2eb0 ip 00007f3e7dee8ba8 sp 00007fffb11349e8 error 4 in libQtGui.so.4.7.4[7f3e7db17000+a41000]
    localhost kernel: [ 2267.195903] akonadi_agent_l[1211]: segfault at 7ff814283eb0 ip 00007ff81f199ba8 sp 00007fff07d510c8 error 4 in libQtGui.so.4.7.4[7ff81edc8000+a41000]
    localhost kernel: [ 2267.203174] akonadi_agent_l[1231]: segfault at 7fc6e8312eb0 ip 00007fc6f322fba8 sp 00007fffe4476888 error 4 in libQtGui.so.4.7.4[7fc6f2e5e000+a41000]
    localhost kernel: [ 2267.212038] akonadi_agent_l[1212]: segfault at 7f691fc9ceb0 ip 00007f692abb2ba8 sp 00007fff77a2f198 error 4 in libQtGui.so.4.7.4[7f692a7e1000+a41000]
    localhost kernel: [ 2267.212440] akonadi_agent_l[1213]: segfault at 7f726e6e6eb0 ip 00007f72795fcba8 sp 00007fff84d1a738 error 4 in libQtGui.so.4.7.4[7f727922b000+a41000]
    localhost kernel: [ 2268.737592] akonadi_agent_l[2999]: segfault at 0 ip 00007f1ae8d97856 sp 00007fff0eff22d0 error 4
    localhost kernel: [ 2268.737598] akonadi_agent_l[3000]: segfault at 0 ip 00007f3fcc155856 sp 00007fff20f53920 error 4 in libQtCore.so.4.7.4[7f3fcbfdb000+280000] in libQtCore.so.4.7.4[7f1ae8c1d000+280000]
    localhost kernel: [ 2268.737649] akonadi_agent_l[3002]: segfault at 0 ip 00007f97ebd72856 sp 00007fffeec31e60 error 4 in libQtCore.so.4.7.4[7f97ebbf8000+280000]
    localhost kernel: [ 2268.738366] akonadi_agent_l[3001]: segfault at 0 ip 00007fa927213856 sp 00007fff70c5fef0 error 4 in libQtCore.so.4.7.4[7fa927099000+280000]
    localhost kernel: [ 1572.431718] akonadi_agent_l[1145]: segfault at 7f214255feb0 ip 00007f214d475ba8 sp 00007fffeb58ea58 error 4 in libQtGui.so.4.7.4[7f214d0a4000+a41000]
    localhost kernel: [ 1572.431819] akonadi_agent_l[1147]: segfault at 7f082cc86eb0 ip 00007f0837b9cba8 sp 00007fffbc013808 error 4 in libQtGui.so.4.7.4[7f08377cb000+a41000]
    localhost kernel: [ 1572.440044] akonadi_agent_l[1146]: segfault at 7feca85deeb0 ip 00007fecb34f4ba8 sp 00007fffd6066f78 error 4 in libQtGui.so.4.7.4[7fecb3123000+a41000]4670
    etc.
    (The spoiler tags would be good sometimes)

    korganizer didn't sync my google calendar in 4.7.1 (and akonadikonsole segfaulted when I tried to find out why) and that has been fixed in 4.7.2. Yay.

    knode... Get a message rejected by the newsserver and edit it to send it again. It won't have the identity selected you have set in the knode preferences as default. I believe it will have the first identity in alphabetical order. Way to prevent leaking a private email address into usenet.

    akregator... I still can provoke a crash. And it sometimes fails to even put the feeds into the right category. Feeds from Scienceblogs.com sometimes get duplicated into blog.fefe.de for example...

    Guess what happens when you put a calculation that will take a long time to calculate in the qualculate plasmoid? Indeed, it freezes the whole plasma-desktop inclusive the panel(s) while it is calculating. Ever heard of threads?

    Desktop Effects are still not as performant as they should be. I do feel that the OpenGL (and GLES) effects are much slower than XRender with an i5 480M@2,67 ghz + HD 6550 on mid profile with mesa git which I believe should not be the case. Were there not people telling us that kwin did not have performance problems? How come they will get fixed then?
    Full credits go to Alex Fiestas for complaining about the performance in a way that I wanted to do something about it, instead of being just annoyed and ignoring the comment!Alex’s complaints…


    Oh and kdm can still not open kwallet on login.
    Feature Request from 2004 (!): http://bugs.kde.org/show_bug.cgi?id=92845


    Don't get me wrong: KDE is an awesome project. With KDE 4.7 I have changed from XFCE to KDE and have used it nearly daily since then. It is not unusable anymore. But nobody can deny that it has tons of issues. Just look at some of the still open bug reports. It's just that they are not so grave to make it unusable anymore.
    As for plasma active: Yes, amazing. But only if it works well. I do have to wonder whether KDE can afford to maintain yet another project as the work on the main tools is not yet done...
    Not to say they don't make progress. For example in 4.7.1 plasma-desktop would segfault when trying to set it to the grid workspace. In 4.7.2 it finally works.
    Last edited by ChrisXY; 09 October 2011, 06:00 PM. Reason: damn, get some vertical scrolling in code tags

    Comment


    • #12
      Originally posted by ChrisXY View Post
      Code:
      yaourt -S strigi-git

      Comment


      • #13
        I'm going to have to agree with all of the KDE hate. Apparently they're only interested in having a usable desktop experience with the Nvidia blob. It seems nice from the screenshots, but when you try to use it, you realize that they never gave a damm about testing Kwin with the oh-so-popular Radeon drivers, or even the AMD blob. I always go back and try it about once a year, and it's always crap.

        Comment


        • #14
          I been using IceWM as my window manager...no more silly KDE bugs and crashes. KDE apps just run fine under IceWM.

          Comment


          • #15
            Originally posted by nepwk View Post
            I'm going to have to agree with all of the KDE hate. Apparently they're only interested in having a usable desktop experience with the Nvidia blob. It seems nice from the screenshots, but when you try to use it, you realize that they never gave a damm about testing Kwin with the oh-so-popular Radeon drivers, or even the AMD blob. I always go back and try it about once a year, and it's always crap.
            Just for a bit of balance, I'm going to call posters on the faux KDE hate.

            KDE works perfectly for me with the Xorg Radeon drivers (r600g), across a number of different machines.

            In fact with Kubuntu 11.10 and kubuntu-low-fat-settings installed, it even works slick, fast and stable on my low-resource netbook. It is actually much faster than the Windows 7 desktop that came with the machine.

            Comment


            • #16
              I normally use kde on opensuse and as a de it seems very stable. Runs great on both catalyst and intel graphics drivers for me.

              That said if you talking about kde apps, I have had many issuses. Amarok has been very buggy for me. When working its my fav music player but if it breaks dramatically with new versions thats a problem. Choqok, which I dont think is offical kde but is the default twitter client in opensuse and other kde distros, has been buggy to an extent that helps makes the kde expiriance look bad. I've had many issues with korganizer, rekonq and other apps. Usability wise kwallet sucks. I think I read somewhere about it being replaced. If so that would be long overdue.

              Comment


              • #17
                Originally posted by hal2k1 View Post
                Just for a bit of balance, I'm going to call posters on the faux KDE hate.
                For the record: I don't hate KDE.

                Originally posted by hal2k1 View Post
                KDE works perfectly for me with the Xorg Radeon drivers (r600g), across a number of different machines.
                How can it work "perfectly" when there are those open bugreports? For me it only works well enaugh. I probably would still recommend XFCE for a less annoying desktop.

                Graphically it is mostly fine with r600g, yet the OpenGL compositing as well as the GLES compositing feel a bit slow compared with XRender compositing. But I guess with 4.8 this will be fixed.

                Comment


                • #18
                  Originally posted by ChrisXY View Post
                  How can it work "perfectly" when there are those open bugreports? For me it only works well enaugh. I probably would still recommend XFCE for a less annoying desktop.
                  Lots of bugs are really hardware-specific. Someone using one hardware and software setup may have them while someone using a very similar setup may not.

                  Comment


                  • #19
                    I don't really understand how this thread could become so off-topic, but well I comment nevertheless

                    Originally posted by nepwk View Post
                    Apparently they're only interested in having a usable desktop experience with the Nvidia blob. It seems nice from the screenshots, but when you try to use it, you realize that they never gave a damm about testing Kwin with the oh-so-popular Radeon drivers, or even the AMD blob. I always go back and try it about once a year, and it's always crap.
                    I am sure that you are aware of the fact that one of the KWin developers is also an active contributor to the radeon driver, right? You are also aware that the maintainer of KWin is using the r600g on his productive environment and you are probably also aware of the fact that the OpenGL ES 2 port has been developed on nouveau and that the NVIDIA blob does not even support that.

                    The only true part of your comment is that we have hardly any support for the ATI blob as we consider our time best spent by improving support for the free drivers. Also the ATI blob is the only driver which does not support anything more modern than OpenGL 1 for Compositors.

                    Comment


                    • #20
                      Originally posted by mgraesslin View Post
                      the OpenGL ES 2 port has been developed on nouveau and that the NVIDIA blob does not even support that.
                      It does via oGL 4.1 support. It is one of the specs of 4.1 and the blobs have supported it for a while.

                      OpenGL vendor string: NVIDIA Corporation
                      OpenGL renderer string: GeForce GTX 580/PCI/SSE2
                      OpenGL version string: 4.2.0 NVIDIA 285.05.09
                      OpenGL extensions:
                      GL_ARB_base_instance, GL_ARB_blend_func_extended,
                      GL_ARB_color_buffer_float, GL_ARB_compatibility,
                      GL_ARB_compressed_texture_pixel_storage, GL_ARB_conservative_depth,
                      GL_ARB_copy_buffer, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp,
                      GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend,
                      GL_ARB_draw_indirect, GL_ARB_draw_elements_base_vertex,
                      GL_ARB_draw_instanced, GL_ARB_ES2_compatibility,
                      Last edited by deanjo; 10 October 2011, 03:02 PM.

                      Comment

                      Working...
                      X