KDE fails at xinit after recent update [Solved]

Discussion in general that pertains to Sabayon Linux - Must Pertain to Sabayon Linux

Moderator: Moderators

twhite
Baby Hen
Posts: 15
Joined: Tue Sep 20, 2016 20:57

KDE fails at xinit after recent update [Solved]

Post by twhite » Thu Jan 10, 2019 23:17

After I updated a couple days ago my laptop froze where I could see a virtual console login but couldn't type anything to login and couldn't change consoles with Ctl+Alt+F2 or F3, etc. and couldn't ssh into it. I had to hold the power button to power off and restart. I was able to boot into rescue mode and disable automaic staring of KDE by executing "systemctl set-default multi-user.target" then booted again into a console without any xorg or GUI. Then I could use different consoles and ssh into it also from another computer.

Now whenever I use startx which executes xinit and immediatly locks up everything. From a different user account I also tried startx and also tried another window manager, TWM, and the same thing happened.

Any suggestions?

This is the Xorg logfile from the failed xorg start where it just stops at "visual is TrueColor" without any error.

Code: Select all

[ 46259.471]
X.Org X Server 1.20.3
X Protocol Version 11, Revision 0
[ 46259.473] Build Operating System: Linux 4.9.0-sabayon x86_64 Gentoo
[ 46259.474] Current Operating System: Linux sabayonx86-64 4.9.0-sabayon #1 SMP Wed Dec 26 14:39:44 UTC 2018 x86_64
[ 46259.474] Kernel command line: BOOT_IMAGE=/kernel-genkernel-x86_64-4.9.0-sabayon root=/dev/mapper/sa_sabayon-root ro resume=/dev/mapper/sa_sabayon-swap dolvm vconsole.font=latarcyrheb-sun16 vga=791 splash vconsole.keymap=us quiet
[ 46259.477] Build Date: 27 October 2018  02:21:32PM
[ 46259.478] 
[ 46259.479] Current version of pixman: 0.34.0
[ 46259.480]     Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
[ 46259.480] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 46259.484] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan  9 09:19:00 2019
[ 46259.511] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 46259.512] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 46259.611] (==) No Layout section.  Using the first Screen section.
[ 46259.611] (==) No screen section available. Using defaults.
[ 46259.611] (**) |-->Screen "Default Screen Section" (0)
[ 46259.611] (**) |   |-->Monitor "<default monitor>"
[ 46259.612] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
[ 46259.612] (==) Automatically adding devices
[ 46259.612] (==) Automatically enabling devices
[ 46259.612] (==) Automatically adding GPU devices
[ 46259.612] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 46259.646] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 46259.646]     Entry deleted from font path.
[ 46259.646] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 46259.646]     Entry deleted from font path.
[ 46259.646] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 46259.646]     Entry deleted from font path.
[ 46259.680] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
[ 46259.680] (**) ModulePath set to "/usr/lib32/xorg/modules,/usr/lib64/xorg/modules"
[ 46259.680] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 46259.680] (II) Loader magic: 0x556a2212cd00
[ 46259.680] (II) Module ABI versions:
[ 46259.680]     X.Org ANSI C Emulation: 0.4
[ 46259.680]     X.Org Video Driver: 24.0
[ 46259.680]     X.Org XInput driver : 24.1
[ 46259.680]     X.Org Server Extension : 10.0
[ 46259.681] (++) using VT number 1

