Slashdot Mirror

← Back to Stories (view on slashdot.org)

KDE Plasma 5 Problem Traced To Bug In Intel Graphics Driver

Posted by timothy on from the where's-the-glitch dept.

prisoninmate writes with news that certain complaints about the KDE Plasma 5 desktop environment may not be KDE's fault at all: Apparently, KDE Plasma 5 runs just fine, and the issue is related to a serious Intel Graphics Driver Stack bug. The good news is that a workaround for the bug is already available, and it requires you to modify the /etc/X11/xorg.conf.d/20-intel.conf file from your Linux kernel-based operating system, by switching back to the older UXA acceleration method instead of the default SNA method used in many distros.

8 of 56 comments (clear)

  1. SystemD by kimvette · · Score: 2, Funny

    Some of have SystemD and don't have /etc/X11, you insensitive clod!

    --
    The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    1. Re:SystemD by Anonymous Coward · · Score: 4, Funny

      what is this mysterious "/etc" everyone is talking about? the systemd nightlies don't have this. is it part of the deprecated "directory" system?

    2. Re:SystemD by binarylarry · · Score: 2, Funny

      I usually use systemdedit, its a pretty capable text editor built into systemd.

      --
      Mod me down, my New Earth Global Warmingist friends!
  2. Re:Why would a graphics driver bug... by Viol8 · · Score: 2

    Oddly enough windows are moved around all the time. There must be something specific they're doing here wrt switching desktops since apparently the crash doesn't happen at other times.

  3. Re:If you want something done right... by goarilla · · Score: 2

    You forgot to include Docker somewhere.

  4. Re:Why would a graphics driver bug... by gstoddart · · Score: 2

    You are the one saying this is just a move. Did you write the code? Do you know what it does?

    Or are you just naively deciding the bug must be in moving windows because that's what you think it is?

    There's a lot of pieces to a window manager and a graphic driver.

    Obviously, some of these are interacting and causing the crash. Saying must be something specific ... well, that's the nature of bugs, you have to do the right things to trigger them.

    If it was "just moving windows", the crash would happen all the time. Which means it's probably more complicated than your oversimplified explanation.

    --
    Lost at C:>. Found at C.
  5. Are you sure it's Intel? by danomac · · Score: 2

    Considering we had a Samsung firmware bug in TRIM that turned out to not to be an issue with Samsung drives, but with the TRIM code itself.

  6. Re:taskbar by Tapewolf · · Score: 2

    just installed Kububtu 15 with plasma. yikes, there's no task bar or "start"-like menu anymore. How do I get back those interface features I'm comfortable with?

    You may need to add a few widgets to do this, I think you can right-click to bring up the appropriate menu. It was a bit of a nuisance but in about 10 minutes or so I was able to get a reasonably good start menu and taskbar. It was disappointing that it didn't import the profile and layout from v4, though.

    I could probably look up exactly how it was done, but right now I've switched to XFCE for the time being, because Plasma 5 crashes if you look at it funny. This on an nVidia card with the proprietary drivers so I think there's more to this than a bug in the Intel driver.

    One important thing to note is that Plasma 5 drops support for the little systray icons, apparently they were powered by the XEmbed system which is considered deprecated. This means things like Dropbox and WINE applications which use the systray won't appear. There are workarounds for this (alternate libraries that implement a systray) and in the case of Dropbox it looks like they've recently added support for whatever new library or protocol replaces it.