Screen Freeze on Leap 42.2 only option is reboot

Hi there,

I’m getting a screen freeze about once or twice a day since i upgraded to Leap 42.2 from 42.1, the mouse still works but I cannot click anything or use the keyboard, other processes still seem to be running such as music playing.

leaving it a while doesn’t help, I gone out for a few hours and came back to it locked up. The only answer is to do a reboot by manually pushing the bitton on my PC.

I have a HP p6-2260ea

This is my graphics;

09: PCI 02.0: 0300 VGA compatible controller (VGA)
[Created at pci.378]
Unique ID: _Znp.12NBFg9BiwF
SysFS ID: /devices/pci0000:00/0000:00:02.0
SysFS BusID: 0000:00:02.0
Hardware Class: graphics card
Device Name: “Onboard IGD”
Model: “Intel 2nd Generation Core Processor Family Integrated Graphics Controller”
Vendor: pci 0x8086 “Intel Corporation”
Device: pci 0x0102 “2nd Generation Core Processor Family Integrated Graphics Controller”
SubVendor: pci 0x103c “Hewlett-Packard Company”
SubDevice: pci 0x2ada
Revision: 0x09
Driver: “i915”
Driver Modules: “drm”
Memory Range: 0xf7800000-0xf7bfffff (rw,non-prefetchable)
Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable)
I/O Ports: 0xf000-0xf03f (rw)
IRQ: 31 (76715 events)
Module Alias: “pci:v00008086d00000102sv0000103Csd00002ADAbc03sc00i00”
Driver Info #0:
Driver Status: i915 is active
Driver Activation Cmd: “modprobe i915”
Config Status: cfg=new, avail=yes, need=no, active=unknown

Primary display adapter: #9

Really hope you can help as otherwise I will have to go back to Leap 42.1 or try another Distro.


** Bump **


I have same problem.
Plasma on Intel graphics.
Desktop effects enable. Desktop theme - openSUSE or Breeze.

How did you perform the upgrade?
Any theming stuff active apart from the defaults?
Output from

zypper lr -d

, between CODE tags, the # in the layout ribbon, please

for plasma 5 to work on intel graphics you need to use/force uxa acceleration
make the file /etc/X11/xorg.conf.d/20-intel.conf

kdesu kate /etc/X11/xorg.conf.d/20-intel.conf

then paste this and save it

Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "AccelMethod"  "uxa"

Installed with just the defaults, I did have Leap 42.1 but I had some minor problems so I decided to do a fresh install from an ISO image, of course it recognised the partitions, secure boot etc. but it was effectively a start from scratch install.

This is the output, I hope this is what you meant.

| Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service

1 | PlexRepo | PlexRepo | No | ---- | No | 99 | NONE | |
2 | | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | |
3 | | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | |
4 | | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | |
5 | | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | |
6 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | 99 | rpm-md | |
7 | | openSUSE:Leap:42.2:Update | Yes | (r ) Yes | Yes | 99 | rpm-md | |
8 | openSUSE-42.2-0 | openSUSE-42.2-0 | No | ---- | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-hp_DVD_A_DH16ACSH_388217917322 |
9 | | Packman Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | |
10 | repo-debug | openSUSE-Leap-42.2-Debug | No | ---- | Yes | 99 | NONE | |
11 | repo-debug-non-oss | openSUSE-Leap-42.2-Debug-Non-Oss | No | ---- | Yes | 99 | NONE | |
12 | repo-debug-update | openSUSE-Leap-42.2-Update-Debug | No | ---- | Yes | 99 | NONE | |
13 | repo-debug-update-non-oss | openSUSE-Leap-42.2-Update-Debug-Non-Oss | No | ---- | Yes | 99 | NONE | |
14 | repo-source | openSUSE-Leap-42.2-Source | No | ---- | Yes | 99 | NONE | |
15 | repo-source-non-oss | openSUSE-Leap-42.2-Source-Non-Oss | No | ---- | Yes | 99 | NONE | |


I’ll give this a go and see what happens.


Same here on Intel Graphic ( Lenovo E330)

I’ll give this a go too and let you know.
Many thanks anyway !

Thanks! Very! Very mach!!
I added this file and later I will look what will turn out

Same here but on a HP 6320nc. I will give the fix a try.

/Tomas Jensen

I’ve same problem too after upgrade to 42.2. I heard about intel bug (and thks for information), but what interesting for me: why I haven’t same problem with 42.1?

No, this error occurred at me in prior version, but is much more rare, 1-2 times a week. Now it occurs each 2 - 4 hours.

Option “uxa” solve this problem for me. Today my desktop work without problem, but I read that didn’t finish testing yet.

in “man 4 intel” about “uxa”:
…It is in the process of being superseded by “SNA” (Sandybridge’s New Acceleration)…
…Default: use SNA (render acceleration)

