Fedora Linux Support Community & Resources Center
  #1  
Old 23rd November 2016, 03:53 PM
adventurer Offline
Registered User
 
Join Date: Nov 2016
Location: Germany
Posts: 20
macoschrome
[SOLVED] KDE workspace broken since kernel 4.8.7

Hello everybody,

I'm new to this forum but have been a happy Fedora KDE user for about a year.

When I was still on Fedora 24 everything was fine up to kernel 4.8.6. After getting 4.8.7 (and a couple of days later 4.8.8) it got weird:

On the login screen I couldn't see the mouse cursor anymore. And when I input my password in the password field no dots were displayed like before. But I was able to login. However, the workspace was broken. The background image was vanished, conky wouldn't start, and there was no panel anymore. If I tried to create a new panel the workspace got dark and unresponsive. The only way to reboot was ctrl-alt-f2 and login on the console.

The funny thing was that everything was fine when I booted with the 4.8.6 kernel. I could even see the under 4.8.8 newly created panel at the top of the workspace

Then I decided to not upgrade to Fedora 25 but install it anew. I formatted the root partition, kept my home partition but renamed the ~/.kde and ~/.config folders just in case. The installation was hassle-free. The KDE workspace was as it should - but hey, the iso came with kernel 4.8.6! Once I updated the system to kernel 4.8.8 the problems I had in Fedora 24 were back.

I removed xorg-x11-drv-intel to make sure that that driver one was not the culprit - but to no avail.

Here's my configuration. lspci -nnk | grep -A3 -i vga says:
Quote:
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915
inxi says:

Code:
System:    Host: HANNIBAL Kernel: 4.8.6-300.fc25.x86_64 x86_64 (64 bit gcc: 6.2.1)
           Desktop: KDE Plasma 5.8.1 (Qt 5.7.0) Distro: Fedora release 25 (Twenty Five)
Machine:   Device: desktop Mobo: ASUSTeK model: Z170 PRO GAMING v: Rev X.0x
           UEFI [Legacy]: American Megatrends v: 2003 date: 09/19/2016
CPU:       Quad core Intel Core i7-6700K (-HT-MCP-) cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 32064
           clock speeds: max: 4300 MHz 1: 799 MHz 2: 799 MHz 3: 800 MHz 4: 800 MHz 5: 799 MHz 6: 3906 MHz
           7: 800 MHz 8: 3376 MHz
Graphics:  Card: Intel HD Graphics 530 bus-ID: 00:02.0
           Display Server: Fedora X.org 118999.2 drivers: (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz
           GLX Renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2)
           GLX Version: 3.0 Mesa 12.0.3 Direct Rendering: Yes
Audio:     Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.8.6-300.fc25.x86_64
Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6
           IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 1256.3GB (42.4% used) ID-1: /dev/sda model: WDC_WD10EZEX size: 1000.2GB temp: 33C
           ID-2: /dev/sdb model: Samsung_SSD_840 size: 256.1GB temp: 24C
Partition: ID-1: / size: 26G used: 5.6G (23%) fs: ext4 dev: /dev/sdb1
           ID-2: /home size: 168G used: 96G (60%) fs: ext4 dev: /dev/sdb2
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 250 Uptime: 1:12 Memory: 2175.3/15938.4MB Init: systemd runlevel: 5 Gcc sys: 6.2.1
           Client: Shell (bash 4.3.431) inxi: 2.3.3
Am I really the only KDE user with this problem? Do you have any suggestions how to solve my problem?

EDIT: some additional info.

journalctl -b | grep i915 with kernel 4.8.6 gives:

Quote:
Nov 23 14:10:59 localhost.localdomain kernel: [drm:i915_gem_init_stolen [i915]] *ERROR* conflict detected with stolen region: [0xc6000000 - 0xc8000000]
Nov 23 14:10:59 localhost.localdomain kernel: [drm] Finished loading i915/skl_dmc_ver1_26.bin (v1.26)
Nov 23 14:10:59 localhost.localdomain kernel: [drm] Initialized i915 1.6.0 20160711 for 0000:00:02.0 on minor 0
Nov 23 14:10:59 localhost.localdomain kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Nov 23 14:11:03 HANNIBAL kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
However, with kernel 4.8.8. I got:

