Pacman -Syu error resolution

lilsirecho · 2004-01-22 05:47:25

Attempting pacman -Syu

Received "font config conflicts with XFree86, Remove XFree86 (y,n)?
"
What action do I take to allow the upgrade to continue?

Xentac · 2004-01-22 05:56:23

Let's see... the safest thing to do is... read the announcement section! Everything you need to know about problematic upgrades is in there.

lilsirecho · 2004-01-22 06:14:57

Hello xentac, please advise as to what and where the "announcement section"

Xentac · 2004-01-22 06:32:28

Right at the top of the Forum Index there's a section called "Announcements" If you still can't find it, I've included a link.

http://bbs.archlinux.org/viewforum.php?f=24

lilsirecho · 2004-01-22 18:26:45

Thanks for the info, xentac.

lilsirecho · 2004-01-23 20:09:41

Xentac:

If a person upgrades arch per the instructions given in the announcement, I assume that I will lose GUI KDE along with X and will have to re-setup KDE to open and so-on.

I also assume that this will occur every time I upgrade using Pacman -Syu and there is no escape from the "Ugly X-86 upgrade".

Do I understand the situation correctly?

contrasutra · 2004-01-23 20:52:31

No, you don't. Your KDE/GNOME/whatever preferences are not stored in anything that has to do with XFree86.

You will have to restart X, but none of your settings will be gone.

lilsirecho · 2004-01-23 21:05:39

Please excuse my persistence but the statement given in reply said "no you don"t" and I "don't" what? Don't understand or don"t have to do the procedure every time I update?

I still assume I can escape the "Ugly X-86 upgrade" by some other procedure which might involve using a previous release of X-86.

The big question to answer is...Does the pacman -syu activity require the "ugly X-86 " every time it is used?

lilsirecho · 2004-01-23 22:02:02

To make certain I understand the procedure, I expect to do the following:

Enter ...... # pacman -Rd xfree86.....

The above exactly as appears.

I expect that something will happen to my display....

I do not know what will occur first off. Then I assume I do not need to restart the computer but must enter :

#pacman -Sy xfree86 ....enter

This is expected to install xfree86 by pacman with the fonts no longer in conflict thereby.

I expect I have to ......#startx..enter :However, to provide KDE at start up I need something further I seem to recall.

Do I have this procedure correct? If so, what happens after the first ...#pacman -Rd xfree86 enter.....? Does my screen go blank?

tsykoduk · 2004-01-23 22:26:53

pacman -Rd xfree86 will remove xfree86 - the X windows server. KDE will still be installed, Gnome, XFCE or other WM's will still be there. Just X will be gone.

IMHO I would do all of this from a console log in.

To get to a console login.. at the KDE log in, you should be able to choose login type - and console - or just hit <crtl><alt><f1>. Login as root (or yourself then SU). Then head on over to /etc/rc.d and do "./kdm stop". This will shut down X. Then go ahead and do "pacman -Rd xfree86" and then "pacman -Sy xfree86". Your X server should be uninstalled and re-installed. You can then do "./kdm start" and get your nice, pretty KDE Login.

Good Luck!

lilsirecho · 2004-01-23 23:02:58

I am getting in the soup even deeper with each question I ask.

I don't know what a " console login" is and have done everything as "root".

What occurs if I enter "ctl..alt.f1"?

When I go to "/etc/rc.d" in what manner do I address it with "./kdm stop" since it usually requires an "Edit" to be performed in my experience. I assume I get to /etc/rc.d with a "cd"command.

As you can see, I am not an expert in linux.

The last comment: After installing #pacman -Sy xfree86 .....is the entry....
./kdm start.... made in "root" or somewhere else? In addition, previous mention of "startx" was made. Is this required before ./kdm start?

tsykoduk · 2004-01-23 23:15:03

No problem - we all start somewhere

WHen you hit <ctrl><alt><f1> you should see a text based login prompt. Just login.

To get to /etc/rc.d - type in cd /etc/rc.d

that will change you to the /etc/rc.d directory

Then

#./kdm stop

- you are telling the kdm deamon to stop running - which shuts down Xwindows

then you remove and re-install X

then you

#./kdm start

telling kdm to start running again.

You should <ctrl><alt><f1> again and issue an exit command until you see the login prompt

#exit

when you see the text based login prompt, you should be able to <ctrl><alt><f7> to get back to the KDM.

lilsirecho · 2004-01-24 00:47:20

tsykoduk:

Performed the.... ctl alt f1.... and entered root and password...

Next...cd /etc/rc.d... enter
Next#./kdm stop... enter

Result: no such file or directory....

tsykoduk · 2004-01-24 00:52:01

Sorry - I did not remove the hash mark...

./kdm stop

./ tells you to run something in the same directory that you are in

kdm is the deamon

stop tells it what to do

lilsirecho · 2004-01-24 00:58:27