Here therefore often there are problems…

I have the same problem on a ThinkPad and what’s interesting is that it never occurred while I was testing the Leap 42.2 betas, including the final release candidate. I’ve never experienced this issue with 42.1.

I had high hopes for the 42.2 release and this is very disappointing. I have abandoned openSUSE for now, in favor of another (more stable) Linux distro.

this has nothing to do with opensuse but with intel, on every distro using the Linux kernel to avoid crashes under plasma 5 you’ll need to use uxa as the intel driver is part of the Linux kernel not the distribution.
if you want to use sna and plasma 5 there are other solutions, one is to use a different window manager like
with openbox-kde
or compiz
or disable compositing under plasma 5

The graphics stack is more complicated then there being “a” (single) driver for the hardware. (And while it is still more complicated then this,) The major components are:
[li]the kernel driver … the intel hardware kernel driver is “i915” … only this is a part of the linux kernel [/li][li]the userspace components:[/li][LIST]
[li]the Xorg driver (in case of using X as your display server, and which is not applicaple to use of the Wayland display server) … the intel hardware xorg driver is “intel” … but there are others that can be used too[/li][LIST]
[li]uxa and sna are acceleration methods tied to the intel xorg driver, not the intel (i915) kernel driver [/li][/ul]

[li]the 3D drivers (which for the oss drivers is Mesa, which provides for your openGL and, very recently, Vulkan needs) … the intel hardware Mesa driver is “i965” [/li][/LIST]

All three layers get updated over the course of time. Different distros (and their respective releases e.g. Leap42.1, Leap42.2 RC2 or …) may (and that’s much more probably a “do”, as opposed to a “may”) contain different versions of those components.

This bug would seem to be a regression on top of an existing problem. As they say, “stuff happens” … or something like that.

For the record, I’m on TW with my intel based laptop and it has been affected by “the freeze” for a while – originally, it was an infrequent occerence, as several of you noticed with your respective distro release, but more recently, it’s become very frequent (i.e. now its a bloody PITA … its a coin flip of whether or not it will freeze just after logging in … and even if that’s successful, a freeze usually isn’t too far off (typically within the hour)).

there are other solutions

and yet another solution you can try is to forgo using the intel xorg driver and, instead, use alternative xorg driver solutions

[li]the generic xorg “modesetting” driver … it will work in conjunction with the i915 kernel (kms - kernel mode setting) driver, and will make use of glamor (another acceleration scheme, analogous to what uxa and sna do, but does so by using openGL i.e. it hooks into the i965 Mesa driver to do the dirty work) … while YMMV, I’d bet that most would not likely notice a difference between running this over a “bug free” intel [/li][li]or use the fbdev xorg driver … boot under “recovery mode” and this is what you’ll get … note that it has no acceleration capabilities and can’t make use of the 3D driver. [/li][/ul]

It is not true that Plasma 5 has this problem, generally. If version 5.7 is not ready for prime time without hacks by the user, then it should not have been incorporated into the openSUSE Leap 42.2 repositories.

plasmashell 5.5.x on openSUSE Leap 42.1 – works fine

plasmashell 5.5.x on Kubuntu 16.04 – works fine

plasmashell 5.5.x on Fedora 23 – works fine

plasmashell 5.6.x on LinuxMint 18 – works fine

plasmashell 5.7.x on openSUSE Leap 42.2 – crashes

How to accomplish this?

Similar to the instructions in post #5 of this thread … for that matter, it might be good to just recycle that suggested intel file (so that, down the road if you want to change something, you’ll easily know exactly where you’ve made the changes)

Empty the contents and then add something like the following:

Section "Device"
        Identifier "Xorg Modesetting Driver "
        Driver "modesetting"

The identifier can be whatever your heart feels like. It’ll use glamor by default, so you don’t need to list the acceleration option. If you have further needs, see “man modesetting”. You’ll have to log out or reboot for the change to take affect

I agree. But it certainly has existed (outside of your own experiences) for a while, and has certainly become worse recently. For example, on TW, which has been using 5.8.x for several months, its only been in the 5.8.4 time period that its become insufferable for me.

That said, I don’t think all intel chipsets are impacted (or, at least, equally). Whether the fault lies in the intel xorg driver or rests with Plasma is not clear to me (I haven’t spent any time looking into it).

If version 5.7 is not ready for prime time without hacks by the user, then it should not have been incorporated into the openSUSE Leap 42.2 repositories.
Didn’t you say so yourself that you didn’t experience any problems in the late 42.2 RC?

The information above includes a typo. The buggy version of Plasma is 5.8.3:

plasmashell 5.8.3 on openSUSE Leap 42.2 – crashes (freezes)