You are not logged in.

#1 2022-05-14 16:32:26

kavex
Member
Registered: 2022-05-14
Posts: 32

Startx fails with mismatch in [file]

Hello,
I spent the last few days installing Arch on encrypted zfs (using zfs built in encryption) on my computer. Since Grub does not seem to work with zfs built in encryption, I choose systemd-boot as my bootloader. After some trouble shooting the computer booted into arch nicely everytime I start it and asks me for the encryption passphrase of the zpool.
My computer is using a GTX1060 6GB and an intel chipset as GPUs and an i5 7500k CPU overclocked to 4.2GHz. As harddrived it uses a 250GB SSD (sda1 = /boot w. Fat32 where I generate my kernel, sda2 = /efi w. Fat32 where I installed systemd-boot onto, sda3 = Solaris Rolt w. ZFS), a 4TB HDD (sdb1 = Solaris Root w. ZFS, sdb2 = Microsoft basic data w. NTFS which contains some personal stuff from a previous windows installation, sdb3 = swap 64G) and a 1TB HDD (sdc1 = Solaris w. ZFS, sdc2 = Linux data w. Ext4).
So much for my setup.
My problem is that I wanted to install sddm and KDE to run it on xorg. So I installed xorg-server, xorg, intel and nvidia drivers, plasma, kde-applications, wayland and kde-wayland-session.
At first sddm started fine, but froze after login. Then I figured that the startx command wasn't available so I installed xorg-xinit.
Then startx didn't want to start. I googled and figured I might need to add i915 to my kernel, so I made sure the driver package was installed and edited my mkinitcpio.conf

MODULES=(i915)
HOOKS=(base udev autodetect modconf block keyboard zfs filesystem fsck)
 

and rebuilt my kernel images and moved them to my efi directory for systemd-boot to boot into.
Now everytime I run sddm now I get stuck in a blackscreen and when I run startx I get

waiting for X server to shut down [ 678.432499] i915 0000:00:02.0: [drm] *ERROR* [CRTC:51:pipe A] mismatch in pch_pfit.enabled (expected no, found yes)lostnd n
[ 678.432501] i915 0000:00:02.0: [drm] *ERROR* [CRTC:51:pipe A] mismatch in scaler_state.scaler_id (expected -1, found 0)
(II) Server terminated successfully (0). Closing log file.

I will now post some paragraphs of logs and configfiles from which I feel they could be relevant. Sorry for not providing the full logs, byt I can't copy paste the text since it is not in a virtual box and I need to type this on my phone.

# var/log/Xorg.0.log
Many
No input driver specified, ignoring this device 
And
This device may have been added with another device file.
# /etc/home/kavex/.xinit
does not exist
# /etc/home/kavex/.Xauthority
Is empty

I am sorry for providing so few informations, but I will be happy to provide more if asked for it, I just don't really know whats relevant here.

Thanks in advance!

Last edited by kavex (2022-05-14 16:33:34)

Online

#2 2022-05-14 16:53:11

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 26,701
Website

Re: Startx fails with mismatch in [file]

kavex wrote:

Sorry for not providing the full logs, byt I can't copy paste the text ...

Yes you can.  And it looks like you'll need to as your paraphrasing is problematic.

kavex wrote:

I wanted ... to run it on xorg. So I installed ... wayland and kde-wayland-session.

That doesn't add up.

kavex wrote:

At first sddm started fine, but froze after login. Then I figured that the startx command wasn't available

SDDM/KDE do not need startx - it's completely irrelevant.

kavex wrote:

so I installed xorg-xinit.  Then startx didn't want to start.

What do you mean it wouldn't start?  Were you trying to run startx manually?  Did you create an ~/.xinitrc?  If not it's not expected to work.

kavex wrote:

I googled and figured I might need to add i915 to my kernel

What google result led you to this conclusion?

Last edited by Trilby (2022-05-14 17:02:18)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#3 2022-05-14 19:14:54

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

Trilby wrote:

Yes you can.  And it looks like you'll need to as your paraphrasing is problematic.

Okay. I will answer your questions and provide the full log fiiles from above.

Trilby wrote:

That doesn't add up.

Yes, I installed wayland swell, just to have a backup. Assuming you were referring to me installing wayland there aswell. I tried getting a session with wayland as sddm was still working and that didn't start aswell, just caught me in a black screen.

Trilby wrote:

SDDM/KDE do not need startx - it's completely irrelevant.

Oh, that's good to know! Then nevermind that. I just thought that being able to run it manually would help me to get more logs about the problem.

Trilby wrote:

What do you mean it wouldn't start?  Were you trying to run startx manually?  Did you create an ~/.xinitrc?  If not it's not expected to work.

I tried starting sddm, aswell as running startx manually. Sddm results in a black screen and start x results in the error

X.Org X Server 1.21.1.3
X Protocol Version 11, Revision0
Current Operating System: Linux Zafkiel 5.17.6-arch-1 #1 SMP PREEMPT Tue, 10 May 2022 23:00:39 +0000 x86_64
Kernel command line: initrd=\archzfs\intel-ucode.img root=ZFS=zroot/ROOT/arch rw

Current version of pixman: 0.40.0
               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: "var/log/Xorg.0.log", Time: Sat May 14 19:53:11 2022
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
waiting for X server to shut down [ 6558.134446] i915 0000:00:02.0: [drm] *ERROR* [CRTC:51:pipe A] mismatch in pch_pfit.enable (expected no, found yes)nd not f
[ 6558.134448] i915 0000:00:02:0: [drm] *ERROR* [CRTC:51:pipe A] mismatch in scaler_state.scaler_id (expected -1, found 0)
(II) Server terminated successfully (0). Closing log file.
Trilby wrote:

What google result led you to this conclusion?

Sadly I am unable to find that post. I even looked through my history... But I found another post in which it helped.

So my .Xauthority file is empty.
I didn't have a .xinitrc file in my home directory, so I copied the system default config in there, just to be sure.

#!/bin/sh

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then

   xrdb -merge $sysresources

fi
if [ -f $sysmodmap ]; then
   xmodmap $sysmodmap
fi
if [ -f "$userresources" ]; then

   xrdb -merge "$userresources"
fi
if [ -f "$usermodmap" ]; then
   xmodmap "$supermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinitrc.d] ; then
 for f in /etc/X11/xinitr.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
  done
  unset f
fi

tdm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login

Now for /var/log/Xorg.0.log
I posted it here

I hope this information is better than before

Last edited by kavex (2022-05-14 20:18:38)

Online

#4 2022-05-14 19:27:07

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 26,701
Website

Re: Startx fails with mismatch in [file]

kavex wrote:

I just thought that being able to run it manually would help me to get more logs about the problem.

That much is definitely true - startx/xinit is not used by sddm, but testing out whether you have a functional Xorg (with startx) is a good first step before even trying to get a DE running.

But from the logs it appears Xorg is running just fine and exits successfully.  I gather KDE may be erroring out.  But first, you can try startx again, but you'd need to install xterm and twm if you use that template xinitrc as it is.  That may be a worthwhile test.  Then if that works, we'll know the issue is with something KDE specific.  If startx (with twm and xterm installed) fails, please post the log from that attempt as text (or as a link to a file sharing site), not as a series of images.

EDIT: any the xorg log from startx will not be under /var/log, it will be under ~/.local/share/xorg/

Last edited by Trilby (2022-05-14 19:28:02)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#5 2022-05-14 19:58:57

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: Startx fails with mismatch in [file]