[ 46259.681] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 46259.683] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[ 46259.684] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 46259.684] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 10 paused 0
[ 46259.686] (--) PCI:*([email protected]:2:0) 8086:0a16:14c0:0075 rev 9, Mem @ 0xb0000000/4194304, 0xa0000000/268435456, I/O @ 0x00004000/64, BIOS @ 0x????????/131072
[ 46259.686] (II) LoadModule: "glx"
[ 46259.712] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 46259.738] (II) Module glx: vendor="X.Org Foundation"
[ 46259.738]     compiled for 1.20.3, module version = 1.0.0
[ 46259.738]     ABI class: X.Org Server Extension, version 10.0
[ 46259.739] (==) Matched intel as autoconfigured driver 0
[ 46259.739] (==) Matched modesetting as autoconfigured driver 1
[ 46259.739] (==) Matched fbdev as autoconfigured driver 2
[ 46259.739] (==) Matched vesa as autoconfigured driver 3
[ 46259.739] (==) Assigned the driver to the xf86ConfigLayout
[ 46259.739] (II) LoadModule: "intel"
[ 46259.739] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[ 46259.778] (II) Module intel: vendor="X.Org Foundation"
[ 46259.778]     compiled for 1.20.3, module version = 2.99.917
[ 46259.778]     Module class: X.Org Video Driver
[ 46259.778]     ABI class: X.Org Video Driver, version 24.0
[ 46259.778] (II) LoadModule: "modesetting"
[ 46259.778] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[ 46259.794] (II) Module modesetting: vendor="X.Org Foundation"
[ 46259.794]     compiled for 1.20.3, module version = 1.20.3
[ 46259.794]     Module class: X.Org Video Driver
[ 46259.794]     ABI class: X.Org Video Driver, version 24.0
[ 46259.794] (II) LoadModule: "fbdev"
[ 46259.795] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[ 46259.802] (II) Module fbdev: vendor="X.Org Foundation"
[ 46259.802]     compiled for 1.20.3, module version = 0.5.0
[ 46259.802]     Module class: X.Org Video Driver
[ 46259.802]     ABI class: X.Org Video Driver, version 24.0
[ 46259.802] (II) LoadModule: "vesa"
[ 46259.802] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 46259.813] (II) Module vesa: vendor="X.Org Foundation"
[ 46259.813]     compiled for 1.20.3, module version = 2.4.0
[ 46259.813]     Module class: X.Org Video Driver
[ 46259.813]     ABI class: X.Org Video Driver, version 24.0
[ 46259.813] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
    i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
    915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
    Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
    GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 46259.814] (II) intel: Driver for Intel(R) HD Graphics
[ 46259.814] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[ 46259.814] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[ 46259.814] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 46259.814] (II) FBDEV: driver for framebuffer: fbdev
[ 46259.814] (II) VESA: driver for VESA chipsets: vesa
[ 46259.825] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20160919
[ 46259.827] (WW) Falling back to old probe method for modesetting
[ 46259.827] (WW) Falling back to old probe method for fbdev
[ 46259.827] (II) Loading sub module "fbdevhw"
[ 46259.827] (II) LoadModule: "fbdevhw"
[ 46259.827] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 46259.836] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 46259.836]     compiled for 1.20.3, module version = 0.0.2
[ 46259.836]     ABI class: X.Org Video Driver, version 24.0
[ 46259.846] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4400
[ 46259.846] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2; using a maximum of 2 threads
[ 46259.846] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
[ 46259.846] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 46259.846] (==) intel(0): RGB weight 888
[ 46259.846] (==) intel(0): Default visual is TrueColor
(this is the end of the logfile)

Here is an older log from a few months ago from a successful KDE load. Here I have left out the beginning of this log where very little difference from the above log. If you need that I'll post it. Here you can see what should have happened right after the crash.

Code: Select all

...
[172973.163] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
[172973.163] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[172973.163] (==) intel(0): RGB weight 888
[172973.163] (==) intel(0): Default visual is TrueColor
   **** This is where it stops in the current log above ****
[172973.163] (II) intel(0): Output eDP1 has no monitor section
[172973.164] (**) intel(0): Found backlight control interface intel_backlight (type 'raw') for output eDP1
[172973.164] (II) intel(0): Enabled output eDP1
[172973.164] (II) intel(0): Output DP1 has no monitor section
[172973.164] (II) intel(0): Enabled output DP1
[172973.164] (II) intel(0): Output HDMI1 has no monitor section
[172973.164] (II) intel(0): Enabled output HDMI1
[172973.164] (II) intel(0): Output HDMI2 has no monitor section
[172973.164] (II) intel(0): Enabled output HDMI2
[172973.164] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[172973.164] (II) intel(0): Output VIRTUAL1 has no monitor section
[172973.164] (II) intel(0): Enabled output VIRTUAL1
[172973.164] (--) intel(0): Output eDP1 using initial mode 1366x768 on pipe 0
[172973.164] (--) intel(0): Output DP1 using initial mode 1920x1200 on pipe 1
[172973.164] (==) intel(0): TearFree disabled
[172973.164] (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
[172973.164] (==) intel(0): DPI set to (96, 96)
[172973.164] (II) Loading sub module "dri3"
[172973.164] (II) LoadModule: "dri3"
[172973.164] (II) Module "dri3" already built-in
[172973.164] (II) Loading sub module "dri2"
[172973.164] (II) LoadModule: "dri2"
[172973.164] (II) Module "dri2" already built-in
[172973.164] (II) Loading sub module "present"
[172973.165] (II) LoadModule: "present"
[172973.165] (II) Module "present" already built-in
[172973.165] (II) UnloadModule: "modesetting"
[172973.165] (II) Unloading modesetting
[172973.165] (II) UnloadModule: "fbdev"
[172973.165] (II) Unloading fbdev
[172973.165] (II) UnloadSubModule: "fbdevhw"
[172973.165] (II) Unloading fbdevhw
[172973.165] (II) UnloadModule: "vesa"
[172973.165] (II) Unloading vesa
[172973.165] (==) Depth 24 pixmap format is 32 bpp
...
This above log continues to a successful loading of KDE ...

Here is the output from lspci.

Code: Select all

00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01)
01:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a)
02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
If it helps I can also post the list of the packages that were updated just before the problem. Xorg was not updated.

