1. | How can I upgrade KDE3.1.1 to 3.1.3 ? |
| Stefan Parvu
SuSE 8.2 ships with KDE 3.1.1 Right now there are already the new KDE
3.1.3 packages out. You can find them to this ftp address: ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE
There are many ways to update your KDE 3.1.1 to KDE 3.1.3 under SuSE 8.2:
yast, manual or using apt-get We will present the Yast version. Procedure 1. Scenario 1 "One directory" -
Pick up your SuSE distribution version and download all rpm files from:
ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_8.2
-
Place all rpm files under one directory, eg. kde-3.1.3
Close the kdm by switching to level init 3
# init 3
-
Change the directory to the KDE update directory and start yast as root:
# cd kde-3.1.3
# yast -i *.rpm
Wait until yast will finish to install all rpm files
-
Fix system dependencies
After this phase you will find out that some packages are reported to use wrong library versions.
The libwmf is one of them; this library has been updated to version 0.2.8 from version 0.2.6
Start Yast2 and select: Install and Remove Software .
You notice an warning from Yast2 about libwmf library.
You can select to remove all packages or Ignore Conflict and Risk System
Inconsistencies ... Many users have reported that ImageMagic works fine with
the new library. So you can easily choose Ignore Conflict and Risk System
Inconsistencies
Procedure 2. Scenario 2 "Use Yast2" Another solution to upgrade KDE 3.1.1 is to use the Yast2 GUI tool.
Download all KDE 3.1.3 files from the above mentioned ftp site.
-
Start Yast2
-
Select 'change Source of Installation'
-
Add a new source ofinstallation by clicking Add button and selecting Local directory
-
Under Add Local Directory dialog input the path where all KDE
3.1.3 files are saved /home/smith/KDE3.1.3/update_for_8.2/yast-source
It is also possible to point to a ftp server for instance
ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_8.2/yast-source as install source.
-
The new source will be visible under Yast2. Enable the source to On and switch
all other to Off, if you have any. You should have at least one due your initial Suse installation.
-
Close Software Source Media by clicking to Close button
-
Select System Update and select next if you need that Yast will create a backup. If you
don't need unselect Create Backup
-
Choose Update Installed Packages only. Unselect Clean up the system
Yast will detect all KDE stuff and install them.
You can repeat and fix the system dependencies as presented under Scenario 1, above.
|
2. | How do I start up an application each time the PC is booted into KDE ?
|
|
Jon Klaussen
For which purpose the nice people at KDE provide us with... the "Autostart
Folder"... ;)
Look in .kde2/ in your home
directory... and check this out:
http://www.kde.org/documentation/userguide/all-about-your-desktop.html#THE-AUTOSTART-FOLDER
|
3. | After upgrading to KDE3, KDM is unable to start KDE. How can I fix it
?
|
| To fix it: -
mkdir /opt/kde3/share/config/kdm
ln -s /etc/opt/kde3/share/config/kdm/kdmrc /opt/kde3/share/config/kdm/kdmrc
ln -s /etc/X11/xdm/Xaccess /opt/kde3/share/config/kdm/Xaccess
-
Edit the files in /etc/SuSEconfig and change:
qt2 → qt3 and
kde2 → kde3
-
edit /etc/init.d/xdm, change:
kde2 → kde3
-
Add kde3 to
/usr/X11R6/bin/wmlist
-
Add kde3 to the sessionlist in
/etc/opt/kde3/share/config/kdm/kdmrc
-
Add kde3 to
/etc/ld.so.conf
-
run ldconfig
-
run rcxdm start
|
4. | After upgrading to KDE 3.03, there's no background in KDM
|
|
Szabó László
This is because of the missing path from qt plugin configuration. If you
check the qtconfig Library Paths settings, you will see
all previously installed qt plugin paths in the list, but not the current
(3.0.5). If you add the correct plugin path (/usr/lib/qt-3.0.5/plugins), you will see
jpeg images in file preview or kview etc...once again.
You may have to restart KDE once you make the changes in
QTconfig. Just open a shell/console window and
type qtconfig and it will open up! Go to the
Library Paths tab and add the new path to
qt 3.0.5 plugins! That will take care of all your
jpeg problems in the main KDE screens, but your login background will
still have to be a png for now, as it does not affect that image format.
Note
Graham Murray
I have found what I did wrong. I thought that qtconfig was
global, so I ran sux first and made the changes as root. When I ran
qtconfig as my normal user and restarted kde, jpegs worked again.
|
5. | How can I have the Numlock turned on when KDE
starts ?
|
|
Go to+-> and select the Turn on radio button
in NumLock on KDE startup under the Advanced tab.
|
6. | How can I apply/install a different splash screen to KDE ?
|
|
-
Open konqueror
-
Create the directory ~/.kde/share/apps/ksplash/pics
-
Browse to ~/.kde/share/apps/ksplash/pics
-
Move and decompress your new splash screen file into the konqueror
window.
|
7. | How can I autoboot to selected user ?
|
| ->->
|
8. | How can I change the KDM backround for KDE3 under SuSE 7.3 ?
|
|
If you use kde3 and /opt/kde3/bin/kdm as login-manager, and always get an
ugly grey xdm-ish background, make sure you have the following lines in
/etc/X11/xdm/Xsetup:
kde3root=/opt/kde3/bin #Somewhere near line 52
for p in ${kde1root}/kdm \ #Starting circa line 62
${kde2root}/kdm \
${kde3root}/kdm
do
|
9. | How can I set the KDE Defaults for any new users ?
|
|
To change the menu for all users, you have to modify the general kde menu
that is in /opt/kde3/share/applnk. If you want to
add a new icon that is not present there, you have to create a new
.desktop file and you may specify the following
fields:
[Desktop Entry]
Encoding=UTF-8
Name= #name of the application in menu
GenericName[i18n]= #text within brackets in menu, i18n is the code of the
# language you're using, [en] I suppose... :-)
Exec= #name of the application o execute, you can specify full path
Icon= #name of the icon of the applicatio, you can specify full path. !! If
#you don't put anything here you're entry won't be displayed in the menu
Type=Application
Terminal=0 #whether the application has to be executed in a console. 0 for
#none
To add a new menu or submenu, simply create a new folder and assign it an
icon you like. For the folder to be displayed you must at least put a
.desktop file in it.
The /opt/kde3/share/applnk is merged with the personal user-kde directory to
generate the menu for each user. If the ~/.kde/share/applnk doesn't contain
any entry, the whole /opt/kde3/share/applnk menu will be displayed. If it
contains different entries, those will be displayed next to the ones of
the general kde menu. If it contains an entry that is in the same folder or
subfolder of the general menu and has the same name, the entry won't be
displayed in the menu.
For example, if you have:
/opt/kde3/share/applnk/Applications/[empy]
and
~/.kde/share/applnk/Applications/xmms.desktop
The xmms entry will be displayed in the folder 'Applications' of the Kmenu,
but if you have:
/opt/kde3/share/applnk/Applications/xmms.desktop
and
~/.kde/share/applnk/Applications/xmms.desktop
The xmms entry won't appear in the menu. Note
I did this by eliminating the SuSE menu and using the Kmenu, if you want
to use the Suse menu you'll have to change the entries in the SuSE menu. I've
uninstalled it and now I can't remember where it was stored, but if you can
find it, things work the same as for the Kmenu.
In respect to the icons on the desktop, I don't know how to add new ones.
There's a script in /opt/kde3/bin/startkde written
for SuSE that substitutes the original
/opt/kde3/bin/startkde.original that
do the job of creating the new desktop icons when a user logs in for the first
time. But as I don't know bash script programming very well, I decided to
create my own icons manually and I uninstalled the SuSE theme. This way only
aTrash icon is created on the desktop. If you know bash
programming, I think it wouldn't be difficult to understand the SuSE script
and change it to create your own desktop icons. |
10. | How to compile KDE from CVS ?
|
|
Anders Johansson
On request, a little mini-howto on how to compile kde from cvs
It's probably a good idea to do all this in one terminal window. If you set an
environment variable in one konsole window, that variable will not be set in
another window, so stay in one window when you do this.
First of all, make sure you have cvs installed. It is on SuSE's CDs.
You also need gcc, gpp, automake, autoconf and yacc. I can't list here
everything you need exactly. If you install the "development" setup in yast,
you should get most, if not all of it. I never worry too much about that,
because the compilation scripts will complain if you lack a certain package
you need. Just install it as you go along. -
Check out the code from cvs
-
You need to tell cvs which server to download from, and you need to log in to
it.
export CVSROOT=:pserver:anonymous@anoncvs.kde.org:/home/kde cvs login
-
There is no password, so just hit enter when it asks you.
-
You only need to login once. If you decide to update your code in two weeks
you only need to do the "export", not the "login" then.
-
make a directory where you put the source. I keep mine in
/home/andjoh/src/kde-3.1. Then "cd" to that directory (in my case, "cd
/home/andjoh/src/kde-3.1")
-
Now download what you want to compile. You need the base bits, the rest is "if
you feel like it".
-
cvs co qt-copy
to get an up-to-date version of qt.
cvs co arts
cvs co kdelibs
cvs co kdebase
-
Those three are needed. Then you can download
"kdenetwork",
"kdemultimedia",
"kdegraphics",
"kdegames",
"kdeartwork",
"kdeutils"
"kdeaddons" and
"kdeextragear-1" if you want them. But
only the first three + qt-copy are actually needed to run
kde.
-
Compile qt-copy
-
You can find this info in the file README.qt-copy
cd qt-copy
export QTDIR=$PWD
make -f Makefile.cvs
./configure -system-zlib -qt-gif -system-libpng -system-libjpeg \
-plugin-imgfmt-mng -thread -no-stl -no-g++-exceptions
make symlinks sub-src sub-tools
This will run for some time.
-
Compile kde
-
First you need to decide where you're going to store the compiled binaries. I
keep them in my home directory, in /home/andjoh/kde3.1
export KDEDIR=/home/andjoh/kde3.1
cd arts
make -f Makefile.cvs
./configure
make
make install
This is the magic sequence for compiling all the packages in kde. Simple, no?
:)
cd kdelibs
make -f Makefile.cvs
./configure
make
make install
cd kdebase
make -f Makefile.cvs
./configure
make
make install
Those four packages should be handled in that order.
The procedure is exactly the same for the rest of the packages you decided to
download. You can do them in any order, except that kdeaddons should be done
last of all.
-
Now, to use this, put these lines in your ~/.bashrc
export KDEDIR=~/kde3.1
export QTDIR=~/src/kde3.1/qt-copy
export WINDOWMANAGER=~/kde3.1/bin/startkde
export PATH=$KDEDIR/bin:$PATH
export LD_LIBRARY_PATH=$KDEDIR/lib:$QTDIR/lib:$LD_LIBRARY_PATH
export KDEHOME=~/.kde31-test
-
Log out and back in and you should see the brand new kde3.1 start up and your
old kde 3.0.x settings won't be affected. Comment out those lines in .bashrc
to get back to the old kde.
Note
with those lines in .bashrc, kde3.1 will start up regardless of what you
select from kdm. This isn't really a "nice" solution, but it was the first
one I could think of :) If anyone has a better idea of how to do this in a
more "SuSE" manner, please speak up :)
|
11. | How can I change the KDE dpi settings ? |
|
Stefan Parvu
You can easily change the dpi settings for KDE env by editing the Xservers file found under:
/etc/opt/kde3/share/config/kdm directory. Edit the file and change the :0 local line like:
:0 local /usr/X11R6/bin/X vt7 -dpi 100
you just have to add after vt7 the '-dpi 100' or whatever other setting you would like. 'Dpi 75' is another solution.
|