The xorg screenshots (please upload the file, reading screenshot isn't fun) indicate an issue w/ the nvidia driver, resulting in the VESA driver running the main GPU and that's not gonna meet SDDMs or KDEs standards.
PLease upload the complete system journal (NOT! screenshots!)

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Online

#6 2022-05-14 20:06:55

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

I installed twm and xterm, but startx still gives the same result. ~/.local/share/xorg does not exist. Only a sddm folder.

System jounral is pasted here.

I also edited my post and reuploadet /var/log/Xorg.0.log here

Last edited by kavex (2022-05-14 20:19:28)

Online

#7 2022-05-14 20:17:28

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: Startx fails with mismatch in [file]

May 14 21:40:50 Zafkiel kernel: NVRM: API mismatch: the client has the version 515.43.04, but
                                NVRM: this kernel module has the version 510.68.02.  Please
                                NVRM: make sure that this kernel module and all NVIDIA driver
                                NVRM: components have the same version.
pacman -Qs nvidia

Online

#8 2022-05-14 20:22:29

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

seth wrote:

pacman -Qs nvidia

Results in

local/egl-wayland 2:1.1.9+r3+g582b2d3-1
    EGLStream-based Wayland external platform
local/libvdpau 1.5-1
    Nvidia VDPAU library
local/libxnvctrl 515.43.04-1
    NVIDIA NV-CONTROL X extension
local/nvidia 515.43.04-2
    NVIDIA drivers for linux
local/nvidia-settings 515.43.04-1
    Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 515.43.04-1
    NVIDIA drivers utilities
local/xf86-video-nouveau 1.0.17-2 (xorg-drivers)
    Open Source 3D acceleration driver for nVidia cards

Online

#9 2022-05-14 20:23:48

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: Startx fails with mismatch in [file]

Did you put the nvidia module into the initramfs and forgot to update the latter?
https://wiki.archlinux.org/title/NVIDIA#pacman_hook

Online

#10 2022-05-14 20:33:17

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

Everytime I use pacman -S nvidia I get

resolving dependencies...
looking for conflicting packages...

Packages (1) nvidia-515.43.04-2

Total Installed Size:  28.01 MiB
Net Upgrade Size:       0.00 MiB

checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
reinstalling nvidia...
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Update Nvidia module in initcpio
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.17.6-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [zfs]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: module not found: `nvidia'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.17.6-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [zfs]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: module not found: `nvidia'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.

So I think my kernel does probably not contain the nvidia drivers

Online

#11 2022-05-14 20:37:12

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: Startx fails with mismatch in [file]

"Yes"-  somewhat.

pacman -Qkk nvidia

and post your mkinitcpio.conf (for the one in #1 doesn't explain the error)

Online

#12 2022-05-14 20:44:07

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

seth wrote:

pacman -Qkk nvidia

Results in

nvidia: 14 total files, 0 altered files
seth wrote:

and post your mkinitcpio.conf (for the one in #1 doesn't explain the error)

Contents of /etc/mkinitcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=(i915 nvidia)

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect modconf block keyboard zfs filesystems fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

Online

#13 2022-05-14 20:48:05

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: Startx fails with mismatch in [file]

Ah, nvidia-515.43.04-2 is built for 5.17.7-arch1-1
Don't run partial updates.

sudo pacman -Syu

Online

#14 2022-05-14 20:51:46

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

seth wrote:

Ah, nvidia-515.43.04-2 is built for 5.17.7-arch1-1
Don't run partial updates.

sudo pacman -Syu

This results in

:: Synchronizing package databases...
 core downloading...
 extra downloading...
 community downloading...
 multilib downloading...
 archzfs downloading...
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
:: installing linux (5.17.7.arch1-1) breaks dependency 'linux=5.17.6.arch1-1' required by zfs-linux
error: failed to prepare transaction (could not satisfy dependencies)

Last edited by kavex (2022-05-14 20:52:40)

Online

#15 2022-05-14 21:07:55

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: Startx fails with mismatch in [file]

Don't update (the kernel and out of tree drivers) until the zfs module caught up or use https://aur.archlinux.org/packages/zfs-dkms
In the meantime, you can downgrade nvidia to match the installed kernel.
https://archive.archlinux.org/packages/n/nvidia/ - 515.43.04-1 should™ fit your kernel and the nviida-utils package.

Online

#16 2022-05-14 21:30:32

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

Thanks! Now my sddm starts fine, but freezes (with cursor still movable) after login.

I did another journalctl -b and uploaded it here assuming it might help to find the error

Online

#17 2022-05-14 22:28:47

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

And when I do plasmashell I get

qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposit-glx, xcb.

Aborted (core dumped)

Last edited by kavex (2022-05-14 22:28:59)

Online

#18 2022-05-15 06:06:51

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: Startx fails with mismatch in [file]

sddm starts fine, but freezes (with cursor still movable) after login

when I do plasmashell

?
"do plasmashell" from the console?

Please post an updated xorg log and a journal that covers an attempt to login from SDDM (if that is what causes the freeze described in #16) - the last journal only has two root logins on TTY1 and TTY2

Sidebar: you're running networkmanager and dhcpcd concurrently.
Pick one, disable the other (since there doesn't seem to be a wifi NIC, dhcpcd would suffice)

Online

#19 2022-05-15 11:17:03

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

seth wrote:

do plasmashell" from the console?

Yes, I executed plasmashell from the console yesterday.
Well  today I tried to start sddm and log in, but I get stuck with a blackscreen and the kde cursor (moveable) on it.
I hope my logs captured everything.

seth wrote:

Please post an updated xorg log and a journal that covers an attempt to login from SDDM

I uploaded my jounral here
And I have a (hopefully) updated xorg log here

seth wrote:

Sidebar: you're running networkmanager and dhcpcd concurrently.
Pick one, disable the other (since there doesn't seem to be a wifi NIC, dhcpcd would suffice)

I disabled networkmanager and enabled dhcpcd with systemctl.

Last edited by kavex (2022-05-15 13:05:28)

Online

#20 2022-05-15 13:02:27

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: Startx fails with mismatch in [file]

I executed plasmashell from the console yesterday

As you figured: that's not gonna work.

but I get stuck with a blackscreen and the kde cursor (moveable) on it.

What if you don't log into KDE, but eg. an openbox session?

There's

May 15 13:07:26 Zafkiel sddm-helper[1818]: Starting: "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
May 15 13:07:26 Zafkiel sddm-helper[1823]: Adding cookie to "/home/kavex/.Xauthority"

but then plasma doesn't actually start at all, no errors from it, nothing.

pacman -Qss plasma-workspace

You're aware that this is an optimus system and you're running on the nvidia chip?

Online

#21 2022-05-15 15:22:04

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

seth wrote:

What if you don't log into KDE, but eg. an openbox session?

I tried to make sddm start a gnome session, but it behaved the same like with kde.
I then tried to run gdm, but that does not even seem to start. I get a blackscreen and a blinking cursor.


pacman -Qss plasma-workspace returns

local/plasma-workspace 5.24.5-1 (plasma)
       KDE Plasma Workspace
local/plasma-workspace-wallpapers 5.24.5-1 (plasma)
       Additional wallpapers for the Plasma Workspace
seth wrote:

You're aware that this is an optimus system and you're running on the nvidia chip?

In my uefi/bios there are two different graphic options "PEG" and "IGD". I think this does have to do with what you asked? I was having it set on IGD, but now I turned it to PEG (with IGD enabled, since PEG seems to be able to run both). Sadly it didn't change anything, except the monitors it was using.

Online

#22 2022-05-15 15:26:08

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: Startx fails with mismatch in [file]

Sorry, signal error between my brain and my fingers:

pacman -Qkk plasma-workspace

Also, on a hunch: your shell rc (eg. ~/.bashrc or ~/.zshrc etc.)

Online

#23 2022-05-15 15:42:43

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

pacman -Qkk plasma-workspace

returns

plasma-workspace: 6901 total files, 0 altered files
seth wrote:

Also, on a hunch: your shell rc (eg. ~/.bashrc or ~/.zshrc etc.)

I actually don't see a .bashrc or .zshrc when I type

ls -la

in the home directory of root and the kavex user. All I see there is

total 29785
drwxr-xr-x 12 root root       18 May 15 17:07 .
drwxr-xr-x 18 root root       22 May 14 19:47 ..
-rw-------  1 root root        0 May 15 13:02 .Xauthority
-rw-------  1 root root    10744 May 15 17:07 .bash_history
drwxr-xr-x  3 root root        3 May 14 00:29 .cache
drwx------  2 root root        4 May 14 01:13 .config
-rw-------  1 root root       20 May 15 13:12 .lesshst
-rw-r--r--  1 root root      128 May 14 21:34 .pastebinit.xml
-rw-r--r--  1 root root      176 May 14 23:12 .wget-hsts
drwxr-xr-x  2 root root        2 May 14 01:13 Desktop
drwxr-xr-x  2 root root        2 May 14 01:13 Documents
drwxr-xr-x  2 root root        2 May 14 01:13 Downloads
drwxr-xr-x  2 root root        2 May 14 01:13 Music
drwxr-xr-x  2 root root        2 May 14 01:13 Pictures
drwxr-xr-x  2 root root        2 May 14 01:13 Public
drwxr-xr-x  2 root root        2 May 14 01:13 Templates
drwxr-xr-x  2 root root        2 May 14 01:13 Videos
-rw-r--r--  1 root root 29364221 May 12 00:43 nvidia-515.43.04-1-x86_64.pkg.tar.zst

Online

#24 2022-05-15 15:48:41

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 26,701
Website

Re: Startx fails with mismatch in [file]

kavex wrote:

... in the home directory of root and the kavex user.

"And"?  How do these share a home directory?  All that content has root:root ownership.  I don't know if this is behind your current symptoms, but it would definitely cause problems running X.  Can you confirm that you are somehow sharing a home directory for root and your user?  And if so, how and why?

Last edited by Trilby (2022-05-15 15:49:33)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#25 2022-05-15 16:00:07

kavex
Member
Registered: 2022-05-14
Posts: 32

Re: Startx fails with mismatch in [file]

Trilby wrote:

"And"?  How do these share a home directory?

I thought I might check the home directory for another user aswell, just to be sure I didn't miss anything. They don't have much to do with each other.

Trilby wrote:

Can you confirm that you are somehow sharing a home directory for root and your user?

They don't share a home directory. Root is in /root and kavex is in /home/kavex

Online

Board footer

Powered by FluxBB