[SOLVED]Failed to start Xorg[SOLVED]

PqndqDX · 2021-04-26 19:31:42

error. there is no package

seth · 2021-04-26 20:16:32

Possibly unrelated but you're concurrently running networkmanager and dhcpcd what will destabilize your network connection.
Pick one, disable the other.

The journal still doesn't see to cover an attempt to log into a KDE session, there's an SDDM session and an openbox one and that's it. But no further mentioning of plasma or ksmserver.
The big DEs implicitly rely on a sane $HOME where you esp. have writing access - since you're using a non-standard path here, can you verify full access to /mnt/Data/home/qenta/ ?

paulkerry · 2021-04-26 20:25:10

I'm not sure what your status is now after the flurry of replies with others trying to help you and you further mentioning sddm.
Going back to my earlier post, post #4 from loqs and your reply in post #5, you didn't mention if you had also installed the xorg-twm package ( https://archlinux.org/packages/extra/x86_64/xorg-twm/ ) which is what the

twm &

would try to run if you were still using the xinitrc file.

loqs · 2021-04-26 21:10:17

https://bugs.archlinux.org/task/70597 ?

PqndqDX · 2021-04-26 22:24:01

:seth
I've disabled dhcpcd.service. I can see directories and ".directories" with ls command at $HOME. also can cd command. but my keyboard layout is strenge. after using Openbox session, my keyboard is english layout. I tried to set german several times but still english layout.

:paulkerry
yes twm is alredy installed. when type "twm &", output is "another window manager is already running. on screen 0?" is that correct?

:loqs
I downgraded sddm but didn't help..

Last edited by PqndqDX (2021-04-26 22:38:43)

loqs · 2021-04-26 22:49:14

Please try creating a new user with a home directory in the default location under /home, does logging into sddm as the new user produce the same result?
Have you installed anything other than themes using sudo make install?

PqndqDX · 2021-04-26 23:28:29

I made a new account and now Plasma is running!!!
It means my home directry is wrong?

Last edited by PqndqDX (2021-04-26 23:29:18)

loqs · 2021-04-27 00:18:38

What is the output of

stat /mnt/Data/home/qenta/
findmnt --target /mnt/Data/home/qenta/

PqndqDX · 2021-04-27 00:33:31

here it is

[momoqo@T-90Q ~]$ stat /mnt/Data/home/qenta/
  File: /mnt/Data/home/qenta/
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 10304h/66308d   Inode: 43515906    Links: 31
Access: (0700/drwx------)  Uid: ( 1000/   qenta)   Gid: ( 1000/   qenta)
Access: 2021-04-27 01:31:36.030530088 +0200
Modify: 2021-04-27 01:31:35.940530088 +0200
Change: 2021-04-27 01:31:35.940530088 +0200
 Birth: 2021-02-20 10:55:56.468690211 +0100
[momoqo@T-90Q ~]$ findmnt --target /mnt/Data/home/qenta/
TARGET    SOURCE         FSTYPE OPTIONS
/mnt/Data /dev/nvme1n1p1 ext4   rw,relatime,discard

seth · 2021-04-27 05:30:58

The "discard" option might have corrupted some data, https://wiki.archlinux.org/index.php/So … nuous_TRIM
We still can't say *why* your original plasma session fails because

seth wrote:

The journal still doesn't see to cover an attempt to log into a KDE session

We need a journal that covers a failed attempt to log into KDE.

PqndqDX · 2021-04-27 20:25:38

my status of fstrim war "inactive", and also

journalctl -u fstrim

gives nothing back. just

 --No Entries--

.

seth · 2021-04-27 20:37:54

Because you don't have the fstrim service enabled but use the (pot. fragile) continuous trim via the "discard" mount option.
The journal we're looking for is more sth. like

sudo journalctl -b

*after* you attempted and failed to log into a KDE session.

PqndqDX · 2021-04-27 21:01:42

now I can login with terminal tty2(befor was tty3). and after type startx, monitor looks like a this photo
https://imgur.com/eZXEQX9

here is journal after login fail. please check out.
http://ix.io/3gPr

seth · 2021-04-27 21:17:23

The only login there is on TTY2 via /bin/login - did you reboot after the failed login attempt?
If so, you need to provide the previous journal ("sudo journactl -b -1")

PqndqDX · 2021-04-27 22:16:19

yes, I did login again, so here is with "-1".
http://ix.io/3h0X

seth · 2021-04-28 05:27:12

No, it's "journalctl -b --since=2021-04-28 00:09" as the journal excerpt that covers nothing but the journal call because the target date is in the future, says…

PqndqDX · 2021-04-28 21:17:23

