Forum › Forums › New users › New Users and General Questions › Errors when updating?
- This topic has 15 replies, 4 voices, and was last updated Apr 9-9:52 am by Anonymous.
-
AuthorPosts
-
January 29, 2019 at 4:54 pm #18134Member
SolusUmbra
I tried to install wine and it said I needed to update so I tried to update and it gave me more errors;
could not resolve; “mirrors.rit.edu” “tfp.us.debian.org” “security.debian.org”January 29, 2019 at 5:03 pm #18136Moderator
caprea
::Go to controlcenter~~> maintenance~~> managing apt repos
There you can choose the antiX and debian repos
The internet is up ?January 29, 2019 at 5:12 pm #18137MemberSolusUmbra
::Internet wasn’t first time I tired, I can’t seem to get the wicd to stay on. Changed the repos and it seems to have worked.
January 29, 2019 at 5:23 pm #18139Moderator
caprea
::Did you chose wicd on the live-boot with the F4 key like I said in your first post ?
If not so wicd will not autoconnect on startup.
You could try ceni or you have to make some changes in /etc/default/wicd
So did you use F4 option ?January 29, 2019 at 5:26 pm #18140MemberSolusUmbra
::I tried but I guess I didn’t do it right.
I know this should be a new post, but it says I’m not permitted to make changes to wicd file.- This reply was modified 4 years, 3 months ago by SolusUmbra.
January 29, 2019 at 5:41 pm #18143Moderator
caprea
::Ok, do the following
sudo leafpad /etc/default/wicdThis will open the file with a line like this
START_DAEMON=noChange this line to this
#START_DAEMON=noclose and save
Then go to controlcenter -> Session -> User Desktop Session
In this file it should be line 23 24 25
change it to look like this# Uncomment to show wicd networking monitor wicd-client -t & grep -q "START_DAEMON=no" /etc/default/wicd || wicd-client -t &close and save
wicd should now autostart on bootup
January 29, 2019 at 5:53 pm #18144MemberSolusUmbra
January 29, 2019 at 5:59 pm #18145Moderator
caprea
::No, my file
# Start the daemon by default, let the user disable it. # Use "no" (without quotes) to make /etc/init.d/wicd *NOT* start the WICD daemon. #START_DAEMON=no # By default don't kill connections on daemon shutdown, see # https://bugs.debian.org/816076 and # https://bazaar.launchpad.net/~wicd-devel/wicd/experimental/revision/851 DAEMON_ARGS="--keep-connection"January 29, 2019 at 6:10 pm #18146MemberSolusUmbra
::So my username that I created and “root” user aren’t the same and have different permissions.
When I used the root terminal I was able to access sudo leafpad /etc/default/wicd
and save it.January 29, 2019 at 6:16 pm #18147Moderator
caprea
::Did you also make the changes above in controlcenter -> Session -> User Desktop Session ?
Does wicd now autostart on bootup ?January 29, 2019 at 6:20 pm #18148MemberSolusUmbra
January 29, 2019 at 6:27 pm #18152Moderator
caprea
January 29, 2019 at 6:27 pm #18153MemberSolusUmbra
April 9, 2019 at 5:15 am #20296Member
eriefisher
::Why comment it out instead of changing it to “yes”. This is mine unmolested.
# NOTE: This file is ignored if systemd is used as init system! # # Start the daemon by default, let the user disable it. # Use "no" (without quotes) to make /etc/init.d/wicd *NOT* start the WICD daemon. START_DAEMON=yes # By default don't kill connections on daemon shutdown, see # https://bugs.debian.org/816076 and # https://bazaar.launchpad.net/~wicd-devel/wicd/experimental/revision/851 DAEMON_ARGS="--keep-connection"Just curious as to why this way and not that way.
eriefisher
April 9, 2019 at 5:40 am #20297Moderator
caprea
::There have been slightly different solutions over the past 2 years for this.
Some then started not to work on some systems.
The above until now always worked. I don’t know why. -
AuthorPosts
- You must be logged in to reply to this topic.