Thanks for any suggestions.

Stupot
Sagely Hen
Posts: 1744
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

Re: KDE fails at xinit after recent update

Post by Stupot » Sun Jan 13, 2019 7:28

So it sounds like something is messed up with your Display Manager. Are you using sddm, or lightdm? My system is using sddm as shown here:

Code: Select all

[email protected] ~ $ cat /etc/systemd/system/display-manager.service
[Unit]
Description=Simple Desktop Display Manager
Documentation=man:sddm(1) man:sddm.conf(5)
After=systemd-user-sessions.service [email protected] systemd-logind.service

[Service]
ExecStart=/usr/bin/sddm
Restart=always
StandardOutput=syslog
BusName=org.freedesktop.DisplayManager

[Install]
Alias=display-manager.service

So, what are the contents of that file? If it's not set up at all, pick one and let's try it out. If it is set up, let's try switching it to the other to see if that at least gets you out of hot water for the time being.

You might need to install the other dm. It doesn't hurt to have to both installed at the same time, but you will only use one at a time.

Code: Select all

# equo install lightdm sddm
Then, if you already have one enabled, let's disable it:

Code: Select all

# systemctl disable sddm
or

Code: Select all

# systemctl disable lightdm
Lastly, take the one you're trying to enable it, and do so:

Code: Select all

# systemctl enable sddm
or

Code: Select all

systemctl enable lightdm
Then reboot and cross your fingers.

twhite
Baby Hen
Posts: 15
Joined: Tue Sep 20, 2016 20:57

Re: KDE fails at xinit after recent update

Post by twhite » Tue Jan 15, 2019 0:16

Thanks for responding...

I was using sddm and the file /etc/systemd/system/display-manager.service looked the same as yours. I disabled sddm, installed lightdm and enabled it then tried it again with the same result of freezing with trying to load the GUI.

For now I have disabled the GUI from booting with

Code: Select all

systemctl set-default multi-user.target
so I tried both using startx from another user account and also tried booting after setting it back to boot with the GUI by doing

Code: Select all

systemctl set-default graphical.target
I get the same results. Is there something else I can try?

Stupot
Sagely Hen
Posts: 1744
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

Re: KDE fails at xinit after recent update

Post by Stupot » Wed Jan 16, 2019 1:40

What GPU are you using? nVidia proprietary?

twhite
Baby Hen
Posts: 15
Joined: Tue Sep 20, 2016 20:57

Re: KDE fails at xinit after recent update

Post by twhite » Wed Jan 16, 2019 18:54

From lspci

Code: Select all

VGA compatible controller: Intel corporation Haswell-ULT Intregrated Graphics Controller (rev09)
From Xorg.1.log

Code: Select all

[174116.261] (II) LoadModule: "intel"
[174116.262] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[174116.262] (II) Module intel: vendor="X.Org Foundation"
[174116.262]    compiled for 1.19.5, module version = 2.99.917
[174116.262]    Module class: X.Org Video Driver
[174116.262]    ABI class: X.Org Video Driver, version 23.0
There's other video modules listed there:
  • glx
  • modesetting
  • fbdev
  • visa
This is a laptop that I bought with Sabayon installed. It has been working fine for years until this last update. I tried an older Gentoo 2014 livedvd that I had sitting around and it loaded KDE fine. Maybe I should try a newer livedvd and see if that makes a difference. I'm pretty much just shooting in the dark.