Quote:
Nov 23 15:57:36 localhost.localdomain kernel: [drm:i915_gem_init_stolen [i915]] *ERROR* conflict detected with stolen region: [0xc6000000 - 0xc8000000]
Nov 23 15:57:36 localhost.localdomain kernel: [drm] Finished loading i915/skl_dmc_ver1_26.bin (v1.26)
Nov 23 15:57:36 localhost.localdomain kernel: [drm] Initialized i915 1.6.0 20160711 for 0000:00:02.0 on minor 0
Nov 23 15:57:37 localhost.localdomain kernel: [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many full retries, give up
Nov 23 15:57:37 localhost.localdomain kernel: [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many full retries, give up
Nov 23 15:57:37 localhost.localdomain kernel: [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many full retries, give up
Nov 23 15:57:37 localhost.localdomain kernel: [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many full retries, give up
Nov 23 15:57:37 localhost.localdomain kernel: [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many full retries, give up
Nov 23 15:57:37 localhost.localdomain kernel: [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many full retries, give up
Nov 23 15:57:37 localhost.localdomain kernel: [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many full retries, give up
Nov 23 15:57:37 localhost.localdomain kernel: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to train DP, aborting
Nov 23 15:57:37 localhost.localdomain kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Nov 23 15:57:39 HANNIBAL kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

Last edited by adventurer; 8th December 2016 at 06:30 PM. Reason: Marking as solved
Reply With Quote
  #2  
Old 23rd November 2016, 04:37 PM
CSchwangler Offline
Registered User
 
Join Date: Feb 2009
Posts: 2,747
linuxfedorafirefox
Re: KDE workspace broken since kernel 4.8.7

This is very interesting. I have a F24 KDE with the latest kernel from updates testing and it runs without issues. It is running on a ThinkPad X220 with Intel Core i7-2620M and HD Graphics 3000.
Another machine is more close to your specs

Code:
00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Pro Graphics 580 [8086:193b] (rev 09)
	Subsystem: Intel Corporation Device [8086:2064]
	Kernel driver in use: i915
	Kernel modules: i915
It runs F25 with Kernel 4.8.8-300.fc25.x86_64, but it runs on the Mate desktop environment and it also has no problems.
Both systems run with minimal graphical effects. So, I am wondering if maybe you have graphical effects enabled, which are causing these problems.
I am not sure whether you already have Wayland installed? Both of my systems are not using Wayland. On Gnome there is an option to use traditonal X11. Could you check if there is a similar option for KDE and, if yes, try that instead?
Reply With Quote
  #3  
Old 23rd November 2016, 04:53 PM
adventurer Offline
Registered User
 
Join Date: Nov 2016
Location: Germany
Posts: 20
macossafari
Re: KDE workspace broken since kernel 4.8.7

Thank you very much for your reply!

Quote:
Originally Posted by CSchwangler View Post
Both systems run with minimal graphical effects. So, I am wondering if maybe you have graphical effects enabled, which are causing these problems.
Which changes do you suggest? I already tried to switch from OpenGL to Xrender but that didn't help. Besides, I wonder if changing those settings would explain that different behavior on different kernel versions ...

Quote:
I am not sure whether you already have Wayland installed?
No, I haven't. AFAIK, it's only activated by default for the Gnome version of F25. I must admit that right now I don't even know how I would have to do it. It might be worth a try.
Reply With Quote
  #4  
Old 26th November 2016, 06:24 PM
Bequimao Offline
Registered User
 
Join Date: Nov 2016
Location: Germany
Posts: 1
linuxfedorafirefox
Re: KDE workspace broken since kernel 4.8.7

I have upgraded Fedora 24 KDE to Fedora 25 and the same or similar issue.

The display manager sddm worked fine, and I could not spot any issue at boot. After logging in my primary user I had only a cursor over a black background. A secondary user and a newly created user worked as expected. I did not test any older kernel.

But I could resolve the problem by copying ~/.config/plasma* and ~/.config/kwin* from the newly created user to my original user. I do not know what exactly caused the issue in first place.

Best regards,
Bequimão
Reply With Quote
  #5  
Old 26th November 2016, 06:28 PM
CSchwangler Offline
Registered User
 
Join Date: Feb 2009
Posts: 2,747
linuxfedorafirefox
Re: KDE workspace broken since kernel 4.8.7

Your problems have most likely nothing to do with the kernel but are configuration or cache related. This happens very often:

https://wiki.archlinux.org/index.php...ration_related
Reply With Quote
  #6  
Old 26th November 2016, 06:53 PM
adventurer Offline
Registered User
 
Join Date: Nov 2016
Location: Germany
Posts: 20
macossafari
Re: KDE workspace broken since kernel 4.8.7

@Bequimao : I agree with @CSchwangler that your problem is different as your symptoms don't explain why it works for me with kernel 4.8.6. (both on F24 anf F25) but not with the newer kernel versions.
Reply With Quote
  #7  
Old 28th November 2016, 01:19 PM
adventurer Offline
Registered User
 
Join Date: Nov 2016
Location: Germany
Posts: 20
windows_7chrome
Re: KDE workspace broken since kernel 4.8.7

FWIW, I tried Wayland with kernel 4.8.8 after installing the plasma-workspace-wayland package.

Although there are still problems (e.g. conky wouldn't start) it was rather stable. The panel showed up as expected (although it sometimes disappeared for blick of the eye), I could start Firefox and Thunderbird, and the workspace did not crash or become unresponsive. It was a bit slower than under X11. Taken all together, Wayland on KDE is not yet ready but well on the way.

And the fact that Wayland worked better under kernel 4.8.8 than Plasma with X11 supports my suspicion that there is a problem with the graphics stack in 4.8.7 and 4.8.8.
Reply With Quote
  #8  
Old 8th December 2016, 06:29 PM
adventurer Offline
Registered User
 
Join Date: Nov 2016
Location: Germany
Posts: 20
windows_7chrome
Re: KDE workspace broken since kernel 4.8.7

The problem is finally fixed for me! I had opened this bug https://bugzilla.redhat.com/show_bug.cgi?id=1398362 and got a hint that adding

video=eDP-1:d

as a boot option to /boot/grub/grub.cfg could help. And indeed - all is well now. Both with kernels 4.8.11 and 4.8.12 (from updates-testing). So I added this parameter to /etc/default/grub. The respective line looks like this now:

Code:
GRUB_CMDLINE_LINUX="rhgb quiet video=eDP-1:d"
EDIT: Don't forget to execute

Code:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
thereafter!
Reply With Quote
  #9  
Old 4th January 2017, 08:30 PM
crdennett Offline
Registered User
 
Join Date: Dec 2016
Location: Rochester, New York, USA
Posts: 2
windows_7firefox
Re: KDE workspace broken since kernel 4.8.7

I also had this problem and filed bugzilla report 1397864 in case anyone wants to join teh cc list. I think I was the one who found the workaround by disabling eDP-1 video

Charlie
Reply With Quote
  #10  
Old 5th January 2017, 08:03 PM
adventurer Offline
Registered User
 
Join Date: Nov 2016
Location: Germany
Posts: 20
linuxubuntufirefox
Re: KDE workspace broken since kernel 4.8.7

Quote:
Originally Posted by crdennett View Post
I also had this problem and filed bugzilla report 1397864 in case anyone wants to join teh cc list. I think I was the one who found the workaround by disabling eDP-1 video

Charlie
Indeed, you are the one who commented to my bug report and provided this crucial hint. Thank you very much again! FWIW, I also tried KDE Neon (based on Ubuntu 16.04) where I ran into the same problem with kernel 4.8.0 - but applying your "trick" solved this problem for that distro, too.

Do you also have a solution for this problem quite accidentally?
Reply With Quote
  #11  
Old 5th January 2017, 09:11 PM
crdennett Offline
Registered User
 
Join Date: Dec 2016
Location: Rochester, New York, USA
Posts: 2
windows_7firefox
Re: KDE workspace broken since kernel 4.8.7

Quote:
Originally Posted by adventurer View Post

Do you also have a solution for this problem quite accidentally?
Sorry, have not had that particular issue. I have a wired keyboard and a wireless mouse. Keyboard and receiver for mouse are plugged into a kvm switch. My server and a docking station for my work laptop are connected to the kvm switch. Tried a wireless keyboard once but it did not get along with the kvm switch.

Charlie
Reply With Quote
Reply

Tags
broken, kde, kernel, workspace

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Launching firefox in any workspace other than workspace 1, triggers overview expectATIon F18 Development 3 5th December 2012 10:11 PM
AIGLX last virtual workspace is always broken Anonycat Using Fedora 0 30th October 2006 11:17 PM


Current GMT-time: 01:31 (Sunday, 26-03-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat