The installation of the
gnome package proceeds without any errors, but the environment crashes after logging in with the message:
Oh no! Something has gone wrong
The archwiki (https://wiki.archlinux.org/title/GNOME/Troubleshooting#gnome-shell_/_gnome-session_crashes_on_session_startup) recommendation of deleting files in the
~/.config/gnome-session/saved-session directory or turning off the auto-save session feature
doesn't work for me.
lol,
now only systemd is missing in the repos and the artix project is exactly where it was 7 years ago.
If you can help me, help me. If not, refrain from empty flooding.
“Does not work / Something has gone wrong” is definitely not a useful error description.
I can only advise against Gnome and KDE, is that enough help for you?
- Doctor, when I do this, it hurts here.
- Don’t do that.
What should I use? Although Linux has a large choice between environments, it is essentially a choice between different types of garbage.
Maybe it’s better to spend 10,000 years setting up some wm that has even more bugs?
Or maybe install windows right away, which I can’t stand? What?
AGAIN: YOU CAN HELP, HELP! YOU CAN'T, DON'T FLOOD!
KDE works fine on Artix.
Gnome tends to be very tightly wound around systemd so from what I remember can be a challenge to get working on systemd free systems. Not that I'd bother trying myself as I find it repulsive.
But if you like and want gnome, as you are perfectly entitled to, then some more of the surrounding output around
could be useful as could other details and logs.
For instance X or wayland ? What display manager if any?
The two facts that you installed Gnome and got the error message provided ,without context, is not a lot to go on.
LOL - I took that both ways as in finding both systemd and gnome being repulsive - and I tend to agree in both cases.
I did not know that Artix has gnome, there is no ISO.
Is it actually supported?
If you wanted to use gnome you could try cinnamon which was originally based on GNOME 3, but follows traditional desktop metaphor conventions.
I never tried it on Artix but I'd recommend it.
I use a standalone WM that needs some configuration.
Of course Gnome is supported. iso or not doesn't matter. You can simply look at the package repos and find mutter, gnome-shell, etc. Anyways as for OP, I tried gnome wayland and gnome x11 just now and both worked fine for me. You'll need to provide some actual meaningful log information if you want further help.
Dudemanguy, Do you need information from a specific log? Which one?
ls /var/log/
audit dinit lxdm.log pacman.log wtmp
auth.log errors.log lxdm.log.old README Xorg.0.log
btmp everything.log messages.log syslog.log Xorg.0.log.old
daemon.log kernel.log old user.log
I was going to post something then realized is was systemd related. Jeez.
I suppose starting with dmesg might be a place to start looking
Both X and Wayland behave the same. Yes, I used lxdm.
The dmesg only has information about disabling the nvidia discrete graphics card I was configuring. Nothing else.
You could check everything.log (system log) and Xorg.0.log (for X).
everything.log (https://pastebin.com/7AZrCPZS)
Xorg.0.log (https://pastebin.com/ZDAB7ReG)
I don’t understand... Judging by the log, he complains about systemd, but the priority of the artix repositories is higher than that of arch in pacman.conf.
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives
#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
#HookDir = /etc/pacman.d/hooks/
HoldPkg = pacman glibc
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
IgnorePkg = intellij-idea-community-edition
#gstreamer
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
#Color
#NoProgressBar
CheckSpace
#VerbosePkgLists
ParallelDownloads = 5
# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required
# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Artix Linux
# packagers with `pacman-key --populate artix`.
#
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#
# The gremlins repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
# Artix
#[gremlins]
#Include = /etc/pacman.d/mirrorlist
[system]
Include = /etc/pacman.d/mirrorlist
[world]
Include = /etc/pacman.d/mirrorlist
#[galaxy-gremlins]
#Include = /etc/pacman.d/mirrorlist
[galaxy]
Include = /etc/pacman.d/mirrorlist
# If you want to run 32 bit applications on your x86_64 system,
# enable the lib32 repositories as required here.
#[lib32-gremlins]
#Include = /etc/pacman.d/mirrorlist
[lib32]
Include = /etc/pacman.d/mirrorlist
# Arch
[extra]
Include = /etc/pacman.d/mirrorlist-arch
#[community]
#Include = /etc/pacman.d/mirrorlist-arch
[multilib]
Include = /etc/pacman.d/mirrorlist-arch
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
[universe]
Server = https://universe.artixlinux.org/$arch
Server = https://mirror1.artixlinux.org/universe/$arch
Server = https://mirror.pascalpuffke.de/artix-universe/$arch
Server = https://artixlinux.qontinuum.space/artixlinux/universe/os/$arch
Server = https://mirror1.cl.netactuate.com/artix/universe/$arch
Server = https://ftp.crifo.org/artix-universe/$arch
Server = https://artix.sakamoto.pl/universe/$arch
Also, there are posts about elogind, but I need seatd to run sway.
And do other desktop environments / window managers start OK ?
If yes then try disabling lxdm and starting Gnome manually (https://wiki.archlinux.org/title/GNOME#Manually)
I'm not guaranteeing this syntax but
export XDG_SESSION_TYPE=x11
export GDK_BACKEND=x11
startx /usr/bin/gnome-session -- -keeptty >~/xorg.log 2>&1"
should try to start Gnome with Xorg and log all messages to ~/xorg.log
You will probably need to install xorg-xinit to get the startx command.
gripped, yes, lxdm started mate and xfce without any problems. I tried to start gnome manually using xinitrc, but the startx command was misspelled...
I took the code block for xinitrc which is listed in the documentation:
export XDG_SESSION_TYPE=x11
export GDK_BACKEND=x11
exec gnome-session
Next startx and... Success. He just took it and loaded up. Well, I can believe that lxdm is to blame. I'll recheck all this later and find myself another dm or even configure everything to run without a dm. Many thanks to everyone who responded!
Unless the system in question has multiple user accounts I consider Display Managers a waste of time and resources.
If a single user system you can:
- Setup autologin on tty1
- Get X to start automatically on tty1
- put a .desktop file in ~/.config/autostart which locks the screen (works on KDE)
With that in place the system boots straight into the desktop and you still need a password to access it.
I don't think they consume enough resources to worry about it.
It doesn't worry me. I just consider them useless for my particular use case.
And on top of that they can sometimes introduce issues which don't exist without them.
Keep it simple imho.