Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
Graphics Bug Intel KDE Hardware

KDE Plasma 5 Problem Traced To Bug In Intel Graphics Driver 56

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.
This discussion has been archived. No new comments can be posted.

KDE Plasma 5 Problem Traced To Bug In Intel Graphics Driver

Comments Filter:
  • SystemD (Score:2, Funny)

    by kimvette ( 919543 )

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

    • Re:SystemD (Score:4, Funny)

      by Anonymous Coward on Thursday August 06, 2015 @10:07AM (#50262533)

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

    • The /etc/X11/ dir is optional on any recent Xorg versions, this is not related to systemd or the init system in any way. If/when you need to start making customizations to the default Xorg setup, you *can* do it in /etc/X11/ .
      • Yes yes yes of course... lots of aspies on here.

        I thought ", you insensitive clod!" was a good clue that I was just talking shit to be funny.

  • ...and I still think that plasma 5 is not ready for prime time (to put it mildly)
  • by dos1 ( 2950945 )

    I feel a bit bad now, because around week/two weeks ago I managed to find it out by myself that switching to UXA fixed the crashes on my machine. Looks like I should have made some fuss about it!

    • by Anonymous Coward

      It ain't a bad thing, if you find a fix or workaround and make a little fuss.

  • ... cause a crash when desktops are switched? All that does is move windows from onscreen to off and vice verca. What the hell is KDE doing with the X server than means this happens anyway?

    • Oddly enough ... desktops are rendered in graphics, and bugs cause strange behavior because nobody planned for them.

      There's probably tons of things which can go wrong when your graphics driver has bugs in it.

      • by Viol8 ( 599362 )

        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.

        • by Anonymous Coward

          Where do you get the idea that the crash doesn't happen at other times? I looked around and see reports from a month ago of XBMC on GNOME crashing on startup, and mpv player crashing after watching a video for a bit, all originating from the same point in the same driver. There's a bug in Intel's new SNA driver and this causes various failures in otherwise-working code which happens to rely on the driver; switching to Intel's older UXA driver fixes the problem.

        • 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 t

          • by Viol8 ( 599362 )

            FYI I've written a window manager. Switching desktops involves nothing more than moving the correct windows on and off screen. You can't unmap them because that generates a different event which the applications might respond to incorrectly in the circumstances.

    • ... cause a crash when desktops are switched? All that does is move windows from onscreen to off and vice verca. What the hell is KDE doing with the X server than means this happens anyway?

      Bugs like that are discovered when you actually starts using new features to render things more hardware accelerated. If no major application used it before, it is common to uncover bugs in drivers. The alternative though is not use new features.

    • 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?

      • by Teun ( 17872 )
        You must have mistaken Win8 for Kubuntu Plasma.
        Because Plasma is in every respect a traditional DE but then with a new engine.
        That admittedly requires some tuning.
      • 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 dr

  • by Anonymous Coward

    Once a upon a time, Intel used to be the answer to users questions about which graphics hardware would work best on a new linux installation. It was never the fastest hardware, but it had the reputation for being the most stable with adequate performance for ordinary desktop use. That doesn't seem to be the case anymore with high performance desktop shells exposing more and more flaws with Intel's graphic stack.

    • by AaronW ( 33736 )

      I have never found Intel graphics hardware to be the most stable for Linux, far from it. For years I had a lot of problems with Intel graphics such as every time my laptop went into standby the graphics would never recover. At work I had two identical desktops and with the same image I could only get X11 to work on one of them and then it refused to support the monitor's resolution. The other identical machine would just lock up. I dropped in nVidia cards and suddenly everything worked well. It just worked

  • by Anonymous Coward

    You have to do it yourself.

    If I were a KDE dev, I would write a display server in house, bundle it with LibreOffice, then roll the whole thing into systemd. Then we could finally ditch those pesky operating systems all together.

    Just think of how easy ps output would be to read.

  • by danomac ( 1032160 ) on Thursday August 06, 2015 @01:53PM (#50264153)

    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.

    • The Samsung firmware bug is still there, in the Samsung drives. In addition there was a bug in the RAID0/10 TRIM code which Samsung fixed.

      So no, we did not have a Samsung firmware bug in TRIM that was not an issue with Samsung drives.

  • How about using glamor instead of uxa? Does that work around it too, or is the bug just so rare I haven't noticed it?

    I run KDE plasma 5, have been using glamor for a long while, and am running the xorg-edgers drivers... and I haven't seen anything like the bug described at kde.org.

  • I'm going to regret asking but.. is KDE talking directly to the graphics drivers? I knew the situation with X on a programming level was bad but.. that bad?

    Is that why starting with version 4 KDE has worked terribly (if at all) in VNC? Is it because it wants to talk directly to the hardware's drivers and VNC is something other than hardware?

    - Forgive me if the KDE/VNC situation has improved, I stopped using KDE in part because of this over a year ago.

  • I've used KDE for a while, from 3 through 5. 4 worked really well and when I got the upgrade to 5, I thought that I finally had the perfect desktop - if it worked like 4 and looked like 5, I'd be ecstatic.
    Unfortunately, I found it to be overall a little sluggish to start and that deteriorated over time to the often reported states of coming out of screensaver to a black screen with cursor for a minute before anything would show; a programs menu which would take 30 seconds to open the first time, no matter h

"The number of Unix installations has grown to 10, with more expected." -- The Unix Programmer's Manual, 2nd Edition, June, 1972

Working...