Hi, I'm using arch for 3 days and have never used any linux OS before.
After entering password for root user in SDDM, terminal is opened for few seconds and returns to SDDM screen. I have no idea how to solve this problem. It happens in KDE Plasma Wayland. But if I use COSMIC everything works fine.
Before this happend I installed Brave Browser, used pacman -Syu command, tried to download steam and make it work by this instruction https://wiki.archlinux.org/title/Steam: I enable the multilib repository by uncommenting the [multilib] section in /etc/pacman.conf, installed steam package, downloaded mesa-amber and xf86-video-intel packages (I use intel 2 gen gpu btw) and that's all.
Hope this info helps to solve my problem.
Last edited by Azobioz (Today 17:40:47)
plasma crashes, please post your complete system journal for the boot *after* failing to start an X11 session :
sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'seth wrote:
plasma crashes, please post your complete system journal for the boot *after* failing to start an X11 session :
sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'
You're logging in fom cosmic-greeter into a cosmic session as user azobioz
This doesn't at all reflect the problem - you need to cause the failure and then upload the journal from a cosmic session (you should be able to log into that from sddm as well) or the console (ctrl+alt+f3)
Edit: logging in as actual root user (UID0) into a GUI session might be denied and is also a terrible idea. Don't do that tbw.
Last edited by seth (Today 18:06:10)
seth wrote:
You're logging in fom cosmic-greeter into a cosmic session as user azobioz
This doesn't at all reflect the problem - you need to cause the failure and then upload the journal from a cosmic session (you should be able to log into that from sddm as well) or the console (ctrl+alt+f3)Edit: logging in as actual root user (UID0) into a GUI session might be denied and is also a terrible idea. Don't do that tbw.
https://paste.c-net.org/WerewolfAbortion
I'll create a new regular user for logging into GUI session, thanks for the tip.
The user 'azobioz' will do
Jun 26 21:10:27 azobioz-host kwin_wayland[807]: querying vulkan devices failed: "ErrorInitializationFailed"
Jun 26 21:10:27 azobioz-host kwin_wayland[807]: No backend specified, automatically choosing drm
Jun 26 21:10:27 azobioz-host systemd[1]: Started Disk Manager.
Jun 26 21:10:27 azobioz-host kwin_wayland[807]: Invalid framebuffer status: "GL_FRAMEBUFFER_UNSUPPORTED"
Jun 26 21:10:27 azobioz-host kernel: traps: kwin_wayland[807] trap divide error ip:7f18a77c9321 sp:7ffd72639aa0 error:0 in i965_dri.so[9c9321,7f18a6f7c000+8c7000]
Jun 26 21:10:27 azobioz-host systemd-coredump[836]: Process 807 (kwin_wayland) of user 1000 terminated abnormally with signal 8/FPE, processing...
Jun 26 21:10:27 azobioz-host systemd[1]: Created slice Slice /system/systemd-coredump.
Jun 26 21:10:27 azobioz-host systemd[1]: Started Process Core Dump (PID 836/UID 0).
Jun 26 21:10:28 azobioz-host systemd-coredump[837]: Process 807 (kwin_wayland) of user 1000 dumped core.
Stack trace of thread 807:
#0 0x00007f18a77c9321 n/a (i965_dri.so + 0x9c9321)
#1 0x00007f18a74f16c8 n/a (i965_dri.so + 0x6f16c8)
#2 0x00007f18a7839afb n/a (i965_dri.so + 0xa39afb)
#3 0x00007f18afe22f54 n/a (libgbm.so.1 + 0x5f54)
#4 0x00007f18afe267db gbm_bo_create_with_modifiers (libgbm.so.1 + 0x97db)
#5 0x00007f18b31cb7dd n/a (libkwin.so.6 + 0x1cb7dd)
#6 0x00007f18b331f970 _ZN4KWin12EglSwapchain6createEPNS_23GraphicsBufferAllocatorEPNS_10EglContextERK5QSizejRKNS_12ModifierListE (libkwin.so.6 + 0x31f970)
#7 0x00007f18b35244ac n/a (libkwin.so.6 + 0x5244ac)
#8 0x00007f18b3525038 n/a (libkwin.so.6 + 0x525038)
#9 0x00007f18b3525695 n/a (libkwin.so.6 + 0x525695)
#10 0x00007f18b351ae5c n/a (libkwin.so.6 + 0x51ae5c)
#11 0x00007f18b3521930 _ZN4KWin6DrmGpu13testPipelinesEv (libkwin.so.6 + 0x521930)
#12 0x00007f18b3521b7d _ZN4KWin6DrmGpu19checkCrtcAssignmentE5QListIPNS_12DrmConnectorEERKS1_IPNS_7DrmCrtcEENSt6chrono10time_pointINSA_3_V212steady_clockENSA_8durationIlSt5ratioILl1ELl1000000000EEEEEE (libkwin.so.6 + 0x521b7d)
#13 0x00007f18b3521b7d _ZN4KWin6DrmGpu19checkCrtcAssignmentE5QListIPNS_12DrmConnectorEERKS1_IPNS_7DrmCrtcEENSt6chrono10time_pointINSA_3_V212steady_clockENSA_8durationIlSt5ratioILl1ELl1000000000EEEEEE (libkwin.so.6 + 0x521b7d)
#14 0x00007f18b3521b7d _ZN4KWin6DrmGpu19checkCrtcAssignmentE5QListIPNS_12DrmConnectorEERKS1_IPNS_7DrmCrtcEENSt6chrono10time_pointINSA_3_V212steady_clockENSA_8durationIlSt5ratioILl1ELl1000000000EEEEEE (libkwin.so.6 + 0x521b7d)
#15 0x00007f18b352201b _ZN4KWin6DrmGpu19checkCrtcAssignmentE5QListIPNS_12DrmConnectorEERKS1_IPNS_7DrmCrtcEENSt6chrono10time_pointINSA_3_V212steady_clockENSA_8durationIlSt5ratioILl1ELl1000000000EEEEEE (libkwin.so.6 + 0x52201b)
#16 0x00007f18b352246e _ZN4KWin6DrmGpu24testPendingConfigurationEv (libkwin.so.6 + 0x52246e)
#17 0x00007f18b3501ea6 _ZN4KWin10DrmBackend18applyOutputChangesERKNS_19OutputConfigurationE (libkwin.so.6 + 0x501ea6)
#18 0x00007f18b348ec0d _ZN4KWin9Workspace24applyOutputConfigurationERNS_19OutputConfigurationE (libkwin.so.6 + 0x48ec0d)
#19 0x00007f18b348ef30 _ZN4KWin9Workspace25updateOutputConfigurationEv (libkwin.so.6 + 0x48ef30)
#20 0x00007f18b34972c6 _ZN4KWin9Workspace31slotOutputBackendOutputsQueriedEv (libkwin.so.6 + 0x4972c6)
#21 0x00007f18b348c842 _ZN4KWin9Workspace4initEv (libkwin.so.6 + 0x48c842)
#22 0x00007f18b3301b4f _ZN4KWin11Application15createWorkspaceEv (libkwin.so.6 + 0x301b4f)
#23 0x00005643de204d8b n/a (kwin_wayland + 0x4bd8b)
#24 0x00005643de1f801a n/a (kwin_wayland + 0x3f01a)
#25 0x00007f18afc27741 n/a (libc.so.6 + 0x27741)
#26 0x00007f18afc27879 __libc_start_main (libc.so.6 + 0x27879)
#27 0x00005643de1fc635 n/a (kwin_wayland + 0x43635)2nd gen is not the CPU but the GPU, you've gen6 HW which should™ be covered by the crocus driver.
Does mesa instead of mesa-amber not work (either)? (Remove xf86-video-intel)
seth wrote:
Does mesa instead of mesa-amber not work (either)? (Remove xf86-video-intel)
In the process of installing mesa-amber package there was a conflict with mesa package and there was a choice to delete mesa, I chose to delete it. Aren't these package similar in functionality or mesa-amber is dependent of mesa? Removed xf86-video-intel.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。