I was going to ask how to change TTYs So if I understand you correctly, from the current TTY i’m in (I assume that would be F1) I click CTRL+ALT+F2 and I get to a new window with a prompt (will I be asked to login again?) then run the command. then back to the first TTY and there maybe more text (or do I have to enter the ‘startx’ command again to get a new output?)
the reply was: failed to start Lightdm.service: unit lightdm.service not found
repeating text some of it in red - seems to be looking at appimage launcher.service Failed core-dump
Yes - except that you don’t click - because you can’t, because you have no mouse there.
You use the keyboard.
startx should work
I just tried it myself in a Cinnamon VM
It didn’t for you - more tries won’t make it magically work.
What about that log file content?
that’s a bit vague - we need information
you can see it, but don’t know what it means
I might know what it means - but I can’t see it unless you tell me. 
Should be obvious …
The order of things is kind of important here.
first start that log
then change TTY and try to start the display manager or startx
it fails, as we know
go back to the other TTY and see what got added to what was there before
this I can’t believe - it was there a few minutes ago
probably a typo
use startx
as I said: I know that works - when all is well
which it is not for you at the moment
could you tell me how to get to the log file from the TTY session? I mean from a terminal prompt
it located on /var/log/Xorg.0.log Thanks
Alternatively I can leave TTY, back into the ‘live’ session and from there navigate to the log - that way I can copy/paste into this forum.
[HowTo] Use public command-line pastebin services without installing anything!
sorry - I can’t give you a personal crash course
The info is all there - here on the forum as well as in the Arch wiki and the basic stuff is everywhere.
1 Like
Complete type out of Systemctl start lightdm
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ==== (in red)
Authentication is required to start 'lightdm.service'
Authenticating as: (my credentials)
Password:
==== AUTHENTICATION COMPLETE ==== (in red)
Failed to start Lightdm.service: Unit Lightdm.service not found. (in red)
Print out for 'journalctl -f
(date) (Computername) system [1]: system-coredump0125-2834-0.service: Deactivated succefully.
' ' system[1138]: appimagelauncherd.service: Main process sxited, code-dumped, status=11/SEGV
" " system[1138]: appimagelauncher.service: failed with result 'core-dump'.
" " system[1138]: appimagelauncher.service: scheduled restart job, restart counter is at 126.
" " appimagelauncherd[2845]: Search for existing appimages
" " appimagelauncherd[2845]: Searching directory: /home/jp/appimageapps
" " appimagelauncherd[2845]: Found Appimage: /home/jp/Appimageapps/balenaEtcher-1.18.11-x64.AppImage
" " appimagelauncherd[2845]: Appimage Integrated already, skipping
" " appimagelauncherd[2845]: Searching directory: /home/jp/Downloads
" " appimagelauncherd[2845]: Watching directories: /home/jp/Appimageapps /home/jp/Downloads
" " Kernel: traps: appimagelauncher[2045] general protection fault ip: (number) sp: (number) error:0 in libstdc++ .so.6.0.33[number]
" " systemdcoredump[2847] (appimagelauncher) of user 1000 terminated abnormally with signal 11/SEGU, processing...
" " systemd[1]: started processing Core Dump (PID 2847/UID 0).
" " systemd-coredump[2848]: [.] Process 2845 (appimagelauncher) of user 1000 dumped core
Stack trace of thread 2845:
#1 (number) local_rb_tree_increment (libstdc++ .so.6 + 0cx7794)
#2 (number) n/a (appimagelauncherd + 0x16909)
#3 (number) n/a (appimagelauncherd + 0x11de7)
#4 (number) n/a (libQt5Core.so.5 + 0xZe35de)
#5 (number) etc.....
The number count goes to 19 but I can not type anymore it’s 1:45am I need my sleep - if needed I continue tomorrow
In light of this, it might be worth a try to reinstall lightdm, like he suggested:
However - and as I said:
startx
should work
(even) without lightdm - without any display manager at all
I know it works because I did myself what I recommended to you:
I disabled lightdm
systemctl disable lightdm
When the system boots, you’ll land at a TTY
no display manager is started then - no attempt is made
the display manager is out of the equation, so to speak
(I’m not a native english speaker - but I’m sure you get the meaning)
… which was the goal of the operation - to get you to a working system
(just without the interference of a defunct graphical interface)
appimagelauncher is an AUR package - it seems to interfere here
uninstall it
sudo pacman -Rns appimagelauncher
or, at least:
sudo pacman -R appimagelauncher
You can reinstall it later, when the more important things are sorted out.
Or:
at least just disable that appimagelauncher.service, so it won’t be started
and, once more:
sudo pacman -Syu
or
sudo pacman -Syu lightdm
to verify that your base system (excluding AUR packages)
is up to date
I have exactly one (1) appimage: Clipgrab
When I need it, I start it by calling it via the PATH where I put it.
I put it in /home/username/.local/bin - which is in my shell search path
So: I can simply type the name of it
… no appimagelauncher needed …
If you want it (appimagelauncher) for convenience:
reinstall it later
but for now:
remove it!
it is creating (additional) problems you can’t afford while you are trying to repair the fundamentals
while the part of needing sleep was true (good night!)
the rest was a total euphemism
We’ll see.
1 Like
Like you English is not my first language so maybe the words I type may not be the best for what I mean to say. What I meant by that sentence is that if you need to see the remaining 14 lines of code, I will post them tomorrow.
Anyway We’re on different time zones (it’s 17:30 here) I’m going out tonight, so I will not be burning the midnight oil.
What I have done since last night:
I uninstalled ‘appimagelauncher’
I run the install of ‘lightdm’
sudo pacman -Syu Lightdm
== Syncrhronizing package database...
core is up to date
extra
community is up to date
error: target not found: Lightdm
I tried to access the log file from the terminal, but was unsuccessful. I tried
cat /var/log/Xorg.0.log That showed the content on the screen, but when to the end so I could not see the top part
I tried: less /var/log/Xorg.0.log that did not give any result
I tried: sudo nano /var/log/Xorg.0.log that opened an empty doc with the name of the file on top and commands on bottom but empty in between.
I then log in the live session and got it from within.
[ 234.732]
X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
[ 234.733] Current Operating System: Linux jpmanjarohome 5.15.167-1-MANJARO #1 SMP PREEMPT Thu Sep 12 11:38:41 UTC 2024 x86_64
[ 234.733] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64 root=UUID=1bbcd301-42b9-497a-b018-36db090a3a5e rw apparmor=1 security=apparmor resume=UUID=2c14b0b1-444f-4331-a99d-cf58591be87e udev.log_priority=3 3
[ 234.734]
[ 234.734] Current version of pixman: 0.43.4
[ 234.734] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 234.735] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 234.736] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 22 22:47:29 2024
[ 234.740] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 234.740] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 234.742] (==) ServerLayout "Layout0"
[ 234.742] (**) |-->Screen "Screen0" (0)
[ 234.742] (**) | |-->Monitor "Monitor0"
[ 234.742] (**) | |-->Device "Device0"
[ 234.742] (**) |-->Input Device "Keyboard0"
[ 234.742] (**) |-->Input Device "Mouse0"
[ 234.742] (**) Option "IgnoreABI" "1"
[ 234.742] (**) Ignoring ABI Version
[ 234.742] (**) Allowing byte-swapped clients
[ 234.742] (==) Automatically adding devices
[ 234.742] (==) Automatically enabling devices
[ 234.742] (==) Automatically adding GPU devices
[ 234.742] (==) Automatically binding GPU devices
[ 234.742] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 234.742] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/misc".
[ 234.742] Entry deleted from font path.
[ 234.742] (Run 'mkfontdir' on "/usr/share/fonts/misc").
[ 234.743] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF".
[ 234.743] Entry deleted from font path.
[ 234.743] (Run 'mkfontdir' on "/usr/share/fonts/TTF").
[ 234.743] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[ 234.743] Entry deleted from font path.
[ 234.743] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[ 234.743] Entry deleted from font path.
[ 234.743] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[ 234.743] Entry deleted from font path.
[ 234.743] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[ 234.743] Entry deleted from font path.
[ 234.743] (==) FontPath set to:
[ 234.743] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 234.744] (**) Extension "COMPOSITE" is enabled
[ 234.744] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 234.744] (WW) Disabling Keyboard0
[ 234.744] (WW) Disabling Mouse0
[ 234.744] (II) Module ABI versions:
[ 234.744] X.Org ANSI C Emulation: 0.4
[ 234.744] X.Org Video Driver: 25.2
[ 234.744] X.Org XInput driver : 24.4
[ 234.744] X.Org Server Extension : 10.0
[ 234.744] (++) using VT number 1
[ 234.745] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[ 234.748] (--) PCI:*(1@0:0:0) 10de:1244:0000:0000 rev 161, Mem @ 0xf6000000/33554432, 0xe0000000/134217728, 0xec000000/67108864, I/O @ 0x0000ef00/128, BIOS @ 0x????????/131072
[ 234.748] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 234.748] (II) LoadModule: "glx"
[ 234.749] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 234.752] (II) Module glx: vendor="X.Org Foundation"
[ 234.752] compiled for 1.21.1.13, module version = 1.0.0
[ 234.752] ABI class: X.Org Server Extension, version 10.0
[ 234.752] (II) LoadModule: "nvidia"
[ 234.752] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 234.759] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 234.759] compiled for 4.0.2, module version = 1.0.0
[ 234.760] Module class: X.Org Video Driver
[ 234.761] (II) NVIDIA dlloader X Driver 390.157 Wed Oct 12 09:21:41 UTC 2022
[ 234.761] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 234.763] (II) Loading sub module "fb"
[ 234.763] (II) LoadModule: "fb"
[ 234.763] (II) Module "fb" already built-in
[ 234.763] (II) Loading sub module "wfb"
[ 234.763] (II) LoadModule: "wfb"
[ 234.763] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 234.765] (II) Module wfb: vendor="X.Org Foundation"
[ 234.765] compiled for 1.21.1.13, module version = 1.0.0
[ 234.765] ABI class: X.Org ANSI C Emulation, version 0.4
[ 234.765] (II) Loading sub module "ramdac"
[ 234.765] (II) LoadModule: "ramdac"
[ 234.765] (II) Module "ramdac" already built-in
[ 234.769] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[ 234.769] (EE) NVIDIA: system's kernel log for additional error messages and
[ 234.769] (EE) NVIDIA: consult the NVIDIA README for details.
[ 234.769] (EE) No devices detected.
[ 234.769] (EE)
Fatal server error:
[ 234.769] (EE) no screens found(EE)
[ 234.769] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 234.769] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 234.769] (EE)
[ 234.843] (EE) Server terminated with error (1). Closing log file.
That’s where I stopped - it’s dinner time
Like I thought, it is an issue with your NVIDIA card.
The fact that /var/log/Xorg.0.log is empty could mean that you where using wayland instead of xorg - but that is only speculation.
Manjaro uses a tool called mhwd to configure the graphics.
I never needed to use it.
You’d have to look up the HowTo’s here in the forum or the Manjaro wiki.
Or hope that someone else with experience will help you.
I can’t.
I never used the tool and I don’t have an NVIDIA card.
Good luck!
Nachlese thank for your help (I know it can be very frustrating with ‘nobs’ like me)
I will look tomorrow in the wiki for info or if someone else give me advice…, but to be honest the way that is going I’m inclined to try a ‘restore’ the only thing holding me back is the fact that it is app 7 months old! so it will need a lot of updates and that was what broke my system.
Anyway we see in a few days.
I’m not so sure about that “and that was what broke my system” - but anyway:
save/back up your /home/user
reinstall using a recent manjaro edition
restore the backed up /home/user
done …
You are overcomplicating things.
Linux is not magic - it’s more like Lego - putting pieces together
1 Like