twhite
Baby Hen
Posts: 15
Joined: Tue Sep 20, 2016 20:57

Re: KDE fails at xinit after recent update

Post by twhite » Wed Jan 16, 2019 19:26

I don't know much about this but it looks like it is locking up within Xorg. Notice the "running task" below. Xorg itself wasn't updated but maybe a configuration or permission was changed.


journalctl --since "2019-1-9 09:18:00"

Code: Select all

Jan 09 09:20:00 sabayonx86-64 kernel: INFO: rcu_sched self-detected stall on CPU
Jan 09 09:20:00 sabayonx86-64 kernel:         1-...: (59999 ticks this GP) idle=581/140000000000001/0 softirq=183409/183409 fqs=14998
Jan 09 09:20:00 sabayonx86-64 kernel:          (t=60000 jiffies g=131393 c=131392 q=321)
Jan 09 09:20:00 sabayonx86-64 kernel: Task dump for CPU 1:
Jan 09 09:20:00 sabayonx86-64 kernel: Xorg            R  running task        0 19622  19621 0x00400008
Jan 09 09:20:00 sabayonx86-64 kernel:  ffff88025f243e20 ffffffff8109425c 0000000000000001 ffffffff823261c0
Jan 09 09:20:00 sabayonx86-64 kernel:  ffff88025f243e38 ffffffff81096a02 0000000000000001 ffff88025f243e70
Jan 09 09:20:00 sabayonx86-64 kernel:  ffffffff81123ee9 ffff88025f259680 ffffffff82246ac0 0000000000000000
Jan 09 09:20:00 sabayonx86-64 kernel: Call Trace:
Jan 09 09:20:00 sabayonx86-64 kernel:  <IRQ>
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff8109425c>] sched_show_task+0xcc/0x120
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff81096a02>] dump_cpu_task+0x32/0x40
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff81123ee9>] rcu_dump_cpu_stacks+0x92/0xb4
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff810c975d>] rcu_check_callbacks+0x5ad/0x800
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff8109776f>] ? account_process_tick+0x6f/0x140
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff810cc49a>] update_process_times+0x2a/0x50
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff810daffd>] tick_sched_handle.isra.5+0x2d/0x30
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff810db03d>] tick_sched_timer+0x3d/0x70
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff810cd038>] __hrtimer_run_queues+0xb8/0x170
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff810cd342>] hrtimer_interrupt+0x92/0x170
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff810483e7>] smp_apic_timer_interrupt+0x77/0xb0
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff81ad2156>] apic_timer_interrupt+0x96/0xa0
Jan 09 09:20:00 sabayonx86-64 kernel:  <EOI>
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff810acf0a>] ? queued_spin_lock_slowpath+0x5a/0x1a0
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff81ad119c>] _raw_spin_lock+0x1c/0x20
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffffa00d7a6c>] i915_gem_throttle_ioctl+0x4c/0x170 [i915]
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffffa0010888>] drm_ioctl+0x218/0x7d0 [drm]
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffffa00d7a20>] ? i915_gem_busy_ioctl+0xf0/0xf0 [i915]
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff811bc319>] ? dentry_free+0x49/0x80
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff811bc468>] ? __dentry_kill+0x118/0x150
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff811b7e74>] do_vfs_ioctl+0x94/0x5e0
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff811a70e7>] ? __fput+0x147/0x1f0
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff811b8434>] SyS_ioctl+0x74/0x80
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff810032de>] do_syscall_64+0x6e/0xe0
Jan 09 09:20:00 sabayonx86-64 kernel:  [<ffffffff81ad148e>] entry_SYSCALL_64_after_swapgs+0x58/0xc6
Here's the list of packages that were updated:

Packages that were updated just before the problem occurred:
from /var/log/entropy/entropy.log
(There were 57 packages installed)

Code: Select all

