[0.12.29+][Linux] Factorio kills KWin Desktop setup

[bohne2k7]

Since today, i.e. 0.12.30, Factorio (through Steam) kills my dual-screen, multi-(virtual)-desktops setup under Linux (openSUSE Leap 42.1) with KDE Frameworks 5.20.0.

Setup:
As seen from log, I have two physical screens with different resolution, the larger being the primary screen.
In addition, I'm using multiple (4) virtual desktops.

Up to and including version 0.12.29 I could start Factorio on any virtual desktop on the primary screen in fullscreen and switch between the virtual desktops (via shortcut) without hazel (and Factorio even noticing).

Problem:
When I start Factorio in fullscreen, the loading screen starts correctly in fullscreen on the primary monitor, but around the 30-60% progress bar, the virtual desktops somehow get killed and I'm not any more able to switch between the virtual desktops with the configured shortcut (e.g. [Ctrl]+[F1-4] in my case). Factorio succeeds loading. When I quit Factorio, the virtual desktops keep broken. Relogging into my user account does fix it.

Factorio Log

0.000 2016-04-06 22:04:46; Factorio 0.12.30 (Build 17998, linux64, steam)
0.043 Operating system: Linux (SUSE LINUX 42.1)
0.043 Program arguments: "/home/tobbe/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio"
0.043 Read data path: /home/tobbe/.local/share/Steam/steamapps/common/Factorio/data
0.043 Write data path: /home/tobbe/.factorio
0.043 Binaries path: /home/tobbe/.local/share/Steam/steamapps/common/Factorio/bin
0.049 Graphics options: [FullScreen: true] [VSync: false] [UIScale: 95%] [MultiSampling: OFF] [Graphics quality: normal] [Video memory usage: all] [Light scale: 100%] [Screen: 255]
0.148 Available display adapters: 2
0.148 [0]: resolution 1920x1080px at [0,0]
0.148 [1]: resolution 1680x1050px at [1920,0]
0.148 Create display on adapter 0. Size 1280x720 at position [310, 162].
0.419 Initialised OpenGL:[0] Gallium 0.4 on AMD CAPE VERDE (DRM 2.42.0, LLVM 3.7.0); driver: 3.0 Mesa 11.0.8
0.478 Loading mod core 0.0.0 (data.lua)
0.479 Loading mod base 0.12.30 (data.lua)
0.514 Loading mod FARL 0.5.17 (data.lua)
0.545 Loading mod Landfill 2.1.7 (data.lua)
0.576 Loading mod RailTanker 1.1.3 (data.lua)
0.604 Loading mod STRS 0.0.5 (data.lua)
0.634 Loading mod TrainOutpost 0.9.0 (data.lua)
0.673 Loading mod 8L-Train-Project 1.1.0 (data.lua)
0.701 Loading mod FARL 0.5.17 (data-updates.lua)
0.729 Loading mod TrainOutpost 0.9.0 (data-updates.lua)
0.769 Loading mod FARL 0.5.17 (data-final-fixes.lua)
0.797 Checksum for core: 3711505753
0.797 Checksum for mod base: 2829195351
0.797 Checksum for mod FARL: 1534116067
0.797 Checksum for mod Landfill: 4029589584
0.797 Checksum for mod RailTanker: 166006525
0.797 Checksum for mod STRS: 3816178630
0.797 Checksum for mod TrainOutpost: 1945578081
0.797 Checksum for mod 8L-Train-Project: 1662010032
1.022 Initial atlas bitmap size is 16384
1.023 Created atlas bitmap 16384x9557
6.251 Sprites loaded
6.251 Loading sounds...
7.459 Factorio initialised
39.784 Steam API shutdown.
39.785 Goodbye

Unfortunately, I haven't a log from 0.12.29 laying around as I've already tried it multiple times with 0.12.30, thus factorio-previous.log is identical to this one.

Edit [7.4.2016]: updated title

[kovarex]

I'm sorry, but I have no idea, how could Factorio make the virtual desktop fail, we didn't make any changes to the graphics library aside mac.
I'm moving it to 1/0 magic.

[bohne2k7]

Thanks for the reply. I'll dig little bit into that and try launching 0.12.29 and 0.12.30 without Steam. When I think about it a little further, it might be affected/caused by some Linux/KDE packages updated between 0.12.29 and 0.12.30.

[bohne2k7]

Tracked it down to a segfault of KWin with both 0.12.29 and 0.12.30. Seems to be not related exclusively to Factorio. Most of the KDE packages got updated on 5th April after/during I've played 0.12.29 the last time without issues.

This issue can be closed as not-a-Factorio-bug, I guess.

[daniel34]

This issue can be closed as not-a-Factorio-bug, I guess.

Moved to Not a bug.

[LD100]

Since 15.33 I have this bug again (it worked for me before).

@bohne2k7 did you open a kwin issue?

[golfmiketango]

Since 15.33 I have this bug again (it worked for me before).

@bohne2k7 did you open a kwin issue?

A lot of times if your window manager goes tits-up, you will find a clear-ish explanation of what happened in the Xorg logs. For most people, I think that's /var/log/Xorg.0.log. You could also check the output of dmesg, your "main" system logs (if you have systemd try running "sudo journalctl", and ~/.xsession-errors).

This type of thing could very well be some kind of video-driver-level problem. I haven't noticed anything change in my multi-monitor behavior in 0.15.33 and I run KDE Frameworks 5 with full opengl compositing (however I tick the box that says "programs can disable compositing" or whatever; factorio does turn my compositing off.

[golfmiketango]

Actually I just remembered another thing about my setup. I have a kwin rule for factorio under System Settings->Window Management->Window Rules. IIRC it is a relic from before factorio had the option to control what monitor it wound up on in full screen mode. It matches all windows types, "Window Class(application): exact match="factorio factorio", and the rule it enforces is under the size and position tab: "Position: force: 0,0." No wonder I've never had to mess around with the factorio multi-monitor settings, I'll bet that rule has been doing all the work for me this whole time.