Skip to main content ↑ ↓
Topic: During boot, it won't progress to xfce4 graphical desktop - stalls at terminal (Read 965 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

During boot, it won't progress to xfce4 graphical desktop - stalls at terminal

Suddenly Artix won't fully boot. It jumps out of the boot process  to a terminal login screen, before the xfce4 desktop begins loading.

That text based login allows access to the entire machine via a one-line login screen, in text fashion, like any text terminal does.

Have tried various tips and tricks as found on the  forum, yet no improvement achieved so far.

Thanks in advance for any fixes / explanations.

It's been trying to do this kind of incomplete booting for years, however, the restart cycle usually required to fix this issue doesn't cut it this time.

Re: During boot, it won't progress to xfce4 graphical desktop - stalls at terminal

Reply #1 –
Pls run startx and provide the output.

artist

Re: During boot, it won't progress to xfce4 graphical desktop - stalls at terminal

Reply #2 –
That produced what looks like important info. Before I relay the basics of the output ;

1) In that terminal. how to format the screen so it folds?
2) How to redirect that output to a file, that  nano can display it?  I used the ">" method and nano sees the output as a blank file.
3) For terminal data export, does a thumb drive work with this terminal ? Tried plugging one into a USB port and nothing seemed to change, no surprise there.

*
$startx
X.Org X server 1.21.1.18
Protocol version 11, rev 0
Current OS 6.16.4-Artix1-1 #1 SMP PRE-EMPT DYNAMIC
then "long lists of info"

current ver of pixman : 0.46.4

Log file : (I found it - a very long summary/ )

using Config dir : etc/x11/xorg.conf.d

using system config dir : "usr/share/X11/xorg.conf.d"

waiting for X server to shut down, this terminates successfully. Closing log file.term : not found /etc/X11/xinit/xinitrc

line 55 : xterm not found

*    *

Problem is it is not folding so a lot of info is out of sight. The first runs of startx produced output that listed a lot about systemd. That seems to have vanished on the latest startx runs.

Need to get the terminal to "print" verbosely with folding and then out to a readable  & exportable text file.

*     *

How to proceed from here ?

Thanks in advance - - -

*    *    *
 

Re: During boot, it won't progress to xfce4 graphical desktop - stalls at terminal

Reply #3 –
It seems your system is missing some packages/files.
Please install package xorg-xinit and try again.
If that does not help upload file ~/.local/share/xorg/Xorg.0.log

artist

Re: During boot, it won't progress to xfce4 graphical desktop - stalls at terminal

Reply #4 –
PS : Have figured out the thumb drive aspect to get the data off / out.

Once I have the file, will forward it. Is there a way to forward a file here somehow, or do I  need to block copy the file contents and post that inline here ? I also just noticed the forum commands "insert a quote" or "insert an image", above.

Also looking forward to my other ?'s answered and to any conclusions, so far. Thanks.

*     *

Re: During boot, it won't progress to xfce4 graphical desktop - stalls at terminal

Reply #6 –
Quote from: protoshop – on
How to redirect that output to a file, that  nano can display it?  I used the ">" method and nano sees the output as a blank file.
For error messages: "2>“

Re: During boot, it won't progress to xfce4 graphical desktop - stalls at terminal

Reply #7 –
It's definitely a missing display server type of issue, as anything graphical complains of a lack of display resource, when run.

Quote
Quote from: Artist – on
It seems your system is missing some packages/files.
Please install package xorg-xinit and try again.
If that does not help upload file ~/.local/share/xorg/Xorg.0.log

I tried reinstalling xorg-xinit, from cache. It reinstalled fine, yet same result. Of course, I may be reinstalling the same perhaps-buggy item, which would explain the same result.  Is anyone else reporting issues with xorg-xinit ? Where would it's latest version be in repo so as to be downloadable/installable and then how to install it. I guess that's done via thumb drives and a pacman terminal, somehow? Have no internet / firefox, so cannot get it from the web, such as from AUR. as would be usual.

Thanks for the how-to-paste reference. Should have that by mid-week.

*     *

Quote from: Caramon2 – on
Quote from: protoshop – on
How to redirect that output to a file, that  nano can display it?  I used the ">" method and nano sees the output as a blank file.
For error messages: "2>“
Will use that feature.

Re: During boot, it won't progress to xfce4 graphical desktop - stalls at terminal

Reply #8 –
PS  :

Are there any other suggested files that I could reinstall from cache that might  benefit this situation.

Or to install/run any further troubleshooting routines, generally ?

Re: During boot, it won't progress to xfce4 graphical desktop - stalls at terminal

Reply #9 –
You can't run startx without setting it up first:
First in your homedir, ~/.bashrc needs something like this adding to what is already in there:
Code: [Select]
# start x on login
if (( [[ -z $DISPLAY && ! -e /tmp/.X11-unix/X0 ]] ) && (rc-status -r | grep -q 'default')); then
exec startx -- -verbose 6 -logverbose 6 >/home/$USER/.startx.log 2>&1
fi
or if you aren't using OpenRC, and that last bit isn't really essential anyway, it just makes sure the desktop only starts when you want it to:
Code: [Select]
# start x on login
if ( [[ -z $DISPLAY && ! -e /tmp/.X11-unix/X0 ]] ); then
exec startx -- -verbose 6 -logverbose 6 >/home/$USER/.startx.log 2>&1
fi

and again in your homedir, you need ~/.xinitrc to exist, and for XFCE it contains:
Code: [Select]
exec startxfce4

That will create a log file in ~/.startx.log and log that output for you as well. There may also be logs in /var/log. This sounds like a DM problem following an update. You can also downgrade the relevant packages after checking /var/log/pacman.log then upgrade them in sections to find the culprit(s) as another approach, but trying startx first is also a possible solution.