sys-apps/portage-2.3.51-41
kde-misc/wacomtablet-3.1.1
media-libs/babl-0.1.60
dev-libs/json-glib-1.4.4
media-libs/openjpeg-2.3.0-r1
net-wireless/bluez-5.50-r1
media-sound/pulseaudio-12.2
net-wireless/bluez-5.50-r1
media-libs/gegl-0.4.12
dev-python/pycairo-1.17.0.r1
media-gfx/gimp-2.10.8-r1
media-video/subtitlecomposer-0.6.6-r1
dev-util/dialog-1.3.20181107
x11-themes/gnome-themes-standard-3.22.3-r1
app-misc/geoclue-2.4.13
media-gfx/imagemagick-6.9.10.16-r1
de-libs/libfilezilla-0.15.1
net-ftp/filezilla-3.39.0
sys-devel/llvm-7.0.1
sys-devel/llvm-common-7.0.1
net-analyzer/wireshark-2.9.0-r1
net-misc/iputils-20180629
net-print/cups-filters-1.21.6
x11-themes/gtk-engines-adwaita-3.28
app-office/libreoffice-110n-en_US-6.1.4.2
sys-libs/compiler-rt-sanitizers-7.0.1
sys-devel/clang-7.0.1
sys-libs/libomp-7.0.1
sys-devel/clang-runtime-7.0.1
sys-devel/clang-common-7.0.1
sys-libs/compiler-rt-7.0.1
sys-libs/timezone-data-2018g-r1
app-admin/sysstat-12.1.2
kde-frameworks/kinit-5.53.0-r1
kde-apps/;konsole-18.12.0.r2
app-crypt/openpgp-keys-gentoo-release-20190102
app-arch/tar-1.31
sys-kernel/linux-headers-4.14-r1
app-text/libnumbertext-1.0.5
app-office/libreoffice-6.1.4.2
app-office/libreoffice-110n-6.1.4.2
sys-fs/mtools-4.0.23
dev-libs/fribidi-1.0.5
app-dicts/myspell-en-20181101
irtual/logger-0-r1
irtual/dev-manager-0-r2
app-emulation/docker-proxy-0.8.0_p20180907
app-emulation/docker-proxy-0.8.0_p20180907
app-emulation/docker-18.09.0
sys-power/acpid-2.0.31
x11-themes/adwaita-icon-theme-3.30.1
sys-apps/util-linux-2.33-r1
dev-libs/rasqal-0.9.33
media-video/simplescreenrecorder-0.3.11-r1
net-misc/wget-1.20.1
sys-fs/lvm2-2.02.183
sys-kernel/linux-sabayon-4.4.162
app-emulation/virtualbox-modules-5.2.22#4.4.0-sabayon

joost
Sagely Hen
Posts: 2747
Joined: Fri Nov 17, 2006 12:11
Location: The Netherlands
Contact:

Re: KDE fails at xinit after recent update

Post by joost » Wed Jan 16, 2019 21:03

Hmm in IRC I've heard people say there is a problem with Linux 4.9 kernel and Intel GPU in some cases.
A newer 4.9 kernel will be available soon, hopefully fixes your issue.
My blog | Mastodon | Please support Sabayon: Become a Patron

twhite
Baby Hen
Posts: 15
Joined: Tue Sep 20, 2016 20:57

Re: KDE fails at xinit after recent update

Post by twhite » Thu Jan 17, 2019 4:27

I read at https://wiki.ubuntu.com/X/Troubleshooting/Freeze that most of the GPU freezes tend to be bugs in the kernel. I was at 4.4 so I changed to 4.9. That didn't work. I'll try some different versions and see what happens.

They also suggested that when the freeze happens after an update try to back out the changes.

Thanks for the help. It's not yet fixed but you gave me some things to try.

twhite
Baby Hen
Posts: 15
Joined: Tue Sep 20, 2016 20:57

Re: KDE fails at xinit after recent update [Solved]

Post by twhite » Fri Jan 25, 2019 2:39

I just finish a new large update of Sabayon and KDE is now working. Other than the update any changes I made were put back like the original. I can only guess as to the cause, perhaps a kernel that was installed in the update just before it broke, maybe it didn't work with the graphics driver.

lonesomecrow
Simple Hen
Posts: 60
Joined: Thu Apr 10, 2008 5:16

Re: KDE fails at xinit after recent update [Solved]

Post by lonesomecrow » Mon Feb 04, 2019 20:56

Has anyone solved this issue?

I just wanna say that I'm running into a similar error where my laptop's built in monitor is unable to load a login prompt, it only works if I use an external monitor (using the nvidia GTX 1060 card). Can anyone guide me to get it working?

Razer Blade 14" 2017

Thanks

Post Reply