Mr Seth, I appreciate your help, thank you very much. and Sorry I was a bit busy today and late reply.
I tried again ix.io. please check through.
http://ix.io/3k8k

seth · 2021-04-29 06:17:32

This is - again - just a getty login on TTY2…

1. Reboot
2. Try to log into KDE from SDDM
3. Reboot
4. Log into a functional session
5.

sudo journalctl -b -1 | curl -F 'f:1=<-' ix.io

6. Post the link you get in return.

PqndqDX · 2021-04-29 15:59:13

sorry for my missunderstanding.
here it ishttp://ix.io/31ka

Last edited by PqndqDX (2021-04-29 16:05:38)

seth · 2021-04-29 16:02:07

That's 15 bytes of random binary data…

Last edited by seth (2021-04-29 16:02:42)

PqndqDX · 2021-04-29 16:12:51

sorry, i don't understand why but ix.io returns this... I tried several times but same..
I will try later again!

Last edited by PqndqDX (2021-04-29 16:18:44)

PqndqDX · 2021-04-29 21:50:53

with ix.io get same result then I tried with sprunge.us
http://sprunge.us/rDIdpb

I hope I didn't wrong.
-reboot
-login from SDDM
-shutdown by power button
-login from tty2
-sudo jour...

dakota · 2021-04-30 01:16:19

PqndqDX wrote:

sorry, i don't understand why but ix.io returns this... I tried several times but same..
I will try later again!

I don't know why it fails, but I had the same problem recently. Some uploads succeeded, some failed, using the same command.
You might try pushing the data into a file, first, then uploading the file. It *should* be the exact same thing, but for me the file upload worked after several attempts. (I had to change the file name after a failed attempt.)

sudo journalctl -b -1 > tempFile
cat tempFile | curl -F 'f:1=<-' ix.io

... and then follow the link to make sure it uploaded correctly.

Cheers,

Last edited by dakota (2021-04-30 01:17:26)

seth · 2021-04-30 06:34:24

Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr: Connected output 71 to CRTC 63
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xcb.helper: Detected XRandR 1.6
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xcb.helper: Event Base:  89
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xcb.helper: Event Error:  147
Apr 29 23:35:16 T-90Q kded5[1424]: kscreen.kded: PowerDevil SuspendSession action not available!
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr: XRandR::setConfig
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr: Requested screen size is QSize(640, 480)
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr: Needed CRTCs:  1
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr: Actions to perform: 
                                                               Primary Output: true
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr:                 Old: 69 
                                                                       New: 71
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr:         Change Screen Size: true
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr:                 Old: QSize(3840, 2160) 
                                                                       Intermediate: QSize(3840, 2160) 
                                                                       New: QSize(640, 480)
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr:         Disable outputs: false
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr:         Change outputs: true
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr:                  (71)
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr:         Enable outputs: false
Apr 29 23:35:16 T-90Q kscreen_backend_launcher[1563]: kscreen.xrandr: RRSetCrtcConfig (change output) 
                                                               Output: 71 ( "HDMI-1" ) 
                                                               CRTC: 63 
                                                               Pos: QPoint(0,0) 
                                                               Mode: 196 KScreen::Mode(Id: "196" , Size: QSize(640, 480) @ 60 ) 
                                                               Rotation: KScreen::Output::None