The hash mark (#) is part of the preamble..
I entered (./kdm stop) and received the "no such file or directory" result.

tsykoduk · 2004-01-24 01:16:07

[root@linux /]# cd /etc/rc.d
[root@linux rc.d]# ls
crond  fam  hotplug  network  nscd  slapd  syslogd  yppasswd
cups functions  kdm  nfsd portmap  spamd  xinetd   ypserv
esd gdm klogd nfslock  samba sshd   ypbind
[root@linux rc.d]#

That is what my rc.d directory looks like - if yours does not have the kdm - I dunno... try xdm (if you have it) or gdm? When you boot into linux do you get a GUI login or a text login?

If you get a text login, then no worries.

Accually - no worries anyways. I would just do the upgrade then restart X (<ctrl><alt><del> does that when you are in X).
[/code]

lilsirecho · 2004-01-24 01:31:18

I do not have kdm in /etc/rc.d

I have a GUI login ... root / password .....

From what you say, I should continue with the procedure and end it with ctl alt del .... then on reboot will everything be back to normal
????

tsykoduk · 2004-01-24 01:34:14

reboot is not nessary - just a restart of the X server - the clt alt del will force a restart of the X server and read in the new code. If you want to reboot it should not hurt anything

Xentac · 2004-01-24 01:34:36

He means <ctrl><alt><backspace>. That kills the X server, when you're in X. Because you have a graphical login thingy X will start right back up again, but it will be the new version.

Then again, <ctrl><alt><del> would do something similar because it would restart the whole machine.

tsykoduk · 2004-01-24 01:36:40

Yeah.. ctrl alt del, crtl alt backspace - same flavor right?

lilsirecho · 2004-01-24 02:01:27

Gents:

Performed the pacman procedures w/o the ./kdm stop and start and the system loaded the new Xfree86 and I am back up in KDE.

I will later try the Syu command for full system upgrade.

Thank you for your patience....

lilsirecho · 2004-01-24 03:30:23

After entering ....pacman -Syu.......

The download commenced and entered all upgrades ending with xemacs-21.5.16-2....... This was followed by:

Checking package integrity...

This was followed by:

archive scrollkeeper 0.3.12-5.pkg.tar is corrupted....

What should I do next?

lilsirecho · 2004-01-24 03:56:51

Does this failure mean I have to rerun ...pacman -Syu.... and wait for the downloads again?

sarah31 · 2004-01-24 04:47:58

try pacman -Sc, (make sure your pacman is up to date) then try -Syu'ing again.

lilsirecho · 2004-01-24 06:34:50

performed the ....pacman -Sc.....
Performed .....pacman -Syu......
No errors occured and system returned to root prompt after checking for file conflicts.
How can I be sure the system is upgraded? Some warnings appeared concerning changes to file extensions such as; /etc/modules.conf.pacsave.

Arch Linux

#1 2004-01-22 05:47:25

Pacman -Syu error resolution

#2 2004-01-22 05:56:23

Re: Pacman -Syu error resolution

#3 2004-01-22 06:14:57

Re: Pacman -Syu error resolution

#4 2004-01-22 06:32:28

Re: Pacman -Syu error resolution

#5 2004-01-22 18:26:45

Re: Pacman -Syu error resolution

#6 2004-01-23 20:09:41

Re: Pacman -Syu error resolution

#7 2004-01-23 20:52:31

Re: Pacman -Syu error resolution

#8 2004-01-23 21:05:39

Re: Pacman -Syu error resolution

#9 2004-01-23 22:02:02

Re: Pacman -Syu error resolution

#10 2004-01-23 22:26:53

Re: Pacman -Syu error resolution

#11 2004-01-23 23:02:58

Re: Pacman -Syu error resolution

#12 2004-01-23 23:15:03

Re: Pacman -Syu error resolution

#13 2004-01-24 00:47:20

Re: Pacman -Syu error resolution

#14 2004-01-24 00:52:01

Re: Pacman -Syu error resolution

#15 2004-01-24 00:58:27

Re: Pacman -Syu error resolution

#16 2004-01-24 01:16:07

Re: Pacman -Syu error resolution

#17 2004-01-24 01:31:18

Re: Pacman -Syu error resolution

#18 2004-01-24 01:34:14

Re: Pacman -Syu error resolution

#19 2004-01-24 01:34:36

Re: Pacman -Syu error resolution

#20 2004-01-24 01:36:40

Re: Pacman -Syu error resolution

#21 2004-01-24 02:01:27

Re: Pacman -Syu error resolution

#22 2004-01-24 03:30:23

Re: Pacman -Syu error resolution

#23 2004-01-24 03:56:51

Re: Pacman -Syu error resolution

#24 2004-01-24 04:47:58

Re: Pacman -Syu error resolution

#25 2004-01-24 06:34:50

Re: Pacman -Syu error resolution

Board footer