After installing the Artix xface4 openrc and subsequent post installation , I have rebooted Artix. However, it goes to straight forward to terminal instead of desktop environment. How to get desktop environment.
pacman -S displaymanager-openrc. Install a login manager example: sddm. Set which login manager in /etc/conf.d/xdm
rc-update add xdm default
rc-service xdm start
xdm already installed in run level default, skipping and xdm has already started. What to do
"Install a login manager example: sddm."
https://wiki.artixlinux.org/Main/Installation#Desktop_Environment (https://wiki.artixlinux.org/Main/Installation#Desktop_Environment)
I think in this case xdm is a service script, although there is an actual dm called xdm, but that's probably the xorg-xdm package. There doesn't seem to be any openrc-xdm package at all in the repos, but it is in the AUR, perhaps it's under a different name. I'm using startx and have no xdm service at all, so it's not part of openrc.
How to install login manager. I feel i have already installed and followed above link.
Because openrc “xdm” script is displaymanager-openrc and allows choosing which login manager you want including xdm
I have installed sddm and edit to nano /etc/xdm added sddm in the file. However, still going straight to terminal after rebooting. What to do. ?. Is it not suitable layman>
without providing any logs we only could use a crystal ball to help you…
lspci
dmesg
cat /var/log/Xorg.0.log
Actually I got perplexed when I seen your request for log file because i dont know how to save the log file in my situation. Because no desktop with browser. After googling I got some idea and saved the command line and attaching the saved log text file through another distributions.
The file is "/etc/conf.d/xdm" and the is variable "DISPLAYMANAGER" which you need to set to xdm
The whole file might look like this:
# We always try and start X on a static VT. The various DMs normally default
# to using VT7. If you wish to use the xdm init script, then you should ensure
# that the VT checked is the same VT your DM wants to use. We do this check to
# ensure that you haven't accidentally configured something to run on the VT
# in your /etc/inittab file so that you don't get a dead keyboard.
CHECKVT=7
# What display manager do you use ? [ xdm | gdm | kdm | gpe | entrance ]
# NOTE: If this is set in /etc/rc.conf, that setting will override this one.
DISPLAYMANAGER="sddm"
This file will be present only if you have package "displaymanager-openrc" installed.
To start it when you start your machine add it into default runleve.
rc-update add xdm default
after that either reboot or you can start service manually like this:
rc-service xdm start
PS: If i missed your point I hope this will at worst feed search engines with answers.
I have changed xdm ("/etc/conf.d/xdm" and the is variable "DISPLAYMANAGER" which you need to set to xdm).
while running rc-update add xdm default , it says that already installed. Then rebooted still goes to terminal and login prompt. (same as before)
I have also applied rc-service xdm start, it says xdm already started.
than try restart with verbose option.
rc-service --verbose xdm restart
This should print some messages / logs, I hope you can post the output here.
I'd just like to say that I'm having the same problem. I'm in VirtualBox using lightdm.
[ 12.853576] b43 ssb0:0: Direct firmware load for b43/ucode15.fw failed with error -2
[ 12.853636] b43 ssb0:0: Direct firmware load for b43-open/ucode15.fw failed with error -2
A dmesg error suggests you can install the b43-firmware package from the AUR for wireless to work. This won't affect the desktop starting though.
It works here - I installed displaymanager-openrc and sddm. Then edited /etc/conf.d/xdm:
#DISPLAYMANAGER="xdm"
DISPLAYMANAGER="sddm"
Enabled service:
$ sudo rc-update add xdm default
I commented out my pre-existing startx content in .xinitrc and .bashrc, it worked and the sddm login page appeared, and I could get to the desktop.
I could get to a terminal prompt at boot by removing the xdm service again:
$ sudo rc-update delete xdm default
Then after logging in at the terminal prompt I tried
$ sudo /etc/init.d/xdm start
which worked, and then after rebooting:
$ sudo sddm
which also worked - not sure if that would start a root x but it also got the login page and desktop.
If you have this issue, then try to restart xdm as previously suggested by SGOrava to hopefully get some messages in the terminal login, you could also try starting the dm itself like I did above. Another thing could be to check you are on the right tty for X - (CTRL) ALT F(1-7) should switch through tty's, CTRL is only needed when X has started. I think I've seen cases when X starts on tty7 yet you stay on tty1, usually when I got my personal config wrong.
Upon running the command rc-service --verbose xdm restart , the output as follows:-
xdm.Executing: /usr/lib/openrc/sh/openrc-run-sh /usr/lib/ openrc-run.sh /etc/initd/xdm.stop
stopping xdm....
Will stop usr/bin/xdm
start-stop-demeon : no matching process found
xdm.xdm.Executing: /usr/lib/openrc/sh/openrc-run-sh /usr/lib/ openrc-run.sh /etc/initd/xdm.start
your XDM value is invalid
No. xdm executable could be found on system
Error : Please set lyour DISPLAYMANAGER variable in etc/conf.d/xdm
or instal x11-apps/xdm package
gettign up xdm
shart-stop deamon: /usr/bin/xdm
could not start the display manager
I feel displaymanager earlier was sddm and later changed to sddm as per the advice given in previous post.
can you run:
pacman -S sddm
and put this into
/etc/conf.d/xdm# We always try and start X on a static VT. The various DMs normally default
# to using VT7. If you wish to use the xdm init script, then you should ensure
# that the VT checked is the same VT your DM wants to use. We do this check to
# ensure that you haven't accidentally configured something to run on the VT
# in your /etc/inittab file so that you don't get a dead keyboard.
CHECKVT=7
# What display manager do you use ? [ xdm | gdm | kdm | gpe | entrance ]
# NOTE: If this is set in /etc/rc.conf, that setting will override this one.
DISPLAYMANAGER="sddm"
you either dont have program which you set as DISPLAYMANAGER installed or you made an error/typo while writing it.
it reinstalled and changed display manager to sddm. however no use at all
is there any other error message?
Because the log you provided said that it cant find executable specified in DISPLAYMANAGER variable in /etc/conf.d/xdm
can you provide file /etc/conf.d/xdm ?
Sounds a lot like you have not installed the actual sddm package.
Now got below output while running rc-service --verbose xdm restart
xdm.Executing: /usr/lib/openrc/sh/openrc-run-sh /usr/lib/ openrc-run.sh /etc/initd/xdm.stop
stopping xdm....
Will stop usr/bin/xdm
start-stop-demeon : no matching process found
xdm.xdm.Executing: /usr/lib/openrc/sh/openrc-run-sh /usr/lib/ openrc-run.sh /etc/initd/xdm.start
Seting up sddm
Detaching to start usr/bin/sddm
# We always try and start X on a static VT. The various DMs normally default
# to using VT7. If you wish to use the xdm init script, then you should ensure
# that the VT checked is the same VT your DM wants to use. We do this check to
# ensure that you haven't accidentally configured something to run on the VT
# in your /etc/inittab file so that you don't get a dead keyboard.
CHECKVT=7
# What display manager do you use ? [ xdm | gdm | sddm | gpe | entrance | lightdm | lxdm ]
# NOTE: If this is set in /etc/rc.conf, that setting will override this one.
DISPLAYMANAGER="sddm"
so it is trying to start sddm but fails for some reason?
Can you check sddm logs ? they are probably somewhere in /var/log/sddm something.
Jul 31 11:10:51 ramesh connman-vpnd[2250]: D-Bus disconnect
Jul 31 13:40:41 ramesh pulseaudio[2790]: [pulseaudio] core-util.c: Failed to create secure directory (/run/user/1000/pulse): No such file or directory
Jul 31 13:40:42 ramesh /etc/init.d/xdm[4858]: start-stop-daemon: no matching processes found
Jul 31 13:40:43 ramesh connman-vpnd[2289]: D-Bus disconnect
Jul 31 13:43:05 ramesh kernel: usb 1-1: device not accepting address 4, error -71
Jul 31 14:23:21 ramesh login[2683]: pam_tally2(login:auth): pam_get_uid; no such user
Jul 31 14:38:58 ramesh login[2736]: pam_tally2(login:auth): pam_get_uid; no such user
Jul 31 15:17:41 ramesh login[2798]: pam_tally2(login:auth): pam_get_uid; no such user
Jul 31 15:17:53 ramesh /etc/init.d/xdm[3351]: start-stop-daemon: no matching processes found
Jul 31 15:17:54 ramesh connman-vpnd[2289]: D-Bus disconnect
Jul 31 17:05:50 ramesh kernel: usb 1-1: device descriptor read/64, error -71
Jul 31 17:05:52 ramesh /etc/init.d/xdm[3150]: start-stop-daemon: no matching processes found
Jul 31 17:05:53 ramesh connman-vpnd[2299]: D-Bus disconnect
Jul 31 18:16:37 ramesh /etc/init.d/xdm[2716]: xdm: superuser access required
Jul 31 18:54:38 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 18:54:38 ramesh connmand[2233]: Deleting host route failed (No such device)
Jul 31 18:54:38 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 18:55:06 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 18:55:06 ramesh connmand[2233]: Deleting host route failed (No such device)
Jul 31 18:55:06 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 18:55:07 ramesh kernel: usb 1-1: device not accepting address 6, error -71
Jul 31 18:57:58 ramesh login[2776]: pam_tally2(login:auth): pam_get_uid; no such user
Jul 31 18:57:59 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 18:57:59 ramesh connmand[2233]: Deleting host route failed (No such device)
Jul 31 18:57:59 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 18:58:23 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 18:58:23 ramesh connmand[2233]: Deleting host route failed (No such device)
Jul 31 18:58:23 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 18:58:28 ramesh login[2776]: pam_tally2(login:auth): pam_get_uid; user?
Jul 31 18:59:33 ramesh login[2800]: pam_tally2(login:auth): pam_get_uid; no such user
Jul 31 19:00:06 ramesh login[2800]: pam_tally2(login:auth): pam_get_uid; user?
Jul 31 19:00:15 ramesh agetty[2804]: tty1: invalid character 0x3 in login name
Jul 31 19:00:28 ramesh login[2805]: pam_tally2(login:auth): pam_get_uid; no such user
Jul 31 19:00:43 ramesh login[2805]: pam_tally2(login:auth): pam_get_uid; user?
Jul 31 19:01:12 ramesh login[2809]: pam_tally2(login:auth): pam_get_uid; no such user
Jul 31 19:01:16 ramesh login[2809]: pam_tally2(login:auth): pam_get_uid; user?
Jul 31 19:04:03 ramesh agetty[2819]: tty1: invalid character 0x1b in login name
Jul 31 19:05:10 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 19:05:10 ramesh connmand[2233]: Deleting host route failed (No such device)
Jul 31 19:05:10 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 19:22:56 ramesh /etc/init.d/xdm[2970]: xdm: superuser access required
Jul 31 19:24:11 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 19:24:11 ramesh connmand[2233]: Deleting host route failed (No such device)
Jul 31 19:24:11 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 19:25:57 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 19:25:57 ramesh connmand[2233]: Deleting host route failed (No such device)
Jul 31 19:25:57 ramesh connmand[2233]: Removing default gateway route failed (No such device)
Jul 31 19:26:02 ramesh /etc/init.d/xdm[3631]: start-stop-daemon: no matching processes found
Jul 31 19:26:03 ramesh connman-vpnd[2299]: D-Bus disconnect
Aug 1 13:24:54 ramesh connman-vpnd[2366]: Can't load /usr/lib/connman/plugins-vpn/wireguard.so: /usr/lib/connman/plugins-vpn/wireguard.so: undefined symbol: __vpn_ipconfig_foreach
Aug 1 13:36:17 ramesh /etc/init.d/xdm[3600]: start-stop-daemon: no matching processes found
Aug 1 13:36:17 ramesh connman-vpnd[2366]: D-Bus disconnect
Aug 1 13:37:02 ramesh connman-vpnd[2419]: Can't load /usr/lib/connman/plugins-vpn/wireguard.so: /usr/lib/connman/plugins-vpn/wireguard.so: undefined symbol: __vpn_ipconfig_foreach
Aug 1 13:41:19 ramesh /etc/init.d/xdm[3472]: start-stop-daemon: no matching processes found
Aug 1 13:42:54 ramesh /etc/init.d/xdm[3162]: start-stop-daemon: no matching processes found
Aug 1 13:42:55 ramesh connman-vpnd[2328]: D-Bus disconnect
Aug 1 13:42:55 ramesh login[2691]: pam_elogind(login:session): Failed to release session: Connection reset by peer
Aug 1 18:57:11 ramesh connman-vpnd[2375]: Can't load /usr/lib/connman/plugins-vpn/wireguard.so: /usr/lib/connman/plugins-vpn/wireguard.so: undefined symbol: __vpn_ipconfig_foreach
Aug 1 18:57:28 ramesh login[2667]: pam_tally2(login:auth): pam_get_uid; no such user
Aug 1 19:07:21 ramesh /etc/init.d/xdm[3173]: start-stop-daemon: no matching processes found
Aug 1 19:07:22 ramesh connman-vpnd[2375]: D-Bus disconnect
Aug 1 20:48:15 ramesh /etc/init.d/xdm[2731]: xdm: superuser access required
Aug 1 20:54:36 ramesh /etc/init.d/xdm[3147]: start-stop-daemon: no matching processes found
Aug 1 20:54:37 ramesh connman-vpnd[2325]: D-Bus disconnect
Aug 1 20:54:37 ramesh login[2682]: pam_elogind(login:session): Failed to release session: Connection reset by peer
Aug 1 20:55:58 ramesh /etc/init.d/xdm[3232]: start-stop-daemon: no matching processes found
Aug 1 20:55:58 ramesh connman-vpnd[2337]: D-Bus disconnect
Aug 1 22:44:40 ramesh /etc/init.d/xdm[3278]: start-stop-daemon: no matching processes found
Aug 1 22:44:41 ramesh connman-vpnd[2329]: D-Bus disconnect
Aug 2 09:24:49 ramesh agetty[2669]: tty1: invalid character 0x3 in login name
Aug 2 09:24:57 ramesh /etc/init.d/xdm[3103]: start-stop-daemon: no matching processes found
Aug 2 09:24:57 ramesh connman-vpnd[2336]: D-Bus disconnect
Aug 2 09:25:37 ramesh /etc/init.d/xdm[2375]: start-stop-daemon: /usr/bin/xdm does not exist
Aug 2 09:25:37 ramesh /etc/init.d/xdm[2376]: ERROR: could not start the Display Manager
Aug 2 09:25:38 ramesh connman-vpnd[2408]: Can't load /usr/lib/connman/plugins-vpn/wireguard.so: /usr/lib/connman/plugins-vpn/wireguard.so: undefined symbol: __vpn_ipconfig_foreach
Aug 2 09:29:17 ramesh /etc/init.d/xdm[3185]: start-stop-daemon: no matching processes found
Aug 2 09:29:18 ramesh connman-vpnd[2408]: D-Bus disconnect
Aug 2 09:30:08 ramesh /etc/init.d/xdm[3115]: start-stop-daemon: no matching processes found
Aug 2 09:30:09 ramesh connman-vpnd[2327]: D-Bus disconnect
Aug 2 09:35:22 ramesh /etc/init.d/xdm[2785]: xdm: superuser access required
Aug 2 09:35:34 ramesh /etc/init.d/xdm[2812]: start-stop-daemon: no matching processes found
Aug 2 09:35:34 ramesh /etc/init.d/xdm[2858]: start-stop-daemon: /usr/bin/xdm does not exist
Aug 2 09:35:34 ramesh /etc/init.d/xdm[2859]: ERROR: could not start the Display Manager
Aug 2 09:36:05 ramesh /etc/init.d/xdm[2898]: start-stop-daemon: no matching processes found
Aug 2 09:36:06 ramesh /etc/init.d/xdm[2942]: start-stop-daemon: /usr/bin/xdm does not exist
Aug 2 09:36:06 ramesh /etc/init.d/xdm[2943]: ERROR: could not start the Display Manager
Aug 2 09:36:06 ramesh /etc/init.d/xdm[2965]: xdm: unknown function `-'
Aug 2 09:36:26 ramesh /etc/init.d/xdm[2994]: start-stop-daemon: no matching processes found
Aug 2 09:36:26 ramesh /etc/init.d/xdm[3038]: start-stop-daemon: /usr/bin/xdm does not exist
Aug 2 09:36:26 ramesh /etc/init.d/xdm[3039]: ERROR: could not start the Display Manager
Aug 2 09:36:26 ramesh /etc/init.d/xdm[3061]: xdm: unknown function `-'
Aug 2 09:36:47 ramesh /etc/init.d/xdm[3089]: start-stop-daemon: no matching processes found
Aug 2 09:36:47 ramesh /etc/init.d/xdm[3133]: start-stop-daemon: /usr/bin/xdm does not exist
Aug 2 09:36:47 ramesh /etc/init.d/xdm[3134]: ERROR: could not start the Display Manager
Aug 2 09:36:57 ramesh /etc/init.d/xdm[3145]: xdm: superuser access required
Aug 2 09:37:41 ramesh /etc/init.d/xdm[3181]: start-stop-daemon: no matching processes found
Aug 2 09:37:41 ramesh /etc/init.d/xdm[3225]: start-stop-daemon: /usr/bin/xdm does not exist
Aug 2 09:37:41 ramesh /etc/init.d/xdm[3226]: ERROR: could not start the Display Manager
Aug 2 09:37:41 ramesh /etc/init.d/xdm[3248]: xdm: unknown function `-'
Aug 2 09:45:38 ramesh /etc/init.d/xdm[3835]: start-stop-daemon: no matching processes found
Aug 2 10:22:22 ramesh connman-vpnd[2465]: Can't load /usr/lib/connman/plugins-vpn/wireguard.so: /usr/lib/connman/plugins-vpn/wireguard.so: undefined symbol: __vpn_ipconfig_foreach
Aug 2 10:23:15 ramesh agetty[2618]: tty1: invalid character 0x1b in login name
Aug 2 10:24:40 ramesh connmand[2237]: Failed to find URL:http://ipv6.connman.net/online/status.html
Aug 2 10:26:16 ramesh agetty[2688]: tty4: invalid character 0x1b in login name
Aug 2 10:31:33 ramesh /etc/init.d/xdm[3379]: start-stop-daemon: no matching processes found
Aug 2 13:06:59 ramesh connmand[2243]: Failed to find URL:http://ipv6.connman.net/online/status.html
Aug 2 13:08:14 ramesh /etc/init.d/xdm[3212]: start-stop-daemon: no matching processes found
Aug 2 13:08:15 ramesh connman-vpnd[2331]: D-Bus disconnect
Aug 2 13:08:56 ramesh connman-vpnd[2453]: Can't load /usr/lib/connman/plugins-vpn/wireguard.so: /usr/lib/connman/plugins-vpn/wireguard.so: undefined symbol: __vpn_ipconfig_foreach
Aug 2 14:44:49 ramesh /etc/init.d/xdm[2775]: start-stop-daemon: no matching processes found
Aug 2 14:47:48 ramesh /etc/init.d/xdm[2857]: start-stop-daemon: no matching processes found
Aug 2 14:53:32 ramesh /etc/init.d/xdm[3316]: start-stop-daemon: no matching processes found
Aug 2 14:53:33 ramesh connman-vpnd[2453]: D-Bus disconnect
Aug 2 14:53:33 ramesh login[2679]: pam_elogind(login:session): Failed to release session: Connection reset by peer
error file from /var/log. Not sddm error just error file.
Please use the code tags for log output.
I already asked, do you have the sddm package installed?
Jul 31 14:23:21 ramesh login[2683]: pam_tally2(login:auth): pam_get_uid; no such user
Jul 31 19:00:15 ramesh agetty[2804]: tty1: invalid character 0x3 in login name
Jul 31 19:04:03 ramesh agetty[2819]: tty1: invalid character 0x1b in login name
Could be the user name - a lot of non latin fonts use wide characters made up of 2 bytes, which would not make sense intepreted as ASCII single byte characters, unless Ramachandran has intentionally created a username with escape and control characters for security reasons ;D
Try another username with ASCII characters. Or possibly it is something else to do with the user, like groups / permissions, or the login name doesn't exist.
Installed sddm.
Regarding Post No.25: I have not intentionally created any username either in forum or in my artixlinux installation.
You probably need to check this has been completed successfully then, and a user created:
https://wiki.artixlinux.org/Main/Installation#Add_user.28s.29 (https://wiki.artixlinux.org/Main/Installation#Add_user.28s.29)
And if that isn't it, sddm has an autologin feature which needs to match an existing username if you were using it:
https://wiki.archlinux.org/index.php/SDDM#Autologin (https://wiki.archlinux.org/index.php/SDDM#Autologin)
From the log entries, you already have the hostname set as ramesh, that's the name of your computer, you need a user account to log into.
Also check user permissions are correct in /etc/group
https://wiki.artixlinux.org/Main/Configuration (https://wiki.artixlinux.org/Main/Configuration)