…
Apr 29 23:35:16 T-90Q kernel: ------------[ cut here ]------------
Apr 29 23:35:16 T-90Q kernel: WARNING: CPU: 0 PID: 540 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:953 dc_commit_state+0x98a/0xa70 [amdgpu]
Apr 29 23:35:16 T-90Q kernel: Modules linked in: rfcomm hidp cmac algif_hash algif_skcipher af_alg nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib bnep btusb btrtl btbcm btintel bluetooth nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 ecdh_generic nft_reject ecc ch341 nft_ct nft_chain_nat nf_tables ip6table_nat ip6table_mangle ip6table_raw ip6table_security joydev iptable_nat mousedev nf_nat nf_conntrack hid_multitouch nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_mangle iptable_raw iptable_security ip_set snd_hda_codec_realtek nfnetlink usbhid snd_hda_codec_generic ledtrig_audio ip6table_filter snd_hda_codec_hdmi ip6_tables iptable_filter snd_hda_intel snd_intel_dspcfg iwlmvm soundwire_intel intel_rapl_msr soundwire_generic_allocation intel_rapl_common amdgpu mac80211 soundwire_cadence snd_hda_codec snd_hda_core snd_hwdep libarc4 edac_mce_amd wmi_bmof nct6683 soundwire_bus gpu_sched iwlwifi squashfs ext4 kvm snd_soc_core i2c_algo_bit drm_ttm_helper crc32c_generic crc16 mbcache snd_compress jbd2 ttm loop
Apr 29 23:35:16 T-90Q kernel:  irqbypass ac97_bus crct10dif_pclmul crc32c_intel snd_pcm_dmaengine cfg80211 ghash_clmulni_intel drm_kms_helper snd_pcm aesni_intel r8169 snd_timer cec crypto_simd snd ccp cryptd realtek glue_helper sp5100_tco syscopyarea mdio_devres sysfillrect sysimgblt rapl soundcore libphy fb_sys_fops pcspkr rfkill i2c_piix4 k10temp rng_core acpi_cpufreq gpio_amdpt pinctrl_amd gpio_generic wmi mac_hid drm fuse crypto_user agpgart bpf_preload ip_tables x_tables f2fs xhci_pci crc32_pclmul xhci_pci_renesas
Apr 29 23:35:16 T-90Q kernel: CPU: 0 PID: 540 Comm: Xorg Not tainted 5.11.16-arch1-1 #1
Apr 29 23:35:16 T-90Q kernel: Hardware name: Micro-Star International Co., Ltd. MS-7C91/MPG B550 GAMING EDGE WIFI (MS-7C91), BIOS 1.40 10/29/2020
Apr 29 23:35:16 T-90Q kernel: RIP: 0010:dc_commit_state+0x98a/0xa70 [amdgpu]
Apr 29 23:35:16 T-90Q kernel: Code: 89 f7 e8 79 79 d3 c1 e9 dc f8 ff ff 0f 1f 44 00 00 e9 7c fd ff ff 31 d2 e9 05 f8 ff ff 80 b8 80 03 00 00 00 0f 84 15 fd ff ff <0f> 0b e9 0e fd ff ff 48 89 ef e8 b7 bb 00 00 48 89 ef e8 3f 79 d3
Apr 29 23:35:16 T-90Q kernel: RSP: 0018:ffffaed400c6b808 EFLAGS: 00010202
Apr 29 23:35:16 T-90Q kernel: RAX: ffff8cd70f62ec00 RBX: ffff8cd70d4a01e8 RCX: 0000000000000000
Apr 29 23:35:16 T-90Q kernel: RDX: 0000000000001464 RSI: 0000000000000e11 RDI: 000009909b87a6fc
Apr 29 23:35:16 T-90Q kernel: RBP: 0000000000000000 R08: ffffaed400c6b7d4 R09: 00000000000003e8
Apr 29 23:35:16 T-90Q kernel: R10: 0000000000000002 R11: 8000000100000000 R12: ffff8cd70d4a1ec8
Apr 29 23:35:16 T-90Q kernel: R13: 0000000000000001 R14: ffff8cd6dc610000 R15: ffff8cd70d4a0000
Apr 29 23:35:16 T-90Q kernel: FS:  00007f85a7736940(0000) GS:ffff8cd9dea00000(0000) knlGS:0000000000000000
Apr 29 23:35:16 T-90Q kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 29 23:35:16 T-90Q kernel: CR2: 00007f95c9b41048 CR3: 000000011c420000 CR4: 0000000000350ef0
Apr 29 23:35:16 T-90Q kernel: Call Trace:
Apr 29 23:35:16 T-90Q kernel:  amdgpu_dm_atomic_commit_tail+0x5f7/0x2660 [amdgpu]
Apr 29 23:35:16 T-90Q kernel:  ? __free_one_page+0x63/0x440
Apr 29 23:35:16 T-90Q kernel:  ? free_one_page+0x5f/0xd0
Apr 29 23:35:16 T-90Q kernel:  ? kfree+0x3eb/0x430
Apr 29 23:35:16 T-90Q kernel:  commit_tail+0x94/0x130 [drm_kms_helper]
Apr 29 23:35:16 T-90Q kernel:  drm_atomic_helper_commit+0x113/0x140 [drm_kms_helper]
Apr 29 23:35:16 T-90Q kernel:  drm_atomic_helper_set_config+0x70/0xb0 [drm_kms_helper]
Apr 29 23:35:16 T-90Q kernel:  drm_mode_setcrtc+0x233/0x770 [drm]
Apr 29 23:35:16 T-90Q kernel:  ? drm_mode_getcrtc+0x180/0x180 [drm]
Apr 29 23:35:16 T-90Q kernel:  drm_ioctl_kernel+0xb2/0x100 [drm]
Apr 29 23:35:16 T-90Q kernel:  drm_ioctl+0x215/0x390 [drm]
Apr 29 23:35:16 T-90Q kernel:  ? drm_mode_getcrtc+0x180/0x180 [drm]
Apr 29 23:35:16 T-90Q kernel:  amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
Apr 29 23:35:16 T-90Q kernel:  __x64_sys_ioctl+0x83/0xb0
Apr 29 23:35:16 T-90Q kernel:  do_syscall_64+0x33/0x40
Apr 29 23:35:16 T-90Q kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Apr 29 23:35:16 T-90Q kernel: RIP: 0033:0x7f85a8138e6b
Apr 29 23:35:16 T-90Q kernel: Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 af 0c 00 f7 d8 64 89 01 48
Apr 29 23:35:16 T-90Q kernel: RSP: 002b:00007fff1a62cce8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Apr 29 23:35:16 T-90Q kernel: RAX: ffffffffffffffda RBX: 00007fff1a62cd20 RCX: 00007f85a8138e6b
Apr 29 23:35:16 T-90Q kernel: RDX: 00007fff1a62cd20 RSI: 00000000c06864a2 RDI: 000000000000000e
Apr 29 23:35:16 T-90Q kernel: RBP: 00000000c06864a2 R08: 0000000000000000 R09: 00005591fbcddee0
Apr 29 23:35:16 T-90Q kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00005591fb1f7590
Apr 29 23:35:16 T-90Q kernel: R13: 000000000000000e R14: 00005591fb0834b8 R15: 0000000000000001
Apr 29 23:35:16 T-90Q kernel: ---[ end trace a4bb5d901103c977 ]---

