Forum › Forums › Official Releases › antiX-19 “Marielle Franco, Hannie Schaft, Manolis Glezos, Grup Yorum, Wobblies” › Desktop can’t start – stalls at prompt [solved]
- This topic has 22 replies, 6 voices, and was last updated Apr 12-8:26 am by caprea.
-
AuthorPosts
-
December 15, 2021 at 11:39 am #72980Member
scruffyeagle
I had a major crash of Antix v19.3 (upgraded). It’s being run on a Dell Precision M6300 laptop, 4GB RAM, 10 GB swap, 27 GB ext4 partition.
I’d been online, reading a long document. When I was done, I tried to update my diary – and, it couldn’t save. The error message box said it couldn’t write to the file. I eventually shut down LibreOffice w/o saving it. I tried opening files on other partitions, but couldn’t close them. The error message said no space on the disk. I tried to reboot, but it couldn’t shut down properly. I shut it down via press-and-hold of the power button. Trying to reboot into Antix 19.3 (up’d), it stalled out at a terminal prompt, unable to start up the X windowing w/ desktop.
There were 2 error lines visible on the screen, which were both the same:
rsyslogd: file ‘4’ write error: No space left on device [v8.1904.0 try https://www.rsyslog.com/e/2027 ]
I tried using “startx”, and it didn’t work. Here’s the output it printed to the screen:
———————————–
Xauth: Unable to write authority file /home/spirit/.Xauthority-n
(EE)
fatal server error
(EE) Cannot open log file /home/spirit/.local/share/xorg.0.log
(EE)
(EE)
Please consult the Xorg Foundation support at http://wiki.x.org for help
(EE)
Xinit: giving up
Xinit: Unable to connect to X server
: connection refused
Xinit: server error
——————————–I painstakingly copied by hand, the vital info from the screen onto paper. Luckily, I had a second laptop set up with Antix v19.4 – and that’s what I’m using for posting here. Note, that I was under the impression that I still had around 9 GB unused in the partition.
- This topic was modified 1 year, 4 months ago by scruffyeagle.
December 15, 2021 at 3:14 pm #72994Forum Admin
rokytnji
::Can you boot a live dvd or usb of full iso and post back the results
sudo parted -lI have had dying hard drives also that exhibit these same symptoms.
Maybe
inxi -Fxzwon’t hurt to be posted in this thread also. Good luck.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsDecember 15, 2021 at 3:37 pm #72997MemberModdIt
::If you can read the drive contents, get data backed up fast. Unless you have all you need already safe.
then please follow the advice from roky.December 15, 2021 at 4:23 pm #73006Member
sybok
::Hi,
if I understand you sentence
it stalled out at a terminal prompt, unable to start up the X windowing w/ desktop.
correctly, you could try to access your account without X.
I assume the PC boots, X is not started.
Usually, there are several console modes accessible via Ctrl+Alt+F<2-6>.
If you manage to login without X, then you may look around and attempt to clear some files found in /tmp/ or ~/.cache/
Proceed with care during the clearing.Hope that helps.
@painstaikingly:
If you have a smart-phone, you can take a picture and try some OCR program to detect the text and convert it into a string.December 26, 2021 at 6:57 am #73689Memberscruffyeagle
::I tested & found that inxi -Fxz works. But, I don’t see any way of piping or saving the output into a file. And when I tried plugging in a flashdrive, the computer froze up. I had to use the power button to break out of the lockup.
However, I read in a thread elsewhere, of someone who took a picture of their screen to save the output. So, I did that, using my phone’s camera. I was then able to transfer the pic into the computer using Linux Mint in another partition. It’s not a very good pic, but I think if you zoom in, you should be able to read the contents of the screen.
I did look into the /.cache/ folder, but I had no way of knowing what was eligible for disposing of and what wasn’t – so, I just left it as is.
- This reply was modified 1 year, 4 months ago by scruffyeagle. Reason: adding extra detail
Attachments:
December 26, 2021 at 8:32 am #73693MemberModdIt
::Delete data in /cache delete /home/yourusername/.cache it will be recreated automagicaly
Delete /home/yourusename/.config/libreoffice/4/crash it might be named slightly different regarding the 4
When you get back in to your system start libreoffice for first time with –norestore option my start option looks like this libreoffice7.2 –norestore –writer
you may not need the version number that depends on install method.A corrupted or full cache can completely block graphical login, sometimes complete system. Libreoffice crash recovery will try and auto restart with the big
document so you should prevent that. You may have to delete the complete LO config in home, no worry it will be recreated next time you start LO.4GB RAM, 10 GB swap, 27 GB ext4 partition. Do you mean 10GB /home or really such a huge swap area.
Generaly about same swap size as ram is the recommendation.- This reply was modified 1 year, 4 months ago by ModdIt.
- This reply was modified 1 year, 4 months ago by ModdIt.
December 26, 2021 at 2:52 pm #73714Forum Admin
Dave
::Another couple of things to do to gain some space is to remove the logs from /var/log/* as well as run apt clean && apt autoclean.
Sometimes the apt cache folder can hold large amounts of debs from updates and add up to several GBs.Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
December 28, 2021 at 8:59 am #73939Memberscruffyeagle
::Thanks for the advice. I’ll return to it, and not be timid about wiping .cache items out.
Yes, I really did use that large a swap partition. I’ve read in the past, that one should have double the swap space vs. RAM. That would be 8GB. All my data is stored on encrypted external HD’s, NOT the internal drive. The machine this is happening on has (came with) a 250GB internal drive, of which about 60GB hosts Antix & Linux Mint (~30GB each) – so, I have a huge amount of drive space to spare. I could easily afford doubling the RAM, and adding on a couple GB more to make it 10GB. And, 10 is such a nice, round number…
December 28, 2021 at 9:03 am #73940Memberscruffyeagle
::Thanks for the advice. I’ve written it down, for the next time I get back to working with it.
I know the easiest way to deal with this, would be to simply over-write the installation with a new operating system. But, I’m not at a point where I don’t have anything to work with yet – and, I think it would provide an immense feeling of achievement, if I can actually get the current installation functional again.
December 28, 2021 at 9:16 am #73942Memberscruffyeagle
::I was working with this yesterday, trying to figure out what’s wrong. I think the problem is that the Xorg directory is simply missing. Gone, with all its contents too.
——————————-Here was vital output, when I entered the startx command as root:
Using config directory “/etc/share/x11/xorg.conf.d”
Using system config directory “/usr/share/x11/xorg.conf.d”
) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error(1).
Closing log file.ornation. (EE) (II
Xinit: giving up
Xinit: Unable to connect to X server: connection refused
Xinit: Server error
————————————–Here was some output when I entered the startx command as a regular user:
Fatal server error:
(EE) Cannot open log file “/home/spirit/.local/share/xorg/Xorg.0.log”
———————————Changing directories & doing ls at the command prompt, I found that the /home/spirit/.local/share/Xorg/ directory simply doesnt’ exist – and I suspect based on the error message, that it should.
- This reply was modified 1 year, 4 months ago by scruffyeagle. Reason: typos
December 28, 2021 at 9:58 am #73944Member
sybok
::My ‘/home/sybok/.local/share’ does not contain [Xx]org directory at all. (antiX-19.b2_x64-full with testing repositories)
Did you manage to free some space?
The error could occur due to failure to create some intermediate/auxiliary files.- This reply was modified 1 year, 4 months ago by sybok. Reason: Free space added
December 28, 2021 at 11:05 am #73951Moderator
caprea
::Did you already try to free some space, according to the suggestions that Dave and Moddit have made?
It’s your main problem that there’s no space, the partition on the hard disk is full, you can see it on the photo.Partition:Id1: / size: 23.91 Gib used: 23,89 Gib (99,9%) fs:ext4 dev:/dev/sda2
Xorg might works again when there’s space.
December 29, 2021 at 6:45 am #74014Memberscruffyeagle
::Wow! I didn’t catch that, info about drive space. Yes, definitely.
Earlier this evening, I applied all the suggestions people have given me. Wiped out .cache, tmp, & logs. When I rebooted, it made it to the login screen, and from there into the desktop. BUT – it’s still not fixed. I have a new problem now. (Just to restate this, I’m using the Space-ICEwm desktop in an Antix v19.3 (upgraded) OS.)
Here’s the problem:
I can’t mount the encrypted partitions as drives, using VeraCrypt. VC itself seems to work properly. It can find the encrypted partitions on the external drive, and proceeds normally through entering the password, and gaining the Admin permissions. (I’ve tried this using different partitions, so it’s not just one; it’s always the same.)Then, I see a few things in rapid succession:
* I see the selected drive’s info in the appropriate text box of VC’s drives list.
* I see a new file manager window open, showing the newly mounted drive.
* I see the newly mounted drive disappear from the file manager’s window.
* In VC, I find that the newly mounted drive has disappeared from VC’s list (leaving it empty again).So, although I can now get into the desktop environment, my ability to actually make use of the OS is still severely crippled. I can’t mount the external drive’s partitions, to work with my files.
December 29, 2021 at 12:12 pm #74033Member
sybok
::I have never used VeraCrypt (VC).
Does VC have a CLI interface or if/can you start it from CLI (e.g. by executing ‘veracrypt’ or whatever is the name to call)?
I would expect thus started VC to produce errors printed in the console for you to share with us?
VC also may store some information in a dedicated log.How about re-install of VC or trying a different software if it manages better?
- This reply was modified 1 year, 4 months ago by sybok.
December 31, 2021 at 1:05 pm #74221Memberscruffyeagle
::I have never used VeraCrypt (VC).
Does VC have a CLI interface or if/can you start it from CLI (e.g. by executing ‘veracrypt’ or whatever is the name to call)?
I would expect thus started VC to produce errors printed in the console for you to share with us?
VC also may store some information in a dedicated log.How about re-install of VC or trying a different software if it manages better?
Thanks for the reply. I’m not sure if VeraCrypt can be run from a CLI. I suppose it could be started that way, but I can’t imagine its functions working properly for mounting drives in a securely encrypted manner, if one has to type in the secret password via a terminal screen.
Ever try typing 128 semi-random characters accurately, without being able to see them for verification? I’ve tried this, and it’s quite difficult unless your an EXCELLENT typist. (Which, I’m not.)
That’s a good suggestion about the log. I’ll give it a search, next time I’m trying to fix that OS.
VC wasn’t available via the repos. I had to download a package from the creator, and it was difficult to install. I’m not even sure how to go about uninstalling it. But, I have the impression it’s doing its job properly – it’s just that mounting of the drive isn’t sticking.
There really is no other comparable software. VeraCrypt is the successor to TrueCrypt, of which the development was abandoned by its author. There were speculations, that the spooks were leaning on him to install backdoors into the encryption process – so he quit. But, there’s no proof of that. Others picked up the open code, and pursued development of it…
There are other encryption programs, but they’re nowhere near as evolved as VC. The interfaces are incredibly clumsy, and the instructions are obscure to nonexistent. I tried “zulucrypt” at one point, and it was AWFUL! Re-read my comment about typing… That was zulucrypt. It was incapable of displaying the passwords one typed in. Or, if it could display them, I was unable to find that option.
I’ll see what I can do, about finding a VC log.
-
AuthorPosts
- You must be logged in to reply to this topic.
