Forum › Forums › New users › New Users and General Questions › Problems upgrading Antix17 to 19
- This topic has 11 replies, 2 voices, and was last updated Apr 1-4:08 am by anticapitalista.
-
AuthorPosts
-
March 30, 2020 at 10:59 pm #34093Member
DaveW
I made a previous post on this subject. But it disappeared after an edit.
After trying a liveUSB of bare Antix19, I decided to upgrade my existing 32 bit Antix 17.4.1 system, by following the steps shown in the post “Upgrading antiX-17 to antiX-19”.
Step 5 is apparently no longer valid with the isos available now (since March 27) according to other posts. This step should be edited, to show that it is only needed with older isos. (This caused confusion, because apt-get complained that libpam-elogind-compat could not be installed, due to a held program, As far as I can see, there is no held program. But until discovering that elogind was no longer an issue, I was stuck.)
Unfortunately, my initial attempt was interrupted, and failed because I accidentally skipped the final step
“apt-get install –reinstall desktop-session-antix”
The system appeared to boot, but the desktop never came to life.My question, in the post that disappeared, was whether there was a way to recover from my mistake.
When the post disappeared, I decided the quickest cure was to re-install Antix 17 from backup (did so successfully), and to try the upgrade steps again, more carefully.I did so. Things appeared to progress well. The process completed successfully. But upon reboot,the system behaves just the same… it appears to be booting up, but the desktop never opens.
I was hoping to avoid starting from scratch with a bare system. But maybe that’s all that remains.
Your suggestions will be appreciated.
March 31, 2020 at 5:01 am #34101Forum Admin
anticapitalista
::I made a couple of edits to the “Upgrading antiX-17 to antiX-19” post.
Check that /etc/slim.conf is configured to use your username.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 31, 2020 at 12:23 pm #34121MemberDaveW
::Check that /etc/slim.conf is configured to use your username.
The slim.conf file is very similar to the previous version (last modified Sept 15, 2018). In the old file, the only mention of my username is commented out in the “default user” section. In the new file, the only mention of username is ‘demo’ which is commented out in the same place. Perhaps slim.conf references another file for username?
Thank you for editing the original “Upgrading antiX-17 to antiX-19”. I skipped step 5 completely. Therefore, apulse was not installed prior to “apt-get dist-upgrade.” Is this fixable? (Assuming that the upgraded system can eventually be booted.)
Thanks…
- This reply was modified 3 years, 1 month ago by DaveW. Reason: corrected an error in first paragraph
March 31, 2020 at 12:44 pm #34123Forum Admin
anticapitalista
::Does
apt -f installshow any issues?Do you autologin?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 31, 2020 at 1:17 pm #34128MemberDaveW
::I do not usually auto-login.
I don’t know how to run “apt -f install” when I can’t start the system.
I got access to the slim.config file on the harddisk, by running a liveUSB.
More info (perhaps some clues?)…
During the apt-get dist-upgrade, there were several warnings. I may have missed some, but I noted these:
— Failed to delete /etc/polkit-/nul/backend.conf.d (directory not empty)
— Unable to delete /etc/cryptset-intramfs
— Unable to delete /etc/gnome/epiphany
— Unable to delete /etc/gnome
— Ignored file (not found) /etc/ld.so.conf.d/i-386/invx-gnu_EGL,conf
— Ignored file (not found) /etc/ld.so.conf.d/i-386/invx-gnu_GL,conf
— There were also some warnings about a broadcom-sta modules and DKMSDuring the attempted Antix19 bootup dialogue, there are warnings that UFW failed to load or start.
- This reply was modified 3 years, 1 month ago by DaveW. Reason: added pertinent information
March 31, 2020 at 1:52 pm #34133Forum Admin
anticapitalista
::Boot normally, and when it fails to get you to desktop, do Ctrl Alt F1.
This will dump you to a console.
Then login as root, password, then typeapt-get update && apt-get -f installSeems like you installed some stuff that may have caused breakage.
Running the above command will help us.Also, do/did you have nvidia drivers installed?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 31, 2020 at 3:44 pm #34139MemberDaveW
::Thank you… here’s what happened…
$ apt-get update && apt-get -f install Reading package lists... Done E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied) E: Unable to lock directory /var/lib/apt/lists/ W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied) W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)Tried the same, but: sudo apt-get update && apt-get -f install
The dialogue shows that it attempted to connect with several repositories, but in all cases, the repos “Could not be resolved” (apparently, internet connection is broken, but external router shows the computer connected),
Also the following messages:
W: Some index files failed to download. They have been ingnored, or old ones used insteand E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?For what it’s worth, I am able to change directories and open Midnight Commander.
I was not knowingly using nvidea drivers. However, I think they were mentioned during the original dist-upgrade.
- This reply was modified 3 years, 1 month ago by DaveW. Reason: added line to answer question
March 31, 2020 at 3:55 pm #34140Forum Admin
anticapitalista
::sudo apt-get update && sudo apt-get -f installPhilosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 31, 2020 at 4:03 pm #34142MemberDaveW
::Thanks for the correction. I ran…
sudo apt-get update && sudo apt-get -f installResults were similar to the above post.
— could not resolve repos
— failed to fetch…
— files failed to download. They have been ignored… using old files…
— 0 upgraded, 0 newly installed, 0 to remove, 0 not upgraded.March 31, 2020 at 4:07 pm #34143Forum Admin
anticapitalista
::Try using ceni to connect.
sudo ceniPhilosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
March 31, 2020 at 4:39 pm #34144MemberDaveW
::I’m not familiar with how to use ceni.
However, I’m on a wired connection, using eth0. Ceni said that was already configured, But I asked it to reconfigure, leaving the address boxes open. After reconfiguration, it shows ip address info. But, the “sudo apt-get update” still does not connect.While your help is very much appreciated, I’m afraid I am wasting your time, and probably should start with a fresh install. Let me know what you think.
April 1, 2020 at 4:08 am #34167Forum Admin
anticapitalista
::Start with fresh install since we can’t get connected to the net.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
-
AuthorPosts
- You must be logged in to reply to this topic.