It crashes when kscreen tries to restore/set a VGA resolution.
Obviously amdgpu shouldn't™ crash, but resetting the kscreen config for your user will likely prevent this, https://community.kde.org/Solid/Project … umentation
Ie. remove ~/.local/share/kscreen before logging into plasma.

PqndqDX · 2021-04-30 20:02:41

WOW Now I can login!!! I'm writing from KDE Plasma!!
https://imgur.com/Y7omaJi

thank you thank you very much, Mr seth!!!

Arch Linux

#26 2021-04-26 19:31:42

Re: [SOLVED]Failed to start Xorg[SOLVED]

#27 2021-04-26 20:16:32

Re: [SOLVED]Failed to start Xorg[SOLVED]

#28 2021-04-26 20:25:10

Re: [SOLVED]Failed to start Xorg[SOLVED]

#29 2021-04-26 21:10:17

Re: [SOLVED]Failed to start Xorg[SOLVED]

#30 2021-04-26 22:24:01

Re: [SOLVED]Failed to start Xorg[SOLVED]

#31 2021-04-26 22:49:14

Re: [SOLVED]Failed to start Xorg[SOLVED]

#32 2021-04-26 23:28:29

Re: [SOLVED]Failed to start Xorg[SOLVED]

#33 2021-04-27 00:18:38

Re: [SOLVED]Failed to start Xorg[SOLVED]

#34 2021-04-27 00:33:31

Re: [SOLVED]Failed to start Xorg[SOLVED]

#35 2021-04-27 05:30:58

Re: [SOLVED]Failed to start Xorg[SOLVED]

#36 2021-04-27 20:25:38

Re: [SOLVED]Failed to start Xorg[SOLVED]

#37 2021-04-27 20:37:54

Re: [SOLVED]Failed to start Xorg[SOLVED]

#38 2021-04-27 21:01:42

Re: [SOLVED]Failed to start Xorg[SOLVED]

#39 2021-04-27 21:17:23

Re: [SOLVED]Failed to start Xorg[SOLVED]

#40 2021-04-27 22:16:19

Re: [SOLVED]Failed to start Xorg[SOLVED]

#41 2021-04-28 05:27:12

Re: [SOLVED]Failed to start Xorg[SOLVED]

#42 2021-04-28 21:17:23

Re: [SOLVED]Failed to start Xorg[SOLVED]

#43 2021-04-29 06:17:32

Re: [SOLVED]Failed to start Xorg[SOLVED]

#44 2021-04-29 15:59:13

Re: [SOLVED]Failed to start Xorg[SOLVED]

#45 2021-04-29 16:02:07

Re: [SOLVED]Failed to start Xorg[SOLVED]

#46 2021-04-29 16:12:51

Re: [SOLVED]Failed to start Xorg[SOLVED]

#47 2021-04-29 21:50:53

Re: [SOLVED]Failed to start Xorg[SOLVED]

#48 2021-04-30 01:16:19

Re: [SOLVED]Failed to start Xorg[SOLVED]

#49 2021-04-30 06:34:24

Re: [SOLVED]Failed to start Xorg[SOLVED]

#50 2021-04-30 20:02:41

Re: [SOLVED]Failed to start Xorg[SOLVED]

Board footer