LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Installing KDE 3.2 on SuSE 9.0 (https://www.linuxquestions.org/questions/linux-newbie-8/installing-kde-3-2-on-suse-9-0-a-150938/)

MatthewASmith79 02-26-2004 06:55 PM

Installing KDE 3.2 on SuSE 9.0
 
Hey Gang:

Hey anyone want to give me a blow by blow description on how to install KDE 3.2 on SuSE 9.0? It seems like they are trying make it as hard as possible, and by they I mean everyone who provides the packages. I don't know what order to to install them in, which ones to install, whether to use Yast2 or whether to use Konsole; all I know is I don't want to do irreparable harm to an OS that is working fine with KDE 3.1.4. Like I always say, I am not a computer idiot, but I am new to Linux so I do need some major hand holding but not the type that you would give to your mother who is still trying to grasp the fundamentals of "point and click," icons, and computer solitaire. :D

Cheers :Pengy:

Dabria 02-26-2004 07:16 PM

This is the way I got it up and running 2 different machines and the only problem I could find was that libmusicbrainz was missing to get Juk up and running but that was quite easily fixed.

In konsole

su
then
rpm -Uvh --nodeps --force *.rpm

Pretty sure this is not the best way of doing it but worked for me.

Just forgot to add that I did this after downloading all 90 rpm's in the KDE 3.2 directory


MatthewASmith79 02-26-2004 11:53 PM

Thank you, I figured "--force" would be a requisite of any installation :-)

Cheers

MatthewASmith79 02-27-2004 12:34 AM

Did not work
 
This is what I got when I tried your suggestion:

matthewasmith79@linux:~/KDE 3.2> rpm -Uvh --nodeps --force *.rpm
error: cannot get exclusive lock on /var/lib/rpm/Packages
error: cannot open Packages index using db3 - Operation not permitted (1)
error: cannot open Packages database in /var/lib/rpm
matthewasmith79@linux:~/KDE 3.2>


any suggestions?

I saved all the packages in my home directory, is that the problem?

Cheers

:confused:

philipph 02-27-2004 03:43 AM

Have you tried doing the installing in runlevel 3? (init 3)
The exclusive lock problem seems to be caused by a running KDE environment.

Another (better?) way to install KDE3.2 is to run
yast2 --install *.rpm


It should be no problem that you have your files in the home directory

Philipp

MatthewASmith79 02-27-2004 05:50 AM

hmmm, will running the yast command from Konsole initiate the graphical interphase? Also, how to you run at level 3? I used to be able to do it on Red Hat way back when I tried Linux (4 years ago?) but the ability has since left me lol.

cheers

bitpicker 02-27-2004 06:13 AM

I guess you shouldn't install KDE from within KDE.

I downloaded all the files for KDE 3.2 and set kpackage to include the directory where I put them (I was running kpackage under XFce, any window manager will do, I suppose). I then checked all the packages which were listed as being newer (meaning older versions were installed) plus all packages listed to be new (no previously installed version) which I thought would be useful. Kpackage has a test option, so you can simulate the entire installation process and will be notified about any problems. There were some; I had to uninstall some kdebase3-SuSE file (name is not necessarily correct, but it was similar), and K3B, and I also had to install two or three items from my SuSE DVD, but then finally kpackage gave the go ahead and it worked fine.

Robin

philipph 02-27-2004 06:19 AM

to get to runlevel 3 just type
init 3
as root in the console
in this mode the yast command won´t initiate the graphical interface

gauld 02-28-2004 01:14 AM

Re: Did not work
 
Quote:

Originally posted by MatthewASmith79
matthewasmith79@linux:~/KDE 3.2> rpm -Uvh --nodeps --force *.rpm
error: cannot get exclusive lock on /var/lib/rpm/Packages
error: cannot open Packages index using db3 - Operation not permitted (1)
error: cannot open Packages database in /var/lib/rpm
matthewasmith79@linux:~/KDE 3.2>

You need to be logged in as root in order to install the packages via the rpm command. (Actually, you need to log in as root to install an rpm in whatever way you choose).

Therefore, before you run the "rpm" command that someone gave earlier in this thread, you need to type in the following command (from any directory):

Code:

su
Then, press enter. At this point, you will be prompted for the root password, which you subsequently enter. Then, you will be able to run the above rpm command(s). (At least, it worked for me).

gauld 02-28-2004 01:19 AM

Re: Re: Did not work
 
Oh, and additionally, I had to remove anything related to k3b and koffice before i could install KDE 3.2. Curiously enough, I didn't have to use --force.

kevinatkins 03-28-2004 05:10 PM

hi folks,

I've just installed KDE 3.2 onto a SuSE 9.0 system from the April 2004 coverdisk of 'Linux Format' (UK-based magazine). There were a few pitfalls to be avoided which are detailed in the readme included on the disc (specific to SuSE installations) and which I'll copy here -

Quote:

#
# KDE 3.2 packages for SuSE distributions
#

Disclaimer:

These packages have NOT been tested at all and SuSE do NOT recommend to
upgrade to these. However we build these packages for convenience, but
it is your risc to use them ;)
You should not update, if you want to have a stable system and expect
to get security updates for your installation.

To install these packages via command line you need to
* rpm -e kdebase3-SuSE kdenetwork3-mail
(kdebase3-SuSE has not yet been ported to KDE 3.2 and plain rpm
can not handle the move from kmail to kdepim3 package correct).
* rpm -Uvh taglib*rpm
* install flac and gnokii from your CD/DVD
* rpm -Fvh *.rpm

An alternative way would be to use the yast_source from ftp.suse.com KDE
update packages.

Known issues:
* Qt 3.3.0 final has not been released yet, we expect it next week
and it will be avaible on ftp.suse.com.
The qt packages in these directories contain a late snapshot
(Qt 3.2 would need many patches, so we decided to go the 3.3 way)
* Several issues with updating old configurations, these will be
addressed with SuSE 9.1. However SuSE 9.1 will not fix these, when
you have already updated to KDE 3.2. So you might backup your
~/.kde directory first.
* kdebindings packages are missing atm, they need further fixes and
will appear on ftp.suse.com later
In addition to the above, I had a small issue with k3b, which I just ignored and all still seems to work OK regardless.

Overall, KDE 3.2 seems very nice - some annoying bugs have been fixed at last (i.e. the inability to unmount and eject CD-ROMs, even when they are not in use..), and the whole shebang looks great, with nice shadowed fonts for icons a la Win XP. It also seems more responsive. On the downside, some of the tight SuSE integration has been lost, and JuK seems broken (damn!)..

Hope this helps..


All times are GMT -5. The time now is 03:20 PM.