You are not logged in.
- Topics: Active | Unanswered
#1 2018-01-04 22:59:24
- blablubs82352
- Member
- Registered: 2016-09-25
- Posts: 21
[SOLVED] Plasma cannot connect to display :0 Plasma?
Hey to everybody
tldr; Problem: Plasma cannot connect to xorg: I guess something is wrong with plasmashell or nouveau, xorg
Today after I experienced some performance lacks I got to the great idea of updateing my arch. Then I reboot and after I enter my password in sddm xorg is exiting with failure.
I've got a Yoga 460 so:
Intel HD Graphics 520 and/or NVIDIA GeForce 940M is my GPU which I use with nouveau. (I guess)
Furthermore I've installed multiple WMs and DEs on different OSs. all, beside arch linux with Plasma, work properly. I only use Arch Linux and Plasma.
On Arch Linux: Plasma and awesome
Debian: Plasma
Both plasma use the same locale config, as I share the home partition.
First I disabled sddm.service and tried it using the 'startx' command. Which finally runs 'exec startkde' and crashes while connecting to display:0.
local log Xorg:~/.local/share/xorg/Xorg.0.log Errors
[ 159.041] (EE) Failed to load module "intel" (module does not exist, 0)
[ 159.041] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 159.041] (EE) Failed to load module "nv" (module does not exist, 0)
[ 159.041] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 159.042] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 159.457] (EE) Wacom Pen and multitouch sensor Finger: Invalid type 'stylus' for this device.
[ 159.457] (EE) Wacom Pen and multitouch sensor Finger: Invalid type 'eraser' for this device.
[ 159.457] (EE) Wacom Pen and multitouch sensor Finger: Invalid type 'cursor' for this device.
[ 159.458] (EE) Wacom Pen and multitouch sensor Finger touch: Invalid type 'stylus' for this device.
[ 159.458] (EE) Wacom Pen and multitouch sensor Finger touch: Invalid type 'eraser' for this device.
[ 159.458] (EE) Wacom Pen and multitouch sensor Finger touch: Invalid type 'cursor' for this device.
[ 159.458] (EE) Wacom Pen and multitouch sensor Finger touch: Invalid type 'pad' for this device.
[ 159.518] (EE) Wacom Pen and multitouch sensor Pen stylus: Invalid type 'cursor' for this device.
[ 159.519] (EE) Wacom Pen and multitouch sensor Pen stylus: Invalid type 'touch' for this device.
[ 159.519] (EE) Wacom Pen and multitouch sensor Pen stylus: Invalid type 'pad' for this device.
[ 159.548] (EE) Failed to load module "evdev" (module does not exist, 0)
[ 159.548] (EE) No input driver matching `evdev'Warnings
[ 159.012] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 159.015] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 159.040] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 159.041] (WW) Warning, couldn't open module intel
[ 159.041] (WW) Warning, couldn't open module nouveau
[ 159.041] (WW) Warning, couldn't open module nv
[ 159.041] (WW) Warning, couldn't open module fbdev
[ 159.042] (WW) Warning, couldn't open module vesa
[ 159.042] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 159.548] (WW) Warning, couldn't open module evdevThat's what startx is prompting when it crashes
ist with a single query: "xcb;" qt.qpa.screen: QXcbConnectio: Could not connect to display :0nplugins/kaccounts_ktp_plugins.so "org.kde.kcoreaddons: Expect JSON property "X-KDE-OnlyShowOnQtPlatforms" to be a string list. Treating it as a D?
ist with a single query: "xcb;" qt.qpa.screen: QXcbConnectio: Could not connect to display :0nplugins/kaccounts_ktp_plugins.so "org.kde.kcoreaddons: Expect JSON property "X-KDE-OnlyShowOnQtPlatforms" to be a string list. Treating it as a D?
qt.qpa.screen: QXcbConnection: Could not connect to display :0
.Could not conect to any X display.
Could not conect to any X display.
(II) Server terminated succesfully (0), Closing log file.
kdeinit5: Communication error with launcher. Exiting!
"KLauncher could not be reached via D-Bus. Error when calling kdeinit_exec_wait:\nThe name org.kde.klauncher5 was not provided by any .service files\n"
KCrash: Attempting to start /usr/bin/kdeinit5 from kdeinit
...
more unspecific crash logThan I looked up wether there was something strange happening during boot. And I found the folliwing.
Log of journalctl -xe | grep nouveau
Jan 04 23:17:03 myhostname kernel: nouveau: detected PR support, will not use DSM
Jan 04 23:17:03 myhostname kernel: nouveau 0000:06:00.0: enabling device (0006 -> 0007)
Jan 04 23:17:03 myhostname kernel: nouveau 0000:06:00.0: NVIDIA GM108 (118070a2)
Jan 04 23:17:03 myhostname kernel: nouveau 0000:06:00.0: bios: version 82.08.4a.00.03
Jan 04 23:17:03 myhostname kernel: nouveau 0000:06:00.0: fb: 2048 MiB DDR3
Jan 04 23:17:03 myhostname kernel: nouveau 0000:06:00.0: bus: MMIO read of 00000000 FAULT at 612004 [ IBUS ]
Jan 04 23:17:03 myhostname kernel: nouveau 0000:06:00.0: bus: MMIO read of 00000000 FAULT at 10ac08 [ IBUS ]
Jan 04 23:17:04 myhostname kernel: nouveau 0000:06:00.0: DRM: VRAM: 2048 MiB
Jan 04 23:17:04 myhostname kernel: nouveau 0000:06:00.0: DRM: GART: 1048576 MiB
Jan 04 23:17:04 myhostname kernel: nouveau 0000:06:00.0: DRM: Pointer to TMDS table invalid
Jan 04 23:17:04 myhostname kernel: nouveau 0000:06:00.0: DRM: DCB version 4.0
Jan 04 23:17:04 myhostname kernel: nouveau 0000:06:00.0: DRM: MM: using COPY for buffer copies
Jan 04 23:17:04 myhostname kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:06:00.0 on minor 0Further the output of journalctl is the following when startx crashes
Jan 04 23:40:59 myhostname kernel: vga_switcheroo: enabled
Jan 04 23:40:59 myhostname kernel: [TTM] Zone kernel: Available graphics memory: 4030396 kiB
Jan 04 23:40:59 myhostname kernel: [TTM] Zone dma32: Available graphics memory: 2097152 kiB
Jan 04 23:40:59 myhostname kernel: [TTM] Initializing pool allocator
Jan 04 23:40:59 myhostname kernel: [TTM] Initializing DMA pool allocator
Jan 04 23:40:59 myhostname kernel: nouveau 0000:06:00.0: DRM: VRAM: 2048 MiB
Jan 04 23:40:59 myhostname kernel: nouveau 0000:06:00.0: DRM: GART: 1048576 MiB
Jan 04 23:40:59 myhostname kernel: nouveau 0000:06:00.0: DRM: Pointer to TMDS table invalid
Jan 04 23:40:59 myhostname kernel: nouveau 0000:06:00.0: DRM: DCB version 4.0
Jan 04 23:40:59 myhostname NetworkManager[509]: <info> [1515105659.7933] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 04 23:40:59 myhostname kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Jan 04 23:40:59 myhostname kernel: IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
Jan 04 23:40:59 myhostname kernel: nouveau 0000:06:00.0: DRM: MM: using COPY for buffer copies
Jan 04 23:40:59 myhostname kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:06:00.0 on minor 0
Jan 04 23:40:59 myhostname kernel: [drm] Initialized i915 1.6.0 20170818 for 0000:00:02.0 on minor 1
Jan 04 23:40:59 myhostname kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
Jan 04 23:40:59 myhostname kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input16
Jan 04 23:40:59 myhostname kernel: ACPI: Video Device [PXSX] (multi-head: no rom: yes post: no)
Jan 04 23:40:59 myhostname kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:42/LNXVIDEO:01/input/input17
Jan 04 23:40:59 myhostname kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Jan 04 23:41:00 myhostname NetworkManager[509]: <info> [1515105660.0088] bluez: use BlueZ version 5
Jan 04 23:41:00 myhostname NetworkManager[509]: <info> [1515105660.0110] supplicant: wpa_supplicant running
Jan 04 23:41:00 myhostname NetworkManager[509]: <info> [1515105660.0111] device (wlp3s0): supplicant interface state: init -> starting
Jan 04 23:41:00 myhostname NetworkManager[509]: <info> [1515105660.0154] bluez5: NAP: added interface A4:34:D9:59:70:7B
Jan 04 23:41:00 myhostname NetworkManager[509]: <info> [1515105660.0527] sup-iface[0x563cca4a2220,wlp3s0]: supports 5 scan SSIDs
Jan 04 23:41:00 myhostname NetworkManager[509]: <info> [1515105660.0532] device (wlp3s0): supplicant interface state: starting -> ready
Jan 04 23:41:00 myhostname NetworkManager[509]: <info> [1515105660.0533] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jan 04 23:41:01 myhostname kernel: fbcon: inteldrmfb (fb0) is primary device
Jan 04 23:41:01 myhostname kernel: snd_hda_codec_conexant hdaudioC0D0: CX20753/4: BIOS auto-probing.
Jan 04 23:41:01 myhostname kernel: snd_hda_codec_conexant hdaudioC0D0: autoconfig for CX20753/4: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
Jan 04 23:41:01 myhostname kernel: snd_hda_codec_conexant hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Jan 04 23:41:01 myhostname kernel: snd_hda_codec_conexant hdaudioC0D0: hp_outs=1 (0x16/0x0/0x0/0x0/0x0)
Jan 04 23:41:01 myhostname kernel: snd_hda_codec_conexant hdaudioC0D0: mono: mono_out=0x0
Jan 04 23:41:01 myhostname kernel: snd_hda_codec_conexant hdaudioC0D0: inputs:
Jan 04 23:41:01 myhostname kernel: snd_hda_codec_conexant hdaudioC0D0: Internal Mic=0x1a
Jan 04 23:41:01 myhostname kernel: snd_hda_codec_conexant hdaudioC0D0: Mic=0x19
Jan 04 23:41:01 myhostname kernel: snd_hda_codec_conexant hdaudioC0D0: Enable sync_write for stable communication
Jan 04 23:41:01 myhostname kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
Jan 04 23:41:01 myhostname kernel: input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
Jan 04 23:41:01 myhostname kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
Jan 04 23:41:01 myhostname kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input21
Jan 04 23:41:01 myhostname kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input22
Jan 04 23:41:01 myhostname kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input23
Jan 04 23:41:01 myhostname kernel: input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input24
Jan 04 23:41:01 myhostname kernel: input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input25
Jan 04 23:41:01 myhostname kernel: IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
Jan 04 23:41:01 myhostname kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Jan 04 23:41:01 myhostname kernel: [drm] RC6 on
Jan 04 23:41:01 myhostname kernel: Console: switching to colour frame buffer device 240x67
Jan 04 23:41:01 myhostname kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Jan 04 23:41:01 myhostname systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight...
-- Subject: Unit systemd-backlight@backlight:intel_backlight.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-backlight@backlight:intel_backlight.service has begun starting up.
Jan 04 23:41:01 myhostname systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:intel_backlight.
-- Subject: Unit systemd-backlight@backlight:intel_backlight.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-backlight@backlight:intel_backlight.service has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:05 myhostname NetworkManager[509]: <info> [1515105665.0076] manager: startup complete
Jan 04 23:41:08 myhostname login[535]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost= user=myusername
Jan 04 23:41:11 myhostname login[535]: FAILED LOGIN 1 FROM tty1 FOR myusername, Authentication failure
Jan 04 23:41:19 myhostname login[535]: pam_unix(login:session): session opened for user myusername by LOGIN(uid=0)
Jan 04 23:41:19 myhostname systemd[1]: Created slice User Slice of myusername.
-- Subject: Unit user-1000.slice has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-1000.slice has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[1]: Starting User Manager for UID 1000...
-- Subject: Unit user@1000.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user@1000.service has begun starting up.
Jan 04 23:41:19 myhostname systemd-logind[502]: New session c1 of user myusername.
-- Subject: A new session c1 has been created for user myusername
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID c1 has been created for the user myusername.
--
-- The leading process of the session is 535.
Jan 04 23:41:19 myhostname systemd[1]: Started Session c1 of user myusername.
-- Subject: Unit session-c1.scope has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-c1.scope has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: pam_unix(systemd-user:session): session opened for user myusername by (uid=0)
Jan 04 23:41:19 myhostname systemd[590]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Listening on GnuPG network certificate management daemon.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Listening on GnuPG cryptographic agent and passphrase cache.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Reached target Timers.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Listening on Sound System.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Starting D-Bus User Message Bus Socket.
-- Subject: Unit UNIT has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has begun starting up.
Jan 04 23:41:19 myhostname systemd[590]: Reached target Paths.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Listening on D-Bus User Message Bus Socket.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Reached target Sockets.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Reached target Basic System.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname systemd[590]: Startup finished in 38ms.
-- Subject: User manager start-up is now complete
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The user manager instance for user 1000 has been started. All services queued
-- for starting have been started. Note that other services might still be starting
-- up or be started at any later time.
--
-- Startup of the manager took 38472 microseconds.
Jan 04 23:41:19 myhostname systemd[1]: Started User Manager for UID 1000.
-- Subject: Unit user@1000.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user@1000.service has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:19 myhostname login[535]: LOGIN ON tty1 BY myusername
Jan 04 23:41:26 myhostname systemd[590]: Started D-Bus User Message Bus.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:29 myhostname systemd[1]: Created slice system-systemd\x2dcoredump.slice.
-- Subject: Unit system-systemd\x2dcoredump.slice has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit system-systemd\x2dcoredump.slice has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:29 myhostname systemd[1]: Started Process Core Dump (PID 734/UID 0).
-- Subject: Unit systemd-coredump@0-734-0.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-coredump@0-734-0.service has finished starting up.
--
-- The start-up result is RESULT.
Jan 04 23:41:29 myhostname systemd-coredump[735]: Process 689 (kded5) of user 1000 dumped core.
Stack trace of thread 689:
#0 0x00007f049298e860 raise (libc.so.6)
#1 0x00007f04945e5f9a _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5)
#2 0x00007f049298e8e0 __restore_rt (libc.so.6)
#3 0x00007f048574a40f _ZN14QXcbConnection10internAtomEPKc (libQt5XcbQpa.so.5)
#4 0x00007f048576fbba _ZN19QXcbNativeInterface8atspiBusEv (libQt5XcbQpa.so.5)
#5 0x00007f0485770989 _ZN19QXcbNativeInterface28nativeResourceForIntegrationERK10QByteArray (libQt5XcbQpa.so.5)
#6 0x00007f04857edd4d n/a (libQt5XcbQpa.so.5)
#7 0x00007f04857ee5bc n/a (libQt5XcbQpa.so.5)
#8 0x00007f04857e1b99 n/a (libQt5XcbQpa.so.5)
#9 0x00007f04857520c0 _ZNK15QXcbIntegration13accessibilityEv (libQt5XcbQpa.so.5)
#10 0x00007f04934ef5e7 _ZN11QAccessible13setRootObjectEP7QObject (libQt5Gui.so.5)
#11 0x00007f0493516154 _ZN15QGuiApplication4execEv (libQt5Gui.so.5)
#12 0x00007f0485c845a4 kdemain (libkdeinit5_kded5.so)
#13 0x000056188b88504f n/a (kdeinit5)
#14 0x000056188b881b69 n/a (kdeinit5)
#15 0x00007f049297af4a __libc_start_main (libc.so.6)
#16 0x000056188b8821ba _start (kdeinit5)
Stack trace of thread 710:
#0 0x00007f0492a45f2b __poll (libc.so.6)
#1 0x00007f048edbbed3 n/a (libglib-2.0.so.0)
#2 0x00007f048edbbfae g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f048edbc002 n/a (libglib-2.0.so.0)
#4 0x00007f048edb01eb n/a (libglib-2.0.so.0)
#5 0x00007f0490eb408a start_thread (libpthread.so.0)
#6 0x00007f0492a5042f __clone (libc.so.6)
Stack trace of thread 695:
#0 0x00007f0492a45f2b __poll (libc.so.6)
#1 0x00007f048edbbed3 n/a (libglib-2.0.so.0)
#2 0x00007f048edbbfae g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f049300a691 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#4 0x00007f0492fac82b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5 0x00007f0492dbc78e _ZN7QThread4execEv (libQt5Core.so.5)
#6 0x00007f048a0e6416 n/a (libQt5DBus.so.5)
#7 0x00007f0492dc1b2d n/a (libQt5Core.so.5)
#8 0x00007f0490eb408a start_thread (libpthread.so.0)
#9 0x00007f0492a5042f __clone (libc.so.6)
Stack trace of thread 711:
#0 0x00007f0492a45f2b __poll (libc.so.6)
#1 0x00007f048edbbed3 n/a (libglib-2.0.so.0)
#2 0x00007f048edbcf42 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f047877c208 n/a (libgio-2.0.so.0)
#4 0x00007f048edb01eb n/a (libglib-2.0.so.0)
#5 0x00007f0490eb408a start_thread (libpthread.so.0)
#6 0x00007f0492a5042f __clone (libc.so.6)
-- Subject: Process 689 (kded5) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
--
-- Process 689 (kded5) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.Last edited by blablubs82352 (2018-01-06 19:36:21)
Offline
#2 2018-01-04 23:08:34
- loqs
- Member
- Registered: 2014-03-06
- Posts: 19,113
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
Please post the entire Xorg.log grepping it like that strips the context from it, please also post the ~/.xinitrc of the user you tested startx with.
Edit:
Please also do not post journalctl output with the -x option https://lists.freedesktop.org/archives/ … 13029.html
Last edited by loqs (2018-01-04 23:10:12)
Offline
#3 2018-01-04 23:46:43
- blablubs82352
- Member
- Registered: 2016-09-25
- Posts: 21
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
.xinitrc
exec startkdelet me reboot
Offline
#4 2018-01-04 23:51:34
- loqs
- Member
- Registered: 2014-03-06
- Posts: 19,113
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
Please see the second note on Xinit#xinitrc.
Offline
#5 2018-01-04 23:56:01
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,426
- Website
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
Moving to NC...
Offline
#6 2018-01-05 00:22:04
- blablubs82352
- Member
- Registered: 2016-09-25
- Posts: 21
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
Note: At the very least, ensure that the last if block in /etc/X11/xinit/xinitrc is present in your .xinitrc file to ensure that the scripts in /etc/X11/xinit/xinitrc.d are sourced.
If you mean this point it doesn't helped a lot, because I didn't changed anything with my xinitrc. Plasma is crashing when some components (maybe QXcbConnection) want to connect to display :0 .
Offline
#7 2018-01-05 10:54:20
- blablubs82352
- Member
- Registered: 2016-09-25
- Posts: 21
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
The libjson-c was the problem.
Plasma wanted libjson-c.so.2 and the current was libjson-c.so.3 or libjson-c.so
I solved it a bit hacky by linking 2 to 3. That did the trick.
Pls mark as solved
Offline
#8 2018-01-05 12:03:39
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,435
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
Only you can and should be doing that...
That said, what you did does only mask the problem and is guaranteed to run you into further issues. Don't symlink soname bumps they have been bumped for a reason. Fix your system by updating it properly: https://wiki.archlinux.org/index.php/Sy … nsupported
Last edited by V1del (2018-01-05 12:04:15)
Offline
#9 2018-01-05 13:33:30
- mrunion
- Member
- From: Jonesborough, TN
- Registered: 2007-01-26
- Posts: 1,938
- Website
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
blablubs82352 wrote:
If you mean this point it doesn't helped a lot, because I didn't changed anything with my xinitrc. Plasma is crashing when some components (maybe QXcbConnection) want to connect to display :0 .
I think what he means is that there should be more in the .xinitrc than you have shown. so either you are filtering your files and only showing us parts of them -- don't do that -- or there is something wrong with the .xinitrc.
And V1del is right -- update your system completely and properly.
Are you running pure Arch?
Matt
"It is very difficult to educate the educated."
Offline
#10 2018-01-05 14:46:29
- blablubs82352
- Member
- Registered: 2016-09-25
- Posts: 21
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
Thanks, first for your kindness and help.
I run pure arch
I run this setup for more than a year, and fixed xorg several times, after some updates broke smthing.
I didn't hide any lines in ~/.xinitrc
Once more I just run # pacman -Syu and ran into this problem.
I updated now, but I if remove the manual symlink, plasma crashes as before.
Offline
#11 2018-01-05 15:21:27
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,435
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
If that is your entire .xinitrc that is incorrect, as noted read the blue note in the .xinitrc article again.
But there's something much more broken on your system. nothing should link against that libjson anymore... The most harmless possibility, do you have a custom plasma extension/plasmoid that you didn't recompile? What did you have to "fix with Xorg" exactly? Post the entire outputs of
pacman -Qm
pacman -Q plasma-workspace qt5-base
uname -a
lddtree /usr/bin/kdeinit5 #Needs pax-utilsOffline
#12 2018-01-05 17:26:49
- blablubs82352
- Member
- Registered: 2016-09-25
- Posts: 21
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
Well the only I wanted to say is that my xinitrc is maybe not the best but it is however not attached to this problem here, at least it seems to me.
pacman -Qm
mh... maybe some aur plasma-* or kde* are outdated.
I updated them already.
android-platform 27_r01-1
android-sdk 26.1.1-1
android-sdk-platform-tools r27.0.1-1
archlinux-java-run 3-1
aurget 4.7.2-1
avogadro 1.2.0-5
bear 2.3.9-1
blogilo 17.08.3-1
cgns 3.3.1-4
chromium-pepper-flash 1:22.0.0.192-1
cruiser 1.4.27-1
depot-tools-git r4677.77b7687e-1
dict-freedict-deu-eng 0.3.4-6
dict-freedict-deu-fra 2016_11_20-1
dict-freedict-eng-deu 0.3.6-6
dict-freedict-eng-fra 0.1.4-6
dict-freedict-fra-deu 2016_11_20-1
dict-freedict-fra-eng 0.3.5-6
dict-gcide 0.51-1
dict-wn 3.1-3
dolphinpart4 16.08.3-1
eigen2 2.0.17-3
epson-inkjet-printer-201212w 1.0.0-8
fifechan-git 0.1.4.r57.ga984c55-1
fizsh-git 1.0.8.r10.g2ecbbe8-1
franz-bin 5.0.0_beta.13-3
gcc-gcj-ecj 4.9-4
gdcm 2.8.3-10
gimp-gap 2.6.1-2
gimp-plugin-mathmap 1.3.5-8
google-breakpad-git r1669.2aaeead7-1
gpgmepp 16.08.3-1
gpxsee-git r704.de2278b-1
gstreamer0.10 0.10.36-17
gstreamer0.10-base 0.10.36-11
gstreamer0.10-base-plugins 0.10.36-11
hid-replay-git 0.7.1.r13.g7ff6cec-1
hplip-plugin 3.17.11-1
jabref 4.1-1
js17 17.0.0-4
katepart4 4.14.3-6
kdeaccessibility-jovie 17.08.3-1
kdeaccessibility-kaccessible 17.08.3-1
kdeadmin-kuser 16.08.3-1
kdebase-kdepasswd 16.08.3-1
kdebase-lib 16.08.3-1
kdebindings-python-common 4.14.3-7
kdebindings-python2 4.14.3-7
kdegraphics-ksaneplugin 17.08.3-1
kdemultimedia-kscd 17.08.3-1
kdenetwork-kppp 17.08.3-1
kdepimlibs4 4.14.10-11
kdeutils-kremotecontrol 17.08.3-1
kdewebdev-kfilereplace 17.08.3-1
kdewebdev-klinkstatus 17.08.3-1
kdewebdev-kommander 16.12.3-1
kdgantt2 16.08.3-1
kirigami 1.1.0-2
kronometer 2.2.0-1
kvkbd 0.7.2-2
lib32-libtxc_dxtn 1.0.1-5
libakonadi-qt4 1.13.0-14
libcurl-openssl-1.0 7.57.0-1
libgcj17-bin 6.4.0_11-1
libkactivities4 4.13.3-3
libkcddb4 16.08.3-1
libkcompactdisc4 16.08.3-1
libkdegames4 14.12.3-3
libkexiv2_4 15.08.3-2
libkolab 1.0.2-3
libksane4 15.08.3-4
libkscreen4 1.0.5-2
libmatthew-unix-java 0.5-1
libmusicbrainz3 3.0.3-4
libopenssl-1.0-compat 1.0.2.l-1
liboverlay-scrollbar-gtk3-bzr r391-2
libpulse-raop2 8.0-1
libqzeitgeist 0.8.0-6
libtracker-sparql 1.12.3-1
libtxc_dxtn 1.0.1-6
libxfont 1.5.3-1
overlay-scrollbar-bzr r391-2
pdftk-bin 2.02_4_b2-3
pim-storage-service-manager 16.12.3-1
plasma5-applets-redshift-control-git r67.f3ea169-1
plasma5-applets-thermal-monitor-git r60.691928e-1
plasma5-applets-uptime-widget-git r14.519943c-1
pmount 0.9.23-12
ppd-dell-5130cdn 1.3-5
pulseaudio-bluetooth-raop2 8.0-1
pulseaudio-equalizer-raop2 8.0-1
pulseaudio-gconf-raop2 8.0-1
pulseaudio-jack-raop2 8.0-1
pulseaudio-lirc-raop2 8.0-1
pulseaudio-raop2 8.0-1
pulseaudio-xen-raop2 8.0-1
pulseaudio-zeroconf-raop2 8.0-1
qt5-enginio 5.6.2-2
qwt-qt4 6.1.3-1
qwtpolar-qt4 1.1.1-1
rstudio-desktop-bin 1.1.383-4
ruby-archive-tar-minitar 0.5.2-2
ruby-commander-4.2.1 4.2.1-1
ruby-highline-1.6 1.6.21-1
ruby-httpclient 2.8.3-1
ruby-net-scp 1.2.1-2
ruby-net-ssh 4.1.0-1
ruby-net-ssh-2.9.2 2.9.2-1
ruby-net-ssh-gateway 2.0.0-1
ruby-net-ssh-multi 1.2.1-1
ruby-open4 1.3.4-1
samsung-printers 1.00.37-1
songs 3.0-1
spatialindex 1.8.5-1
spotify 1.0.70.399-1
tor-browser-bin 7.0a3-1
ttf-ms-fonts 2.0-10
ttf-oxygen 1:5.4.3-4
v4l-dvb-git r692.ecfc9bf-1
webkitgtk 2.4.11-6
xenstore 6.2.0-2
xorg-server-utils 7.6-4pacman -Q plasma-workspace qt5-base
plasma-workspace 5.11.5-1
qt5-base 5.10.0-2uname -a
Linux myhostname 4.14.11-1-ARCH #1 SMP PREEMPT Wed Jan 3 07:02:42 UTC 2018 x86_64 GNU/Linuxlddtree /usr/bin/kdeinit5
/usr/bin/kdeinit5 (interpreter => /lib64/ld-linux-x86-64.so.2)
libKF5Crash.so.5 => /usr/lib/libKF5Crash.so.5
libKF5CoreAddons.so.5 => /usr/lib/libKF5CoreAddons.so.5
libpthread.so.0 => /usr/lib/libpthread.so.0
libm.so.6 => /usr/lib/libm.so.6
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1
libQt5X11Extras.so.5 => /usr/lib/libQt5X11Extras.so.5
libstdc++.so.6 => /usr/lib/libstdc++.so.6
libKF5I18n.so.5 => /usr/lib/libKF5I18n.so.5
libX11.so.6 => /usr/lib/libX11.so.6
libdl.so.2 => /usr/lib/libdl.so.2
libxcb.so.1 => /usr/lib/libxcb.so.1
libXau.so.6 => /usr/lib/libXau.so.6
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6
libKF5WindowSystem.so.5 => /usr/lib/libKF5WindowSystem.so.5
libQt5Widgets.so.5 => /usr/lib/libQt5Widgets.so.5
libxcb-keysyms.so.1 => /usr/lib/libxcb-keysyms.so.1
libQt5Gui.so.5 => /usr/lib/libQt5Gui.so.5
libGL.so.1 => /usr/lib/libGL.so.1
libGLX.so.0 => /usr/lib/libGLX.so.0
libXext.so.6 => /usr/lib/libXext.so.6
libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0
libpng16.so.16 => /usr/lib/libpng16.so.16
libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0
libpcre.so.1 => /usr/lib/libpcre.so.1
libfreetype.so.6 => /usr/lib/libfreetype.so.6
libharfbuzz.so.0 => !!! circular loop !!!
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0
libgraphite2.so.3 => /usr/lib/libgraphite2.so.3
libz.so.1 => /usr/lib/libz.so.1
libQt5Core.so.5 => /usr/lib/libQt5Core.so.5
libsystemd.so.0 => /usr/lib/libsystemd.so.0
libgcrypt.so.20 => /usr/lib/libgcrypt.so.20
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0
librt.so.1 => /usr/lib/librt.so.1
liblzma.so.5 => /usr/lib/liblzma.so.5
liblz4.so.1 => /usr/lib/liblz4.so.1
libicui18n.so.60 => /usr/lib/libicui18n.so.60
libicuuc.so.60 => /usr/lib/libicuuc.so.60
libicudata.so.60 => /usr/lib/libicudata.so.60
libpcre2-16.so.0 => /usr/lib/libpcre2-16.so.0
libdouble-conversion.so.1 => /usr/lib/libdouble-conversion.so.1
libc.so.6 => /usr/lib/libc.so.6Offtopic: Back when I used awesome updates broke from now and than , my xinitrc and /etc/X11/... conf. Recently I had a lot of problems with wacom, still having them.
Last edited by blablubs82352 (2018-01-05 17:39:46)
Offline
#13 2018-01-05 20:01:36
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,435
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
You have a lot of useless cruft there. Remove all these pulseaudio packages and swap them for the repo versions, you are a full 3 version behind and the raop2 patches have been added upstream with pulseaudio 11. Remove libtxc_dxtn that is part of mesa now. Make sure your rebuild these plasma-applets if you are using them actively (not reinstalling the package, do a real rebuild) remove the really old kde4 libraries that don't have any active dependencies anymore (kdegames4,libkexi4 etc.) nothing in the repos depends on these anymore. get rid of chromium-pepper-flash and install the repo pepper-flash instead. And a few others.
Offline
#14 2018-01-06 16:23:46
- blablubs82352
- Member
- Registered: 2016-09-25
- Posts: 21
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
Thanks :-), Seems that the problem laid indeed in some outdated aur-package...
To me most likely libtxc_dxtn was the problem.
Lesson learned. I'll have a look now from time to time, which aur packages are installed.
Still with most pacakages I wasn't sure if I installed them once on a specific purpose, like pulseaudio-raop2 or just by dependency.
Offline
#15 2018-01-06 19:20:42
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,435
Re: [SOLVED] Plasma cannot connect to display :0 Plasma?
Most of those KDE libraries will have been dependencies yes. Usually pacman will warn you when it orphans packages, and in this case there is no harm in removing a few of them. Always make sure that you check if you still need a package pacman tells you it orphans. I find it unlikely to be libtxc that was the culprit here, that was one of the most recent changes and it shouldn't link any JSON anyway, my guess is on js17 resp the old pulseaudio which was required by the old version of pulseaudio but was depcrecated there as well, due to the lack of development there.
If this is solved now, please edit your original post's title and add [SOLVED] or similar.
Offline