Bug 478399

Summary:	Wayland session not starting on intel igpu.
Product:	[Plasma] plasmashell	Reporter:	punchcake
Component:	Startup process	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	kde, nate
Priority:	NOR
Version First Reported In:	5.27.10
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	wayland-session.log

Description punchcake 2023-12-11 14:03:16 UTC

Hi, I just installed endeavorOS on my laptop with KDE plasma, everything is as up to date as it should be but the wayland session will not start for some reason. 

STEPS TO REPRODUCE
1. Try to login to wayland session

OBSERVED RESULT
Session will not start

EXPECTED RESULT
Session should start and operate normally

SOFTWARE/OS VERSIONS:

Linux/KDE Plasma: s
Operating System: EndeavourOS 
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
Kernel Version: 6.6.5-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 12 × 12th Gen Intel® Core™ i5-1235U
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: LENOVO
Product Name: 82RK
System Version: IdeaPad 3 15IAU7

Comment 1 Nate Graham 2023-12-12 17:13:17 UTC

Is this a regression? Did it work in the past?

What happens instead of logging in?

Can you attach the file ~/.local/share/sddm/wayland-session.log?

Comment 2 punchcake 2023-12-12 18:04:26 UTC

Created attachment 164115 [details]
wayland-session.log

Comment 3 punchcake 2023-12-12 18:05:56 UTC

(In reply to Nate Graham from comment #1)
> Is this a regression? Did it work in the past?
> 
> What happens instead of logging in?
> 
> Can you attach the file ~/.local/share/sddm/wayland-session.log?

I am unsure, wayland used to work fine on Kubuntu but not on endavourOS for some reason, Everything is fine on the xorg side though. When i log into wayland i just get a black screen and i see my cursor and then it kicks me back to login.

Comment 4 Nate Graham 2023-12-13 22:13:33 UTC

Pasting inline:




X.Org X Server 1.21.1.9
X Protocol Version 11, Revision 0
Current Operating System: Linux faisal-82rk 6.6.5-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 08 Dec 2023 17:06:25 +0000 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=f454c0d0-f522-44a4-aa76-84862fbdfdc3 rw nowatchdog nvme_load=YES resume=UUID=dd47d0db-0f1b-4500-8eaf-9ffb2f62317e loglevel=3
 
Current version of pixman: 0.42.2
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/faisal/.local/share/xorg/Xorg.1.log", Time: Tue Dec 12 20:59:04 2023
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
/etc/X11/xinit/xinitrc: line 55: exec: xterm: not found
/etc/X11/xinit/xinitrc: line 54: xterm: command not found
/etc/X11/xinit/xinitrc: line 51: twm: command not found
/etc/X11/xinit/xinitrc: line 52: xclock: command not found
/etc/X11/xinit/xinitrc: line 53: xterm: command not found
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

Comment 5 Nate Graham 2023-12-13 22:15:10 UTC

There seems to be something wrong with the way XWayland or even the X server itself are set up on your system. I'd recommend seeking support in a distro-specific forum.